Active threads

hey @Nick A i have problem when connecting to the box throught adb connect, i have installed every dependencies before (i won't show ouput bc too long but it succesed) here is what i tried: i am using a virtual machine to do this work my uncle tried reset the prop on the tv box(mxq pro 4k 5g) (he's an android expert):

What does the following command show? sudo fdtoverlay -v -i /sys/firmware/fdt -o /dev/null /path/to/your_overlay.dtbo panel-simple-dsi ... Expected bpc in {6,8} but got: 0 So possibly the default with the older kernel was by accident correct and now you should define it. And it seems that you use an overlay meant for the 5a on a 5c?

Can you try if any of the H3 images from libre-elec would get you video acceleration? https://libreelec.tv/downloads/allwinner/ i once tried the orange pi pc image in my orange pi zero lts (h3) and it worked

Hi friends, back to the Gnome version which works incredibly well It works so well that I put my big desktop tower away and have been getting by strictly on this Armbian Gnome environment. I will be donating to Armbian soon However, I am curious, does anybody know how to fix the resume from suspend? For me, the computer goes into suspend mode just fine, but when I tap a keyboard key, the LED's will light on the keyboard indicating they have power, but the system never comes back. If I press the power button on the Orange Pi 5 itself, the system resumes perfectly -- no crashes, everything works as intended I just need it to work from a keyboard press instead! Thanks!

Exactly -- this is the same symptom I experience as well, plasmashell window popups with error reporting. Some retry buttons and so on, none of which do anything significant

That issue was just dealt with by disabling cruft instead. If you want to test a newer uboot with a reenabled cruft you will again need to go into building and testing, followed by a PR.

@laibsch It seems that if you set the pixel clock or refresh rate too high that you can shorten its lifespan. But when you use extreme values and the display doesn't have any protection in rare cases you can even damage it. A bigger chance is driver instability or a distorted display.

close investigation it seems to use grub, not bootp, card written does not show any activity of green led even after 10 minutes from powerup. Do you have some of the magic twanger needed to boot a pi? Thank you, gene1934

