bug: 290156 title: "Display out of range" after upgrade to Intrepid date-reported: Tue, 28 Oct 2008 05:41:16 -0000 date-updated: Wed, 13 Jun 2018 08:52:16 -0000 reporter: Scott Kitterman (kitterman) duplicate-of: duplicates: attachments: https://bugs.launchpad.net/bugs/290156/+attachment/403489/+files/lspci text/plain https://bugs.launchpad.net/bugs/290156/+attachment/403576/+files/Xorg.0.log text/plain https://bugs.launchpad.net/bugs/290156/+attachment/403577/+files/Xorg.0.log.old application/x-trash https://bugs.launchpad.net/bugs/290156/+attachment/403593/+files/Xorg.0.log.new text/plain https://bugs.launchpad.net/bugs/290156/+attachment/403671/+files/edid text/plain https://bugs.launchpad.net/bugs/290156/+attachment/406278/+files/xorg.conf.intrepid text/plain https://bugs.launchpad.net/bugs/290156/+attachment/406287/+files/Xorg.0.log.intrepid text/plain patches: tags: fuzzy-match intrepid subscribers: Scott Kitterman (kitterman) L.Lopez (ldotlopez) Daniel Elstner (daniel-elstner) Murray Cumming (murrayc) Sergio Zanchetta (primes2h) task: ubuntu-release-notes status: Invalid date-created: Wed, 29 Oct 2008 04:11:01 -0000 date-left-new: Wed, 29 Oct 2008 18:01:42 -0000 date-closed: Wed, 29 Oct 2008 18:01:42 -0000 reporter: Scott Kitterman (kitterman) importance: Undecided assignee: milestone: task: xorg-server status: Invalid date-created: Wed, 29 Oct 2008 04:10:26 -0000 date-closed: Wed, 13 Jun 2018 08:52:14 -0000 reporter: Scott Kitterman (kitterman) watch: https://bugs.freedesktop.org/show_bug.cgi?id=18276 importance: High assignee: milestone: task: kdebase-workspace (Ubuntu) status: Invalid date-created: Tue, 28 Oct 2008 05:41:16 -0000 date-left-new: Tue, 28 Oct 2008 18:18:42 -0000 date-closed: Tue, 28 Oct 2008 18:18:42 -0000 reporter: Scott Kitterman (kitterman) importance: High component: main assignee: milestone: task: xorg-server (Ubuntu) status: Fix Released date-created: Tue, 28 Oct 2008 14:42:04 -0000 date-left-new: Tue, 28 Oct 2008 17:39:00 -0000 date-confirmed: Tue, 28 Oct 2008 20:28:40 -0000 date-triaged: Tue, 28 Oct 2008 20:28:40 -0000 date-inprogress: Tue, 20 Oct 2009 20:15:35 -0000 date-closed: Tue, 20 Oct 2009 20:15:35 -0000 date-fix-committed: Tue, 20 Oct 2009 20:15:35 -0000 date-fix-released: Tue, 20 Oct 2009 20:15:35 -0000 reporter: Scott Kitterman (kitterman) importance: High component: main assignee: milestone: task: kdebase-workspace (Ubuntu Intrepid) status: Invalid date-created: Tue, 28 Oct 2008 10:24:25 -0000 date-left-new: Tue, 28 Oct 2008 18:18:42 -0000 date-closed: Tue, 28 Oct 2008 18:18:42 -0000 reporter: Scott Kitterman (kitterman) importance: High assignee: milestone: task: xorg-server (Ubuntu Intrepid) status: Won't Fix date-created: Tue, 28 Oct 2008 14:42:04 -0000 date-left-new: Tue, 28 Oct 2008 17:39:00 -0000 date-closed: Tue, 30 Mar 2010 20:47:54 -0000 reporter: Scott Kitterman (kitterman) importance: High assignee: milestone: Content-Type: multipart/mixed; boundary="===============2077016769620645478==" MIME-Version: 1.0 --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Binary package hint: kdebase-workspace System works fine in Hardy. Intel D945Gnt with Intel integrated graphics. = Hitachi CM721F monitor gets display out of range error no matter what reso= lution or frequency I try. Tried dpkg-reconfigure on X. Tried xfix in the= recovery console. System works fine with a Viewsonic VA903b LCD. [lspci] 00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Control= ler Hub [8086:2770] (rev 02) Subsystem: Intel Corporation Device [8086:544e] 00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integ= rated Graphics Controller [8086:2772] (rev 02) Subsystem: Intel Corporation Device [8086:544e] --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Tue, 28 Oct 2008 14:35:19 -0000 Message-Id: <20081028143519.30582.83037.malone@gandwana.canonical.com> uname -a: Linux kid-desktop 2.6.27-7-generic #1 SMP Fri Oct 24 06:42:44 UTC 2008 i686= GNU/Linux lspci output attached. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Tue, 28 Oct 2008 14:38:12 -0000 Message-Id: <20081028143812.12975.53894.malone@palladium.canonical.com> sudo discover --disable=3Dparallel,serial,usb,ide,scsi,pcmcia --format=3D"%= M\t%S\t%D\t%i\n" video discover: Bus not found. sudo xresprobe intel id: VA903 SERIES res: 1280x1024 1280x960 1152x864 1024x768 832x624 800x600 720x400 640x480 freq: 30-82 50-85 disptype: This is using the working LCD. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Tue, 28 Oct 2008 14:42:47 -0000 Message-Id: <20081028144247.13105.90914.malone@palladium.canonical.com> Not sure if I should blame X or krandr. More info when I have more energy for this. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Tue, 28 Oct 2008 17:26:40 -0000 Message-Id: <20081028172641.4437.23982.malone@gangotri.canonical.com> This is the log when using the working LCD. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Tue, 28 Oct 2008 17:28:13 -0000 Message-Id: <20081028172813.4437.78936.malone@gangotri.canonical.com> Xorg.0.log.old --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Tue, 28 Oct 2008 17:37:26 -0000 Message-Id: <20081028173726.30234.74585.malone@gandwana.canonical.com> Often these issues occur due to issues with the monitor's EDID. EDID issues are monitor-specific, so that can account for why swapping monitors seems to make the issue go away. An Xorg.0.log from booting with that monitor *should* display the EDID. Another tool for getting the EDID is available in the read-edid package. `get-edid | parse-edid`, but I'm not sure if you can run that if the monitor isn't working in the first place... However, these sorts of EDID bugs *shouldn't* appear from a hardy->intrepid upgrade, so the fact that it did suggests that something deeper's at work. Even so, looking at the EDID may be of use. The xrandr command line tool can also be used to add/remove modelines and examine the running X server. What I'd do is ssh into the box from another system, boot X until you get to the invalid mode situation, and poke at it with xrandr to try to get a functioning modeline. See man xrandr for documentation on this. Perhaps with an Xorg.0.log from the failed case I can give some more specific advice, and investigate if there's any quirks, or changes in the xserver that could account for this issue. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Tue, 28 Oct 2008 17:52:39 -0000 Message-Id: <20081028175239.30722.12792.malone@gandwana.canonical.com> Here's the log booting with the bad monitor. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Tue, 28 Oct 2008 18:03:56 -0000 Message-Id: <99256-SnapperMsgD8DB99B6C52D049F@[75.197.99.109]> If the log doesn't help would running those tools in an alternate VT work? --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Tue, 28 Oct 2008 18:18:24 -0000 Message-Id: <20081028181824.12623.98840.malone@palladium.canonical.com> (II) intel(0): Using fuzzy aspect match for initial modes (II) intel(0): Output VGA using initial mode 2048x1536 It looks like it's not finding an exact match between your video card's resolution/refresh rates, and what your monitor can do, so it's doing a fuzzy match, which results in a resolution (2048x1536) that's out of range for the monitor. Silly thing. For now, I think you can get around this by ssh'ing into the box and using xrandr to temporarily set a different resolution (e.g. xrandr --output VGA --mode 1024x768). That should enable you to boot up. Then use the Screen Resolution tool to select a resolution to use persistently. If you can also attach the output of `get-edid | parse-edid` with this monitor attached, I can forward this bug upstream so we can hopefully get a permanent fix. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Tue, 28 Oct 2008 19:10:53 -0000 Message-Id: <99274-SnapperMsgD8DB99B6C52D1445@[75.197.99.109]> Will do when I get back to the box. Since this is a regression from Hardy,= =20 do we need a release note or something? --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Tue, 28 Oct 2008 19:54:32 -0000 Message-Id: <20081028195432.13105.76134.malone@palladium.canonical.com> Output of get-edid | parse-edid. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Tue, 28 Oct 2008 20:28:38 -0000 Message-Id: <20081028202838.12975.3109.malone@palladium.canonical.com> I think we're up to Triaged now. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Tue, 28 Oct 2008 21:09:12 -0000 Message-Id: <20081028210912.28820.73811.malone@potassium.ubuntu.com> Hi Scott, I've forwarded your bug upstream to https://bugs.freedesktop.org/show_bug.cgi?id=3D18276. Please subscribe to that bug, in case upstream wishes additional information or needs you to test something. Thanks ahead of time! --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Wed, 29 Oct 2008 04:09:22 -0000 Message-Id: <20081029040922.26770.99038.malone@palladium.canonical.com> I have a kdm specific work around. I added: xrandr --output VGA --mode 1280x960 to /etc/kde4/kdm/Xsetup That particular script runs as root before the login dialogue appears so the settings affect all uses and the login dialogue. All the per user attempts were failing because the login dialogue was still at the wrong resolution. There is still a brief 'out of range' error when the initial wallpaper is shown at full resolution, but then it shifts and login/normal operation follows. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Wed, 29 Oct 2008 04:11:57 -0000 Message-Id: <20081029041157.30582.12019.malone@gandwana.canonical.com> Not sure if this kind of issue should get release noted or not, but it's a regression from Hardy and a very problematic one if you happen to have the affected monitor. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Wed, 29 Oct 2008 18:01:06 -0000 Message-Id: <20081029180106.10413.45877.malone@palladium.canonical.com> Since this seems to be an EDID modeline mismatch, my guess is that this is a very monitor model-specific issue (i.e., other Hitachi monitors won't have this problem, just the specific model you have). It may even be particular to the specific monitor and graphics card combo (i.e., maybe swapping out either a different monitor or a different video card, and it works). So at this point I'm not sure it's important enough to put in the release notes, esp. since the workaround takes a bit to explain. I could be wrong though - if there is a pattern of "Display out of range" regressions reported, then it could be something different in xserver's mode selection logic. Upstream should be able to clue us in on this, or if we can find a spate of bug reports similar to this one but with different monitors. If evidence proves to be the case, then yeah we definitely should include mention of it. Regardless, I definitely agree this is well worth having a documented worka= round/troubleshooting guide, even if it's not referenced in the release not= es. I've written up a shot of it here: =20 https://wiki.ubuntu.com/X/Troubleshooting/Resolution . Please review and = copyedit. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: L.Lopez (ldotlopez) Date: Sat, 01 Nov 2008 14:04:34 -0000 Message-Id: <20081101140434.31452.67772.malone@potassium.ubuntu.com> I hit the same bug using LG Flatron L222WS monitor and Radeon HD 2400 PRO video card. Adding xrandr --output VGA --mode 1650x1050 to my /etc/gdm/Init/Default doesnt work --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: L.Lopez (ldotlopez) Date: Sat, 01 Nov 2008 14:05:25 -0000 Message-Id: <20081101140525.31320.65835.malone@potassium.ubuntu.com> Xorg log --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: leshachek (vladimir-highskytech) Date: Sun, 26 Apr 2009 02:42:31 -0000 Message-Id: <20090426024231.30731.57151.malone@gandwana.canonical.com> I have this problem trying to install Kubuntu Intrepid on a PC, Intel LGA77= 5 with Hitachi CM715 monitor attached. I incidently was trying to install 3= 2 bit first and had the problem. however Intrepid 64 bit version does not h= ave this problem and I installed it smoothly within 15 minutes. Note. Fedora 10, 64 bit seems has the same problem.=20 Vladimir --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Scott Kitterman (kitterman) Date: Tue, 20 Oct 2009 20:15:29 -0000 Message-Id: <20091020201531.3875.51069.malone@gangotri.canonical.com> Works fine with the same monitor on Karmic (without the work around). --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sergio Zanchetta (primes2h) Date: Tue, 30 Mar 2010 20:47:53 -0000 Message-Id: <20100330204754.32371.81612.malone@gandwana.canonical.com> Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL = on 30 March 2010. Please see this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases=20 Please feel free to report any other bugs you may find.=20 Thank you. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sergio Zanchetta (primes2h) Date: Tue, 30 Mar 2010 21:38:48 -0000 Message-Id: <20100330213848.23595.17206.malone@wampee.canonical.com> I realized I had made a mistake, Intrepid Ibex 8.10 "will reach" EOL on 30 "APRIL" 2010. Sorry for this. Anyway, I think that one month doesn't make any difference now. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Tue, 28 Oct 2008 14:04:59 -0000 Message-Id: <152887993946.11742.5357404832508043513.launchpad@loganberry.canonical.com> Forwarding this bug from a Ubuntu reporter: https://bugs.edge.launchpad.net/ubuntu/+bug/290156 [Problem] Intel D945Gnt + Hitachi CM721F monitor gets display out of range error on x= server 1.5.2. [Discussion] From the Xorg.0.log it appears confused what resolution to use, and ends up= picking one the monitor can't do: (II) intel(0): Using fuzzy aspect match for initial modes (II) intel(0): Output VGA using initial mode 2048x1536 From the EDID it appears this monitor provides one modeline: Mode "1600x1200" # vfreq 75.000Hz, hfreq 93.750kHz DotClock 202.500000 HTimings 1600 1664 1856 2160 VTimings 1200 1201 1204 1250 Flags "+HSync" "+VSync" EndMode I'm assuming that it ought to be matching this modeline: (II) intel(0): Modeline "1600x1200"x75.0 205.99 1600 1720 1896 2192 1200 1201 1204 1253 -hsync +vsync (94.0 kHz) So why might it not be matching up properly? Where is the 2048x1536 resolution coming from? Is that what it's actually trying to use? Is there a way (e.g. a quirk) to force it to not use anything above 1600x1200? --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Tue, 28 Oct 2008 14:07:58 -0000 Message-Id: <152887993960.11742.17175118703861296976.launchpad@loganberry.canonical.com> Created attachment 19915 Parsed EDID info --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Bryce Harrington (bryce) Date: Tue, 28 Oct 2008 14:08:23 -0000 Message-Id: <152887993962.11742.4778405826575636537.launchpad@loganberry.canonical.com> Created attachment 19916 Xorg.0.log from failed session --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Ajax-a (ajax-a) Date: Mon, 10 May 2010 11:41:06 -0000 Message-Id: <152887993966.11742.6107799424868184985.launchpad@loganberry.canonical.com> The raw edid block is much more useful than the parsed one... --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Ajax-a (ajax-a) Date: Mon, 09 Aug 2010 13:16:06 -0000 Message-Id: <152887993969.11742.5924968306049537776.launchpad@loganberry.canonical.com> No EDID block means I can't work on this. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Sklist (sklist) Date: Mon, 09 Aug 2010 14:02:46 -0000 Message-Id: <152887993973.11742.2708903078361210732.launchpad@loganberry.canonical.com> Tell me how to collect the information and I'll be glad to do it. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Julien Cristau (jcristau) Date: Sun, 22 Aug 2010 04:02:52 -0000 Message-Id: <152887993978.11742.13391668948800799619.launchpad@loganberry.canonical.com> (In reply to comment #5) > Tell me how to collect the information and I'll be glad to do it. xrandr --prop should list it. Or, with kms, /sys/class/drm/card0-$output/edid. --===============2077016769620645478== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Author: Ajax-a (ajax-a) Date: Tue, 12 Jun 2018 18:43:41 -0000 Message-Id: <152887993981.11742.16033596632264487715.launchpad@loganberry.canonical.com> Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server. --===============2077016769620645478==--