I am not able to make Radxa Camera 8M to work with Armbian_24.5.3_Radxa-zero3_bookworm_vendor_6.1.43_minimal.img and Armbian_24.5.1_Radxa-zero3_noble_vendor_6.1.43.img

gst-launch-1.0 v4l2src device=/dev/video0 io-mode=4 ! videoconvert ! video/x-raw,format=NV12,width=1920,height=1080 ! jpegenc ! multifilesink location=/home/a2t/test.jpg
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.
Additional debug info:
../libs/gst/base/gstbasesrc.c(3132): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
streaming stopped, reason not-negotiated (-4)
Execution ended after 0:00:00.001604801
Setting pipeline to NULL ...
Freeing pipeline ...

root@radxa-zero3:~# v4l2-ctl -i /dev/video0 --list-formats
VIDIOC_S_INPUT: failed: Inappropriate ioctl for device
ioctl: VIDIOC_ENUM_FMT
        Type: Video Capture Multiplanar

        [0]: 'UYVY' (UYVY 4:2:2)
        [1]: '422P' (Planar YUV 4:2:2)
        [2]: 'NV16' (Y/UV 4:2:2)
        [3]: 'NV61' (Y/VU 4:2:2)
        [4]: 'YM16' (Planar YUV 4:2:2 (N-C))
        [5]: 'NV21' (Y/VU 4:2:0)
        [6]: 'NV12' (Y/UV 4:2:0)
        [7]: 'NM21' (Y/VU 4:2:0 (N-C))
        [8]: 'NM12' (Y/UV 4:2:0 (N-C))
        [9]: 'YU12' (Planar YUV 4:2:0)
        [10]: 'YM24' (Planar YUV 4:4:4 (N-C))

root@radxa-zero3:~# v4l2-ctl --device=/dev/video0 --all
Driver Info:
        Driver name      : rkisp_v5
        Card type        : rkisp_mainpath
        Bus info         : platform:rkisp-vir0
        Driver version   : 2.4.0
        Capabilities     : 0x84201000
                Video Capture Multiplanar
                Streaming
                Extended Pix Format
                Device Capabilities
        Device Caps      : 0x04201000
                Video Capture Multiplanar
                Streaming
                Extended Pix Format
Media Driver Info:
        Driver name      : rkisp-vir0
        Model            : rkisp0
        Serial           :
        Bus info         : platform:rkisp-vir0
        Media version    : 6.1.43
        Hardware revision: 0x00000000 (0)
        Driver version   : 6.1.43
Interface Info:
        ID               : 0x0300000e
        Type             : V4L Video
Entity Info:
        ID               : 0x0000000d (13)
        Name             : rkisp_mainpath
        Function         : V4L2 I/O
        Pad 0x01000010   : 0: Sink
          Link 0x02000011: from remote pad 0x1000004 of entity 'rkisp-isp-subdev' (Unknown V4L2 Sub-Device): Data, Enabled
Priority: 2
Format Video Capture Multiplanar:
        Width/Height      : 0/0
        Pixel Format      : ''
        Field             : Any
        Number of planes  : 0
        Flags             :
        Colorspace        : Default
        Transfer Function : Default
        YCbCr/HSV Encoding: Default
        Quantization      : Default
Selection Video Capture: crop, Left 0, Top 0, Width 0, Height 0, Flags:
Selection Video Capture: crop_bounds, Left 0, Top 0, Width 800, Height 600, Flags:
Selection Video Output: crop, Left 0, Top 0, Width 0, Height 0, Flags:
Selection Video Output: crop_bounds, Left 0, Top 0, Width 800, Height 600, Flags:

What should be done to get the image 

eMMC is not detected on Radxa Zero 3W when booting Armbian Trixie from SD card. The eMMC controller initializes but fails to find power supply regulators, resulting in no block device being created.

Hardware

Board: Radxa Zero 3W (4GB RAM / 8GB eMMC)

Boot media: SD card

Image

Armbian Trixie (current kernel) for Radxa Zero 3

DTB: rk3566-radxa-zero3.dtb

Symptoms

WiFi and SD card work fine

eMMC does not appear in lsblk

dmesg shows the SDHCI controller at fe310000.mmc loading but failing regulator lookups:
 

sdhci-dwcmshc fe310000.mmc: Looking up vmmc-supply property in node /mmc@fe310000 failed
sdhci-dwcmshc fe310000.mmc: Looking up vqmmc-supply property in node /mmc@fe310000 failed
mmc0: SDHCI controller on fe310000.mmc [fe310000.mmc] using ADMA

