Orange pi 5B - install to emmc doesnt work anymore. Armbian-install behaves oddly

[chall88]

I have attempted this with the vendor kernels and the mainline kernels, and they both do the same thing. The vendor kernel cannot see the EMMC at all after running updates on it. So that version would kill itself when updated even if it did install and boot off the emmc. The wifi also doesnt work on the mainline, so the options are mainline with no wifi or vendor with no emmc.


Install to SD card --> to through setup wizard --> change firmware to 5b instead of 5.-->  reboot --> armbian-install --> boot from emmc, system on emmc ---> spends a long time on counting files ---> file transfer screen flashes by in 1 second. --> shutdown ---> boot from emmc. ---> completely dead, the lights on the board never even flash green like they do with an SD inserted

This has worked in the past, many many versions ago, but it did not do this when it worked "spends a long time on counting files ---> file transfer screen flashes by in 1 second"

Files appear to be there though when mounting the filesystem. Correct uuids in the armbianEnv and fstab

I also attempted to just burn it from the sd to the emmc with dd, but that also didnt work

How can I load a current version of amrbian onto my emmc for the orange pi 5b?

[allatutti]

"spends a long time on counting files ---> file transfer screen flashes by in 1 second"
I will say is normal behaviour, I have same symptoms when moving sd 2 usb, but files are moved to usb.
In your case what will happen if your do change dtb from 5 to 5b and do reboot still with SD card, will it boot?

[chall88]

I always had the dtb set to 5b


I did manage to get it onto the emmc manually by using 2 SD cards

1. manually creating an ext4 on the emmc
2. I installed to SD
3. Installed again on a second SD

4. Booted off second SD
3. Attached the usb to SD reader
3. made a /mnt/old /mnt/new and rsync'ed the entire filesystem over to the emmc

4. adjusted the /boot/armbianEnv.txt on the booting SD card and the fstab on the emmc to point to the UUID of the emmc storage.

I cant boot off just the emmc, but this sort of uses the sd card as a springboard to load the stuff in emmc.

Anyways, armbian-install doesnt work on the 5b. The part that is failing seems to be the bootloading part. Whatever happens before /boot/armbianENV.txt is loaded, that part's broke for emmc 

Edited November 5 by chall88
me and the guy above posted at the same time

[chall88]

Downgrading the kernel from current or vender to the legacy-5.10.160 makes everything work properly.

By everything working i mean the wifi and the emmc, and the install to emmc.

I also discovered in my poking around that the current kernel regularly locks up the orange pi5b. It wont even respond to network traffic when it locks up.

Edited November 6 by chall88
more detail.

[Gerbil42]

I'm stuck in this same situation with the 5B.  Which image did you use with the legacy 5.10 kernel?

[chall88]

I loaded the vendor kernel(6.1) one, then I used armbian config to roll back to the 5.10 legacy kernel and then proceeded from there

IDK what happened but stuff really seemed to go off the rails with armbian on this specific board variant on the newer kernels

[chall88]

I did hook up a serial to it after installing to emmc. It's not lying in theis message. You have to flash it with the RKDEVTOOL in order to ahve any kind of functionality back from the emmc