All Activity

I'm more concerned about what version 5 might break. Still, I don't think anyone makes Facebook account in order to login to Armbian forums 😄 and GitHub is not far from those I am afraid By the end of the day, this would be a symbolic gesture that works against practical ways. I think most of people uses Google login connector. Do we have any stats for that?

If this worked for you, I propose to open a PR, so there is a GitHub record of your work. Add it here https://github.com/armbian/build/tree/main/patch/kernel/archive/sunxi-6.12 Here you also need to pay attention to add to series* files.

All good now?

fwiw I was able to build a set of Armbian kernel packages based on 6.16-rc1 and this patchset: https://lore.kernel.org/all/20250619173007.3367034-1-wens@kernel.org/ If it works, no clue, don't have the hw. Just played around. https://github.com/armbian/build/pull/8330

as I've not been running X11, I can't really help with this, but among the things, check the logs during X startup, that could lead to the cause. note also that more recently, the display systems are running wayland rather than X11. that could cause xfce etc to fail if it is expecting an X11 based setup it is also recommended to bootup in the uart console (debug) port using a usb-uart dongle. - the benefits are numerous, the boot messages are mostly presented - it provides you with a console to login and check things while the system is running e.g. to login and check dmesg and other logs - essential especially when re-wiring network configuration

Once we do the major bump to v5 we should focus on getting Github to work and - if reasonable - drop commercial proprietary logins like Facebook and so on. Less pain, more freedom

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Wow Tnx A LOT .. @Nick A .. your img work perfect to me .. download that image Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_server.img burn to sd sudo dd if=/ISO/H313/Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_server.img of=/dev/sdk bs=4M intro with ssh ssh root@192.168.X.X check the partitions lsblk burn to emmc dd if=/dev/mmcblk1 of=/dev/mmcblk0 bs=4M status=progress e2fsck -f /dev/mmcblk0p1 resize2fs /dev/mmcblk0p1 turn off = shutdown -r now remove the SD, reboot Enjoy. If dont works, try with gparted .. sudo apt-get install gparted sudo gparted resize

I have orange pi zero 3 4gb, I had gnome installed but when i installed xfce with lightdm and rebooted, its stuck on the armbian splash screen with the loading wheel, any assistance?

@Nick_SlTried everything, the same module in a raspberry pi 4 works, but in the orange pi 4A no, I tried to get the output signals using an oscilloscope, the signals are inconsistent and have a lot of noise, maybe there is an issue with the i2c kernel driver.

Indeed. Comparing sources between kernel 6.12 and 6.15, I could only spot one difference in the drm_atomic_helper_connector_hdmi_check() function so I have tested applying this via a patch and the build compiled successfully. Testing the build I found that reboot now works and shutdown finishes with just a blank display. If it is indeed the same issue then this patch will likely fix the problem. Based on what I found it may impact certain Rockchip Socs also: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/display/drm_hdmi_state_helper.c?h=linux-6.15.y&id=0d337b40ca1e532af42516d9e9024baad466319a drv-drm-atomic-helper-null-pointer-fix.patch Thanks Ryzer

And how to compile openvfd with this patch? How to apply this patch to openvfd?

Not supported by forum software. Keeping Facebook and Google operational requires constant attention and adjustement, while others worked so far without troubles.

Added instructions for joining your home lab: https://docs.armbian.com/WifiPerformance/#adding-a-new-device

Hi and thank you for the advice. The USB end of the dongle goes to my desktop PC. I compared the time stamps of the last issue and found that the PC was actually switched off during the last issue, having been switched on 10 minutes after the last sysrq log entry. So for the moment I will watch the findings of auditd, although the startup msgs from yesterday looked somewhat suspicious (?): 2025-06-23T18:23:09.799581+02:00 bananapipro2 systemd[1]: Starting auditd.service - Security Auditing Service... 2025-06-23T18:23:09.910646+02:00 bananapipro2 auditd[18408]: Audit daemon is low on disk space for logging 2025-06-23T18:23:09.911684+02:00 bananapipro2 auditd[18408]: Audit daemon is suspending logging due to low disk space. 2025-06-23T18:23:09.912308+02:00 bananapipro2 auditd[18408]: No plugins found, not dispatching events 2025-06-23T18:23:09.917468+02:00 bananapipro2 auditd[18408]: Init complete, auditd 3.0.9 listening for events (startup state enable) 2025-06-23T18:23:10.181350+02:00 bananapipro2 systemd[1]: Started auditd.service - Security Auditing Service. Greetings.

