http://bugzilla.opensuse.org/show_bug.cgi?id=971885 http://bugzilla.opensuse.org/show_bug.cgi?id=971885#c18 --- Comment #18 from Felix Miata <mrmazda@earthlink.net> --- Created attachment 670256 --> http://bugzilla.opensuse.org/attachment.cgi?id=670256&action=edit start script amended as comment 16 directs, its output, and lspci -nn output, all from TW20160321 KDE3 host gx780 (In reply to Egbert Eich from comment #16)
- Could you do a: xrandr --dpi 108 --output VGA1 --mode 1680x1050 &>> /tmp/startx.log xrandr -q >> /tmp/startx.log
in your setup script? (leave out the first 'xrandr -q' which may 'fix' things magically). I'd be curious if the output of the first command produces any error messages if it fails to set the mode.
xrandr: cannot find mode 1680x1050 Very unsurprising to me given upstream comment "A recent change to xrandr was not to do a forced query before setting the mode". This non-programmer can only guess it could not be found because when using Intel, where unlike with Nouveau and Radeon, the KMS framebuffer mode resulting from cmdline video= directive is inherited by Xorg, probably by KMS hiding higher res modes at handoff to Intel X driver (possibly affected due to absence of Plymouth involvement?). The other workaround that I'm aware of is not using xrandr in startup script at all, instead using /etc/X11/xorg.con* (on gx780, the following): Section "Device" Identifier "DefaultDevice" Option "monitor-DP1" "DefaultMonitor" EndSection Section "Monitor" Identifier "DefaultMonitor" Option "PreferredMode" "1680x1050" DisplaySize 394 247 # 108 DPI @ 1680x1050 EndSection Section "Screen" Identifier "DefaultScreen" Device "DefaultDevice" Monitor "DefaultMonitor" EndSection Because with FOSS drivers there is no explicit DPI option, it's more work to configure xorg.con* than xrandr in startup script (if it works at all), but it does result in initialization of both IceWM and KDE3 to 1680x1050@108DPI.
- Please get me the output of an 'lspci -nn' of the troubled system. I will see what I can do to get as close to the hardware you are using as possible.
Attachment tail. Still more Egbert Eich comments I have not yet addressed, but do any remain that I still need to? -- You are receiving this mail because: You are on the CC list for the bug.