Makes board unstable

[ 1173.843180] rockchip-dw-pcie 3c0800000.pcie: PCIe Gen.3 x2 link up
[ 1173.971258] pcieport 0002:20:00.0: Root Port has been reset
[ 1173.971328] nvme nvme0: restart after slot reset
[ 1173.982877] nvme nvme0: D3 entry latency set to 8 seconds
[ 1173.994210] nvme nvme0: 4/0/0 default/read/poll queues
[ 1173.994642] pcieport 0002:20:00.0: AER: device recovery successful
[ 1173.994719] pcieport 0002:20:00.0: Recovering Root Port due to Link Down
[ 1173.994761] nvme nvme0: frozen state error detected, reset controller
[ 1174.028524] phy phy-fe8c0000.phy.7: lane number 0, val 1
[ 1174.343104] rockchip-dw-pcie 3c0800000.pcie: PCIe Gen.3 x2 link up
[ 1174.471131] pcieport 0002:20:00.0: Root Port has been reset
[ 1174.471191] nvme nvme0: restart after slot reset
[ 1174.486326] nvme nvme0: D3 entry latency set to 8 seconds
[ 1174.496045] nvme nvme0: 4/0/0 default/read/poll queues
[ 1174.496250] pcieport 0002:20:00.0: AER: device recovery successful
[ 1174.496284] pcieport 0002:20:00.0: Recovering Root Port due to Link Down
[ 1174.496303] nvme nvme0: frozen state error detected, reset controller

Please test rc in bleeding-edge before making it available on edge

Thanks !

just installed 23.8.1 on my odroid M1, and I get poor network perf when using 1G port speed.

iperf to another machine (iperf -c <server>, M1 sends traffic) gives the following:

[ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  8.15 MBytes  6.84 Mbits/sec  631             sender
[  5]   0.00-10.04  sec  7.86 MBytes  6.57 Mbits/sec                  receiver

reverse direction, M1 receives traffic: iperf -R -c <server> 
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.04  sec  1.10 GBytes   937 Mbits/sec  587             sender
[  5]   0.00-10.00  sec  1.09 GBytes   938 Mbits/sec                  receiver
 

same exists with older releases.

also tried with older kernel (6.1.12-rk3568-odroid)

when I set the network port on switch side to 100Mbps / full, then send, receive side is ok, can fill 100Mbps.

Can you please help?

BR,

Tamas

I've installed armbian with Debian Trixie on my Odroid-M1 to replace the Ubuntu installed via petitboot.

Everything was running smoothly except the networking part which was very slow (with luck some 100kbit/s) and has shown very high packetloss, even while the switch and ethtool report absolutely no problems and replacing cables and switching ports didn't help.

Switching to 100Mbit/s was working fine, no loss anymore, switching back to 1G caused massive packet loss.

With some help from chatgpt and another M1 I own that was still running the hardkernel/petitboot installed kernel and dtb I could trace the issue down the RGMII timings provided in the armbian provided dtb compared to the hardkernel dtb.

My odroid-m1 with 4G RAM running armbian used this (from dmesg)

rk_gmac-dwmac fe2a0000.ethernet: init for rgmii with delay (tx: 0x4f, rx: 0x2d)

The other one with 8G and hardkernel ubuntu (also from dmesg):

rk_gmac-dwmac fe2a0000.ethernet: TX delay(0x35).
rk_gmac-dwmac fe2a0000.ethernet: RX delay(0x2d).

After installing busybux with devmem I could change the settings on the fly

busybox devmem 0xfdc60380 32 0x007F0035
# restoring old value
# busybox devmem 0xfdc60380 32 0x007F004F

The previous values and new value can be check with this command

busybox devmem 0xfdc60380 32

Before the change it had shown the old values (0x00002D4F), and afterwards 0x00002D35 (RX and TX).

With that settings via devmem I could switch the packet loss on and off.

Am I'm the only one with that issue or does it make sense to create bug to get it fixed?

There must be a reason why armbian is using different values in the odroid-m1 dtb files than hardkernel itself.

Thanks in advance for any replies.

Karsten

$ lsb_release -a
No LSB modules are available.
Distributor ID:    Debian
Description:    Armbian 26.8.3 trixie
Release:    13
Codename:    trixie

$ dmesg
[   18.683974] r8152 6-1:1.0 enx001e063222ad: carrier on
[   27.803475] wlxe0e1a93880f7: authenticate with xx:xx:xx:xx:xx:xx
[   29.112665] wlxe0e1a93880f7: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[   29.115405] wlxe0e1a93880f7: authenticated
[   29.126606] wlxe0e1a93880f7: associating to AP xx:xx:xx:xx:xx:xx with corrupt beacon and probe response
[   29.134087] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 1/3)
[   29.253998] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 2/3)
[   29.374009] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 3/3)
[   29.494035] wlxe0e1a93880f7: association with xx:xx:xx:xx:xx:xx timed out
[   35.700754] wlxe0e1a93880f7: authenticate with xx:xx:xx:xx:xx:xx
[   36.945503] wlxe0e1a93880f7: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[   36.950699] wlxe0e1a93880f7: authenticated
[   36.950924] wlxe0e1a93880f7: associating to AP xx:xx:xx:xx:xx:xx with corrupt beacon and probe response
[   36.955088] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 1/3)
[   37.065067] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 2/3)
[   37.175046] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 3/3)
[   37.285432] wlxe0e1a93880f7: association with xx:xx:xx:xx:xx:xx timed out
[   43.743849] wlxe0e1a93880f7: authenticate with xx:xx:xx:xx:xx:xx
[   44.995503] wlxe0e1a93880f7: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[   44.998111] wlxe0e1a93880f7: authenticated
[   45.005706] wlxe0e1a93880f7: associating to AP xx:xx:xx:xx:xx:xx with corrupt probe response
[   45.025088] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 1/3)
[   45.135078] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 2/3)
[   45.255109] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 3/3)
[   45.375222] wlxe0e1a93880f7: association with xx:xx:xx:xx:xx:xx timed out
[   52.237430] wlxe0e1a93880f7: authenticate with xx:xx:xx:xx:xx:xx
[   53.485642] wlxe0e1a93880f7: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[   53.486297] wlxe0e1a93880f7: aborting authentication with xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
[   70.197420] wlxe0e1a93880f7: authenticate with xx:xx:xx:xx:xx:xx
[   71.445752] wlxe0e1a93880f7: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[   71.449174] wlxe0e1a93880f7: authenticated
[   71.454615] wlxe0e1a93880f7: associating to AP xx:xx:xx:xx:xx:xx with corrupt beacon and probe response
[   71.455350] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 1/3)
[   71.565277] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 2/3)
[   71.685295] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 3/3)
[   71.815254] wlxe0e1a93880f7: association with xx:xx:xx:xx:xx:xx timed out
[   82.570077] wlxe0e1a93880f7: authenticate with xx:xx:xx:xx:xx:xx
[   83.795886] wlxe0e1a93880f7: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[   83.798750] wlxe0e1a93880f7: authenticated
[   83.799500] wlxe0e1a93880f7: associating to AP xx:xx:xx:xx:xx:xx with corrupt beacon and probe response
[   83.805438] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 1/3)
[   83.935371] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 2/3)
[   84.055403] wlxe0e1a93880f7: associate with xx:xx:xx:xx:xx:xx (try 3/3)
[   84.165387] wlxe0e1a93880f7: association with xx:xx:xx:xx:xx:xx timed out

