Feedback and Queries regarding Armbian 23.11 Bookworm CLI Kernel 6.7 on Orange Pi 5

[adr3nal1n27]

Hi,

 

Thank you for maintaining this excellent distribution,

 

I have tried out this evening, via SD card, the new Armbian 23.11 Bookworm CLI Kernel 6.7 and I wanted to share some feedback on it along with some queries please:

 

1) HDMI works connected to my 4K Samsung TV, although I had to turn off "Input Signal Plus" for it to display the console correctly, otherwise there were all manner of green rectangles and other screen corruption present. Turning off "Input Signal Plus" fixed this straight away.

 

2) I cannot access either of the SSDs I have connected to my powered USB 3 hub. I tried with the hub connected to the USB-C port on the Orange Pi 5 and I also tried with it connected to the Top USB 3 port on the Orange Pi 5. I installed the full firmware package but this made no difference (not sure if it should). Issuing an lsusb does not show the USB connected SSDs. Is it expected to have these issues with USB 3 or USB-C on Kernel 6.7 ? as I do not have these issues using the legacy 5.10 kernel

 

3) If I issue a "sudo poweroff" the Orange Pi 5 shuts down all services and reboots rather than shutting down and powering off like the legacy 5.10 kernel does. If I press the power button on the Orange Pi 5 nothing happens, whereas the legacy 5.10 kernel initiates a shutdown and powers the Orange Pi 5 off. Is this expected behaviour on Kernel 6.7 ?

 

Thanks again for all your work on this distribution.

 

 

[Efe Çetin]

1- HDMI is pretty experimental.

2- Can you send lsusb output

3- Yeah it's a known issue about edge kernel. I suppose it's related to cpufreq

 

@adr3nal1n27

[adr3nal1n27]

lsusb and lsusb -t output for comparison between the kernels...

 

When running Armbian 23.11 Bookworm CLI legacy kernel 5.10:

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 005: ID 174c:0193 ASMedia Technology Inc. USB 3.0 Destop HD EP0 Product string
Bus 008 Device 004: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 008 Device 003: ID 152d:0562 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 008 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 003: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 007 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 1915:0144 Nordic Semiconductor ASA RF Controller
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c21f Logitech, Inc. F710 Wireless Gamepad [XInput Mode]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

/:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
        |__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M
        |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 1: Dev 5, If 0, Class=Mass Storage, Driver=uas, 5000M
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 3, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 4, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=xpad, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

When running Armbian 23.11 Bookworm CLI kernel 6.7:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 1915:0144 Nordic Semiconductor ASA RF Controller
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c21f Logitech, Inc. F710 Wireless Gamepad [XInput Mode]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 3, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 4, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=xpad, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M

 

When booting kernel 6.7, I noticed one service failed on boot that relates to usb.

Output below from "sudo journalctl -xeu orangepi5-usb2-init.service"

Nov 30 22:24:00 orangepi5 systemd[1]: Starting orangepi5-usb2-init.service - Init USB2 for Orange Pi 5...
░░ Subject: A start job for unit orangepi5-usb2-init.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit orangepi5-usb2-init.service has begun execution.
░░ 
░░ The job identifier is 153.
Nov 30 22:24:00 orangepi5 sh[778]: /usr/bin/sh: 1: cannot create /sys/kernel/debug/usb/fc000000.usb/mode: Directory nonexistent
Nov 30 22:24:00 orangepi5 systemd[1]: orangepi5-usb2-init.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit orangepi5-usb2-init.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 2.
Nov 30 22:24:00 orangepi5 systemd[1]: orangepi5-usb2-init.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit orangepi5-usb2-init.service has entered the 'failed' state with result 'exit-code'.
Nov 30 22:24:00 orangepi5 systemd[1]: Failed to start orangepi5-usb2-init.service - Init USB2 for Orange Pi 5.
░░ Subject: A start job for unit orangepi5-usb2-init.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit orangepi5-usb2-init.service has finished with a failure.
░░ 
░░ The job identifier is 153 and the job result is failed.

 

Hope this information helps.

 

[Spooky]

With the vendor kernel, the orangepi5-usb2-init.service is used to put the USB 2.0 port into host mode. I would not worry about the service failing on mainline Linux.

[royk]

To shutdown without a reboot 'shutdown -h now' works, although to boot it again it's necessary to press the shutdown key for a few seconds and press it again to boot.

[Thewonderer]

Congratulations with the new Amrbian build.  It's exciting to read the 23.11 include 6.7 with support for RK3588.  My question is, this doesn't seem to support the PLUS ...  Is this something that is still WIP?  Thanks.

