gounthar

If I were to try a SoQuartz blade/Quartz64 these days, where could I find a recent image? I haven't been able to find any in the download page. Or should I use another image that would work for this model? Thanks.

Thanks.

I'm happy to see the support for this board is progressing. 🤗 @tiziano000, where did you find an adapter to connect to the GPIO pins? I have an SPI screen that I can't connect for the time being because of the strange (to me) spacing of the GPIO pins. 🤷‍♂️

Hello there, I'm trying to get an i2c ssd1306 screen to work with my Radxa Zero, without much luck for the time being. https://paste.armbian.com/cirulemeho I found two i2c devices, 3 and 5. sudo i2cdetect -y -r 3 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- sudo i2cdetect -y -r 5 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- I think the 5 is for HDMI, right? Would the UU for the 3 mean my screen is not correctly connected or detected? Thanks.

I also have a cgroup problem, on a more recent version: lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Armbian 23.11.2 bookworm Release: 12 Codename: bookworm uname -a Linux k3s-control-plane 6.1.68-current-bcm2711 #1 SMP PREEMPT Sun Dec 17 11:40:38 UTC 2023 aarch64 GNU/Linux déc. 29 21:30:12 k3s-control-plane k3s[3689]: I1229 21:30:12.173705 3689 server.go:156] Version: v1.28.4+k3s2 déc. 29 21:30:12 k3s-control-plane k3s[3689]: I1229 21:30:12.174299 3689 server.go:158] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK="" déc. 29 21:30:12 k3s-control-plane k3s[3689]: time="2023-12-29T21:30:12+01:00" level=info msg="To join server node to cluster: k3s server -s https://192.168.1.138:6443 -t ${SERVER_NO> déc. 29 21:30:12 k3s-control-plane k3s[3689]: time="2023-12-29T21:30:12+01:00" level=info msg="Agent node token is available at /var/lib/rancher/k3s/server/agent-token" déc. 29 21:30:12 k3s-control-plane k3s[3689]: time="2023-12-29T21:30:12+01:00" level=info msg="To join agent node to cluster: k3s agent -s https://192.168.1.138:6443 -t ${AGENT_NODE_> déc. 29 21:30:12 k3s-control-plane k3s[3689]: time="2023-12-29T21:30:12+01:00" level=info msg="Wrote kubeconfig /etc/rancher/k3s/k3s.yaml" déc. 29 21:30:12 k3s-control-plane k3s[3689]: time="2023-12-29T21:30:12+01:00" level=info msg="Run: k3s kubectl" déc. 29 21:30:12 k3s-control-plane k3s[3689]: time="2023-12-29T21:30:12+01:00" level=fatal msg="failed to find memory cgroup (v2)" déc. 29 21:30:12 k3s-control-plane systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE I have modified the /boot/firmware/config.txt and rebooted, but it was not enough... cat /boot/firmware/config.txt # For more options and information see # http://rptl.io/configtxt # Some settings may impact device functionality. See link above for details # For k3s (see https://github.com/k3s-io/k3s/issues/970#issuecomment-548409262) cgroup_memory=1 cgroup_enable=memory

Hi there, Has anyone tried openRGB with armbian? I found a few references to Raspberry Pi and openRGB, but nothing really usable. I would like to build a Kubernetes cluster and use an RGB fan to display the status of the cluster (and of course try to cool it down). Thanks.

Where did you find the image? Thanks.

Apparently, Paris, France.

Good to know, thank you, I'll try that.

Thank you @balbes150. I guess there is no other alternative to the existing image? I have to rewrite everything with the new image, I can't update the board with the latest kernel because it's not official yet.?

I have the same kind of problem, trying to build a rtl8821CU module for the Rock5B. I have installed the whole firmware package through armbian-config . Then: sudo apt update sudo apt upgrade sudo apt install build-essential dkms sudo apt install git git clone https://github.com/whitebatman2/rtl8821CU.git cd rtl8821CU sudo make make ARCH=aarch64 CROSS_COMPILE= -C /lib/modules/6.2.0-rc1-station-m6/build M=/home/poddingue/rtl8821CU modules make[1]: Entering directory '/usr/lib/modules/6.2.0-rc1-station-m6/build' make[1]: *** No rule to make target 'modules'. Stop. make[1]: Leaving directory '/usr/lib/modules/6.2.0-rc1-station-m6/build' make: *** [Makefile:1923: modules] Error 2 but it fails... `uname -r` gives me `6.2.0-rc1-station-m6`. ll /lib/modules/6.2.0-rc1-station-m6/ total 1392 drwxr-xr-x 11 root root 4096 Mar 20 15:19 kernel -rw-r--r-- 1 root root 320711 Mar 17 14:22 modules.alias -rw-r--r-- 1 root root 327286 Mar 17 14:22 modules.alias.bin -rw-r--r-- 1 root root 16981 Mar 17 14:22 modules.builtin -rw-r--r-- 1 root root 37042 Mar 17 14:22 modules.builtin.alias.bin -rw-r--r-- 1 root root 18873 Mar 17 14:22 modules.builtin.bin -rw-r--r-- 1 root root 117401 Mar 17 14:22 modules.builtin.modinfo -rw-r--r-- 1 root root 79754 Mar 17 14:22 modules.dep -rw-r--r-- 1 root root 123183 Mar 17 14:22 modules.dep.bin -rw-r--r-- 1 root root 243 Mar 17 14:22 modules.devname -rw-r--r-- 1 root root 38207 Mar 17 14:22 modules.order -rw-r--r-- 1 root root 703 Mar 17 14:22 modules.softdep -rw-r--r-- 1 root root 136364 Mar 17 14:22 modules.symbols -rw-r--r-- 1 root root 170537 Mar 17 14:22 modules.symbols.bin

