#RPi bookworm OS crashing on boot, bullseye OS works

1 messages · Page 1 of 1 (latest)

buoyant remnant
#

Recently I needed to reimage my RPi and so I attempted to go from bullseye to bookworm. As soon as I restored my printer.cfg file in klipper and restarted, the OS would crash. SSH drop and no ping. Every time. If I unplugged the USB connections to all MCUs, I could boot the RPi. After spending a week trying to get something to work and repeating the install multiple times, I reimaged my RPi with bullseye. After restoring my printer.cfg, everything comes alive and works. Anyone having this happen?

Hardware:
Voron Trident 350mm
RPi 3+
Octopus control board connected via USB

#

With the bookworm OS crashing, I can't see any log files, so I have no idea what is causing this.

buoyant remnant
#

@heavy plover , you suggested I needed to upgrade to bookworm to fix some issues I had. It seems I just needed a fresh install of bullseye. Have you had issues with bookworm?

heavy plover
#

None

buoyant remnant
#

Anyone know how to get log files when the OS crashes on boot? I'm curious to figure this one out.

rancid socket
#

why are u using bookworm?

#

just flash themainsail image from the rpi imager

buoyant remnant
#

RPi imager defaults to latest OS, bookworm. I thought klipper based images were outdated. I used Eric's guide.

rancid socket
#

i used the btt cb1 with their image for my voron but for my other printer i used the pi imagers image or just ubuntu 23.04

#

with kiauh

buoyant remnant
#

Yeah, I just used kiauh. Worked great. Something isn't working with my setup and bookworm OS. I don't have time to figure out why.

rancid socket
#

just use ubuntu

buoyant remnant
#

I never thought about using ubuntu on a RPi. Since Raspberry Pi OS Bullseye is working good for me, I'm going to stick with it for now. Thanks for the tip though. Still, I find it strange Bookworm kept crashing on my hardware.

eternal pine
#

Similar problem for me. The new 64bit raspbian and armbian with clean install crash on sudo systemctl start klipper. The old (bullseye) 32bit raspbian does not crash

#

Hardware: rpi 3b+, spider, ercf (easy brd)

eternal pine
buoyant remnant
eternal pine
rancid socket
#

Bookworm is giving me issues with docker using umbrell os

eternal pine
#

like what

nova moat
#

I have the same issue hardware RPI 3b+, spider crashes when I have the printer MCU plugged in found out that if I don't enable the TMC part in my config it will work as soon as TMC2209 is enable and you restart klipper it crashes going to give 32bit a try

merry nest
#

I also have this issue. I am currently in the progress of doing a fresh install. Tried the RPI imager images raspbian lite in 32 and 64 bit. Only installed KIAUH and had it install moonraker, Klipper, klipperscreen, mainsail.

My board (skr 1.4 turbo) is recognized in /dev/serial/by-id/ when I plug the usb of the board into the pi when the pi is already running.

However, rebooting with the USB plugged results in a „freeze“? On boot. I can not even SSH into the pi.

Pulling that SD card out and putting in the old card with the previous image is working fine still (bullseye).

Did you find any fix for this?