[Werner]

42 minutes ago, Thewonderer said:

My question is, this doesn't seem to support the PLUS ...  Is this something that is still WIP?  Thanks.

edge is always to be considered WIP or experimental since the name implies "bleeding edge". Anyway look here: https://fi.mirror.armbian.de/dl/orangepi5-plus/archive/

 

[Thewonderer]

Thanks.  I'm using the latest plus version.  It does download the 23.11 firmware during an apt-upgrade.

 

Shame my EMMC module isn't booting.  It shows us using lsblk and can write to it, but when i remove the SD card, it won't boot.  I've used the armbian-config to try and set it and even use orange pi tools from the wiki to write it that way.  LED stays constant blue.  Think I'm resigned to using a fast SD card until I get a spare M2 for testing.

[adr3nal1n27]

I tried again this evening regarding point 2 from my original post, and I unplugged the powered usb3 hub from the usb-c port on the orange pi 5 and used the adaptor that came with the hub to convert it from usb-c to usb type a and then plugged it in again to the top usb 3 port on the orange pi 5 and this time it worked! 😀 and I can now access my 2 x usb connected ssd devices (1 x NVME to usb3 and 1 x SATA to usb3). I must have not pushed the adaptor all the way in when I first tried it the other night.

 

lsusb and lsusb -t now show:

Bus 002 Device 005: ID 174c:0193 ASMedia Technology Inc. USB 3.0 Destop HD EP0 Product string
Bus 002 Device 004: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 002 Device 003: ID 152d:0562 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 003: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
    |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
        |__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M
        |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M
            |__ Port 1: Dev 5, If 0, Class=Mass Storage, Driver=uas, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M

 

Some queries off the back of this please:

1) Does this mean that the usb-c port on the orange pi 5 is not fully yet fully supported in kernel 6.7 ?

 

2) How do I install kernel 6.7 and switch to it in my armbian 23.11 nvme ssd installation that is currently running the legacy 5.10 BSP kernel ? 

 

Thanks ever so much for the help and guidance.

 

 

 

[Werner]

7 hours ago, adr3nal1n27 said:

1) Does this mean that the usb-c port on the orange pi 5 is not fully yet fully supported in kernel 6.7 ?

https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md

7 hours ago, adr3nal1n27 said:

2) How do I install kernel 6.7 and switch to it in my armbian 23.11 nvme ssd installation that is currently running the legacy 5.10 BSP kernel ?

Try using armbian-config. Keep in mind that 6.7 is bleeding edge and if this breaks your installation it is up to you to fix it by yourself.

[adr3nal1n27]

@Werner

 

I have looked at armbian-config regarding switching kernels on my NVME SSD install of armbian 23.11 currently running kernel 5.10, however it does not list the latest edge kernel. The only kernels listed for selection are 6.1.11 (linux-image-edge-rk35xx - Linux kernel, armbian version 6.1.11-rk35xx edge) and 2 x instances of the 5.10.160 kernel (from armbian 23.08).

 

The 6.7 kernel in the latest 23.11 sd card image (linux-image-edge-rockchip-rk3588 - Armbian Linux edge kernel image 6.7.0-rc1-edge-rockchip-rk3588) is not available for selection in armbian-config.

 

If I ran "sudo apt install linux-image-edge-rockchip-rk3588" would this be enough to pull in the dtb and u-boot dependencies and switch to that kernel, or is there more to it?

 

Thanks again for all your help.

 

 

 

[Werner]

4 hours ago, adr3nal1n27 said:

 linux-image-edge-rockchip-rk3588

If that gives you 6.7 you can try.

[adr3nal1n27]