Thank you, I should try that.

My WaveShare hat may be faulty. 🤷‍♂️

Thanks balbes150. After a few reboots, the boards started to boot on the NVMe. 🤔 The image was Armbian_23.02.0-trunk_Rock-5b_sid_edge_6.2.0.img .

Thanks for this tool. I'm trying to use it on a NanoPi Duo2 with I2C and SPI displays, but I'm struggling.

Hi there 👋 I'm using a NanoPi Duo2 with Armbian 21.08.1 Bullseye and Linux jenkins-agent-arm32 5.15.93-sunxi #23.02.2 SMP Fri Feb 17 23:49:46 UTC 2023 armv7l GNU/Linux I want to use an SPI screen on it, but I don't know which library to use to handle the GPIO... I've tested quite a few and none of them seem to work. I have enabled SPI and I2C in `armbian-config` and `sudo i2cdetect -y 0` works (even if nothing is found), but what is the next step? sudo i2cdetect -y 0 [sudo] password for poddingue: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- poddingue@jenkins-agent-arm32:~$ ls /dev/i2c* /dev/i2c-0 What library/tool should I install to get the `gpio` command for example? Thanks.

No, I don't, but I should.

Here is the result of my test: http://ix.io/4sgx .

I failed... I installed the image, booted, launched armbian-config, chose the option write to NVMe/MPD, and after the poweroff, I removed the SDCard. Unfortunately, I then get: done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. [...] Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell! The board still boots fine once I put the SDCard back in.

Thanks a lot for taking the time to answer @balbes150. 🙏 The writing on the NVMe is taking place now... But for the latest image, I can't configure WiFi. 🤔

Stupid me had a problem in `/etc/fstab`. Once I got rid of the problem, I got the network (and the rest) back as usual. Well... 🤷‍♂️

Thanks a lot for taking the time to answer @balbes150. 🙏 I'll try that.

Hi, I don't know if this has anything to do with it, but I had a functional Armbian distro on the Rock5B working from the SDCard, and after installing it on the NVMe (which does not boot), I restarted the board from the SDCard (after having removed the NVMe), and I lost my network connections. How could I get the network back on? And the UART regularly asks me: Give root password for maintenance (or press Control-D to continue): Give root password for maintenance (or press Control-D to continue): Something must be broken... root@rock-5b:~# uname -a Linux rock-5b 5.10.110-rockchip-rk3588 #23.02.2 SMP Fri Feb 17 23:59:20 UTC 2023 aarch64 GNU/Linux root@rock-5b:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enP4p65s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:e0:4c:68:03:e4 brd ff:ff:ff:ff:ff:ff 3: wlx4401bb082c96: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 44:01:bb:08:2c:96 brd ff:ff:ff:ff:ff:ff root@rock-5b:~# ifup enP4p65s0 ifup: unknown interface enP4p65s0 root@rock-5b:~# cat /etc/network/interfaces source /etc/network/interfaces.d/* # Network is managed by Network manager auto lo iface lo inet loopback root@rock-5b:~# ls /sys/class/net enP4p65s0 lo wlx4401bb082c96 root@rock-5b:~# `armbian-config` does not give me a way to launch a wireless connection (no menu), and the network configuration file in `armbian-config` does not reflect what is in `/etc/network`.

Hi there, My Rock5B worked well with Armbian until I tried to migrate to an NVMe. Here is a boot log without any SDCard: Now, if I put back the SDCard, I get: That does look the same to me. Why can't it find the SDCard? Thanks.

I have no idea unfortunately. But this board is finicky when it comes to power... It worked well with a dummy 5V power supply for me, and even with my PinePower WC3.0 port. I then added an NVME, and since then, it does not want to boot anymore, with or without NVME...