My charge LED has suddenly started working when the uConsole is powered off and I plug it in??
Rex, did you fix something?
Edit:
Never mind, think I figured it out.
Noticed my battery was pretty much flat when it should have been nearly full from yesterday.
I installed RetroPie image on a separate SD yesterday and that was the last thing I was using.
I must have shut down by pressing the power button which it looks like that doesn’t fully shut the uConsole down, even though it appears that it has. Must be like a standby mode.
If I go into the RetroPie menu and shutdown system from there it shuts down fully and no charge LED when charging.
Hello, Rex. I’m trying to use the CM5 version of bookworm 6.12.y. I put CM5 on the extension for my first try. After normal startup, the mouse and keyboard cannot be used. Does this have anything to do with my baseplate? Or do you have to use the uconsole motherboard to work with an external mouse and keyboard?
I have most of the USBs and the onboard ethernet disabled in my kernel. They are unneeded in the uConsole. While the image will start in most carrier boards, most stuff won’t work because it’s optimized for the uConsole.
Finally recieved my CM5, only took a month because of “Lost Shipping”. But, anyway… Installed Rex’s Bookworm and Parrot on two different sd cards. I ran into the random display not showing anything but lit, and the lightly lit green power led too. I see about shutting down via a “blind shutdown”. and some others have removed the batteries (ran into that). Has anyone figured out the problem with this?
Since you got the lite CM5, did you do the eeprom edit in the OP? Not all SD cards work right away with the CM5. You can try booting it with a HDMI connected to see if you get a SD card error. if so you’ll need to do the edit to get it to work.
You’ll need a to test a few to find one that works. If you don’t have one that you can boot with I have test this one in the 128gb version and it works without the edit. once you get booted make the edit then all SDs will work.
Sorry, I did not explain this well. It boots and all, actually using the teamgroup sd, for both OS. I was just looking to see if there was any update on the random blank screen issue, and the light green led that I see others have had an issue in the past with. I am seeing the same problems.
Uconsole and yes, the latest as of last night. CM5, Lite, 8gb. Bookworm I worked with until I updated the keyboard with QMK and upgraded the firmware. Then moved to parrot OS, latest, onto an SD card. After about 30 min, battery charging. the screen went blank, keyboard was still lit. Shut it down, (button held worked). Then, when i started it the keyboard and screen where lit but no information. then I tried to hold the power button and it went dimmer but never actually shut off. That is when I went on ahead and pulled the batteries. I have read others have had this issue.
With parrot screen blanking is enabled by default, so the screen going blank could be normal. Did the screen come back at all after rebooting? Did you do any kind of forced update?
It was like the display wen’t out, and it wasnt coming back. After I forced the shutdown, powered back on, the screen was lit but nothing was on display when I rebooted. If it’s a parrot issue, I have no problem loading what I use into the rasp-pi image. It just saves a lot of work If the parrot os worked haha, has most of the tools I use. I did check for updates, it was all up to date. Kinda odd, I was watching the CPU temp, thinking maybe that was it… but it never wen’t over 60c.
I’d be tempted to take it all apart, disconnect the screen and battery module then refit everything, just to make sure all hardware connections are good.
normal updates should work, it’ll even get my custom kernel updates. if you do a dist upgrade it’ll replace the custom kernel with the stock one but then the backlight won’t even work.
I’d recheck the connections like @Talos said, sometimes when you take the back off the thermal pad will pull the CM out of the socket a bit. If that doesn’t work flash the image again to another sd card and see if it works.
even if you’re using the teampro+ card and it works, i’d do the eeprom edit to make sure everything is more reliable during boot.
Amazing work, Rex! I got the latest image working beautifully on my CM5 Lite last night (wow the 8GB CM5 is a HUGE speed improvement over the 4GB CM4), until I sleepily installed Wireguard along with a mainline kernel via apt, and obviously broke it
I’m reflashing now (for a third time), and sorry for the noob question, but does anyone know if there’s a way to prevent apt thinking it needs mainline kernel as a dependency in cases like this? I tried messing around with equivs but apt still insisted it needed a different kernel…
I didn’t have this problem with Wireguard on one of Rex’s earlier Bookworm builds, and can’t figure out what’s different. No Wireguard is a bit of an issue for my use-case…
Thank you I appreciate it! I’ll look tonight and see what’s up with wireguard, I might have to add something to the provides info of the kernel package. I’ll let you know if I find anything.
