Comment # 12
on bug 971885
from Egbert Eich
(In reply to Felix Miata from comment #11)
> (In reply to Egbert Eich from comment #10)
> > Ok, what happens if you do a
> > xrandr --dpi 108 --output VGA1 --mode 1680x1050
> > right after doing the 'xrandr -q' on the same machine? Does the mode change
> > to 1680x1050 - or do you get an error message?
>
> Different machine, almost the same though, same CPU, Optiplex 780 instead of
> Optiplex 760. Main difference is DDR3 instead of DDR2, besides different HD,
> and much better availability for testing. The 760 is my TV's PC, normally
> used with HDTV, so needs to be off the 1680x1050 workspace rotation. This is
> the 4th official failure since opening this bug, on host gx780, also Intel
> gfx. It's fresh TW 20160321 KDE3 zypper up (sans 4.5.0 kernel). Same
> 1680x1050 LCD, but connected via DisplayPort. So in
> /etc/X11/xinit/xinitrc.d/setup, is
>
> xrandr --dpi 108 --output DP1 --mode 1680x1050 # Intel digital
>
> Producing same 1440x900@96DPI = failure.
OK.
> /proc/cmdline tail: ...splash=0 vga=791 video=1440x900@60 3
>
> # xdpyinfo | egrep 'dimen|ution'
> dimensions: 1440x900 pixels (381x238 millimeters)
> resolution: 96x96 dots per inch
> # xrandr -q
> Screen 0: minimum 8 x 8, current 1440 x 900, maximum 32767 x 32767
> DP1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 474mm
> x 296mm
> 1680x1050 59.97 + 74.89
> 1600x1000 60.01
> 1280x1024 75.02 72.05 60.02
> 1440x900 74.98 59.89* 59.98
> 1152x864 75.00
> 1280x720 60.00 50.00 59.94
> 1024x768 75.08 70.07 60.00
> 800x600 72.19 75.00 60.32
> 720x576 50.00
> 720x480 60.00 59.94
> 640x480 75.00 72.81 66.67 60.00 59.94
> 720x400 70.08
> DVI1 disconnected (normal left inverted right x axis y axis)
> HDMI1 disconnected (normal left inverted right x axis y axis)
> VGA1 disconnected (normal left inverted right x axis y axis)
> VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Ok, so ...
> # xrandr --dpi 108 --output DP1 --mode 1680x1050
> # xdpyinfo | egrep 'dimen|ution'
> dimensions: 1680x1050 pixels (395x246 millimeters)
> resolution: 108x108 dots per inch
> So, yes it changes, as I would expect from a timing problem solved by
> running a dummy xrandr prior to a real one in the startup script.
... mode and dpi change work in principle, which indicates that this is not a
problem of KMS, then Xserver or the driver.
>
> > Please also do what I've asked for in comment #3 on this machine. (The
> > proposal in comment #3 was not meant as a workaround but as a debugging aid).
>
> I did that on two machines several hours before comment 7, and couldn't see
> the point since there was no evidence of any bug. I prefaced the comment 3
Exactly. This was what I wanted to find out!
> commands with date commands for my own benefit, and used my own filename
> xstart.txt, but otherwise I think it's what you asked for (on host gx780):
Yes, when I did this test, I've added the 'date' command as well. Granularity
of the time stamp is not really high but sufficient.
> Wed Mar 23 03:30:10 EDT 2016
> Screen 0: minimum 8 x 8, current 1440 x 900, maximum 32767 x 32767
> DP1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 474mm
> x 296mm
> 1680x1050 59.97 + 74.89
> 1600x1000 60.01
> 1280x1024 75.02 72.05 60.02
> 1440x900 74.98 59.89* 59.98
> 1152x864 75.00
> 1280x720 60.00 50.00 59.94
> 1024x768 75.08 70.07 60.00
> 800x600 72.19 75.00 60.32
> 720x576 50.00
> 720x480 60.00 59.94
> 640x480 75.00 72.81 66.67 60.00 59.94
> 720x400 70.08
> DVI1 disconnected (normal left inverted right x axis y axis)
> HDMI1 disconnected (normal left inverted right x axis y axis)
> VGA1 disconnected (normal left inverted right x axis y axis)
> VIRTUAL1 disconnected (normal left inverted right x axis y axis)
I assume you did the 'xrandr --dpi 108 --mode ...' command in here.
> Wed Mar 23 03:30:10 EDT 2016
> Screen 0: minimum 8 x 8, current 1680 x 1050, maximum 32767 x 32767
> DP1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm
> x 296mm
> 1680x1050 59.97*+ 74.89
> 1600x1000 60.01
> 1280x1024 75.02 72.05 60.02
> 1440x900 74.98 59.89 59.98
> 1152x864 75.00
> 1280x720 60.00 50.00 59.94
> 1024x768 75.08 70.07 60.00
> 800x600 72.19 75.00 60.32
> 720x576 50.00
> 720x480 60.00 59.94
> 640x480 75.00 72.81 66.67 60.00 59.94
> 720x400 70.08
> DVI1 disconnected (normal left inverted right x axis y axis)
> HDMI1 disconnected (normal left inverted right x axis y axis)
> VGA1 disconnected (normal left inverted right x axis y axis)
> VIRTUAL1 disconnected (normal left inverted right x axis y axis)
This output shows that changing the resolution did succeed and you are in a
1680x1050 mode exactly at this point.
> Wed Mar 23 03:31:09 EDT 2016
> Screen 0: minimum 8 x 8, current 1680 x 1050, maximum 32767 x 32767
> DP1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm
> x 296mm
> 1680x1050 59.97*+ 74.89
> 1600x1000 60.01
> 1280x1024 75.02 72.05 60.02
> 1440x900 74.98 59.89 59.98
> 1152x864 75.00
> 1280x720 60.00 50.00 59.94
> 1024x768 75.08 70.07 60.00
> 800x600 72.19 75.00 60.32
> 720x576 50.00
> 720x480 60.00 59.94
> 640x480 75.00 72.81 66.67 60.00 59.94
> 720x400 70.08
> DVI1 disconnected (normal left inverted right x axis y axis)
> HDMI1 disconnected (normal left inverted right x axis y axis)
> VGA1 disconnected (normal left inverted right x axis y axis)
> VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Ok, you ran 'xrandr -q' again a second later. Mode is still the same, ie the
one you were trying to set.
If you are at a 1440x900 mode by the time your desktop is finally up, there is
something else that changes your mode again. I'm sure, that the Xserver log
file will show traces of this.
Now, I don't know what this is what changes your mode. This is why I tried to
get the KDE folks into the boat as well. Could it be that your:
[Module-kscreen]
autoload=false
doesn't work any more?
I don't know.
> Other than brief food and nature breaks, responding here has occupied the
> overwhelming majority of the past 9 hours or so of my time. I still have yet
> to finish responding to all Egbert Eich comments that I hope or intend to.
> Timezone here is -0500, so it's now past bedtime yet again.
Please be assured that testing things for this ticket took me a considerable
amount of time yesterday as well ;)