[OS] Debian Bullseye (11) N2/N2L

[meveric]

The u-boot itself can be compiled on arm64 directly, no problem.
Only the signing needs to be done via x86_64.
Although this depends on how good box64 becomes in the future.
RockChip for example I can already sign with box64 directly under arm64.. but I think t hat's a different topic.

eMMC does not have any specialty on the N2/N2L over SD card.. you can flash the SD card image on the eMMC and it works exactly the same on eMMC as it does on SD card.

[back2future]

Ok, i see. Btw, every of the u-boot versions (2015.01, mainline) has its own advantages.

The difficulty with eMMC for me is with booting u-boot from sd-card and e.g. trying to access an eMMC device from u-boot terminal. While 2015.01 version enables e.g. ls command to eMMC, mainline versions lists the eMMC, but it's not accessible (it is not a problem to start u-boot from a flashed image from eMMC). Maybe it's only about explicitly enabling an eMMC option for u-boot mainline configurations, but haven't found yet (another difficulty seems with configuring 'saveenv' on 0x0 offset setting on mainline u-boot version)? (Thx)

[meveric]

Oddly specific use case, to boot from SD but access eMMC from u-boot console, but well, why not:

Code: Select all

U-Boot 2021.10+dfsg-1 (Oct 10 2021 - 04:20:52 +0000) odroid-n2/n2-plus

Model: Hardkernel ODROID-N2
SoC:   Amlogic Meson G12B (S922X) Revision 29:c (40:2)
DRAM:  3.8 GiB
MMC:   sd@ffe05000: 0, mmc@ffe07000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Board variant: n2-plus
Net:   eth0: ethernet@ff3f0000
Hit any key to stop autoboot:  0 
=> ls mmc 0:1
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<DIR>       4096 dtbs
            3934 boot.scr.txt
            4064 boot.scr
            3838 config.ini.bak
<SYM>         50 dtb
            4264 config.ini
<SYM>         63 dtb-6.0.0-0.deb11.6-rt-arm64
          300549 config-6.2.7-arm64
        15580034 vmlinuz-6.2.7-arm64
<SYM>         50 dtb-6.2.7-arm64
        25445538 uInitrd-6.0.9-arm64
        25387301 initrd.img-6.2.7-arm64
            3238 boot.scr.bak
        25445538 uInitrd
         7289177 System.map-6.2.7-arm64
          297988 config-6.1.14-arm64
        42484224 Image
            3352 boot.scr.txt.bak
            1805 boot.scr.deactivated
        14882173 Image.gz
        14830886 vmlinuz-6.1.14-arm64
          300672 config-6.2.0-rc4-arm64
        15599437 vmlinuz-6.2.0-rc4-arm64
<SYM>         51 dtb-6.1.14-arm64
           79689 meson64_odroidn2l.dtb
          300696 config-6.2.1-arm64
         7103734 System.map-6.1.14-arm64
            6491 boot.ini.bak
              83 System.map-6.0.0-0.deb11.6-rt-arm64
<SYM>         54 dtb-6.2.0-rc4-arm64
        25555134 initrd.img-6.2.0-rc4-arm64
        25482156 initrd.img-6.1.14-arm64
        15625591 vmlinuz-6.2.1-arm64
<SYM>         50 dtb-6.2.1-arm64
         7290463 System.map-6.2.1-arm64
        25399889 initrd.img-6.2.1-arm64
         7287606 System.map-6.2.0-rc4-arm64
          280604 config-6.0.0-0.deb11.6-rt-arm64
        28846016 vmlinuz-6.0.0-0.deb11.6-rt-arm64
        64524314 initrd.img-6.0.0-0.deb11.6-rt-arm64
=> ls mmc 1:1
<DIR>       4096 .
<DIR>       4096 ..
<DIR>      16384 lost+found
<SYM>         49 dtb-4.19.219-arm64
           41831 boot-logo.bmp.gz
            2299 boot.scr
            2298 boot.scr.bak
        14399715 vmlinuz-5.17.1-arm64
             188 config.ini
<SYM>         47 dtb
         7937974 System.map-5.17.1-arm64
<DIR>       4096 dtbs
<SYM>         25 initrd.img
          283337 config-5.17.1-arm64
<SYM>         25 initrd.img.old
<SYM>         22 vmlinuz
<SYM>         47 dtb-5.17.1-arm64
<SYM>         22 vmlinuz.old
          162681 config-4.19.219-arm64
         8856699 vmlinuz-4.19.219-arm64
        13687106 initrd.img-5.17.1-arm64
            2227 boot.scr.txt
         4981085 System.map-4.19.219-arm64
         6622545 initrd.img-4.19.219-arm64
            2299 boot.scr.4.19

works for me, although apparently not with all eMMC modules.. green and black eMMC modules did not work, orange and red did work though.
You can actually hot swap them... not sure how good it's for the health of the eMMC/board.. but i could switch eMMC modules on the fly and check with ls

[back2future]

[ i see, eMMC access from OS system is possible, therefore eMMC device seems functional (~175MB/s), only u-boot (version built from mainline sources) can not access. It's no urgent difficulty, but could help to boot the other OS more directly, what speeds up that boot time on a several seconds base. Thanks for reviewing. Btw, something comparable to ~S.M.A.R.T. for eMMCs. ]

[jmccoy555]

Hi, does anyone have SPDIF via the 7pin header working with this. I have confirmed it works with the official Odroid image but no luck with this and obviously I'd rather use this OS!

[Illusion]

Hi All, Thank you @meveric for providing these images, yours seem to be the only ones that don't have a lot of errors (any!) in my boot.log! I have an N2 v0.4 that I've been running (using Armbian 20.05) in a remote location for about a year. I'm at the remote site, trying to move toward something that will give me better access to more GPIO pins, the Armbian definition only gave me a few.

I ran into the same problem that kl_sensio had in this thread's post: viewtopic.php?p=367557#p367557. I didn't notice it when I first read that post, but later, when closely examining my logs. There is no overlay/ directory in the /boot/dtbs/<kernel>/ path. I modified my boot.cmd/boot.scr file to remove that directory (changed to: setenv overlaypath "amlogic/odroidn2", and suddenly the overlays were loading! Later, I read that @meveric's build work-flow needed that directory name, so another way was to contort the /boot directory structure so everything is in the right place (including a symbolic link to amlogic/meson64_odroid${variant}.dtb. That change loaded overlays, too.

My current problem is that while the serial overlays are loaded, the ttyAML6 and ttyAML7 ports (that come up for uart0 and uart1) don't function (I've got a GPS connected to one, with a constant data stream). I DID get the GPS to work when I booted debian-bullseye-server-odroidn2plus-20220128.img that I got from the Odroid website, but it uses the 4.9 kernel and doesn't have Wireguard built in (which I also need). I tried compiling wireguard-dkms, but there were too many errors (and searching showed many others with the same problem), so I abandoned that image and found yours (@meveric).

1) Are there many substantive differences between the de-compiled DTB files, such as the interrupts = <....> definitions? I noticed that the serial ports of interest have different interrupt values.
2) Am I correct in assuming that there should be no difference between the device trees of the different kernels (4.19, 5.15, 6.1, 6.3), because it is simply a hardware definition file? It also links drivers, so maybe the compatible = "....." names need to be specific for the given kernel.
3) When building a new kernel, where does one go to find the DTS? I noticed the various DTSI files in the main Odroid Linux kernel source tree, so I assume it's from there.
4) Could it be that most of the differences happen automatically (like the phandle definitions) when a kernel is built, and thus are not "substantive" (unlike the "cpu-active" trip, added to the thermal-zones in 6.3)?

I'm on a limited data plan, so I'd prefer to not download the entire kernel repository, just to see if I can build a working DTS structure for my poor old N2. I'm tempted to use the 6.1 DTB with the 6.3 kernel, then maybe modify the 6.3 serial ports to resemble the 4.19 DTB.

Thanks again for all your work! I apologize for all my newbie questions.
Doug

[Illusion]

Quick update: I put a symbolic link in place of the 6.3 DTB, pointing to the 6.1 DTB (moving the original as a backup) and rebooted 6.3 with the 6.1 device tree. I got my working serial port! I haven't explored different versions of the tree to determine what made it work, but if I get a chance before I need to depart, I'll post back here. My other questions are less relevant, but still interesting to me, if anyone wants to point me in the right direction. I'm making my way through the kernel.org device tree documentation already.

My GPS server is running with Wireguard and my other monitoring scripts, so I have regained remote access to this system's monitoring.

Thanks again to everyone who's helped bring my N2 into the modern kernels!
Doug

[meveric]

Hi,

Let's see if I can answer some of your questions.
I'm not big into GPIOs therefore I can't answer specifics but I know that in general they work and I have been testing them out a bit.

