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 1MnAAZ-0005px-Qo for garchives@archives.gentoo.org; Mon, 14 Sep 2009 11:56:32 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 47627E0810; Mon, 14 Sep 2009 11:56:30 +0000 (UTC) Received: from mail-fx0-f211.google.com (mail-fx0-f211.google.com [209.85.220.211]) by pigeon.gentoo.org (Postfix) with ESMTP id D8D35E0810 for ; Mon, 14 Sep 2009 11:56:29 +0000 (UTC) Received: by fxm7 with SMTP id 7so1990166fxm.34 for ; Mon, 14 Sep 2009 04:56:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=jVbI5Xvt2CBKPJ65eMyZyJsbLnDyr1sttS/Fsgu6hiQ=; b=eko+LEyfD6QALi9Xr/3D3+xDvyGRGR9W/YYbN4wpno1KIjlikVrXWpVeJmtzhEmT1k xIJmpLL1acrS3Q1cNzYrJ5IeVMzWxDGEXlghKt+JbVdFpl/407fdraKTuJYt+RKQSrJb +BYwDbeOCK1k9ICJhqVqiPViBTqDqcAdM6Gyw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=FBX20kQOCn7gSL25dwh4Ip6en+m/AX+LLVSY2sbChl09s7wkZ7y4Yrjz7rNxp+qQA0 JE/xp8vfjt3WhMTKlVyEemdBd5vfC/+ZHW192HiENhqT7s/BNzesGdA6HFka3fG198ro C8/rsGeRxpfJq3MtvyC0zkjCSRTU/mWGxvENw= Received: by 10.86.103.19 with SMTP id a19mr4874019fgc.54.1252929389280; Mon, 14 Sep 2009 04:56:29 -0700 (PDT) Received: from nazgul.localnet (196-210-140-68-rrdg-esr-2.dynamic.isadsl.co.za [196.210.140.68]) by mx.google.com with ESMTPS id d4sm299382fga.11.2009.09.14.04.56.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 14 Sep 2009 04:56:28 -0700 (PDT) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Screen resolution problem Date: Mon, 14 Sep 2009 13:54:50 +0200 User-Agent: KMail/1.12.1 (Linux/2.6.31-gentoo; KDE/4.3.1; x86_64; ; ) References: <20090913205928.5154bf74@osage.osagesoftware.com> <200909141123.38784.alan.mckinnon@gmail.com> <20090914073639.467706ea@osage.osagesoftware.com> In-Reply-To: <20090914073639.467706ea@osage.osagesoftware.com> 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 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200909141354.50518.alan.mckinnon@gmail.com> X-Archives-Salt: 7da94b17-3089-4782-abad-1d6fa1ebe9d0 X-Archives-Hash: 34df7e6c6fb107401c105d0038e0119a On Monday 14 September 2009 13:36:39 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 ??? It's been a while since I looked into the X logs on my spare machine (which has an ati card). Obviously my memories of what I used to do are now obsolete :-) There's also this new quirk called hal ... I recommend you post the current and previous logs as attachments, together with the output of eix for xorg-server and your drivers. Many eyeballs might get to the bottom of it. -- alan dot mckinnon at gmail dot com