Active threads

Never mind, I found this old image with built-in desktop environment and I was able to upgrade it to current. https://users.armbian.com/jock/web/rk322x/armbian/beta/Armbian-unofficial_24.11.0-trunk_Rk322x-box_noble_current_6.6.56_xfce_desktop.img.xz

The display was working fine on 6.12, but has now stopped. I have tried the other kernels, the vendor has issues with passwords as well for some strange reason its not recognising the set password. I am going to look into the kernel, and kernel patches if I can work out what I am doing, but Armbian with its three fixed kernel versions is a nightmare and always has been. I have had exactly the same issue with BananaPi-M3. The fact Armbian will not build old versions is stupid. I can select older kernels using armbian-config and these work. If armbian/build would allow the user to select the same kernel images as armbian-config can this would go some way to solving this issue.

Open a terminal, type the command in question, provide us the output.

If boot from USB works, you don't need to install anything, just do 1st login config as described here: https://docs.armbian.com/User-Guide_Getting-Started/#first-login If boot from USB is not supported by this hardware (I don't recall if it works on N2+ or not), you need to start with SD card, conduct previous steps following by https://docs.armbian.com/User-Guide_Getting-Started/#installation

Please see https://github.com/armbian/community/issues/39

@HqnicolasI tried following your post but not successful. Do you have another method for that. Thank you.

B00-MX3mini-Ver1.7 2GB RAM eMMC Android backup for armbian-ddbr As promised here is the link to the factory android image eMMC backup for fake tanix tx3 mini s905l2-b box with 2gb ram. Obviously the image must be moved to the /ddbr/ folder and the armbian-ddbr command must be used to restore it from a working Linux system on a USB stick or microSD card inserted in the box.

Most likely a U-boot problem. Please see https://github.com/armbian/community/issues/39

@ScoreABSM https://github.com/armbian/build/pull/8394 I enabled gpu via overlay. Looking fine on my end. Tested using Chromium and Youtube. Still not sure about that audio dmesg error. Audio does work though. Image I ran test with: https://github.com/pyavitz/binary/releases/download/images/Armbian-unofficial_25.08.0-trunk_Bananapim4zero_bookworm_current_6.12.35_xfce_desktop.img.xz dmesgandmisc.txt

