This boot fail is known issue
Please wait to fix, or disable CONFIG_KASAN on your kernel config and build image.
Posts by Yasai-san
-
-
Quote
Out of curiosity Yasai-san are you also having issues?
I don't use the Radxa Zero 3W now.
So I have no informarion for this issue sorry. -
I've confirmed the issue with the odroid-xu4 boot failure.
It occurs starting with the following image:
- LibreELEC-Exynos.arm-13.0-nightly-20250730-ecfa284-odroid-xu4.img.gzAnd it has been fixed in the following image:
- LibreELEC-Exynos.arm-13.0-nightly-20251223-941298b-odroid-xu4.img.gzIf my testing method is correct, both(boot fail and performance) problems appeared since v6.16.
- 81e3bc35c1e59d75693062b45b05adae32210fe5 is booted
- 821d827dba93b3ffe14ac40dfb7dbc33935b6eca is not booted- 821d827dba93b3ffe14ac40dfb7dbc33935b6eca + 2 fix commits
(098bfdb6b51d06adf6285b63e21b71078ae1d497 + 0b4b7ecca0daabe90b39f7171c78c5a4840a41e1) is booted but wrong performanceThis topic is talked for the boot fail issue.
I think performance issue will talk on new topic better.
(Similar performance issue is also happened on Lakka.) -
Yasai-san I've managed to build an image of LE13 for RK356X for my Radxa Zero 3 thanks to your work. Many thanks!
I rebased on master, and tried to bump the aic8800 driver from the radxa-pkg/aic8800 repo from 4.0~ to 5.0~, but it failed to build. ie:
CodePKG_VERSION="5.0+git20260123.5f7be68d-4" PKG_SHA256="58c4c1ee085fac7971e9972dba99c5e3207e1ea0991c3f957bd9200f6ec8fbe7"Two questions:
- Did you pick 4.0+git20250410.b99ca8b6-5 specifically, or was it just the latest when worked on this?
- How did you figure out the right targets in projects/Rockchip/packages/aic8800/package.mk?
- When trying to build 5.0+git20260123.5f7be68d-4 i had to comment out the pre_make_target for linux 6.12 as that build patch is missing and it then failed anyway with another error.
Hello axel
> Did you pick 4.0+git20250410.b99ca8b6-5 specifically, or was it just the latest when worked on this?
I used the latest version at that time.
This is reason.
> When trying to build 5.0+git20260123.5f7be68d-4 i had to comment out the pre_make_target for linux 6.12 as that build patch is missing and it then failed anyway with another error.
I also confirmed this build failure.
a) Radxa aic8800 repo removed linux 6.12 patch file by version up.
fix: update patchset · radxa-pkg/aic8800@89f865b
-> it needs to remove this patch apply from package.mk
b) (after a) compile error is shown about vfree
-> Radxa aic8800 repo has patch file for this compile error.
aic8800/debian/patches/fix-vmalloc-not-include.patch at main · radxa-pkg/aic8800
it needs to add this patch apply to package.mkPlease check my following commit
(Sorry, this is compilation check only)
Note.
as you know, I do not actively support this.
-
It looks like CONFIG_KASAN=y snuck into a kernel defconfig and this increases the KERNEL size to a point where standard vendor u-boot configurations (as used with Android STBs) will fail to load the kernel and fault. This is nothing to do with RAM size.
I have a large list of changes to work on and current progress is rather slow, so I will update images at some point soon, but to avoid breaking promises I'm not going to give a timeline on when.
Thank you very much for this information.
My bananapi-m5 was able to boot with "CONFIG_KASAN" kernelconfig disabled. (using attached patch)
-
I can't boot nightly LE13 build image (since 20260211-4871898) on my bananapi-m5.
I want to report about this.
May I create new thread? or keep to report here? -
Yasai-san Just create a pull-request with "This PR is being submitted so information on how to add the AIC8800 driver package into a self-built image is more easily found. I support the project's wish to not add downstream drivers that have no visibility of being upstreamed and do not expect this to be merged" .. so we look less authoritarian when we close it without merging
I made PR as https://github.com/LibreELEC/LibreELEC.tv/pull/10960
Please close this PR. -
From a "how do i get this device to do what i want" perspective, it sounds like i need to learn to build LE and add the driver in my image, to get it to get usable wifi? or add an external wifi adaptor, which is a lot simpler, a bit sad considering it has onboard wifi, and not as fun (probably type-2 fun though, lets' be honest). Or run Armbian / Radxa Debian and make it boot into Kodi.
Regarding this, my post will help with your image building LE I think.
But I don't create Pull requests for AIC8800 driver because I'm agree with chewitt and LibreELEC perspective.
-
RadxaNaoki
I found your latest rock5c update in mainline linux contribution.
Many thanks!
About HDMI audio, rock5a is also needed patch I think.
Could you please make it? -
chewitt RadxaNaoki
I was able to get HDMI audio on my rock5c with above RadxaNaoki's patch.
Many thanks!
But still logged "fde80000.hdmi: i2c read timed out" in journalctl log.
> LibreELEC kernel: dwhdmiqp-rockchip fde80000.hdmi: i2c read timed out
rock5c's kodi also doesn't show rk3588-es8316 audio device after apply patch.
but "aplay -L" shows "rk3588es8316".
> LibreELEC:~ # aplay -L
> null
> Discard all samples (playback) or generate zero samples (capture)
> default:CARD=hdmi0
> hdmi0, fddf0000.i2s-i2s-hifi i2s-hifi-0
> Default Audio Device
> sysdefault:CARD=hdmi0
> hdmi0, fddf0000.i2s-i2s-hifi i2s-hifi-0
> Default Audio Device
> default:CARD=rk3588es8316
> rk3588-es8316, fe470000.i2s-ES8316 HiFi ES8316 HiFi-0
> Default Audio Device
> sysdefault:CARD=rk3588es8316
> rk3588-es8316, fe470000.i2s-ES8316 HiFi ES8316 HiFi-0
> Default Audio Device
> LibreELEC:~ #
Please let me know if "pastekodi" is needed. -
chewitt
I tested your 20251107 image on my rock5a.
HDMI audio device was not shown.
Log hrer: https://paste.libreelec.tv/advanced-snake.log
BTW, I got HDMI audio device on my rock5a with attached DT patch.
rockchip-9999-add_enable_rock5a_hdmiaudio.patch.txt please remove ".txt" from file name
But this patch has a problem that lost rk3588-es8316 device \when patch is enabled.
And I couldn't confirm it on my rock 5c because my rock 5c has same problem with gnarlsnishi -
hi, I tried your image for rock5b, it didn't load, there's only a black background on the screen.
My ROCK 5B was able to start LibreELEC with 20251021-3f3aa0f nightly image via mSD.
LibreELEC-RK3588.aarch64-13.0-nightly-20251021-3f3aa0f-rock-5b.imgMy ROCK 5B has no eMMC and no nvme SSD.
Dose your ROCK 5B have eMMC or nvme SSD? -
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.
GitHub - ShigeakiAsai/LibreELEC.tv at Add-Aicsemi-aic8800-WiFi-driver-and-firmwareJust enough OS for KODI. Contribute to ShigeakiAsai/LibreELEC.tv development by creating an account on GitHub.github.comIt 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. -
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:LtPurpie's comment on "Orange pi 3B won't boot"Explore this conversation and more from the OrangePI communitywww.reddit.com -
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. -
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.) -
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 -
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)
