Active threads

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 ?

Hi, yes, I agree, but I am only a user of Armbian and I do not have such skills to do this solution you suggest I can check the available Community Releases of Armbian and check how it works. Community editions, which are issued for testing and updated on average every week?

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

In addition to what Werner said, I would like to point to the option of not installing recommended packages. "sudo apt install --no-install-recommends lxqt". Personally, i like to use aptitude for package management for more control and transparency.

Yes, followed the guide you linked on the other thread. Here is my dts. sun50iw9.dts

@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

@Ducdanh Nguyen hard to tell. I don’t see any markings for uart. It’s not going to be easy to debug your board.

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.

@Randlin have you tried adding secure boot to @sicxnull build. If that doesn’t work you’ll need to play with the dram code. I don’t have time or a 1.5g board. https://github.com/sicXnull/armbian-build/tree/X96Q-TVBOX-LPDDR3

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?

I'd do it in a 'simplier' way, just use a new uSD card, that is partly a benefit of SBCs running on uSD cards.

Thanks for your feedback. But as I wrote, it looks like hw accel works in general when checking the much lower CPU load vs. the fps. CPU 4x100% => ~10fps HW 1x20% => ~6fps Thats why I think the VPU really gets used but not optimal. btw. I did not yet get mpv to work with frambebuffer. T.

Short GPIO PIN13 and PIN14

Thank you so much for your generosity, @coroner21. I shall do my very best to keep the machine well maintained in Armbian.

Getting the grub bootloader right with tow-boot's efi implementation seems like the most urgent as it is a hard blocking anyone trying to install. As tow-boot isn't unique to pinebook pro my guess is that handling it impacts other systems. I don't know what would be involved in maintaining it.

hello everyone! I bought this tv box..https://www.aliexpress.com/item/1005009346784515.html?spm=a2g0o.order_list.order_list_main.11.79e81802pgNRxu but after starting it was not possible to log in to googleplay even though I had a connection via wifi or ethernet. the preinstalled version for applications was Aptoide TV..through it I wanted to update all applications (youtube, netflix, etc.) I managed to do that but no application could be started. the original file manager did not show the internal memory or USB disk or SD card until I managed to download ES file manager through aptoide and it showed my flash disk I installed HW info device and there I found out that it was an RK3528 chip. so I wanted to flash the firmware and I used a rom image for H96max with the same parameters. the firmware upgrade went OK but the device is dead. I can't find the correct firmware. I'm attaching a photo--- maybe someone will recognize the board and identify which rom-img should be correct. the seller can't help me in any way.

yep, thats how i connected them i think it might be that? ill try to get some fresh wires and see if it helps

I also confirmed that USB-C functionality is still not working on ODROID-M2 with Kernel 6.16 RC. I guess we would have to wait a little more for the working USB-C Port.

Depending on your location this might not be anything that can be fixed on Armbian side. If this happens on any mirror, the issue is either your setup or ISP blocking access.