All Activity

Post not related to 0.4! Since yesterday I've been doing a few tests on your kernel patch against mainline kernel 6.16-rc5. here what I found out. I am testing against Johsua's ubuntu because this is my goal ( newer kernel on that image ) 1) Kernel compile and works , but I get a few warnings on the dtbs compilation DTC arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dtb arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dts:235.3-13: Warning (reg_format): /mmc@fe2d0000/wifi@1:reg: property has invalid length (4 bytes) (#address-cells == 2, #size-cells == 1) arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dtb: Warning (pci_device_reg): Failed prerequisite 'reg_format' arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dtb: Warning (pci_device_bus_num): Failed prerequisite 'reg_format' arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dtb: Warning (i2c_bus_reg): Failed prerequisite 'reg_format' arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dtb: Warning (spi_bus_reg): Failed prerequisite 'reg_format' arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dts:233.17-241.4: Warning (avoid_default_addr_size): /mmc@fe2d0000/wifi@1: Relying on default #address-cells value arch/arm64/boot/dts/rockchip/rk3588s-orangepi-5-pro.dts:233.17-241.4: Warning (avoid_default_addr_size): /mmc@fe2d0000/wifi@1: Relying on default #size-cells value 2) Your patch works and makes the system bootable from the SDCARD. U-boot reads the /boot from the sdcard, since it can not find the EMMC, but after booting I can have to / on the EMMC and that works. 3) Curiously after the uboot handoff to the linux kernel, emmc is available but the sdcard fails to initialize emmc initialize just fine with the / [ 10.225763] mmc2: new HS400 Enhanced strobe MMC card at address 0001 [ 10.228424] mmcblk2: mmc2:0001 A3A564 233 GiB [ 10.233239] mmcblk2: p1 p2 [ 10.234373] mmcblk2boot0: mmc2:0001 A3A564 4.00 MiB [ 10.237884] mmcblk2boot1: mmc2:0001 A3A564 4.00 MiB So I basically have a working system but it requires the sdcard to boot and I can not mount the sdcard after boot root@pi5pro1:~# uname -r 6.16.0-rc5 root@pi5pro1:~# cat /etc/os-release PRETTY_NAME="Ubuntu 24.04.1 LTS" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04.1 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=noble LOGO=ubuntu-logo

Hi, I'm facing the same issue with my BananaPI-M1 running ARMbian and I have another one bPI-M1 running ArchARM which is suffering exactly for the same issue (bPI is not supposed to be supported but it working pretty well but this HDMI issue and the miss of AXP209 exposition). I'm a bit lost about the current status : is the upstream 6.15 (or upcoming 6.16) already patched/corrected ? @eselarm The link seems dead 🙂

@C127 0.4 output. Still no boot DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 ch0 ttot7 LPDDR5, 2400MHz channel[0] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch1 ttot7 channel[1] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch2 ttot7 channel[2] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch3 ttot7 channel[3] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB Manufacturer ID:0xff DQS rds:h1,l0 CH0 RX Vref:24.6%, TX Vref:21.0%,21.0% DQ rds:h4 h2 h1 h2 h1 h5 l0 h7, h1 h1 h3 h3 h1 h1 h7 l0 DQS rds:l0,h2 CH1 RX Vref:27.9%, TX Vref:21.0%,21.0% DQ rds:h4 l0 h2 h3 h7 l0 h7 l0, h6 h5 h4 h5 l1 h1 h6 h6 DQS rds:l0,h2 CH2 RX Vref:25.0%, TX Vref:21.0%,21.0% DQ rds:h1 l0 h2 l3 h1 h2 h5 h1, l1 h7 l1 h4 l2 h1 h1 h3 DQS rds:l0,h1 CH3 RX Vref:27.5%, TX Vref:21.0%,21.0% DQ rds:h3 h1 h2 h1 h4 h1 h1 h1, h5 h6 h2 h2 h4 h4 l0 h5 stride=0x2, ddr_config=0x6 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0x0 0x2400 0x44800 0x89000, rank_mask0 0x2000 change to F1: 534MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F2: 1320MHz ch0 ttot8 ch1 ttot8 ch2 ttot8 ch3 ttot8 change to F3: 1968MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F0: 2400MHz ch0 ttot7 ch1 ttot7 ch2 ttot7 ch3 ttot7 out U-Boot SPL 2024.04-armbian-2024.04-S2504-P83ae-H29de-Vbf83-Bb703-R448a (Jul 03 2025 - 17:49:57 +0000) Trying to boot from MMC1 Card did not respond to voltage select! : -110 spl: mmc init failed with error: -95 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ###

I will flash the new image now and let you know what happens,

I will gladly help you to test it. Just to let you know, on 0.3 apparently If i boot from the sdcard, after booting the emmc is available. So the kernel knows about it. just uboot does not ?

Thanks, I'll pursue with the thread you mentioned.

If you guys want Bionic, I can remove stretch, and link it. You should try to download stretch again, and try a different SD card before anything else.

Ricardo Martin Mantelli seria bueno saber que equipo estas usando, porque en mi caso con una MXQ 4K con Amlogic S805 me anduvo sin problemas.

Hello @salas Thanks a lot for testing and for the eMMC boot log! That's super helpful. I'm ready to tackle the eMMC boot issue. As you saw, it's failing very early in the U-Boot SPL, so it's definitely a hardware initialization problem. I'm creating a new fork to add a patch for this (Patch >=v0.4). Since I can't test it myself (I don't own an eMMC module), I would need your help to flash and test the new images. With a bit of luck and your feedback, we should be able to get it working.

@re.ADW You can generate and share the "SHA256" hash of the image that was used on your board, please...

Hello, One of my BananaPI is used to display a graphical dashboard. But after a system upgrade (apt update / apt upgrade), the HDMI output seems disabled after reboot : - the boot process is displayed, but it seems it's disabled as soon as the DRM driver is loaded. Any tips, help ? Thanks # uname -a Linux TdB 6.12.30-current-sunxi #1 SMP Thu May 22 12:29:54 UTC 2025 armv7l GNU/Linux # cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=bananapi BOARD_NAME="Banana Pi" BOARDFAMILY=sun7i BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=1a8daf0 VERSION=23.02.2 LINUXFAMILY=sunxi ARCH=arm IMAGE_TYPE=nightly BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=Image BRANCH=current

i do not use armbian-config normally, but there is a 6.12.35 here http://beta.armbian.com/pool/main/l/linux-6.12.35/ (fix or edit or follow path/mirror youself)

@eselarm ok thats interesting. Is it not even listed if looking for alternative kernels via armbian-config? Scrolling through the collection of community creation builds does not appear to list anything for the M1 only for the Pro Model.

Just noticed I was not up to date, I did a armbian-upgrade and still no change. Here is an updated paste : https://paste.armbian.de/loderavavi

@Ryzer just started it, was updated a week ago or so: root@banlipi:~# uname -a Linux banlipi 6.12.30-current-sunxi #1 SMP Thu May 22 12:29:54 UTC 2025 armv7l GNU/Linux root@banlipi:~# dmesg | grep drm [ 0.996620] sun4i-drm display-engine: bound 1e00000.display-frontend (ops 0xc0bb0c8c) [ 0.996924] sun4i-drm display-engine: bound 1e20000.display-frontend (ops 0xc0bb0c8c) [ 0.997494] sun4i-drm display-engine: bound 1e60000.display-backend (ops 0xc0bb03f8) [ 0.997999] sun4i-drm display-engine: bound 1e40000.display-backend (ops 0xc0bb03f8) [ 0.998903] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 0.998973] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc0bae8e8) [ 0.999936] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 1.000015] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 0xc0bae8e8) [ 1.002143] sun4i-drm display-engine: bound 1c16000.hdmi (ops 0xc0bb1688) [ 1.004289] [drm] Initialized sun4i-drm 1.0.0 for display-engine on minor 0 [ 1.004495] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 1.032416] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 6.475086] [drm] Initialized lima 1.1.0 for 1c40000.gpu on minor 1 [ 11.323101] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm... [ 12.107664] systemd[1]: modprobe@drm.service: Deactivated successfully. [ 12.124764] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. no newer kernel available via apt now I see when running update.

Hello. I have no Xorg installed, so no xorg config. I'm checking the correct resolution on the command line. xrandr is not available either, I'd rather not install it if possible. Here is the log paste : https://paste.armbian.de/nitibagujo Thanks for having a look!

Hi, can you provide logs with: PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u Also, take a look at this thread how to force a mode using boot parameters and Xorg config. https://forum.armbian.com/topic/46932-5-inch-hdmi-display-not-working/#comment-206059 I suggest you connect your monitor to a linux system which supports it and gather the modelines there with: xrandr --verbose Then you can try to force that missing mode. Cheers

Some more info : dmesg has this error message : rockchip-drm display-subsystem: [drm] User-defined mode not supported: "1920x1080": 60 173106 1920 2048 2248 2576 1080 1083 1088 1120 0x20 0x6 Sure enough, when I do a cat /sys/class/drm/card0-HDMI-A-1/modes I get 1024x768 800x600 800x600 No 1920x1080 mode is listed. Any ideas?

@eselarm what kernel version are you currently using? As a quick check could you please provide the output of sudo dmesg | grep drm, on the off chance I may have missed something or broke again during kernel bump?

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Hi @Alex83, Ok that aligns more with prior welcome screen in your prior post and the Banana Pi M1 is an A20. I dont know how long it takes for changes to flow through to automated builds after submitting a PR but I should hope they would now be present in the latest release kernel 6.12.35. Out of interest where did you source the image from as armbian pages only list images with 6.6 kernel unless you are using the image from the Banana Pi pro? While HDMI output can be convient it is not always ideal for debug purposes. For instance it is not possible to scroll back through logs using just hdmi alone.

BananaPi M1 is A20 SoC. I have 1 but not using HDMI. I just have a permanent USB serial console cable connected to it, much easier than HDMI+keyboard.

It's been a while since I used Armbian. I have tons of ARM SBCs from a few years back because I think they're fascinating but they either wind up being too slow or just not worth using it for whatever since x86 "SBC like" boards exist and are pretty cheap. Fast forward to now and I'm doing some touchscreen development and just because of how I have things setup I needed 3 things, I2C, Interrupt capable GPIO and an actual DisplayPort. That combination of things is surprisingly hard to find. I had a couple of things on hand, (Seeed Odyssey x86, Odroid H2/H3, Rpi's, Nvidia Jetson Nano). I spent way more time than I should have trying to make each of these work, in the end only the Rpi4 worked because the GPIO is good, problem is the HDMI ports are native. That's kind of a thing with ARM SBC's that's opposite from x86 and desktop GPU's...the native display interface is usually DisplayPort of some form on x86. So with the Pi4 I had to use one of the few HDMI->DP adapters I could find (the other way is common, this way is rare) and it worked but it's kind of jank. The other SBCs had various issues with GPIO even though they had displayports. So I picked up the Orange Pi 5 Plus because it has a typeC/DP which is fine. I think I tried the latest image of Armbian first, and it doesn't boot, there was a post here over a month ago about it so I wound up dropping Armbian cuz that's not a good start. Manjaro Rpi images work well, they have a dev image for the orange Pi but their device tree is missing the typeC displayport connections. Then I tried Orange Pi OS / Arch which looks ugly but the DP works....though the colors are swapped, like the red/green channels are mixed up. I couldn't get I2C2 working either. I saw a post on here about it mentioning the kernel version etc. but I couldn't get it by device wouldn't show up on a scan. So I came back to Armbian, slightly older image with the vendor kernel. Has pretty much the same issues. After some messing around I found that the I2C4_M3 mux overlay works to put the I2C4 bus into play, this one worked for me. So I was able to compile my driver module against the orange Pi source and get it working but I still have this issue with the DP colors being swapped and slightly shifted. Something is off about the DP configuration. Right now I have enough to do what I need to do but I will have to resolve that. I'm leaning towards the issue being in the DT. If anyone has any ideas about this it'd be much appreciated. Just figured I'd tell that little story in case some of the Armbian devs are looking for feedback. Think I'll stick with Armbian since it works better than anything else, though I much prefer Arch based distros. As for the Orange Pi itself, this thing is great. It's an actual development board, with enough interfaces to actually develop something, so I think I'll actually use this one.

@SteeMan It is not easy to take an UART-Cable every time when I wanna check what's wrong with the device... - So am I the only unhappy person with the HDMI-bug?