No mmcblk0 device is created. Only the SD card (mmcblk1) appears.
 

Expected Behavior

eMMC should appear as /dev/mmcblk0 in lsblk.

Notes

The DTB (rk3566-radxa-zero3.dtb) appears to be missing vmmc-supply and vqmmc-supply regulator definitions for the eMMC node (/mmc@fe310000)

A rk3566-radxa-zero-3w.dtb (with proper 3W-specific regulators) does not exist in the image — only rk3566-radxa-zero3.dtb and rk3566-radxa-zero3-ap6212.dtb are present

Related: #8776 (wrong DTB filename for Zero 3W)

This causes me to not be able to install to EMMC using armbian-install

I created partision on the usb-disk with ambian-install, and after that trying to select 8 (download and install clean image), but it can't find any image for my board. I have no eMMC on my 4GB ram radaxa zero 3Wso I run from SD-card. 

1. Issues

• All branches (Vendor, Current, Edge)
  • Depending on cable orientation, USB3 devices register inconsistently on either:  
    • Bus 001 → USB 2.0 (480M)  
    • Bus 002 → USB 3.0 (5000M)  
  • Reference: previous forum post
     
• Armbian dfb7c4f: Current (6.12) & Edge (6.16)
  • My unpowered USB3 hub fails to work at all (it's fine on Radxa's builds & Vendor).
  • On touch, the hub feels more electrically charged than on vendor builds.
  • Plugging in a single device works, but it will still suffer from the cable “upside-down” speed bug.

2. Logs

• Vendor branch
  • armbianmonitor -u: link
• Edge branch (same behavior as Current)
  • armbianmonitor -u: link
• Tried with U-Boot master and ATF mainline → no improvement  
  • build script diffs: link
  • U-Boot: 0c558bb
  • ATF: still v2.13, cannot set branch:master (or 9ee2ff1 directly) as Armbian's build script will fail
• lsusb {-t} outputs: link
• Build command used:

    ./compile.sh build BOARD=radxa-zero3 BRANCH=edge RELEASE=trixie \
      BUILD_DESKTOP=yes BUILD_MINIMAL=no \
      DESKTOP_ENVIRONMENT=gnome \
      DESKTOP_APPGROUPS_SELECTED="browsers desktop_tools" \
      KERNEL_CONFIGURE=no

3. Notes

• My USB-PD passthrough adapter’s ethernet device does not appear on the OTG port (seems broken on both Armbian & Radxa vendor images).
• No relevant fixes appear left in the kernel repos:
  • Linux mainline: rk356
  • linux-rockchip: rk356

4. Device Tree References

• Radxa U-Boot fork (2024.10, next-dev branch)
  • rk3566.dtsi
  • rk3568-u-boot.dtsi
  • rk3566-radxa-zero3.dts
• u-boot-rockchip (merged into mainline)
  • rockchip-u-boot.dtsi
  • rk356x-u-boot.dtsi
  • rk3566-radxa-zero-3w-u-boot.dtsi

I think this is due to the DT overlays, but this is a new topic for me. Could somebody please help me or point towards the next steps?

I started by copying over the .dtbo files from the regular radxa official image, and putting them into the overlay-user folder in /boot. Then I enabled the radxa-zero3-tc358743.dtbo overlay, which gets the devices to show up.

I am following this guide from GEEKOM https://wiki.geekworm.com/X1300_Software, however, I keep getting ioctl errors when trying to set the EDID file on the Radxa Zero. On the Raspberry Pi, this was not an issue.

Here is the output of my media-ctl:

media-ctl -d /dev/media0 -p
Media controller API version 6.1.115

Media device information
------------------------
driver          rkisp-vir0
model           rkisp0
serial          
bus info        platform:rkisp-vir0
hw revision     0x0
driver version  6.1.115

