Search the Community

Hello, I've recently bought a rock 5B plus. I have a brand new crucial P310 nvme 1TB with the goal to boot from it. As the title says, sometimes the nvme drive is properly detected, sometimes not. (Everytime the controller is visible in lspci, but only sometimes shows in lsblk). When the drive is properly detected, I can write to it and it works fine, without issues. I've noticed that it is more likely to be detected on a cold boot (ie. if I turn off the power and come back the next day, the first time it will probably show up). I have the official radxa 65w PD power adapter (although I've also tried a lot more during the process with the same results). I tried with the official radxa debian image, and with armbian, and the results are exactly the same on both. Btw, I would like to mention that armbian noble gnome doesn't boot even from the sd card (blue led but no display output, I let it for over 10 minutes), only the minimal/iot works. I don't know what else to try at this point, I can post any info / logs you may want. Thanks!

hey all, I have been running three Rock 5B+ for some time now with Proxmox arm port, and last night I did a kernel update to the latest, and now all three SBC are running extremely slow, PVE does not load, and there are a bunch of system errors (see below). I tried going back to an older kernel, but the same errors remain. any thoughts? Aug 18 07:13:00 PMOX2 kernel: rk806 spi2.0: no dvs-setting pinctrl state Aug 18 07:13:00 PMOX2 kernel: cpu cpu0: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu0: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu0: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: cpu cpu4: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu4: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu4: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: cpu cpu6: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu6: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: cpu cpu6: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active. Aug 18 07:13:00 PMOX2 kernel: debugfs: File 'Capture' in directory 'dapm' already present! Aug 18 07:13:00 PMOX2 kernel: debugfs: File 'Capture' in directory 'dapm' already present! Aug 18 07:13:00 PMOX2 kernel: rk-multicodecs es8316-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length> Aug 18 07:13:00 PMOX2 kernel: dw-pcie fe190000.pcie: invalid resource Aug 18 07:13:00 PMOX2 kernel: dw-pcie fe190000.pcie: Failed to initialize host Aug 18 07:13:00 PMOX2 kernel: mpp_rkvdec2 fdc38100.rkvdec-core: shared_niu_a is not found! Aug 18 07:13:00 PMOX2 kernel: rkvdec2_init:1198: No niu aclk reset resource define Aug 18 07:13:00 PMOX2 kernel: mpp_rkvdec2 fdc38100.rkvdec-core: shared_niu_h is not found! Aug 18 07:13:00 PMOX2 kernel: rkvdec2_init:1201: No niu hclk reset resource define Aug 18 07:13:00 PMOX2 kernel: mpp_rkvdec2 fdc48100.rkvdec-core: shared_niu_a is not found! Aug 18 07:13:00 PMOX2 kernel: rkvdec2_init:1198: No niu aclk reset resource define Aug 18 07:13:00 PMOX2 kernel: mpp_rkvdec2 fdc48100.rkvdec-core: shared_niu_h is not found! Aug 18 07:13:00 PMOX2 kernel: rkvdec2_init:1201: No niu hclk reset resource define Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19 Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: failed to set opp config Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init opp info Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init_opp_table Aug 18 07:13:00 PMOX2 kernel: rkvenc_init:2147: failed to add venc devfreq Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19 Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: failed to set opp config Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init opp info Aug 18 07:13:00 PMOX2 kernel: mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init_opp_table Aug 18 07:13:00 PMOX2 kernel: rkvenc_init:2147: failed to add venc devfreq Aug 18 07:13:00 PMOX2 kernel: rockchip-dmc dmc: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: rockchip-dmc dmc: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: rockchip-dmc dmc: failed to get vop bandwidth to dmc rate Aug 18 07:13:00 PMOX2 kernel: rockchip-dmc dmc: failed to get vop pn to msch rl Aug 18 07:13:00 PMOX2 kernel: mali fb000000.gpu: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: mali fb000000.gpu: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: mali fb000000.gpu: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: debugfs: Directory 'fb000000.gpu-mali' with parent 'vdd_gpu_s0' already present! Aug 18 07:13:00 PMOX2 kernel: debugfs: Directory 'fb000000.gpu-mali' with parent 'vdd_gpu_s0' already present! Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: can't request region for resource [mem 0xfdab0000-0xfdabffff] Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: can't request region for resource [mem 0xfdac0000-0xfdacffff] Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: can't request region for resource [mem 0xfdad0000-0xfdadffff] Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: RKNPU: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: Failed to get specification_serial_number Aug 18 07:13:00 PMOX2 kernel: RKNPU fdab0000.npu: Failed to get leakage Aug 18 07:13:00 PMOX2 kernel: debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present! Aug 18 07:13:00 PMOX2 kernel: debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present! Aug 18 07:13:00 PMOX2 kernel: rk_hdmirx fdee0000.hdmirx-controller: hdmirx_cancel_cpu_limit_freq freq qos nod add Aug 18 07:13:00 PMOX2 systemd-tmpfiles[765]: Setting file flags is only supported on regular files and directories, cannot set > Aug 18 07:13:00 PMOX2 blkmapd[786]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [quorum] crit: quorum_initialize failed: 2 Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [quorum] crit: can't initialize service Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [confdb] crit: cmap_initialize failed: 2 Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [confdb] crit: can't initialize service Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [dcdb] crit: cpg_initialize failed: 2 Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [dcdb] crit: can't initialize service Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [status] crit: cpg_initialize failed: 2 Aug 18 07:13:01 PMOX2 pmxcfs[1241]: [status] crit: can't initialize service Aug 18 07:13:20 PMOX2 kernel: [GTP-ERR][__do_register_ext_module:79] Module [goodix-fwu] timeout

I am Running Armbian 24.5.1 Jammy with Linux 6.1.115-vendor-rk35xx on Radxa Rock5b (and it works great!!) when running sudo apt dist-upgrade or sudo apt upgrade I get Die folgenden Pakete sind zurückgehalten worden: armbian-bsp-cli-rock-5b " Packages retained" apt list --installed | grep armbian-bsp-cli-rock-5b gives: armbian-bsp-cli-rock-5b-legacy/jammy,now 24.5.1 arm64 [installiert] armbian-bsp-cli-rock-5b/jammy,now 24.5.1 arm64 [Installiert,aktualisierbar auf: 25.5.1] ## installed, can be updated can/shall I force the the use of "armbian-bsp-cli-rock-5b/jammy,now 24.5.1 arm64 [Installiert,aktualisierbar auf: 25.5.1]" ? how? what is the correct procedure to update to 25.5.x? thanks

Why does HDMI Audio work on Debian 12 Bookworm 6.1 version and not on Debian 12 Bookworm 6.12? I have updated to latest version and still no HDMI audio. Is there a patch or something i can do to fix this?

Hi i want to know if it’s possible to connect a raxda rock 5B with armbian on a touch screen Joy-it LCD10 V2 Module écran tactile 25.7 cm (10.1 pouces) 1280 x 800 Pixel by usb and hdmi ?

Hi all! I am entirely new to Armbian. I see Radxa's Rock5B RK3588 based SBC is suppored and its Armbian page is https://www.armbian.com/rock-5b/ . Can you give me a small crash course on your experience with Armbian on the Radxa Rock5B? If you have an idea of any of the points I raise below, please share. 1. Super stable? Generally to use and to upgrade Armbian, how stable has it been to you? 2. Which image should I pick? I see both Debian and Ubunto are offered. I'll pick Debian. Then there are "Desktop", "Server" and "Minimal/IOT"and "Dedicated applications" images, and some are listed as "Linux v6.1" and some as "Linux v6.12". Which one of v6.1 and v6.12 should I take? 12 means twelve and 1 means one, right, so 6.12 sounds a lot preferable. Under "Server", there is no Debian option at all. Any idea why? What does "Dedicated applications" mean here? If I would just guess my way through, I would probably take the "Desktop" variant with 6.12 kernel and then on the first boot I'd disable the GUI permanently by running "systemctl set-default multi-user.target". It sounds like "Desktop" should include a lot of drivers. Who knows, perhaps one of those drivers would be needed for a PCI or USB peripheral. In respect of drivers, "Minimal/IOT" sounds risky. Did I get it right? 3. Armbian SPI flash image with particular u-boot?? Radxa distribute a SPI flash image with their latest u-boot. Typically you flash a MicroSD card with their whole Debian distribution on it, then you run "rsetup" and pick the SPI flash option. But, their wiki contains the manual flashing instructions based on "dd" also. Ref https://docs.radxa.com/en/rock5/rock5b/download . I was told that Armbian has its own u-boot for Rock5B, is it true? Where is it, and where are the installation instructions? 4. Peripherals, drivers, all OK? Firstly what about the peripherals such as the onboard Realtek 8125 2.5gbe NIC, is it always stable? Does everyone only have good experiences with using the 22x80mm M.2 slot on the bottom which has 4x PCIe v3 lanes? All good experiences with the 22x30mm A+E key M.2 slot on the top, which has 1x PCIe v2 lane? 5. PD? About the USB-C PD power supply protocol negotiation for voltage, the main Armbian page https://www.armbian.com/rock-5b/ says "PD is broken for the 5B model (background) on most revisions that are in the wild and is causing boot loop. Workaround is to use a stupid / fixed 5-24 volts USB-C power supply." and links to https://www.spinics.net/lists/linux-usb/msg239175.html . I presume here, just using a USB-C power supply that supports up to 5A in the default 5V mode will do, normally. But to not negotiate to 20V sounds quite limited especially as the Rock5B has the hardware to take 20V DC input. Radxa themselves have implemented support for hte USB-C PD protocol negotiation in their Debian distribution. What about just bring in their code as pragmatic solution? 6. "aptitude update; aptitude upgrade" OK & safe? Is "aptitude update; aptitude upgrade" always safe on Armbian, so any kernel offered will be properly patched? Did anyone's system break down permanently after doing "aptitude update; aptitude upgrade"? 7. Kernel version? Just for recap, which kernel version is provided right now? I think someone said 6.12. Via "apt upgrade" will it pick a newer kernel automatically now or when one is released? Via "apt install" are there any optional even newer kernels avaiable? 8. URL to the Rock5B/RK3588 specific patches? Just curious, where is Armbian's sourcecode that's specific to Rock5B and RK3588 actually? 9. Mainlining status? Does anyone have a notion of what status there is to including Rock5B & RK3588 specific patches to mainline Linux? Ideally over time custom patches should go to zero, right. However also occasionally for some device it seems like the mainlining work just grinds to a halt. How is it here. 10. Armbian-Debian packages What is the relation between Debian's packages repository and Armbian's - does Armbian copy essentially everything? 11. ARM64 CPU optimizations? Are sensible ARM64 CPU optimizations enabled so generally Armbian operates at a really high speed? I'd guess yes. Many thanks.

Hey everyone, for the past couple of days I've been looking into the Mesa-VPU script made by AmazingFate that's used to patch Mesa/VPU onto a custom build of Armbian. https://github.com/armbian/build/blob/main/extensions/mesa-vpu.sh I already have an install of Armbian (Debian XFCE 6.12.28-current-rockchip64 ) on my Rock5b and was looking into applying as much as I can without re-building an image or starting from scratch. From my understanding, You'd need the vendor rk3588 kernel if you want the best possible compatibility with things like the VPU for multimedia acceleration (Someone please correct me if this is not the case lol) What follows is what I was able to piece together after troubleshooting, reading the Mesa changelog & trying to apply as many packages as I can from AmazingFate's kernel extension script. I've also included some tweaks for XFCE to hopefully provide a smooth graphical experience. Although my Rock5b is used as a headless server and doesnt have anything plugged into the HDMI port, I can say that the following changes have made a huge difference in graphical performance of VNC. Please keep in mind that i'm not a developer for Armbian. I just wanted to share this as a guide i've put together to hopefully help someone else who's tried the same (Please let me know your thoughts or if there was anything i've missed. Like I said, this is what has worked for me) (Obviously the correct fix is to rebuild Armbian with Mesa-VPU. What follows was done as an experiment) #################### GUIDE BELOW. THIS IS NOT A SHELL SCRIPT! PLEASE READ AND DO NOT COPY/PASTE ENTIRETY INTO TERMINAL!############################# #### -- 01 Setup AmazingFate Panfork-Mesa repo for mali-g610-firmware 01 -- #### ## 1A: import gpg key and use it to sign repo ## wget -qO - https://download.opensuse.org/repositories/home:/amazingfate:/panfork-mesa/Debian_12/Release.key | sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/panfork-mesa.gpg ## 1B: Add Repo to apt sources & update ## echo "deb https://download.opensuse.org/repositories/home:/amazingfate:/panfork-mesa/Debian_12/ /" | sudo tee /etc/apt/sources.list.d/panfork-mesa.list sudo apt update ## 1C: Install firmware ## sudo apt install mali-g610-firmware libmali-g610-x11 ## 1D: **RECOMMENDED** : Remove panfork-mesa repo ## sudo rm -rf /etc/apt/sources.list.d/panfork-mesa.list sudo rm -rf /etc/apt/trusted.gpg.d/panfork-mesa.gpg #### -- 02 Enable Debian Experimental Repo for recent Mesa Packages 02 -- #### sudo nano /etc/apt/sources.list ## 2A: Add the following to the bottom of the document... ## deb http://deb.debian.org/debian unstable main contrib non-free deb http://deb.debian.org/debian experimental main ## 2B: Update and install Mesa Packages ## sudo apt update sudo apt install -t experimental mesa-vulkan-drivers mesa-utils libgl1-mesa-dri libglx-mesa0 mesa-vdpau-drivers mesa-va-drivers mesa-opencl-icd mesa-libgallium ## 2C: **RECOMMENDED** : Re-open apt sources and remove Experimental/Unstable repos... ## sudo nano /etc/apt/sources.list #Remove the following and update apt...# deb http://deb.debian.org/debian unstable main contrib non-free deb http://deb.debian.org/debian experimental main sudo apt update #### -- 03 Add rockchip-multimedia Ubuntu Repo to Apt 03 -- #### echo "deb [arch=arm64] https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu jammy main" | sudo tee /etc/apt/sources.list.d/rockchip-multimedia.list ## 3A: Download Key and add convert to gpg ## curl -o rockchip-multimedia.asc "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x8065BE1FC67AABDE" gpg --dearmor rockchip-multimedia.asc sudo mv rockchip-multimedia.asc.gpg /etc/apt/keyrings/rockchip-multimedia.gpg ## 3B: Add PPA Repo and update ## echo "deb [arch=arm64 signed-by=/etc/apt/keyrings/rockchip-multimedia.gpg] https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu jammy main" | sudo tee /etc/apt/sources.list.d/rockchip-multimedia.list sudo apt update ## 3C: Install packages ## sudo apt install libv4l-rkmpp chromium gstreamer1.0-rockchip1 rockchip-multimedia-config ## 3D: **OPTIONAL** : Disable rockchip-multimedia PPA repo ## sudo mv /etc/apt/sources.list.d/rockchip-multimedia.list /etc/apt/sources.list.d/rockchip-multimedia.list.disabled sudo apt update #### -- 04 Optimize XFCE/Xorg and Reboot 04 -- #### ## 4A: Open default xorg config ## sudo nano /etc/X11/xorg.conf.d/01-armbian-defaults.conf #Add the following... # Section "Device" Identifier "Mali-G610" Driver "modesetting" Option "DRI" "3" # Required for Mali GPUs Option "GALLIUM_DRIVER" "panfrost" Option "PageFlip" "on" # Reduces tearing Option "TearFree" "true" # Xfce-specific anti-tearing EndSection ## 4B: Add XFCE Specific tweaks ## sudo nano /etc/X11/xorg.conf.d/20-xfce-tweaks.conf #Add the following... # Section "Extensions" Option "COMPOSITE" "Enable" EndSection Section "ServerFlags" Option "AutoAddGPU" "off" # Prevents duplicate GPU detection EndSection ## 4C: Reboot ## sudo reboot now

Hello all! I have a radxa rock 5b (8GB, not the plus version) and am running armbian (bookworm) on it. The kernel version (uname -r) reports as 6.12.32-current-rockchip64. By and large almost everything seems to be working - video playback in VLC is fine, 3d acceleration is working (I get around 58-60fps in the game 'torcs' as an example). The only thing I can't seem to get working (and can't find much about it) is the hdmi input. I see some five devices listed in dev (from /dev/video0 to /dev/video4) although none of these seem to relate to the hdmi input. Does the hdmi input work on the 5b under armbian at all? thanks ljones

