@Sineos kindly posted a process for identifying whether or not your system is affected by the Debian 11 Bullseye bug: [image] Debian Bullseye Bug causing Klipper to no longer find the printer board Announcements Moved to Debian 11 (Bullseye) udev bug - No board or serial …

Nice work @mykepredko Indeed, I did think about it as well. If done as a script, we should extend the checks and make it less depending on the RPi version, since users might have different Linux flavors installed. Maybe something along the lines of: #!/bin/bash is_udev_version_deb11u2() { # …

[image] Sineos: Nice work @mykepredko Indeed, I did think about it as well. If done as a script, we should extend the checks and make it less depending on the RPi version, since users might have different Linux flavors installed. Thanx - I know it could have been done better. Now, when I re…

[image] mykepredko: Rather than return “0” for true and “1” for false, how about using the true and false Linux commands? In shell scripts, the logic generally is return 0 for true return anything not 0 for false working with true and false in a boolean sense can be tricky in shell and has …

I have turned the instructions Debian Bullseye Bug causing Klipper to no longer find the printer board - #8 into a shell script: https://raw.githubusercontent.com/Sineos/useful_bits/main/Linux/fix_debian_udev.sh It will: Check if it is executed on Debian 11 Check if the installed udev contains th…

To end off this thread, I’ve done a fairly extensive experiment to try and figure out what is the best approach to get to the ultimate goal which is to have an OS/firmware controller installation that can be updated without physically accessing the controller. In terms of updating a controller, I b…

In depth and to the point. I think more makes of things that work should shine while it is difficult, they should still shine. And by shine, I basically mean hold virtue. I like fixtures and builds. The only thing that keeps me from building a machine to call my own is lack of “shine” or “virtue.” …

[image] mykepredko: I know that some people don’t like using a CAN bus interface to their toolheads but this approach will work even if there are no CAN devices attached to the controller. Interesting write up. Thanks. Just to be clear, one should only configure Klipper in USB to CANbus bri…

[image] koconnor: Just to be clear, one should only configure Klipper in USB to CANbus bridge mode if there is an actual functional CANbus with at least 1 additional device attached to it. If these requirements are not met, the Klipper code may appear to work, but will be prone to hard to debug…

FWIW, if you want to test this, run FIRMWARE_RESTART a bunch of times. The buffers will fill and the “bridge mcu” will appear to go offline. Cheers, -Kevin

The FIRMWARE_RESTART button in Mainsail? Is there a command line instruction (like sudo service klipper restart) that can be run repeatedly and monitored to see when the system goes tilt?

Debian Bullseye Bug Remedy Script

General Discussion

Topic		Replies	Views
Problems Implementing Debian Fix General Discussion	20	2703	March 7, 2024
CAN bus, Katapult and Klipper on a Voron 0 General Discussion	14	6613	September 30, 2025
Debian 12 and Klipper General Discussion	39	8982	November 11, 2023
Raspi 4 failing to make usb connection to MCU General Discussion	36	7271	May 5, 2024
Unable to connect to MCU after update General Discussion	33	5850	May 5, 2024

Debian Bullseye Bug Remedy Script

Related topics