All Activity

i have the DQ08 and the lan cable is not working anymore. It was in the past but now it only works through Wifi. How is this even possible? Anyone an idea? or how to fix this. The option is not even in the menu anymore even when the LAN cable is plugged in

I have an IoT project that uses an SPI LCD (480x320), showing 1 full screen application on top of X11, which starts automatically, almost in kiosk mode. Is it worth a lot trying to switch to Wayland? I have 2 roadblocks, which I am trying to drill through: * tkinter app re-write in pyqt * starting from a minimal armbian image, and install the bare minimum to have wayland and start the app Solid advantage: * Future proofing the product I have these preconceived advantages: * less resources needed: my application is fine with an OrangePi Zero 3 with 1 GB RAM, I don't want to upgrade RAM * faster startup (now I need to wait 1 minute from power-on to app ready to use, reducing it to 30 seconds would be nice) I know that I can't expect these advantages, since I use SPI instead of HDMI or DSI: * 30 FPS * No frame tearing But really, my main objective is faster startup: will Wayland help me with that? (without having disadvantageous side effects)

Found a handful of working mxq boards in the trash, the unique ones are labed R329Q_v8.1, MXQ_RK3229_EMPC_V4.1 and B00-RK28A-REV76. What are they actually? Almost all of them have an ssv6256p. Can someone confirm me it's actually impossible to use the wifi with this chip? I tried and tried and couldn't get it to work. There's one board with a chip called MSN8800D I would try to get wifi with it but multitool says the emmc storage was not found. Did the chip fry, even though it's a 8Gb/8GB one? If it fried the board shouldn't work at all because the ram would fry too, no? It's Samsung KMQ7X000SA-B315

glad i stumbled on this - had the same problem and i spent the weekend reconfiguring my nas and turning off all updates for now. Igor you have done great work over the years and absolutely understand the difficulty. I wish I knew programming and could assist. However the helios4 has had a great run, its def time for an upgrade.

I am including the Tanix tx6s and Vontar h618 complete android firmware for wifi/bluetooth. I previously tried using some of the files with no success but found the complete firmware save to a usb drive. I think android is using different file names to what is usually expected to work. hopefully its useful to get Bluetooth working in armbian. Tanix Tx6s Wifi/BT: SP6330-X0 Clock: 26.0 MHz tanix tx6s android firmware also includes fdt (dtb) file Vontar H618 Wifi/BT: HK6334Q Clock: 37.4 MHz Vontar h618 android firmware I no longer have working android to boot into. If someone can copy the android fdt (dtb) file from their vontar h618 box and upload it. i would be very grateful. here is how you can do it , i did this for tanix tx6s get android fdt (dtb) think this is the android path to the file /sys/firmware/fdt

@dale murata is armbian firmware, samsung is from vontar android firmware, if you open .hcd with text editor you see text of murata or samsung, I just use that as reference for each file.

Try some of these images. https://github.com/armbian/os/releases/tag/25.5.0-trunk.507 And please post here what doesn't work with the download link to the image.

Armbian has exactly zero in common with Android. Flashing from Android isn't supported either. https://docs.armbian.com/User-Guide_Getting-Started/

Ver 20250505-edge kernel 6.15-rc5 - fix Wifi and eMMC

Need more debug info. Try running “sudo dockerd --debug”

Alfi ciio, I have a Transpeed 8K 4/64Gb and I also use Nick A builds. Docker is installed and running on the 6.9.12 kernel, and it is installed on the 6.12.11 kernel, but it issues an error when running. Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.

The GPU node needs to be enabled. There has been adjustments made to the patching for 6.12.y and above, but I haven't messed with yet. Basically nodes need to be added for sound. As for Bluetooth. I haven't figured out yet why it doesn't work on Armbian. In my personal builds it works fine. I believe there is some patching or service preventing it from loading. But I can't be sure. I've put a lot of time already into the DTS to get this working on both REVS. To much time in my opinion. Anyone is welcome to do a PR and add and enable the bits if they like. Otherwise peps are just gonna have to wait till I get around to it again.