adding COMPRESS_OUTPUTIMAGE to your call will compress your image. $ ./compile.sh build BOARD=rockpi-s BRANCH=current BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie COMPRESS_OUTPUTIMAGE=xz [...] $ ls -lh output/images/*.xz -rw-rw-r-- 1 user root 342M Aug 15 01:03 output/images/Armbian-unofficial_25.11.0-trunk_Rockpi-s_trixie_current_6.12.41_minimal.img.xz

Bookworm is going to remain as an armbian-build option, right?

@mdidis do non secure boot images show any output. The one posted is an android uboot output.

It seems to me that Gnome is installed by tasksel because you didnt deselect it. I mean that gnome is selected by default.

I tried this patch https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3/blob/main/patches/1.5GB_OPZ3_fix.patch , ported to your u-boot (hardcoded 1.5gb), same result. Will try warpme or that sicxnull build, still wondering if I am on a red herring, I'll keep poking around and testing stuff. I'll post as I find things that work/don't work, hopefully this will help someone else too. And no worries, I'm sure your busy. You've helped a lot and helped me get a foundation. Thank you 💯 Log for notes:

Do you perhaps know how we could integrate this into Armbian? I don't know much about Gnome internals - came this far: https://github.com/armbian/build/blob/main/config/desktop/common/environments/gnome/debian/postinst

I was thinking the same. Must soldering the TTY cosolle so can getting the Uboot messages. The eMMC is the flash dead and have one Armbian on the SD-Card for jump starting the USB-SSD but the device used is only the USB-SDD i the demesg and it shall writing other devices if not booting one the USB-SSD and its the right one then HA is current and on the SD-Card is not updated. Shall i rewriting the bootloader on the USB-SSD but it shall being updated for some mouths ago ?

I second btrfs. I second-guess running bittorrent off SD cards.

@dale there’s a new patch to fix boards without external 32k clock. I haven’t tested it yet. https://github.com/warpme/minimyth2/commit/728a14a73924e349fe88fb4def7e5f50a79aed5c

I'm not sure what you're asking. I'm requesting information because I am seeing information stating that there is a working linux kernel that exists, but I don't know how to bridge that into a form where that kernel could be built or compiled into an image. Can what is on that github page be input into the build process? I've looked at what it takes to build Armbian from source and I understand the instructions when the board being built fits the categories in the instructions, but I'm not sure if that github kernel is useable or can be applied in that buidl process.

I see that the reported problem was raised in another topic:

There is certainly nothing planned. In general most of the open source community has moved away from working on amlogic based devices as the support from amlogic if lacking (and given the arm cpu space where all arm cpu vendors don't really support main line linux very much, amlogic is significantly even less supportive). So these days around armbian in particular most developers choose to invest there volunteer time in Rockchip cpus (and more recently some in allwinner cpus). But this is open source and community driven. So anyone is welcome to pitch in and do the heavy lifting to support it if they want. That is how most boards get support, is that someone with an interest volunteers to do the work.

Yep, I’ve been testing the 1.5GB version with Armbian. Images are still rough—some issues with AdGuard Home not starting properly after reboot, and a few quirks with networking. Promising board though, especially for the price.

Check if AdGuard is binding to the correct IP after reboot. You can verify this in the AdGuardHome.yaml file—make sure bind_host is set to 0.0.0.0 or your static IP. Also confirm the service is listening with sudo netstat -tulnp | grep 3000 and check logs with journalctl -u AdGuardHome.

The Mesa 25.2 release introduces support for AFBC compressed YUV textures in the Panfrost driver for ARM Mali GPUs, enabling more efficient memory bandwidth and power usage in video playback and real-time texture processing. View the full article

I am using Orange Pi Zero2 / Zero2W / Zero3 boards with the Allwinner H618 SoC and I am encountering an issue with I2C3 (mv64xxx_i2c). Board Details: Board: Orange Pi Zero2 / Zero2W / Zero3 SoC: Allwinner H616 Kernel: 6.12.35-current-sunxi64 (Armbian) Overlay: i2c3-ph (/boot/armbianEnv.txt: overlays=i2c3-ph) Pinout: PH4 = SDA, PH5 = SCL Problem: After boot, /dev/i2c-2 is created, but the bus is locked dmesg shows: [ 0.846937] i2c_dev: i2c /dev entries driver [ 1.479459] sun8i-dw-hdmi 6000000.hdmi: registered DesignWare HDMI I2C bus driver [ 1.484185] /soc/i2c@7081400/pmic@36: Fixed dependency cycle(s) with /soc/pinctrl@300b000 [ 1.501006] mv64xxx_i2c 5002c00.i2c: Error applying setting, reverse things back [ 1.501095] axp20x-i2c 1-0036: AXP20x variant AXP313a found [ 1.502779] axp20x-i2c 1-0036: AXP20X driver loaded [ 53.381005] i2c i2c-2: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 55.429017] i2c i2c-2: mv64xxx: I2C bus locked, block: 1, time_left: 0 Attempting rmmod: sudo rmmod mv64xxx_i2c rmmod: ERROR: Module mv64xxx_i2c is not currently loaded Bus /dev/i2c-2 remains locked System Information: Full system info collected via https://paste.armbian.com/vezeminihu What I have tried: Created a new overlay i2c3-ph for PH4/PH5 Configured /boot/armbianEnv.txt to load the overlay Rebooted multiple times, but the bus remains locked Verified pull-up resistors (PH4/PH5 connected to 3.3V) Questions: Has anyone encountered mv64xxx_i2c bus lock on H618? How should DTS / pinctrl / PMIC be adjusted to get the bus working? Is there a working example overlay for I2C3 on Orange Pi Zero3 / H618?

Short GPIO PIN13 and PIN14