Any fixes for this? Some rock chip ICs need custom PCie overlay to set pcie speeds, maybe the kernel just has it set to gen 2? 0001:11:00.0 Non-Volatile memory controller: Micron/Crucial Technology Device 5421 (rev 01) (prog-if 02 [NVM Express]) Subsystem: Micron/Crucial Technology Device 5021 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 126 Region 0: Memory at f1200000 (64-bit, non-prefetchable) [size=16K] Capabilities: [80] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0W DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 16GT/s, Width x4, ASPM L1, Exit Latency L1 unlimited ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s (downgraded), Width x2 (downgraded) TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+ 10BitTagComp+ 10BitTagReq- OBFF Not Supported, ExtFmt+ EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- TPHComp- ExtTPHComp- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled, AtomicOpsCtl: ReqEn- LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS- LnkCtl2: Target Link Speed: 16GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ EqualizationPhase1+ EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest- Retimer- 2Retimers- CrosslinkRes: Upstream Port Capabilities: [d0] MSI-X: Enable+ Count=9 Masked- Vector table: BAR=0 offset=00002000 PBA: BAR=0 offset=00003000 Capabilities: [e0] MSI: Enable- Count=1/8 Maskable+ 64bit+ Address: 0000000000000000 Data: 0000 Masking: 00000000 Pending: 00000000 Capabilities: [f8] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Latency Tolerance Reporting Max snoop latency: 0ns Max no snoop latency: 0ns Capabilities: [110 v1] L1 PM Substates L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ PortCommonModeRestoreTime=10us PortTPowerOnTime=300us L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1- T_CommonMode=0us LTR1.2_Threshold=0ns L1SubCtl2: T_PwrOn=10us Capabilities: [128 v1] Alternative Routing-ID Interpretation (ARI) ARICap: MFVC- ACS-, Next Function: 0 ARICtl: MFVC- ACS-, Function Group: 0 Capabilities: [1e0 v1] Data Link Feature <?> Capabilities: [200 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap+ ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: 00000000 00000000 00000000 00000000 Capabilities: [300 v1] Secondary PCI Express LnkCtl3: LnkEquIntrruptEn- PerformEqu- LaneErrStat: 0 Capabilities: [340 v1] Physical Layer 16.0 GT/s <?> Capabilities: [378 v1] Lane Margining at the Receiver <?> Kernel driver in use: nvme

I had this plan on utilizing the Radxa Rock 5 ITX+ as a Moonlight client device to stream games from my desktop computer to my living room TV, and using my 8BitDo Ultimate controller to play. On paper, the board has all the bells and whistles needed to do it, but I am having trouble getting hardware decoding of H264 and/or HEVC to work as expected. From what I gather, I need mesa-vpu support, but the documentation I find is very scattered, and repositories that once held the needed resources are no longer available. I am currently running Armbian_25.DBhsHKsx.2.2_Rock-5-itx_bookworm_vendor_6.1.99_cinnamon-backported-mesa_desktop.img (build date 21st of February, 2025), downloaded from Armbian.com. Hardware decoding does however not work, despite it being marked with "backported mesa". I've been at this for two weeks now with different images, including Armbian and Radxa OS, even going so far as trying to build Armbian myself from scratch. The image I am currently using is however the most stable I have experienced so far. Am I missing something? How do I get hardware decoding to work? Edit: Link to armbianmonitor output

FYI latest image for rock 5B+ in downloads section is broken (Armbian_25.5.1_Rock-5b-plus_noble_vendor_6.1.115_gnome_desktop) Wont boot at all, previous 25.2.2 images works fine.

I upgraded my ROCK5B in-place from Armbian Bookworm beta to Armbian Testing/Trixie beta and it turns out that no Ambian packages are seen (so not updated). The Debian Trixie packages do upgrade, as for example I just saw while doing full-upgrade: libavif16:arm64 (1.2.1-1.2) over (1.2.1-1.1) ... I thought something with my install, but also downloaded 'Armbian_25.8.0-trunk.50_Rock-5b_trixie_vendor_6.1.115_minimal.img' yesterday and it has the same issue (quick test via systemd-nspawn container on loopdev mounted image). My goal is at least to figure out what is best bootloader and kernel for the ROCK5B. So far I simply copied/cloned Armbian Bookworm rootfs from ROCK3A+NanoPi-R6C and did some ROCK5B specific changes like U-Boot, but not much more and it actually is already good enough. But before the ROCK5B becomes a 24/7 headless workhorse with long uptime, I thought better to prepare/check for newer Linux or potential issues. I already upgraded some other devices from Bookworm->Trixie and that is quite an improvement, for example KDE 6 performs much better/nicer than KDE5 in Bookworm. It currently uses U-Boot 'edge' and 'current' kernel and very important for me, both the 'vendor' and 'mainline current/edge' overlay for SERDES multi-PHY SATA on the M.2 E-key work (and also the NVMe keeps working). I need to drill a hole in the Radxa aluminum cooling case for the SATA cable (and serial console cable), that needs some time first. I can build and install U-Boot and kernel etc manually of -course, but i wonder why Armbian packages are not visible. Is it as expected or is something wrong? I assume it is just too early yet and that it is work in progress. I think maybe policies are an issue, but don't understand what it could be. Maybe someone has a hint. root@rock-5b:~# apt policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://deb.debian.org/debian trixie/non-free-firmware arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=non-free-firmware,b=arm64 origin deb.debian.org 500 http://deb.debian.org/debian trixie/non-free arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=non-free,b=arm64 origin deb.debian.org 500 http://deb.debian.org/debian trixie/contrib arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=contrib,b=arm64 origin deb.debian.org 500 http://deb.debian.org/debian trixie/main arm64 Packages release o=Debian,a=testing,n=trixie,l=Debian,c=main,b=arm64 origin deb.debian.org 500 https://beta.armbian.com trixie/trixie-desktop all Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-desktop,b=all origin beta.armbian.com 500 https://beta.armbian.com trixie/trixie-desktop arm64 Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-desktop,b=arm64 origin beta.armbian.com 500 https://beta.armbian.com trixie/trixie-utils all Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-utils,b=all origin beta.armbian.com 500 https://beta.armbian.com trixie/trixie-utils arm64 Packages release o=Armbian,a=trixie,n=trixie,l=Armbian,c=trixie-utils,b=arm64 origin beta.armbian.com 500 https://github.armbian.com/configng stable/main arm64 Packages release o=armbian.github.io/configurator,n=stable,l=armbian.github.io/configurator,c=main,b=arm64 origin github.armbian.com Pinned packages:

On the ROCK 5B+, I am getting the following error at boot [ 12.361648] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 12.389297] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 12.390688] cfg80211: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600' [ 12.392699] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid I believe this is the cause of being unable to set the regulatory region for WiFi. Running sudo iw reg get returns global country 00: DFS-UNSET even after running sudo iw reg set GB

