Kernel 6.2 does not boot on Odroid N2+

[woody]

On Odroid N2+, I updated the kernel from v5.19.8-1 to v6.2.1-1 and the installation failed to boot. I reverted to the v5.19.8-1, and it boots normally. Does anybody know what the problem is with this kernel version? I've seen reference to a patch in another forum, but I don't what the patch does and I haven't seen it propagated to the Arch Arm repositories.

First, here is uname on my odroid n2
$this->bbcode_second_pass_quote('', 'L')inux n2 6.2.1-1-aarch64-ARCH #1 SMP PREEMPT_DYNAMIC Sat Feb 25 15:18:35 MST 2023 aarch64 GNU/Linux

[woody]

Thanks for your response!. Yes, I am running headless and I have a problem seeing the serial console. I think it's an issue with Petitboot. I am on systemd v253, so the problem might be with a failure to establish an ethernet connection, as you suggest. I guess it would be a good idea to go with the flow and adapt to the Predictable Device Names scheme rather than to keep using the old method.

I found a method that might give me the Predictable name:

$this->bbcode_second_pass_code('', 'udevadm info --export --query=property --path=/sys/class/net/eth0')

Using the output from that command, it looks like the name for my interface would be 'end0' . I'll try setting it up with that and see if I can update to the mainline kernel.

[karog]

$this->bbcode_second_pass_quote('woody', 'U')sing the output from that command, it looks like the name for my interface would be 'end0' . I'll try setting it up with that and see if I can update to the mainline kernel.

[woody]

Thanks for the info. I did actually set it to 'en*' just to be cautious. I haven't updated to kernel 6.2 yet, so I'm still on 5.19. One thing I see is that even though I have the interface set to match 'en*' in /etc/systemd/network, the interface still gets assigned to eth0. is this because the udev rule only gets installed with 6.2? I would prefer to test the interface name change before I update the kernel, if possible.

Also, I have another issue you might be able to help with. I notice that the hwclock is not implemented with the dtb file that I boot with (meson64_odroidn2.dtb). I tried switching to meson-g12b-odroid-n2-plus.dtb, but the system does not seem to boot reliably when I use that one. With meson-g12b-odroid-n2-plus.dtb, hwclock is enabled, though.

Do you know of a better dtb file to use? I can't seem to find any good source of information about which parameters are loaded or where to get reliable device tree files.

[karog]

I can't help with the hwclock.

As I wrote above, the device naming is in systemd-253, not the kernel. And no, you won't see it until you upgrade. Also, cover both eth0 and en* until it works with the upgrade and then check the actual device name and cleanup.

I stuck with eth0 because I will never have another ethernet on my N2 so there will never be a naming problem and I have eth0 referenced in other places like some iptables rules. As I am not entirely sure where all such references are, I don't want to change the name and have unexpected things happen.

[woody]

I see your point. Maybe it's better to stick with eth0. As far as the dtb file, can you tell me which one you're booting with? It should be referenced in your boot.ini file.

In my boot.ini it's called in this line:

$this->bbcode_second_pass_code('', 'load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson64_odroidn2_plus.dtb')

[karog]

$this->bbcode_second_pass_code('', 'load mmc ${devno}:1 ${dtb_loadaddr} /dtbs/amlogic/meson-g12b-odroid-n2.dtb')
Note I have an N2, not the N2+.

These are the only ones in my dtbs
$this->bbcode_second_pass_code('', '$ls -lh | grep "n2"
-rwxr-xr-x 1 root root 69K Apr 5 2019 meson64_odroidn2_android.dtb
-rwxr-xr-x 1 root root 77K Mar 3 17:10 meson-g12b-odroid-n2.dtb
-rwxr-xr-x 1 root root 77K Mar 3 17:10 meson-g12b-odroid-n2-plus.dtb
')
Now you have got me wondering why I don't have meson64_odroidn2.dtb in my dtbs. The only meson64 I have is the one mentioned above for android.

[woody]

I got some of my dtb files from someone a couple of years ago, and I just tried different ones until I got something to work. I don't know which ones are up to date or where to get any newer ones. I know the one I'm using doesn't support everything that's available. I might have to figure out how to build my own, although that may be a rabbit hole I don't want to go down!

[woody]

So, I did the upgrade to the 6.2.2 kernel today, and I am unable to boot up, just as before. It appears that problem is something other than the network name issue, because the boot process seems to fail very quickly. The blue light flashes just for a short time then stops before there would be time for much to happen. Plus, I don't get anything logging to the system log. I'm going to experiment by updating on my older Odroid N2 system and see if I can figure out what's going on.