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