I've got a ROCK 5B+ with two NVMe drives installed, and for reasons I've not been able to track down, I'm noticing that the `-edge` releases (Kernel 6.14.6) are not able to display more than one of the NVMe drives at once. I've checked various physical configurations (i.e., slot one, slot two, both slots), and only one slot is presented (i.e., output from `lspci` or `lsblk`) – but it doesn't seem to matter whether its slot one or two. If I use a `-vendor` images (6.1.115), I see both devices and can use them without problems. I'd love to be able to provide more information or help debug, but I'm not quite sure where to start here! Cheers Andrew

hi running Armbian 25.2.3 stable 6.1.99-vendor-rk35xx (Ubuntu noble) having to change audio every time on reboot (not sticking after selecting),and maybe not showing as they should ,currently using HDMI 0 but shows as below:

Hi All I'm trying to use a microphone using the audiojack connector but without any success. Any help around that? I tried to search in the forum but didn't find any useful information regarding Radxa 5B Plus Thanks Erez

Can you tell me how I'm able to enable PWM? I'm not able to see any of them in the armbian-config overlay management

I updated my Rock-5b after a few months, but the latest edge kernel doesn't boot. Getting this on bootup: [ 38.709046] rockchip-pm-domain fd8d8000.power-management:power-controller: failed to get ack on domain 'gpu', val=0xaffff [ 38.710010] SError Interrupt on CPU5, code 0x00000000be000411 -- SError [ 38.710013] CPU: 5 UID: 0 PID: 449 Comm: (udev-worker) Tainted: G C 6.14.0-rc7-edge-rockchip64 #1 [ 38.710017] Tainted: [C]=CRAP [ 38.710018] Hardware name: Radxa ROCK 5B (DT) [ 38.710019] pstate: 404000c9 (nZcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 38.710021] pc : _raw_spin_lock_irqsave+0x38/0x8c [ 38.710027] lr : regmap_lock_spinlock+0x18/0x2c [ 38.710031] sp : ffff800085b4b650 [ 38.710032] x29: ffff800085b4b650 x28: ffff800082263538 x27: ffff80007a891558 [ 38.710035] x26: 0000000000000001 x25: ffff000100d7b080 x24: ffff000100d9b898 [ 38.710037] x23: 0000000000000000 x22: 0000000000000001 x21: 0000000000000000 [ 38.710039] x20: 000000000000000c x19: 0000000000000000 x18: 00000000ffffffff [ 38.710042] x17: 66203a72656c6c6f x16: 72746e6f632d7265 x15: 776f703a746e656d [ 38.710044] x14: 6567616e616d2d72 x13: 000000000000030d x12: 00000000ffffffea [ 38.710046] x11: 0000000000000001 x10: 0000000000000001 x9 : ffff800082227770 [ 38.710048] x8 : 000000000002ffe8 x7 : c0000000ffffdfff x6 : 00000000000affa8 [ 38.710050] x5 : ffff800080adc9dc x4 : 0000000000000008 x3 : ffff800080adc450 [ 38.710052] x2 : 0000000000000001 x1 : 0000000000000000 x0 : ffff000100d9d400 [ 38.710055] Kernel panic - not syncing: Asynchronous SError Interrupt [ 38.710056] CPU: 5 UID: 0 PID: 449 Comm: (udev-worker) Tainted: G C 6.14.0-rc7-edge-rockchip64 #1 [ 38.710058] Tainted: [C]=CRAP [ 38.710059] Hardware name: Radxa ROCK 5B (DT) [ 38.710060] Call trace: [ 38.710062] show_stack+0x18/0x24 (C) [ 38.710066] dump_stack_lvl+0x38/0x90 [ 38.710069] dump_stack+0x18/0x24 [ 38.710071] panic+0x39c/0x3f4 [ 38.710075] nmi_panic+0x40/0x8c [ 38.710077] arm64_serror_panic+0x64/0x70 [ 38.710079] do_serror+0x3c/0x78 [ 38.710081] el1h_64_error_handler+0x30/0x48 [ 38.710085] el1h_64_error+0x6c/0x70 [ 38.710087] _raw_spin_lock_irqsave+0x38/0x8c (P) [ 38.710090] regmap_lock_spinlock+0x18/0x2c [ 38.710092] regmap_write+0x3c/0x78 [ 38.710095] rockchip_pd_power+0xf8/0x5e8 [ 38.710098] rockchip_pd_power_on+0x14/0x20 [ 38.710100] _genpd_power_on+0x98/0x18c [ 38.710103] genpd_power_on.part.0+0xa4/0x1ac [ 38.710106] __genpd_dev_pm_attach+0x1fc/0x304 [ 38.710108] genpd_dev_pm_attach+0x64/0x74 [ 38.710111] dev_pm_domain_attach+0x20/0x34 [ 38.710114] platform_probe+0x50/0xdc [ 38.710117] really_probe+0xc0/0x388 [ 38.710120] __driver_probe_device+0x7c/0x15c [ 38.710122] driver_probe_device+0x40/0x114 [ 38.710124] __driver_attach+0xf4/0x1fc [ 38.710126] bus_for_each_dev+0x74/0xd4 [ 38.710128] driver_attach+0x24/0x30 [ 38.710130] bus_add_driver+0x110/0x234 [ 38.710132] driver_register+0x60/0x128 [ 38.710135] __platform_driver_register+0x24/0x30 [ 38.710138] panthor_init+0x64/0x1000 [panthor] [ 38.710148] do_one_initcall+0x44/0x2a8 [ 38.710150] do_init_module+0x58/0x208 [ 38.710154] load_module+0x2000/0x20c0 [ 38.710156] init_module_from_file+0x84/0xc4 [ 38.710159] __arm64_sys_finit_module+0x1f4/0x2f8 [ 38.710161] invoke_syscall+0x48/0x110 [ 38.710164] el0_svc_common.constprop.0+0x40/0xe8 [ 38.710167] do_el0_svc+0x20/0x2c [ 38.710170] el0_svc+0x30/0xd0 [ 38.710173] el0t_64_sync_handler+0x144/0x168 [ 38.710176] el0t_64_sync+0x198/0x19c [ 38.710178] SMP: stopping secondary CPUs [ 38.710244] Kernel Offset: disabled [ 38.710245] CPU features: 0x380,00000070,00901250,8200720b [ 38.710247] Memory Limit: none [ 38.737861] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]--- Looks like this issue? https://patchwork.kernel.org/project/linux-rockchip/cover/20250220-rk3588-gpu-pwr-domain-regulator-v6-0-a4f9c24e5b81@kernel.org/ Are others are running into the same? Downgrading to kernel 6.12 works around this for the time being.

I have tried to used apt update and upgrade to update latest Mesa driver but keep getting error 'file has unexpected size' so therefore fails as unable to fetch the archive! the file is available after apt update but unable to install. How can i fix this please?

Hi I have just installed this version of Armbian on Rock 5b but there is no wifi! I have wifi module installed and works fine on the latest Gnome build but not on Cinnamon. Can anyone help please? I have also found that there is no sound through hdmi. Only option is for headphones! How can I change this? Note: just started up again and option for wifi has appeared, good news! But still no sound.

The code being compiled is the latest mainline. My compile command: ./compile.sh build BOARD=rock-5b BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=noble ENABLE_EXTENSIONS=mesa-vpu It has not been compiled successfully and is stuck here. I am in China and have used a VPN. Sometimes it compiles successfully, but after installation, the 3D acceleration feature is not detected. In the GNOME settings, it shows as LLVM software rendering. Installing 3D extension packages [ mesa-vpu ] [🚸] WARNING: SDCARD /var/cache/apt dir is not empty [ before 'apt-get --no-install-recommends install libgl1-mesa-dri libglx-mesa0 mesa-utils mesa-utils-extra glmark2 glmark2-wayland glmark2-es2-wayland glmark2-es2 glmark2-x11 glmark2-es2-x11 chromium rockchip-multimedia-config chromium libv4l-rkmpp gstreamer1.0-rockchip libwidevinecdm0' :: /home/qqq/lyh/v24_11_build/.tmp/rootfs-1777ddf6-77e5-4225-bf2d-2f8abff527ae/var/cache/apt (2 files) ] [🔨] /home/qqq/lyh/v24_11_build/.tmp/rootfs-1777ddf6-77e5-4225-bf2d-2f8abff527ae/var/cache/apt: [🔨] total 3.9M [🔨] drwxrwxr-x 2 root root 4.0K Mar 12 18:57 . [🔨] -rw-r--r-- 1 root root 2.3M Mar 12 18:57 pkgcache.bin [🔨] -rw-r--r-- 1 root root 1.6M Mar 12 18:57 srcpkgcache.bin [🔨] drwxr-xr-x 13 root root 4.0K Mar 12 18:37 .. [🔨] E: Unable to correct problems, you have held broken packages. [🚸] Command failed, retrying in 5s [ chroot_sdcard_apt_get_install libgl1-mesa-dri libglx-mesa0 mesa-utils mesa-utils-extra glmark2 glmark2-wayland glmark2-es2-wayland glmark2-es2 glmark2-x11 glmark2-es2-x11 chromium rockchip-multimedia-config chromium libv4l-rkmpp gstreamer1.0-rockchip libwidevinecdm0 ] [🚸] WARNING: SDCARD /var/cache/apt dir is not empty [ before 'apt-get --no-install-recommends install libgl1-mesa-dri libglx-mesa0 mesa-utils mesa-utils-extra glmark2 glmark2-wayland glmark2-es2-wayland glmark2-es2 glmark2-x11 glmark2-es2-x11 chromium rockchip-multimedia-config chromium libv4l-rkmpp gstreamer1.0-rockchip libwidevinecdm0' :: /home/qqq/lyh/v24_11_build/.tmp/rootfs-1777ddf6-77e5-4225-bf2d-2f8abff527ae/var/cache/apt (2 files) ] [🔨] /home/qqq/lyh/v24_11_build/.tmp/rootfs-1777ddf6-77e5-4225-bf2d-2f8abff527ae/var/cache/apt: [🔨] total 3.9M [🔨] drwxrwxr-x 2 root root 4.0K Mar 12 18:57 . [🔨] -rw-r--r-- 1 root root 2.3M Mar 12 18:57 pkgcache.bin [🔨] -rw-r--r-- 1 root root 1.6M Mar 12 18:57 srcpkgcache.bin [🔨] drwxr-xr-x 13 root root 4.0K Mar 12 18:37 .. [🔨] E: Unable to correct problems, you have held broken packages. [🚸] Command failed, retrying in 5s [ chroot_sdcard_apt_get_install libgl1-mesa-dri libglx-mesa0 mesa-utils mesa-utils-extra glmark2 glmark2-wayland glmark2-es2-wayland glmark2-es2 glmark2-x11 glmark2-es2-x11 chromium rockchip-multimedia-config chromium libv4l-rkmpp gstreamer1.0-rockchip libwidevinecdm0 ] [🚸] WARNING: SDCARD /var/cache/apt dir is not empty [ before 'apt-get --no-install-recommends install libgl1-mesa-dri libglx-mesa0 mesa-utils mesa-utils-extra glmark2 glmark2-wayland glmark2-es2-wayland glmark2-es2 glmark2-x11 glmark2-es2-x11 chromium rockchip-multimedia-config chromium libv4l-rkmpp gstreamer1.0-rockchip libwidevinecdm0' :: /home/qqq/lyh/v24_11_build/.tmp/rootfs-1777ddf6-77e5-4225-bf2d-2f8abff527ae/var/cache/apt (2 files) ] [🔨] /home/qqq/lyh/v24_11_build/.tmp/rootfs-1777ddf6-77e5-4225-bf2d-2f8abff527ae/var/cache/apt: [🔨] total 3.9M [🔨] drwxrwxr-x 2 root root 4.0K Mar 12 18:57 . [🔨] -rw-r--r-- 1 root root 2.3M Mar 12 18:57 pkgcache.bin [🔨] -rw-r--r-- 1 root root 1.6M Mar 12 18:57 srcpkgcache.bin [🔨] drwxr-xr-x 13 root root 4.0K Mar 12 18:37 .. [🔨] E: Unable to correct problems, you have held broken packages. [🚸] Command failed, retrying in 5s [ chroot_sdcard_apt_get_install libgl1-mesa-dri libglx-mesa0 mesa-utils mesa-utils-extra glmark2 glmark2-wayland glmark2-es2-wayland glmark2-es2 glmark2-x11 glmark2-es2-x11 chromium rockchip-multimedia-config chromium libv4l-rkmpp gstreamer1.0-rockchip libwidevinecdm0 ] [🚸] Command failed 3 times, giving up [ chroot_sdcard_apt_get_install libgl1-mesa-dri libglx-mesa0 mesa-utils mesa-utils-extra glmark2 glmark2-wayland glmark2-es2-wayland glmark2-es2 glmark2-x11 glmark2-es2-x11 chromium rockchip-multimedia-config chromium libv4l-rkmpp gstreamer1.0-rockchip libwidevinecdm0 ] [💥] Error 1 occurred in main shell [ at /home/qqq/lyh/v24_11_build/extensions/mesa-vpu.sh:160 post_install_kernel_debs__3d() --> extensions/mesa-vpu.sh:160 post_install_kernel_debs() --> <extension_magic>:222 call_extension_method() --> lib/functions/general/extensions.sh:57 install_distribution_agnostic() --> lib/functions/rootfs/distro-agnostic.sh:309 do_with_logging() --> lib/functions/logging/section-logging.sh:81 build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:28 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36 do_with_default_build() --> lib/functions/main/default-build.sh:42 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> compile.sh:50 ] [💥] Cleaning up [ please wait for cleanups to finish ] [🌿] Unmounting recursively [ SDCARD - be patient ] [🌱] Unmounted OK after 2 attempt(s) [ SDCARD ] [🌿] Unmounting recursively [ MOUNT - be patient ] [🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-1777ddf6-77e5-4225-bf2d-2f8abff527ae.log.ans ] [🌿] Share log manually (or SHARE_LOG=yes): [ curl --data-binary @output/logs/log-build-1777ddf6-77e5-4225-bf2d-2f8abff527ae.log.ans https://paste.armbian.com/log ]

I am using the M.2 connector on the Radxa Rock 5B+ board to connect an LTE module (EM7455). According to the datasheet and engineers, this M.2 slot is connected to the board via a USB hub (USB 2.0). When using the official Radxa OS, I can successfully detect the module under lsusb, the necessary kernel modules load correctly, ModemManager recognizes the modem, and I can establish an internet connection. However, on Armbian, I am experiencing a strange issue. The device does not consistently appear under lsusb; instead, the logs show that it keeps connecting and disconnecting in an endless loop. I am unsure of the root cause and how I can gather more detailed logs. Since I am dual-booting with the official Radxa OS (Debian) and the modem works fine there, I believe this is not a hardware issue. Below are the relevant dmesg logs for further analysis.(dmesg) [ 115.811271] qcserial 4-1.4:1.0: Qualcomm USB modem converter detected [ 115.8Preformatted text12190] usb 4-1.4: Qualcomm USB modem converter now attached to ttyUSB0 [ 116.882327] usb 4-1.4: USB disconnect, device number 9 [ 116.883136] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0 [ 116.883201] qcserial 4-1.4:1.0: device disconnected [ 130.325805] usb 4-1.4: new high-speed USB device number 10 using ehci-platform [ 130.524496] usb 4-1.4: New USB device found, idVendor=1199, idProduct=9070, bcdDevice= 0.00 [ 130.524554] usb 4-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 130.524584] usb 4-1.4: Product: Sierra Wireless EM7455 Qualcomm [ 130.524610] usb 4-1.4: Manufacturer: Sierra Wireless, Incorporated [ 130.524636] usb 4-1.4: SerialNumber: LF{XXX} [ 130.527209] qcserial 4-1.4:1.0: Qualcomm USB modem converter detected [ 130.528144] usb 4-1.4: Qualcomm USB modem converter now attached to ttyUSB0 [ 131.602614] usb 4-1.4: USB disconnect, device number 10 [ 131.603279] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0 [ 131.603339] qcserial 4-1.4:1.0: device disconnected [ 145.045108] usb 4-1.4: new high-speed USB device number 11 using ehci-platform [ 145.243503] usb 4-1.4: New USB device found, idVendor=1199, idProduct=9070, bcdDevice= 0.00 [ 145.243521] usb 4-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 145.243528] usb 4-1.4: Product: Sierra Wireless EM7455 Qualcomm [ 145.243535] usb 4-1.4: Manufacturer: Sierra Wireless, Incorporated [ 145.243540] usb 4-1.4: SerialNumber: LF{XXX} [ 145.244431] qcserial 4-1.4:1.0: Qualcomm USB modem converter detected [ 145.244712] usb 4-1.4: Qualcomm USB modem converter now attached to ttyUSB0 [ 146.322437] usb 4-1.4: USB disconnect, device number 11 [ 146.323113] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0 [ 146.323183] qcserial 4-1.4:1.0: device disconnected [ 159.751520] usb 4-1.4: new high-speed USB device number 12 using ehci-platform [ 159.949674] usb 4-1.4: New USB device found, idVendor=1199, idProduct=9070, bcdDevice= 0.00 [ 159.949698] usb 4-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 159.949705] usb 4-1.4: Product: Sierra Wireless EM7455 Qualcomm [ 159.949711] usb 4-1.4: Manufacturer: Sierra Wireless, Incorporated [ 159.949717] usb 4-1.4: SerialNumber: LF{XXX} [ 159.950592] qcserial 4-1.4:1.0: Qualcomm USB modem converter detected [ 159.950877] usb 4-1.4: Qualcomm USB modem converter now attached to ttyUSB0 [ 161.028727] usb 4-1.4: USB disconnect, device number 12 [ 161.029336] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0 [ 161.029399] qcserial 4-1.4:1.0: device disconnected I tried blocking the `qcserial` driver, but it keeps connecting and disconnecting in a nonstop loop again. Not sure if it could be any power configuration problem “echo ‘-1’ | sudo tee /sys/module/usbcore/parameters/autosuspend” didn't help me. MoreDetaildLogs: https://paste.next.armbian.com/iwiqanihuw LTE Module: Sierra Wireless EM7455 Qualcomm Linux rock-5b-plus 6.1.99-vendor-rk35xx Distributor ID: Ubuntu Description: Armbian 25.2.2 noble Release: 24.04 Codename: noble

