Hi Uwe On 08.04.25 18:56, Uwe Kleine-König wrote: > Maybe it's worth to try to reload the usb bus driver in the broken > state. Something like: > > # cd -P /sys/bus/usb/devices/usb5/../driver/ > # echo 0000:02:00.0 > unbind > # echo 0000:02:00.0 > bind > > (where 0000:02:00.0 is a link in the directory that the first command > cd'd into). Note that
That doesn't seem to be an option. The error messages right now point to "/sys/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2/1-2.2". cd'ing to "/sys/bus/usb/devices/usb1/1-2/1-2.2/" (or just to "/sys/bus/usb/devices/usb1/" fails, nothing happens. > > > a) there might be several device links in that directory, try > > ls -ld /sys/bus/usb/devices/usb5 > > to determine the right one. This shows this symlink: ls -ld /sys/bus/usb/devices/usb1 lrwxrwxrwx 1 root root 0 25. Apr 19:18 /sys/bus/usb/devices/usb1 -> ../../../devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1 With that information I can cd to "/sys/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2/1-2.2", but then I don't understand what you mean with "where 0000:02:00.0 is a link in the directory that the first command cd'd into". The only symlinks in the directory I'm inside now are: driver -> ../../../../../../../bus/usb/drivers/usb port -> ../1-2:1.0/1-2-port2 subsystem -> ../../../../../../../bus/usb cd'ing (with or without -P) into driver shows a lot of symlinks. Anyway, I came to the conclusion with Framework that all this is probably a hardware issue and we hope the issue is fixed with a replacement module. It arrived a couple of days ago and I just left the old one inside to see if I can follow these instructions and if they had any success. I'll be switching to the new module now and hope that this actually fixes things. Fingers crossed. If not I'll be reporting back here in a week or two and maybe we can brainstorm on that issue a bit more. Best Regards Richard
