From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MnADr-0006I1-36 for garchives@archives.gentoo.org; Mon, 14 Sep 2009 11:59:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9B66FE0891; Mon, 14 Sep 2009 11:59:53 +0000 (UTC) Received: from outbound.icp-qv1-irony-out2.iinet.net.au (outbound.icp-qv1-irony-out2.iinet.net.au [203.59.1.107]) by pigeon.gentoo.org (Postfix) with ESMTP id A4CFCE0891 for ; Mon, 14 Sep 2009 11:59:52 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAOPMrUrLOywn/2dsb2JhbADbH4QYBYI6 X-IronPort-AV: E=Sophos;i="4.44,383,1249228800"; d="scan'208";a="562124979" Received: from unknown (HELO moriah.localdomain) ([203.59.44.39]) by outbound.icp-qv1-irony-out2.iinet.net.au with ESMTP; 14 Sep 2009 19:59:50 +0800 Received: from localhost (localhost [127.0.0.1]) by moriah.localdomain (Postfix) with ESMTP id 391BB1974D5B for ; Mon, 14 Sep 2009 19:59:50 +0800 (WST) X-Virus-Scanned: amavisd-new at localdomain Received: from moriah.localdomain ([127.0.0.1]) by localhost (moriah.localdomain [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VAPKiuM3ULan for ; Mon, 14 Sep 2009 19:59:46 +0800 (WST) Received: from [192.168.1.2] (rattus [192.168.1.2]) by moriah.localdomain (Postfix) with ESMTP id 46A2B18F779C for ; Mon, 14 Sep 2009 19:59:46 +0800 (WST) Subject: Re: [gentoo-user] Screen resolution problem From: William Kenworthy To: gentoo-user@lists.gentoo.org In-Reply-To: <20090914073639.467706ea@osage.osagesoftware.com> References: <20090913205928.5154bf74@osage.osagesoftware.com> <200909141123.38784.alan.mckinnon@gmail.com> <20090914073639.467706ea@osage.osagesoftware.com> Content-Type: text/plain Organization: Home in Perth! Date: Mon, 14 Sep 2009 19:59:45 +0800 Message-Id: <1252929585.23332.324.camel@rattus> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 Content-Transfer-Encoding: 7bit X-Archives-Salt: 86d85f92-2fb9-445e-9401-759398b1339b X-Archives-Hash: 938eae69795173dc72cdd6adec5882f5 On Mon, 2009-09-14 at 07:36 -0400, David Relson wrote: > On Mon, 14 Sep 2009 11:23:38 +0200 > Alan McKinnon wrote: > > > On Monday 14 September 2009 02:59:28 David Relson wrote: > > > G'day, > > > > > > I'm running Xorg with a minimal config file (only 15 lines - which > > > provide font paths and set the AllowMouseOpenFail option). > > > > > > When I last restarted my computer (about 3 months ago), X came up in > > > 1280x1024 mode. Today I restarted X (because the shift and control > > > keys were non-responsive) and my computer is in 1024x768 mode. I > > > much prefer the higher resolution. > > > > > > I have the Xorg.0.log files from the reboot 3 months ago and > > > today's X restart. What should I be looking at in them to diagnose > > > what has happened differently? > > > > > > Several obvious questions arise: > > > > > > _Why_ did X select a different resolution today? > > > _How_ can I get to the higher resolution? > > > _What_ can I do to prevent a recurrence of this problem? > > > > > > I'm running a 2.6.28-gentoo-r5 kernel with the following packages: > > > > > > x11-base/xorg-x11-7.2 > > > x11-drivers/ati-drivers-8.552-r2 > > > x11-drivers/xf86-video-ati-6.12.1-r1 > > > > Recent Xorg interrogates the hardware to find what resolutions it > > supports and can pick one of those to use. The user can also specify > > their preference, so I reckon you likely didn't specify a preference; > > and what Xorg thinks you want isn't what you want. > > > > Look for the string "EDID" in both logs and make comparisons in that > > area. > > > > Before you do that, run "genlop -l" or examine emerge.log to find > > what upgrades and merges were done in the last three months that > > affect resolution. > > H'lo Alan, > > Here's what genlop found for "x11.*" since June 1: > > Mon Jun 15 00:20:36 2009 >>> x11-libs/openmotif-2.3.2 > Sun Jun 21 11:58:51 2009 >>> x11-drivers/ati-drivers-8.552-r2 > Sun Jun 21 17:59:39 2009 >>> x11-drivers/ati-drivers-8.552-r2 > Sun Jun 21 19:48:37 2009 >>> x11-drivers/ati-drivers-8.552-r2 > > *** GOOD REBOOT > > Fri Jul 10 23:28:06 2009 >>> x11-libs/qt-test-4.5.1 > Sat Jul 11 07:12:12 2009 >>> > x11-themes/gtk-engines-ubuntulooks-0.9.12-r3 Sat Jul 25 13:02:56 2009 > >>> x11-drivers/ati-drivers-8.552-r2 Sun Jul 26 08:24:12 2009 >>> > >>> x11-libs/libgksu-2.0.9 > Sun Jul 26 08:30:31 2009 >>> x11-libs/gksu-2.0.2 > Tue Jul 28 07:24:07 2009 >>> x11-drivers/ati-drivers-8.552-r2 > Fri Aug 7 18:25:05 2009 >>> x11-libs/fltk-2.0_pre6786-r1 > > ati-drivers-8.552-r2 package was present at the reboot and has been > reinstalled since. None of these x11 packages seem relevant. > > Grepping for EDID finds no hits in the old log and multiple occurrences > of RADEON in the new log. Comparing the logs shows VESA in old, but > not new. Here are grep counts: > > root@osage log # grep -c VESA Xorg.0.old.log Xorg.0.new.log > Xorg.0.old.log:79 > Xorg.0.new.log:4 > root@osage log # grep -c RADEON Xorg.0.old.log Xorg.0.new.log > Xorg.0.old.log:0 > Xorg.0.new.log:385 > > Perhaps I need to specify VESA in xorg.conf somehow ??? > > Regards, > > David > I ran into the same problem though with different versions of the software a couple of days ago. The only fix that worked was to -hal xorg-server, and recreate the xorg.conf file that I had previously deleted, making sure that EDID and DDC were not being used. Section "Device" Identifier "AtiRadeon" Driver "radeon" VendorName "ATI" Option "DPMS" "On" Option "EnablePageFlip" "1" Option "RenderAccel" "1" Option "AGPMode" "4" Option "IgnoreEDID" "1" Option "NoDDC" "1" EndSection Not sure all the settings are optimal, but I have a display thats at least at a usable resolution ... It might seem all and good that xorg automaticly chooses the best resolution - but it clearly doesnt. This is on a system running as 1600x1200 for years on the same hardware, with xorg suddenly deciding it can only do 1280x1024 (and even then, it first defaulted to 1024x768). Whatever happened to the idea that in Linux (and esp gentoo-linux) its the "user" thats in control :) It certainly seems someone - seemingly xorg - dropped the ball recently :( BillK