Z11ntal33r

I just want to say, c0rnelius, you are a lifesaver! I’ve spent several hours trying to figure out this issue, and it’s reassuring to see I’m not the only one dealing with it. This problem must be more common than it seems. I initially thought it was related to power management, as the external drives might be drawing too much power. In my case, I tried countless methods to disable USB power management and other tweaks, but it turns out the simple custom boot file was the ultimate solution! For reference, I’m running v24.11.1 on an Odroid N2 with Armbian Linux 6.6.63-current-meson64 Update This is a more widely issue it seems given there are other releated threads

Same issue here. Upgraded from Armbian 23.8.1 Bookworm with Linux 6.1.63-current-rockchip and now my Tinkerboard won't boot Here is the log from the upgrade process. Unfortunately, I am not home and hence cannot debug any further with an UART for the next weeks

Same issue here as well. I have ended up in this situation multiple times for the last year and I think it's time to move over to a more powerful board. Not sure yet which one I should pick up yet. One option might be Orange Pi 5. For everyone else with kernel issues, here is what I do when I use an. eMMC setup 1. Burn new raw image to SD (e.g. `Armbian_23.11.2_Odroidn2_jammy_current_6.1.68`) 2. Power it on and make sure it works and libs are fine. E.g `dm_mod` 3. Mounts eMMC partition 4. Move both boot folder and libs (E.g. folder `6.1.68-current-meson64` in /lib/modules to lib/modules) to eMMC 5. Run the following in both boot folders: `mkimage -A arm64 -O linux -T kernel -C none -a 0x1080000 -e 0x1080000 -n Linux -d vmlinuz-* uImage` 6. Reboot and verify that setup on eMMC works