Endian

Hmm.. Maybe I said spoke too soon.. What I see is that if I build an image from the Armbian tree like this ./compile.sh BOARD=rock-5b BRANCH=legacy RELEASE=jammy COMPRESS_OUTPUTIMAGE=img KERNEL_CONFIGURE=no BUILD_MINIMAL=no BUILD_DESKTOP=no and boot from it my older (and problematic) screen works ok on HDMI-2 but not on HDMI-1 at the initial boot. However, if I do an apt update / apt upgrade and reboot my problematic screen stops working again... This seems not-so-good... Any insights on why this can happen?

I see that there is a lot of work ongoing on improving the UEFI boot support for Rock 5B and this is quite exciting. In my view this seem to be the ideal route for future SBC boards. However, I am yet to try it so I am still a novice in the area. How do you guys look at the future of UEFI vs U-boot for Linux on SBC’c in general and on the Rock 5B in particular? Will the UEFI version be as capable as a u-boot version or do you see limitations?

I was testing Armbian support for the Rock 5B board a few weeks ago, and although it is still early it looks very promising. So i thought i should test how it works for my Vim4 board too.. To my surprise it does not seem to supported by armbian. Could you help explain a bit What causes this? Is it some lack of support from Amlogic and / or Khadas or What is missing for the Khadas Vim4 boards to be supported by Armbian? (Maybe link to somewhere where a discussion on the subject is ongoing?)

It seems like current builds with both 6.2 and 5.10.110 kernels are working with both my screens, but the old screen only works if connected to the HDMI-2 port. Strangely when I build it myself using this command it works, but if I fetch this build https://github.com/armbian/build/releases/download/23.02.0-trunk.0254/Armbian_23.02.0-trunk.0254_Rock-5b_jammy_legacy_5.10.110_minimal.img.xz#rock-5b only the newer screen works. Even if i set BUILD_MINIMAL=yes my build lights up both my screens nicely. How can this be? Shouldn't my build be quite similar to the trunk builds? Edit: I checked the gitlog and there is a trunk.254 label in the history. The diff against it is quite large. It seems like they may have exchanged a radxa kernel for some locally built kernel instead?

It seems like the problem is fixed on master now. If I build a new image from the armbian build tool with a 5.10.110 kernel both my screens work ok. The nightly builds at armbian/build/releases (currently trunk.256) is not fine though.

Thanks, this worked.

How do I build from the Armbian tree with the exact same config as these builds https://github.com/armbian/os/releases/download/23.05.0.0134/Armbian_23.05.0.0134_Rock-5b_lunar_midstream_6.2.0-rc1_minimal.img.xz (but on latest version on the selected branch)? I do not want to go back in time, just use the same config.

I am a Linux developer but havent been debugging Armbian before, so newbie warning. I'd like to try to help debug this, but haven't found a good place to start digging yet. Also, when I try to build a similar 6.2rc2 based image from the Armbian tree it does not light up any of my screens when booting from SD card...

But my point is that this bleeding edge version works better than the main build based on the 5.10.110 kernel. With this kernel the hdmi/DVI screen works when connected to the HDMI-2 port. With any 5.10.110 based build it does not work on either of the ports. On older 5.10.66 and 5.10.72 based builds it worked on both ports. There are a couple of forum threads about this, but no solution.

I am one of those who have problems with one of my screens staying black on the 5.10.110 kernel. On the 6.2.rc2 kernel it lights up but only when connected to the HDMI-2 port. Is there anything I should test to help find out what is causing this problem?

The linked image above which I tried before (and it seemed nice) now seem to be gone. Where did it go? I now tried the latest build from here https://github.com/armbian/os/releases/download/23.05.0.0134/Armbian_23.05.0.0134_Rock-5b_lunar_midstream_6.2.0-rc1_minimal.img.xz and it seems similarly good. These are the first builds since 5.10.72 that works with my seconds screen (although it only works if it's connected in HDMI-2).

@Roman KhudobeiI have tried the media kernel from balbes150 and it works fine with my newer Dell screen, but the older BENQ screen is always black with that kernel too. The BENQ screen works ok with the 5.10.66 and 5.10.72 kernel builds.

Here are my other threads for this issue https://forum.radxa.com/t/after-apt-upgrade-the-screen-gui-doesnt-start/15030/

I have tried a balbes150 build, which uses the 5.10.110 kernel and has the same problem, although I am not sure if the "media kernel" is something special?

In that thread I have mentioned that the screen is detected and EDID negotiated ok so when selected as second screen Armbian thinks its present, but the screen itself is always black, so something wrong with the video signal sent to it.

I have a similar issue where one of my screens never lights up when armbian boots. What i found is that the problem is not present on older builds using the 5.10.72 and 5.10.66 kernel versions. my screen is 1920x1080@60 and EDID negotiation seem ok

Also reported in this thread https://forum.radxa.com/t/after-apt-upgrade-the-screen-gui-doesnt-start/15030

I should add that the screen can handle 1920x1080@60Hz

I can try it but I can mention that I have done some more debugging and I have noticed that kernels 5.10.66 and 5.10.72 works fine with my old screen, but 5.10.110 does not light up the screen at all. It applies to both Debian Buster and Ubuntu Jammy

I have tried the Debian image for ROCK5B and the Gnome GUI works fine there. But when booting the Armbian image (running from emmc) the screen does not notice any signal from the ROCK5B regardless of which HDMI port I try. I am using a quite old HDMI monitor (connected though a DVI-HDMI adapter). How do I debug this?