Active threads

No problem installing Armbian stable 23.11 (or 23.8) and then upgrading to 25.2.3. Don't use nightly/trunk... francesco@orangepipc2:~$ uptime 08:32:44 up 29 days, 16:57, 1 user, load average: 0,26, 0,64, 0,36

This is not uncommon. Very few boards have hdmi support at boot level since developing this feature is expensive and simply not worth since the console output is also available via debug serial console where adapters for those are dirt cheap. To get an idea what happens inside you have to grab these logs and provide them. https://debug.armbian.de

Hi @Hqnicolas, could you please help to tell me how to flash this official community image? it seems can not upgrade the firmware directly

Hi @Zaf9670, Your situation actually helped find an OBOE in the U-Boot image overlap test, so thank you for that! Can you try with an older image and share the U-Boot output? Also, can you add the following in your armbianEnv.txt: verbosity=8 earlycon=on console=serial I've had better experience with setting console to serial only and earlycon might help the kernel spew out some things earlier on. Groetjes,

Nope, not gonna happen. If anyone spot something, let me know, I'll wait for 25.5 and kernel 6.1.115 and hope for the best.

Yes I verified that its there. But im suspecting something though. I have a NAND rk322x and using jumpstart to boot armbian using sd card, can that possibly causing this issue? edit: nah scratch that, I snag my on emmc model and tried it there but this time uboot did throw some useful stuff it relates that it cannot load the dtbo file? I cd to the directory and it was there. edit2: managed to partially get the OTG port working, just have to edit the dtb file on my own instead of relying on armbian-config now the otg functionality kinda works? I ended with this error and basically clueless at this point [ 76.310374] dwc2 30040000.usb: new device is high-speed [ 76.310458] dwc2 30040000.usb: dwc2_hsotg_enqueue_setup: failed queue (-11) pi-kvm is partially working, the usb capture and everything works except for the USB OTG so no remote keyboard/mouse functionality.

It is diffucult to add certain advanced features to both / all base packages versions - which is the core difference between Debian and Ubuntu. And later more difficult and certainly less fun is keeping features operational. This is one of the main points behind providing both variants. Making assembly (Debian Bookworm, Ubuntu Jammy, Noble, ...) is easier, and cover several other aspects too, then adding and maintaining advanced features for both / all. Sometimes its nearly impossible (our resources are not endless and we have to remember we are in open source world - forks compete without contributions to commons) to add something to one, while its relatively easy adding it to another. At the end of the day, it is, like you said, more important that some feature works.

CP2102 are not capable of 1.5 megabaud in linux

$ xz -t Armbian_25.2.1_Khadas-edge2_noble_vendor_6.1.99_gnome_desktop.oowow.img.xz $ echo $? 0 Check your download. Probably corrupted.

Hi, Very good news. Could you please give output of following commands cat /proc/cpuinfo cat /proc/interrupts Thanks in advance

wireless-regdb is already installed and apt returns E: Unable to locate package crda for crda. Thanks for trying to help

Some chips that support 1.5Mbaud and more: - FT232R - CH340G - CP2104

GPU blacklisted the panfrost module Has it been resolved？ Thank you

It's the link up/down problem. Never seen this under bullseye but it happens on bookworm

after some research i have (finally) found the original archives form balbes. they can also been burn to the internal eemc. with some work you can run bookworm with kernel 3.10.99 (dont ask why) from the internal storage... https://archive.org/details/amlogic-s805-linux tks for 0jw4tts witch uploaded those files to archive.og !!!

Guys, does anyone know how to enable the TV Box's wifi with the ik316 process? I downloaded armbian, the only thing missing is wifi. Data transmission works with a network cable, only the wifi is having problems. The iso I downloaded was Armbian-unofficial_25.05.0-trunk_X96q-lpddr3_bookworm_edge_6.12.11_xfce_desktop.img.xz

No logs - no issue. https://debug.armbian.de

Be aware that the answer might depend on the filesystem you are using on your board Be aware that a resize operation can easily destroy your data or at least make it inaccessible have a look at shrink-backup for "reverse"

@Popolon indeed this issue rot for a long time. I cleaned up my backlog to have more time for armbian. Also I still have quite a few processes to learn about armbian board maintenance still to this day. But you confirm that with mainline 6.12 all is fine ? But, indeed no HDMI out and no audio. I still have a patch for mainline 6.12 in the pipe about a race condition between SATA chip and nvme as far as I remind. I will prioritize data vendor kernel debugging if this mainline patch is not required (and indeed mainline still lacks any multimedia capability, this might be a showstopper for most users) even though I am close to complete testing and send PR for this one. As of now I have confirmed that this mainline patch set does not help vendor as the vendor branch has a hack that workaround the issue that mainline faces about this SATA/nvme race.

100mbps is enough for all my projects. if not, there are some usb3 gigabit adapters

Looks like the server images uses systemd for network control, but desktop images use network manager. I believe this should build the server images with network manager: ./compile.sh NETWORKING_STACK="network-manager"

Network bridge is added within armbian-config Docker install ... Perhaps open a ticket https://github.com/armbian/configng so this is eventually done properly.

@ZjemCiKolege than you! Now wireless is activated by the overlay. @c0rnelius wifi ok but I'm still missing bluetooth (pb with the controller). See dmseg attached. dmseg-H-wifi-bt.txt

Issues with the build framework, building Armbian to say, should be reported in the framework repository. https://github.com/armbian/build/ Make sure you include full logs. Use the curl command at the very and of the process or use SHARE_LOG=yes as build switch. Otherwise report might be rejected.

Thank you, I will study it.