I recently installed a fresh version of MainsailOS (Bullseye).
After flashing the Duet, it disappeared.
It cannot be found by lsusb, nor by ‘ls /dev/serial/by-id/*’.
Dmesg reports: ‘unable to enumerate USB device’
According to the linked Github issue, this is directly related to either flashing in Buster or Bullseye.
The issue was unfortunately closed without a proper solution.
Additional Info:
After Plugging in the Duet to the Raspberry, dmesg reports:
[ 503.970560] usb 1-1.3: new full-speed USB device number 7 using xhci_hcd
[ 504.073708] usb 1-1.3: device descriptor read/all, error -75
[ 504.154558] usb 1-1.3: new full-speed USB device number 8 using xhci_hcd
[ 504.257487] usb 1-1.3: device descriptor read/all, error -75
[ 504.262973] usb 1-1-port3: attempt power cycle
[ 504.866606] usb 1-1.3: new full-speed USB device number 9 using xhci_hcd
[ 504.890485] usb 1-1.3: device descriptor read/all, error -75
[ 504.970570] usb 1-1.3: new full-speed USB device number 10 using xhci_hcd
[ 504.994590] usb 1-1.3: device descriptor read/all, error -75
[ 504.995564] usb 1-1-port3: unable to enumerate USB device
There is a known, weird interaction between Bullseye and this board. A developer with this board and the needed knowledge would have to debug this. This has not happened as of yet.
Currently your only solution is to not using Bullseye.
Yep, I saw that you closed the issue back then, but no further investigation has been initiated.
Since the Klipper github issues section seesm only to be allowed for whitelisted users, I hope that Kevin will read this. Maybe he has an idea or at least know the right direction to go as this will possibly impact every Duet user when they switch to Bullseye.
Hi, I have had the same issue. I have tested a lot of different possible solutions to try to solve this issue.
First off, I do have an SD card with a working install, based on Buster with klipper v0.11.0_66_g4671cf2d.
This has been my safe path back to a working install.
I, as many has had failure after failure when updating to all releases after this one. Tried to download MainsailOS several times and build it all from scratch, but to no use, it fails all the time. So - I tried to move the new *.bin file to my “safe install” and do the make flash FLASH_DEVICE=*my printer ID - still fails. (looses the USB connection)
So - today I did it different, I made yet another SD card, but this time I used the rasbian lite img (Bullseye, and Buster) - and dropped MainsailOS, and went for semi automated install trough Kiauh, and to my suprise, it now works both on Buster and Bullseye. I did it on the Buster distro first, found it odd, cleaned my SD, made Bullseye and went troug it all by Kiauh again, and voila, my board flashed just fine.
Weird error, and I have had the same issue on pre v0.11.0_66_g4671cf2d who actually worked on Bullseye. So, my best bet - this has something todo with the Bossa instructions not “getting” it is flashed for usage trough USB.
Hope anyone else found this useful, I have done my “share” of of trial and error- to say the least!
Thanks for sharing your findings!
Best would be to also crosspost this in the thread that I linked above. The most insights and findings are also shared there.
Instaled buster lite.
Instaled klipper and monraker with KIAUG
Flashed with make flash.
After flashing the serial usb address changes. note this .
Then installed mainsail.
Configured the printer file.
Then reboot a few times to ensure consistent comunication.
Then update and upgrade all modules.
Job done. I´m working on an Step by step document.
Thanks so much to Lurifax!!!
do we have any update on this or any new work around? trying to run my duet 2 wifi with klipper. did bookworm fix this issue or is it still only possible to make this work with buster?
