Active threads

If anyone in interested in a lightweight wayland desktop, inspired by openbox, you should try labwc. In orange pi zero 3, we need to stay in bookworm to get video acceleration, so this guide helps build labwc in bookworm As a greeter, I chose pi-greeter, because it is the lightest login manager I could setup, without any X11 https://github.com/robertojguerra/opiz3-labwc-setup I am open to read any improvements, or show me how I could make deb packages. In the near future, I will make a step-by-step video tutorial in Youtube.

Just out of curiosity, are you able to run your device with firmware loaded from microSD? I. e. firmware area on eMMC cleared. If so, you can try my kernel build and see how it works for you.

For video acceleration, you need to stick with Bookworm.

I don't think you understand how Armbian works. This board is community supported. It does not and hasn't been an Armbian supported board. Given the hundreds of boards out there Armbian only has the resources to officially support a handful. The rest end up being supported by the user community like this board. Thus support is only as good as the community volunteers who have the board and wish to volunteer their time to support it. Armbian provides the tools and infrastruction to make supporting boards easier, but the work still needs to be done by someone for community supported boards like this.

Can I still find the image somewhere? I would like to run Armbian on my Jetson Nano 2 GB, but Armbian_community_25.11.0-trunk.367_Jetson-nano_trixie_current_6.12.54_minimal.img and older images won't boot. I have tried images repeatedly over the past six weeks, but none of them will boot. It would be a shame if the Jetson Nano 2 GB ended up as electronic waste.

If it isn't the PSU or SD than I'm not sure. The only REV available in the STATES "which is where I am" is the 2GB. The u-boot patch set is identical to the BPI-M4-Zero "minus the dts and defconfig of course". All my testing has been done with the unit I have available to me. It works with the Armbian, KIckpi and my own personal builds. As an aside the Kickpi web site is down for me STATE side. Not sure what that means? Doesn't look good though. Anyway, I'm out of ideas. Sorry.

Yep enabled the module and it's working now, Just sent a PR. Thank you.

@MeJune A523/T527 support still needs a lot of work. There is no HDMI support yet. So you will need to install a usb serial device to your uart to interact with your box. You can find details at the botton of the site you posted https://linux-sunxi.org/X96QPro%2B. You could try warpme minimyth2 or miniarch. He has the latest support for these boxes. I don't own a X96q pro+ so I can't help you.

@Unrealchex The base-files error is a known issue. You'll need to run the ./compile command a second time and it should continue where it left off. Here's a post that show's you how to create patches. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-227058 You want to edit u-boot and kernel dts. Remove the x96q code and add the wifi code from x98h. The x96h U-boot and kernel code might be different double check it. remove (Existing x96q wifi code.) reg_vcc_wifi: reg_vcc_wifi { compatible = "regulator-fixed"; regulator-name = "vcc-wifi"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; gpio = <&pio 6 18 GPIO_ACTIVE_HIGH>; /* PG18 WL_REG_ON */ regulator-always-on; enable-active-high; status = "okay"; }; wifi_pwrseq: wifi_pwrseq { compatible = "mmc-pwrseq-simple"; clocks = <&rtc CLK_OSC32K_FANOUT>; clock-names = "ext_clock"; pinctrl-names = "default"; pinctrl-0 = <&x32clk_fanout_pin>; /* PG10 with MUX3 set */ }; &mmc1 { vmmc-supply = <&reg_dldo1>; vqmmc-supply = <&reg_vcc_wifi>; mmc-pwrseq = <&wifi_pwrseq>; bus-width = <4>; non-removable; status = "okay"; wlan: wifi@1 { reg = <1>; interrupt-parent = <&pio>; interrupts = <6 15 IRQ_TYPE_EDGE_RISING>; /* PG15 WL_HOSTWAKE*/ interrupt-names = "host-wake"; local-mac-address = [dc 44 6d c0 ff 02]; }; }; Add (code borrowed from x98h) reg_vcc3v3: vcc3v3 { /* discrete 3.3V regulator */ compatible = "regulator-fixed"; regulator-name = "vcc-3v3"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-on; }; reg_3v3_wifi: vcc3v3-wifi { compatible = "regulator-fixed"; regulator-name = "vcc-3v3-wifi"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-on; }; }; &mmc1 { vmmc-supply = <&reg_vcc3v3>; bus-width = <4>; non-removable; max-frequency = <35000000>; status = "okay"; wlan: wifi@1 { reg = <1>; }; }; You don't need to create a patch for build/config/boards. Edit the file x96q-lpddr3.csc and add this to the bottom of display_alert "$BOARD" "Using ${BOOT_FDT_FILE} for ${BRANCH}" "info" display_alert "Applying wifi firmware" pushd "$SDCARD/lib/firmware" ln -s "aic8800/SDIO/aic8800D80" "aic8800_sdio" # use armbian-firmware cp -R $SRC/packages/blobs/sunxi/h618/armbian-audio-config $SDCARD/usr/lib/armbian cp -R $SRC/packages/blobs/sunxi/h618/armbian-audio-config $SDCARD/lib/armbian popd

Sorry, I didn't take my medicines. where did you find the link between SliTaz and armbian? Do you intend to be the maintainer of this link? you need help writing SliTaz documentation?

https://github.com/manjaro-arm/opi5-plus-images/issues/22#issuecomment-3340442272

Kernel Edge now support npu, for reference: https://github.com/armbian/build/commit/2e139987e79e68a4e4c4d98cd9367a057626a673