1) Are there many substantive differences between the de-compiled DTB files, such as the interrupts = <....> definitions? I noticed that the serial ports of interest have different interrupt values.

Sadly that's a bit too specific for me I would assume the interrupts shouldn't change a lot but as you asked later on how to find the decompiled versions of the files, you can read up on it and hopefully find your answer

2) Am I correct in assuming that there should be no difference between the device trees of the different kernels (4.19, 5.15, 6.1, 6.3), because it is simply a hardware definition file? It also links drivers, so maybe the compatible = "....." names need to be specific for the given kernel.

Your assumption is not entirely correct.
Kernel 4.19 was provided by the SoC vendor (AmLogic) and is a highly modified Kernel snapshot with lots of alteration specific for the SoC, a simple example is the GPU drivers, which for version 4.19 is based around the closed source Mali drivers. Linux would not include Kernel Modules for closed source drivers into to Kernel as it's against their policy, still they are included in this specific branch of the Kernel. And there are a lot of other modifications from the Vendor including GPIOs I would assume. Therefore 4.19 is probably very specific and may not match what other Kernel versions are using.
Kernel 5.15 is probably what Armbian is using. I know Armbian does a lot of changes to their Kernels while it's probably closer to my Kernels when it comes to patches I can not say for sure as I don't follow up the development.
For 6.1 or 6.3 which I provide. The dtb files are probably very similar with only minor changes they are based on the upstream sources meaning since the N2 is now officially supported by Linux Kernel it ships with official dts/dtb files for hardware definitions.
While the definition itself will probably not change much some of the notation might change depending on how the Kernel changes and how it expects the new notations.. most of it should only be semantic though not changing of interrupt vales or such.

3) When building a new kernel, where does one go to find the DTS? I noticed the various DTSI files in the main Odroid Linux kernel source tree, so I assume it's from there.

the DTS comes from the Kernel source. I'm using: https://git.kernel.org/pub/scm/linux/ke ... /linux.git
Here you can find the definitions for the N2 for example: https://git.kernel.org/pub/scm/linux/ke ... ts/amlogic
Please note, that at the top of these files there are often includes from which it pulls additional definitions and the file itself are just overwrites of the defaults which in the end will be assembled to the final dtb file.
For example:
meson-g12b-odroid-n2.dts:

Code: Select all

// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
/*
 * Copyright (c) 2019 BayLibre, SAS
 * Author: Neil Armstrong <narmstrong@baylibre.com>
 */

/dts-v1/;

#include "meson-g12b-s922x.dtsi"
#include "meson-g12b-odroid-n2.dtsi"

/ {
	compatible = "hardkernel,odroid-n2", "amlogic,s922x", "amlogic,g12b";
	model = "Hardkernel ODROID-N2";
};

It only overwrites the model and compatible, the rest is imported from meson-g12b-odroid-n2.dtsi and meson-g12b-s922x.dtsi which in return import other definitions.
It can take a while to get all of the parts pieced together

4) Could it be that most of the differences happen automatically (like the phandle definitions) when a kernel is built, and thus are not "substantive" (unlike the "cpu-active" trip, added to the thermal-zones in 6.3)?

Not exactly the Kernel development team adds new features to the Kernel itself and if required they adjust the dts files accordingly. Sometimes I also snatch some patches either from @tobetter:
https://github.com/tobetter/linux/tree/odroid-6.3.y
or from Armbian if they make sense to me. Which may change some of the definitions for example regarding VPU support so that open source drivers work better out of the box with H264 and HEVC support.
But it also means any one of the people involved can forget to add something or has added something that is no longer working due to changes in the Kernel.

I'm on a limited data plan, so I'd prefer to not download the entire kernel repository, just to see if I can build a working DTS structure for my poor old N2. I'm tempted to use the 6.1 DTB with the 6.3 kernel, then maybe modify the 6.3 serial ports to resemble the 4.19 DTB.

GPIOs went under a lot of changes over the years it's not just the "dts" that was changed (which in most cases is probably still the same definition) but mainly the way the Kernel handles the GPIOs was changed drastically.
For example the ODROID-C2 originally came with Kernel 3.10/3.16 GPIOs were numbered between 200~250 for example.
Later Kernel 4.x switched the layout to something between 430~480 if I remember correctly in Kernel 6.x it went up again and pin layout is between 500~600 now, with some pins over 600. Not only did the GPIO numbers change, but with Kernel 5.x you had two gpiochips splitted between gpiochip0 and gpiochip1 with some boards I have now seen up to 36 gpiochips (depending on the ODROID model). This is an underlying change in the Linux Kernel and has nothing to do with the DTB file.
In the DTB nothing changed regarding this, so it may not be possible for you to change everything back to how it was with Kernel 4.19 in your case.

BTW I also provide 6.1 LTS Kernel which you can switch to, if you want to stay with a "relative stable" branch rather than always going for the latest Kernel.

[Illusion]

Yes, thanks, that helps me understand a lot more. I found your 6.1 LTS kernel and am using it now. Everything seems to be working as I need it. Thanks again! --Doug

[kl_sensio]

Got the same result with a different odroid n2+

You still get the same error about failing to load dtbo files?
Do you have any other SD/eMMC connected at the same time?

I only use eMMC. Upgraded to 6.3.11 kernel still same result..

[Moan]

Hi.

