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