All Activity

I think most important is that people make sure they can fix their own issues if a HW/computer fails. I found high-availability interesting, but for just my house (or even 2 places/countries at the same time) I found it too much to make it all work. The thing I could maybe use is DRDB, however I see v9 is under development since 2011 and it still is not in mainline kernel. Compared to that I have some script to transfer latest differential Btrfs snapshot from 1 computer to the other on-the-fly, I doubt I can really benefit from DRDB, but maybe I set up a test and see what it does. I use only ARM64 for 24/7 servers, so no x86_64 <=> ARM64 incompatibility. So same as for ZFS for example, it is external to Linux distro and my experience is that complicated issues/failures always happen at the wrong moment, e.g. also no internet and/or mains power failure etc. So I try to minimize the amount of 'external' HW/SW modules, certainly if the backing company is commercial and in whatever country far away from where I am. Proxmox is nice, but also 'external'. Same for even Docker, so I have actually no such containers. But it all depends on how much you are involved in various HW and SW. As you can see in my earlier message, I already forgot HA was available as generic aarch64 image, so that says enough. I use several custom (own) HW (like 'changed' solar inverter) and HomeAssistent does not support it, so I actually do not really use it. It is mostly C-code and Node-RED in conjunction with various micro-controllers. A good test is to disconnect internet (power-off fiber-RJ45 box in my case) and/or also do an ad-hoc power cut (no cheating with UPS). And then see if you can get it all running again within a certain time frame (what you think is acceptable, like before temperature in freezer gets > -10 or so).

@humanus You are a very nice guy!

Hi team, I am on the latest vendor release of gnome installed via armbian installer. Kernel is linux-image-6.1.115-*-rk2410. When I look for audio drivers I do not see card 3: rockchiphdmiin [rockchip,hdmiin], device 0: fddf8000.i2s-dummy_codec hdmiin-dc-0 [fddf8000.i2s-dummy_codec hdmiin-dc-0] Subdevices: 1/1 Subdevice #0: subdevice #0 I got the board very recently and the forum is a little mesay about the hdmi rx functionality. It would be a great help if anyone can help me out on this, let me know if i am missing anything.

The eMMC is still not detected. Kernel log: [ 4.621568] mmc2: error -110 whilst initialising MMC card [ 4.627066] mmc2: Failed to initialize a non-removable card Working devices: [ 4.502846] mmc0: new high speed SDXC card at address aaaa [ 4.508907] mmcblk0: mmc0:aaaa SC64G 59.5 GiB [ 4.551951] mmc1: new high speed SDIO card at address 0001 The system boots correctly from the SD card, but the onboard eMMC (mmc2) is not initialized. There are also still Ethernet issues. After connecting through PuTTY, the system sometimes hangs when running dmesg, and the network connection becomes unstable or unresponsive. System information: Thanks

@JamesCl Sorry, It's ok with 100m, but 1000m also doesn't receive an ip with dhcp. Guess it is a dtb problem or maybe uboot

Hi ... Thanks @Evgeniy evotronik. Yesterday I downloaded the image "Armbian_community_26.2.0-trunk.886_Orangepi-4a_trixie_edge_7.0.5_minimal.img.xz", but the Ethernet and eMMC issues are still present. I will apply the Ethernet patch. Thanks again.

to start ethernet #!/bin/bash echo -n "4510000.ethernet" > /sys/bus/platform/drivers/dwmac-sun55i/unbind 2>/dev/null echo 271 > /sys/class/gpio/export 2>/dev/null echo out > /sys/class/gpio/gpio271/direction 2>/dev/null echo 0 > /sys/class/gpio/gpio271/value 2>/dev/null sleep 0.1 echo 1 > /sys/class/gpio/gpio271/value 2>/dev/null sleep 0.3 echo 271 > /sys/class/gpio/unexport 2>/dev/null echo -n "4510000.ethernet" > /sys/bus/platform/drivers/dwmac-sun55i/bind 2>/dev/null just systemd it [Unit] Description=Fix ethernet PHY on cold boot After=multi-user.target [Service] Type=oneshot ExecStart=/usr/local/bin/fix-eth.sh RemainAfterExit=yes [Install] WantedBy=multi-user.target

Hi @Tavares R You should definetly check the "Media framework installer v0.1" by Jock, on this link -> https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/page/10/#comment-102655 Also, this other link contains a repo to install some patched libs to at least use decoded video -> https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/ Hope it helps, but reality check is the rk3229 is just too weak to properly handle a full DE running a modern browser... Something also worth trying is to enable the "cpu-hs" overlay. it will "overclock" the rk3229 from 1200Mhz to 1400Mhz, giving some extra performance, but keep low expectations... PS: Are you brazillian by any means? Tavares is a very common last name in Brazil.

