-
Notifications
You must be signed in to change notification settings - Fork 938
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install latest hassos on ODROID-C2 #1202
Comments
Hm, I haven't seen this issue so far, and C2 seems to work on my end. So this is probably device specific. There was an issue with Ethernet and PHY timing (see #1042), but the fix is in 4.20 as well as in 5.10/5.11, so it seems that this patch does not cause or fix this problem. Can you try with 5.5? It does not contain those fixes but is already on Linux 5.9. I am intending to update to Linux 5.10 on the dev branch, that might be worth a try as well. I'll post once a development build is available. |
Tried to run installation with 5.5 but same issue occurred. |
I've tried upgrading that working 4.20 to latest, and it failed to boot afterwards (expected), with same error. |
I have the same problem since upgrading from 4.2 to anything higher on my c2 |
I confirm. When upgrading to a version higher than 4.20:
|
Same error for me with a fresh install on version 5.12. |
Hi, I tried 5.11 few days ago with same issue on my Odroid C2 and used 4.20 instead after reading @oOoHoCo comment. When I saw 5.12 coming, I decided to test it by using firmware OTA update from USB. It performs update and restart correctly. I could use HA locally few times on last version (no more update available notification in supervisor). I stopped my Odroid and restart it next day with issue back... I assumed that hassos-boot partition files could be in cause and switch them by 4.20 versions (copy/past on the only partition I could access on Windows) with no success.
Here is the capture, I hope it can help ! |
+1 This happened after my Odroid C2 (HW rev. 0.2 20160226) lost power in the night. I've unsuccessfully tried every release from 5.4 to 5.12 with a previously working SDCard (SanDisk 32GB) and eMMC (16 GB). With 4.20, the issue does not exist. Note: Because I was dumb and didn't configure backups, I needed to recover my configuration by mounting the SDCard in my PC. |
Same issue on a fresh install, reflashed the 4.20 image on the eMMC, and no problem there. Might be kernel-related but the regression is definitely in 5.x. |
It's definitely kernel related, as I've found some mentions of same issue on odroid c2 boards with newer kernels, unrelated to hassos. 4.20 works without any issues so far, so it's recommended version I suppose until there's some development on this front. Various users happens to have different network issues on r-pi boards on versions 5.x (happened to me as well), so I'm running sticking to 4.20 on other boards as well. |
Can somebody try a 6.0 development release from here: This comes with the Linux kernel 5.10 for all boards. |
Just tested it via SD-Card. Still no activity LED on ethernet port and the same messages being spammed:
I found this thread on the C2's ARMBian-Forum, where the same issue is discussed: There seems to be an issue with uboot. One person "fixed" it by copying 4.19's uboot to his device: Another person compiled a specific version, which he claims to be functional: I'm no developer, but these might be worth to look into. I have spare SD-Cards laying around, so I will gladly test any new build. :) |
Thanks for the pointers those are good finds. It is somewhat unclear if Armbian added new patches or just that new U-Boot fixes it. I actually updated to U-Boot 2021.04-rc4 just yesterday, so we can just give that a shot and see if it fixes the problem. I'll create a build sometime today and will post the link once ready. |
New builds with U-Boot 2021.04-rc4 are ready: |
Sadly, no luck with that build, either. The systems still spams the usual messages. |
HAOS 4.20 came with U-Boot 2020.01. With HAOS 5.3 we switched to 2020.10. HAOS 4.20 came with Linux 5.7.19. With HAOS 5.4 we switched to 5.9.1. So now the interesting question is: Is this U-Boot or a Linux kernel problem? If 5.3 works, then it must be a Linux problem, however, if 5.3 already shows the problem, it is most likely a U-Boot regression which came in sometime between 2020.01 and 2020.10 release. @Blogshot can you test 5.3 and see if that works? |
I just confirmed the issue on 5.3 (https://github.com/home-assistant/operating-system/releases/download/5.3/hassos_odroid-c2-5.3.img.gz). This indicates that the issue indeed lies within uboot. |
I created two custom OS 5.12 builds, one with U-Boot 2020.01 and one with 2020.04, can you give those a try? https://os-builds.home-assistant.io/hassos_odroid-c2-5.12.dev20210319-uboot-2020.01.img.xz |
Good news: The image with uboot 2020.04 worked. I'm currently sitting in front of "Preparing Home Assistant". This narrows down the issue to uboot newer than 2020.04. Therefore I haven't tested your 2020.01 image. |
I also got to the "Preparing Home Assistant" using the 2020.04 as @Blogshot reported. But the log is full of:
|
@Blogshot I made a version with U-Boot 2020.07, can you test if that version still works? |
Actually I have a theory what could cause the problem. Commit "arm64: dts: meson: sync dt and bindings from v5.6-rc2" changes reset timings for the Ethernet PHY. Can you try this build: |
The PHY-reset build is booting and showing the "Preparing Home Assistant". However, because HomeAssistant is also my DNS Server, it can't finish setup because it can't download the docker images. Since the PHY-fix has the more recent uboot, I haven't tested the 2020.07 build. |
@agners can you post your patch somewhere so I can build/test it using meta-meson? |
I would not expect 2020.07 to work, since that was the hard cut-off for the DM changes (that are still missing some in-queue patches to make things work again). For now, it's either 2020.04 or the above patch (I'd probably stick with 2020.04 for public releases for now). |
Cool! So that is it then. I also changed reset timings in update Linux recently. In this second variant I use that same timing. Can you give this a try too? If this works, then the fix is really a trivial change we can also send to upstream U-Boot:
It seems you have a chicken-egg problem there :) You probably would have to change the host system DNS Server to something else to get it to download the Docker image. Should be possible with a |
This is the patch from the first try: 0001-arm64-dts-meson-revert-breaking-change-for-Ethernet.patch.gz And this is the change for the variant 2 test. If this fixes it, I will send that upstream. 0001-arm64-dts-meson-fix-PHY-deassert-timing-requirements.patch.gz |
@agners Off-Topic:
I've tried PS: I've restored my latest backup of 4.20 to 5.12, which has worked flawlessly. :) |
Cool! Thanks a lot for testing! Wrt DNS: The There is some documentation here in the OS repository in the Documentation folder. But its less than optimal and rework is on the todo list. |
It turns out that this actually should not be working, since the change doens't really do anything 🙈 . Is the problem maybe not appearing always and it was just "bad" luck that it worked in your test? I committed now the first fix, and the latest development build should definitely fix it: |
For reference, upstream patch: https://lists.denx.de/pipermail/u-boot/2021-April/446658.html |
This will be fixed from OS 5.14 onwards. |
For anyone wondering, the upgrade from 4.20 to 6.0 went smoothly on the Odroid-C2. |
Hardware Environment
Home Assistant OS release:
Supervisor logs:
Journal logs:
Kernel logs:
Description of problem:
I've tried to setup latest hassos on forgotten ODROID-C2, but was unable to complete installation. Board is powered, Kernel is up, but Ethernet card cannot be found.
After initial boot messages, it start to spam these two lines in loop:
I've tried with sdcard and with emmc, same situation. I found that there was issue similar to this, reported in #1142 apparently fixed on 5.10, but it seems that this is something different. Same behavior with 5.11.
Tried with 4.20 - no issue, installation does not hang and ethernet working as expected.
The text was updated successfully, but these errors were encountered: