00:19 <vagrantc> having trouble booting odroid-c2 with u-boot 2022.07 (from Debian) ... 2022.04 seemed to work ok, using the same arm-trusted-firmware

00:22 <vagrantc> a failed boot log https://paste.debian.net/1250943/

00:22 <vagrantc> it triggers a "Synchronous Abort" handler, esr 0x96000004 and then resets

00:27 <vagrantc> doesn't look like the kernel, initrd or dtb are clobbering each other ...

02:51 <lvrp16> vagrantc: Johan reported a problem with u-boot 2022.07 on GXL. I have been booting efi so I have not had the issue and haven't had time to reproduce. He was using a boot.scr.

02:52 <vagrantc> heh. and i was using extlinux.conf

02:52 <vagrantc> .... i could maybe try getting EFI on a partition somehow...

02:53 <vagrantc> i *might* also have a boot script ... could try that too, just in case for some bizarre reason that would work

02:53 <vagrantc> thanks

02:53 <lvrp16> vagrantc: he bisected it to this commit: a9bf024b2933bba0e23038892970a18b72dfaeb4

02:53 <lvrp16> yw

02:54 <vagrantc> oh, bisecting boot failures is an adventure

02:54 <lvrp16> a few of us do it enough we have scripts for the process XD

02:55 <lvrp16> i'm running 3 separate soc vendors and have automated tooling for each as well

02:55 <vagrantc> i even have some sd-muxing hardware, i just haven't taking the time to hook it all up :)

02:55 <vagrantc> which, probably means i'm spending more time not hooking that stuff up :)

02:56 <lvrp16> yeah by this time next year, hopefully I have sd muxing and CI for the bootloaders

02:56 <vagrantc> wonder if disabling EFI support in the u-boot build might work around the issue too ...

02:56 <lvrp16> worth a shot

02:56 <vagrantc> the process for building these "signed" images is a bit annoying, which is why i've probably put this off for so long

02:58 <lvrp16> amlogic ftw, I really want to use upstream ATF but I lose LZ4 support

02:58 <lvrp16> and I need the BL to stay under 1M

02:58 <lvrp16> smh...

02:59 <vagrantc> ah, i'm definitely using "upstream" atf ... well, debian's package

03:00 <vagrantc> only carrying one patch, and that's for the tools

03:00 <vagrantc> don't think i've done anything too crazy with the packaging

19:24 <mop_> hi. I have a 1920x1200 screen and unfortunately the screenspace is slightly off (can't read last 2 lines and I have a black space in the top) for the linux framebuffer and I have the same problems when starting a wayland compositor. I have read that other people had similar problems. Is there anything I can do? use a newer kernel, incorporate some patches, maybe a simple config issue? I have tested it with a

19:24 <mop_> vim3 pro and a odroid c4

19:24 <mop_> the display is working fine with my amd laptop :|

19:25 <mop_> using armbian on both devices

19:43 <steev> mop_: is it maybe doing 1920x1080 and not 1920x1200?

19:47 <mop_> steev, the OSD shows 1920x1200. when I force 1080p using kernel boot options it shows 1080p and it looks differently. linux console is ok and the display is correctly positioned but unfortunately I get green areas when starting a wayland session. probably a different problem (which I btw don't have at 1200p).

19:47 <steev> just making sure :)