CraftWorld

5.19-media and 6.1-media all of it was curren at the moment of building. 16:10 gave me some head ache - needed to build kernels that allow to specifiy EDID and make specific EDID files. Actually tested only for 1280x800 screen, and only one of them is working totally fine without EDID fix. another one need EDID fix to display cli interface but works okay when it load to login page (but i do believe it's display issue).

well, wasn't that hard - all the work was done for me. I've just took your image for Station P1, dts for Orange Pi 800 from your github, dts for OrangePi 4 from armbian github, Then refilled all nodes in Pi 800s dts with info from Pi 4. only thing that was not building - type c settings, had to cut them off. After that done - got all i need working on OPi 4. (HDMI USB WiFi Bt Ethernet) and no resolution issues with 16:10. Thanks for that.

@Roman Khudobei I can suggest you try to add more supported resolutions throught 40-monitor.conf file. Then you can try to switch between them somehow. (not that good at linux scripts myself, but i do belive it's possible to read-edid of non-working monitor and then select corresponding modeline from 40-monitor.conf

Hello, so if my solution did help you it means that EDID should be ok, because that how it was in my case, problem is somewhere in hdmi driver. IDK what kernel is used for ROCK 5B, but if it's possible - try balbes150 media kernel - with it i don't need my fix on some of the screens

Huge thanks for fast answer and for all of mentioned images

@balbes150 does it mean you've deleted orangepi-800.dtb from your build? Also wanna ask if it is possible to get Opi4 with your media kernel? cause it doesn't have resolution issues i've been encountering on mainline armbian. Can it be achieved only by providing right dtb? Asking cause i was trying to run Armbian_22.11.0-trunk_Orangepi-800_jammy_current_5.19.17.img on Orange Pi 4, everything that i need was working. Bluetooth wasn't. Then apt upgrade erased orangepi-800.dtb, and i had to manually put it back.

so, in case someone needs this too: General guide to succesfuly use not so popular screen resolutions. 0) Make sure your monitor works with another PCs, and, maybe, with other distros 1) Get your monitor EDID any convinient way - through console ( cat /sys/class/drm/cardX-HDMI-A-Y/edid X and Y are numbers depending on your setup) or another PC and check if it is OK. 2) Check what clock frequency is used in your EDID, (e.g. min was 71.33 MHz) and pick the closet in from given list: 27, 36, 40, 54, 65, 66, 74.25, 83.5, 108, 106.5 146.25, 148.5.( so i picked 74,25) and use modeline calculator using resolution and clock frequency as only inputs. 3a) EASY WAY but screen gets normal only when DM starts: put your modeline to /etc/X11/xorg.conf.d/40-monitor.conf like this: Section "Monitor" Identifier "HDMI-X" Modeline "YOUR_MODE_NAME" 74.25 1280 1290 1300 1500 800 805 810 823 +hsync -vsync //here should be modeline you get from calculator Option "PreferredMode" "YOUR_MODE_NAME" EndSection 3b) LONG WAY but you'll be able to see boot messages and use cli interface on 1st login(if you do this before 1st launch of the image) build your image with CONFIG_DRM_LOAD_EDID_FIRMWARE=y (in config menu search for EDID and it wiil whos where it is) something like device drivers -> graphics support->Direct Render...->enable loading edid insteadof probingfor it compile custom EDID using modeline from step 2. edit /boot/armbianEnv.txt: append extraargs=drm.edid_firmware=edid/YOUR_EDID.bin place YOUR_EDID.bin to /lib/firmware/edid/ you're good to go

actuallly found kinda better solution - so 1280x800 is not very common mode as all other 16:10. So it has not very big list of possible settings built-in to the driver. Due to that only exact frequencyes from kernel/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c in array called dw_hdmi_mpll_config rockchip_mpll_cfg[] are accepted as okey when producing modeline. And despite edid from monitor is correct it doesn't match any frequency in that array and therefore modeline from edid gets thrown away as bad. So i just picked the closest to the edid frequency from that array and putted modeline with it to /etc/X11/xorg.conf.d/40-monitor.conf. This way screen turns on and image is normal, but all startup messages do not display. Gonna try building image with CONFIG_DRM_LOAD_EDID_FIRMWARE=y and providing custom edid.bin to see if this makes any difference

gathered some info that can be usefull: outputs of armbianmonitor -U, parsed monitor's EDID and xrandr --verbose for both used kernels armbianMonitor-4.4.213.txt edidDecode-4.4.213.txt xrandrVerbose-4.4.213.txt armbianMonitor-5.15.76.txt edidDecode-5.15.76.txt xrandrVerbose-5.15.76.txt

Have an OPi 4B with installed Armbian (Armbian_21.05.1_Orangepi4_buster_legacy_4.4.213_xfce_desktop.img from here) which is working perfectly. HUGE thanks for that. So i wanted to try images with mainline kernel and found that none of XFCE desktop images from the archive can correctly output HDMI signal for my screen, maximum i could achive was compressed and flickering image using method from docs (editing /etc/X11/xorg.conf.d/40-monitor.conf). by default there are no modes in /sys/class/drm/card0-HDMI-A-1/modes in mainline images and in legacy one there are two: 1280x800p60 and 1280x800p57. EDID is there in both images. And if i set resolution via /etc/X11/xorg.conf.d/40-monitor.conf in mainline i can't change it to anything via xrandr because "Configure crtc 0 failed". on the latest mainline image (Armbian_22.08.10_Orangepi4_jammy_current_5.15.76_xfce_desktop.img) i was able to get normal resolution doing the following : 1. edit /etc/X11/xorg.conf.d/40-monitor.conf from console like below: Section "Monitor" Identifier "HDMI-1" Modeline "1280x800_try4" 75 1280 1290 1300 1500 800 805 810 823 +hsync -vsync Option "PreferredMode" "1280x800_try4" EndSection this gets me a compressed screen after reboot. 2. then in terminal: xrandr --newmode "1280x800_60.00" 83.46 1280 1344 1480 1680 800 801 804 828 -hsync +vsync xrandr --addmode DP-1 1280x800_60.00 xrandr --output DP-1 --mode 1280x800_60.00 xrandr --output DP-1 --crtc 1 after that image on HDMI suddenly becomes normal but still no resolution changes can be applied to HDMI Any chances for easy workaround here?

Hello! Trying to build legacy buster desktop image for orangePi4 ends with error Processing triggers for libc-bin (2.28-10+deb10u1) ... Processing triggers for systemd (241-7~deb10u8) ... Processing triggers for dbus (1.12.20-0+deb10u1) ... [ o.k. ] Checking MD5 sum of installed packages [ debsums ] [ error ] ERROR in function create_rootfs_cache [ main.sh:588 -> main.sh:549 -> debootstrap.sh:59 -> debootstrap.sh:343 -> general.sh:0 ] [ error ] MD5 sums check of installed packages failed [ o.k. ] Process terminated [ error ] unmount_on_exit() called! [ main.sh:1 -> image-helpers.sh:0 ] [ o.k. ] Unmounting [ /home/lord/build/.tmp/rootfs-b9124b12-3d75-454e-a579-cf4a2a7ea928/ ] [ error ] ERROR in function unmount_on_exit [ main.sh:1 -> image-helpers.sh:94 -> general.sh:0 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated root@lord-VirtualBox:/home/lord/build# build system Ubuntu 22.04 on virtual box. Any suggestions how to overcome this?