Since I changed my router to Asus GT-AX6000, my USB to Ethernet adapter (RL8156B) started crashing the kernel. I tried many drivers, including the newest version 2.17.1 ( https://www.realtek.com/en/component/zo ... 0-software )

It crashes with error: transmit queue 0 timed out, then it becomes fully frozen, filesystem gets unmounted and only power cycle helps:
https://i.imgur.com/KUAG0gI.jpg

I can easily reproduce this problem, because it usually happens right after wireguard starts (120 seconds after boot). But obviously, without wireguard it would crash few seconds / minutes later.

I thought I installed some updates that could break it, but then I restored a full backup of my boot and system partition from April 2023, and I have the same issue. I have got two of these RL8156B adapters (from different manufacturers), and they both are experiencing the same issue.

When I connect my old router, everything seems to be back to normal, but I remember some occasional freezes that occurred every few weeks (maybe even unrelated to this adapter). I wonder if anybody experienced the same issue with these adapters? For now I blame the new router (and I'll probably refund it), but it still looks like something is wrong with the USB drivers or whatever.

Following some other threads, I added:

Code: Select all

extraargs=usbcore.quirks=0bda:8156:k,05e3:0612:k,05e3:0620:k

to config.ini (successfully, according to cat /proc/cmdline), but it didn't help.

I also tried:

Code: Select all

ethtool -K eth1 tx off sg off tso off

Which didn't help.

Do you guys have any idea what I could try to fix it? The new router doesn't seem to use any jumbo frames. The adapter most likely freezes because the new router is... faster. But that's still strange.

[meveric]

In the picture it looks like the network scheduler is crashing or the watchdog for it.
I have the feeling that the rtl8152 driver is not very stable, as we see issues with it on the XU4 as well.
Do you have any other USB to LAN adapters you could test, a different brand?

Also, you could try installing irqbalance which will distribute irq request more efficiently over different cores, which can increase performance and maybe it helps with the crashes?

But for now I would suggest if you can, try a different USB adapter that is not realtek based and see if this may solve the issue.

[mad_ady]

Or, if 1Gbps is enough, you can use ethtool to force the connection in 1Gbps mode.

[Moan]

Thanks for the answers.

Or, if 1Gbps is enough, you can use ethtool to force the connection in 1Gbps mode.

I think it didn't work (because I connected it to the 1Gb/s LAN port in the router, and it was still crashing bad.

I found some old 1Gb/s USB adapter. I don't know what chipset it is (it's from Ugreen), but worth to try.

Just to clarify, I was getting full 2.5Gb/s speeds with that adapter with no crashes. The problem started after I bought a new router (and factory resetted it). I tried flashing older router firmware (and Merlin) but nothing seems to change it. So the router is to blame too, but logically, devices should defend itself from too-many packets or something.
Also, I use an externally powered USB-hub for this adapter, but I tried when it was connected directly to N2 with the same crashes.

I think I'll try one more night to see if I can fix it, if not I'll just refund that router and use the old one

[Moan]

Sorry guys, I won't be able to test it.

I decided to return that disgusting bugged Asus router. I was unable to connect it to the Internet (simple DHCP with MAC change) for over 2 hours, while 2 other routers (from ISP and my old one) worked fine. So I decided that it's not worth the risk to keep a bugged device like this.

Since the problem with Ethernet crashes don't occur on my old router, unfortunately (or fortunately) I won't be able to test it more. Maybe there's some way to trigger this crash, but to be honest, for the normal NAS use (saving / reading files with speed around 210MB/s) I never had problems like this.

[mad_ady]

As anecdotal information - I once had a small cisco switch in my lan that for some reason sometimes decided to flood all ports with Ethernet OAM frames. The purpose of these was to let downstream devices know the switch was receiving too much traffic, and they should stop transmitting for a while. But since the switch was sending too many of these, the effect was that nothing on my LAN could send traffic anymore.
Moral of the story: your router might have some default option enabled that does more harm than good, but without a packet capture it's difficult to tell what it is.

[Moan]

What is more strange:
- I bought this router, configured and used for a few days with no problem. I flashed merlin firmware on it, and it still worked good.
- After a few days I decided to restore factory settings (just because I was playing with it for the first days, testing options, etc. so a fresh start was a smart thing).
- As soon as the factory settings router rebooted (and made a simple configuration such as DHCP) Odroid started crashing with that USB ethernet adapter.
- I spent hours trying to fix drivers etc. I also flashed official Asus firmware, older versions of it and was restoring factory default settings all the time. Nothing seemed to help.

So they either released the recent firmware versions with some flooding, or I don't know what happened. Either way Asus routers are bad, so maybe it's better that such thing happened now, before the refund period expired?

EDIT:

FYI: I wrote a new thread Odroid N2: My watchdog scripts to optimize the 2.5Gb USB Ethernet Adapter (tested with RTL8156B).
It has some extra tips how to optimize a performance of these USB adapters. Maybe somebody find it helpful, it's working with this Debian Bullseye (11) N2/N2L image.

[kl_sensio]

Finally got around to test this a little bit.

So as it should be the RTC is found automatically you don't need to load the module manually.
BUT the RTC is connected to the I2C bus, and the I2C bus is not loaded automatically.
For this you need to activate i2c as an overlay.

In /boot/config.ini
you should already find a section for overlays.
If you add fk_overlays=i2c1
You could also activate i2c0 (fk_overlays=i2c0 i2c1) but apparently that is not needed.

Once i2c1 is loaded, rtc is found automatically and activated.

Hi meveric,

Flashed my N2+ with the latest image and added fk_overlays=i2c1 i2c0 in config.ini but still the RTC won't work. At the boot I'll get this error:



Same result after upgrading to 6.2.1.
Any idea how to fix this?

I finally figured out the problem with loading the overlays. The overlay files are located in /boot/dtbs/6.3.11-arm64/amlogic/odroidn2 when it should be in /boot/dtbs/6.3.11-arm64/overlays/amlogic/odroidn2. Had to create the overlays folder and move the amlogic folder to it. Now I have a working hwclock again.


Kristian

[meveric]

I wonder if you only use part of my packages.. I changed the path for the overlay files a while ago and there is a script that puts these files in the correct folder.
It's working perfectly fine for me and was updated months ago to this.
My guess is, your script that put the files in the correct folder is not in place as it should be, meaning it was never updated, while it should have been updated a long time ago, no manual changes needed.

The script should have been updated together with the package setup-odroid which was pre-installed and should have been updated multiple times by now.
You can compare: /etc/kernel/postinst.d/copy-overlays with /usr/local/share/setup-odroid/fixes/General/copy-overlays which should be identical unless the second one does not exist due to the fact that you removed it or something like that.

[servili007]

I wonder if you only use part of my packages.. I changed the path for the overlay files a while ago and there is a script that puts these files in the correct folder.
It's working perfectly fine for me and was updated months ago to this.
My guess is, your script that put the files in the correct folder is not in place as it should be, meaning it was never updated, while it should have been updated a long time ago, no manual changes needed.

The script should have been updated together with the package setup-odroid which was pre-installed and should have been updated multiple times by now.
You can compare: /etc/kernel/postinst.d/copy-overlays with /usr/local/share/setup-odroid/fixes/General/copy-overlays which should be identical unless the second one does not exist due to the fact that you removed it or something like that.

For what it's worth, on a fresh image I'm seeing the same behavior of failing to load/find the dtbs by default. Only steps taken were to manually update date/time to resolve cert issues, run updates, and add i2c1 to config.ini.

It's still looking for files in the overlay folder, while the 6.3 folder puts everything in amlogic.

[meveric]

For what it's worth, on a fresh image I'm seeing the same behavior of failing to load/find the dtbs by default. Only steps taken were to manually update date/time to resolve cert issues, run updates, and add i2c1 to config.ini.

It's still looking for files in the overlay folder, while the 6.3 folder puts everything in amlogic.

I did some testing and here are the results starting from a newly flashed image:

Fixing date for apt:

Code: Select all

root@odroid-bullseye64:~# date
Sun 07 Aug 2022 01:27:03 PM UTC
root@odroid-bullseye64:~# systemctl restart systemd-timesyncd.service 
root@odroid-bullseye64:~# date
Sun 24 Sep 2023 01:06:37 PM UTC

apt runs fine after that:

Code: Select all

root@odroid-bullseye64:~# apt update
Get:1 http://security.debian.org bullseye-security InRelease [48.4 kB]
Get:2 http://deb.debian.org/debian bullseye InRelease [116 kB]                                  
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]                                    
Get:4 http://www.deb-multimedia.org bullseye InRelease [17.8 kB]
Get:5 http://deb.debian.org/debian bullseye-backports InRelease [49.0 kB]              
Get:6 http://security.debian.org bullseye-security/main arm64 Packages [243 kB]                
Get:7 http://security.debian.org bullseye-security/main Translation-en [160 kB]               
Get:8 http://security.debian.org bullseye-security/non-free Translation-en [464 B]                           
Get:9 http://deb.debian.org/debian bullseye/main arm64 Packages [8,071 kB]                                  
Get:10 https://oph.mdrjr.net/meveric all InRelease [19.4 kB]
Get:11 https://oph.mdrjr.net/meveric bullseye InRelease [4,136 B]  
Get:12 http://www.deb-multimedia.org bullseye/main arm64 Packages [124 kB]
Get:13 http://www.deb-multimedia.org bullseye/main Translation-en [88.7 kB]
Get:14 http://www.deb-multimedia.org bullseye/non-free arm64 Packages [1,736 B]
Get:15 http://www.deb-multimedia.org bullseye/non-free Translation-en [2,039 B]
Get:16 http://deb.debian.org/debian bullseye/main Translation-en [6,240 kB]   
Get:17 https://oph.mdrjr.net/meveric all/main arm64 Packages [30.6 kB]                 
Get:18 https://oph.mdrjr.net/meveric all/testing arm64 Packages [1,816 B]                             
Get:19 https://oph.mdrjr.net/meveric bullseye/main arm64 Packages [17.7 kB]                            
Get:20 https://oph.mdrjr.net/meveric bullseye/backports arm64 Packages [45.2 kB]                       
Get:21 http://deb.debian.org/debian bullseye/contrib arm64 Packages [41.0 kB]                    
Get:22 http://deb.debian.org/debian bullseye/contrib Translation-en [46.9 kB]
Get:23 http://deb.debian.org/debian bullseye/non-free arm64 Packages [73.0 kB]
Get:24 http://deb.debian.org/debian bullseye/non-free Translation-en [92.2 kB]
Get:25 http://deb.debian.org/debian bullseye-updates/main arm64 Packages [14.9 kB]
Get:26 http://deb.debian.org/debian bullseye-updates/main Translation-en [10.1 kB]
Get:27 http://deb.debian.org/debian bullseye-backports/main arm64 Packages [402 kB]
Get:28 http://deb.debian.org/debian bullseye-backports/main Translation-en [341 kB]
Get:29 http://deb.debian.org/debian bullseye-backports/contrib arm64 Packages [5,180 B]
Get:30 http://deb.debian.org/debian bullseye-backports/contrib Translation-en [5,984 B]
Get:31 http://deb.debian.org/debian bullseye-backports/non-free arm64 Packages [9,780 B]
Get:32 http://deb.debian.org/debian bullseye-backports/non-free Translation-en [27.6 kB]
Fetched 16.4 MB in 6s (2,694 kB/s)                                                                                                                                                                                
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
28 packages can be upgraded. Run 'apt list --upgradable' to see them.

installing tree and checking file layout in boot partition

Code: Select all