I think the main way to go is to create a .dtsi that will patch the base "old" board with this new features, +&gmac1 { + phy-mode = "rgmii"; + clock_in_out = "output"; + snps,reset-gpio = <&gpio4 RK_PC2 GPIO_ACTIVE_LOW>; + snps,reset-active-low; + /* Reset time is 20ms, 100ms for rtl8211f */ + snps,reset-delays-us = <0 100000 200000>; + assigned-clocks = <&cru SCLK_GMAC1_RX_TX>, <&cru SCLK_GMAC1>; + assigned-clock-parents = <&cru SCLK_GMAC1_RGMII_SPEED>; + assigned-clock-rates = <0>, <125000000>; + pinctrl-names = "default"; + pinctrl-0 = <&gmac1m1_miim + &gmac1m1_tx_bus2 + &gmac1m1_rx_bus2 + &gmac1m1_rgmii_clk + &gmac1m1_rgmii_bus>; + tx_delay = <0x4b>; + rx_delay = <0x26>; + phy-handle = <&rgmii_phy1>; + status = "okay"; +};

@Fajar Muttaqin Can you share your compiled kernel & headers `.debs` In default kernel support for filesystems `cifs` & `nfs` were not included. I compiled with these support as well https://github.com/defencedog/orangepi4A/tree/main/kernels

@Nick A It started, but it stopped right at the beginning. In fact, well before than the other image secure boot for H618. U-Boot SPL 2025.01-armbian-2025.01-S6d41-P13d0-H8869-Vfdd1-Bb703-R448a-dirty (Apr 25 2025 - 18:09:15 -0300) DRAM:testing 32-bit width, rank = 2 read calibration failed! testing 32-bit width, rank = 1 DRAM:Store cfg DRAM:1st writing pattern DRAM:detecting column address bits detected 11 columns DRAM:restore cfg DRAM:reconfigure for all active rows DRAM:store cfg DRAM:2nd writing pattern DRAM:detecting row address bits detected 15 rows DRAM:restoring cfg DRAM:end of auto detect dram size MBUS port 0 cfg0 0100000d cfg1 00640080 MBUS port 1 cfg0 06000009 cfg1 01000578 MBUS port 2 cfg0 0200000d cfg1 00600100 MBUS port 3 cfg0 01000009 cfg1 00500064 MBUS port 4 cfg0 20000209 cfg1 1388157c MBUS port 5 cfg0 00640209 cfg1 00200040 MBUS port 6 cfg0 00640209 cfg1 00200040 MBUS port 8 cfg0 01000009 cfg1 00400080 MBUS port 11 cfg0 01000009 cfg1 00640080 MBUS port 14 cfg0 04000009 cfg1 00400100 MBUS port 16 cfg0 2000060d cfg1 09600af0 MBUS port 21 cfg0 0800060d cfg1 02000300 MBUS port 22 cfg0 01000009 cfg1 00640080 MBUS port 25 cfg0 0064000f cfg1 00200040 MBUS port 26 cfg0 20000209 cfg1 1388157c MBUS port 37 cfg0 01000009 cfg1 00400080 MBUS port 38 cfg0 00640209 cfg1 00200040 MBUS port 39 cfg0 20000209 cfg1 1388157c MBUS port 40 cfg0 00640209 cfg1 00200040 2048 MiB Trying to boot from MMC1

I have an Orange Pi 5 running Armbian Noble and I need a distribution that supports USB OTG in peripheral mode and supports dcw3_generic kernel module. I've tried to compile one with support, but I keep getting: modprobe: FATAL: Module dwc3_generic not found in directory /lib/modules/6.1.115-vendor-rk35xx I triple checked .config and the appropriate flags are set to Y. I am trying to get the Pi to act as a mouse attached to another machine's USB port. Any help is greatly appreciated.

