[OS] Debian Bullseye (11) N2/N2L

[meveric]

This is my version of Debian Bullseye (11) for the ODROID N2/N2Plus/N2L

I've been working on this and other images on and off, and finally I got around to getting the finishing touches on this image.

It uses Kernel 6.1.0 at the moment, but will get updates as usual from my repository.

It's a headless server image only with user root. But it has all my repositories included, which allows for easy installation and updates of packages such as Kernel and Headers and other packages.

The image has my usual setup: means on first boot it's resizing the rootfs partition and configures SSH. It will automatically reboot after the initial setup after which this image is ready to use.
Kernel and headers are already installed if you need to build your own drivers.
A few basic tools such as htop, mc, vim and bash-completion are already installed for your convenience.


Download N2: https://oph.mdrjr.net/meveric/images/Bu ... -N2.img.xz md5 sha512 sig

Download N2L: https://oph.mdrjr.net/meveric/images/Bu ... N2L.img.xz md5 sha512 sig

Size compressed: 165MiB
Size uncompressed: 1.3GiB

Default Login: root
Default Password: odroid

It's ready to be used as a server image.

Features:

• Debian Bullseye (11) debootstrap image (minimal OS)
• upstream u-boot 2022-10
• upstream Kernel (6.1.0)
• ext4 partitions for both bootfs and rootfs
• unified flash-kernel config (should be fitting for all ODROID arm64 boards)
• uses opensource drivers for GPU/VPU (Panfrost / meson-vdec)
• device-tree-overlay support via config.ini
• OpenGL 2.1/3.1 and OpenGL ES 2.0/3.1 support for Mali-G52 GPU (depending on MESA version)
  

First things first:
Since there's constantly new development for this image and ODROIDs in general the First thing you should do after the image is up and running is to install all updates:

Code: Select all

apt update && apt upgrade && apt dist-upgrade

How to convert the image into a Desktop image:
The image can easily converted into a Desktop image looking similar to this:


I created a setup tool that's already preinstalled:

Code: Select all

setup-odroid

Which should easily allow you to install a Desktop Environment.
Wayland desktop is also supported:


Hints:
Changing language:
If you install a Desktop environment you should already have keybord-configuration installed, it will ask upon the first installation what keyboard layout it should use.
This configuration is for your X11 Desktop so you have your desired keyboard layout.
For console you need to install console-setup to do the same, so just in case:

Code: Select all

apt install console-setup keyboard-configuration
dpkg-reconfigure keyboard-configuration

should be all that is needed to change your keyboard layout.
You probably want to set timezone as well

Code: Select all

dpkg-reconfigure tzdata

Device-Tree-Overlays:
Device-Tree-Overlays are supported by the image and handled in the config.ini on /boot/
Here you can activate overlays to support additional hardware such as 3.5" display, or RTC.
You can add multiple overlays at once, just check the description in the config.ini file.
Please Note: By default RTC is not activated on the board and in order to use it you need to activate the i2c1 overlay which is connected to the RTC.

Setting up WLAN from command line:
Edit the file /etc/network/interfaces or create a new one under /etc/network/interfaces.d/ and add the following lines

Code: Select all

auto wlan0
iface wlan0 inet dhcp
    wpa-essid <NAME-OF-YOUR-WLAN>
    wpa-psk <WLAN-PASSWORD>

If you're using a "hidden" network, please also add wpa-scan-ssid 1

Webbrowser:
Hardware accelerated web-browsing is possible both via Chromium WebBrowser as well as FireFox (version 91 or higher), but only with backport MESA drivers (MESA 21 or higher).
WebGL is also supported the same way:


Sadly due to the fact that GPU drivers are still somewhat in an experimental state, chromium may show some graphical glitches, especially under X11, therefore FireFox might be the better choice.
Starting Chromium with --disable-gpu-rasterization can resolve some of the issues.
Youtube playback in 1080p should be fine, even 1440p should work in some cases.

Video Playback
While Kodi can be installed and runs both from X11 desktop as well as directly from terminal (GBM). It does not support hardware accelerated video playback.
Still since the CPU is very strong you can run Kodi to watch most videos in up to 1080p without much issues in Kodi software decoded.
If you install a desktop via setup-odroid I opted for installing mpv as a video player which will support hardware accelerated video decoding of H264/MP4 files.

The totem video player does also support hardware accelerated video decoding but will show more artifacts.

Known Issues:
H265 decoding should work with up to 1080p, 4k does not work.

SPI boot is currently not supported, as the image comes with it's own u-boot and configs which do not work with petitboot.

As usual feedback is welcome.

[mad_ady]

