I’d already read that this had happened to others as well. When I updated my uConsole using apt, the akrex kernel was updated and the clockwork kernel was uninstalled. Nothing works anymore 
What’s causing the problem and what’s the simplest solution? Thanks for any advice!
you’ve installed default kernel without uconsole drivers
connect by ssh / attach display and keyboard and run something like it:
(probably you don’t need to add the repository)
# sudo add-apt-repository -y "deb [arch=arm64] https://raw.githubusercontent.com/ak-rex/akrex-arm-repo/main/debian stable main
try to reinstall, or install
# sudo apt reinstall akrex-kernel
# sudo apt install clockworkpi-cm-firmware akrex-kernel
1 Like
I’ve changed the name to akrex-kernel since it’s now on several devices.
It should have just changed over unless maybe you answered no when it asked you if you’d like to switch the repo but that shouldn’t of mattered you would just not get updates from me. Not break the kernel.
3 Likes
I wasn’t asked anything. What a pity. I’m unfortunately very busy at the moment, but I’ll try to get it up and running again over the next few days. I will report here…
Thanks for your suggestions!
The uConsole was completely dead. There was no signal coming from HDMI.
As my uConsoles have been running on NVMe since day one, today I booted from an SD card for the first time.
Now I can chroot into the NVMe OS and start the repair. I’ll do that as soon as I have some free time.
2 Likes
I just experimentally tried apt full-upgrade and it had the clockworkpi kernel package marked for removal.
I didn’t go through with it after seeing your post but I’m left a little confused. I thought that the akrex kernel worked independently of the clockworkpi one.
ak-rex replaces clockworkpi.
Yeah, kernel 7 did a number on me. Meshtasticd won’t start and the uConsole isn’t responding to it’s name from another machine. the avahi-daemon is running, but it’s apparently not advertising the name. And the foot terminal emulator’s font size went huge. So, of the top three things I use on the device, all are broken in one way or another, LOL.
Ak-rex kernel is the new name, clockworkpi kernel is the old name
Great, that’s broadly how I understood it but it’s such an ominous message to see after reading a post like this.
Well I went through with that apt full-upgrade and updating akrex-kernel and removing the clockworpi-kernel.
Update seemed normal and then I rebooted to a blank screen and no keyboard. I guess I’ll dig out my recovery SD card tomorrow and try and get it working again.
The surprising thing is that I’ve always used the same sequence:
apt update
apt upgrade
apt dist-upgrade
apt autoremove
apt autoclean
apt clean
No problems until the day before yesterday.
What do yes your boot partition look like. Can you give me a file list?
I will do so on Wednesday, as I’m on a trip right now.
Two out of three of my issues with the new kernel have been resolved. mDNS just started working sometime overnight. Fixing the font size issue with foot just required editing its INI file.
Meshtasticd still won’t run – an issue raised by another user in the kernel 7.1.y thread and seconded by me 
. @Rex, I can give you a file listing if you need it, but I’m guessing that since my system is booting fine, you don’t. If I’m wrong, let me know! And as always, thanks for all you do for this community.
I can confirm Meshtasticd no longer working. I have tried some preliminary things that have worked in the past to get it working with no luck yet. All other AIO features are working fine.
here’s what I pulled off my nvme drive this morning. I haven’t really dug in that much yet. I’m def a novice so I’ve been reading about recovery options before I make new problems for myself.
pideck@clockworkpi:~ $ ls /media/pideck/bootfs
bcm2710-rpi-2-b.dtb bcm2712-rpi-cm5l-cm4io.dtb fixup_db.dat
bcm2710-rpi-3-b.dtb bcm2712-rpi-cm5l-cm5io.dtb fixup_x.dat
bcm2710-rpi-3-b-plus.dtb bcm2837-rpi-2-b.dtb issue.txt
bcm2710-rpi-cm0.dtb bcm2837-rpi-3-a-plus.dtb kernel_2712.img
bcm2710-rpi-cm3.dtb bcm2837-rpi-3-b.dtb kernel8.img
bcm2710-rpi-zero-2.dtb bcm2837-rpi-3-b-plus.dtb LICENCE.broadcom
bcm2710-rpi-zero-2-w.dtb bcm2837-rpi-cm3-io3.dtb meta-data
bcm2711-rpi-400.dtb bcm2837-rpi-zero-2-w.dtb network-config
bcm2711-rpi-4-b.dtb bootcode.bin overlays
bcm2711-rpi-cm4.dtb cmdline.txt start4cd.elf
bcm2711-rpi-cm4-io.dtb config.txt start4db.elf
bcm2711-rpi-cm4s.dtb config.txtn start4.elf
bcm2712d0-rpi-5-b.dtb fixup4cd.dat start4x.elf
bcm2712-d-rpi-5-b.dtb fixup4.dat start_cd.elf
bcm2712-rpi-500.dtb fixup4db.dat start_db.elf
bcm2712-rpi-5-b.dtb fixup4x.dat start.elf
bcm2712-rpi-cm5-cm4io.dtb fixup_cd.dat start_x.elf
bcm2712-rpi-cm5-cm5io.dtb fixup.dat user-data
Thanks so much for all that you do Rex. TBH having things break occasionally helps me learn the most.
Happened to me on 2 of my uConsoles, both running the Rex Trixie image on CM5 (16GB, Lite, WiFi). Been working great for months, then an apt upgrade removed the clockwork pi kernels and added the arex kernel. Then the uConsoles would not boot any more. Black screen, DOA for all practical purposes. Had to reimage both to get them back, lost all my data.
Why didn’t you back up the data off the SD card after it wouldn’t boot?
I can still access all my files and am backing them up before mucking around.