Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Me too. I was not paying attention to this due to dealing with many non technical things in past few months and as already mentioned, those upgrades are not being tested on older boards. We simply don't have enough resources, test automation is limited - HDMI is not tested in any case. There is more or less just one main person doing general maintenance on Allwinner with occasional help of random people. 6.14 is already EOL and we just switched to 6.15 (EDGE branch), but we will probably stay on stable CURRENT branch with 6.12.y for awhile as its fairly stabilized in general across several platforms. IMO it is best to backport this patch for 6.12.y or fix whatever breaks this.
  3. @Igor I can only guess that something has changed within the drm framework somewhere between kernel 6.6 and 6.12. After a bit of digging I did find the patch mentioned in my previous post, which I can confirm does restore HDMI functionality albiet with what appear to be minor errors. Taken from Pcduino3: ryan@pcduino3:~$ sudo dmesg | grep drm [sudo] password for ryan: [ 1.000426] sun4i-drm display-engine: bound 1e00000.display-frontend (ops 0xc0caec14) [ 1.000666] sun4i-drm display-engine: bound 1e20000.display-frontend (ops 0xc0caec14) [ 1.001260] sun4i-drm display-engine: bound 1e60000.display-backend (ops 0xc0cae380) [ 1.001797] sun4i-drm display-engine: bound 1e40000.display-backend (ops 0xc0cae380) [ 1.002745] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 1.002787] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc0cac870) [ 1.003623] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 1.003671] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 0xc0cac870) [ 1.005703] sun4i-drm display-engine: bound 1c16000.hdmi (ops 0xc0caf610) [ 1.007882] [drm] Initialized sun4i-drm 1.0.0 for display-engine on minor 0 [ 1.068719] sun4i-drm display-engine: [drm] *ERROR* Unsupported infoframe type: 131 [ 1.068755] sun4i-drm display-engine: [drm] *ERROR* Unsupported infoframe type: 129 [ 1.126922] sun4i-drm display-engine: [drm] fb0: sun4i-drmdrmfb frame buffer device [ 4.022304] [drm] Initialized simpledrm 1.0.0 for 7e000000.framebuffer on minor 1 [ 4.150136] simple-framebuffer 7e000000.framebuffer: [drm] fb1: simpledrmdrmfb frame buffer device [ 4.537321] [drm] Initialized lima 1.1.0 for 1c40000.gpu on minor 2 [ 8.416996] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm... [ 8.783119] systemd[1]: modprobe@drm.service: Deactivated successfully. [ 8.785117] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. kernel 6.14 already has the changes adopted so does not need to be patched. I appreciate that boards like the pcduino2 are over a decade old now and not likely to achive the same attention as something like the orange pi zero.
  4. Did you make any progress with this? Also looking to build something with I2S.
  5. I have noticed regression on A20, probably also on A10 few weeks ago ... but so far we haven't been able to do anything - almost no active developer have those boards. ... and Welcome!
  6. From https://github.com/morrownr/8821au-20210708
  7. Welcome! This question is a bit off topic here as general Armbian updates are not part of HA extension. As this is community supported hardware, stable BSP upgrades - where OS version is stored - might not be generated, while kernel and everything else is getting upgrades. tl;dr; Don't worry about this. For board related topics proceed here https://forum.armbian.com/forum/173-allwinner-sunxi/
  8. Hey if it’s still available I will pay the shipments
  9. Hey, @arbeiter! It shouldn't be necessary to put the device in Maskrom mode, Loader mode should be enough - you can do that by using a toothpick to activate the reset button in the 3.5 mm jack (example photo attached) before plugging the device with the USB-A-USB-A cable. For the flashing - you should run rkdeveloptool ld (to list recognized devices) and see if the box is in LOADER mode rkdeveloptool write 0 Ambian-unofficial... Here should be the latest gnome desktop verison that I compiled. Please be advised that your version is M9S and, as far as I know, the only difference is that M9 comes with Android and M9S comes with Android TV; this image hasn't been tested on M9S. Don't forget to freeze the kernel updates from armbian-config; you should be able to update the other packages normally after this. For me the box has been stable, no hangs whatsover and, as described, the VPU and the NPU work, but the GPU doesn't (that's why it's blacklisted). Haven't tried the remote nor the LCD screen.
  10. Was this 8812au.ko in the lib/modules folder originally, or did you copy it from somewhere else?
  11. I'm not aware of any support by mainline linux for this processor. Maybe in a few years, but in general, Amlogic doesn't work with mainline linux to get their cpu's supported, so there is unlikely to ever be any support outside android for this box.
  12. Hi Ryzer, thanks for your response! Okay, I will be on the lookout for some updates in your branch "pcduino2-and-3-improvements" and try again. Thanks for all your efforts to keep those old boards running!
  13. Hello! I'm new to the Armbian world! I have successfully downloaded and got my OrangePi Zero 3 working on my end, but I do not know how to do updates. I've done apt update + apt upgrade and armbian-upgrade and they went fine, but I still see V25.2.3 upon entering the SSH session. To upgrade to latest V25.5.1 I need to to something else, or maybe wait until you update, or I need a fresh reinstall? Sorry if this seems a basic question. Anyways, thanks for your contribution Igor! I can run other things along Home Assistant with this image!
  14. Hello, Have a Helios64 - was/is running on Buster and is no longer required. If anyone is interested, just pay for the postage. I am based in UK. It also has the wire strap for the 2.5G Network issue. Available without any drives. If a new home is not found by Aug-25, will dispose into a recycling center. pls contact me by private message. **** i5Js has adopted my Helios64. , thanks *** no longer available
  15. @Igor Just tried with the latest image on https://dl.armbian.com/rock-5b-plus/Noble_vendor_gnome. This 100% works as I had tested, so either @armbuilder has a broken flash storage or had an error while writing to the storage medium. Gnome Desktop is working too
  16. I happen to have got a Android tv box with a s905Y5 processor. I got this by a tv subscription from a company airtel in India. I unsubscribed from the subscription and my tv box is completely useless. it asks money for watching youtube!!!. I am extremely frustrated from this approach by this company so please help me save this from getting into e-waste. From my research i found that it runs android 14 with a custom launcher which checks for the subscription and a locked down kernel/bootloader which checks for signatures before boot. I came to know these from the uart output. I also found that it is basically a customised version of this box https://www.videostrong.com/products-show/vt9201-s905y5-aiot-solution
  17. Thank you. I also can confirm this issue on Armbian 25.5.1 Bookworm, and that the suggest workaround works. For those interested, here is a more detailed explanation of what @Lars Christian Nygård said. Create a backup of original DTB. sudo cp /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts-orig.dts Decompile the DTB for the Orange Pi 3 LTS. sudo dtc -I dtb -O dts -o /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dtb Modify the decompiled DTS file according with your favorite editor, e.g. nano or vim. sudo nano /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts Navigate to the "spi@5011000" section and modify it. Set "status" to "okay" and add the "spidev@0" section. spi@5011000 { compatible = "allwinner,sun50i-h6-spi\0allwinner,sun8i-h3-spi"; reg = <0x5011000 0x1000>; interrupts = <0x00 0x0b 0x04>; clocks = <0x06 0x53 0x06 0x51>; clock-names = "ahb\0mod"; dmas = <0x2e 0x17 0x2e 0x17>; dma-names = "rx\0tx"; pinctrl-names = "default"; pinctrl-0 = <0x31 0x32>; resets = <0x06 0x20>; status = "okay"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0x78>; spidev@0 { compatible = "armbian,spi-dev"; reg = <0x00>; spi-max-frequency = <0xf4240>; }; }; Save and compile the modified DTS file. sudo dtc -I dts -O dtb /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dts -o /boot/dtb/allwinner/sun50i-h6-orangepi-3-lts.dtb Remove any previously configured overlay for SPI using "armbian-config" or editing the "/boot/armbianEnv.txt" file directly. No further modifications are needed to load our new recompiled DTB, since we directly modified the base DTB. Reboot when done.
  18. ls: unable to get access to '/boot/dtb/overlays': No such file or directory. Despite this, I attached full tree of "boot" directory. boot_dir_content.txt
  19. Difficult to see like this, better list the overlay directory: ls /boot/dtb/overlays
  20. I don't see such interfaces. Could you point me if one of these are suitable?
  21. sudo armbian-config Are you able to see the below overlays ? If yes, activate them. System → Hardware/Kernel → Activate UART0, UART1, BT overlays
  22. Just plugged a M.2 M key to E key adapter with an Intel AX200 iwlwifi (installed the firmware) booted up and Wifi 6 is going without using a USB port. My project is one step closer!!! Just have to get that last USB-C port working.
  23. Description fix build error with new compiler update uboot to v2024.04 ras314: fix sd-card regulator error How Has This Been Tested? [x] Build and Boot CLI/Gnome image on mba8mp [x] Build and Boot CLI/Gnome image on mba8mp-ras314 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article
  24. user@orangepizero2w:~$ systemctl status bt-gpio.service × bt-gpio.service - Enable GPIO for Bluetooth chip Loaded: loaded (/etc/systemd/system/bt-gpio.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Tue 2025-06-10 23:18:23 +03; 11h ago Process: 489 ExecStart=/bin/sh -c echo 225 > /sys/class/gpio/export || true; echo out > /sys/class/gpio/gpio225/direction; echo 1 > /sys/class/gpio/gpio225/value (code=exited, status=2) Main PID: 489 (code=exited, status=2) CPU: 5ms jun 10 23:18:23 orangepizero2w systemd[1]: Starting bt-gpio.service - Enable GPIO for Bluetooth chip... jun 10 23:18:23 orangepizero2w sh[489]: /bin/sh: 1: echo: echo: I/O error jun 10 23:18:23 orangepizero2w sh[489]: /bin/sh: 1: cannot create /sys/class/gpio/gpio225/direction: Directory nonexistent jun 10 23:18:23 orangepizero2w sh[489]: /bin/sh: 1: cannot create /sys/class/gpio/gpio225/value: Directory nonexistent jun 10 23:18:23 orangepizero2w systemd[1]: bt-gpio.service: Main process exited, code=exited, status=2/INVALIDARGUMENT jun 10 23:18:23 orangepizero2w systemd[1]: bt-gpio.service: Failed with result 'exit-code'. jun 10 23:18:23 orangepizero2w systemd[1]: Failed to start bt-gpio.service - Enable GPIO for Bluetooth chip. Also I attached boot log which is connected to that "systemctl status bt-gpio.service" command. bt_fail_boot_log_3.txt When the board was boot correctly (BT is working fine) the output looks the same: user@orangepizero2w:~$ systemctl status bt-gpio.service × bt-gpio.service - Enable GPIO for Bluetooth chip Loaded: loaded (/etc/systemd/system/bt-gpio.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2025-06-11 11:04:21 +03; 1min 30s ago Process: 492 ExecStart=/bin/sh -c echo 225 > /sys/class/gpio/export || true; echo out > /sys/class/gpio/gpio225/direction; echo 1 > /sys/class/gpio/gpio225/value (code=exited, status=2) Main PID: 492 (code=exited, status=2) CPU: 5ms jun 11 11:04:21 orangepizero2w systemd[1]: Starting bt-gpio.service - Enable GPIO for Bluetooth chip... jun 11 11:04:21 orangepizero2w sh[492]: /bin/sh: 1: echo: echo: I/O error jun 11 11:04:21 orangepizero2w sh[492]: /bin/sh: 1: cannot create /sys/class/gpio/gpio225/direction: Directory nonexistent jun 11 11:04:21 orangepizero2w sh[492]: /bin/sh: 1: cannot create /sys/class/gpio/gpio225/value: Directory nonexistent jun 11 11:04:21 orangepizero2w systemd[1]: bt-gpio.service: Main process exited, code=exited, status=2/INVALIDARGUMENT jun 11 11:04:21 orangepizero2w systemd[1]: bt-gpio.service: Failed with result 'exit-code'. jun 11 11:04:21 orangepizero2w systemd[1]: Failed to start bt-gpio.service - Enable GPIO for Bluetooth chip.
  1. Load more activity
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines