Active threads

@robertoj I apologize, perhaps you missed the message.

Looking at transpeed-8k618-t-allwinner-h6.dtso, you may need these flags instead of 0/1: (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)

Today investigated, why BCM Bluetooth was not working with my image. What a rabbit hole 🙄 Also added OrangePi R2S board. Smaller brother of RV2 (I have no board but it's probably working). For the Bluetooth: everyone is obviously happy to hack the BCM firmware file instead of implementing bcm init into hciattach. The brcm_patchram_plus firmware hacking tool was added for this arch and that arch as a binary under BSP for different boards. Not very Debian-style. I grabbed the working source, compared to the one avail in Android AOSP and added it to my branch, added lib6-dev-riscv64-cross to the Docker image and now have a working image with BT. LG && HTH // Sven-Ola

See here, HW description bulletpoint 17 https://www.hardkernel.com/shop/odroid-m1s-with-4gbyte-ram/ Maybe it is also available on the 40-pins or 14-pins I/O headers, so a simple generic USB serial cable with jumper wires can be connected.

Actually, I was able to find that IC but in chinese version.. https://datasheet4u.com/datasheets/I-CORE/AiP1628/1571692 Looks like its some kind of low level chip that probably transforms low voltage signals into higher voltage, like the ones used on ethernet ports. Probably to power up the LCD leds.

To get the ethernet working you have no option but to build an image with kernel support for mae621. See these posts :

@PH Ph Ask Google AI mode... I haven't played with 4G CPE routers.

So far, the best working images I have found for the LonganPi 3H are those developed for the BananaPi M4 Zero. Only issues I have encountered are wifi-related. Hopefully this helps someone.

Thank you, everyone, for the suggestions. After having been absent here for a while, I am going to try Dante's suggestion first. Thanks again!

Hi all, I found where the problem was... My SD-card was not working correctly. My apologies. The system could not read/find ext4 partition on SD-card (because of "unknown" type and mounting point). I guess this happened when I erased my previous ext4 partitions by Windows disk manager and re-wrote Armbian image later. Problem was resolved as soon as I reformatted/recorded new image by Ubuntu. Thank you all.

Hello! I'm new to this forum but i follow the SBC comunity for a long time. I have a Pine 64, a bunch of raspberryies, 2 nanopies and some "japanese" arm64 tablet. Now i have bought a Radxa 5 Mini-ITX and i'm very happy with it. I was capable to compile ffmpeg with the rockchip extensions and exploit the RK3588 VPU and the NPU with face recognition. Now i was testing the HDMI Input of the board and unfortunaly discovered that the video is capturing just fine but i'm out of luck with the audio side. On the kernel 6.1.115 (last BSP at the moment i think) the recording device of the audio input is not visible in arecode -l This is what i see: **** List of CAPTURE Hardware Devices **** card 4: rockchipes8316 [rockchip-es8316], device 0: dailink-multicodecs ES8316 HiFi-0 [dailink-multicodecs ES8316 HiFi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 But the hdmi input audio card is still found under /proc/asound/cards: root@rock-5-itx:~# cat /proc/asound/cards 0 [rockchiphdmi1 ]: rockchip-hdmi1 - rockchip-hdmi1 rockchip-hdmi1 1 [rockchiphdmi0 ]: rockchip-hdmi0 - rockchip-hdmi0 rockchip-hdmi0 2 [rockchiphdmi2 ]: rockchip-hdmi2 - rockchip-hdmi2 rockchip-hdmi2 3 [rockchiphdmiin ]: rockchip-hdmiin - rockchip-hdmiin rockchip-hdmiin 4 [rockchipes8316 ]: rockchip-es8316 - rockchip-es8316 rockchip-es8316 5 [rockchipspdiftx]: simple-card - rockchip,spdif-tx1 rockchip,spdif-tx1 Furthermore if i go under /proc/asound/pcm: root@rock-5-itx:~# cat /proc/asound/pcm 00-00: rockchip-hdmi1 i2s-hifi-0 : rockchip-hdmi1 i2s-hifi-0 : playback 1 01-00: rockchip-hdmi0 spdif-hifi-0 : rockchip-hdmi0 spdif-hifi-0 : playback 1 02-00: rockchip-hdmi2 spdif-hifi-0 : rockchip-hdmi2 spdif-hifi-0 : playback 1 03-00: rockchip-hdmiin i2s-hifi-0 : 04-00: dailink-multicodecs ES8316 HiFi-0 : dailink-multicodecs ES8316 HiFi-0 : playback 1 : capture 1 05-00: fe4f0000.spdif-tx-dit-hifi dit-hifi-0 : fe4f0000.spdif-tx-dit-hifi dit-hifi-0 : playback 1 So the HDMI Input is still found (rockchip-hdmiin) but is not exposing any playback or capture jack So i tried to investigate and found that rockchip as changed the sound driver at some point as i found out here: https://zhuanlan.zhihu.com/p/664345417 (Link in Chinese) (I don't know if i can post link so let me know) Now i found that if i manualy install the 6.1.75 Kernel i found the device and i am able to record the audio: root@rock-5-itx:~# arecord -l **** List of CAPTURE Hardware Devices **** card 0: rockchiphdmiin [rockchip-hdmiin], device 0: rockchip-hdmiin i2s-hifi-0 [rockchip-hdmiin i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: rockchipes8316 [rockchip-es8316], device 0: dailink-multicodecs ES8316 HiFi-0 [dailink-multicodecs ES8316 HiFi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Anyone can't test this? Maybe is for all the RK3588 or only the Radxa 5 ITX.

