Odroid HC1 does not boot on 6.1.y and 6.6.y kernels

[polyzen]

archlinuxarm/PKGBUILDs#2027 (comment) (https://github.com/user-attachments/files/16120285/exception.txt)
ffaille/alarm-linux-odroid-xu3#1

[mdrjr]

What defconfig you used? what gcc you used? what u-boot...
Please don't truncate the boot log

[polyzen]

• https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-odroid-xu3/config
• Built with the gcc-14.1.1+r1+g43b730b9134-1-armv7h package
• Presumably the uboot-odroid-xu3 2018.01-2 package

@bwcknr and/or @kyak, could you provide the logs requested?

[polyzen]

Unrelated, but could you confirm the kernel built from the odroid-6.6.y branch should be used for N2 devices as well? That would mean https://github.com/archlinuxarm/PKGBUILDs/tree/master/core/linux-odroid-n2 could be removed.

Edit: Unless perhaps they should use the generic https://github.com/archlinuxarm/PKGBUILDs/tree/master/core/linux-armv7

[mdrjr]

Yes, we are using odroid-6.6.y for C4 Series, N2 Series and XU4.
I can't reproduce your issue with HC1 using odroid-6.6.y branch.

[wickner-consid]

• https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-odroid-xu3/config
• Built with the gcc-14.1.1+r1+g43b730b9134-1-armv7h package
• Presumably the uboot-odroid-xu3 2018.01-2 package

@bwcknr and/or @kyak, could you provide the logs requested?

Sure, here you go!

@mdrjr thanks for still supporting the eol'ed platform

*edit: attached the log, sorry had a long day
hc1_dump.txt

[kyak]

• https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-odroid-xu3/config
• Built with the gcc-14.1.1+r1+g43b730b9134-1-armv7h package
• Presumably the uboot-odroid-xu3 2018.01-2 package

@bwcknr and/or @kyak, could you provide the logs requested?

Sure, here you go!

@mdrjr thanks for still supporting the eol'ed platform

*edit: attached the log, sorry had a long day hc1_dump.txt

My HC1 refuses to boot with exact same error (won't duplicate logs).

[polyzen]

I learned how to properly use defconfig's now 😅. Please try linux-odroid-xu3 6.6.44-1 @wickner-consid @kyak

What defconfig you used?

odroidxu4_defconfig. Previously I had copied the defconfig rather than using make ARCH=arm odroidxu4_defconfig, and during the build I had to provide some decisions when prompted for some configurations options. I had used the other kernel configs in https://github.com/archlinuxarm/PKGBUILDs/tree/master/core to fill in those answers. With a fresh .config created with make ARCH=arm odroidxu4_defconfig, now I only had to adjust CONFIG_LOCALVERSION.

[polyzen]

The package config had also been missing these changes:
5776281
b9e3e21

[graysky2]

@mdrjr -

Yes, we are using odroid-6.6.y for C4 Series, N2 Series and XU4.
I can't reproduce your issue with HC1 using odroid-6.6.y branch.

Do you know if this branch will work with the C1 or C2?

[Basanites]

@bwcknr and/or @kyak, could you provide the logs requested?

Sure, here you go!

@mdrjr thanks for still supporting the eol'ed platform

*edit: attached the log, sorry had a long day hc1_dump.txt

Sadly I have to report the issue on the current kernel too.
This is my HC1 crash log on 6.6.50-3: kernel_panic.log
The issue seems to lie in the same function as before, at least the virtual address, *pgd and *pmd are all the same.
I would be happy to try and debug if you can give me any pointers.

In the meantime, could somebody point me in the right direction on how to compile a working kernel from an x86 system 😅 ?

[kyak]

In the meantime, could somebody point me in the right direction on how to compile a working kernel from an x86 system 😅 ?

If you need any kernel, then regular linux-armv7 on Arch Linux ARM works fine for me.

This vendor kernel still doesn't work for me (same crash as your's).

[Basanites]

Ah nice, thanks for the super quick reply and info! (and sorry for the ping, forgot you would be notified from the quote)

If you need any kernel, then regular linux-armv7 on Arch Linux ARM works fine for me.

Follow up to that:
Is there any way you can recommend to me, to get that installed on my board? I full on can't boot right now and don't have a backup which includes the kernel.

Do you know of any way or just suck it up and reinstall from scratch with the linux-armv7 package?

[mdrjr]

One question, are you guys using xu4 dtb or hc1 dtb?

[Basanites]

One question, are you guys using xu4 dtb or hc1 dtb?

How can I check?
I am running this package https://archlinuxarm.org/packages/armv7h/linux-odroid-xu3 on arch linux arm if that helps already.

[kyak]

Do you know of any way or just suck it up and reinstall from scratch with the ´linux-armv7´ package?

Well, I just plugged the SD card to laptop and overwrote broken zImage with the one from linux-armv7 package. As soon as it booted, I installed linux-armv7 package properly.

[Basanites]

Thanks a ton! The kernel now loads but systemd refuses to run because I have systemd.unified_cgroup_hierarchy=0 because docker was not running under the old kernel otherwise.

To not go any further offtopic, thank you so much @kyak and if I can be of any further help just give me a ping @mdrjr

Edit: if anybody stumbles onto this from Google. Here is how I got back to a running system afterwards. Fixing the systemd issue requires unplugging your sd card, plugging it into your (linux) PC, navigating to boot, removing the offending parameters and running sudo mkscr. Iirc this was a fix for docker when the odroid kernel was stuck on 4.7 or something alike and the linux-armv7 package did not work. With the current kernel docker works fine.
With that out of the way I was able to boot, but ethernet did not work. For that I copied all files from the linux-armv7 package to my SD card, removed the old mkinitcpio preset, booted the device, ran sudo mkinitcpio -P and rebooted (not sure if these two steps are actually necessary). To fix the missing kernel modules I ran sudo modprobe -c and another sudo mkinitcpio -P. After one last reboot everything was up and running smoothly again, allowing me to truly install the linux-armv7 package and update the remaining system.