progress:
I was able to get the commit for this RK3588 boot failure with "git bisect" maybe , many thanks.
https://github.com/u-boot/u-boot/…6149ce96a4d1037
This commit was merge commit, I will investigate more.
I was able to boot on my Orange Pi 5 Max with the u-boot v2025.10-rc1 that there were needed 8 commits revert.
But, I feel something strange. I'll take a short break. (I'll try chewitt u-boot 2025.10-rc4 version)
chewitt u-boot v2025.10-rc4 version quick boot test result.
[[RK356X]]
Working:
- NanoPi R5C
- NanoPi R5S
- ODROID-M1(with SPI recovery SW on)
- Quartz64-A
- radxa zero 3e
- radxa zero 3w (but no wifi - driver is not included)
- radxa ROCK 3A
- radxa ROCK 3B
NOT working:
- OrangePi 3B(HW v2.1: not boot, OrangePi splash is shown)
- Quartz64-B (show black screen, I dont know linux started or not)
- radxa ROCK 3C (show black screen, but linux might be started)
NOT test
- ODROID-M1S (I have no this device)
[[RK3576]]
NOT test
- ROC-RK3576-PC (I have no this device)
- radxa ROCK 4D (I have no this device)
[[RK3588]]
will report
Yasai-san Focus on reporting non-working devices (working ones are not interesting). Provide UART log output because it shows where the problem is. Your list is confusing because it shows Odroid-M1 in both working and not-tested. It shows Quartz64-A in both working and non-working.
NB: Rock3C, Rock4D, Rock5B are all working fine (tested by me).
Thank you comment. I fixed/edit mis-writing in my post.I will get UART log that is not working later. Attached boot UART log files.
My Rock3C is able to start kernel, but it stops before partition resizing.
When this time, HDMI cable Insert/remove start again.
This is not the case with other RK356X devices.
I'll try using a different HDMI cable just to be sure.(I will buy new HDMI cable later.)
My Rock3C boot failure was incompatible case trouble, not HDMI cable.
Currently my Rock3C without case is working correctly.
I'm sorry my bad environment.
OrangePi 3B is booting vendor u-boot (2017.09-orangepi) so you need to erase that from SPI or wherever it's been stored.
OrangePi 3B was booted after erase SPI thanks!
I used this method for erase SPI:
The initial dev samples of the Zero3W had a Broadcom WiFi5 chip. The release versions were 'upgraded' to WiFi6 with an AIC8800 chip that has no drivers in the upstream kernel, which is probably why the WiFi/BT nodes required to use a driver that doesn't exist have not been added to the device-tree file.
Radxa have an AIC8800 driver in their repo: https://github.com/radxa-pkg/aic8800 but LE has no interest to add downstream vendor drivers to codebase unless there is a visible/known plan to upstream them (so we can drop them once upstream).
I made the aic8800 driver and firmware package using Radxa driver repo for my Radxa ZERO 3W confirmation.
It needs 2 commits. ( 6cb5a2a7e83535b1265a23d79124356956df6f4e and d9c5aa21eaea8dbdc3a984ddc964c52e81c2b6e2 )
The firmware files were loaded and wifi was able to use.
Just report only, I don't make pull request for this.
Just report only, I don't make pull request for this.
The current AIC8800 driver will not be accepted into our codebase. The driver code is poor quality and needs a ground-up rewrite and Radxa has no plan for that. We would be stuck with a bad out-of-tree driver. Our instruction will be for users to vote with their wallets and not-purchase any boards using that chip; unless WiFi is not a requirement.
The current AIC8800 driver will not be accepted into our codebase. The driver code is poor quality and needs a ground-up rewrite and Radxa has no plan for that. We would be stuck with a bad out-of-tree driver. Our instruction will be for users to vote with their wallets and not-purchase any boards using that chip; unless WiFi is not a requirement.
There's always the option of a hub and a USB Wi-Fi stick. At least that's what I use for my tests, and it works very well. jejejeje, the board looks like a Frankenstein, but it doesn't matter.
Hello chewitt , would you be interested in a test on an older TV box with the RK3328 ? I’m new to LibreELEC, but I recently flashed LibreELEC-RK3328.aarch64-12.2.0-a1.img.gz onto my H96 MAX H2 (RK3328). I was surprised that it worked. I’ve been using it in last few weeks and would be happy to do more testing if it would be useful for you. And thanks a lot for LibreELEC ! .
I used to run XBMC on my Xbox 1 
and its really cool to run it again.
I gave it a try today and so far so good, it booted without problems LAN is working , wifi and BT is not detected but it was before also and i had same with armbian .. i never tried to look for some drivers as i am happy with the LAN
This is the image i tried from your link in the 1st post LibreELEC-RK3328.aarch64-12.90.1-a1.img.gz
Here is the dolphin log
https://paste.libreelec.tv/proud-dolphin.log
Hw dec is working as i played some 1080 video without any problem, 4K not really but i guess thats expected with this tv box.
Btw i made a image backup of my previous installation so i can go back to it if its something wrong here.
I will try to use this in the next days and see how it goes . If i could provide some more info for you pls let me know.
thanks a lot for your work !