Just flashed an u-bbot version from here which does support NVMe...well at least it recognizes the SSD (o; https://github.com/cubie-image/sun55iw3p1/releases => pci enum Speed change timeout PCIe speed of Gen1 => nvme scan feng >>>> debug <<<<< nvme_probe => nvme device IDE device 0: Vendor: 0x1dee Rev: 1.4.7.70 Prod: 2510194702629 Type: Hard Disk Capacity: 488386.3 MB = 476.9 GB (1000215216 x 512)

Thank you Nick I tried again with compositor off I still get: [vd] Unsupported hwdec: drm [vd] Using software decoding. https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/page/4/

I have tried again with orange pi zero 3, debian trixie linux edge, xfce desktop. This time, I tried without compositor. I ran this from SSH, as my user: killall xfwm4 && xfwm4 --compositor=off & I got: (xfwm4:7880): Gtk-WARNING **: 10:45:56.629: cannot open display: Then I tried "killall xfwm4 && xfwm4 --compositor=off &" and there were no errors. The orange transparent effect when moving windows is now a white line rectangle Then, mpv played my 1080p mp4 with low framerate (slow motion, 75% of speed)... sometimes with 100% CPU and sometimes with 25% CPU I noticed this in the log (both high and low CPU cases) [vd] Unsupported hwdec: drm [vd] Using software decoding. With high CPU: [cplayer] Set property: user-data/osc/margins={"b":0,"r":0,"t":0,"l":0} -> 1 With 25% CPU: [cplayer] Set property: user-data/osc/margins={"l":0,"b":0,"r":0,"t":0} -> 1 Whole log (low CPU case): (Mpv.conf at the bottom) Another sanity check: Ryzer, did you turn the compositor off? Are you using an armbian-downloaded OS, or self built? What kernel version? DId you change anything in the linux menuconfig? I am recompiling again, having checked again that the new linux patches are taken.... how could I check that my current Linux kernel has the new v4l2, cedrus functions? Then I will try again with Bookworm

No, this board isn't supported. However anyone from the community can step up and add support for it. Found an attempt on Github:https://github.com/juanesf/build/pull/1

Correct way to provide logs: Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

We cannot support 3rd party OS.

What did you do to fix it? Others that come across this may find it useful.

I discovered something strange When powering on from being off it displays the bluetooth device but after a reboot it does not Any ideas?

Good afternoon! I bought a server home assistant. The web used to open. the interface is at 192.168.1.141:8123, and now it’s reaching armbian and I don’t know what to do next and I don’t understand why this happened either. I’m asking for your help. Has anyone ever had such a situation? If I created the wrong theme, can you tell me where to create it, or maybe there is already such a theme?

Ok, thanks

yes, see these two posts: and

Bug reported and fixed. https://bugzilla.kernel.org/show_bug.cgi?id=220261 Hopefully included with rc4

Hi, I tried the solution of extracting the idbloader.img from the official OrangePi image and flashing it at the appropriate address, as suggested in one of the previous posts. I tried this with the latest official Armbian Gnome image for OPi 5b. While it did boot, dmesg returned some errors and bluetooth did not work. I didn't inspect if there were more devices affected. The thing is that the boot process consist of several stages as described in the official Rockchip wiki: https://opensource.rock-chips.com/wiki_Boot_option Take a look at the "Boot Flow 2" in the boot flow chart. It involves idbloader.img and u-boot.itb binaries. Both are present in u-boot package inside the official OPi image. When I flashed both, each to the address specified in the wiki linked above, I got everything working. There is, however, an easier way to patch the bootloader. Go to Joshua Riek's Ubuntu Rockchip download page: https://joshua-riek.github.io/ubuntu-rockchip-download/ Download the image for your board and flash it to SD card. After flashing, copy the Armbian image to the same SD card. Don't forget to change the overlay (in the Armbian image) in the /boot/armbianEnv.txt as instructed in the official Armbian OPi5/5B page: https://www.armbian.com/orangepi-5/ Insert the SD card in your OPi5B and boot Ubuntu Rockchip from it. Open the terminal and use the dd command to flash the Armbian image to the emmc as described in the official OPi5B board user manual available at the board manufacturer's website. After that, just run sudo u-boot-install /dev/mmcblkX where you need to replace X with the appropriate number for your emmc (usually mmcblk0). This will install u-boot supplied with the Ubuntu Rockchip to emmc. Notice from the output that the command basically flashes the two binaries mentioned earlier, probably using the dd command. Power off, eject the SD card and try powering on. The board shoud boot Armbian from emmc.

I have been trying to set up labwc as a replacement for openbox (X11) in my project. I can install it very simply by building a minimal image Trixie (Bookworm does not include labwc), then * sudo apt install labwc seatd foot * at the screen with usb keyboard (not from SSH) start: labwc -d -s foot Then I am in labwc, with a terminal emulator on my HDMI screen When I right click on the desktop and choose "Exit", I get a kernel oops: And the labwc process shows "defunct" Has anybody experienced this? Maybe my kernel is too new? I used 6.15.4 (edge). My labwc is 0.8.3 The error in the terminal that started labwc (the HDMI screen) is: ...wlr_drm_lease_v1.c:103] Destroying wlr_drm_lease_device_v1 for /dev/dri/cardiationsodifier LINEAR (0x0000.....) XT_EGL_image_storage_compression GL_EXT_texture_storage_compression GL_MESA_bgra im... Same error message here: https://github.com/labwc/labwc/issues/1424 Source of wlroots, mentioned in the error: https://github.com/swaywm/wlroots/blob/master/types/wlr_drm_lease_v1.c A developer in the labwc group suggest this might be GPU driver related https://github.com/labwc/labwc/discussions/2923 Can someone with an SBC other than H618 try running labwc and exiting? What about xfce in wayland mode... does it crash? Is anyone aware of a H618 or sunxi running wayland successfully?

Hello everyone, I recently bought an used Helios64 NAS without AC Adapter. I found some adapters on AliExpress (for Italian country) but I don't know the PIN disposition (about the polarity, V+ V- etc.) Could someone of you share a photo of the original Kobol Helios64 AC Adapter with the polarity details? Thanks.

Thank you.