Hmmm…
Just went through the procedure on two printers, no errors but when I run ls /dev/serial/by-id/* after rebooting I get:
Ideas what I’m doing wrong?
- Is this Debian Bullseye?
- What board you have connected to the host?
- What type of connection does the board have? USB, serial?
- Did you build CanBoot for USB connection?
Here you go.
- Is this Debian Bullseye? Yes:
- What board you have connected to the host? Genuine Raspberry Pi 4B connected to an Octopus('F446)
- What type of connection does the board have? USB, serial? USB
- Did you build CanBoot for USB connection? Yes
Honestly, I thought that you could no longer see the connection in /dev/serial/by-id when you set up CanBoot.
If you are using Klipper in “USB to CAN bridge” mode then the micro-controller is not a “serial device” and will never show up in /dev/serial/. (When Klipper runs in “USB to CAN bridge” mode it instead behaves as a “gs_usb” can bus adapter.) When in this mode, it can therefore not be discovered as a serial device and is also therefore not impacted by a system issue involving the reporting of serial devices.
Cheers,
-Kevin
2 Likes
Thanx Kevin for the explanation.
Hey so it looks like i got the bug too. Sineos, im real new to printers and mcus and barely got enough knowledge to flash a pu with mainsail and update an mcu’s firmware. I see youve given step by step instructions on how to fix this debian bug but im still having issues with following your instructions. Though it may sound funny to others i dont mind asking if you can break it down into layman’s step for this newbee. Please and thanks
Show the output of
cat /etc/apt/sources.list
Use the </> formatting tags here in the post’s menu to properly format the text. Do not use screenshots
Did the firmware install succesfully on the msu ?
Try to install an new mainsail image from rasppberr pi imager. Folow skr steps to reflash the firmware and should work. When reflash, disconect skr power, install usb 5v jumper, insert sdcard and power via usb . Shutdown the skr and see if firmware have chage extension fom .bin to .cur in sd card
Then try to obtain usb definition by “ls -l /dev/serial/by-id/”
1 Like
Thanks i did end up getting the board to work by using usb for connection instead of the uarts. Then noticed a new issue. All my thermistors on the board were reading way off. I know my settings were good as i pasted my old config over when i reflashed so i bought another board. When swapping boards i noticed i had a loose wire that was touching my old board. More than likely i had to have shorted something to cause the initial issues but after re crimping the loose wire and swapping boatlrds, all is working good as expected. Thank you!
Just wanted to say that this just happened to me as well and the above steps solved it. Thank you very much, you are a wizard <3
1 Like
Something weird happened today. I will pass it along in case this is a version of your problem. I fired up my printer uneventfully. Klipper connected to the printer. I remoted in and saw there were updates to Klipper and to System. I loaded both and rebooted the Raspberry PI4 host. Upon reboot, I could not connect to the printer.
Power to the controller board? Yes
USB cable still plugged in Okay? Yes
Cable good? Yes
It was like Klipper could no longer find the board. I ran ls /dev/serial/by-id/* to see if I had a Raspian problem or a Klipper problem. To my surprise the path was no good. I changed directory into /dev/serial/ and there was no by-id folder. There was a by-path folder. So, I ran /dev/serial/by-path/* and copied the result into my printer.cfg and all was well.
So, I am now running fine, but I have no explanation of what happened.
If this happens to you herein lies the fix.
Known issue and already discussed multiple times. See Debian Bullseye Bug causing Klipper to no longer find the printer board
Hello everybody,
I’m running into thre same problem.
I tried using the commands into Debian Bullseye Bug causing Klipper to no longer find the printer board but the commands give me no positive feedback I think:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 0E98404D386FA1D9
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.NhhImxKvYW/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 0E98404D386FA1D9
same thing for the other command.
What should I do? What files do you need (logs, cfg, …)?
Thanks in advance for your attention.
These are warnings and can be safely ignored.
1 Like