Update LinuxCNC 2.9.5 on debian 13

More
1 year 1 month ago #335243 by PCW
The SmartSerial is also a latency related issue

Pinning the Ethernet IRQ to the top processor in conjunction with isolcpus=LastCPU
can also help a lot (LastCPU =3 for a 4 core processor)

This script can do this temporarily:

 

File Attachment:

File Name: pinirq_2025-09-21.txt
File Size:668 B

Please Log in or Create an account to join the conversation.

More
1 year 1 month ago #335483 by anli
Thank you, I managed to get the machine up and running now.
I fixed the errors in the ini and the glade file (wrong labels).

However, if I try to update to LinuxCNC via
Code:
apt update
, I receive the following error:
Code:
root@linuxcnc:/etc/apt/sources.list.d# apt update OK:1 http://security.debian.org/debian-security trixie-security InRelease OK:2 http://deb.debian.org/debian trixie InRelease                                                                                                                                  OK:3 http://download.opensuse.org/repositories/science:/EtherLab/Debian_12 ./ InRelease                                                                                             OK:4 http://deb.debian.org/debian trixie-updates InRelease                                                                                                                          OK:5 https://tvd-packages.tradingview.com/ubuntu/stable jammy InRelease                                                                                                             OK:6 https://repository.qtpyvcp.com/apt develop InRelease                                                                                                                           OK:7 https://dl.google.com/linux/chrome/deb stable InRelease                                                                                                                        OK:8 https://packages.microsoft.com/repos/code stable InRelease                                       Holen:9 https://www.linuxcnc.org trixie InRelease [31,1 kB]                  Fehl:9 https://www.linuxcnc.org trixie InRelease   Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on EEDD0D29F81DCAA0D258661F3CB9FD148F374FEF is not bound:            Policy rejected asymmetric algorithm   because: DSA1024 is not considered secure since 2014-02-01T00:00:00Z Warnung: http://download.opensuse.org/repositories/science:/EtherLab/Debian_12/./InRelease: Policy will reject signature within a year, see --audit for details Warnung: OpenPGP-Signaturüberprüfung fehlgeschlagen: https://www.linuxcnc.org trixie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on EEDD0D29F81DCAA0D258661F3CB9FD148F374FEF is not bound:            Policy rejected asymmetric algorithm   because: DSA1024 is not considered secure since 2014-02-01T00:00:00Z Fehler: Das Depot »https://www.linuxcnc.org trixie InRelease« ist nicht signiert. Hinweis: Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert. Hinweis: Weitere Details zur Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite apt-secure(8).
Stating that the repo is not signed.
This is my linuxcnc.list:
Code:
deb [arch=amd64,arm64 signed-by=/usr/share/keyrings/linuxcnc.gpg] https://www.linuxcnc.org/ trixie base 2.9-uspace 2.9-rt deb-src [arch=amd64,arm64 signed-by=/usr/share/keyrings/linuxcnc.gpg] https://www.linuxcnc.org/ trixie base 2.9-uspace 2.9-rt
The key lives in /usr/share/keyrings/linuxcnc.gpg
What am I doing wrong here?

Please Log in or Create an account to join the conversation.

More
1 year 1 month ago #335515 by andypugh
You can try downloading the .deb file directly and manually installing.
(sudo apt-get install ./deb-filename )
The ./ is a clue to apt-get to look at a local file rather than on the repository.

It looks like Trixie has a more restrictive archive key policy than Bookworm, and it's going to take me some time to work that out as it's a subject I know next-to-nothing about.

www.linuxcnc.org/dists/trixie/

Please Log in or Create an account to join the conversation.

More
1 year 4 weeks ago #335774 by rodw
It looks like we are using a 1024 bit long key (DSA1024) which is considered insecure by Trixie.
Ref: Google AI
Debian prefers a key length of 4096 bits for RSA OpenPGP keys used for signing, although Ed25519 is now the default for new keys generated with current tools, offering even stronger security.
While 2048-bit RSA keys are still considered secure for some applications, Debian's preference for 4096-bit keys is influenced by both security considerations and the desire to reduce future migration efforts for volunteers maintaining keyrings. This aims to combine potential future migrations from 2048 to 4096 bits into a single, proactive move.
When creating a new GPG key pair for signing Debian packages, you can specify the key type and length, with 4096-bit RSA or Ed25519 being the recommended choices.

and:
A dsa1024 key refers to a Digital Signature Algorithm (DSA) key with a length of 1024 bits, 
 
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
1 year 2 weeks ago - 1 year 2 weeks ago #336572 by andypugh

Hi,
I used Debian 12 LinuxCNC image to install LinuxCNC. Afterwards I updated to Debian 13 as shown here in the forum
Code:
                           Holen:7 https://www.linuxcnc.org bookworm InRelease [31,1 kB]                 Fehl:7 https://www.linuxcnc.org bookworm InRelease

The "bookworm" there should be "trixie" You need to change the distro name in /etc/apt/sources.list.d/linuxcnc.list

To address the key length issue (which, oddly, didn't seem to effect my Trixie installation) I have created a new, longer key and signed the trixie repository with it (I _think)

The new key can be found at keyserver.ubuntu.com/pks/lookup?search=L...gerprint=on&op=index

But the best option is probably to use a new version of the LinuxCNC install script which will install the keys then install LinuxCNC.

www.linuxcnc.org/linuxcnc-trixie-install.sh

This can be downloaded (right-click and save-file-as), made executable ("chmod +x linuxcnc-trixie-install.sh") and then run ("./linuxcnc-trixie-install.sh")

I would very much appreciate it if folk could try this out before I properly announce / release it.[/code][/quote]
Last edit: 1 year 2 weeks ago by andypugh.

Please Log in or Create an account to join the conversation.

More
1 year 2 weeks ago #336618 by f355
Thank you for fixing this, Andy, the new key works just fine!

However, the debian package itself seems to have a broken python3 dependency. I'm on the latest Raspberry Pi OS Lite (which is basically trixie with a custom kernel and a few Pi-specific tools installed). Any particular reason for the arm64 package to want python3 < 3.12? amd64 one depends on 3.13, and so does linuxcnc-uspace 2.9.4 that comes with trixie.
Code:
$ sudo apt-get install linuxcnc-uspace Reading package lists... Done Building dependency tree... Done Reading state information... Done Solving dependencies... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies:  linuxcnc-uspace : Depends: python3 (< 3.12) but 3.13.5-1 is to be installed                    Depends: libboost-python1.74.0 (>= 1.74.0+ds1) but it is not installable                    Depends: libboost-python1.74.0-py311 but it is not installable                    Depends: libgpiod2 (>= 1.5.1) but it is not installable                    Depends: libpython3.11 (>= 3.11.0) but it is not installable                    Recommends: linuxcnc-doc-en but it is not going to be installed or                                linuxcnc-doc                    Recommends: librsvg2-dev but it is not going to be installed                    Recommends: hostmot2-firmware-all but it is not installable                    Recommends: python3-pil but it is not going to be installed                    Recommends: python3-pil.imagetk but it is not going to be installed E: Unable to correct problems, you have held broken packages. E: The following information from --solver 3.0 may provide additional context:    Unable to satisfy dependencies. Reached two conflicting decisions:    1. linuxcnc-uspace:arm64=1:2.9.6 is selected for install    2. linuxcnc-uspace:arm64=1:2.9.6 Depends python3 (< 3.12)       but none of the choices are installable:       [no choices] 

Please Log in or Create an account to join the conversation.

Time to create page: 0.095 seconds
Powered by Kunena Forum