Regarding SPI boot - does mainline kernel offer any features that HK doesn't and are needed to boot the kernel?

[meveric]

Regarding SPI boot - does mainline kernel offer any features that HK doesn't and are needed to boot the kernel?

does the Kernel offer feature to boot the Kernel?
I guess you mean u-boot?

No the Kernel itself would run fine, but DTBO is really hard to handle on the older u-boot I had trouble running fdt addr command which would always fail stating, I need to run fdt addr befor I can run other fdt commands

Feature wise the newer u-boot has a couple more things it can offer, for example extlinux/syslinux support, something similar to grub, or EFI support.
Are they required? Probably not, but it makes certain things easier, everything is unified, which allows me to have one bootscript for all boards.

In fact, technically you could take this image, flash an u-boot from the ODROID C2 on it, and the image will work just the same, flash a u-boot of the C4 (next image that will be released) and the image should work just the same.
Same goes for ODROID N1, flash u-boot and done. I assume, the image actually works on many more boards, as long as they use a similar u-boot, all important parts are already part of the image and it would work out of the box or with minor adaptations.

[hatsu]

Hi @meveric,

Known Issues:
The Panfrost GPU drivers are not yet completely working yet, while most things work there are some issues with the drivers, especially with OpenGL ES support.
When you start glmark2-es2 the benchmark will crash eventually due to driver issues.

glmark2 version 2014-3 does have issue with the later mesa 21 where it will crash but if you update to glmark2 from debian unstable branch (glmark2-es2-x11/unstable,now 2021.10~git.e359bb0-2 arm64) it will work.

Chromium stable 90.0.4430.212-1 also does not allow you to login to Gmail (Not supported or security issue). With chromium-browser 1:97.0.4692.20-0ubuntu1~ppa2~20.04.1 from https://launchpad.net/~saiarcot895/+arc ... omium-beta, --use-gl=egl works and works with --ozone-platform=wayland but have a lot of error message (command line launch chromium) but does not crash so far and No issue with Gmail.

In Xorg session with your kernel 5.15.10-arm64 without the Amlogic HWCursor patch the mouse pointer/cursor does flicker at times (not all the time). With your earlier kernel 5.15.7-arm64 (Dec 08 version) with HWCursor patch, no mouse pointer/cursor flickering in Xorg.

[mad_ady]

I guess you mean u-boot?

Yes, my bad.

So, based on your explanation, there is no reason why it wouldn't boot from petitboot via kexec, right?

[tobetter]

I guess you mean u-boot?

Yes, my bad.

So, based on your explanation, there is no reason why it wouldn't boot from petitboot via kexec, right?

Not really, since I found a bug in Petitboot...so it's my bad...

I've tested the boot script in @meveric's Debian image and it requires a bit of change like below, I thinks this change will also work with the upstream U-Boot as well. The thing is I need to improve Petitboot to read the boot script and I've done a bit in a hour, and...need some test later.

Code: Select all

--- boot.cmd.orig	2021-12-22 14:56:15.000000000 +0900
+++ boot.cmd	2021-12-22 19:08:36.000000000 +0900
@@ -2,6 +2,8 @@
 # flash-kernel: bootscr.odroid64
 #
 
+setenv bootlabel "Debian Bullseye (11)"
+
 # legacy support
 if test -z "${scriptaddr}"; then
   setenv scriptaddr ${loadaddr}
@@ -22,7 +24,7 @@
 if test -z "${rootfs}"; then
   setenv rootfs "UUID=e139ce78-9841-40fe-8823-96a304a09859"
 fi
--
+
 # ethernet MAC address
 if test -n "${ethermac}"; then
   setenv ethaddr "${ethermac}"
@@ -73,6 +75,8 @@
 	fi
 fi
 
+fdt addr ${fdt_addr_r}
+
 # load overlays on C4/N2 variants only
 if test -n "${variant}"; then
   run fk_fdt_cmd

[meveric]

I can easily add the changes suggested no big deal
Although fdt addr ${fdt_addr_r} is already part of the load_overlays_cmd, as it's technically only needed here.
Although most likely this won't work anyway as DTBO is different in u-boot 2015 used in SPI/petitboot and the upsteam one.
I probably have to check again if this works at all, and add more legacy definition for the older u-boot variants to make this work.

Also thanks for finding that "-" in line 22 that one was bugging me the entire time and I couldn't find it

Edit:
meh... there are so many things broken with the stock SPI boot.
no config parameter for the device tree file or path is passed to petitboot.
no official dtbo addresss is defined
no variant to verify if it's n2 or n2plus.
Such a pain to work with this -.-
And yes I guess updating SPI may fix this, but if you have to update the SPI to get an image to work at all, it's somewhat a pain in the a**.