root@odroid-bullseye64:~# apt install tree
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  tree
0 upgraded, 1 newly installed, 0 to remove and 28 not upgraded.
Need to get 48.2 kB of archives.
After this operation, 117 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main arm64 tree arm64 1.8.0-1 [48.2 kB]
Fetched 48.2 kB in 0s (227 kB/s)
Selecting previously unselected package tree.
(Reading database ... 33676 files and directories currently installed.)
Preparing to unpack .../tree_1.8.0-1_arm64.deb ...
Unpacking tree (1.8.0-1) ...
Setting up tree (1.8.0-1) ...
root@odroid-bullseye64:~# tree /boot
/boot
├── boot.scr
├── config-6.1.0-arm64
├── config.ini
├── dtb -> dtbs/6.1.0-arm64/rockchip/rk3399-odroid-n1.dtb
├── dtb-6.1.0-arm64 -> dtbs/6.1.0-arm64/rockchip/rk3399-odroid-n1.dtb
├── dtbs
│   └── 6.1.0-arm64
│       ├── amlogic
│       │   ├── meson64_odroidc2.dtb
│       │   ├── meson64_odroidc4.dtb
│       │   ├── meson64_odroidhc4.dtb
│       │   ├── meson64_odroidn2.dtb
│       │   ├── meson64_odroidn2l.dtb
│       │   ├── meson64_odroidn2_plus.dtb
│       │   ├── meson-g12b-odroid-n2.dtb
│       │   ├── meson-g12b-odroid-n2l.dtb
│       │   ├── meson-g12b-odroid-n2-plus.dtb
│       │   ├── meson-gxbb-odroidc2.dtb
│       │   ├── meson-sm1-odroid-c4.dtb
│       │   ├── meson-sm1-odroid-hc4.dtb
│       │   └── overlays
│       │       ├── odroidc4
│       │       │   ├── display_vu7c.dtbo
│       │       │   ├── hifishield2.dtbo
│       │       │   ├── hktft32.dtbo
│       │       │   ├── hktft35.dtbo
│       │       │   ├── i2c0.dtbo
│       │       │   ├── i2c1.dtbo
│       │       │   ├── pcf8563.dtbo
│       │       │   ├── pps-gpio_p11.dtbo
│       │       │   ├── pps-gpio_p12.dtbo
│       │       │   ├── spi0.dtbo
│       │       │   ├── sx865x-i2c1.dtbo
│       │       │   ├── uart0.dtbo
│       │       │   ├── uart1.dtbo
│       │       │   ├── uart2.dtbo
│       │       │   ├── uart3.dtbo
│       │       │   ├── w1-gpio_p15.dtbo
│       │       │   └── w1-gpio_p22.dtbo
│       │       └── odroidn2
│       │           ├── fanspeed-full.dtbo
│       │           ├── hktft35.dtbo
│       │           ├── i2c0.dtbo
│       │           ├── i2c1.dtbo
│       │           ├── pps-gpio_p11.dtbo
│       │           ├── pps-gpio_p12.dtbo
│       │           ├── pwm_cd.dtbo
│       │           ├── pwm_ef.dtbo
│       │           ├── pwmfan-lowtemp.dtbo
│       │           ├── spi0.dtbo
│       │           ├── sx865x-i2c1.dtbo
│       │           ├── uart0.dtbo
│       │           ├── uart1.dtbo
│       │           ├── w1-gpio_p15.dtbo
│       │           └── w1-gpio_p22.dtbo
│       ├── rk3399-odroid-n1.dtb -> rockchip/rk3399-odroid-n1.dtb
│       └── rockchip
│           ├── overlays
│           │   ├── odroidm1
│           │   │   ├── i2c0.dtbo
│           │   │   ├── i2c1.dtbo
│           │   │   ├── onewire.dtbo
│           │   │   ├── pwm1.dtbo
│           │   │   ├── pwm2.dtbo
│           │   │   ├── pwm9.dtbo
│           │   │   ├── spi0.dtbo
│           │   │   ├── uart0.dtbo
│           │   │   ├── uart0-with-ctsrts.dtbo
│           │   │   └── uart1.dtbo
│           │   ├── rockchip-dwc3-0-host.dtbo
│           │   ├── rockchip-i2c7.dtbo
│           │   ├── rockchip-i2c8.dtbo
│           │   ├── rockchip-pcie-gen2.dtbo
│           │   ├── rockchip-rk3328-opp-1.4ghz.dtbo
│           │   ├── rockchip-rk3328-opp-1.5ghz.dtbo
│           │   ├── rockchip-rk3399-opp-2ghz.dtbo
│           │   ├── rockchip-spi-jedec-nor.dtbo
│           │   ├── rockchip-spi-spidev.dtbo
│           │   ├── rockchip-uart4.dtbo
│           │   └── rockchip-w1-gpio.dtbo
│           ├── rk3326-odroid-go2.dtb
│           ├── rk3399-odroid-n1.dtb
│           └── rk3568-odroid-m1.dtb
├── initrd.img-6.1.0-arm64
├── lost+found
├── System.map-6.1.0-arm64
└── vmlinuz-6.1.0-arm64

10 directories, 77 files

as expected overlays currently are located in the old folder layout:
/boot/dtbs/<Kernel-Version>/amlogic/overlays/

performing a full system upgrade:

Code: Select all

root@odroid-bullseye64:~# apt update && apt upgrade && apt dist-upgrade && apt autoremove && apt clean && apt update
Hit:1 http://www.deb-multimedia.org bullseye InRelease
Hit:2 http://security.debian.org bullseye-security InRelease                                                            
Hit:3 http://deb.debian.org/debian bullseye InRelease                                                                   
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Hit:5 http://deb.debian.org/debian bullseye-backports InRelease
Hit:6 https://oph.mdrjr.net/meveric all InRelease 
Hit:7 https://oph.mdrjr.net/meveric bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
28 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-6.3.11-arm64 linux-image-6.3.11-arm64
The following packages will be upgraded:
  base-files debian-archive-keyring grep isc-dhcp-client isc-dhcp-common libc-bin libc-l10n libc6 libgnutls30 libjson-c5 libncurses6 libncursesw6 libssl1.1 libsystemd0 libtinfo6 libudev1
  linux-headers-arm64-odroid linux-image-arm64-odroid locales ncurses-base ncurses-bin openssl setup-odroid systemd systemd-sysv systemd-timesyncd tzdata udev