-plug and unplug usb wifi dongle
$ dmesg
[ 1124.053961] usb 3-1.2: new high-speed USB device number 5 using xhci-hcd
[ 1124.184704] usb 3-1.2: New USB device found, idVendor=0bda, idProduct=c820, bcdDevice= 2.00
[ 1124.184755] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1124.184782] usb 3-1.2: Product: 802.11ac NIC
[ 1124.184802] usb 3-1.2: Manufacturer: Realtek
[ 1124.184822] usb 3-1.2: SerialNumber: 123456
[ 1124.277700] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
[ 1124.278629] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 1124.279640] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[ 1124.279664] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
[ 1124.282156] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
[ 1124.282839] Bluetooth: hci0: RTL: cfg_sz 10, total sz 21678
[ 1124.299444] rtw_8821cu 3-1.2:1.2: Firmware version 24.11.0, H2C version 12
[ 1124.693624] Bluetooth: hci0: RTL: fw version 0x826ca99e
[ 1124.729501] rtw_8821cu 3-1.2:1.2 wlxe0e1a93880f7: renamed from wlan0

$ ip link
3: wlxe0e1a93880f7: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff

$ sudo nmcli device wifi list
IN-USE  BSSID              SSID                MODE   CHAN  RATE        SIGNAL  BARS  SECURITY
        xx:xx:xx:xx:xx:xx  mywifi              Infra  5     405 Mbit/s  87      ▂▄▆█  WPA1 WPA2

$ sudo nmcli device status
DEVICE           TYPE      STATE                   CONNECTION
wlxe0e1a93880f7  wifi      disconnected            --

$ sudo nmcli device show wlxe0e1a93880f7
GENERAL.DEVICE:                         wlxe0e1a93880f7
GENERAL.TYPE:                           wifi
GENERAL.HWADDR:                         xx:xx:xx:xx:xx:xx
GENERAL.MTU:                            1500
GENERAL.STATE:                          30 (disconnected)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
IP4.GATEWAY:                            --
IP6.GATEWAY:                            --

$ nmcli connection show
NAME                UUID                                  TYPE      DEVICE
mywifi              9bf79c36-d724-470f-bd62-f461a44290b2  wifi      --

What runs, measured against CPU-only TFLite on the same board:

