Ho! I have regularly had problems with Kingstons whether with pi3, 4 or 5. I use Samsung or Sandisk, which still work. Have you applied the @Paragonnov CM5 eeprom settings?
You can use the « endurance » versions of these SD for a better reliability.
Thanks! I’m using Sandisk 128Gb now, but I’ve flawlessly flashed the regular ClockworkOS image both on Sandisk and Kingston 256 Endurance. The problem seems a corrupted download, but having the same error both from MEGA and GDrive folders it’s a bit odd. Am I missing some steps?
Hum… have you tried with rpi-imager? I find it effective and it checks the burn. You just have to uncheck “apply presets” for everything to work.
I’m giving a shot. Keep you posted, thank you!
1 Like
I have had no problems with RaspberryPi Imager. Don’t customize install and it will work.
1 Like
I was getting the same error with etcher but pi imager works every time with any sd card.
Etcher is not the best, plus Etcher phones home with info with info about your SD/Flash drive, the image you’re flashing. Not a big deal to most but something to be aware of.
1 Like
CM5: Updating my previous install resulted in xfce4/mesa getting borked. System froze, I did a hard reboot (pressing down the power button for 10 seconds) and ended up with the dim green light of death.
Made a fresh image of the newest file file the Google Drive. Since this is just a test, I threw a whole bunch of stress stuff on it. Was installing Windows 2000 in 86Box, and the graphics started messing up (May be related, but could also be the system I am emulating). The system froze. I did a hard reboot, and got the dim green light of death again.
To remind, the Dim Green Light of Death happens when you do a hard reboot by holding down the power button. The green light becomes dim instead of turning off. Then no matter what you do, you can not boot the system back up until the batteries are unplugged. I also noticed some whines/electrical noise and the screen being slightly lit during the dim light phase.
Anyway, I can duplicate it every time by just hard shutting down.
Beyond that, boots every time. System may or may not be unstable compared to CM4 install (not sure yet), when doing apt-get update / upgrade on the new install, initframs-tools will not update.
What CM are you running?
Sorry, I was editing my post (added some more stuff there). I am talking about the CM5 image. Using CM5 8GB Lite, with Wifi
if you’re on a fresh image on the CM5 there shouldn’t be no updates that would need to update the initramfs. if you do sudo apt reinstall clockworkpi-kernel it will update the initramfs for both kernels or you can update-initramfs -c -k all to update them manually. hard reboots on the CM5 still require removal of the batteries. if you have a lite i’ve had a bit of luck removing the sd then holding the power button, but it’s about 50/50 if it works for me.
3 Likes
rpi-imager did the trick! It works like… clockwork! 
thx!
2 Likes
I tried Kali Linux. It doesn’t ask me to create a user/pass.
What are the defaults credentials?
kali/kali They’re listed on the forum post of the Kali image also. That’s how the image comes setup from Kali, there’s no user creation on first boot. You should definitely change them.
1 Like
For this, rpi imager has been more reliable.
Etcher is now sending a lot of data out to third parties, dead to me now! TailsOS has been looking into this a lot, and etcher user agreement lists way too much data that they might send to third parties. Rufus, usb imager, rpi imager from now on.
3 Likes
Rex, thank you so much for doing all this hard work in making these images accessible! I recently upgraded my uconsole to the cm5 lite with 8 GB ram and it would have been a nightmare to get running without your images.
Its working perfectly for me now with the latest image, I was going through the rebooting to get the display working with the last version, but now it’s as stable as the CM4 with the original image.
I’m considering mounting an m.2 heatsink to the back to improve passive cooling a bit, but only get to 70 C at the worst, so still functional as it is.
Thanks again, keep up the great work!
5 Likes
Is anyone overclocking their CM5 without cooling mods and if so what settings have you had luck with.
I had mine OC’d to 2800cpu and 1000gpu before i put my m.2 heatsink on. it’s not bad if you’re just using the OC for a little extra when opening apps and stuff but if you are using it for compiling or putting it under some load for more then 10-15 minutes you’ll need to add something to help the heat.
1 Like
These correct? Tried a while back and saw no change, battery just stays at 100%.
Trying again now.
Should the value of calibrate be 48 (voltage?) after running this?
Thanks
Not voltage but 48 does mean it’s calibrating.