@digital, there is not a lot of info about the 024c:b723 device you mentioned on linux-hardware.org, but there is a lot of people claiming it works on debian 10+. Some boards have alternate pins for wireless chips, hence there is an specific wifi overlay for those scenarios (attached pic). However, I would not recommend to add this overlay for now, until we find the exact wifi chip model from your board... Can you share more details form your board? Brand/Model would be a start, but pictures from the board, and specially the wi-fi chip would be the best. Also, please share the output of the commands below with us: 1- lsusb 2- lshw (install it with sudo apt install lshw) 3- dmesg | grep -iE 'wlan|wifi|wireless|80211' 4 - ip a 5 - nmcli

@Cammera, what are you exactly trying to do? Can you share what's your device model? Your screenshot is from the Android main loader, not really related to Armbian... If you are on this screen you already missed the boot window to start armbian... Take a look at the first post on this thread, but usually you should deploy an SD card with multitool or armbian nightly build, and when inserted, the boot screen from armbian will be different from yours...

@Morales Morales when I have more free time.. busy with work the next couple of months.

@eas07027 depends on the device... but since you are in the rk322x thread, I'm afraid there is no Home-Assistant-ready images for this specific stub, but if you have an arm64 device, it is easy to deploy armbian and then to deploy the Docker Home Assistant version using the official guides from home assistant. What is your device?

Hey @greg396, On top of previous answers, I'd like to suggest the read of this link: https://linbit.com/blog/home-assistant-high-availability/ If your home ecosystem grows, you will need high availability. Otherwise, turning lights on with your home assistant server down can become impossible depending your setup. If you have 2 devices, you can then create a cluster, so one can be backup of each other. I'm running this very same setup with 3 Nodes: 1 - Proxmox x64 VM (Main Node) 2- Tanix TXT arm64 Running Armbian (Backup Node) 3 - NanoPi Neo (Quorum Decider), running arm32 armbian. Nodes 1 and 2 are backups of each other and node 3# is a split brain tie-breaker.

I created this account just to thank you, man. Thank you so much, it worked perfectly here. Finally, my old TV box has another use besides collecting dust.

@Droll, something worth to check out is the SMB version your server is running... They have slightly different authentication, so the mount command differs a bit: SMBV1: sudo mount -t cifs -o vers=1.0,username=your_username,password=your_password //server_ip/share_name /mnt/myshare SMBV2: sudo mount -t cifs -o vers=2.0,username=your_username,password=your_password //server_ip/share_name /mnt/myshare

Suggestions will be very appreciated.

@Arthur Gu Thank you for the effort and congratulations for your success. I will try it in the next days.

@Nick A Hi, I was wondering if you plan to update your distro since it hasn't been updated since 2025.

yet still giving enough to write a answer. flaming over LPEs (or any vulnerability) does not solve any issues. I suggest to read the license again to get a clue who's responsible about fixing things in general: https://github.com/armbian/build/blob/5e60c0183d035bfd5179373e1eac284790e08904/LICENSE#L265-L268 Both parties also shall read the terms of use again, the very first bullet point in particular. I will not give this hint a second time. fixes will land upstream, stable builds will adapt four times a year. For everyone wants things faster, options were provided.

@Levy Barbosa I was able to boot and install! Instructions Download Armbian from: https://www.armbian.com/boards/aml-s9xx-box Use: - Debian 13 (Trixie) Minimal - Current kernel (6.18.26) Create bootable USB with Rufus/Balena Etcher. S805X-P241 Specific Changes After writing the image, before booting: 1. Set correct DTB - Open armbi_boot partition - Edit extlinux/extlinux.conf - On line 4, change DTB to: meson-gxl-s805x-p241.dtb 2. Set correct u-boot - In armbi_boot, copy u-boot-s905x-s912 - Rename copy to u-boot.ext 3. Boot - Insert USB into USB2 port (closest to power input) - Hold reset button (between USB ports) while applying power - Release after 15 seconds First Login Username: root Password: 1234 Change password when prompted. Notes - Wi-Fi works - Ethernet is 100 Mbps

TV Box Name: Intelbras IzyPlay Board name: DV8038 CPU: Amlogic S805X (GXL Meson, Rev D) Armbian build file name: Armbian_community_26.2.0-trunk.821_Aml-s9xx-box_trixie_current_6.18.26_minimal.img.xz DTB file used: meson-gxl-s805x-p241.dtb Kernel Version: 6.18.26-current-meson64 Distribution Installed: Debian 13 (Trixie) Working Ethernet: Yes Max Ethernet Speed that works: 100 Mbps Does wifi work: Yes Does bluetooth work: No Does HDMI audio work: Not tested (headless setup) Additional Comments: - Board has 1GB RAM (908MB available) and 7.3GB eMMC - HDMI output works (tested on a DELL P2219H) - Reset button is between USB1 and USB2 ports - USB2 port is required for booting (closest to power input) - To boot from USB: hold reset button while applying power, release after 15 seconds

Thank @iav

@iav Yes, thank you. I'll be able to test the PR for you next week.

@guenter I have resolved the NVMe SSD detection issue. The updated device tree access path is listed below. https://github.com/Arthur97172/Armbian-Community-Build/blob/main/patch/kernel/archive/rockchip64-6.18/dt/rk3568-yy3568.dts

@iav Thank you very much !