[Bug 94403] [regression] scripted xrandr commands in /etc/X11/xinit/xinitrc.d/ are disregarded
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Mar 6 09:23:15 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=94403
--- Comment #4 from Felix Miata <mrmazda at earthlink.net> ---
Created attachment 122124
--> https://bugs.freedesktop.org/attachment.cgi?id=122124&action=edit
bad & good F24 on big41 Xorg.0.logs prepended with applicable xrandr
On host big41's F24 freshly updated, I found a difference between working and
non-working xrandr, using:
xrandr --dpi 108 --output HDMI1 --mode 1400x1050 --output VGA1 --mode 1680x1050
--primary --above HDMI1 # intel dual 1
xrandr failing:
[ 567.401] Kernel command line: ro root=LABEL=f24p13sv5 ipv6.disable=1
net.ifnames=0 selinux=0 splash=0 vga=791 video=1280x720 at 60 video=1024x768 at 60
video=1440x900 at 60 3
xrandr succeeding:
[ 44.192] Kernel command line: ro root=LABEL=f24p13sv5 ipv6.disable=1
net.ifnames=0 selinux=0 splash=0 3
Surely this explains at least in part the difference between Intel and
non-Intel gfxchip behavior, as only with Intel driver does Xorg use video= from
cmdline to supplant EDID preferred.
As noted in https://bugs.freedesktop.org/show_bug.cgi?id=90842 xorg.conf on
same big41 F24 installation can produce expected modes and virtual size, while
its DisplaySize is ignored, with or without video= on cmdline. Could the root
of both problems be the same?
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160306/3fa57fb6/attachment.html>
More information about the intel-gfx-bugs
mailing list