I have been trying for days now to update my device and all goes well until i get to 'beta.armbian.com:80 (130.185.239.78)' and then it will not update and stays at 0%. i have tried on different! installations and on different devices even a new installation but the same problem occurs. It used to work fine until a couple of days ago! I have even tried turning off all security on my router but no change. Is there a reason for this , if so is there anything i can do to correct it?

root@calypso:~# uname -a Linux calypso 6.12.0-current-rockchip-rk3588 #3 SMP PREEMPT Sun Nov 17 22:15:08 UTC 2024 aarch64 GNU/Linux cat /proc/asound/cards 0 [Audio ]: USB-Audio - USB Audio Bluetrum USB Audio at usb-xhci-hcd.1.auto-1, full speed 1 [rk3588es8316 ]: rk3588-es8316 - rk3588-es8316 rk3588-es8316 HDMI itself works perfect, monitor and cable tested for video and sound OK Both audio cards work with alsa - pulseaudio but no HDMI sound. Any suggestions how tho get the hdmi audio cards for HDMI0 and HDMI1 How to enable the HDMI sound driver? Thanks a lot... willi

The issue is related with FriendlyElec NanoPC T6 LTS (platinum support) but there were no separate category. The SoC was merged to mainstream kernel in 6.7 version. It is properly recognized and a module is loaded but there is an issue with loading a firmware: root@nanopct6-lts:~# dmesg | grep -i bluetooth [ 9.068631] Bluetooth: Core ver 2.22 [ 9.069414] NET: Registered PF_BLUETOOTH protocol family [ 9.069422] Bluetooth: HCI device and connection manager initialized [ 9.069435] Bluetooth: HCI socket layer initialized [ 9.069442] Bluetooth: L2CAP socket layer initialized [ 9.069458] Bluetooth: SCO socket layer initialized [ 9.251768] bluetooth hci0: Direct firmware load for mediatek/mt7925/BT_RAM_CODE_MT7925_1_1_hdr.bin failed with error -2 [ 9.251777] Bluetooth: hci0: Failed to load firmware file (-2) [ 9.252287] Bluetooth: hci0: Failed to set up firmware (-2) [ 9.252776] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 11.175222] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 11.175230] Bluetooth: BNEP filters: protocol multicast [ 11.175236] Bluetooth: BNEP socket layer initialized root@nanopct6-lts:~# dmesg | grep mt7925e [ 9.073757] mt7925e 0003:31:00.0: enabling device (0000 -> 0002) [ 9.075567] mt7925e 0003:31:00.0: Direct firmware load for mediatek/mt7925/WIFI_RAM_CODE_MT7925_1_1.bin failed with error -2 [ 9.079873] mt7925e 0003:31:00.0: ASIC revision: 79250000 [ 9.157219] mt7925e 0003:31:00.0: Direct firmware load for mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin failed with error -2 [ 9.236988] mt7925e 0003:31:00.0: Direct firmware load for mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin failed with error -2 [ 9.319744] mt7925e 0003:31:00.0: Direct firmware load for mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin failed with error -2 [ 9.402872] mt7925e 0003:31:00.0: Direct firmware load for mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin failed with error -2 [ 9.480248] mt7925e 0003:31:00.0: Direct firmware load for mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin failed with error -2 [ 9.559599] mt7925e 0003:31:00.0: Direct firmware load for mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin failed with error -2 [ 9.639770] mt7925e 0003:31:00.0: Direct firmware load for mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin failed with error -2 [ 9.719790] mt7925e 0003:31:00.0: Direct firmware load for mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin failed with error -2 [ 9.799481] mt7925e 0003:31:00.0: Direct firmware load for mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin failed with error -2 [ 9.883152] mt7925e 0003:31:00.0: Direct firmware load for mediatek/mt7925/WIFI_MT7925_PATCH_MCU_1_1_hdr.bin failed with error -2 [ 9.963791] mt7925e 0003:31:00.0: hardware init failed