*** This bug is a duplicate of bug 640807 ***
https://bugs.launchpad.net/bugs/640807
Thanks for all the help Tormod.
I've marked this as a duplicate of bug 640807.
** This bug has been marked a duplicate of bug 640807
automatic xrandr module misconfigures monitors
* You can subscribe to
The EDID information from the monitor lists 1600x1...@75hz as a
supported Standard Timing, and the clock rates are within ranges,
although close to the limits. So this might be false information built
in to your monitor (or it can not handle its own stated specifications)
and not a bug in the X ser
** Changed in: xorg (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: badmode
--
Maverick xorg results in "out of range" error w/Intel i945 & 22" LCD
https://bugs.launchpad.net/bugs/654660
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed t
** Attachment added: "xrandr.white.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/654660/+attachment/1673974/+files/xrandr.white.txt
--
Maverick xorg results in "out of range" error w/Intel i945 & 22" LCD
https://bugs.launchpad.net/bugs/654660
You received this bug notification bec
Thanks. You can always redirect the command output to a file, and attach the
file, for instance:
xrandr --verbose -d :0 > xrandr.white.txt
I am not sure it is normal to have a 1600x1...@75.0hz mode in your case,
especially if it makes the monitor flaky! Please attach the verbose
output so we can
The output of "xrandr --verbose -d :0" is so long that I can't see the
top portion, which I can see after playing is what we really need to
see, but I did manage to get the output of "xrandr -d :0". This is the
broken one:
ubu...@ubuntu:~$ xrandr -d :0
Screen 0: minimum 320 x 200, current 1600 x 1
Sorry I forgot the -d in there!
xrandr --verbose -d :0
--
Maverick xorg results in "out of range" error w/Intel i945 & 22" LCD
https://bugs.launchpad.net/bugs/654660
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
_
Running "xrandr --verbose :0" simply shows all xrandr options, same if I
copy-n-paste from a working install:
la...@lance-desktop:~$ xrandr --verbose :0
usage: xrandr [options]
where options are:
...
If I run xrandr wit
Thanks for filing your own report! Would you be able to tell us which
mode is broken, that is, the one that is chosen when it is "Out of
range"? Running "xrandr --verbose :0" on the ctrl-alt-F1 console while X
is broken should tell.
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/654660/+attachment/1671596/+files/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/654660/+attachment/1671597/+files/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http
10 matches
Mail list logo
