All Activity

Hey @Werner Thanks for quick reply. I tested with verbosity=7, may be correct fs driver is not loading? [ 4.103985] /dev/root: Can't open blockdev [ 4.108224] VFS: Cannot open root device "UUID=dc3421ab-734e-47cb-8f5d-5b8ffecf9484" or unknown-block(0,0): error -6 [ 4.118847] Please append a correct "root=" boot option; here are the available partitions: [ 4.127246] 0100 4096 ram0 [ 4.127265] (driver?) [ 4.133442] 0101 4096 ram1 [ 4.133458] (driver?) [ 4.139623] 0102 4096 ram2 [ 4.139639] (driver?) [ 4.145787] 0103 4096 ram3 [ 4.145803] (driver?) [ 4.151982] b300 15558144 mmcblk0 [ 4.151999] driver: mmcblk [ 4.158846] b301 1060864 mmcblk0p1 a9741697-01 [ 4.158866] [ 4.165738] List of all bdev filesystems: [ 4.169781] ext3 [ 4.169792] ext2 [ 4.171748] ext4 [ 4.173685] squashfs [ 4.175645] vfat [ 4.177929] fuseblk [ 4.179888] f2fs [ 4.182086] btrfs [ 4.184046] [ 4.187565] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 4.195841] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.43-current-sunxi #1 [ 4.203689] Hardware name: Allwinner sun8i Family [ 4.208406] Call trace: [ 4.208435] unwind_backtrace from show_stack+0x11/0x14 [ 4.216251] show_stack from dump_stack_lvl+0x37/0x42 [ 4.221341] dump_stack_lvl from panic+0xc9/0x278 [ 4.226080] panic from mount_root_generic+0x171/0x1f4 [ 4.231264] mount_root_generic from prepare_namespace+0x161/0x1ae [ 4.237491] prepare_namespace from kernel_init_freeable+0x1f9/0x20a [ 4.243893] kernel_init_freeable from kernel_init+0x21/0x100 [ 4.249686] kernel_init from ret_from_fork+0x11/0x1c [ 4.254774] Exception stack(0xc8821fb0 to 0xc8821ff8) [ 4.259847] 1fa0: 00000000 00000000 00000000 00000000 [ 4.268041] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 4.276231] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 4.282974] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- my next steps, - testing image from oldarchieve - experiment rebuilding armbian with kernel menuconfig?

Hm that should not be a BIG issue since H2+ and H3 are quite similar, just a few features were stripped IIRC. I don't know for their images but I assume there is something similar like Armbian has. Edit /boot/armbianEnv.txt and set verbosity to 7 to increase the output of the kernel while it is starting. So you may know why it is stuck. Overall I'd recommend to try some older images like https://fi.mirror.armbian.de/archive/nanopiduo/archive/ or https://fi.mirror.armbian.de/oldarchive/nanopiduo/archive/ and then bump kernel step by step via armbian-config to know where it starts failing.