Just for the reference of others who are currently running the legacy 5.10.160 kernel and wanting to switch to kernel 6.7 (As this is not currently selectable in armbian-config >> System >> Other "Switch to other kernels"

 

Note that I tested this on a clean sd card install of Armbian Bookworm CLI with kernel 5.10

 

Here is what I did:

sudo apt install linux-image-edge-rockchip-rk3588 linux-dtb-edge-rockchip-rk3588 linux-u-boot-orangepi5-edge

sudo reboot

 

After reboot, uname -a now reports: 

Linux orangepi5 6.7.0-rc1-edge-rockchip-rk3588 #1 SMP PREEMPT Mon Nov 13 00:19:07 UTC 2023 aarch64 GNU/Linux

 

Thanks very much armbian team for an excellent distribution.

Edited December 5, 2023 by adr3nal1n27

[Marc R]

It is a pitty no rk3588s-orangepi-5b.dtb for orange pi 5 b

[Jean-Philippe]

I am also having problems with USB3 hub. When plugging a hub in the USB3 top port, the journal log is filled with

usb usb6-port1: Cannot enable. Maybe the USB cable is bad?

lsusb -t gives:

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 004: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
    |__ Port 001: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M

 

Plugging a USB3 drives without a hub works correctly. Everything works fine with legacy kernel.

[Marc R]

Thank you to all.

 

Latest compilation has support for orange pi 5b using kernel 6.7. Nice. No longer inferior than raspberry pi 5. Superior.

[sugatam]

I have the same problem as Jean-Philippe with an USB3 hub. On an Orange Pi 5 with edge kernel 6.7 rc4.

 

Jean-Philippe, is the vertical USB 2.0 port working for you?

[Gullik]

I have the same problem too,

 

Comparing 5.10 kernel with 6.7.0-rc7-edge indicate two fewer usb buses, so my thinking is that

either the dtb is wrong, and omitting a controller or kernel is generated without one usb.

 

Otherwise the new edge with rc7 seems good....

 

Gullik

[Eternalight7]

is this for the orangepi5 or the 5 plus version.  I get a no boot with edge 6.7rc1 on opi 5 plus

[Gullik]

It is for the orange pi 5 (flat), 16 gb

 

Works fine, but missing usb vertical port.

 

Gullik

[David Pottage]

I have booted my Orange pi5 with a recent Trixe nightly image. It is responding to pings, but I can't ssh into it. Is there a way to enable ssh access by mounting the SD card from another Linux PC and editing config files?

 

I have a USB TTL adaptor but I have mislaid it, so if there is a short cut to turning on ssh, then I would prefer to do that. I promise I will change the root password 😅

[Werner]

SSH is always enabled by default.

However I remember there is a rare case where sshd cannot start properly for some reason.

serial console is the best way to debug this (and restart sshd)

 

  

3 hours ago, David Pottage said:

but I have mislaid it,

 

Buy a few extra. They are dirt cheap
 

[Gullik]

Now at

 

Linux orangepi52 6.8.0-rc1-edge-rockchip-rk3588 #1 SMP PREEMPT Sun Jan 21 22:11:32 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

 

Still no USB2 / vertical USB.

Firefox does not run , errors out with

 

snap-update-ns killed by signal 11

 

Gullik

[Werner]

Use legacy if you need those. Do not run bleeding edge stuff if you don't know how to deal with such issues.

[Marco Schirrmeister]

@David Pottage, like Werner said, ssh is enabled, but it does not start. 

From what I have seen it fails to start because there is a problem with the ssh host keys. They are 0 bytes. At least this was the case for me, when I tried to debug this. If you do not want to go through the first setup wizard via the console, then try to delete the host key files in the /etc/ssh/ directory, when you mount your sd card on another machine. Or check if they are indeed 0 bytes and if so, delete them. Then try to boot again. It should re-create them automatically.

 

No idea what why they are empty. There is an armbian-firstrun script, which seems to delete and re-configures sshd, but no idea what or if it is even invoked.

 

[Marco Schirrmeister]

@adr3nal1n27, for you initial question #3. If you want poweroff working on the OPi5(+), then you need to patch your system for now. This patch here from the Rock 5b seems to work on the OPi5(+) as well. 

https://lore.kernel.org/lkml/170389050012.2630399.8754217298577818519.b4-ty@sntech.de/T/

 

Maybe the Armbian maintainer will add these things at one point. Otherwise it might eventually show up upstream in the mainline kernel.

[David Pottage]

Quote

From what I have seen it fails to start because there is a problem with the ssh host keys. They are 0 bytes. At least this was the case for me, when I tried to debug this. If you do not want to go through the first setup wizard via the console, then try to delete the host key files in the /etc/ssh/ directory, when you mount your sd card on another machine. Or check if they are indeed 0 bytes and if so, delete them. Then try to boot again. It should re-create them automatically.

Yes, I spotted that as well. I found my USB TTL adaptor and successfully logged in over serial, but it took effort to get ssh working. That was one of the issues, the other was that I had messed up the systemd unit files with my attempts to edit them on the MicroSD card.

 

If I get the chance I will see if I can find where the bug is. I suspect that there might be a lack of entropy during that early boot so the host key creation times out.

[David Pottage]

I found an nVME M.2 drive to fit the socket on the underside of the board: WD PC SN740 SDDPTQD-512G

 

root@orangepi5:~# smartctl -a /dev/nvme0n1
smartctl 7.4 2023-08-01 r5530 [aarch64-linux-6.8.0-rc1-edge-rockchip-rk3588] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       WD PC SN740 SDDPTQD-512G
Serial Number:                      23176Q443121
Firmware Version:                   73110000
PCI Vendor/Subsystem ID:            0x15b7
IEEE OUI Identifier:                0x001b44
Total NVM Capacity:                 512,110,190,592 [512 GB]
Unallocated NVM Capacity:           0
Controller ID:                      0
NVMe Version:                       1.4
Number of Namespaces:               1
Namespace 1 Size/Capacity:          512,110,190,592 [512 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            001b44 4a48c68698
Local Time is:                      Tue Jan 30 07:25:18 2024 GMT
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x00df):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Verify
Log Page Attributes (0x7e):         Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Log0_FISE_MI Telmtry_Ar_4
Maximum Data Transfer Size:         256 Pages
Warning  Comp. Temp. Threshold:     84 Celsius
Critical Comp. Temp. Threshold:     88 Celsius
Namespace 1 Features (0x02):        NA_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     4.70W    4.30W       -    0  0  0  0        0       0
 1 +     3.00W    3.00W       -    0  0  0  0        0       0
 2 +     2.20W    2.00W       -    0  0  0  0        0       0
 3 -   0.0150W       -        -    3  3  3  3     1500    2500
 4 -   0.0050W       -        -    4  4  4  4    10000    6000
 5 -   0.0033W       -        -    5  5  5  5   176000   25000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         2
 1 -    4096       0         1

 

root@orangepi5:~# fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --filename=/mnt/nvme0n1p1/test --bs=4k --iodepth=64 --size=4G --readwrite=randrw --rwmixread=75
test: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=64
fio-3.36
Starting 1 process
test: Laying out IO file (1 file / 4096MiB)
Jobs: 1 (f=1): [m(1)][100.0%][r=329MiB/s,w=109MiB/s][r=84.3k,w=27.9k IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=3556: Tue Jan 30 07:20:48 2024
  read: IOPS=80.5k, BW=314MiB/s (330MB/s)(3070MiB/9764msec)
   bw (  KiB/s): min=266528, max=339688, per=100.00%, avg=322661.47, stdev=21780.95, samples=19
   iops        : min=66632, max=84920, avg=80665.16, stdev=5445.10, samples=19
  write: IOPS=26.9k, BW=105MiB/s (110MB/s)(1026MiB/9764msec); 0 zone resets
   bw (  KiB/s): min=88128, max=115320, per=100.00%, avg=107853.47, stdev=7553.47, samples=19
   iops        : min=22032, max=28830, avg=26963.37, stdev=1888.37, samples=19
  cpu          : usr=9.34%, sys=39.17%, ctx=134205, majf=0, minf=14
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
     issued rwts: total=785920,262656,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=64

Run status group 0 (all jobs):
   READ: bw=314MiB/s (330MB/s), 314MiB/s-314MiB/s (330MB/s-330MB/s), io=3070MiB (3219MB), run=9764-9764msec
  WRITE: bw=105MiB/s (110MB/s), 105MiB/s-105MiB/s (110MB/s-110MB/s), io=1026MiB (1076MB), run=9764-9764msec

Disk stats (read/write):
  nvme0n1: ios=767663/256616, sectors=6141304/2052936, merge=0/1, ticks=451440/50138, in_queue=501578, util=99.12%

 

[David Pottage]

21 minutes ago, David Pottage said:

If I get the chance I will see if I can find where the bug is. I suspect that there might be a lack of entropy during that early boot so the host key creation times out.

I just found a kernel manline status page (For another rk3588 board) and it shows the random number generator as TODO

 

https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md#:~:text=Random Number Generator

 

So I guess for now the OrangePi5 will be starved of entropy during early bootup, and won't be able to generate ssh host keys.

[Marco Schirrmeister]

In my case, they are not always empty. Maybe early on, I don't know. Have not tried to mount the disk after each first boot to see the status.

They keys are often fine, after I ran through the first boot setup wizard (armbian-firstlogin). Then a restart of the daemon or a reboot is all to get it started.

 

The other day when I looked at it, I found this one. https://github.com/armbian/build/issues/3771

In the armbian-firstrun script are the commands to delete the keys, re-create them and restart the service. Given that this commands are run in serial, I wonder if the "dpkg-reconfigure openssh-server" can fail in a why to generate 0 byte files. But given that they are most of the time ok, I don't understand why a restart of the service later in the script would fail. Unless there is something else besides the firstrun script that tries to do the same thing.