[olco]

Is this build already stable?

I have to set up my odroid with a new OS and I thought I might as well install bullseye instead of buster.

So far everything I installed worked well but I was wondering, why there were only the folder scripts and resize--log.txt shown in root?

[meveric]

Is this build already stable?

It's as stable as currently possible.
The OS itself is stable, the Panfrost GPU drivers not as much yet.
Although by default you'll have MESA 20.3.5 installed which works fine but is limited to OpenGL 2.1 and OpenGL ES 2.0.
So you trading speed and features for stability, but you could update to newer MESA which has more features but may not be as stable.

So far everything I installed worked well but I was wondering, why there were only the folder scripts and resize--log.txt shown in root?

What else do you need in the root folder?
That's all there is by default.

[olco]

I guess I am still quite a newbe when If comes to Linux.
I created folders like /data in root and was wondering, why these weren't shown, too.
Although they are accessable.

[mad_ady]

/data was created in filesystem root (/), not in /root that is root's home directory

[olco]

Okay, the build I used before (buster) had the User odroid also created automatically, so I did most tasks via that user.
Now I thought I would just use root instead for setting everything up and create an odroid user later, but maybe that let to my confusion.

[meveric]

Okay, the build I used before (buster) had the User odroid also created automatically, so I did most tasks via that user.

No, the buster build also only comes with the user root.
But when you install a desktop it will recommend to setup a new user as well, and guides you to the process of creating a new user.
But the Buster image also only has the user root by default.

Now I thought I would just use root instead for setting everything up and create an odroid user later, but maybe that let to my confusion.

The images are both pretty much identical, Buster and Bullseye both have the same tools pre-installed and the same settings.
Everything you did to prepare the Buster image should work the same here on the Bullseye image.
Only difference is that instead of using closed source Mali GPU drivers it uses the open source MESA GPU drivers and has a newer Kernel that supports this.

[olco]

I guess I am remembering thus wrong then, thought I also had to activate ssh and so on.

Nevertheless, thanks for the explanation

Edit:
Before on buster Installed all applications directly.
Now I like to Install all as docker containers.

So before installing wireguard as docker
https://hub.docker.com/r/linuxserver/wireguard
Do I have to enable the kernels wireguard module first or is it already in your build?

[meveric]

wireguard is available as a kernel module:

Code: Select all

$ modinfo wireguard
filename:       /lib/modules/5.15.10-arm64/kernel/drivers/net/wireguard/wireguard.ko
alias:          net-pf-16-proto-16-family-wireguard
alias:          rtnl-link-wireguard
version:        1.0.0
author:         Jason A. Donenfeld <Jason@zx2c4.com>
description:    WireGuard secure network tunnel
license:        GPL v2
srcversion:     944997E03CEE8D079C6B997
depends:        libcurve25519-generic,ipv6,libblake2s,udp_tunnel,libchacha20poly1305,ip6_udp_tunnel
intree:         Y
name:           wireguard
vermagic:       5.15.10-arm64 SMP preempt mod_unload aarch64

[Gburas]

