On Sonntag 07 März 2010, Mick wrote: > On Saturday 06 March 2010 18:43:15 Volker Armin Hemmann wrote: > > On Samstag 06 März 2010, Mick wrote: > > > On Saturday 06 March 2010 16:08:05 Volker Armin Hemmann wrote: > > > > On Samstag 06 März 2010, Mick wrote: > > > > > I first tried radeonhd, but Xorg.0.log complained that it couldn't > > > > > find the ati module, so I added radeon in VIDEO_CARDS and it now > > > > > comes up with this error: > > > > > =========================================== > > > > > (EE) AIGLX error: dlopen of /usr/lib64/dri/r600_dri.so failed > > > > > (/usr/lib64/dri/r600_dri.so: cannot open shared object file: No > > > > > such file or directory) > > > > > (EE) AIGLX: reverting to software rendering > > > > > =========================================== > > > > > > > > > > Have you seen this before? Any idea what I should tweak now to get > > > > > this going? > > > > > > > > mesa. You need to install mesa with the right flags. > > > > > > Thanks Volker, > > > > > > I had installed mesa with the radeon flag already, but now I just > > > unmasked/updated it to 2.4.8 and the above error is gone! > > > > > > However, still no X. :-( > > > > > > I have also added mouse and synaptics, after initially trying with only > > > evdev in my INPUT_DEVICES. So now it looks like this: > > > > > > INPUT_DEVICES="keyboard mouse synaptics evdev" > > > > > > When I added synaptics I got an error about RECORD being disabled > > > because it is broken. I attach my logs in case there is something in > > > there showing why this is not working and I can't see it. > > > > RECORD does not matter. > > > > > I can't explain why both Knoppix and Sysrescue CDs work fine and my > > > Gentoo build does not. I even used their xorg.conf as a guide and > > > still > > > > > no joy. I noticed this message (with no xorg.conf): > > yeah. please create a xorg.conf. Depending on hal is nice and dandy in > > > > theory. But so does not work for many people. > > Hmm, can't make it work after multiple attempts of creating and editing a > xorg.conf. I think that the problem is with the drivers and perhaps the > versions of xorg-server and or mesa. I am using the latest testing of > everything and unmasked any dependencies that they had. > > Tomorrow I will have a go at the fglrx. This is doing my head in ...
fglrx won't have any influence on your INPUT DRIVER based problem. After emerging the latest xorg-server, did you rebuilt the input drivers?