I really like this small board but with new revision firmware choice is a nightmare... Looking for Debian or Ubuntu with XFCE and support for wifi (usb eth at start if needed ok), bluetooth, HDMI sound, QHD display resolution (2560x1440) Main tests results: - Standard Armbian (V25.2.2 Linux 6.6.75 Ubuntu noble XFCE + overlays=bananapi-m4-sdio-wifi-bt) -> wifi OK, bluetooth NO, HDMI sound NO, bad display perf, buggy screen size (display 1920 when choosing 2560) - Official BPI (V24.8.2 Linux 5.4.125 Debian XFCE + overlays=i2c0 spi1 uart4 -> wifi OK, Bluetooth NO, HDMI sound NO, bug in screen size (limited to 1920) - Other rolling releases, starting from minimal, ...: not better ou worse. Any build you know with better results? Please help.

Others may chime in but I really think you are going to need to get access to a suitable computer and compile armbian with kernel patches from here : https://github.com/CoreELEC/linux-amlogic/pull/13 You will need a PC running Ubuntu 22.04 or emulated using something like VirtualBox. @GBEM made a good guide here : https://green.bug-eyed.monster/armbian-on-the-h96-max-v56-android-tv-box/

can it be compiled in currently running armbian ? my computer specs and internet speed is not decend enough to compile armbian from scratch, compile using github action may be a choice but i don't know how to do that yet. i attached the dmesg.txt with your dtb, my bluetooth seems incompatible with your dtb, and ethernet still not working dmesg.txt also added dmesg with default dtb (rk3566-h96-tvbox.dtb), bluetooth is working dmesg-hqnic.txt

I got SPDIF working. Just change the DTS node status to "okay". viz : spdif@fe460000 { compatible = "rockchip,rk3568-spdif"; reg = <0x00 0xfe460000 0x00 0x1000>; interrupts = <0x00 0x66 0x04>; clock-names = "mclk\0hclk"; clocks = <0x0f 0x5f 0x0f 0x5c>; dmas = <0x6f 0x01>; dma-names = "tx"; pinctrl-names = "default"; pinctrl-0 = <0x7e>; #sound-dai-cells = <0x00>; status = "okay"; phandle = <0xc4>; }; Edit : @Andre B The compatible = part was only to make the driver module load automatically. The driver module itself had to be first compiled into the kernel using source code from the chip vendor. I suggest you try my DTB (it might be close to what you need) and then post your dmesg as a file (sudo dmesg > dmesg.txt). my_rk3566-h96-tvbox3.dts my_rk3566-h96-tvbox3.dtb

This type of error occurred whe flash Etchdroid app can suggest any flashing app apk

This image flash use android phone

moved insufficient information.

Armbian_community_25.5.0-trunk.444_Radxa-cubie-a5e_bookworm_dev_6.14.0-rc1_minimal.img use to flash android phone echerdroid apk use for flash but not flashing proper not boot

My bluetooth is not working as well, but i fixed it with : rm -fv /lib/firmware/brcm/BCM4335C0.h96-TVbox,rk3566.hcd /lib/firmware/brcm/BCM4335C0.hcd sync wget https://raw.githubusercontent.com/unifreq/openwrt_packit/refs/heads/master/files/firmware/brcm/BCM4335C0.hcd -O /lib/firmware/brcm/BCM4335C0.hcd ln -frsv /lib/firmware/brcm/BCM4335C0.hcd /lib/firmware/brcm/BCM4335C0.h96-TVbox,rk3566.hcd sync reboot now i just need to make the ethernet work. i read @maka's reply to @WINEDS which just simply replace compatible = "ethernet-phy-ieee802.3-c22" line, so i search web for JL2101 compatible = "ethernet-phy-ieee802.3-c22", one of the result is https://blog.csdn.net/zuiaikg703/article/details/123892743 , i translated the top content into (more or less) like bellow : JL2101 is a domestic 1000M PHY IC that is pin-to-pin with Realtek Rtl8211F Since it has the same pin and supply voltage as RTL8211F, we first compiled it directly with the configuration of RK RTL8211F according to RK's suggestion: ICs such as RK3566 and RK3568 need to pay attention to the domain working voltage configuration. According to the actual hardware configuration, the corresponding voltage configuration is made in the software : PMUIO2 Supply Power Voltage1:3300000 VCCIO1 Supply Power Voltage1:3300000 VCCIO3 Supply Power Voltage1:3300000 VCCIO4 Supply Power Voltage1:1800000 VCCIO5 Supply Power Voltage1:3300000 VCCIO6 Supply Power Voltage1:1800000 VCCIO7 Supply Power Voltage1:3300000 @Hqnicolas, would you mind assist me to assign those values to rk3566-h96-tvbox.dtb ?