i have moved our conversation here since it`s about debian 11

after i try to move to hdd it fails (i think so):

Code: Select all

root@odroid-bullseye64:/mnt# lsblk -f
NAME         FSTYPE      FSVER    LABEL  UUID                                   FSAVAIL FSUSE% MOUNTPOINT
sda
└─sda1       LVM2_member LVM2 001        DxO3GV-iagb-Y34f-Si2j-0yfK-Bmed-08i0Tu
  └─hdd-root ext4        1.0             58092e3f-7b01-40c1-89f7-78b979733565
mmcblk0
├─mmcblk0p1  ext4        1.0      boot   c07a1d9a-071f-45a9-abdd-4f145c8dd72e    385.9M    13% /boot
└─mmcblk0p2  ext4        1.0      rootfs e139ce78-9841-40fe-8823-96a304a09859      5.7G    13% /
mmcblk0boot0
mmcblk0boot1

[Gburas]

I figured out how to mount this volume, it turns out that the files was there already. So I tried to modify boot.scr and fstab, but i bricked it. So i start over again. But after clean flashing is the same: (i think) it creates the volume, copy files and that's all.

Wysłane z mojego AC2003 przy użyciu Tapatalka

[mad_ady]

You're not supposed to edit boot.scr. You should regenerate it if needed from boot.txt

[Gburas]

You're not supposed to edit boot.scr. You should regenerate it if needed from boot.txt

I guess it's not that easy, but as I said before I'm still noob and i'm not afraid of "trials and mistakes"

The funny part is that my heating system depends on odroid

Wysłane z mojego AC2003 przy użyciu Tapatalka

[mad_ady]

<offtopic>

The funny part is that my heating system depends on odroid

Mine too. That's why, when my C2 crashed years ago it left the heater running all night so we woke up sweating... Could have been worse!
</offtopic>

I think you need to run flash-kernel after editing /boot/boot.txt to regenerate boot.scr. Details here: http://docs.linuxfactory.or.kr/guides/c ... ernel.html

[meveric]

There is no boot.txt on the image but under /boot you'll find a config.ini where you can define the rootfs.

Code: Select all

; location of root filesystem (e.g. /dev/mmcblk1p2 or UUID=560b0c5e-cc70-46e6-a38a-d7ab766e01c7)
; rootfs="UUID=e139ce78-9841-40fe-8823-96a304a09859"

just uncomment the line with rootfs="UUID=e139ce78-9841-40fe-8823-96a304a09859"
and change e139ce78-9841-40fe-8823-96a304a09859 to 58092e3f-7b01-40c1-89f7-78b979733565
This is all that should be needed.
The boot.scr doesn't need to be touched, it imports config.ini where you can make changes.

Sadly I haven't had much time for testing hdd installation on Bullseye yet, as the process change quite a bit compared to older Kernel where you had to alter boot.ini instead.
And I've reworked the boot.scr flash-kernel and config.ini what feels like 100 times, so the process was not completed at the time when I had hdd install activated for this image.

[Gburas]

What changes should i make to fstab?

Wysłane z mojego AC2003 przy użyciu Tapatalka

[meveric]

What changes should i make to fstab?

Pretty much the same, make sure that:

Code: Select all

UUID=e139ce78-9841-40fe-8823-96a304a09859       /       ext4    errors=remount-ro,noatime,discard       0       1

is changed to:

Code: Select all

UUID=58092e3f-7b01-40c1-89f7-78b979733565       /       ext4    errors=remount-ro,noatime,discard       0       1

That's all.
The fstab only needs to be changed on the harddrive not on the eMMC as that rootfs is no longer used.

[Gburas]

can i delate data on emmc after all that proces to not mess for me? of course without boot folder

[Gburas]

ok, i have made all those changes, and it reboot successful (hurra) but still i`m not sure which files it using? how i can check this?

[Gburas]

update:
system booted but mounting was lost so i mounted again:

Code: Select all

Last login: Tue Jan  4 19:57:58 2022 from 192.168.0.116
root@odroid-bullseye64:~# ls
resize--log.txt  scripts
root@odroid-bullseye64:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.8G     0  1.8G   0% /dev
tmpfs           381M  816K  380M   1% /run
/dev/mmcblk0p2  6.6G  842M  5.8G  13% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/mmcblk0p1  483M   61M  386M  14% /boot
root@odroid-bullseye64:~# mount /dev/hdd/root /mnt/ssd
root@odroid-bullseye64:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                  1.8G     0  1.8G   0% /dev
tmpfs                 381M  812K  380M   1% /run
/dev/mmcblk0p2        6.6G  842M  5.8G  13% /
tmpfs                 1.9G     0  1.9G   0% /dev/shm
tmpfs                 5.0M  4.0K  5.0M   1% /run/lock
/dev/mmcblk0p1        483M   61M  386M  14% /boot
/dev/mapper/hdd-root  459G  940M  435G   1% /mnt/ssd

and i edited fstab on emmc to be same as lvm and unfortunately that bricked again :/

[meveric]

can i delate data on emmc after all that proces to not mess for me? of course without boot folder

If everything is copied then yes, you can remove /dev/mmcblk0p2 which is the old rootfs on the eMMC