Latest armbian firmwares fail to boot on vim3 and graphical desktop do not start. As a workaround I installed old armbian image from August 2024 which booted and worked fine but sudo apt upgrade installed new firmware and it fails to boot to desktop again. Fails on all images Xfce and gnome available on website.

I have only recently been able to get my LaFrite 512, no EMMC to boot armbian. My errors were legion. Might I suggest: 1. write the spi update image with the dd command, I had used etcher to no avail 2. make sure you use the USB port nearer the gpio pins 3. connect the hdmi output on the board to a monitor or use the serial header pins so that you'll have visual confirmations of what is going on 4. if the spi update image is newer than the board's image the update should be applied. My board was out of date and the image was applied. I've no idea what happens if the board has the same or newer image. I wasn't patient or thorough enough to check. 5. Use etcher to write any of the currently posted minimal images to a usb drive of 8, 16, or 32 GB - don't use a larger usb drive. Do not use the Ubuntu server image - the apt sources are bad on that one. 6. put the usb drive with the linux image in the usb port further from the gpio pins -- the opposite of what is needed for the spi update. Again make user you can see what is going on when you boot - hdmi to monitor is fine. Plug a usb keyboard in the other usb port to make things easy. 7. Power on the board. I used an el-cheapo power supply and it worked just fine. If you have a good usb drive the board should boot fairly quickly. There shouldn't be any or many failures on the way up. Again let me reiterate -- a small usb drive. Every 64GB and larger drive I tried failed during the boot process. You may have better luck, but start small to see it things work. I had decided some months ago that my board was defective, it wasn't, my brain was (or is). Hopefully some of my experiences will help. BTW make sure you use the forky rolling release for your Radxa-2F, because unless Armbian has fixed the older releases, your wireless card's drivers will be deleted on an apt upgrade or an Armbian-upgrade. Hope this helps.

I've noticed that since yesterday the `server` Armbian images disappeared from the product pages. Example: https://www.armbian.com/radxa-rock-5-itx/ I can no longer see them. Is it a bug, or something expected from now on. I also noticed the https://armbian.chi.auroradev.org/dl/rock-5-itx/ folder is empty.

I try FEX today and it is the same. I will try hangover tomorrow

I've been using the Helios64 since launch, still going strong 👍 A couple of years back I had to limit the CPU frequency to avoid crashes until the last clean install of bulleyes. Since then stock clock and no custom dtb. Looking forward to my next holidays, planning on a clean install of Trixie. I'm planning on keeping using it as long as this thing wants to stay alive. An really nice piece of hardware, and I'm too cheap to move to something else 😄

Nothing to read on input. Maybe this is the real error, the keyboard input or console has issues. The console param on boot remained unchanged after update ?

use system resolver instead of default:https://github.com/armbian/build/blob/60e869c42c03af0428d9983750eb766a7a846d43/config/templates/config-example.conf.template#L25

If this is something with languages: I remember Armbian has a preferences option in apt config somewhere 'no languages'. Is old memory, maybe changed nowadays. Maybe a hint where to look and what to try. It would actually be a Cinnamon issue then.

There we go https://github.com/armbian/build/pull/9106

Thank you @Nick A

Duplicate

Could anyone advise the simple example on how to play media files using hardware decoding on VPU? I use actual version of Armbian with Edge kernel user@h96-tvbox-3566:~$ uname -a Linux h96-tvbox-3566 6.18.0-rc7-edge-rockchip64 #1 SMP PREEMPT Sun Nov 23 22:53:16 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux and seems that rkvdec is available user@h96-tvbox-3566:~$ v4l2-ctl --list-devices rockchip,rk3328-vpu-dec (platform:fdea0000.video-codec): /dev/video2 /dev/media1 rockchip,rk3568-vepu-enc (platform:fdee0000.video-codec): /dev/video3 /dev/media2 rockchip-rga (platform:rga): /dev/video1 rkvdec (platform:rkvdec): /dev/video0 /dev/media0 then I've installed MPV player from Armbian repository using apt command, but it seems that it doesn't support hardware decoding. I tried to use different hwdec options (rkvdec, rga, rkmpp, hantro....) but got "Unsupported hwdec" each time. user@h96-tvbox-3566:~$ mpv -hwdec=rkvdec --vo=gpu big_buck_bunny_1080p_h264.mov (+) Video --vid=1 (*) (h264 1920x1080 24.000fps) (+) Audio --aid=1 --alang=eng (*) (aac 6ch 48000Hz) Unsupported hwdec: rkvdec AO: [pulse] 48000Hz 5.1 6ch float VO: [gpu] 1920x1080 yuv420p Exiting... (Quit)

I think I've found it here.

moved. Has nothing to do with opi4a. Remove heatsink to get an idea which SoC hides beneath