1 |
On Mon, 14 Sep 2009 11:23:38 +0200 |
2 |
Alan McKinnon wrote: |
3 |
|
4 |
> On Monday 14 September 2009 02:59:28 David Relson wrote: |
5 |
> > G'day, |
6 |
> > |
7 |
> > I'm running Xorg with a minimal config file (only 15 lines - which |
8 |
> > provide font paths and set the AllowMouseOpenFail option). |
9 |
> > |
10 |
> > When I last restarted my computer (about 3 months ago), X came up in |
11 |
> > 1280x1024 mode. Today I restarted X (because the shift and control |
12 |
> > keys were non-responsive) and my computer is in 1024x768 mode. I |
13 |
> > much prefer the higher resolution. |
14 |
> > |
15 |
> > I have the Xorg.0.log files from the reboot 3 months ago and |
16 |
> > today's X restart. What should I be looking at in them to diagnose |
17 |
> > what has happened differently? |
18 |
> > |
19 |
> > Several obvious questions arise: |
20 |
> > |
21 |
> > _Why_ did X select a different resolution today? |
22 |
> > _How_ can I get to the higher resolution? |
23 |
> > _What_ can I do to prevent a recurrence of this problem? |
24 |
> > |
25 |
> > I'm running a 2.6.28-gentoo-r5 kernel with the following packages: |
26 |
> > |
27 |
> > x11-base/xorg-x11-7.2 |
28 |
> > x11-drivers/ati-drivers-8.552-r2 |
29 |
> > x11-drivers/xf86-video-ati-6.12.1-r1 |
30 |
> |
31 |
> Recent Xorg interrogates the hardware to find what resolutions it |
32 |
> supports and can pick one of those to use. The user can also specify |
33 |
> their preference, so I reckon you likely didn't specify a preference; |
34 |
> and what Xorg thinks you want isn't what you want. |
35 |
> |
36 |
> Look for the string "EDID" in both logs and make comparisons in that |
37 |
> area. |
38 |
> |
39 |
> Before you do that, run "genlop -l" or examine emerge.log to find |
40 |
> what upgrades and merges were done in the last three months that |
41 |
> affect resolution. |
42 |
|
43 |
H'lo Alan, |
44 |
|
45 |
Here's what genlop found for "x11.*" since June 1: |
46 |
|
47 |
Mon Jun 15 00:20:36 2009 >>> x11-libs/openmotif-2.3.2 |
48 |
Sun Jun 21 11:58:51 2009 >>> x11-drivers/ati-drivers-8.552-r2 |
49 |
Sun Jun 21 17:59:39 2009 >>> x11-drivers/ati-drivers-8.552-r2 |
50 |
Sun Jun 21 19:48:37 2009 >>> x11-drivers/ati-drivers-8.552-r2 |
51 |
|
52 |
*** GOOD REBOOT |
53 |
|
54 |
Fri Jul 10 23:28:06 2009 >>> x11-libs/qt-test-4.5.1 |
55 |
Sat Jul 11 07:12:12 2009 >>> |
56 |
x11-themes/gtk-engines-ubuntulooks-0.9.12-r3 Sat Jul 25 13:02:56 2009 |
57 |
>>> x11-drivers/ati-drivers-8.552-r2 Sun Jul 26 08:24:12 2009 >>> |
58 |
>>> x11-libs/libgksu-2.0.9 |
59 |
Sun Jul 26 08:30:31 2009 >>> x11-libs/gksu-2.0.2 |
60 |
Tue Jul 28 07:24:07 2009 >>> x11-drivers/ati-drivers-8.552-r2 |
61 |
Fri Aug 7 18:25:05 2009 >>> x11-libs/fltk-2.0_pre6786-r1 |
62 |
|
63 |
ati-drivers-8.552-r2 package was present at the reboot and has been |
64 |
reinstalled since. None of these x11 packages seem relevant. |
65 |
|
66 |
Grepping for EDID finds no hits in the old log and multiple occurrences |
67 |
of RADEON in the new log. Comparing the logs shows VESA in old, but |
68 |
not new. Here are grep counts: |
69 |
|
70 |
root@osage log # grep -c VESA Xorg.0.old.log Xorg.0.new.log |
71 |
Xorg.0.old.log:79 |
72 |
Xorg.0.new.log:4 |
73 |
root@osage log # grep -c RADEON Xorg.0.old.log Xorg.0.new.log |
74 |
Xorg.0.old.log:0 |
75 |
Xorg.0.new.log:385 |
76 |
|
77 |
Perhaps I need to specify VESA in xorg.conf somehow ??? |
78 |
|
79 |
Regards, |
80 |
|
81 |
David |