[drm] drmOpen failed; MACH64(0): [dri] DRIScreenInit Failed

[lesliek at ozemail.com.au]

Thanks for the further reply, Alex.

I can see that I'll be living with the errors that prompted my original post!

Thanks again,

Leslie
--------------------------------------------------
To see papers written by me on, among other things, literary allusions in
Australian reasons for judgment, start here:
http://ssrn.com/author=1164057

To see photos taken by me of, among other things, Sydney now (as well as
comparative photos taken by others of Sydney then), start here:
http://www.flickr.com/photos/23623601@N03/sets/72157604225021655/
--------------------------------------------------

On Wed Aug  4 15:38 , Alex Deucher  sent:

>On Wed, Aug 4, 2010 at 1:27 AM, lesliek at ozemail.com.au
>lesliek at ozemail.com.au> wrote:
>> Thanks for replying, Corbin.
>>
>> Unfortunately, I haven't got the technical knowledge to understand your reply.
>>
>> Could I just ask this?
>>
>> Right now, the log tells me that "ModulePath [is] set to '/usr/lib/X11/modules'".
>>
>> There's a Modules section in my xorg.conf file that lists five modules, "extmod",
>> "dbe", "glx", "freetype" and "dri". Four of those are in
>> /usr/lib/X11/modules/extensions, while one is in /usr/lib/X11/modules/fonts.
>>
>> The file mach64_dri.so is in /usr/lib/dri.
>>
>> Is there any chance that I could copy /dri/mach64_dri.so to /usr/lib/X11/modules
>> and then add the file's name to the Modules section in my xorg.conf file? Or was
>> your reply telling me in effect that that's what I can't do?
>
>mach64_dri.so is the userspace 3D driver.  It's fine where it is.  You
>also need a kernel module that the userspace 3D driver talks to
>actually send the commands to the card.  The mach64 kernel module was
>never merged into the kernel so so you'll have to dig it out of the
>old out of kernel drm git tree and built it yourself.  I doubt it will
>build on a recent kernel, so you'll probably have to do some hacking
>to get it built against whatever kernel you are running.
>
>Alex
>
>>
>> Thanks again,
>>
>> Leslie
>>
>> --------------------------------------------------
>> To see papers written by me on, among other things, literary allusions in
>> Australian reasons for judgment, start here:
>> http://ssrn.com/author=1164057
>>
>> To see photos taken by me of, among other things, Sydney now (as well as
>> comparative photos taken by others of Sydney then), start here:
>> http://www.flickr.com/photos/23623601@N03/sets/72157604225021655/
>> --------------------------------------------------
>>
>> On Wed Aug  4 14:54 , Corbin Simpson  sent:
>>
>>>The DRI drivers are userspace. The DRM component for mach64, a kernel driver,
>> isn't included in the standard Linux kernel. You are probably on your own as far
>> as obtaining and building it.
>>>Sending from a mobile, pardon the brevity. ~ C.
>>>On Aug 3, 2010 9:41 PM, "lesliek at ozemail.com.au" lesliek at ozemail.com.au> wrote:
>>>Thanks for your reply, Alex.
>>>
>>>
>>>
>>>SliTaz has available a package that it calls "mesa-dri-ati" and that it describes
>>>
>>>as "Mesa DRI drivers for AMD/ATI Radeon and mach64 (include Rage128)".
>>>
>>>
>>>
>>>My system reports that I have that package installed and that one of the files in
>>>
>>>the package is called mach64_dri.so.
>>>
>>>
>>>
>>>If I load that driver, will that overcome my problem? If yes, how do I do that,
>>>
>>>by editing xorg.conf in some way?
>>>
>>>
>>>
>>>(I should add that I just tried to load it using modprobe, but that didn't work.
>>>
>>>Sorry, I'm not too good at these things!)
>>>
>>>
>>>
>>>Thanks again,
>>>
>>>
>>>Leslie
>>>--------------------------------------------------
>>>To see papers written by me on, among oth...On Wed Aug  4 14:22 , Alex Deucher
>>  sent:
>>>
>>>
>>>>On Tue, Aug 3, 2010 at 11:45 PM, lesliek at ozemail.com.au
>>>>lesliek at ozemail.com.au> wrote:
>>>
>>>>> I'm usi...
>>
>>
>>