28 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 75.2 MB of archives.
After this operation, 265 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://deb.debian.org/debian bullseye/main arm64 base-files arm64 11.1+deb11u7 [70.1 kB]
Get:2 http://security.debian.org bullseye-security/main arm64 libssl1.1 arm64 1.1.1n-0+deb11u5 [1,390 kB]
Get:3 http://deb.debian.org/debian bullseye/main arm64 grep arm64 3.6-1+deb11u1 [390 kB]
Get:4 http://deb.debian.org/debian bullseye/main arm64 ncurses-bin arm64 6.2+20201114-2+deb11u1 [424 kB]   
Get:5 http://deb.debian.org/debian bullseye/main arm64 libc6 arm64 2.31-13+deb11u6 [2,460 kB]                          
Get:6 http://security.debian.org bullseye-security/main arm64 libjson-c5 arm64 0.15-2+deb11u1 [41.6 kB]
Get:7 http://security.debian.org bullseye-security/main arm64 openssl arm64 1.1.1n-0+deb11u5 [832 kB]
Get:8 https://oph.mdrjr.net/meveric all/main arm64 linux-headers-6.3.11-arm64 arm64 6.3.11-20230701-odroid [8,432 kB]
Get:9 http://deb.debian.org/debian bullseye/main arm64 libc-bin arm64 2.31-13+deb11u6 [741 kB]
Get:10 http://deb.debian.org/debian bullseye/main arm64 ncurses-base all 6.2+20201114-2+deb11u1 [272 kB]
Get:11 http://deb.debian.org/debian bullseye-updates/main arm64 systemd-timesyncd arm64 247.3-7+deb11u4 [130 kB]
Get:12 http://deb.debian.org/debian bullseye-updates/main arm64 libsystemd0 arm64 247.3-7+deb11u4 [355 kB]
Get:13 http://deb.debian.org/debian bullseye-updates/main arm64 systemd arm64 247.3-7+deb11u4 [4,155 kB]
Get:14 http://deb.debian.org/debian bullseye-updates/main arm64 udev arm64 247.3-7+deb11u4 [1,423 kB]
Get:15 http://deb.debian.org/debian bullseye-updates/main arm64 libudev1 arm64 247.3-7+deb11u4 [163 kB]
Get:16 http://deb.debian.org/debian bullseye-updates/main arm64 systemd-sysv arm64 247.3-7+deb11u4 [114 kB]
Get:17 http://deb.debian.org/debian bullseye/main arm64 libgnutls30 arm64 3.7.1-5+deb11u3 [1,262 kB]
Get:18 https://oph.mdrjr.net/meveric all/main arm64 linux-image-6.3.11-arm64 arm64 6.3.11-20230701-odroid [44.8 MB]
Get:19 http://deb.debian.org/debian bullseye/main arm64 debian-archive-keyring all 2021.1.1+deb11u1 [110 kB]
Get:20 http://deb.debian.org/debian bullseye/main arm64 libncurses6 arm64 6.2+20201114-2+deb11u1 [93.1 kB]
Get:21 http://deb.debian.org/debian bullseye/main arm64 libncursesw6 arm64 6.2+20201114-2+deb11u1 [121 kB]
Get:22 http://deb.debian.org/debian bullseye/main arm64 libtinfo6 arm64 6.2+20201114-2+deb11u1 [336 kB]
Get:23 http://deb.debian.org/debian bullseye/main arm64 tzdata all 2021a-1+deb11u10 [286 kB]
Get:24 http://deb.debian.org/debian bullseye/main arm64 isc-dhcp-client arm64 4.4.1-2.3+deb11u2 [329 kB]
Get:25 http://deb.debian.org/debian bullseye/main arm64 isc-dhcp-common arm64 4.4.1-2.3+deb11u2 [145 kB]
Get:26 http://deb.debian.org/debian bullseye/main arm64 libc-l10n all 2.31-13+deb11u6 [865 kB]
Get:27 http://deb.debian.org/debian bullseye/main arm64 locales all 2.31-13+deb11u6 [4,086 kB]
Get:28 https://oph.mdrjr.net/meveric all/main arm64 linux-headers-arm64-odroid arm64 6.3.11-arm64-1 [662 B]                                                                                                       
Get:29 https://oph.mdrjr.net/meveric all/main arm64 linux-image-arm64-odroid arm64 6.3.11-arm64-1 [662 B]                                                                                                         
Get:30 https://oph.mdrjr.net/meveric bullseye/main arm64 setup-odroid all 0.0.1-79 [1,388 kB]                                                                                                                     
Fetched 75.2 MB in 18s (4,292 kB/s)                                                                                                                                                                               
Preconfiguring packages ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../base-files_11.1+deb11u7_arm64.deb ...
Unpacking base-files (11.1+deb11u7) over (11.1+deb11u6) ...
Setting up base-files (11.1+deb11u7) ...
Installing new version of config file /etc/debian_version ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../grep_3.6-1+deb11u1_arm64.deb ...
Unpacking grep (3.6-1+deb11u1) over (3.6-1) ...
Setting up grep (3.6-1+deb11u1) ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../ncurses-bin_6.2+20201114-2+deb11u1_arm64.deb ...
Unpacking ncurses-bin (6.2+20201114-2+deb11u1) over (6.2+20201114-2) ...
Setting up ncurses-bin (6.2+20201114-2+deb11u1) ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../libc6_2.31-13+deb11u6_arm64.deb ...
Unpacking libc6:arm64 (2.31-13+deb11u6) over (2.31-13+deb11u5) ...
Setting up libc6:arm64 (2.31-13+deb11u6) ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../libc-bin_2.31-13+deb11u6_arm64.deb ...
Unpacking libc-bin (2.31-13+deb11u6) over (2.31-13+deb11u5) ...
Setting up libc-bin (2.31-13+deb11u6) ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../ncurses-base_6.2+20201114-2+deb11u1_all.deb ...
Unpacking ncurses-base (6.2+20201114-2+deb11u1) over (6.2+20201114-2) ...
Setting up ncurses-base (6.2+20201114-2+deb11u1) ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../systemd-timesyncd_247.3-7+deb11u4_arm64.deb ...
Unpacking systemd-timesyncd (247.3-7+deb11u4) over (247.3-7+deb11u1) ...
Preparing to unpack .../libsystemd0_247.3-7+deb11u4_arm64.deb ...
Unpacking libsystemd0:arm64 (247.3-7+deb11u4) over (247.3-7+deb11u1) ...
Setting up libsystemd0:arm64 (247.3-7+deb11u4) ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../systemd_247.3-7+deb11u4_arm64.deb ...
Unpacking systemd (247.3-7+deb11u4) over (247.3-7+deb11u1) ...
Preparing to unpack .../udev_247.3-7+deb11u4_arm64.deb ...
Unpacking udev (247.3-7+deb11u4) over (247.3-7+deb11u1) ...
Preparing to unpack .../libudev1_247.3-7+deb11u4_arm64.deb ...
Unpacking libudev1:arm64 (247.3-7+deb11u4) over (247.3-7+deb11u1) ...
Setting up libudev1:arm64 (247.3-7+deb11u4) ...
Setting up systemd (247.3-7+deb11u4) ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_247.3-7+deb11u4_arm64.deb ...
Unpacking systemd-sysv (247.3-7+deb11u4) over (247.3-7+deb11u1) ...
Preparing to unpack .../libgnutls30_3.7.1-5+deb11u3_arm64.deb ...
Unpacking libgnutls30:arm64 (3.7.1-5+deb11u3) over (3.7.1-5+deb11u2) ...
Setting up libgnutls30:arm64 (3.7.1-5+deb11u3) ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../debian-archive-keyring_2021.1.1+deb11u1_all.deb ...
Unpacking debian-archive-keyring (2021.1.1+deb11u1) over (2021.1.1) ...
Setting up debian-archive-keyring (2021.1.1+deb11u1) ...
Removing obsolete conffile /etc/apt/trusted.gpg.d/debian-archive-stretch-automatic.gpg ...
Removing obsolete conffile /etc/apt/trusted.gpg.d/debian-archive-stretch-security-automatic.gpg ...
Removing obsolete conffile /etc/apt/trusted.gpg.d/debian-archive-stretch-stable.gpg ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../libssl1.1_1.1.1n-0+deb11u5_arm64.deb ...
Unpacking libssl1.1:arm64 (1.1.1n-0+deb11u5) over (1.1.1n-0+deb11u3) ...
Setting up libssl1.1:arm64 (1.1.1n-0+deb11u5) ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../libncurses6_6.2+20201114-2+deb11u1_arm64.deb ...
Unpacking libncurses6:arm64 (6.2+20201114-2+deb11u1) over (6.2+20201114-2) ...
Preparing to unpack .../libncursesw6_6.2+20201114-2+deb11u1_arm64.deb ...
Unpacking libncursesw6:arm64 (6.2+20201114-2+deb11u1) over (6.2+20201114-2) ...
Preparing to unpack .../libtinfo6_6.2+20201114-2+deb11u1_arm64.deb ...
Unpacking libtinfo6:arm64 (6.2+20201114-2+deb11u1) over (6.2+20201114-2) ...
Setting up libtinfo6:arm64 (6.2+20201114-2+deb11u1) ...
(Reading database ... 33684 files and directories currently installed.)
Preparing to unpack .../00-tzdata_2021a-1+deb11u10_all.deb ...
Unpacking tzdata (2021a-1+deb11u10) over (2021a-1+deb11u8) ...
Preparing to unpack .../01-isc-dhcp-client_4.4.1-2.3+deb11u2_arm64.deb ...
Unpacking isc-dhcp-client (4.4.1-2.3+deb11u2) over (4.4.1-2.3+deb11u1) ...
Preparing to unpack .../02-isc-dhcp-common_4.4.1-2.3+deb11u2_arm64.deb ...
Unpacking isc-dhcp-common (4.4.1-2.3+deb11u2) over (4.4.1-2.3+deb11u1) ...
Preparing to unpack .../03-libc-l10n_2.31-13+deb11u6_all.deb ...
Unpacking libc-l10n (2.31-13+deb11u6) over (2.31-13+deb11u5) ...
Preparing to unpack .../04-locales_2.31-13+deb11u6_all.deb ...
Unpacking locales (2.31-13+deb11u6) over (2.31-13+deb11u5) ...
Preparing to unpack .../05-libjson-c5_0.15-2+deb11u1_arm64.deb ...
Unpacking libjson-c5:arm64 (0.15-2+deb11u1) over (0.15-2) ...
Selecting previously unselected package linux-headers-6.3.11-arm64.
Preparing to unpack .../06-linux-headers-6.3.11-arm64_6.3.11-20230701-odroid_arm64.deb ...
Unpacking linux-headers-6.3.11-arm64 (6.3.11-20230701-odroid) ...
Selecting previously unselected package linux-image-6.3.11-arm64.
Preparing to unpack .../07-linux-image-6.3.11-arm64_6.3.11-20230701-odroid_arm64.deb ...
Unpacking linux-image-6.3.11-arm64 (6.3.11-20230701-odroid) ...
Preparing to unpack .../08-openssl_1.1.1n-0+deb11u5_arm64.deb ...
Unpacking openssl (1.1.1n-0+deb11u5) over (1.1.1n-0+deb11u3) ...
Preparing to unpack .../09-linux-headers-arm64-odroid_6.3.11-arm64-1_arm64.deb ...
Unpacking linux-headers-arm64-odroid (6.3.11-arm64-1) over (6.1.0-arm64-1) ...
Preparing to unpack .../10-linux-image-arm64-odroid_6.3.11-arm64-1_arm64.deb ...
Unpacking linux-image-arm64-odroid (6.3.11-arm64-1) over (6.1.0-arm64-1) ...
Preparing to unpack .../11-setup-odroid_0.0.1-79_all.deb ...
Unpacking setup-odroid (0.0.1-79) over (0.0.1-77) ...
Setting up systemd-sysv (247.3-7+deb11u4) ...
Setting up libc-l10n (2.31-13+deb11u6) ...
Setting up linux-headers-6.3.11-arm64 (6.3.11-20230701-odroid) ...
Setting up isc-dhcp-client (4.4.1-2.3+deb11u2) ...
Setting up locales (2.31-13+deb11u6) ...
Generating locales (this might take a while)...
  en_US.UTF-8... done
