86Box (not to be confused with Box86) can handle x86 software emulation up to about 166mhz on a CM5. That’s more than enough to run Win98, ME, or 2000. It can emulate a little faster for some tasks.
I was using this image with a CM5 to run Windows 95 at 166Mhz to play SimCity 3000. Hit about 55C at stock clock, with the stock thermal pad.
I got my CM5108000 yesterday, I had issues where (and I didn’t figure it out for a bit) where it was stuck at the pi bootloader complaining about superblock and disk geometry. Several re-images later, I swapped sdcards, imaged it and was able to boot straightaway. First card was a Samsung Endurance which kept failing, second card was a Samsung Evo and has been working perfectly. So just putting that out if it helps anybody else.
Beautiful work @Rex
First and foremost, @Rex you are amazing!
I’ve tried Kali (6.12 kernel) image, and it was working perfectly (way more snappy than Manjaro 6.6).
But once I’ve done sudo apt upgrade, it found 300+ packages to update, rebooted and now uconsole doesn’t boot.
Maybe I should add some packages to not update list like it was done on Manjaro image?
I have this OS installed on my uConsole with CM4 8GB and it runs great, much better than the stock clockwork OS. Thanks for doing all this work, makes it a lot easier for newbies like me.
Has anyone tried overclocking with this image?
When I try and overclock using the instructions here it will no longer boot up. Interestingly, even if use another computer to remove the config.txt edits it still will not boot. The only way I have found to get it going again is to re-flash my SD card and start fresh.
Is it difficult to install the GNOME environment? I really like the look of it, but am wondering if it will be too slow on the CM4?
Just wanting to add my own observations:
I was previously using the 6.6.x image with my CM5, and it worked great (audio working too with the out-of-tree RP1 driver that was in use previously) The only issue was that relatively rarely, the display wouldn’t start, but everything else booted fine (So double tapping the power button was all that was needed and it’d almost always work the next time).
I apt-updated and it upgraded to the 6.12 kernel automatically, after which it would no longer boot at all, so I re-imaged the SD. Now i’m running into various issues mentioned in this thread, like the dim green LED on shutdown (needing batteries out), the panel seems to work far less often than it doesn’t (about 1 in 5 boots or fewer are successful, and the batteries need to be taken out every time).
The fact that it worked before (and that it always booted, just the display had issues) leads me to rule out any SD card issues, so I’m wondering what else has been changed with the uconsole-specific drivers that would lead to it regressing so much 
EDIT: The new 6.12.17 @paragonnov kernel works flawlessly - i had to install it with my CM4, since using the CM5 it would shutdown halfway through the installation (i think this was to do with the battery calibration though, i was doing it in tty0 and couldn’t see the charge level). Swapping back to the CM5 everything works perfectly now.
Can confirm that clicking power twice successfully shuts down the device so that is a good thing.
Do you know how does the new kernel fixes the screen issue?
Thank you!, panel start to work, but after start wayland have a dead mouse cursor with 90 rotated screen. Trying to dig kde logs. (cm5 with emmc previosly working stable)
UPD:
looks like the reason:
21:19:07 clockworkpi systemd[872]: Started plasma-kwin_wayland.service - KDE Window Manager.
21:19:07 clockworkpi systemd[872]: Starting plasma-kcminit.service - KDE Config Module Initialization...
21:19:07 clockworkpi systemd[872]: Starting plasma-ksplash.service - Splash screen shown during boot...
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: No backend specified, automatically choosing drm
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: did not find extension DRI_Mesa version 1
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: failed to bind extensions
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: did not find extension DRI_Mesa version 1
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: failed to bind extensions
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: did not find extension DRI_Mesa version 1
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: failed to bind extensions
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: did not find extension DRI_Mesa version 1
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: failed to bind extensions
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: MESA-LOADER: failed to open drm-rp1-dsi: /usr/lib/dri/drm-rp1-dsi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/aarch64-linux-gnu/dri:\$${ORIG>
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: did not find extension DRI_Mesa version 1
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: failed to bind extensions
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: did not find extension DRI_Mesa version 1
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: failed to bind extensions
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: did not find extension DRI_Mesa version 1
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: failed to bind extensions
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: kf.globalaccel.kglobalacceld: No desktop file found for service "org.kde.dolphin.desktop"
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: kwin_scene_opengl: Creating the OpenGL rendering failed: "Could not create gbm device"
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: kwin_scene_opengl: Creating the OpenGL rendering failed: "Could not initialize egl"
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: kwin_xkbcommon: XKB: inet:334:58: unrecognized keysym "XF86EmojiPicker"
21:19:07 clockworkpi kwin_wayland_wrapper[2786]: kwin_wayland_drm: Failed to create gamma blob! Invalid argument
21:19:07 clockworkpi kwin_wayland_wrapper[2806]: libEGL fatal: did not find extension DRI_Mesa version 1
21:19:47 clockworkpi systemd[872]: plasma-ksplash.service: start operation timed out. Terminating.
21:19:47 clockworkpi systemd[872]: plasma-ksplash.service: Main process exited, code=killed, status=15/TERM
21:19:47 clockworkpi systemd[872]: plasma-ksplash.service: Failed with result 'timeout'.
21:19:47 clockworkpi systemd[872]: Failed to start plasma-ksplash.service - Splash screen shown during boot.
21:20:07 clockworkpi org.kde.KSplash[2779]: org.kde.knotifications: WaitForName: Service was not registered within timeout
21:20:07 clockworkpi dbus-daemon[894]: [session uid=1000 pid=894] Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1
21:20:37 clockworkpi systemd[872]: plasma-kcminit.service: start operation timed out. Terminating.
UPD:
another update (sudo apt update && sudo apt upgrade) fixes the issue (mesa-libgallium installed, libegl-mesa0 libgbm1 libglapi-mesa libglx-mesa0 updated)
I have updated my CM4 with Debian Bookworm to the latest kernel 6.12 but after reboot the screen stayed black. I also tried flashing a new SD but the problem remained. I guess the new panel driver is not working as intended with the CM4.
btw HDMI still works.
I just tried a fresh flash of the new bookworm image on the CM4 and everything seems to be working right. how’d did you flash the sd and did you apply any custom settings?
I’ve updated the kernel from the update notification. Everything seems to be fine now with the screen.
Does anyone know how I can have uConsole remember keyboard back-light level on boot?
The micro-controller handles that, I’m not sure you can set it from the os.
Any plans on updating Kali to 6.12.17 anytime soon?
planned on it tonight.
I am Running 17 on a CM4 fresh install also it seems much more snappier. Seems to be pulling a little stronger wifi signal.
I used Balena Etcher and Raspberry Imager as well. I tried both the Bookworm and the Bookworm Lite version. no config file change. The screen turned on 2 times out of ~15 reboots. also tried to remove the batteries. Now I rolled back to previous version, it works reliably with it.
are you applying any custom setting when you flash the sd?
I ended up downloading the image again, now from Google Drive instead of MEGA and now it works. Don’t exactly know what went wrong, maybe my download got corrupted.
From my observation when the screen fails to boot give it a good 30 seconds before trying to restart. Press the power button 2 times and it will shutdown. Then press the power button to turn it back on. This method has worked for me 100%. If you get the dim green light you pretty much have to open it up and take out the battery. Also as previously mentioned always shutdown by pressing the power button twice.
Experiencing same kind of issue with CM4 after update to the 6.12.17-v8+. The screen flashes every time, then it either immediately goes blank and unresponsive or there is a brief kernel log output and then it goes blank. Either way it only fully boots around 1 out of 6 attempts