Active threads

This was the best working version, I also have bionic https://www.dropbox.com/scl/fi/cubr0yu3t9garv3rxzarg/Armbian_5.67_Aml-s805_Debian_stretch_default_3.10.108_desktop_20181207.img-1.xz?rlkey=remqj5qcnwyjl3t943qj3uh4l&dl=0

Tomas. In regards to SteeMan writing that we could 'brick' our tv box, I have recovered two tv boxes that have an amlogic chip in them. Here are my and others' notes. Some more notes there about how to install/reinstall Android for the sake of installing Armbian maybe also be useful.

Hey - thanks for Webmin. That looks pretty slick. Nice graphics. I am going to have to do a deeper dive against cockpit but very nice. I bet both work with Tailscale which makes for nice for remote access.

Generally debugging is done through the UART connector: https://debug.armbian.de/

I would first suggest that you read this post: That may give you lots of reasons why you shouldn't depending on what your goals are. Installing armbian on a TV Box depends on the TV Box. Each CPU has differing levels of support (from none to fairly well supported in mainline linux). And then given there are hundreds of different TV Boxes, each will have different sets of working/non-working features depending on a variety of factors. As far as supporting a USB audio device, it shouldn't be any different than support for the device on any other linux platform/distribution. On Armbian you may need to install the linux-firmware-full package to get the driver support as by default Armbian ships with a slimed down set of firmware support.

Thank you!

Oh right, that is fairly old. My USB sticks are not in exFat format which may explain why I have not encoutered such issues. I will have to try re-formatting one as exFat to see if encounter the same kind of issue. That said after a bit of digging, it could be related to this? https://www.cvedetails.com/cve/CVE-2025-22036/

That is a wise thing to do and might be a good default for armbian to adopt.

OK, can you do the following for me, please, to be sure this is properly fixed? Kindly share the console output for me to have a look at. sudo apt reinstall wireless-regdb dpkg -S /lib/firmware/regulatory.db* Then reboot and see if your problem remains fixed. For now, I suggest you keep the wireless-regdb-2025.02.20.tar.xz file around on the NanoPi in case you need it again.

This is nothing new, its Windows related issue. Probably had something with the drivers. But ultimately I just use a older windows version, I had a machine running a Windows 10 1809 LTSC and for some reason it works there. One thing that also works is using a ubuntu live CD and using the upgrade_tool for rockchip.

Collabora is proud to sponsor this year's annual Debian conference, taking place in Brest, France. Join us as we showcase the latest with Apertis, discuss Debian running on mobile devices, and more. View the full article

Ur welcome.

Ugoos AM9 DTB extracted from stock firmware,if it helps someone. AM9dtb.zip

https://debug.armbian.de

Armbian Development Report: Continued Progress and Community Momentum Over the past two weeks, the Armbian project has made steady and meaningful progress across core infrastructure, board support, and kernel development. From bootloader improvements to expanded hardware compatibility, our contributors continue to push the platform forward. This update highlights recent technical advancements, bug fixes, and community contributions that help power the Armbian ecosystem. Highlights Pcduino2/3 Gain HDMI and Display FixesHDMI output is now supported, and a regression affecting display output on Pcduino2 and Pcduino3 boards has been resolved.#8341 Key Bootloader and Memory EnhancementsUpdates include a boot fix for Inovato Quadra, u-boot bumps for Banana Pi Zero3 and 2W, and the addition of 1.5GB memory support.#8334 Enhanced Repository SecurityImprovements include a new signing key, dual signing support, and better GPG key handling via APA.#8323, #8320, #8316 Improved TI Board SupportTexas Instruments boards now benefit from a custom Debian repo, pre-installed packages, and a Real-Time (RT) kernel config option.#8305, #8280 Meson64 Security BoostKernel Address Space Layout Randomization (KASLR) is now enabled by default to improve runtime security.#8354 New Features Add rtl8723ds Bluetooth support to Gateway GZ80x Add HDMI support for Pcduino2/3 and fix sun4i-drm regression TI: Add Debian repo and default packages TI: Add Real-Time kernel config for current Bug Fixes Fix Odroid-C4 I2C overlays (6.15 kernel) Fix I2C overlays for Odroid-C4 Fix WAN interface naming on Nanopi R6/R5 (Netplan rules) Fix DP alt mode on some rk3399 boards (6.15 kernel) Improvements Enable KASLR in Meson64 config Enable USB serial on PocketBeagle2 Add GPIO names to Rock-5C DTS Update u-boot and fix Bluetooth on BPI-M4-Zero Align Rock-5B-Plus edge kernel (6.16) with upstream Allwinner: Bump current to 6.12.35 and edge to 6.15.4 Re-enable xradio wireless driver for Allwinner 64-bit Bootloader/memory improvements for multiple boards Update SpacemiT kernel to 6.6.95 Remove WiFi patches (merged upstream in 6.16) Refactor Rockchip64 patches Bump Rockchip64 edge to 6.16-rc3 Enable Ethernet & USB serial modules on Beagle boards Add new GPG signing key Support dual signing of repos APA: Handle GPG key installation Update TM16xx driver for Rockchip64 edge Community Contributions @veduco @pyavitz @Ayush1325 @EvilOlaf @Ryzer58 @HeyMeco @igorpecovnik @amazingfate @paolosabatino @jsuhaas22 @hyx0329 @leggewie Stay Connected with the Community Looking to join live chats with Armbian developers and users? The Armbian Community Calendar lists upcoming voice chats, planning sessions, and community events. Stay informed and be part of the conversation! The post Armbian Development Highlights first appeared on Armbian. View the full article