ok, i have made all those changes, and it reboot successful (hurra) but still i`m not sure which files it using? how i can check this?

if you type "mount" as a command it should show you where things are mounted.
And /dev/mapper/hdd-root
or /dev/hdd/root should be mounted as "/" (root)

update:
system booted but mounting was lost so i mounted again:

Code: Select all

Last login: Tue Jan  4 19:57:58 2022 from 192.168.0.116
root@odroid-bullseye64:~# ls
resize--log.txt  scripts
root@odroid-bullseye64:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.8G     0  1.8G   0% /dev
tmpfs           381M  816K  380M   1% /run
/dev/mmcblk0p2  6.6G  842M  5.8G  13% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/mmcblk0p1  483M   61M  386M  14% /boot

Yes this means it used eMMC as root as you can see here:

Code: Select all

/dev/mmcblk0p2  6.6G  842M  5.8G  13% /

and i edited fstab on emmc to be same as lvm and unfortunately that bricked again :/

eMMC should not matter when the boot script loads the rootfs, it should load the hdd and not eMMC therefore whatever you change on the eMMC rootfs, does have no affect on the boot from HDD.

Since the system was mounted with

Code: Select all

/dev/mmcblk0p2  6.6G  842M  5.8G  13% /

That means to boot was not correct.
Can you show me the output of /boot/boot.scr and /boot/config.ini?
Let's see if the files are correct.

[Gburas]

/boot/boot.scr

Code: Select all

'VU\8D\89+a\D4[L\00\00\A8\00\00\00\00\00\00\00\00\93\AD\BC\91\00boot script\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\A0\00\00\00\00

#

# flash-kernel: bootscr.odroid64

#



# legacy support

if test -z "${scriptaddr}"; then

  setenv scriptaddr ${loadaddr}

fi

if test -n "${fdt_high}"; then

  setenv fdt_addr_r ${fdt_high}

fi



# try loading user config

if load ${devtype} ${devnum}:${partition} ${scriptaddr} ${prefix}config.ini; then

  env import -t ${scriptaddr}

fi



if test -z "${fk_kvers}"; then

  setenv fk_kvers '5.15.10-arm64'

fi



if test -z "${rootfs}"; then

  setenv rootfs "UUID=e139ce78-9841-40fe-8823-96a304a09859"

fi

-

# ethernet MAC address

if test -n "${ethermac}"; then

  setenv ethaddr "${ethermac}"

fi



# different console for AmLogic devices

if test "${soc}" = "meson"; then

  setenv console "ttyAML0,115200n8"

  # ODROID C2

  if test "${board}" = "p200"; then

    setenv usbcore "usbcore.autosuspend=-1"

  fi

  # C4/N2 only

  if test -n "${variant}"; then

    echo "variant ${variant}"

    if test "$variant" = "n2-plus"; then

        setenv variant "n2_plus"

    fi

    if test "$board" = "odroid-n2"; then

	setenv overlaypath "odroidn2"

    else

	setenv overlaypath "odroidc4"

    fi

    setenv fdtfile "amlogic/meson64_odroid${variant}.dtb"

    # overlay support currently only working with upstream

    setenv load_overlay_cmd 'echo loading overlay ${overlay}; fdt resize 8192; if load ${devtype} ${devnum}:${partition} ${fdtoverlay_addr_r} dtbs/${fk_kvers}/amlogic/${overlaypath}/${overlay}.dtbo; then fdt apply ${fdtoverlay_addr_r}; fi'

    setenv load_overlays_cmd 'fdt addr ${fdt_addr_r}; for overlay in ${fk_overlays}; do run load_overlay_cmd; done'

    setenv restore_fdt_cmd 'echo "error loading overlays, using untouched dtb" && load ${devtype} ${devnum}:${partition} ${fdt_addr_r} ${fdtpath}/${fdtfile}'

    setenv fk_fdt_cmd 'if test -n "${fk_overlays}"; then echo "loading overlays ${fk_overlays}"; run load_overlays_cmd || run restore_fdt_cmd; else true; fi'

  fi

else

  setenv console "ttyS2,115200n8"

fi





setenv bootargs " root=${rootfs} console=${console} console=tty0 net.ifnames=0 fsck.mode=auto fsck.repair=yes rootwait ro earlycon clk_ignore_unused no_console_suspend maxcpus=${maxcpus} ${usbcore} ${videoconfig}"



setenv fdtpath "/usr/lib/linux-image-${fk_kvers}"

if load ${devtype} ${devnum}:2 ${fdt_addr_r} ${fdtpath}/${fdtfile}; then 

	echo "loaded FDT from ${fdtpath}/${fdtfile}"

else

	setenv fdtpath "dtbs/${fk_kvers}"

	if load ${devtype} ${devnum}:${partition} ${fdt_addr_r} ${fdtpath}/${fdtfile}; then

		echo "loaded FDT from ${fdtpath}/${fdtfile}"

	else

		load ${devtype} ${devnum}:${partition} ${fdt_addr_r} dtb

		echo "loaded FDT from /dtb"

	fi

fi



# load overlays on C4/N2 variants only

if test -n "${variant}"; then

  run fk_fdt_cmd

fi



load ${devtype} ${devnum}:${partition} ${kernel_addr_r} ${prefix}vmlinuz-${fk_kvers}

load ${devtype} ${devnum}:${partition} ${ramdisk_addr_r} ${prefix}initrd.img-${fk_kvers}

echo "Booting Debian ${fk_kvers} from ${devtype} ${devnum}:${partition}..."

booti ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}

config.ini

Code: Select all

; Set ethernet adapter MAC address (where supported)

; ethermac=aa:bb:cc:dd:ee:ff



; overwrite Kernel version to be loaded

; fk_kvers="5.13.4-arm64"



; Maximum number of CPU cores 1..4

; maxcpus=4



; location of root filesystem (e.g. /dev/mmcblk1p2 or UUID=560b0c5e-cc70-46e6-a38a-d7ab766e01c7)

rootfs="UUID=3924ee0c-580f-4762-b697-315999ed15e2"



; Device Tree Overlay (ODROID C4/N2 only)

; some available overlays hktft32 hktft35 pcf8563 spi0 sx865x-i2c1 w1-gpio_p15 w1-gpio_p22 uart0 uart1

; check /usr/lib/linux-image-<Kernel-version>/amlogic/overlays for full list

; fk_overlays=spi0 pcf8563 sx865x-i2c1



; Video Resolution

; You can specifiy a desired resolution

; Please note: this only applies to framebuffer and may be overwritten from a Desktop that you have installed

; https://www.kernel.org/doc/Documentation/fb/modedb.txt

; examples:

; ODROID-VU forced resolution

; videoconfig="video=HDMI-A-1:1280x800@60"

; -----------------------------------------------

; ODROID-VU forced EDID

; videoconfig="drm.edid_firmware=edid/1280x800.bin"

; -----------------------------------------------

; 1920x1080 (1080P) with monitor provided EDID information. (1080p-edid)

; videoconfig="video=HDMI-A-1:1920x1080@60"

; -----------------------------------------------

; 1920x1080 (1080P) without monitor data using generic information (1080p-noedid)

; videoconfig="drm.edid_firmware=edid/1920x1080.bin"

; -----------------------------------------------

; 1920x1080 50hz (1080P) with monitor provided EDID information. (1080p 50hz-edid)

; videoconfig="video=HDMI-A-1:1920x1080@50"

; -----------------------------------------------

; 1920x1080 50hz (1080P) without monitor data using generic information (1080p 50hz-noedid)

; videoconfig="drm.edid_firmware=edid/1920x1080_50hz.bin"

; -----------------------------------------------

; 1440x900 with monitor provided EDID information.

; videoconfig="video=HDMI-A-1:1440x900@60"

; -----------------------------------------------

; 1440x900 without monitor data using generic information 

; videoconfig="drm.edid_firmware=edid/1440x900.bin"

; -----------------------------------------------

; 1280x1024 without monitor data using generic information

; videoconfig="drm.edid_firmware=edid/1280x1024.bin"

; -----------------------------------------------

; 1280x720 (720P) with monitor provided EDID information. (720p-edid)

; videoconfig="video=HDMI-A-1:1280x720@60"

; -----------------------------------------------

; 1280x720 (720P) without monitor data using generic information (720p-noedid)

; videoconfig="drm.edid_firmware=edid/1280x720.bin"

; -----------------------------------------------

; 1024x768 without monitor data using generic information

; videoconfig="drm.edid_firmware=edid/1024x768.bin"

; -----------------------------------------------

; 1024x600 without monitor data using generic information (ODROID VU7+)

; videoconfig="drm.edid_firmware=edid/1024x600.bin"

; -----------------------------------------------

; 800x600 without monitor data using generic information 

; videoconfig="drm.edid_firmware=edid/800x600.bin"

; -----------------------------------------------

; 800x480 without monitor data using generic information (ODROID 7")

; videoconfig="drm.edid_firmware=edid/800x480.bin"

; -----------------------------------------------

; 720x576 without monitor data using generic information 

; videoconfig="drm.edid_firmware=edid/720x576.bin"

; -----------------------------------------------

; 720x480 without monitor data using generic information 

; videoconfig="drm.edid_firmware=edid/720x480.bin"

; -----------------------------------------------

; 640x480 without monitor data using generic information

; videoconfig="drm.edid_firmware=edid/640x480.bin"

[meveric]

both look fine, although it seems your UUID changed compared to what you send earlier.

What happens when you boot it?
Does it mount eMMC again?

If so can you mount the hdd to mnt again check what is on that /etc/fstab?
Cause that is the important one.

[Gburas]

yes as i wrote before system bricked (won`t start) and i do it all over again