Device topology
- entity 1: rkisp-isp-subdev (4 pads, 8 links, 0 routes)
            type V4L2 subdev subtype Unknown flags 0
            device node name /dev/v4l-subdev0
	pad0: SINK,MUST_CONNECT
		[stream:0 fmt:UYVY8_2X8/640x480 field:none colorspace:srgb
		crop.bounds:(0,0)/640x480
		crop:(0,0)/640x480]
		<- "rkisp-csi-subdev":1 [ENABLED]
		<- "rkisp_rawrd0_m":0 []
		<- "rkisp_rawrd2_s":0 []
	pad1: SINK
		<- "rkisp-input-params":0 [ENABLED]
	pad2: SOURCE
		[stream:0 fmt:YUYV8_2X8/640x480 field:none colorspace:smpte170m quantization:full-range
		crop.bounds:(0,0)/640x480
		crop:(0,0)/640x480]
		-> "rkisp_mainpath":0 [ENABLED]
		-> "rkisp_selfpath":0 [ENABLED]
		-> "rkisp_iqtool":0 [ENABLED]
	pad3: SOURCE
		-> "rkisp-statistics":0 [ENABLED]

- entity 6: rkisp-csi-subdev (6 pads, 5 links, 0 routes)
            type V4L2 subdev subtype Unknown flags 0
            device node name /dev/v4l-subdev1
	pad0: SINK,MUST_CONNECT
		[stream:0 fmt:UYVY8_2X8/640x480 field:none colorspace:srgb]
		<- "rockchip-csi2-dphy0":1 [ENABLED]
	pad1: SOURCE,MUST_CONNECT
		[stream:0 fmt:UYVY8_2X8/640x480 field:none colorspace:srgb]
		-> "rkisp-isp-subdev":0 [ENABLED]
	pad2: SOURCE
		-> "rkisp_rawwr0":0 [ENABLED]
	pad3: SOURCE
	pad4: SOURCE
		-> "rkisp_rawwr2":0 [ENABLED]
	pad5: SOURCE
		-> "rkisp_rawwr3":0 [ENABLED]

