I am feeling helpless with this lately. My Uconsole / cm5 and rex’s bookworm has worked for many months in the past. Upon upgrading to Trixie a while back the whole unit has gone a little weird. It will take to the image fine, but will only work with hdmi out and weirdly my hacker gadgets version 1 USB. In board keyboard, screen, trackball, power button ect doesn’t work right. Backlight works, and my power button stays green even when powered off. It will do the same thing now when I go back to bookworm.
I HAVE gotten it to FULLY working just tinkering with the SPI settings in raspi config. But this is inconsistent, and goes back to being strange upon a power cycle.
Anyone smarter than me able to help me trouble shoot? It’s been a long while since I had this operating and really miss using it.
I am not adding custom settings upon imaging. In theory I do seem to be following the steps. Same as before every time I had it working during bookworm times.
The weird issue I am describing is persistent now sadly, so any fresh install including bookworm is being strange. From what I can tell the SPI and maybe I2C stuff specifically is being strange. Not sure if it’s a power delivery issue or not. I did think it was broken hardware but it does start working when I force disable/ enable SPI in Raspi Config a few times (with aid of external monitor and keyboard) but upon a power cycle the weirdness starts again
oh dear. i do not have exactly the same setup as you do. but i would think to eliminate all variables one at a time.
If you had a CM4 before moving to a CM5, perhaps you can use only the default hardware, and just use a CM4 to try. Use an image that is well known to work.
This should aim to identify if there are any mainboard issues. it is then possible to swap out pieces one at time. Time consuming. But i don’t see how else to troubleshoot this affirmatively.
Yes I have, it takes fine to the image and eeprom is up to date with his fix included. It’s on the hardware communication level from there that is giving me issues. Super strange. I mean the obvious answer is some of my hardware is junk. I’ll continue trying to see if I can find that issue. Based off the behaviour it just seems there is something about my hardware the kernel is not liking
Good advice. I do not have a cm4 but I likely will purchase one and re purpose my cm5 into something else worst case. Thankfully I know for certain my cm5 works wonderfully.