| 1 |
Summary: X is hosed. |
| 2 |
|
| 3 |
On Fri, May 22, 2009 at 6:35 AM, Kevin O'Gorman <kogorman@×××××.com> wrote: |
| 4 |
> On Fri, May 22, 2009 at 2:40 AM, Alex Schuster <wonko@×××××××××.org> wrote: |
| 5 |
>> Kevin O'Gorman writes: |
| 6 |
>> |
| 7 |
>>> On Thu, May 21, 2009 at 8:20 PM, Kevin O'Gorman <kogorman@×××××.com> |
| 8 |
>> wrote: |
| 9 |
>> |
| 10 |
>>> > I thank you for the expert advice. I'm doing the emerge now, but even |
| 11 |
>>> > if it succeeds, I'm worried that the xorg-server will still own this |
| 12 |
>>> > file, since portageq seems to see that it does. This seems inherently |
| 13 |
>>> > wrong. |
| 14 |
>> |
| 15 |
>> Well, it is indeed. |
| 16 |
>> |
| 17 |
>>> > Sigh. I'm too far along to flinch now, so if this emerges, I'll |
| 18 |
>>> > probably restart X. |
| 19 |
>>> > |
| 20 |
>>> > Wish me luck. |
| 21 |
>> |
| 22 |
>> I do, but I do not believe bad things might happen. |
| 23 |
>> |
| 24 |
>>> Hmm. Even with the FEATURES option from the suggestion, I get exactly |
| 25 |
>>> the same error message. I cut-and-pasted it, but I wonder if it's |
| 26 |
>>> spelled right? |
| 27 |
>> |
| 28 |
>> It is. But I forgot about the protect-owned feature. I thought -collision- |
| 29 |
>> protect would act stronger and imply it, but apparently it does not. So, |
| 30 |
>> 'FEATURES=-protect-owned emerge ati-drivers' might have worked better. If |
| 31 |
>> not, 'FEATURES="-collision-protect -protect-owned" emerge ati-drivers' would |
| 32 |
>> have worked in any case. |
| 33 |
>> |
| 34 |
>>> I'm going to try just deleting (well, renaming) the file, hoping that |
| 35 |
>>> this will work... |
| 36 |
>> |
| 37 |
>> Yes, that's okay. After all, the file is still there, it's just now being |
| 38 |
>> generated by the ati-driver. I wouldn't worry too much. |
| 39 |
>> |
| 40 |
>> Wonko |
| 41 |
> |
| 42 |
> well, it emerged this time. I'm going to restart X over the weekend, |
| 43 |
> when I'll have time to clean up the mess that I half expect. |
| 44 |
> |
| 45 |
> ++ kevin |
| 46 |
|
| 47 |
As I suspected, X won't restart. |
| 48 |
|
| 49 |
When I reboot, the scripts want to run "xdm", which is not loaded on |
| 50 |
the system. This started a while ago and is part of what made me give |
| 51 |
up on keeping the new xorg masked. |
| 52 |
|
| 53 |
"kdm" does nothing at all that I can see, but it was the way I was |
| 54 |
getting X up before I re-emerged the ati drivers. |
| 55 |
|
| 56 |
"startx" at least gives error messages and writes the log. It didn't |
| 57 |
like my xorg.conf, and had this to say about it: |
| 58 |
========================= |
| 59 |
treat X11 # startx |
| 60 |
xauth: creating new authority file /root/.serverauth.7467 |
| 61 |
|
| 62 |
|
| 63 |
X.Org X Server 1.5.3 |
| 64 |
Release Date: 5 November 2008 |
| 65 |
X Protocol Version 11, Revision 0 |
| 66 |
Build Operating System: Linux 2.6.28-gentoo-r5-kosmanor i686 |
| 67 |
Current Operating System: Linux treat 2.6.28-gentoo-r5-kosmanor #5 SMP |
| 68 |
PREEMPT Tue May 19 13:17:14 PDT 2009 i686 |
| 69 |
Build Date: 18 May 2009 09:25:28PM |
| 70 |
|
| 71 |
Before reporting problems, check http://wiki.x.org |
| 72 |
to make sure that you have the latest version. |
| 73 |
Markers: (--) probed, (**) from config file, (==) default setting, |
| 74 |
(++) from command line, (!!) notice, (II) informational, |
| 75 |
(WW) warning, (EE) error, (NI) not implemented, (??) unknown. |
| 76 |
(==) Log file: "/var/log/Xorg.0.log", Time: Sat May 23 14:54:31 2009 |
| 77 |
(==) Using config file: "/etc/X11/xorg.conf" |
| 78 |
(EE) Failed to load module "type1" (module does not exist, 0) |
| 79 |
(EE) module ABI major version (1) doesn't match the server's version (4) |
| 80 |
(EE) Failed to load module "ati" (module requirement mismatch, 0) |
| 81 |
(EE) No drivers available. |
| 82 |
|
| 83 |
Fatal server error: |
| 84 |
no screens found |
| 85 |
giving up. |
| 86 |
xinit: Connection refused (errno 111): unable to connect to X server |
| 87 |
xinit: No such process (errno 3): Server error. |
| 88 |
treat X11 # |
| 89 |
============================= |
| 90 |
If I remove the "xorg.conf" file, the message about type1 goes away, |
| 91 |
but it still won't load the ati drivers. |
| 92 |
|
| 93 |
I'm at a loss. Where do I go to get my X back? I mean where in the |
| 94 |
documentation, of course, but I'm open to other suggestions. |
| 95 |
|
| 96 |
++ kevin |
| 97 |
|
| 98 |
-- |
| 99 |
Kevin O'Gorman, PhD |
Archives