- entity 13: rkisp_mainpath (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video0
	pad0: SINK
		<- "rkisp-isp-subdev":2 [ENABLED]

- entity 19: rkisp_selfpath (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video1
	pad0: SINK
		<- "rkisp-isp-subdev":2 [ENABLED]

- entity 25: rkisp_rawwr0 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video2
	pad0: SINK
		<- "rkisp-csi-subdev":2 [ENABLED]

- entity 31: rkisp_rawwr2 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video3
	pad0: SINK
		<- "rkisp-csi-subdev":4 [ENABLED]

- entity 37: rkisp_rawwr3 (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video4
	pad0: SINK
		<- "rkisp-csi-subdev":5 [ENABLED]

- entity 43: rkisp_iqtool (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video5
	pad0: SINK
		<- "rkisp-isp-subdev":2 [ENABLED]

- entity 49: rkisp_rawrd0_m (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video6
	pad0: SOURCE
		-> "rkisp-isp-subdev":0 []

- entity 55: rkisp_rawrd2_s (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video7
	pad0: SOURCE
		-> "rkisp-isp-subdev":0 []

- entity 61: rkisp-statistics (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video8
	pad0: SINK
		<- "rkisp-isp-subdev":3 [ENABLED]

- entity 67: rkisp-input-params (1 pad, 1 link)
             type Node subtype V4L flags 0
             device node name /dev/video9
	pad0: SOURCE
		-> "rkisp-isp-subdev":1 [ENABLED]

- entity 73: rockchip-csi2-dphy0 (2 pads, 2 links, 0 routes)
             type V4L2 subdev subtype Unknown flags 0
             device node name /dev/v4l-subdev2
	pad0: SINK,MUST_CONNECT
		[stream:0 fmt:UYVY8_2X8/640x480@10000/600000 field:none colorspace:srgb]
		<- "m00_b_tc35874x 2-000f":0 [ENABLED]
	pad1: SOURCE,MUST_CONNECT
		-> "rkisp-csi-subdev":0 [ENABLED]

- entity 76: m00_b_tc35874x 2-000f (1 pad, 1 link, 0 routes)
             type V4L2 subdev subtype Sensor flags 0
             device node name /dev/v4l-subdev3
	pad0: SOURCE
		[stream:0 fmt:UYVY8_2X8/640x480@10000/600000 field:none colorspace:srgb]
		[dv.caps:BT.656/1120 min:1x1@0 max:10000x10000@310000000 stds:CEA-861,DMT,CVT,GTF caps:interlaced,progressive,reduced-blanking,custom]
		[dv.query:no-link]
		[dv.current:BT.656/1120 640x480p59 (800x525) stds:CEA-861,DMT flags:has-cea861-vic]
		-> "rockchip-csi2-dphy0":0 [ENABLED]

The GEEKOM does seem to require some GPIOs, as shown in the second picture from this link https://geekworm.com/products/x1301, however, these all seem to be for audio functionality, which I have disabled. I currently only have the GEEKOM X1301 connected through the CSI Port to the Radxa Zero, as it physically cannot have the GPIOs and the CSI port connected at the same time.

Here is the output of my /dev folder

autofs           crypto    fuse         hugepages    input  loop3         mem          port    rga     stdout   tty13  tty20  tty28  tty35  tty42  tty5   tty57  tty7      urandom      vcs2   vcsa3  vcsu4        video0  video8
block            cuse      gpiochip0    hwrng        iomux  loop4         mmcblk1      ppp     rk_cec  sw_sync  tty14  tty21  tty29  tty36  tty43  tty50  tty58  tty8      v4l          vcs3   vcsa4  vcsu5        video1  video9
btrfs-control    disk      gpiochip1    i2c-0        kmsg   loop5         mmcblk1p1    psaux   rtc     tty      tty15  tty22  tty3   tty37  tty44  tty51  tty59  tty9      v4l-subdev0  vcs4   vcsa5  vcsu6        video2  watchdog
bus              dma_heap  gpiochip2    i2c-2        kvm    loop6         mmcblk1p2    ptmx    rtc0    tty0     tty16  tty23  tty30  tty38  tty45  tty52  tty6   ttyFIQ0   v4l-subdev1  vcs5   vcsa6  vfio         video3  watchdog0
cec0             dri       gpiochip3    i2c-3        log    loop7         mpp_service  pts     shm     tty1     tty17  tty24  tty31  tty39  tty46  tty53  tty60  ttyS1     v4l-subdev2  vcs6   vcsu   vga_arbiter  video4  zero
char             fb0       gpiochip4    i2c-6        loop0  loop-control  mqueue       ram0    snd     tty10    tty18  tty25  tty32  tty4   tty47  tty54  tty61  ubi_ctrl  v4l-subdev3  vcsa   vcsu1  vhci         video5  zram0
console          fd        gpiochip5    iio:device0  loop1  mapper        net          random  stderr  tty11    tty19  tty26  tty33  tty40  tty48  tty55  tty62  uhid      vcs          vcsa1  vcsu2  vhost-net    video6  zram1
cpu_dma_latency  full      hdmi_hdcp1x  initctl      loop2  media0        null         rfkill  stdin   tty12    tty2   tty27  tty34  tty41  tty49  tty56  tty63  uinput    vcs1         vcsa2  vcsu3  vhost-vsock  video7  zram2

This is the error that I get when I run the command to set the EDID file.

v4l2-ctl -d /dev/v4l-subdev3 --set-edid=file=1080P60EDID.txt
VIDIOC_SUBDEV_S_CLIENT_CAP: failed: Inappropriate ioctl for device

Is there any way that I can resolve this issue? The HAT's power LED doesn't light up for some reason, and the device also isn't detected when I plug in any other devices HDMI out into the HDMI IN on the HAT.

I bought a Zero 3w about a week ago and have been beating this horse most of the time. I can't get the device to connect via USB. A or C. When I try to connect (radxa.local) it will always go through wifi. If I have wlan0 disabled or even my internet off it just will NOT connect. It clearly is using wifi to connect even if I use the hostname. Maybe this is something simple but I and another engineer I work with have been scratching our heads about it. The obligatory AI search was an endless loop of everything we had already tried.

Anybody have any advice?

I was experience some strange things with two similar devices, the first I installed in february this year, mesa v.24.x and EGL 1.4 and it was working fine

The other one I installed this week and it turns out that it uses mesa v.25.x and EGL 1.5, although performance was great with most 3D apps (like glmark2) I had poor performance under sway/kitty or the retroarch menu for instance (something like 15 fps).

It took me a few days to find a solution so if you have similar issues please try installing mesa with the kisak repository as it fixed my problems

sudo add-apt-repository ppa:kisak/kisak-mesa -y
sudo apt update
sudo apt upgrade

the last command should upgrade mesa to a more recent version than what's in the ubuntu ppa.

System info https://paste.next.armbian.com/savaleceqe

The usual enable UART options (that I see with other boards) do not show up under armbian-config->System->Kernel->Manage Device Tree Overlays.  (In fact very little shows up there, all the usual SPI / i2c / w1 / usbhost etc are all missing).

I did decompile /boot/dtb/rockchip/rk3566-radxa-zero3.dtb to take a look at what in their, and UART1,2,3,4,5,6,7 along with other missing options armbian-config are their, but the references to other files look to be missing IF (and that's a big IF) I am understanding the dtb / dts correctly. 

Within /boot/dtb/rockchip/rk3566-radxa-zero3.dtb with the symbols stanza I see the following 

 __symbols__ {
    uart1 = "/serial@fe650000";
    uart2 = "/serial@fe660000";
    uart3 = "/serial@fe670000";
}

I'm assuming uart1 is referancing this section within the same file

serial@fe650000 { 
                compatible = "rockchip,rk3568-uart\0snps,dw-apb-uart";
                reg = <0x00 0xfe650000 0x00 0x100>;
                interrupts = <0x00 0x75 0x04>;
                clocks = <0x24 0x11f 0x24 0x11c>;
                clock-names = "baudclk\0apb_pclk";
                dmas = <0x44 0x02 0x44 0x03>;
                pinctrl-0 = <0xe7 0xe8>;
                pinctrl-names = "default";
                reg-io-width = <0x04>;
                reg-shift = <0x02>;
                status = "okay";
                phandle = <0x1a1>;
        };      

What I can't find are any file named rk3568-uart on my system, but I can find files like rk3576-uart*

Same goes for all the other missing items like i2c, spi, etc.

I have no idea if this is the reason.  But would love some help on this as I don;t want to move to a different distribution.

Thanks.

root@radxa-zero3:~# iw phy
Wiphy phy0
        wiphy index: 0
        max # scan SSIDs: 3
        max scan IEs length: 200 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports RSN-IBSS.
        Device supports AP-side u-APSD.
        Supported Ciphers:
                * WEP40 (00-0f-ac:1)
                * WEP104 (00-0f-ac:5)
                * TKIP (00-0f-ac:2)
                * CCMP-128 (00-0f-ac:4)
                * CMAC (00-0f-ac:6)
                * WPI-SMS4 (00-14-72:1)
        Available Antennas: TX 0 RX 0
        Supported interface modes:
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
                 * P2P-device
…

> get_capability pairwise
CCMP TKIP
> get_capability group
CCMP TKIP WEP104 WEP40
> get_capability key_mgmt
NONE IEEE8021X WPA-EAP WPA-PSK WPA-EAP-SUITE-B OWE DPP FT-PSK FT-EAP
> get_capability proto
RSN WPA
> get_capability auth_alg
OPEN SHARED LEAP SAE

Also the screen goes black when the app boots, is that a problem with X11/Wayland?

1. I can't "Create a loop password" as it'll instantly jump to the "armbian-security login:" prompt.
2. If I login with the default root:1234, I'll briefly see the welcome screen, followed by a very brief "waiting for the system to finish booting", then it's back to 1.

This occurs regardless of internet access (provided by a USB-C ethernet adapter, for which Armbian reports a valid LAN IP address).

/:  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
/:  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
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

and lsusb output

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 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 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

i checked the same hub with my windows labtop i was able to achieve USB 3.0 read and write speeds.

kindly guide me how to make the hub detect as USB 3.0 on armbain debian 12 Bookworm Server.

Here's what I see in dmesg that may be relevant:

...

[    9.329177] kernel: Bluetooth: Core ver 2.22
[    9.329247] kernel: NET: Registered PF_BLUETOOTH protocol family
[    9.329261] kernel: Bluetooth: HCI device and connection manager initialized
[    9.329281] kernel: Bluetooth: HCI socket layer initialized
[    9.329296] kernel: Bluetooth: L2CAP socket layer initialized
[    9.329337] kernel: Bluetooth: SCO socket layer initialized

...

[   11.165207] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 77.
[   11.165235] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 17.
[   11.165248] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 12.
[   11.165261] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 11.
[   11.165269] kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: clk_get failed!!!.
[   11.165326] kernel: [BT_RFKILL]: Request irq for bt wakeup host
[   11.165815] kernel: [BT_RFKILL]: ** disable irq
[   11.165979] kernel: [BT_RFKILL]: bt shut off power
[   11.166001] kernel: [BT_RFKILL]: bt_default device registered.
[   11.166198] kernel: input: bt-powerkey as /devices/platform/wireless-bluetooth/input/input2

...

OS: Armbian (24.8.4) aarch64 
Host: Radxa ZERO 3 
Kernel: 6.1.75-vendor-rk35xx 
Uptime: 5 mins 
Packages: 1358 (dpkg) 
Shell: bash 5.2.21 
Terminal: /dev/pts/0 
CPU: (4) @ 2.000GHz 
Memory: 1168MiB / 7686Mi

Reference Posts x2

I have this patch already in my /etc/systemd/journald.conf

I edited /etc/default/armbian-zram-config -> ZRAM_PERCENTAGE=10 but allotment size didn't increase after a reboot (~47M before as well). By default this variable was commented out

Filesystem                Size  Used Avail Use% Mounted on
tmpfs                     769M   24M  745M   4% /run
/dev/mmcblk1p2            116G   32G   84G  28% /
tmpfs                     3.8G  100K  3.8G   1% /dev/shm
tmpfs                     5.0M     0  5.0M   0% /run/lock
tmpfs                     3.8G  4.0K  3.8G   1% /tmp
/dev/md127                439G   65G  352G  16% /media/radxaRaid480gb
/dev/mmcblk1p1            256M  157M  100M  62% /boot
/dev/sdd1                 117G   37G   75G  34% /media/radxa128gb
/dev/zram1                 47M   46M     0 100% /var/log

Is there a way to get h264 encoding working with armbian OR do I have to use radxa oses (or the ubuntu version provided by Joshua Riek) ?

Thanks.

I read about raxda zero3E edge support, and

because I'm having problems with img-6.12.9+bpo-arm64-16k (wireguard dependency)

Do you think I could resonably try the edge version and then,

I understand that I have to install armbian-bsp-cli-radxa-zero3-edge linux-u-boot-radxa-zero3-edge linux-headers-edge-rockchip64

Is there more to install ? or less ? And, does I have to remove old (vendor) kernel version before ?

Thank you

And out of the box after installation I get the message
-bash: fork: retry: Resource temporarily unavailable
(I have to work through the com port, because because of this error ssh and the desktop cannot work)

I checked the performance of the equipment by installing Debian 11 from Radxa, the equipment works correctly (CPU RAM eMMC).

Has anyone encountered this problem?

I encounter a problem when I run the TCPDUMP command Here is the error

eth0: SIOCETHTOOL(ETHTOOL_GLINK) ioctl failed: Device or resource busy

Work like a charm with Radxa Debian OS, but on two Armbian same problem.

Someone knows why ?

Thanks

    After recent sudo apt update && sudo apt upgrade via armbian debian bookwork XFCE chromium and firefox breaks

its not updates for chromium or firefox as happens when i hold those packages from upgrading too

also on fresh sdcard flash/install  without full upgrade(just upgrading chromium and its dependencies via depository) chromium still works fine,

its something else in the depository that breaks it 

I have this display http://www.lcdwiki.com/4inch_HDMI_Display-C  and  touchscreen doesn't work.

I write dts file but apparently he is not a privelege and the touchscreen did not work.

Can  point out my mistakes when writing dts?

rockchip-ads7846.dts

Please help me with my  problem. I have a Radha board  zero 3w and I use the Armbian distrib.  24.8.1  . Everything works fine, except that I can't activate  SPI. In the Armbian-config menu there is no hardware section (I tried different flash cards and Armbian versions, the problem persists), I also tried to edit the armbianEnv.txt  and add overlays there, but I also did not have success. Tell me what else I can try. Activation works on the native distribution radxa debian.

the 3.3V is still available. i dont know if its only a configuration mistake or a bug. normaly after a kernel shutdown, the driver for rk817 should send i2c package to reset the 817. after that you need a power cycle to recover and restart.

https://paste.armbian.com/inibopomew

br

manuel

I’m using a Radxa Zero 3E with Armbian 24.8.1 Bookworm OS and trying to connect a device to Radxa via UART. However, I can’t seem to find the ttyAML0 interface. The only UART interfaces visible are ttyS1 and ttyFIQ0 , but neither works for my setup. I have connected the device to the UART_AO_A pins (pins 8 and 10).

Additionally, when I go to armbian-config -> System -> Hardware, no hardware appears on the screen.

Could this issue be related to the Armbian image I am using? I’ve already tried the b6 image, but it has a boot problem. I also noticed that the other official Radxa images are marked as pre-release.

Is there a specific image I should use for stable UART functionality, or is there a way to solve this issue on the current setup?

Any guidance on resolving the UART problem would be greatly appreciated!

Thanks in advance for your help!

When I inspect the normal datasources, it symlink to non-existent folder.