Hi, I haven't posted for a while since I don't have an OrangePi 4A, just a Cubie A5E. I compiled Armbian for OrangePi 4a, kernel 6.16-rc4. No video yet, just a serial console. Can anyone test the image? https://github.com/juanesf/build/commits/Opi4A/ https://paste.armbian.com/ranagabiku https://drive.google.com/drive/folders/1dx0TApPAEjFDz24Rm22J4jgtIbJrYYHC?usp=sharing

@Nick A good news, everything seems to work except emmc. For now I'll just use the SD card. Thanks again for the help Update: I messed around with the device trees and found out that eMMC works if the frequency is lowered to 12Mhz as done in this patch: https://github.com/sicXnull/armbian-build/blob/333e462466670e9a8609771ccd05977b87800881/patch/u-boot/u-boot-sunxi/board_x96q-v5-1/sunxi_mmc-dec-f_max-to-12MHz-to-get-emmc-reliable.patch Maybe the next x96q-v5.1 builds can just use the x98h base with this patch applied

Hi Guillame, I forget how many hours/days I worked on this to get this box to work and at times I felt like chuckin it in the wastebin! It's not in a github, sadly, but all the info is here in this thread - I tried to document my madness as I went along and as you say I am very indebted to Nick and others for getting me started and the help he provided along the way. In the end I just moved to a Raspberry Pi as it was so much easier lol But I think I have a working SD Card somewhere. I got everything working, including the remote, with the exception of the onboard wifi chip had no drivers for Armbian, that may well have changed by now, I don't know, but I just used a wifi dongle with wifi and bluetooth - It's here in the thread. I can image the sd card if you have somewhere to upload it to - maybe start your own github and let me uploaded the img there to get you started? Regards, Mark

Once PR is merged, automated nightly beta repository has this kernel within hours.

Thanks! 🙏

please share more information about the problem you ran into for the sake of the next guy coming to the forum to look for a solution to the same problem. Thank you.

I am checking now Before installing plymouth, I checked that panel-mipi-dbi-spi is still loaded late: I added the include-lcd-bin.sh and installed plymouth: Checking that my bin file is there: The LCD works with plymouth: it starts the LCD earlier, with a smaller font, then switches to normal font, showing all the boot messages My armbian is not setup yet with lightdm+openbox (x11) or greetd+gtkgreet+labwc (wayland)... I will continue tomorrow

I am using my orange pi zero 3 with an SPI 4.0" LCD, with driver panel-mipi-dbi-spi. It works great with Linux 6.13.7 (started with a self built image with edge, minimal, Bookworm) and older, but I am having troubles with 6.14.8. Result from armbianmonitor -u after upgrading to linux 6.14.8: sudo apt install linux-image-edge-sunxi64=25.5.1 I reboot and the SPI LCD starts the text mode console, then turns black instead of starting lightdm https://paste.armbian.com/ucoxuwetiq Also xorg log after "sudo startx" fails to start. When I start the opiz3 with an HDMI screen connected (appears as /dev/fb0), startx and lightdm start normally, but NOT displaying anything in the small LCD Then, I downgrade to linux 6.13.7, sudo apt install linux-image-edge-sunxi64=25.2.3 I reboot and lightdm starts normally in the 4.0 LCD https://paste.armbian.com/uqafuxexiv Stopping lightdm and trying x11 to see the log sudo startx ... starts xorg normally Just downgrading to Linux 6.13.7 allows the 4.0" SPI LCD to work again. Dowgrading the linux package did not cause a downgrade of X11 (version 1.21.1.7). The small LCD always works ok in text mode. The driver is DRM but it is using the X11 fbdev submodule The fbdev.conf file: Using an HDMI screen is not affected When I disable the fbdev conf file sudo mv 99-fbdev.conf 99-fbdev.conf.disabled Then x11 fails in another way: The xorg log doesn't show any error: dmesg|grep MESA shows nothing. Probably here is the solution https://github.com/agherzan/meta-raspberrypi/issues/1389 rebuilding mesa with some extra dependencies Bookworm containg mesa 22.3.6 right now, but Trixie contains mesa 25.0.5 I tried the same in Trixie and Sid, but still get the same error: not able to load panel-mipi-dbi_dri.so I have a newly built armbian OS with kernel 6.15.x... I will try it later today.

@Turbine Thank you, I had this problem and your solution was spot on. Problem fixed.

some progress $ sudo rfcomm bind /dev/rfcomm0 41:BB:00:D0:D3:D8 && ls -l /dev/rfcomm* crw-rw---- 1 root dialout 216, 0 Jul 7 22:46 /dev/rfcomm0 but $ sudo hcitool info 41:BB:00:D0:D3:D8 Requesting information ... Can't create connection: Input/output error