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

It seems that I am not able to boot directly from eMMC and use the second method Boot from eMMC from armbian-install. However, I am able to set mmcblk1 (eMMC) as SD and choose method 1 Boot from SD where I end up by booting from SD and using my eMMC as root. Prior I could boot without the SD carad, which is what I want, but at least this way I am able to use my eMMC. mmcblk0 is my SD card mmcblk1 is my eMMC ___ _ _ _ _ _ ____ / _ \ __| |_ __ ___ (_) __| | | \ | |___ \ | | | |/ _` | '__/ _ \| |/ _` | | \| | __) | | |_| | (_| | | | (_) | | (_| | | |\ |/ __/ \___/ \__,_|_| \___/|_|\__,_| |_| \_|_____| Welcome to Armbian 23.8.1 Jammy with Linux 6.1.50-current-meson64 No end-user support: community creations System load: 5% Up time: 1 min Memory usage: 5% of 3.69G IP: 192.168.45.19 CPU temp: 42°C Usage of /: 12% of 15G RX today: 154.5 MiB user@odroidn2:~$ sudo lsblk [sudo] password for gzjlspxwkh: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 14.8G 0 disk └─mmcblk0p1 179:1 0 14.7G 0 part /boot /media/mmcboot mmcblk1 179:32 0 14.6G 0 disk └─mmcblk1p1 179:33 0 14.4G 0 part /var/log.hdd / mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk zram0 252:0 0 1.8G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk

I am actually not able to boot from eMMC at all after the upgrade earlier, even after a clean install to eMMC with either Armbian_23.8.1_Odroidn2_jammy_current_6.1.50 or Armbian_23.5.1_Odroidn2_jammy_current_6.1.30. Not sure if I should delete /dev/mmcblk1boot0/1 as well before each clean install or what to do to be able to boot from eMMC again

Same issue here with Odroid N2 as the kernel did not update successfully it seems, but armbian-config did (from 6.1.11-meson64 and armbian 23.02). I ended up with re-installing from a clean image. However, after upgrading packages, the welcoming message now says: "No end-user support: community creations". Not sure why I would receive it as I only have ran apt update and upgrade after booting up before doing a restart. Image: Armbian_23.8.1_Odroidn2_jammy_current_6.1.50

@hexdump it seems that you were absolutely right regarding the issue here! After lowering the max CPU speed from 1900 to 1800, I've done more than 100 benchmarks without facing Illegal instruction Thank you very, very much!

Thanks for reaching out I've default settings and I did a clean install yesterday. The few steps I did was to run cryptstetup benchmark which was fine, ran a script to install and setup packages and so on, tried to mount the drive, but Illegal instruction showed. After that, all cryptsetup benchmarks failed. I can try a new clean build later today, lower the cpu freq and see if that's better. I am also thinking about switching from Jammy to Bullseye in order to apt-pin newer packages of cryptsetup to see if that solves the issue. I that doesn't help, I will think about buying a new SBC, unless I switch to something else than Armbian, which I would like to avoid

Hi, I have two meson64 SBCs where one is Khadas VIM 3 and the other is Odroid N2. They have been running almost the same setup and there has been minor differences with time. For the past months, I have had issues with the error Illegal instruction for my Odroid N2 server. I did a clean install earlier today (Armbian_23.02.2_Odroidn2_jammy_current_6.1.11) without success. For instance, I often face the error when running cryptsetup benchmark. Most of the time I have to reboot multiple times, reinstall cryptsetup packages, try the armhf packages and more. I have never had the same issue with Khadas VIM 3. The issue seems to be related to argon2i and the question is what and where should I look further regarding how to solve this. I've tried switching supported kernel versions, 6.1.*, 5.19.*, 5.10.*, without success. Trying legacy kernel 4.9.* had some issues resulting in the board not booting. Output when everything is fine | => sudo cryptsetup benchmark Output when facing the issue. It's always after trying to open with cryptsetup prior and I think it's in general | => sudo cryptsetup benchmark