Hi, For long (long) time I did not update my nano pi duo image, recently I changed microSD card and wanted start fresh with latest image. I have tried latest debian image and also tried building image for the BOARD target as `nanopiduo`, but in in both cases my board is stuck at ... U-Boot SPL 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-Va723-Bb703-R448a (Mar 09 2025 - 03:54:39 +0000) DRAM: 128 MiB Trying to boot from MMC1 ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-Va723-Bb703-R448a (Mar 09 2025 - 03:54:39 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi DUO DRAM: 128 MiB Core: 57 devices, 16 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial,usbkbd Out: serial Err: serial Net: No ethernet found. starting USB... No working controllers found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 5475 bytes read in 6 ms (890.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD 182 bytes read in 6 ms (29.3 KiB/s) Load fdt: /boot/dtb/sun8i-h2-plus-nanopi-duo.dtb 8431400 bytes read in 357 ms (22.5 MiB/s) 11476944 bytes read in 484 ms (22.6 MiB/s) Found mainline kernel configuration 36294 bytes read in 20 ms (1.7 MiB/s) Working FDT set to 43000000 504 bytes read in 17 ms (28.3 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo 504 bytes read in 17 ms (28.3 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo 4185 bytes read in 17 ms (240.2 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 45000000 Kernel image @ 0x42000000 [ 0x000000 - 0xaf1fd0 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 8431336 Bytes = 8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Working FDT set to 43000000 Loading Ramdisk to 497f5000, end 49fff6e8 ... OK Loading Device Tree to 42ee4000, end 42f55fff ... OK Working FDT set to 42ee4000 Starting kernel ... [ 2.314576] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 2.322869] CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.43-current-sunxi #1 [ 2.330722] Hardware name: Allwinner sun8i Family [ 2.335438] Call trace: [ 2.335467] unwind_backtrace from show_stack+0x11/0x14 [ 2.343286] show_stack from dump_stack_lvl+0x37/0x42 [ 2.348377] dump_stack_lvl from panic+0xc9/0x278 [ 2.353116] panic from mount_root_generic+0x171/0x1f4 [ 2.358299] mount_root_generic from prepare_namespace+0x161/0x1ae [ 2.364527] prepare_namespace from kernel_init_freeable+0x1f9/0x20a [ 2.370928] kernel_init_freeable from kernel_init+0x21/0x100 [ 2.376720] kernel_init from ret_from_fork+0x11/0x1c [ 2.381808] Exception stack(0xc8821fb0 to 0xc8821ff8) [ 2.386881] 1fa0: 00000000 00000000 00000000 00000000 [ 2.395074] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 2.403265] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 2.410060] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- In older images, CPU was detected as `Allwinner H2+`, however now it's detecting as H3. I have tried couple other SD cards, with same error. What config I can try to get my `nanopi duo` working? offtopic: I tried images available from friendlyelec drive, which are getting stuck at "Starting kernel".

I need to set these up: LAFVIN 2 4/2 8/3 2/3 5 Inch Tft Lcd Touch Display Screen Panel 320x240 Spi Serial Ili9341 Compatible With Arduino Uno R3/Mega2560 (To be used as an actual screen) Night Vision Camera ule for Raspberry Pi 4, Mini 5MP 1080P HD Video OV5647 Sensor Webcam Kit with Embedded IR-Cut They're listed according to how they're labeled in the online store. I tried multiple approach no to avail. Can anyone help me?

This doesn't exactly answer your question, but it may meet your need better... I experimented around with different fans & heatsink configurations. Using an official Debian image from Orange PI 5 Plus, I found that the PWM controlled fan changed speed pretty abruptly, and only at high temperatures. Their adjustment algorithm didn't apply any decent smoothing at all. It was very noisy, and the constant changes whenever I did anything made it very distracting. I ended up purchasing a 3rd party fan with two single-pin leads that I could connect to the GPIO's 3.3v (or 5v). And I have it mounted on a Geekworm case (N508 - made for the Orange PI 5 Plus), with a short heatsink over the ICs. That case had actually come with a fan that had a single 2-pin connector, so it was only good for 5v and about 5 months before it died. From the GPIO, the 5v is on all the time the computer is receiving power, but the 3.3v is only on while the computer is on. If you "shut down" the computer, the 3.3v shuts down along with it. When I first tried the new fan on 5v, it wasn't too bad, but I could hear it. If I ran it off the 3.3v (which I do all the time now), it's virtually silent. When I run something that maxes out the CPU for a long time, with this fan on 3.3v running (and the short heatsink in place), the SoC temperatures stabilize around 50 degrees, and I've never seen them exceed the mid-50s with this setup. That is way lower than that official PWM fan did with that pseudo-heatsink it's mounted on, under the same CPU load. And I never have to worry about the fan quitting if some software PWM control malfunctions. Here's that new fan I bought (it came in a pack of 4): https://www.amazon.com/dp/B08R1CXGCJ?ref=ppx_yo2ov_dt_b_fed_asin_title If you have an N508 or similar type of case, the fan mounts to the top of the case. I checked, and Geekworm is apparently no longer selling that case? But back when I was looking into all this, I had found another very similar case sold by a different company (after I'd already purchased the N508) - I don't remember its name. But the fan it came with came with two single-pin connectors like the fan I eventually ended up staying with.

Or simply add whatever packages you desire with apt.

ok, thx

It's enabled by default. I believe that you have the wires swapped. There's a topic here about it where I also added a overlay to adjust what speed at which temperature. I'm not sure if the overlay is still compatible, but since you've already found the source you can change it accordingly.

There is usually only one or two images built per board. That's enough to make sure it compiles properly. All other combinations can be made DIY with the framework, check documentation. Continous Integration https://en.wikipedia.org/wiki/Continuous_integration

ok , so no special procedure exists. There is only minimal image is accessible for download for bpi pro. Does It mean all other failed or nobody tried to build them? Random images are accessible from archive too. What does "CI" stand for?

Our CI produces automated builds which are published here: https://github.com/armbian/community/releases If a build fails we will notice and fix if it doesn't much effort. Otherwise it's demoted to EOS and autobuilds disabled.

Hello everyone, I flashed the armbian into my tf cand and inserted it into my OrangePi 5 Plus, with my fans inserted to the specific socket on board (2pin, 1.25mm, 5V, PWM3_IR_M1). However, when I booted it, the fans was running constantly instead of controlled by temperature dynamically, like the official OS images that did only the fans running when the temperature over 50 celsius. I wanna know how to configure my OS to enable the temperature-controlled fans like the official images. The offical documents shows: Linux uses the default pwm-fan drivers to control thye fans and the device tree was defined in orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts Here is the code: fan: pwm-fan { compatible = "pwm-fan"; #cooling-cells = <2>; pwms = <&pwm3 0 50000 0>; cooling-levels = <0 50 100 150 200 255>; rockchip,temp-trips = < 50000 1 55000 2 60000 3 65000 4 70000 5 >; status = "okay"; }; Here are some descriptions regarding some columns: pwms = <&pwm3 0 50000 0>：The fans use pwm3. cooling-levels = <0 50 100 150 200 > 255>：Used to configure the speed levels (duty cycle of PWM). The number and magnitude of the levels can be customized. 6 levels are configured, with the speed range from 0 to 255. rockchip,temp-trips：Used to configure the correspondence between CPU temperature and fan speed levels. This can be adjusted according to actual needs. In the above configuration, 50°C corresponds to level 1, and 70°C corresponds to level 5. Thank you very much.

mihanson@armbi400:~$ sudo poweroff Broadcast message from root@armbi400 on pts/0 (Thu 2025-09-04 07:29:16 PDT): The system will power off now! mihanson@armbi400:~$ [41893.451514] reboot: Power down [41893.454658] ------------[ cut here ]------------ [41893.459337] Voluntary context switch within RCU read-side critical section! [41893.459354] WARNING: CPU: 0 PID: 1 at kernel/rcu/tree_plugin.h:331 rcu_note_context_switch+0x4e0/0x530 [41893.475859] Modules linked in: sg rfcomm cmac aes_arm64 algif_hash algif_skcipher af_alg bnep zram zsmalloc binfmt_misc hci_uart btbcm bluetooth ecdh_generic ecc bcm2835_codec(C) bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) v4l2_mem2mem vc_sm_cma(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_bcm2835(C) videodev snd_pcm videobuf2_common snd_timer mc raspberrypi_hwmon snd raspberrypi_gpiomem i2c_dev drm drm_panel_orientation_quirks backlight fuse bonding ipv6 brcmfmac_wcc brcmfmac cfg80211 rfkill brcmutil uio_pdrv_genirq uio nvmem_rmem [41893.527454] CPU: 0 UID: 0 PID: 1 Comm: systemd-shutdow Tainted: G C 6.12.44-current-bcm2711 #1 [41893.537603] Tainted: [C]=CRAP [41893.540606] Hardware name: Raspberry Pi 400 Rev 1.0 (DT) [41893.545989] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [41893.553048] pc : rcu_note_context_switch+0x4e0/0x530 [41893.558080] lr : rcu_note_context_switch+0x4e0/0x530 [41893.563112] sp : ffff80008002b770 [41893.566466] x29: ffff80008002b770 x28: ffff2262c6ffb3c0 x27: ffff2262c0c5f8c0 [41893.573707] x26: ffff2262c0260000 x25: ffffcc22d85831f4 x24: 0000000000000000 [41893.580947] x23: 0000000000000000 x22: ffff2262c0260000 x21: ffffcc22d98b3070 [41893.588187] x20: 0000000000000000 x19: ffff22637b779fc0 x18: 0000000000000006 [41893.595426] x17: ffffcc22d97fb000 x16: 00000000a53a0512 x15: ffff80008002b0d0 [41893.602666] x14: 0000000000000000 x13: 216e6f6974636573 x12: 206c616369746972 [41893.609905] x11: 6320656469732d64 x10: ffffcc22d96d7a28 x9 : ffffcc22d7724ed8 [41893.617145] x8 : 00000000ffffefff x7 : ffffcc22d96d3960 x6 : 00000000000002b3 [41893.624384] x5 : 00000000000002b4 x4 : 40000000fffff2b3 x3 : 0000000000000000 [41893.631623] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff2262c0260000 [41893.638863] Call trace: [41893.641336] rcu_note_context_switch+0x4e0/0x530 [41893.646016] __schedule+0xb4/0xe70 [41893.649463] schedule+0x3c/0x148 [41893.652733] schedule_timeout+0x98/0x1a0 [41893.656709] wait_for_completion_timeout+0x80/0x160 [41893.661653] mbox_send_message+0xf8/0x140 [41893.665716] rpi_firmware_property_list+0x104/0x298 [41893.670662] rpi_firmware_property+0x78/0xc8 [41893.674988] rpi_exp_gpio_get_polarity+0x68/0x100 [41893.679760] rpi_exp_gpio_dir_out+0x6c/0x120 [41893.684089] gpiod_direction_output_raw_commit+0x6c/0x348 [41893.689562] gpiod_direction_output+0xa8/0x1b8 [41893.694065] gpio_poweroff_do_poweroff+0x2c/0xd0 [41893.698747] sys_off_notify+0x48/0x80 [41893.702458] notifier_call_chain+0x80/0x140 [41893.706699] atomic_notifier_call_chain+0x44/0x70 [41893.711468] do_kernel_power_off+0x5c/0x80 [41893.715618] machine_power_off+0x40/0x58 [41893.719594] kernel_power_off+0x88/0x98 [41893.723479] __do_sys_reboot+0x1e0/0x240 [41893.727452] __arm64_sys_reboot+0x2c/0x40 [41893.731514] invoke_syscall+0x50/0x120 [41893.735314] el0_svc_common.constprop.0+0x48/0xf0 [41893.740083] do_el0_svc+0x24/0x38 [41893.743441] el0_svc+0x38/0x120 [41893.746622] el0t_64_sync_handler+0x120/0x130 [41893.751037] el0t_64_sync+0x190/0x198 [41893.754745] ---[ end trace 0000000000000000 ]--- 25.8.1 Trixie Armbian image and EXT4 FS. Does not happen on reboot, just poweroff. The below also produce the same result. $ sudo shutdown -H now $ sudo systemctl poweroff mihanson@armbi400:~$ armbianmonitor -u Collecting info and sending to paste.armbian.com, wait... Failed grabbing info (pipe 3 result 22) and sending to server paste.armbian.com. Collecting info and sending to paste.next.armbian.com, wait... https://paste.next.armbian.com/oxawoposil Please post the URL in the forum where you've been asked for.

OK, how should i understand build test?

Yes, csc boards are not actively monitored. Build test only.

As I understood they are not tested, am I right?

moved

Hi! I'm building a custom board for the AM69 processor, which is similar to AM68. My question is if there is any Arabian support for AM69 with web browsing e.g Chromium with streaming ability such as Youtube/Netflix etc? Any pre-compiled builds?

When things are not actively monitored, features stopped working without knowing. This has to be find out. At least all Armbian distributions have the same kernel, regardless of its upstream origin - Debian X,Y,Z and Ubuntu A,B,C ... have same kernel. But of course kernels versions go up all the time. I am not managing this that deep / specific. Where to search? On this forum. I am sure that this was already brought up.

@LanMarc77, I think you meant to tag @laibsch there What you're saying sounds like it could be a good option.

Actually, the connections on the cable harness appear to be good as well as all the capacitors. They are not expanded and they are not leaking--and no, I am not certain. I did not consider that it might be a board issue because I sniffed the board, there were no unusual odors when the system is powered up. Visually nothing appeared burnt. The failure occurred randomly after functioning for 4+ years. It has always been connected to an Online UPS that supports AVR, and Pure Sinewave on my server rack. I am not proficient at soldering, nor do I have a microscope, soldering iron or any of the required accessories to attempt a repair. For testing purposes, yesterday, I supplied power using an external power source from a USB enclosure and it worked. SATA Ports 1 and 2 are both functional, it is definitely related to power. I am meeting with my CEO tomorrow to discuss purchasing a new NAS type system. Leaning towards an HPE MicroServer Gen11. Going from a fantasic little affordable unit to an actual server that is going to cost around CAD$4,000 (price includes HDDs). YIkes. Thank you to everyone that took the time to read and reply though. I appreciate you, your time, and your suggestions. I was hoping I could just buy a cable and move on lol.

Alright, let's give a real quick overview where the code for A20 comes from. Let's focus on current. First stop. Board config: https://github.com/armbian/build/blob/main/config/boards/bananapipro.csc -> BOARDFAMILY="sun7i" Next stop. Family config: https://github.com/armbian/build/blob/main/config/sources/families/sun7i.conf -> No sources defined. However there are includes. Next stop. Includes: https://github.com/armbian/build/blob/main/config/sources/families/include/sunxi_common.inc -> No kernel source URL defined. Therefore kernel comes from mainline (kernel.org to say). However a version is tagged: v6.12.43 So we know: Linux source comes from unmodified mainline and the version is 6.12.43 Next stop. Patches: https://github.com/armbian/build/tree/main/patch/kernel/archive/sunxi-6.12 -> vendor family = sunxi, kernel major.minor is 6.12 All these patches are applied on top of the kernel source from kernel.org. And yes, that's a lot. I think sunxi is the worst family regarding number of additional patches to make stuff work. Next component is u-boot. https://github.com/armbian/build/blob/main/config/sources/families/include/sunxi_common.inc -> BOOTBRANCH:-"tag:v2024.01" so uboot is tagged to this version. So we know: U-Boot source comes from unmodified mainline and the version is v2024.01. And BOOTPATCHDIR="${BOOTPATCHDIR:-"u-boot-sunxi"}" which means here we find the patchset put on top of that version. Let's check. https://github.com/armbian/build/tree/main/patch/u-boot/u-boot-sunxi -> folders starting with board_ are applied only if the target board is being built. All remaining paches are always applied. There are more definitions of stuff appling for multiple families, whole architectures or even all boards regardless of architecture but in this case they are not important. Just including for the sake of completion/information: https://github.com/armbian/build/blob/main/config/sources/armhf.conf https://github.com/armbian/build/blob/main/config/sources/common.conf Good luck.

@grendel Sure you're certain you need a new cable harness? A few years ago, I replaced the HDD power switches myself, they’re just small smd transistors. 1 and 2 (Channel A) power on simultaneously, followed by 3, 4, and 5 (Channel B). There’s a built-in delay between the two channels to help manage voltage spikes that occur during HDD initialization — Channel A starts first, then Channel B.

Well I tried everything to make it work, including switching from PoE to a proven USB power supply, nothing worked. The only thing that worked is flashing back the latest Radxa bullseye image with 5.10.110 kernel, and upgrading to bookworm. I have a lot of errors at boot, so I might consider updating the kernel at some point, but I have absolutely no idea how to do that without flashing a new image. Considering 5.10.110 is the last kernel available from Radxa, I think I'm stuck... I suppressed the radxa apt in the sources.list as there is no bookworm apt, only bullseye. Could I still use the bullseye radxa apt with a bookworm debian? [ 59.024477] ramoops ramoops: failed to locate DT /reserved-memory resource [ 59.084556] fiq_debugger fiq_debugger.0: IRQ fiq not found [ 59.084581] fiq_debugger fiq_debugger.0: IRQ wakeup not found [ 59.084597] fiq_debugger_probe: could not install nmi irq handler [ 60.711536] rockchip-usb2phy ff770000.syscon:usb2-phy@e450: IRQ index 0 not found [ 60.714528] rockchip-usb2phy ff770000.syscon:usb2-phy@e460: IRQ index 0 not found [ 60.723981] rkvdec_init:1230: failed on clk_get clk_hevc_cabac [ 60.724074] mpp_rkvdec ff660000.rkvdec: shared_video_hevc_cabac is not found! [ 60.724090] rkvdec_init:1261: No hevc cabac reset resource define [ 60.746975] rockchip-vop ff8f0000.vop: missing rockchip,grf property [ 60.747264] rockchip-vop ff900000.vop: missing rockchip,grf property [ 60.750685] no ATF memory for init [ 60.763340] no ATF memory for init [ 60.767736] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed [ 61.067311] vcc_cam: failed to get the current voltage: -EPROBE_DEFER [ 61.067671] vcc_mipi: failed to get the current voltage: -EPROBE_DEFER [ 61.090893] vcc_sdio: unsupportable voltage range: 3300000-3000000uV [ 61.094146] rockchip-dmc dmc: Failed to get ddr_leakage [ 61.094884] rockchip-dmc dmc: could not find power_model node [ 61.099683] rksfc_base v1.1 2016-01-08 [ 61.695258] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 61.695324] rockchip-pcie f8000000.pcie: deferred probe failed [ 69.217783] rk-multicodecs es8316-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 69.309154] rk-multicodecs es8316-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 69.456788] debugfs: File 'Left Hp mixer' in directory 'dapm' already present! [ 69.456983] debugfs: File 'Right Hp mixer' in directory 'dapm' already present! [ 69.457046] debugfs: File 'HPCP L' in directory 'dapm' already present! [ 69.457078] debugfs: File 'HPCP R' in directory 'dapm' already present! [ 69.457127] debugfs: File 'HPVOL L' in directory 'dapm' already present! [ 69.457157] debugfs: File 'HPVOL R' in directory 'dapm' already present! [ 70.938277] udc fe800000.usb: failed to start radxa-otgutils: -19 [ 81.008640] ieee80211 phy0: brcmf_escan_timeout: timer expired [ 89.540144] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.540187] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 89.540706] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.540728] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 89.541174] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.541195] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.589939] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.589981] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.590499] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.590521] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.590978] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.591003] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22

@dale looking at the openvfd_x98h.dtso file you shared, openvfd uses these pins: openvfd_gpio_clk = <&pio 2 7 0>; openvfd_gpio_dat = <&pio 2 2 0>; openvfd_gpio_stb = <&pio 2 12 0>; So you should try with their equivalent: mosi-gpios = <&pio 2 2 GPIO_ACTIVE_HIGH>; /* mosi is the same as openvfd_gpio_dat */ sck-gpios = <&pio 2 7 GPIO_ACTIVE_HIGH>; /* sck is the same as openvfd_gpio_clk */ cs-gpios = <&pio 2 12 GPIO_ACTIVE_LOW>; /* cs is the same as openvfd_gpio_stb */