That should make it. You can always try to see if it works and search online if not.

Is it enough to remove these entries from the dts file and recompile it to dtb? 3535-3540 openvfd { compatible = "open,vfd"; dev_name = "openvfd"; status = "okay"; phandle = <0x143>; }; 4031 openvfd = "/openvfd"; meson-sm1-x96-air-gbit.dts

But how do I do that? These are the original Armbian .dtb entries. I didn't add anything and I don't know how to remove it.

Armbian_25.2.2_Rock-5-itx_noble_vendor_6.1.99_gnome_desktop.img.xz I first tried this, as it was the first version offered at the top of the page. No matter what I tried, sound would *not* work. Not speakers, not HDMI, nada, zip. I then started trying earlier versions further down the page. Armbian_25.2.2_Rock-5-itx_bookworm_vendor_6.1.99_cinnamon-backported-mesa_desktop.img.xz And this one, sound *did* work, at least through the speaker jack anyway, but I suspect HDMI would too. I'm really suspecting something kernel related is going here (that "Rockchip BSP" note right above it makes me suspect that). In any case, I'd like to use the kernel where sound is working and put a gnome shell in front of it. Which I take means digging into the build system for armbian? I can figure that out on my own but before I get started on that, what I'm looking for from the forumistas, is an indication of which specific kernel I need to use to make sure sound works. What do I need to make sure to specify so I get the behavior of that second install that worked? And Cinnamon may be better or something, but gnome is what I'm used to.

FYI. HDMI out is broken on those board at the moment. Try to access the board remotely. We don't have people to maintain those old boards.

I've noticed some other threads about Banana Pi builds not booting. I tried the 6.12v built on Jun 19 and that's when my device stopped booting. It won't even power on. I suspect the firmware update is corrupting the MicroSD card. I originally had an older build running and ran an update/upgrade and my system wouldn't boot (won't power on) after that. I purchased a new MicroSD card, and my system booted with an older build. Not realizing my MicroSD would get corrupted, I tried updating/upgrading again and I'm back to not booting. I don't have enough MicroSD cards to pinpoint the exact package. My working build is from 6.6.17, 24.5.0-trunk.58. It appears the archive is even older than that! Is there any way to revive a MicroSD card? I'm using SDFormatter to prep the card and Win32DiskImager to write the image.

Your commands looks ok, but you need to use hk1-x3, not hk1-box Your runtime device-tree do contains the display-controller under /proc/device-tree/i2c-display. So your correctly copying your dtb, but device-tree/i2c-display/sda-gpios and device-tree/i2c-display/scl-gpios shows pin of hk1-box, not hk1-x3. You also need to remove any references to OpenVFD from your device tree. This will create conflicts if you have multiple nodes using the same pins. Your dmesg also has some messages about the i2c bus on which is connected your display controller: [ 3.787786] gpio-576 (sda): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 3.792897] gpio-577 (scl): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 3.802509] i2c-gpio i2c-display: using lines 576 (SDA) and 577 (SCL) If course, you need to first configure the right pins by using hk1-x3 (and removing openvfd). Then you can investigate remaining i2c issues, if any.

Here are the actions I take with the dtb file. Maybe I'm doing something wrong here? # cd /home/INSTALKI # git clone https://github.com/jefflessard/tm16xx-display.git # cd tm16xx-display # cp /boot/dtb/amlogic/meson-sm1-x96-air-gbit.dtb original.dtb # make hk1-box.dtb ORIGINAL_DTB=original.dtb # cp release/hk1-box.dtb /boot/dtb/amlogic/meson-sm1-x96-air-gbit.dtb # reboot

In the /proc/device-tree directory I do not see any "tm16xx" entry but there is an "openvfd" entry. Attached is the /proc/device-tree directory and the dmesg output. device-tree.tar.gz dmseg.txt