…
Suddenly not not being able to get a USB id when running “ls /dev/serial/by-id/*” after an update
Steps tried to resolve this:
Changed the USB cables
Reflashed mainsailos
reflashed the mcu
remade the bin firmware and reflashed
updated the pi
sudo dmesg gives the following output
[ 547.597455] usb 1-1.3: new full-speed USB device number 3 using xhci_hcd
[ 547.703598] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[ 547.703633] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 547.703647] usb 1-1.3: Product: USB Serial
[ 547.799022] usbcore: registered new interface driver usbserial_generic
[ 547.799096] usbserial: USB Serial support registered for generic
[ 547.805280] usbcore: registered new interface driver ch341
[ 547.806438] usbserial: USB Serial support registered for ch341-uart
[ 547.806601] ch341 1-1.3:1.0: ch341-uart converter detected
[ 547.819231] usb 1-1.3: ch341-uart converter now attached to ttyUSB0
Atleast one other person on discord is facing the same issue.
Getting the exact same issue and followed nearly the exact same steps with no resolution.
Here is my log file as well: klippy (2).log (69.8 KB)
[ 156.649029] usb 1-1.1: new full-speed USB device number 3 using xhci_hcd
[ 156.755194] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
[ 156.755217] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 156.755224] usb 1-1.1: Product: USB Serial
[ 156.830704] usbcore: registered new interface driver usbserial_generic
[ 156.830754] usbserial: USB Serial support registered for generic
[ 156.834698] usbcore: registered new interface driver ch341
[ 156.834750] usbserial: USB Serial support registered for ch341-uart
[ 156.834814] ch341 1-1.1:1.0: ch341-uart converter detected
[ 156.842690] usb 1-1.1: ch341-uart converter now attached to ttyUSB0
To add to this use the command "ls /dev/serial/by-path/* "
Then replace /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4:1.0-port0 with the output
An even better fix was found in the Klipper discord by xF4m3 and XeroX:
In case you still have this issue after updating today, i found this fix in the voron discord klipper channel (its a pinned message there)
EDIT: Latest Debian 11 changed by intention or accident by-id and by-path mapping in systemd. This fixes the issue when klipper is not able to connect after recent update of Apr 29th 2023.
Make sure you’re root or using sudo -s before. Reboot is mandatory.
sed -i ‘/^SUBSYSTEMS==“pci”, ENV{ID_BUS}=“pci”./i SUBSYSTEMS==“usb”, IMPORT{builtin}=“usb_id”, IMPORT{builtin}=“hwdb --subsystem=usb”’ /lib/udev/rules.d/60-serial.rules
sed -i 's/^SUBSYSTEMS==“pci”, ENV{ID_BUS}=“pci”./SUBSYSTEMS==“pci”, ENV{ID_BUS}==“”, ENV{ID_BUS}=“pci”, \
ENV{ID_VENDOR_ID}=“$attr{vendor}”, ENV{ID_MODEL_ID}=“$attr{device}”, \
IMPORT{builtin}=“hwdb --subsystem=pci”/g’ /lib/udev/rules.d/60-serial.rules
sed -i ‘/ENV{MODALIAS}==".*/d’ /lib/udev/rules.d/60-serial.rules
The initial workaround was changing to by-path, but this does not work if you change ports. This workaround should fix it permanently and does not collide with future updates of debian.