as i wrote before i did mount it again and changed fstab on mmc to uuid of my drive, previously when i opened fstab on LVM it already had good uuid (what was weird for me), now system don`t start (i can`t connect with putty as i use it headless), i can only read fstab from mmc on another machine but it was same as in lvm

Code: Select all

UUID=3924ee0c-580f-4762-b697-315999ed15e2       /       ext4    errors=remount-ro,noatime,discard       0       1

UUID=c07a1d9a-071f-45a9-abdd-4f145c8dd72e	/boot	ext4	errors=remount-ro,noatime,discard	0	0

[meveric]

hmm that's kinda odd, as I use the same on my ODROID N1 and it' working fine here.

Do you have a UART for debugging?

You can also try to replace UUID=3924ee0c-580f-4762-b697-315999ed15e2 with /dev/mapper/hdd-root
This should work as well, both for config.ini as well as fstab.

[Gburas]

i have replace uuid with path and odroid-n2 booted, but it looks like no changes at all (weird)
maybe i do something wrong with mount?

Code: Select all

Last login: Tue Jan  4 20:19:45 2022 from 192.168.0.116
root@odroid-bullseye64:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            1.8G     0  1.8G   0% /dev
tmpfs           381M  812K  380M   1% /run
/dev/mmcblk0p2  6.6G  858M  5.8G  13% /
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/mmcblk0p1  483M   61M  386M  14% /boot
root@odroid-bullseye64:~# lsblk -f
NAME         FSTYPE      FSVER    LABEL  UUID                                   FSAVAIL FSUSE% MOUNTPOINT
sda
└─sda1       LVM2_member LVM2 001        U6WOMB-ddGC-VdF8-PXfo-yanl-EiwX-PAVL50
  └─hdd-root ext4        1.0             3924ee0c-580f-4762-b697-315999ed15e2