Generation complete.
Setting up tzdata (2021a-1+deb11u10) ...

Current default time zone: 'Etc/UTC'
Local time is now:      Sun Sep 24 13:10:03 UTC 2023.
Universal Time is now:  Sun Sep 24 13:10:03 UTC 2023.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

Setting up libncurses6:arm64 (6.2+20201114-2+deb11u1) ...
Setting up systemd-timesyncd (247.3-7+deb11u4) ...
Setting up udev (247.3-7+deb11u4) ...
Setting up libncursesw6:arm64 (6.2+20201114-2+deb11u1) ...
Setting up linux-image-6.3.11-arm64 (6.3.11-20230701-odroid) ...
update-initramfs: Generating /boot/initrd.img-6.3.11-arm64
Using DTB: amlogic/meson64_odroidn2_plus.dtb
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Installing new meson64_odroidn2_plus.dtb.
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Skipping backup of meson64_odroidn2_plus.dtb.
Installing new meson64_odroidn2_plus.dtb.
flash-kernel: deferring update (trigger activated)
Using DTB: amlogic/meson64_odroidn2_plus.dtb
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Skipping backup of meson64_odroidn2_plus.dtb.
Installing new meson64_odroidn2_plus.dtb.
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Skipping backup of meson64_odroidn2_plus.dtb.
Installing new meson64_odroidn2_plus.dtb.
flash-kernel: deferring update (trigger activated)
Setting up isc-dhcp-common (4.4.1-2.3+deb11u2) ...
Setting up setup-odroid (0.0.1-79) ...
Using DTB: amlogic/meson64_odroidn2_plus.dtb
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Skipping backup of meson64_odroidn2_plus.dtb.
Installing new meson64_odroidn2_plus.dtb.
flash-kernel: deferring update (trigger activated)
Setting up openssl (1.1.1n-0+deb11u5) ...
Setting up libjson-c5:arm64 (0.15-2+deb11u1) ...
Setting up linux-headers-arm64-odroid (6.3.11-arm64-1) ...
Setting up linux-image-arm64-odroid (6.3.11-arm64-1) ...
Processing triggers for libc-bin (2.31-13+deb11u6) ...
Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-6.3.11-arm64
Using DTB: amlogic/meson64_odroidn2_plus.dtb
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Skipping backup of meson64_odroidn2_plus.dtb.
Installing new meson64_odroidn2_plus.dtb.
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Skipping backup of meson64_odroidn2_plus.dtb.
Installing new meson64_odroidn2_plus.dtb.
flash-kernel: installing version 6.3.11-arm64
Generating boot script u-boot image... done.
Skipping backup of boot.scr.
Installing new boot.scr.
Processing triggers for flash-kernel (3.104) ...
Using DTB: amlogic/meson64_odroidn2_plus.dtb
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Skipping backup of meson64_odroidn2_plus.dtb.
Installing new meson64_odroidn2_plus.dtb.
flash-kernel: installing version 6.3.11-arm64
Generating boot script u-boot image... done.
Skipping backup of boot.scr.
Installing new boot.scr.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Hit:1 http://www.deb-multimedia.org bullseye InRelease
Hit:2 http://security.debian.org bullseye-security InRelease
Hit:3 http://deb.debian.org/debian bullseye InRelease
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Hit:5 http://deb.debian.org/debian bullseye-backports InRelease
Hit:6 https://oph.mdrjr.net/meveric all InRelease 
Hit:7 https://oph.mdrjr.net/meveric bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

rechecking layout of files in boot partition:

Code: Select all

root@odroid-bullseye64:~# tree /boot
/boot
├── boot.scr
├── config-6.1.0-arm64
├── config-6.3.11-arm64
├── config.ini
├── dtb -> dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
├── dtb-6.1.0-arm64 -> dtbs/6.1.0-arm64/rockchip/rk3399-odroid-n1.dtb
├── dtb-6.3.11-arm64 -> dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
├── dtbs
│   ├── 6.1.0-arm64
│   │   ├── amlogic
│   │   │   ├── meson64_odroidc2.dtb
│   │   │   ├── meson64_odroidc4.dtb
│   │   │   ├── meson64_odroidhc4.dtb
│   │   │   ├── meson64_odroidn2.dtb
│   │   │   ├── meson64_odroidn2l.dtb
│   │   │   ├── meson64_odroidn2_plus.dtb
│   │   │   ├── meson-g12b-odroid-n2.dtb
│   │   │   ├── meson-g12b-odroid-n2l.dtb
│   │   │   ├── meson-g12b-odroid-n2-plus.dtb
│   │   │   ├── meson-gxbb-odroidc2.dtb
│   │   │   ├── meson-sm1-odroid-c4.dtb
│   │   │   ├── meson-sm1-odroid-hc4.dtb
│   │   │   └── overlays
│   │   │       ├── odroidc4
│   │   │       │   ├── display_vu7c.dtbo
│   │   │       │   ├── hifishield2.dtbo
│   │   │       │   ├── hktft32.dtbo
│   │   │       │   ├── hktft35.dtbo
│   │   │       │   ├── i2c0.dtbo
│   │   │       │   ├── i2c1.dtbo
│   │   │       │   ├── pcf8563.dtbo
│   │   │       │   ├── pps-gpio_p11.dtbo
│   │   │       │   ├── pps-gpio_p12.dtbo
│   │   │       │   ├── spi0.dtbo
│   │   │       │   ├── sx865x-i2c1.dtbo
│   │   │       │   ├── uart0.dtbo
│   │   │       │   ├── uart1.dtbo
│   │   │       │   ├── uart2.dtbo
│   │   │       │   ├── uart3.dtbo
│   │   │       │   ├── w1-gpio_p15.dtbo
│   │   │       │   └── w1-gpio_p22.dtbo
│   │   │       └── odroidn2
│   │   │           ├── fanspeed-full.dtbo
│   │   │           ├── hktft35.dtbo
│   │   │           ├── i2c0.dtbo
│   │   │           ├── i2c1.dtbo
│   │   │           ├── pps-gpio_p11.dtbo
│   │   │           ├── pps-gpio_p12.dtbo
│   │   │           ├── pwm_cd.dtbo
│   │   │           ├── pwm_ef.dtbo
│   │   │           ├── pwmfan-lowtemp.dtbo
│   │   │           ├── spi0.dtbo
│   │   │           ├── sx865x-i2c1.dtbo
│   │   │           ├── uart0.dtbo
│   │   │           ├── uart1.dtbo
│   │   │           ├── w1-gpio_p15.dtbo
│   │   │           └── w1-gpio_p22.dtbo
│   │   ├── overlays
│   │   │   └── amlogic
│   │   │       └── odroidn2
│   │   │           ├── fanspeed-full.dtbo
│   │   │           ├── hktft35.dtbo
│   │   │           ├── i2c0.dtbo
│   │   │           ├── i2c1.dtbo
│   │   │           ├── pps-gpio_p11.dtbo
│   │   │           ├── pps-gpio_p12.dtbo
│   │   │           ├── pwm_cd.dtbo
│   │   │           ├── pwm_ef.dtbo
│   │   │           ├── pwmfan-lowtemp.dtbo
│   │   │           ├── spi0.dtbo
│   │   │           ├── sx865x-i2c1.dtbo
│   │   │           ├── uart0.dtbo
│   │   │           ├── uart1.dtbo
│   │   │           ├── w1-gpio_p15.dtbo
│   │   │           └── w1-gpio_p22.dtbo
│   │   ├── rk3399-odroid-n1.dtb -> rockchip/rk3399-odroid-n1.dtb
│   │   └── rockchip
│   │       ├── overlays
│   │       │   ├── odroidm1
│   │       │   │   ├── i2c0.dtbo
│   │       │   │   ├── i2c1.dtbo
│   │       │   │   ├── onewire.dtbo
│   │       │   │   ├── pwm1.dtbo
│   │       │   │   ├── pwm2.dtbo
│   │       │   │   ├── pwm9.dtbo
│   │       │   │   ├── spi0.dtbo
│   │       │   │   ├── uart0.dtbo
│   │       │   │   ├── uart0-with-ctsrts.dtbo
│   │       │   │   └── uart1.dtbo
│   │       │   ├── rockchip-dwc3-0-host.dtbo
│   │       │   ├── rockchip-i2c7.dtbo
│   │       │   ├── rockchip-i2c8.dtbo
│   │       │   ├── rockchip-pcie-gen2.dtbo
│   │       │   ├── rockchip-rk3328-opp-1.4ghz.dtbo
│   │       │   ├── rockchip-rk3328-opp-1.5ghz.dtbo
│   │       │   ├── rockchip-rk3399-opp-2ghz.dtbo
│   │       │   ├── rockchip-spi-jedec-nor.dtbo
│   │       │   ├── rockchip-spi-spidev.dtbo
│   │       │   ├── rockchip-uart4.dtbo
│   │       │   └── rockchip-w1-gpio.dtbo
│   │       ├── rk3326-odroid-go2.dtb
│   │       ├── rk3399-odroid-n1.dtb
│   │       └── rk3568-odroid-m1.dtb
│   └── 6.3.11-arm64
│       ├── amlogic
│       │   ├── meson64_odroidn2_plus.dtb
│       │   └── odroidn2
│       │       ├── fanspeed-full.dtbo
│       │       ├── hktft35.dtbo
│       │       ├── i2c0.dtbo
│       │       ├── i2c1.dtbo
│       │       ├── pps-gpio_p11.dtbo
│       │       ├── pps-gpio_p12.dtbo
│       │       ├── pwm_cd.dtbo
│       │       ├── pwm_ef.dtbo
│       │       ├── pwmfan-lowtemp.dtbo
│       │       ├── spi0.dtbo
│       │       ├── sx865x-i2c1.dtbo
│       │       ├── uart0.dtbo
│       │       ├── uart1.dtbo
│       │       ├── w1-gpio_p15.dtbo
│       │       └── w1-gpio_p22.dtbo
│       └── meson64_odroidn2_plus.dtb -> amlogic/meson64_odroidn2_plus.dtb
├── initrd.img-6.1.0-arm64
├── initrd.img-6.3.11-arm64
├── lost+found
├── System.map-6.1.0-arm64
├── System.map-6.3.11-arm64
├── vmlinuz-6.1.0-arm64
└── vmlinuz-6.3.11-arm64