- **mobilenet_v1** (224×224 quant): **5.4 ms vs 117 ms (~22×)** — convolutions, depthwise, the fully-connected final layer and average pooling all on the NPU; top-5 classes match the CPU reference, mean absolute logit difference 0.03, bit-identical results across repeated runs.
- **mobilenet_v2**: **6.3 ms vs 76 ms (~12×)** — including all ten fused residual additions; top-5 matches the CPU reference including order.
- **resnet18**: **11.2 ms vs 345 ms (~31×)** — end-to-end in a single NPU partition: convolutions, residual adds, max pooling, global average pooling and the fully-connected classifier, the poolings executed by the NPU's dedicated PPU unit.
- **yolov8n** (320×320 int8, the plain ultralytics TFLite export): **14.9 ms vs 70 ms (~4.7×)** — backbone, neck and the three detection heads on the NPU in two partitions, including all 57 SiLU activations (fused into the convolutions through the DPU lookup table, as the vendor stack does) and the two nearest-neighbour upsamples (the DPU's unpooling mode); the NPU itself takes 8 ms, the rest is the [1, 84, 2100] DFL tail on the CPU. On bus.jpg the same five detections as the CPU (boxes, classes, scores).
- Single-operation probe layers (regular, depthwise, stride-2, the 3-channel first layer, fully-connected, concat, standalone add, SiLU, slice/pad/requantize views, upsample — uint8 and int8, per-tensor and per-channel weights) match the TFLite CPU reference within 1 LSB.
- For the classifiers only reshape and softmax stay on the CPU.

Timings are at the NPU clock pinned to 800 MHz through SCMI (the MAC array is clocked from the SCMI/PVTPLL rate, not the CRU clock the driver sets; a module parameter selects the rate). "Bit-identical" means: same board, fixed clock, repeated runs; results from other RK3568 boards are welcome.

How the hardware is driven: the whole delegated graph is submitted as one job. Each task's command stream is patched to chain into the next, the NPU's PC unit walks the chain in hardware and raises a single interrupt at the end — the same submit model the vendor driver uses. Per-job overhead is ~0.2 ms, so avoiding a round-trip per layer matters: it is most of the difference between these numbers and a naive per-task submit. The NPU cannot address memory above 4 GiB, but no `mem=4G` boot restriction is needed: GFP_DMA32 patches in the IOMMU page-table path and in the driver's buffer allocation keep the full 8 GB usable.

This builds on the RK3588 Mesa branch (MR !42134). RK3568 differs: 8-channel feature atomics instead of 16 (strides in 8-byte units), 8×32 KiB CBUF banks, a different weight layout (with compact tails for partial channel slices and kernel groups), depthwise above 32 channels running as 32-channel-group tasks, a packed-RGB first-layer mode, weight streaming for FC-shaped layers, requantization through the DPU BS stream, a feature-prefetch (FEATURE_GRAINS) formula that grows on narrow feature maps, the element-wise unit configuration for residual adds — including the surface-notch addressing that band-split add tasks need — the PPU/PPU_RDMA pooling programming, the DPU lookup table (SiLU; the tables travel with the job and the kernel writes them over MMIO, loading them from the command stream lands only the first one) and the DPU unpooling mode (2× upsample), all derived from byte-level comparison against captured vendor command streams (resnet18 and probe models). Details are in the commit messages.

Code and reproduction (step-by-step README, kernel .debs in the release):
- https://github.com/iav/rk3568-npu — kernel module, DT overlay, test harness, probe models, README
- https://github.com/iav/mesa (branch rk3568-test-session-20260820)
- release with the kernel .debs / rocket.ko / dtbo: https://github.com/iav/rk3568-npu/releases/tag/v2026.08.22

References used: MR !42134 (https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/42134), the vendor-stack topic above (incl. the >4 GB IOMMU discussion), kiln (https://github.com/gahingwoo/kiln), rknn-toolkit2 (https://github.com/airockchip/rknn-toolkit2 — only needed for further RE, not for running).

Limitations: residual ±1-per-layer rounding drift (the hardware rounding pipeline differs from TFLite's reference requantization); PPU pooling covers kernels ≤ 8 with equal strides and equal input/output quantization, other average poolings fall back to a depthwise-convolution lowering; softmax and the 3D detection tail on the CPU; convolution/depthwise/add/pooling/concat/fully-connected with fused ReLU/ReLU6/SiLU, slice/pad/requantize as addressing, nearest 2× upsample; uint8/int8 activations (per-tensor), per-tensor or per-channel weights; feature maps up to 2047 wide/high. A rare (~2% of fresh processes) one-pixel race between chained tasks shows on tiny probe graphs only; the real networks are bit-identical run to run. The Mesa branch head is ahead of the patch series in the rk3568-npu repo; use the branch for the latest state.

7.1.6 broke my iptables

Thanks !

TL;DR

I've successfully enabled the Rockchip RK3568 NPU (0.8 TOPS INT8) on the ODROID-M1 with 8GB RAM running Armbian 6.18.9-current-rockchip64.

The only thing needed to make this work for everyone is a 1-line kernel patch in Armbian build that I've already submitted: https://github.com/armbian/build/pull/9403

Once this patch is merged into Armbian, the DKMS modules will work out-of-the-box on all RK3568 boards.

The Problem

1. Hardkernel and Rockchip provide NPU patches for quite old kernel versions:

• rockchip <= 6.6
• hardkernel <= 5.10

2. IOMMU page table allocation bug — On systems with >4GB RAM, the kernel's IOMMU allocates page tables above 4GB, but the NPU can only access the first 4GB of physical memory, causing DMA mapping failures and inference timeouts

The Solution

1. Kernel Patch (1 line!)

-   .gfp_flags = 0,
+   .gfp_flags = GFP_DMA32,

This forces IOMMU page tables to be allocated below 4GB, fixing NPU operation on 8GB boards.

2. DKMS Driver Package

I've created a complete DKMS package that:

- Includes DT overlays for NPU, IOMMU, power-domain, and clock configuration

- Supports dynamic frequency scaling (100 MHz - 1000 MHz)

- Provides `/dev/dri/renderD129` (DRM/GEM interface) for RKNN Runtime

- Would compile against Armbian's stock kernel headers with the above patch merged

The Questions

1. What would be the best way to provide those modules for installation in the armbian system?

2. Has someone a 4 GB version of the M1 and could test the modules?

[    2.836541] usb 7-1: new full-speed USB device number 2 using ohci-platform
[    3.024538] usb 7-1: device descriptor read/64, error -62
[    3.304535] usb 7-1: device descriptor read/64, error -62
[    3.596542] usb 7-1: new full-speed USB device number 3 using ohci-platform
[    3.780527] usb 7-1: device descriptor read/64, error -62
[    4.076543] usb 7-1: device descriptor read/64, error -62
[    4.180566] usb usb7-port1: attempt power cycle
[    4.372529] usb 7-1: new full-speed USB device number 4 using ohci-platform
[    4.780541] usb 7-1: device not accepting address 4, error -62
[    4.964529] usb 7-1: new full-speed USB device number 5 using ohci-platform
[    5.372526] usb 7-1: device not accepting address 5, error -62
[    5.372569] usb usb7-port1: unable to enumerate USB device

I have been running armbian with the minmal debian trixie image on a odroid M1 for a few month now and I noticed that since I installed the image there has not been a single kernel upgrade.
the kernel is still at 6.18.10 despite current debian install image for this board being shipped with 6.18.28 so I am assuming I am doing something wrong.
The apt update and apt dist-upgrade logs show clearly all current package information are being downloaded from both debian and the armbian mirrors, and both armbian-config updates and upstream debian packages have been upgraded whenever I run the  apt dist-upgrade commands, but the kernel is still the same old version from several month ago.

Any clue what I should look at to find the issue?
Thanks
 

When I tried to start the board with the community image for the Odroid m1s on a SD card, it wouldn't boot.

The connected screen (HDMI) would stay black and the blue heartbeat LED would stay on permanently.

I tried building and flashing u-boot but that didn't help me.

Here's what DID work:

(Note: it worked for me. I can't guarantee that this fixes it for everyone, use at your own risk)

• I mounted the SD card on a Linux desktop and created backups of the boot scripts (just to be safe)

sudo cp <mount_path>/armbi_root/boot/boot.cmd <mount_path>/armbi_root/boot/boot.cmd.bak
sudo cp <mount_path>/armbi_root/boot/boot.scr <mount_path>/armbi_root/boot/boot.scr.bak

• Then I set the load address to 0x0c000000

sudo sed -i 's/setenv load_addr "0x9000000"/setenv load_addr "0x0c000000"/' <mount_path>/armbi_root/boot/boot.cmd

• Then I ran mkimage as follows:

sudo /usr/bin/mkimage -C none -A arm -T script -d <mount_path>/armbi_root/boot/boot.cmd <mount_path>/armbi_root/boot/boot.scr

• This fixed the booting, but just to be sure a future update wouldn't undo it I also wrote it to armbianEnv.txt

echo "load_addr=0x0c000000" | sudo tee -a <mount_path>/armbi_root/boot/armbianEnv.txt

And that's it!

One more thing: I noticed that Ethernet did not work out of the box, so I did this:

I attached a UART cable to log into the machine and created the following script, which patches the device tree.

You might need to get a little creative if your only access would be through Ethernet, but you I'm sure you can figure something out.

(Maybe create the necessary files while the SD card is still mounted on your PC)

cat > /usr/local/sbin/patch-gmac-dtb.sh << 'EOF'
#!/bin/bash
DTB=/boot/dtb/rockchip/rk3566-odroid-m1s.dtb
dtc -I dtb -O dts $DTB -o /tmp/m1s.dts 2>/dev/null
# Only patch if not already applied
if grep -q 'snps,reset-gpio' /tmp/m1s.dts; then
    echo "GMAC DTB patch already present, skipping"
    exit 0
fi
sed -i '/phy-mode = "rgmii-id";/a \\t\tsnps,reset-gpio = <0x51 0x0f 0x01>;\n\t\tsnps,reset-active-low;\n\t\tsnps,reset-delays-us = <0x00 0x4e20 0x186a0>;' /tmp/m1s.dts
sed -i '/reset-assert-us/d; /reset-deassert-us/d; /reset-gpios = <0x51/d' /tmp/m1s.dts
dtc -I dts -O dtb /tmp/m1s.dts -o $DTB 2>/dev/null
echo "GMAC DTB patch applied"
EOF
  
  

chmod +x /usr/local/sbin/patch-gmac-dtb.sh

Execute the script and Ethernet should be working. (Might need a reboot, though).

If this works, you should make sure this is  applied after every kernel update, because it will get overwritten otherwise:
 

# Run it automatically after kernel/dtb package updates
cat > /etc/apt/apt.conf.d/99-patch-gmac-dtb << 'EOF'
DPkg::Post-Invoke {"if [ -f /usr/local/sbin/patch-gmac-dtb.sh ]; then /usr/local/sbin/patch-gmac-dtb.sh; fi"};
EOF

But is not build in 6.18 / 6.19

otherwise we get 

[   13.370681] panfrost fde60000.gpu: get clock failed -517
[   13.370717] panfrost fde60000.gpu: clk init failed -517
[   13.485723] panfrost fde60000.gpu: get clock failed -517
[   13.485761] panfrost fde60000.gpu: clk init failed -517
[   13.503876] panfrost fde60000.gpu: get clock failed -517
[   13.503918] panfrost fde60000.gpu: clk init failed -517

Thanks !

I downloaded the image Armbian_24.8.3_ordoidm1_jammy_current_6.6.51_kde-neon-kisak-desktop

The image does not start without pressing rcy, so far normal. After flashing the mtd with armbian-installer and copying to SSD. The image still does not start. No display.

After trying several things and without success, I decided to try an old image:

Armbian_24.2.1_ordoidm1_jammy_current_6.6.16_xfce_desktop.

I here rcy boot, install, copy to SSD, flash mtd and reboot. And it works. So I tried image 6.6.51 kde Again. But without flashing the mtd. And there it boots without problems and no need for rcy.

So it seems that the last image and also the 24.2. 4 that I tried. We have a probably corrupted uboot.

I have the odroid m1 8gb.

I hope this will allow others not to waste hours trying because of a corrupted uboot. (This was my first attempt with armbian on this card. Before I had petitboot.)

Sorry for my bad English. I used Google translate.

PS: I tried to make a bug report form. But you have to provide an armbianmonitor -u output or something like that. And that doesn't match the fact. The card doesn't even boot.

Brand new odroid-m1, Samsung Pro Endurance 256GB; and a brand-new/uninitialized Samsung PM9A1 256GB NVMe.

It drops me to a shell [presumably the initramfs].

Note: I'm not out of options yet, I can try building my own image with newer current or edge kernels.

Edited to add: I think it's booting me to the petitboot env, not even attempting to boot the SD card,

Once an SD card with armbian is inserted and the system is booted through the recovery button once, logged in* and then shutdown normally, the system boots again from SPI.

* Without login and regular shutdown of the system booted from sd card, the issue remains

I have observed and reproduced this issue several times in the last year.

In my case the M1 is connected to a power strip that turns on and off the multiple devices.

When I forget to unplug the M1 and it gets turned on and off several times over a day or more, the issue appears.

When I turn it of manually I could not yet observe the issue, so it may be related to being booted and turned off multiple times in short order.

When I investigate the journal of the last boot circles, there is nothing there, as if the boot process never started, leaving me to suspect an issue with the bootloader in combination with SPI and power loss.

I wanted to give my Odroid M1 new life by installing a fresh Armbian 25.5.1. Previously it was running on an old Odroid Ubuntu Image.

After starting from SD I have no ethernet connection. The eth0 interface is DOWN. I tried using a USB3 2.5G ethernet adapter, but the new network interface also shows DOWN.

I have tried Debian and Ubuntu Minimal images with the same results.

What could be the cause and how do I get a working ethernet connection?

Thanks

Malz

I have recently acquired an ODROID M1 board and flashed Armbian 24.5.3 on it to replace my old XU4 running Armbian 24.5.1. I've managed to port everything from the old XU4 to the new M1 except for two WiFi dongles. They worked just fine on the XU4 but the M1 just doesn't want to recognize them, I can see them when I run `lsusb`

Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 0bda:0811 Realtek Semiconductor Corp. Realtek 8812AU/8821AU 802.11ac WLAN Adapter [USB Wireless Dual-Band Adapter 2.4/5Ghz]
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 

but I get no wifi interfaces. 

Does anybody know what the problem could be?

Thanks in advance!

I am looking into OdroidM1 network performance with kernel 6.6.47-current-rockchip64 ( 24.8.1 )

For some reason network performance is x10 faster (upstream) in bookworm and noble, when compared to jammy.
Downstream performance is fine, delivering the same performance in jammy and the other distributions.

Since all of them are using the same kernel, I assume that there must be some configuration that jammy is missing, or?

Any idea about what could be going on?

How can i get the Rknpu working in Armbian for latest builds.

I am unable to find how to make this work.

Thanks in Anticipation

After successfully installed and booted Armbian 23.02.2 Jammy from SD card on Odroid M1, I ran armbian-install script with using option "boot from SD, system on SSD" to move system to SSD. The process finished successfully, see the logs from armbianmonitor (taken before reboot): https://paste.armbian.com/folivedane

After reboot, system failed to boot automatically from SSD due to error:

[   13.766854] 8644d43f-c78d-4586-ab61-14dfa2e740ea: Can't open blockdev
[   13.774855] systemd[1]: Starting Rule-based Manager for Device Events and Files...
[   13.781860] systemd[1]: media-mmcboot.mount: Mount process exited, code=exited, status=32/n/a
[   13.781889] systemd[1]: media-mmcboot.mount: Failed with result 'exit-code'.
[   13.783141] systemd[1]: Failed to mount /media/mmcboot.
[   13.785392] systemd[1]: Dependency failed for /boot.

It asked for root password to go to maintenance mode. I found, boot failed because of wrong entry in /etc/fstab:

root@odroidm1:~# cat /etc/fstab
# <file system>                                 <mount point>   <type>  <options>                                                       <dump>  <pass>
tmpfs                                           /tmp            tmpfs   defaults,nosuid                                                 0       0
8644d43f-c78d-4586-ab61-14dfa2e740ea    /media/mmcboot  ext4    defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide       0       1
/media/mmcboot/boot                             /boot           none    bind                                                            0       0
UUID=832c2ac5-7666-4725-a85f-c8a015d9995a       /               ext4    defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide       0       1

as you can see there is missing "UUID=" before uuid string for /media/mmcboot entry.

After I fixed this problem by mounting /media/mmcboot and /boot (bind mount) manually and exited from maintenance mode it booted OK. I collected another armbianmonitor logs after boot, see: https://paste.armbian.com/qohidenowu

When the broken line is fixed in the /etc/fstab:

UUID=8644d43f-c78d-4586-ab61-14dfa2e740ea       /media/mmcboot  ext4    defaults,noatime,commit=600,errors=remount-ro,x-gvfs-hide       0       1

system is booting normally.

The same issue is present also when I used image Armbian 23.02.2 Bullseye

Could you fix this bug, please? I think problem in nand-sata-install script (line 371).

Thanks in advance!

On update, sometimes I had to reinstall the zfs kernel module, but now I have the problem, that the system does not recognize the kernel headers:

sudo apt-get --reinstall install zfs-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 2,397 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://mirrors.dotsrc.org/armbian-apt jammy/jammy-utils arm64 zfs-dkms all 2.2.3-1 [2,397 kB]
Fetched 2,397 kB in 1s (3,567 kB/s)
Preconfiguring packages ...
(Reading database ... 72929 files and directories currently installed.)
Preparing to unpack .../zfs-dkms_2.2.3-1_all.deb ...
Deleting module zfs-2.2.3 completely from the DKMS tree.
Unpacking zfs-dkms (2.2.3-1) over (2.2.3-1) ...
Setting up zfs-dkms (2.2.3-1) ...
Loading new zfs-2.2.3 DKMS files...
Building for 6.1.12-rk3568-odroid
Module build for kernel 6.1.12-rk3568-odroid was skipped since the
kernel headers for this kernel does not seem to be installed.
Processing triggers for initramfs-tools (0.140ubuntu13.4) ...
update-initramfs: Generating /boot/initrd.img-6.1.12-rk3568-odroid
W: Possible missing firmware /lib/firmware/nvidia/tegra194/xusb.bin for built-in driver xhci_tegra
W: Possible missing firmware /lib/firmware/nvidia/tegra186/xusb.bin for built-in driver xhci_tegra
W: Possible missing firmware /lib/firmware/nvidia/tegra210/xusb.bin for built-in driver xhci_tegra
W: Possible missing firmware /lib/firmware/nvidia/tegra124/xusb.bin for built-in driver xhci_tegra
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.12-rk3568-odroid
Image Name:   uInitrd
Created:      Thu Apr 25 11:27:48 2024
Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
Data Size:    27753116 Bytes = 27102.65 KiB = 26.47 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.12-rk3568-odroid to /boot/uInitrd
'/boot/uInitrd' -> 'uInitrd-6.1.12-rk3568-odroid'
update-initramfs: Armbian: done.

I already removed and reinstalled the headers via armbian-config > Headers_remove, Headers_install but without change.

 

apt-get list --installed |grep header

linux-headers-edge-rockchip64/jammy,now 24.2.1 arm64 [installed]

do I need to create some magic symlinks or parameters for apt-get to get the headers resolved since the kernel version is missing in the package?

Why does /dev/rga not exist in my armbian install?

I need it for my FFmpeg rkmpp config.

But I have another problem the tty1 display on the oled screen when I disconnect the HDMI.

Where can i disabled this ?

>root@yanas3:/dev# i2cdetect -y 3
>     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>00:                         -- -- -- -- -- -- -- -- 
>10: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- 
>20: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>70: -- -- -- -- -- -- -- --   

My peripheral is an OLED screen SSD1306. It works perfectly with an Orange Pi5.
It's connected to GPIO pin  1 (VDD), 3 (SDA),5 (SDL),9 (GND) but I can't see it.

What am i doing  wrong ?

Building bullseye and burn it to an sd card system will not boot even after pressing the RCY button.   I've build today a new img and it boots bullseye but it freezes loading first boot

With bookworm it does boot pressing the RCY button but the Boot from MTD flash and system to nvme seems broken

if power off the board remove the sd card the system won't boot with or without sd card

(If I boot it again using the RCY with the installer already configured on the sd card and use the command df the nvme disk is not present but it appears in the installation)  (Pic 4)

Also on bookworm booting from sd card and installing system to nvme works without issues

The nvme it's a 2TB 970 evo plus which according to hardkernel is compatible and it is since the boot from sd is working without issues

I've notice a blazing fast line while using the MTD

Thanks !

After change it via armbian-config

It stays the default

cpufreq-info       
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 149 us.
  hardware limits: 408 MHz - 1.99 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.10 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 1.99 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 408 MHz and 1.99 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.99 GHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.86%, 600 MHz:9.43%, 816 MHz:3.66%, 1.10 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 1.99 GHz:86.04%  (10441)
analyzing CPU 1:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 149 us.
  hardware limits: 408 MHz - 1.99 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.10 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 1.99 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 408 MHz and 1.99 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.99 GHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.86%, 600 MHz:9.43%, 816 MHz:3.66%, 1.10 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 1.99 GHz:86.04%  (10441)
analyzing CPU 2:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 149 us.
  hardware limits: 408 MHz - 1.99 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.10 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 1.99 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 408 MHz and 1.99 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.99 GHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.86%, 600 MHz:9.43%, 816 MHz:3.66%, 1.10 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 1.99 GHz:86.04%  (10441)
analyzing CPU 3:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 149 us.
  hardware limits: 408 MHz - 1.99 GHz
  available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.10 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 1.99 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 408 MHz and 1.99 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.99 GHz (asserted by call to hardware).
  cpufreq stats: 408 MHz:0.86%, 600 MHz:9.43%, 816 MHz:3.66%, 1.10 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 1.99 GHz:86.04%  (10441)

As I am still working on hardening my Odroid-M1 servers, I am looking for a solution to activate a real console for root login only. My homelab is not in the same room as my desk, so I need to get access from an internal VLAN with restrictions and take control even if the network drivers are not enabled. Have you tested or used a UART to Ethernet converter like https://www.pusr.com/products/ethernet-to-uart-modules-usr-k7.html

or

https://www.waveshare.com/uart-to-eth.htm

or something else?

Let me know your thoughts.

Sincerely, Frederic

I'm a newcomer to ARMBIAN, and I'm eager to transition from my current stock Odroid (20.04) setup (petitboot full nvme SSD) to a more up-to-date distribution, complete with the latest kernel upgrades. I've taken the time to go through the documentation and here's what I've gathered:

1. It appears that native booting from an nvme SSD or USB isn't possible (yet?). Instead, I'll need to use microSD cards or an emmc module for booting while installing the system on an nvme SSD.
2. I also understand that deactivating petitboot is necessary.

Now, I have a few questions:

• Q1: Do I have a correct understanding of these two prerequisites, or is there any way to retain petitboot functionality? Additionally, can I install both the boot and system on the nvme SSD, bypassing the emmc altogether?
• Q2: Given that I require both USB ports to operate at 5Gb/s, it seems that emmc is my best choice. Could you recommend a specific emmc in terms of size or brand that aligns with my needs?
• Q3: In my work with production servers, I frequently employ LVM for storage encapsulation. At home, on my NUC (10i7FNH) with Ubuntu 22.04, I've placed /boot outside the LVM volume, while other filesystems perform well when managed by LVM. Is it feasible to replicate this setup with ARMBIAN during installation, encapsulating / within an LVM volume?
• Q4: As my 3 odroid-M1 systems will be dedicated to running technical services for POCs or homelab (server + CLI only), I'm interested in having KVM installed. Is this a possibility on ARMBIAN, and could you guide me through the process of creating virtual machines within the ARMBIAN environment?
• Appreciating your assistance,

I don't know if I am using the right location to post this message, please tell me where to post it if I was wrong.

Frederic

thanks for supporting this device

I'm trying to install pivccu (homematic smarthome) on armbian to use it with homeassistant.

It's not officially supported (yet) but I got it running with the default hardkernel ubuntu image.

https://github.com/alexreinert/piVCCU/blob/master/docs/setup/armbian.md

I can't seem to find the kernel headers/sources for my kernel. Any Ideas?

Below is what I found. I'm willing to go back to 6.1.12 if that doesn't cause any issues.

Can't do it via armbian-config. Do I need to download an image from the archive and reinstall?

uname -a
Linux odroid 6.3.4-rk3568-odroid #5 SMP PREEMPT Wed May 24 16:30:25 UTC 2023 aarch64 GNU/Linux

-----------------------------------------------

apt search $(uname -r)
Sorting... Done
Full Text Search... Done
linux-dtb-edge-rk3568-odroid/now 23.05.1--6.3.4-S17f2-Db165-P80b4-C323dHfe66-HK01ba-Vc222-B9c18 arm64 [installed,local]
  Armbian Linux edge DTBs version "6.3.4" git revision "17f2d782f18c9a49943ea723d7628da1837c9204" codename "Hurr durr Ima ninja sloth" drivers hash "b165677e9cfc7376" patches hash "80b43c0ea45182e1" .config hash "323dfc8836b51fe8" .config hook hash "fe661159ee64825e" variables hash "" framework bash hash "9c188aa4807ed506" in /boot/dtb-6.3.4-rk3568-odroid

linux-image-edge-rk3568-odroid/now 23.05.1--6.3.4-S17f2-Db165-P80b4-C323dHfe66-HK01ba-Vc222-B9c18 arm64 [installed,local]
  Armbian Linux edge kernel image version "6.3.4" git revision "17f2d782f18c9a49943ea723d7628da1837c9204" codename "Hurr durr Ima ninja sloth" drivers hash "b165677e9cfc7376" patches hash "80b43c0ea45182e1" .config hash "323dfc8836b51fe8" .config hook hash "fe661159ee64825e" variables hash "" framework bash hash "9c188aa4807ed506"

-----------------------------------------------

apt search rk3568
Sorting... Done
Full Text Search... Done
linux-dtb-edge-rk3568-odroid/now 23.05.1--6.3.4-S17f2-Db165-P80b4-C323dHfe66-HK01ba-Vc222-B9c18 arm64 [installed,local]
  Armbian Linux edge DTBs version "6.3.4" git revision "17f2d782f18c9a49943ea723d7628da1837c9204" codename "Hurr durr Ima ninja sloth" drivers hash "b165677e9cfc7376" patches hash "80b43c0ea45182e1" .config hash "323dfc8836b51fe8" .config hook hash "fe661159ee64825e" variables hash "" framework bash hash "9c188aa4807ed506" in /boot/dtb-6.3.4-rk3568-odroid

linux-headers-edge-rk3568-odroid/bookworm,now 23.02.2 arm64 [installed]
  Linux kernel headers for 6.1.12-rk3568-odroid on arm64 edge

linux-image-edge-rk3568-odroid/now 23.05.1--6.3.4-S17f2-Db165-P80b4-C323dHfe66-HK01ba-Vc222-B9c18 arm64 [installed,local]
  Armbian Linux edge kernel image version "6.3.4" git revision "17f2d782f18c9a49943ea723d7628da1837c9204" codename "Hurr durr Ima ninja sloth" drivers hash "b165677e9cfc7376" patches hash "80b43c0ea45182e1" .config hash "323dfc8836b51fe8" .config hook hash "fe661159ee64825e" variables hash "" framework bash hash "9c188aa4807ed506"

linux-source-6.1.12-edge-rk3568-odroid/bookworm,bookworm 6.1.12-edge-rk3568-odroid+23.02.2 all
  This package provides the source code for the Linux kernel 6.1.12


-----------------------------------------------


ls -lah /usr/src/
total 28K
drwxr-xr-x  7 root root 4,0K Aug 14 09:35 .
drwxr-xr-x 11 root root 4,0K Mai 17 00:41 ..
drwxr-xr-x  4 root root 4,0K Aug 12 13:11 linux-headers-6.1.0-11-arm64
drwxr-xr-x  4 root root 4,0K Aug 12 13:10 linux-headers-6.1.0-11-common
drwxr-xr-x 25 root root 4,0K Aug 14 08:04 linux-headers-6.1.12-rk3568-odroid
lrwxrwxrwx  1 root root   23 Aug  8 13:18 linux-kbuild-6.1 -> ../lib/linux-kbuild-6.1
drwxrwxr-x 27 root root 4,0K Feb 18 00:33 linux-source-6.1.12-rk3568-odroid
drwxr-xr-x  2 root root 4,0K Aug 12 13:11 pivccu-1.0.82

When I plug it in, I see "PHY PLL not locked" in dmesg.

If I boot with it plugged in, I see the Hard Kernel logo, then the screen turns off as Armbian boots.

I booted into the Ubuntu 20.04 Gnome image provided by HardKernel and that one works.

1. What could I change to allow this display to be detected?

2. Can I just force the board to boot with output to 1024x768@60. I just need the output.

Thanks all.

If there are other users who use a Samsung SSD 980 PRO 2TB, they may also be interested in following this link: https://www.pugetsystems.com/support/guides/critical-samsung-ssd-firmware-update/

apt update && apt upgrade

is the correct way to install updates?

When I run that from a Armbian 23.02.2 system I will get a Ubuntu 22.04 afterwards.

before:

cat /etc/issue
Armbian 23.02.2 Jammy \l

after:
 

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.2 LTS
Release:        22.04
Codename:       jammy

Similar question: What is the intended way to do an armbian upgrade? I did not find any hint in the documentation. In my current use case installing all from scratch would not be a big issue since I use the odroid to run lxd containers on a separate disk but if someone installs and configures a lot of software a fresh reinstall is maybe a big task.

Thanks

• Why does /dev/rga not exist?
• USB-OTG does not seem to be working at the moment?
• Is MPP enabled in the current kernel?
• When is SPI boot coming out? 

Still love armbian though!

it works great but after installing OMV using armbian-config and rebooting the is no network available.

If i run ap addr i get for the LAN adapter following: eth0: <BROADCAST.MULTICAST> mtu 1500 qdisc noo state DOWN qlen 1000

How can this be fixed?

When I reboot the system it gets stuck on network configuration writing "A start job is running for Wait for Network to be Configured.

I wait two minutes and then the system boots without network.

The only chance to get network back is to run omv-firstaid and configure it or run following commands in the terminal

ip link set dev eth0 up

dhclient eth0

This command gives warning: /etc/resolvcon/update.d/libc: Warning: /etc/resolv.conf is not symbolic link to /run/resolvconf/resolv.conf

Any help would be highly appreciated.

first of all: THANKS for the armbian project!

My issue is with an M1, fresh jammy xfce install on an sd-card.

NVME is installed (can be accessed after mounting it manually, no issues there)

Wishing to move system to this /dev/nvme0n1, keeping boot on the sdcard, as I understand this being the only viable option, currently.

When using armbian-install, selectin option 1 "Boot from SD - system on SATA, USB or NVMe" and confiming, next is an error message:

---

There is not enough free capacity on /dev/nvme0n1. Please check your device.

---

Did so, tried creating an empty (linux) file system, fat etc, accessible using mount, still the same error.

I am pretty sure I am doing something wrong and I'm missing something completely, could someone please help me out?

Thanks so much 🙂

How can I update to the new nightly repo os ?

https://github.com/armbian/os

# PLEASE DO NOT EDIT THIS FILE
BOARD=odroidm1
BOARD_NAME="ODROID M1"
BOARDFAMILY=rk3568-odroid
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=1a8daf0
VERSION=23.02.2
LINUXFAMILY=rk3568-odroid
ARCH=arm64
IMAGE_TYPE=nightly
BOARD_TYPE=wip
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
BRANCH=edge

Thanks !

Some weeks ago, I installed the kinetic version. It was rooted on the nvme drive and was working decently. After some explanations on this forum, I decided to install

the LTS version.

I burned a new SD card, inserted it and powered on.

I was never prompt about where to install the system. After installation, the df command shows that the system is installed on the sd card.

I can see nvme partitions in /dev but they aren't mounted.

nvme is partitionned in two parts : one for the system, the other one is crypted and dedicated to data.

How should I do?

Thanks

Julien

running Armbian_22.11.2_Odroidm1_bullseye_edge_6.1.0.img.xz + updates.

I saw in other post (/topic/17418-cameras-with-rock-pi-4-c/😞

Quote

$ sudo armbian-config

Then select System > Hardware > rpi-cam-imx219

But I do not see any Hardware menu in System.
I had a look to armbian-config and saw that there is a lot of device-specific code and probably odroidm1 is not supported yet.

Also I searched for some DTB that may work, but none is shipped with the current kernel:

Quote

$ apt-file search imx219.dtb | cut -d : -f 1 | sort | uniq | grep linux-image-edge-rk3568-odroid

is empty.

Should I add explicit support like in this patch: https://github.com/armbian/build/pull/1482/files?

Or there are more modern way to add cold-pluggable hardware?

Thanks in advance for your suggestions!

New to the forum, so apologies if the questions are answered elsewhere, but please redirect me if they are.

I have identified a bug in the `armbian-install` script in the current Bullseye Edge image (Dec 19,2022)  that prevents it showing NVMe targets in the installation prompt if they don't have a valid filesystem on them.

This appears to have been fixed on the 19th of December in this commit (the grep for filesystems was removed from the lsblk command that returns valid partitions).
https://github.com/armbian/build/commit/893ed2347d97af574becf69dee1166a1bf933081#diff-8752ea87e0340f217187b70f7b08735d872a14c0467d02a6285222e594db3299L635-R635

I am not sure if it's a coincidence that these are the same date, but the Bullseye image downloaded today still has the older version of the script that includes the 'grep' for filesystems.

I have a workaround for my immediate issue (mkfs.ext4 on the NVMe partition so the installer detects it), but thought this may be impacting other users of Odroid M1 as they are likely installing on the NVMe.

If I need to raise this elsewhere, eg. github issue etc. please let me know the process.

Thanks!

  CC [M]  /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/core/rtw_beamforming.o
  CC [M]  /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/core/rtw_odm.o
  CC [M]  /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/core/efuse/rtw_efuse.o
  CC [M]  /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.o
/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.c: In function ‘rtw_change_ifname’:
/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.c:2183:28: warning: passing argument 1 of ‘_rtw_memcpy’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
 2183 |         _rtw_memcpy(pnetdev->dev_addr, padapter->eeprompriv.mac_addr, ETH_ALEN);
      |                     ~~~~~~~^~~~~~~~~~
/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.c:807:24: note: expected ‘void *’ but argument is of type ‘const unsigned char *’
  807 | void _rtw_memcpy(void* dst, const void* src, u32 sz)
      |                  ~~~~~~^~~
/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.c: In function ‘rtw_random32’:
/var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.c:2310:16: error: implicit declaration of function ‘prandom_u32’; did you mean ‘prandom_u32_max’? [-Werror=implicit-function-declaration]
 2310 |         return prandom_u32();
      |                ^~~~~~~~~~~
      |                prandom_u32_max
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:250: /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/os_dep/osdep_service.o] Error 1
make[1]: *** [Makefile:1992: /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-rc5-rk3568-odroid'

Same issue, if I try to compile the driver manually:

  CC [M]  /home/astrodroid/rtl8812au/core/efuse/rtw_efuse.o
  CC [M]  /home/astrodroid/rtl8812au/os_dep/osdep_service.o
/home/astrodroid/rtl8812au/os_dep/osdep_service.c: In function ‘rtw_random32’:
/home/astrodroid/rtl8812au/os_dep/osdep_service.c:2591:16: error: implicit declaration of function ‘prandom_u32’; did you mean ‘prandom_u32_max’? [-Werror=implicit-function-declaration]
 2591 |         return prandom_u32();
      |                ^~~~~~~~~~~
      |                prandom_u32_max
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:250: /home/astrodroid/rtl8812au/os_dep/osdep_service.o] Error 1
make[1]: *** [Makefile:1992: /home/astrodroid/rtl8812au] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-rc5-rk3568-odroid'

Which package I missed to be installed, that this function may be available. With the original Odroid M1 Ubuntu LTS 22.04 and Linux 5.19 this package could be installed.

Thx