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

lesliek at ozemail.com.au lesliek at ozemail.com.au
Tue Aug 3 21:40:37 PDT 2010


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 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: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 using Slitaz v 3 and a mach64 driver obtained from the Slitaz repositories.
>>
>> In my Xorg.0.log, I find the following lines:
>>
>> (II) MACH64(0): [drm] SAREA 2200+1208: 3408
>> drmOpenDevice: node name is /dev/dri/card0
>> drmOpenDevice: open result is -1, (No such device)
>> drmOpenDevice: open result is -1, (No such device)
>> drmOpenDevice: Open failed
>> drmOpenDevice: node name is /dev/dri/card0
>> drmOpenDevice: open result is -1, (No such device)
>> drmOpenDevice: open result is -1, (No such device)
>> drmOpenDevice: Open failed
>> [drm] failed to load kernel module "mach64"
>> (EE) [drm] drmOpen failed.
>> (EE) MACH64(0): [dri] DRIScreenInit Failed
>>
>> With regard to much of those lines, I do have a directory called /dev/dri, but
>> it's empty. Something I read suggested that card0 would be added to that
>> directory by the loading of the drm module. In my case, the drm module loads
>> automatically on boot-up, but that doesn't seem to create the card0 file that's
>> being looked for.
>>
>> Is there something more I should be doing to overcome the two errors listed?
>
>You need to have the mach64 drm installed.  I'm not sure it was ever
>merged into the upstream kernel.
>
>Alex





More information about the xorg mailing list