16 directories, 114 files

We can observe two major changes, first, the new Kernel is available but uses a layout similar to the old layout for overlays under /boot/dtbs/6.3.11-arm64/amlogic/odroidn2/.

But we can also see the expected new layout for Kernel 6.1:
/boot/dtbs/6.1.0-arm64/overlays/amlogic/odroidn2/

checking back the order of installed packages we can observe the following:

Code: Select all

Preparing to unpack .../09-linux-headers-arm64-odroid_6.3.11-arm64-1_arm64.deb ...
Unpacking linux-headers-arm64-odroid (6.3.11-arm64-1) over (6.1.0-arm64-1) ...
Preparing to unpack .../10-linux-image-arm64-odroid_6.3.11-arm64-1_arm64.deb ...
Unpacking linux-image-arm64-odroid (6.3.11-arm64-1) over (6.1.0-arm64-1) ...
Preparing to unpack .../11-setup-odroid_0.0.1-79_all.deb ...
Unpacking setup-odroid (0.0.1-79) over (0.0.1-77) ...

and:

Code: Select all

Setting up linux-image-6.3.11-arm64 (6.3.11-20230701-odroid) ...
update-initramfs: Generating /boot/initrd.img-6.3.11-arm64
Using DTB: amlogic/meson64_odroidn2_plus.dtb
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Installing new meson64_odroidn2_plus.dtb.
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Skipping backup of meson64_odroidn2_plus.dtb.
Installing new meson64_odroidn2_plus.dtb.
flash-kernel: deferring update (trigger activated)
Using DTB: amlogic/meson64_odroidn2_plus.dtb
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Skipping backup of meson64_odroidn2_plus.dtb.
Installing new meson64_odroidn2_plus.dtb.
Installing /usr/lib/linux-image-6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb into /boot/dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
Skipping backup of meson64_odroidn2_plus.dtb.
Installing new meson64_odroidn2_plus.dtb.
flash-kernel: deferring update (trigger activated)
Setting up isc-dhcp-common (4.4.1-2.3+deb11u2) ...
Setting up setup-odroid (0.0.1-79) ...

seeing this we know that the new Kernel was installed before setup-odroid was deployed which is responsible for setting up the script that handles the new Kernel Overlays in the correct layout.

Starting the script manually:

Code: Select all

/etc/kernel/postinst.d/copy-overlays 6.3.11-arm64

will solve this issue:

Code: Select all

root@odroid-bullseye64:~# tree /boot
/boot
├── boot.scr
├── config-6.1.0-arm64
├── config-6.3.11-arm64
├── config.ini
├── dtb -> dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
├── dtb-6.1.0-arm64 -> dtbs/6.1.0-arm64/amlogic/meson64_odroidn2_plus.dtb
├── dtb-6.3.11-arm64 -> dtbs/6.3.11-arm64/amlogic/meson64_odroidn2_plus.dtb
├── dtbs
│   ├── 6.1.0-arm64
│   │   ├── amlogic
│   │   │   ├── meson64_odroidc2.dtb
│   │   │   ├── meson64_odroidc4.dtb
│   │   │   ├── meson64_odroidhc4.dtb
│   │   │   ├── meson64_odroidn2.dtb
│   │   │   ├── meson64_odroidn2l.dtb
│   │   │   ├── meson64_odroidn2_plus.dtb
│   │   │   ├── meson-g12b-odroid-n2.dtb
│   │   │   ├── meson-g12b-odroid-n2l.dtb
│   │   │   ├── meson-g12b-odroid-n2-plus.dtb
│   │   │   ├── meson-gxbb-odroidc2.dtb
│   │   │   ├── meson-sm1-odroid-c4.dtb
│   │   │   ├── meson-sm1-odroid-hc4.dtb
│   │   │   └── overlays
│   │   │       ├── odroidc4
│   │   │       │   ├── display_vu7c.dtbo
│   │   │       │   ├── hifishield2.dtbo
│   │   │       │   ├── hktft32.dtbo
│   │   │       │   ├── hktft35.dtbo
│   │   │       │   ├── i2c0.dtbo
│   │   │       │   ├── i2c1.dtbo
│   │   │       │   ├── pcf8563.dtbo
│   │   │       │   ├── pps-gpio_p11.dtbo
│   │   │       │   ├── pps-gpio_p12.dtbo
│   │   │       │   ├── spi0.dtbo
│   │   │       │   ├── sx865x-i2c1.dtbo
│   │   │       │   ├── uart0.dtbo
│   │   │       │   ├── uart1.dtbo
│   │   │       │   ├── uart2.dtbo
│   │   │       │   ├── uart3.dtbo
│   │   │       │   ├── w1-gpio_p15.dtbo
│   │   │       │   └── w1-gpio_p22.dtbo
│   │   │       └── odroidn2
│   │   │           ├── fanspeed-full.dtbo
│   │   │           ├── hktft35.dtbo
│   │   │           ├── i2c0.dtbo
│   │   │           ├── i2c1.dtbo
│   │   │           ├── pps-gpio_p11.dtbo
│   │   │           ├── pps-gpio_p12.dtbo
│   │   │           ├── pwm_cd.dtbo
│   │   │           ├── pwm_ef.dtbo
│   │   │           ├── pwmfan-lowtemp.dtbo
│   │   │           ├── spi0.dtbo
│   │   │           ├── sx865x-i2c1.dtbo
│   │   │           ├── uart0.dtbo
│   │   │           ├── uart1.dtbo
│   │   │           ├── w1-gpio_p15.dtbo
│   │   │           └── w1-gpio_p22.dtbo
│   │   ├── meson64_odroidn2_plus.dtb -> amlogic/meson64_odroidn2_plus.dtb
│   │   ├── overlays
│   │   │   └── amlogic
│   │   │       └── odroidn2
│   │   │           ├── fanspeed-full.dtbo
│   │   │           ├── hktft35.dtbo
│   │   │           ├── i2c0.dtbo
│   │   │           ├── i2c1.dtbo
│   │   │           ├── pps-gpio_p11.dtbo
│   │   │           ├── pps-gpio_p12.dtbo
│   │   │           ├── pwm_cd.dtbo
│   │   │           ├── pwm_ef.dtbo
│   │   │           ├── pwmfan-lowtemp.dtbo
│   │   │           ├── spi0.dtbo
│   │   │           ├── sx865x-i2c1.dtbo
│   │   │           ├── uart0.dtbo
│   │   │           ├── uart1.dtbo
│   │   │           ├── w1-gpio_p15.dtbo
│   │   │           └── w1-gpio_p22.dtbo
│   │   ├── rk3399-odroid-n1.dtb -> rockchip/rk3399-odroid-n1.dtb
│   │   └── rockchip
│   │       ├── overlays
│   │       │   ├── odroidm1
│   │       │   │   ├── i2c0.dtbo
│   │       │   │   ├── i2c1.dtbo
│   │       │   │   ├── onewire.dtbo
│   │       │   │   ├── pwm1.dtbo
│   │       │   │   ├── pwm2.dtbo
│   │       │   │   ├── pwm9.dtbo
│   │       │   │   ├── spi0.dtbo
│   │       │   │   ├── uart0.dtbo
│   │       │   │   ├── uart0-with-ctsrts.dtbo
│   │       │   │   └── uart1.dtbo
│   │       │   ├── rockchip-dwc3-0-host.dtbo
│   │       │   ├── rockchip-i2c7.dtbo
│   │       │   ├── rockchip-i2c8.dtbo
│   │       │   ├── rockchip-pcie-gen2.dtbo
│   │       │   ├── rockchip-rk3328-opp-1.4ghz.dtbo
│   │       │   ├── rockchip-rk3328-opp-1.5ghz.dtbo
│   │       │   ├── rockchip-rk3399-opp-2ghz.dtbo
│   │       │   ├── rockchip-spi-jedec-nor.dtbo
│   │       │   ├── rockchip-spi-spidev.dtbo
│   │       │   ├── rockchip-uart4.dtbo
│   │       │   └── rockchip-w1-gpio.dtbo
│   │       ├── rk3326-odroid-go2.dtb
│   │       ├── rk3399-odroid-n1.dtb
│   │       └── rk3568-odroid-m1.dtb
│   └── 6.3.11-arm64
│       ├── amlogic
│       │   ├── meson64_odroidn2_plus.dtb
│       │   └── odroidn2
│       │       ├── fanspeed-full.dtbo
│       │       ├── hktft35.dtbo
│       │       ├── i2c0.dtbo
│       │       ├── i2c1.dtbo
│       │       ├── pps-gpio_p11.dtbo
│       │       ├── pps-gpio_p12.dtbo
│       │       ├── pwm_cd.dtbo
│       │       ├── pwm_ef.dtbo
│       │       ├── pwmfan-lowtemp.dtbo
│       │       ├── spi0.dtbo
│       │       ├── sx865x-i2c1.dtbo
│       │       ├── uart0.dtbo
│       │       ├── uart1.dtbo
│       │       ├── w1-gpio_p15.dtbo
│       │       └── w1-gpio_p22.dtbo
│       ├── meson64_odroidn2_plus.dtb -> amlogic/meson64_odroidn2_plus.dtb
│       └── overlays
│           └── amlogic
│               └── odroidn2
│                   ├── fanspeed-full.dtbo
│                   ├── hktft35.dtbo
│                   ├── i2c0.dtbo
│                   ├── i2c1.dtbo
│                   ├── pps-gpio_p11.dtbo
│                   ├── pps-gpio_p12.dtbo
│                   ├── pwm_cd.dtbo
│                   ├── pwm_ef.dtbo
│                   ├── pwmfan-lowtemp.dtbo
│                   ├── spi0.dtbo
│                   ├── sx865x-i2c1.dtbo
│                   ├── uart0.dtbo
│                   ├── uart1.dtbo
│                   ├── w1-gpio_p15.dtbo
│                   └── w1-gpio_p22.dtbo
├── initrd.img-6.1.0-arm64
├── initrd.img-6.3.11-arm64
├── lost+found
├── System.map-6.1.0-arm64
├── System.map-6.3.11-arm64
├── vmlinuz-6.1.0-arm64
└── vmlinuz-6.3.11-arm64