mmcblk0
├─mmcblk0p1  ext4        1.0      boot   c07a1d9a-071f-45a9-abdd-4f145c8dd72e    385.9M    13% /boot
└─mmcblk0p2  ext4        1.0      rootfs e139ce78-9841-40fe-8823-96a304a09859      5.7G    13% /
mmcblk0boot0
mmcblk0boot1
root@odroid-bullseye64:~# lvdisplay
  --- Logical volume ---
  LV Path                /dev/hdd/root
  LV Name                root
  VG Name                hdd
  LV UUID                Fm82o0-j4ZN-Ysof-loZC-B1vV-VH5U-X4fKk4
  LV Write Access        read/write
  LV Creation host, time odroid-bullseye64, 2022-01-04 14:36:13 +0000
  LV Status              available
  # open                 0
  LV Size                <465.76 GiB
  Current LE             119234
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0

[olco]

wireguard is available as a kernel module:

Code: Select all

$ modinfo wireguard
filename:       /lib/modules/5.15.10-arm64/kernel/drivers/net/wireguard/wireguard.ko
alias:          net-pf-16-proto-16-family-wireguard
alias:          rtnl-link-wireguard
version:        1.0.0
author:         Jason A. Donenfeld <Jason@zx2c4.com>
description:    WireGuard secure network tunnel
license:        GPL v2
srcversion:     944997E03CEE8D079C6B997
depends:        libcurve25519-generic,ipv6,libblake2s,udp_tunnel,libchacha20poly1305,ip6_udp_tunnel
intree:         Y
name:           wireguard
vermagic:       5.15.10-arm64 SMP preempt mod_unload aarch64

Wireguard container works fine!

[Gburas]

Ok so i probably found cause of the problem, i think the SSD drive is up to late. I was wondering why mounting isn't permanent, and after reboot the LVM was unmounted. I read somewhere that maybe place where i mount is bad so i start testing that theory and it finds out that the LVM Partition was unavailable just after boot and it came up right after. ( I connected odroid to Tv and also messages mix with terminal, also weird but help to understand that there is problem with external drive). General SSD should be ok, it worked also as roots on xu4 on Yours image.

Any ideas?

Wysłane z mojego AC2003 przy użyciu Tapatalka

[meveric]

I found two issues.
One is apparently a global issues with all AmLogic boards and the way they handle USB devices, but I can fix that.
The other one is that initramfs is "broken".
Initramfs comes with a file param.conf which has a line ROOT="...." and it extracts this line from the current /etc/fstab.
So if I would update the /etc/fstab on the SD/eMMC first, then did a update-initramfs it would create an entry that matches the rootfs of the HDD
But that means the root=... parameter on the Kernel is completely ignored.

I'll try to investigate and find a better solution than replacing /etc/fstab.
I also fixed setup-odroid to use config.ini in the future, so normally no manual intervention should be necessary as soon as I get initramfs fixed.

[Gburas]

I knew that You can always be counted on. For now, I've put HA on eMMC, and I'll wait for You to get it. By the way, a person acquires so much knowledge while working with Odroids.

[meveric]

I've uploaded a new setup-odroid which should allow you to install the OS on HDD.
Sadly the USB is still not 100% stable and sometimes it takes too long for the HDD to get ready before the OS can use it.
A reboot helps, but it also makes it slightly dangerous to reboot remotely as the system might not boot again (only when booting from HDD)

