perfect ！
thank you very much！
1 Like
I’m running the latest bookworm image and started hearing crackling noise while the device is in use. It is very apparent during boot and shutdown, and overpowers system volume when playing videos.
Appreciate any help!
I assume you’re using a CM5. The crackling is a known issue when the battery is roughly 50%, and gets worse as it gets lower. We’re looking for a fix, but not sure when that’ll happen.
4 Likes
CM5 emmc
Suddenly panel stop to work, as it was before patches (hdmi works). Don’t sure if it a reason, but before 6.12.19 it works. Cant find anything special in logs.
Any advise to troubleshoot?
Thanks for your support.
Did you do any kind of changes, rpi-update? If it was working then just quit something must have changed.
Thank you for the response. Yes I’m using a CM5, but the noise appears even when battery is above 80%. Appreciate your efforts in getting this resolved.
Only updates via apt and rpi-eeprom-update. But it works right after. Can i try somehow install .18 core?
nothing changed between 6.12.18 and 6.12.19 as far as drivers and the CM5 are concerned.
have you removed the back and maybe disconnected the CM5 a bit? have you seen if it’s just your install that might have got borked?
Nothing like that (. Wayland see the panel in display settings on hdmi monitor, all seems to work in logs and /sys/class/backlight/backlight@0/bl_power or actual_brightness. It just black. Very strange.
can you test a fresh image to make sure its not a hardware failure?
i removed lines from boot config:
dtoverlay=spi0-0cs
dtoverlay=test-rp1-audio-out
and added:
enable_uart=0
And it works 
1 Like
I just saw this and wondered if anyone here may find it useful
I’ve already been using pi-gen to build the images and made my own edits that do the same thing that script does. The only advantage to moving from what I already have wouldn’t improve anything for ClockworkPi devices. Starting from scratch rpi-image-gen would be the way to go, but because of all the rotation, hotkey, battery charge rate, and all the other stuff that’s been implemented. It will be easier to stick with pi-gen.
4 Likes
well that was a lot to read. ok pulled out my DevTerm (still waiting on my uConsole) powers on… for about a minute then turns off…
using the CM3. I’ve tried bookworm, bookworm-lite and the kali with no luck. suggestions/ideas?
2 Likes
I have the same system… DevTerm with CM3 and also after editing the config.txt file it didn’t get there either. Too many irons in the fire to play much with it right now. So many want the power of the CM5, I want the low power of the CM3. Not really doing anything compute intensive on it. I did install the latest on the uConsole with CM4, and that works great.
I am waiting to try the next release.
1 Like
I don’t have a DevTerm anymore to test, but the driver that works with the CM4&5 didn’t work with the CM3 and it looks like the old 5.10 driver that worked with the CM3 no longer works under 6.12.
I just tested the image to work with the CM3 in the uConsole. I’ll update the OP accordingly. Maybe Clockwork will send me just a DevTerm screen so I can get it to work.
2 Likes
if not maybe a conversation with me about what changes / additions you’ve done with pi-gen and i can do the legwork. msg me here if that seems agreeable 
It’s not the images that’s the problem with the CM3 and DevTerm. You’ll need to fix the CM3 panel driver for the DevTerm. On my GitHub is the kernel repo everything is already setup to build for the uConsole/DevTerm it’ll be just that one driver that needs worked on to get the CM3 DevTerm to work.
Well I’ll have to try and dig into that then.
1 Like
For the time being, I went back to the old clockwork pi3 image. It works for what I need. For now it is pretty much dedicated to serial/ssh terminal work.
1 Like