19 directories, 130 files

We can now see that the folder structure is in the correct layout.
Also we know that it was just an order issue, which means that every future update of a Kernel will work as expected without manual intervention.

Of cause this can be prevented all together by updating setup-odroid before installing a new Kernel (which sadly doesn't happen during normal update procedure)

I will check if I can update the logic of the script to make sure when setup-odroid is installed it will trigger the script for all installed Kernel, not just for the currently running Kernel.

[jvanveen]

I've tried the image with an Odroid N2L and the ODroid wifi adapter, but don't see the wifi adapter listed (ip a).
My interfaces file:

Code: Select all

auto wlan0
iface wlan0 inet dhcp
    wpa_essid <SSID>
    wpa-psk <PWD>

Does it need separate firmware installed, or did I forgot something?

[meveric]

may depend on the WLAN adapter you're using some of them may not yet been activated in the kernel or may require a DKMS driver to be installed to work properly.

If the device is not shown when you type "ip a" even without an IP that means the hardware is not activated.
You should check the output of dmesg or /var/log/syslog and check if it complains about missing firmware or drivers.

[Nitpicking]

Using an N2+, it refuses to connect to a network in any way. I do not have an Ethernet network set up, so it's wireless or nothing.

If I plug in the Odroid USB Wifi dongle, it detects it as a Bluetooth adapter, but not WiFi. No 802.11 driver loads and wlan0 never exists.

I have two other USB dongles, both Realtek. However, they do the same thing, never being detected as wireless adapters. I downloaded the firmware-realtek package and transferred it over using a thumb drive, but that changed nothing.

I tried to use my Android phone's USB tethering function. When the phone connects, it is detected and correctly identified. I'm going to have to retype the log messages, since this thing won't network:

Code: Select all

rndis_host 1-1.3:1.0 usb1: register 'rndis_host' at usb-xhci-hd.0.auto-1.2 RNDIS device, 4e:03:06:96:33:b7
Using default interface naming scheme 'v247'.
ethtool: autonegotiation is unset or enabled, the speed and duplex are not writeable.

What? I know you didn't write it, but that last message is so cryptic Bletchley Park would struggle. Anyway, wlan0 does not appear.

So ... what the heck? Any suggestions?

[meveric]

seems like you using a the module, that combines WLAN + Bluetooth?
Those often require a modeswitch to work, as WLAN is not activated by default. There are tools like usb-modeswitch which can switch between modes automatically if configured correctly.

I'd first try with WiFi modules that do not combine Bluetooth + WLAN as they probably have more chances to work.

Check the output of dmesg -w. What happens if you plug in the USB adapter?
It will tell you if something is missing like firmware for example.
firmware-realtek should be preinstalled if I remember correctly.

[Nitpicking]

As I mentioned, I did try two other USB-to-WiFi adapters, which were simply not detected. I only have the three. The one that is detected is the official one from Hardkernel. Note that the Ubuntu distro supplied directly by Hardkernel works flawlessly with the HK adapter. I'll reboot the thing into Debian after work today and try your suggestions.

[Nitpicking]

Two attachments. syslog.bullseye was made using the Debian image, and syslog.ubuntu using the Ubuntu Bookworm image supplied by Hardkernel, which I thought might be helpful for you in figuring out the Debian issue. Note that the first device inserted on Bullseye is the Odroid-specific USB dongle, and the other one is a literal $4.00 802.11N device I bought on Wish.com, which works great under Ubuntu and is giving the max speed of the local access point (which is not N).

[meveric]

Sadly the debian bullseye syslog is not very helpful, as you cut it off where the important part would start.
We only see that it finds the hardware itself correctly, but what happens afterwards is cut off.

In the ubuntu log you kept this, and I can see that the first USB is one of the combo ones I was talking about they come with bluetooth and wlan and often require a config to activate the WLAN part.
You can see that it's loading realtek firmware for bluetooth and then activated the wlan part. Sadly as I said, that part is completely missing in the cut off version of the debian log file, so I can not compare.
I think I should have the same model laying around here so I will check if I can find out more.

The second one I can't see much about it. It's found and just starts, can't see if it's loading any firmware or driver. Still it's also Realtek. I can check if the device itself is activated in the kernel, maybe the realtek module for this particular WLAN module is not yet build so activating it in Kernel would be required, but it also requires you to update via apt to get new driver support, hence you need internet access before you can activate wlan for internet access, which could be somewhat hard I understand.

[Nitpicking]

I did try to get networking going using USB tethering with my phone, but that also failed (as mentioned above).

[meveric]

Interesting, as I tried this several times in the past and it was working fine.
I see what I can find, especially the USB tethering is a bit surprising for me.

[Nitpicking]

I will be out of town for the next week, so there will be a delay in my responding. (I'm not bringing the Odroid board.)

[meveric]

I checked on the devices you have again and the first one from HardKernel the one with WLAN and Bluetooth I'm actually using myself, both WLAN and Bluetooth at the same time, so I know it's working.
I can see it's not working out of the box, but if I check what you need for that.
I know it works just fine after you do a normal system update, but since you don't have working network setup I'll try what's are the minimal packages you need.

[meveric]

Ok I checked and it seems just a Kernel update is needed to get it working.
In the Kernel 6.1.0 which came original with the image, the drivers for the WiFi Module from hardkernel were not yet included.
You can manually download https://oph.mdrjr.net/meveric/pool/main ... _arm64.deb put it on an USB drive and transfer it to the ODROID then use:

Code: Select all

dpkg -i linux-image-6.3.11-arm64_6.3.11-20230701-odroid_arm64.deb

to install the file and after a reboot the system should work fine with WiFi available.