DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-amlogic
<DC-IRC>
<narmstrong> Wut there’s no way simpledrm « conflicts » with panfrost, or there’s weird changes on the armbian shipped DT
chewitt has joined #armbian-amlogic
<DC-IRC>
<Tonymac32> I don't think we're touching that DT, in general the patches to Amlogic are really light.
<DC-IRC>
<lanefu> what kind of DT weirdness would it take to make it conflict?
<DC-IRC>
<c0rnelius77> I thought that driver was kind of UEFI related anyway. Allows for you to also preset ur res and whatnots. Personally I've never used it. I don't even have it enabled in my configs.
<DC-IRC>
<c0rnelius77> well there you go. @narmstrong added context.
<DC-IRC>
<nicod_sbc> I've got it too when using X11 desktop and my 4K philips monitor.
<DC-IRC>
<nicod_sbc> The poster seems to suspect u-boot. I have no clue...
<DC-IRC>
<narmstrong> This is what I was expecting, GPU gets card2 and X11 gets confused because it’s 40y old tech designed for x86…
<DC-IRC>
<narmstrong> It’s a very well known issue wayland solves
<DC-IRC>
<nicod_sbc> Thanks for the info.
<DC-IRC>
<nicod_sbc> I do find it weird that with my 13" 1080p display it doesn't create that 2nd card but it does on some high-res monitors. Indeed x11 needs to be retired. I hope the remaining x11 desktops can switch smoothly. It's not easy to make someone use something else than what they've been used for many years.
<DC-IRC>
<rpardini> nice info, thanks. I wonder what is it about those 4k monitors that triggers it, since EFI shouldn't be at play here.
<DC-IRC>
<nicod_sbc> I ask myself the same. Computers can do weird things.
<DC-IRC>
<nicod_sbc> Seems also present in wayland. `I also installed sway / Wayland, while having the QHD monitor attached. Same issue there. `
<DC-IRC>
<nicod_sbc> ` The monitor appears frozen, but when pressing CTRL-ALT-F2, another tty appears and I can kill sway and the first tty becomes responsive again.
<DC-IRC>
<nicod_sbc> Executing the `modprobe -r simpledrm` module fixes the issue and sway can be started normally. `
<DC-IRC>
<nicod_sbc> I'll try my N2+ and see if it also does it.
<DC-IRC>
<rpardini> I don't think that changes anything. Armbian still uses lightdm, which is x11.
<DC-IRC>
<nicod_sbc> That might be it indeed. I can test with installing gdm3.
<DC-IRC>
<nicod_sbc> No more Odroid N2+ support? I didn't know that.
<DC-IRC>
<c0rnelius77> Is there an actual use case for this driver in meson builds? if not why not just remove it.
<DC-IRC>
<rpardini> we've the gdm3 for gnome desktop by default but only in very recent builds.
<DC-IRC>
<rpardini> that's why I approved the 1st blacklist.
<DC-IRC>
<rpardini> (that revealed a bug in my initrd caching code, `/etc/modprobe.d` is not being taken into account and thus makes no effect if you've built without it before)
<DC-IRC>
<c0rnelius77> Sounds like it would be easier just to remove it from the defconfig then and close the blacklist PR.
<DC-IRC>
<c0rnelius77> No legit use case, no point to have it enabled.
<DC-IRC>
<nicod_sbc> I now have the same issue on the small 13" 1080p display. How. I first tested the 13" display with this image and it worked. Then I booted with my 4K attached. And this problem. Then I thought, what would happen if I just switch my HDMI to my 13" display. And nothing.
<DC-IRC>
<nicod_sbc> So I pressed the reset button and now I have the same on my 13". It shows the armbian logo and then goes blank.