[twinbee]

Yes the usb thing is a well know problem without a solution.
many usb to sata controller need some time after plug in to recognize from the system.
im testet some and also test some usb stick.I have success only with one usb stick that runs after power on fine.
it is recognized immediately and runs very well.Axe superb 256GB
all other that i have here need 15-20 seconds to recognize.usb to sata like also usbsticks.

[mad_ady]

wasn't there a rootwait option in the kernel args to handle this case?

[meveric]

wasn't there a rootwait option in the kernel args to handle this case?

yes and no.. there is a rootwait which is suppose to wait until the kernel sees the root device the first time, but there is also initramfs which tries to mount the system.
Initramfs tries for a certain amount of time and then gives up, after which you fall back into rescue mode of initramfs.
If you would skip initramfs, the Kernel would do the rootwait until it finds the HDD (or forever).

You can however define a "bootdelay" variable and with that tell the boot to wait before trying to continue, that way you could tell it "wait 30sec" and then continue, which might be enough for most HDDs.
But that's also a hard sleep timer.. even if the HDD would be up after 2 sec. It would still wait the entire 30sec before continuing.

[Gburas]

Yes, but looking more at reliability, (in my case) a restart after configuring the system happens very rarely, more often I have power outages after which the machine will not wake up anymore, so I can easily wait 20-30 seconds for the machine to start than take it into account that it won't start at all.

The benefits of a 500gb ssd for me are greater than the extended boot time.

[meveric]

I can probably add this as an option for the next update.
So that you can activate a bootdelay if you want to

[Gburas]

Yes please . Yesterday I tried to reinstall and it booted on a third try so this function is needed as for me. Everything else went smoothly.

Can I ask one more thing, can You help me with this: https://www.home-assistant.io/more-info ... /apparmor/
It's the last thing to my installation to be "supported".

Wysłane z mojego AC2003 przy użyciu Tapatalka

[meveric]

I've update setup-odroid again to address the above discussed issues.

It's very interesting to see how things work and how broken they are if you just dig deep enough.

For example, you will find plenty of guides that say:

rootwait - Wait (indefinitely) for root device to show up. Useful for devices that are detected asynchronously (e.g. USB and MMC devices).

Thing is, it seems no OS is actually implementing this. I checked on Debian and Ubuntu and it's not being honored, I read on ARCH forum, that they don't honor this either, it's apparently completely useless.

rootdelay is also interpreted differently by each OS.

On Ubuntu settting rootdelay=60 will increase the default timeout (how long it will try to mount the rootfs) from 30 to 60 sec.
On Debian setting rootdelay=60 would result in FIXED 60 sec sleep before it starts to continue the init process.
There is literally just a sleep $ROOTDELAY" in the code -.-

I did however "hack" the code for initramfs and increased the default timer from 30 to 60 sec.
Which just increases the time how long the initramfs tries to mount the rootfs. If it's done in 5 sec it will only wait 5 sec if it requires 45 sec it will wait 45 sec, but does not sleep 60 seconds as when setting rootdelay to 60.

Anyway this might be overwritten with future updates of initramfs tools but will also be re-applied every time setup-odroid is updated.

I also added an option that allows for your own bootargs for example like apparmor=1 and security=apparmor like in the link you had.
I tested it and it seems to work fine on the image.
Check /boot/config.ini after the update and you'll find these options.

[olco]

I am wondering if my emmc is dying and would like to test that by mmc-utils-old.

How is it possible to Install that?
Isn't found when I am trying to apt Install mmc-utils-old.

[meveric]

There is no package for mmc-utils-old
But you can follow this: viewtopic.php?p=337911#p337911
I also suggest to use fstrim to improve performance of eMMC/SD card.

[odro-volti]

I know, wrong forum, but will Bullseye ever make to XU4 ?

[meveric]

generally speaking you can update from Buster to Bullseye and it should work.
Problem is, it won't work with upstream Kernel and Panfrost, as Panfrost is not supported for the GPU of the XU4.

[odro-volti]

Hi meveric!

Thanks for reply! I don't need any graphics, I only want to run some server (like samba), but wireguard from kernel is what I'm looking for, therefore I would prefer a new kernel, like 5.10.

Armbian has stopped support for XU4 I read somewhere, so the software support for XU4 is getting thin...

[meveric]

I have no firm plan to support Debian Bullseye on XU4 yet.

I will probably start with the older boards X,X2,U2,U3,C1 as they have lima driver support and therefore require very little changes on the Kernel itself.
But I've seen tobetter has done some work on upstream Kernel for XU4 so that might be a thing even if it will not support opensouce GPU drivers.