Re: [gentoo-user] x11-base/xorg-server-1.5.3-r5 with x11-drivers/ati-drivers-8.552-r2 -- file conflict

["Kevin O'Gorman" <kogorman@gmail.com>]

Summary: X is hosed.

On Fri, May 22, 2009 at 6:35 AM, Kevin O'Gorman <kogorman@gmail.com> wrote:
> On Fri, May 22, 2009 at 2:40 AM, Alex Schuster <wonko@wonkology.org> wrote:
>> Kevin O'Gorman writes:
>>
>>> On Thu, May 21, 2009 at 8:20 PM, Kevin O'Gorman <kogorman@gmail.com>
>> wrote:
>>
>>> > I thank you for the expert advice.  I'm doing the emerge now, but even
>>> > if it succeeds, I'm worried that the xorg-server will still own this
>>> > file, since portageq seems to see that it does.  This seems inherently
>>> > wrong.
>>
>> Well, it is indeed.
>>
>>> > Sigh.  I'm too far along to flinch now, so if this emerges, I'll
>>> > probably restart X.
>>> >
>>> > Wish me luck.
>>
>> I do, but I do not believe bad things might happen.
>>
>>> Hmm.  Even with the FEATURES option from the suggestion, I get exactly
>>> the same error message.  I cut-and-pasted it, but I wonder if it's
>>> spelled right?
>>
>> It is. But I forgot about the protect-owned feature. I thought -collision-
>> protect would act stronger and imply it, but apparently it does not. So,
>> 'FEATURES=-protect-owned emerge ati-drivers' might have worked better. If
>> not, 'FEATURES="-collision-protect -protect-owned" emerge ati-drivers' would
>> have worked in any case.
>>
>>> I'm going to try just deleting (well, renaming) the file, hoping that
>>> this will work...
>>
>> Yes, that's okay. After all, the file is still there, it's just now being
>> generated by the ati-driver. I wouldn't worry too much.
>>
>>        Wonko
>
> well, it emerged this time.  I'm going to restart X over the weekend,
> when I'll have time to clean up the mess that I half expect.
>
> ++ kevin

As I suspected, X won't restart.

When I reboot, the scripts want to run "xdm", which is not loaded on
the system.  This started a while ago and is part of what made me give
up on keeping the new xorg masked.

"kdm" does nothing at all that I can see, but it was the way I was
getting X up before I re-emerged the ati drivers.

"startx" at least gives error messages and writes the log.  It didn't
like my xorg.conf, and had this to say about it:
=========================
treat X11 # startx
xauth:  creating new authority file /root/.serverauth.7467


X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.28-gentoo-r5-kosmanor i686
Current Operating System: Linux treat 2.6.28-gentoo-r5-kosmanor #5 SMP
PREEMPT Tue May 19 13:17:14 PDT 2009 i686
Build Date: 18 May 2009  09:25:28PM

	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat May 23 14:54:31 2009
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "type1" (module does not exist, 0)
(EE) module ABI major version (1) doesn't match the server's version (4)
(EE) Failed to load module "ati" (module requirement mismatch, 0)
(EE) No drivers available.

Fatal server error:
no screens found
giving up.
xinit:  Connection refused (errno 111):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.
treat X11 #
=============================
If I remove the "xorg.conf" file, the message about type1 goes away,
but it still won't load the ati drivers.

I'm at a loss.  Where do I go to get my X back?  I mean where in the
documentation, of course, but I'm open to other suggestions.

++ kevin

-- 
Kevin O'Gorman, PhD