The strange thing is that, as far as I can see, this issue doesn’t occur on the vendor kernel. Continuing from our earlier discussion, I’ve just noticed that my variant shows the same problems as well only when i write stuff. I’ll get in touch with FriendlyELEC to clarify this. If the only solution is to scale down the frequency, then it would actually make more sense to modify it directly in the DTS rather than through an overlay.

@Fredrik I got like ~80fps at 720p. I sometimes get the gamepad not working. For me, just remove the wineprefix and it will work again!

my tv box: MXQ pro 4K 5G, Q44_V5.1_20210118, PROCESSOR: ALLWINNER TECH H3 LC267BA 91F2. I recorded the image on a 32gb sd card, but it doesn't boot. Has anyone solved it?

If any of you have experienced skipping and popping when seeking with vlc, you can try setting the audio sink to ALSA and one of the rockchip-es8316 options. That will smooth out the audio playback BUT you will quickly discover that anything pulseaudio related is locked out of using the soundcard while vlc is up. Instead, try this. Set vlc audio back to pulseaudio (or automatic, seems to map to the same thing) and then change these two lines in /etc/pulse/daemon.conf: -; default-sample-rate = 44100 -; alternate-sample-rate = 48000 +default-sample-rate = 48000 +alternate-sample-rate = 44100 Restart pulseaudio with systemctl --user restart pulseaudio and see if vlc plays nice with everything else as well as supporting smooth playback after seeking. It does for me. It seems that forcing pulseaudio to resample causes all sorts of hilarity (vlc seems to like putting everything out at 48000). I'm sure there's a reason why. I'm also sure if I know, I'll be sorry I do. I wonder, how hard is it to get the Vulkan video hardware decoding working? Has anyone gotten it to work?

After many days spent wondering why is my OPI Zero2w 1.5GB not booting some Armbian images (xfce desktop version for example), I have found there is a "bug" or difference in uboot models 1.5GB + 4GB vs 1GB+2GB. Fix that might work for Zero2w is here https://forum.armbian.com/topic/31654-orange-pi-zero-2w/ (planning to test it soon) Can somebody confirm Opi Zero2W 1.5GB has still this issue with some Armbian images ? Armbian minimal boots without aby issues. Not sure why it works and desktop doesnt.

Only that its a known issue. In open source world it is normal to see magnitude more issues then its resolving capacity. I'll look into when possible - its high on 2do list. No need.

Yes for sure, thank you. > lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 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 004 Device 003: ID 2b89:8761 Realtek Bluetooth Radio Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 004: ID 0583:2060 Padix Co., Ltd (Rockfire) 2-axis 8-button gamepad > sudo dmesg | grep -i bluetooth [ 1.706048] usb 6-1: Product: Bluetooth Radio [ 4.360426] Bluetooth: Core ver 2.22 [ 4.360457] NET: Registered PF_BLUETOOTH protocol family [ 4.360460] Bluetooth: HCI device and connection manager initialized [ 4.360466] Bluetooth: HCI socket layer initialized [ 4.360469] Bluetooth: L2CAP socket layer initialized [ 4.360480] Bluetooth: SCO socket layer initialized [ 4.415023] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 4.417020] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 4.417027] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 4.417442] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 6.328832] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.328847] Bluetooth: BNEP filters: protocol multicast [ 6.328859] Bluetooth: BNEP socket layer initialized [ 870.557589] usb 6-1: Product: Bluetooth Radio [ 870.569776] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 870.571601] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 870.571614] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 870.571686] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 1246.745679] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 1246.747602] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 1246.747629] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 1246.747756] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 3667.259558] Bluetooth: RFCOMM TTY layer initialized [ 3667.259580] Bluetooth: RFCOMM socket layer initialized [ 3667.259595] Bluetooth: RFCOMM ver 1.11 [65689.757539] usb 4-1: Product: Bluetooth Radio [65689.769644] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [65689.771604] Bluetooth: hci0: RTL: rom_version status=0 version=1 [65689.771649] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [65689.771913] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin And here's a pastebin of the full dmesg output. https://pastebin.com/wMuX0bVW I got the driver files from here, https://github.com/Elif-dot/RTL8761BU uname Linux opi5 6.16.4-edge-rockchip64 #1 SMP PREEMPT Thu Aug 28 14:34:51 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux thanks

Now it seems that the package is missing for version 25.8.2 and arm64 target. There are packages depending on it (and specifically asking for version >=25.8.2), so this prevents upgrades.

This kernel is available only when you change repository to beta.armbian.com , which provides daily builds. EDGE kernels comes as is - glad to hear it works, but beware it might also break down as kernel is changing rapidly.

@lowscore I'did uploading for you! https://drive.google.com/file/d/1kgyjLl0JXTwFfWfplOKuQY3vLv_KtYlr/view?usp=sharing

Also step 1A & 1B are kind of weird... Like updating won't recognize the gpg key. I still could bypass the error by adding [trusted=true] on step 1B between deb and the link (or use sudo nano /etc/apt/sources.list.d/panfork-mesa.list if the file was already created).

Hi is there a way to enable the old USB port without re-installing Armbian? I have done to much setup work to start all over again.

Yes, or at least there should be less chances to hit some corner case that reduces the compatibility. LibreELEC is using the mainline kernel only for years though, so it is really strange you have issues with both armbian and multitool. I may wonder there is something odd in the device tree, but it would be odd that a misconfiguration in the device tree causes a kernel fault in the DRM code and in particular in the wait for vblank function 🙄