Am Montag, 9. Juni 2025, 15:57:24 CEST schrieb Felix Miata:
> DM composed on 2025-06-09 15:03 (UTC+0200):
> > Trixie with kernel 6.14:
> > 
> > System:
> >   Kernel: 6.14.10-zabbly+ arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
> >   
> >     clocksource: tsc avail: acpi_pm
> >     parameters: BOOT_IMAGE=/vmlinuz-6.14.10-zabbly+
> >     root=/dev/mapper/capys--vg-root ro quiet i915=!46d1 xe=46d1
> 
> Did you try the fresh Trixie without forcing Xe?

Yes, tried both i915 and xe driver on Trixie. And tried both xe and i915 on 
Bookworm with backports kernel..


> 
> Have you tried an IceWM (very lightweight) or any other non-Plasma session
> instead of of Plasma to confirm whether the internal is black there too? If
> not black yours would more likely be a Plasma problem, not X or Wayland.
> Arandr is an available GUI tool you could use instead of xrandr while
> running IceWM to try rotating the internal, or getting it to light up.

Yes, didn't use IceWM, but tried xfce without success. But since the problem 
(blank internal display) starts already right after loading initial Ram disk, 
I would assume that it is independent of the WM.


> > (I couldn't get Debian Trixie to start wayland session when setting
> > "nomodeset", only X11 session)
> > And in this situation: i.e. Fedora, Kernel 6.14, Wayland, I could rotate
> > the internal screen.
> > So when I have more time again, I will again install Fedora and probably
> > use that for now. Only 800x600 instead of the full 1280x800 display
> > resolution, but on 8°, that's good enough for now.
> 
> In fallback modes, such as when using nomodeset, modes are normally limited
> to standard VESA modes, all of which are 4:3 modes, with possible exception
> of 1920x1080 with some hardware, and none of which (IIRC) are portrait.
> 1280x800 is 16:10, not among traditional VESA's standard repertoire.
> 

Unfortunately, my day job keeps me away from the laptop (both in space and 
time) for the next couple of weeks. But I will try to experiment with 
specifying different VESA modes at boot. Am I correct in thinking that I would 
need something like "VGA=1024x768" or similar in my linux cmd line? 



> >> Nomodeset is a troubleshooting workaround that never supports two
> >> displays.
> 
> Somewhere in your thread I thought I saw mention use of nomodeset in
> conjunction with seeing both displays lit at once running Linux. I've never
> been able to make that happen with any distro or kernel on upwards of at
> least 50 computers.

I did have both screens available - but not as independent displays, only as 
mirror of each other.
It definitely worked in Fedora 42 in safe graphics mode, and also in some 
Debian varieties when using "nomodeset", but I am not sure any more, which 
ones (i.e. which kernel).



> 
> Now should be better than later to try submitting a Debian bug report about
> this. It ought to be fixable if you don't have faulty mini firmware.

I will experiment a bit more in a couple of weeks when I have more time. And 
if I still don't have a solution then, I'll do that. 
Not having done that before, I assume the best way would be to use the 
"reportbug" tool, right? I am not sure, which package I should specify, so 
that the report will be read by the relevant people. I would go with "linux-
image". But any hints about where I should report this to are very welcome.

Many thanks again for your help!

DM






Reply via email to