Page 9 of 26 FirstFirst ... 789101119 ... LastLast
Results 81 to 90 of 256

Thread: HOWTO: enable 3d acceleration w/ Rage Mobility (mach64)

  1. #81
    Join Date
    Dec 2006
    Beans
    5

    Re: HOWTO: enable 3d acceleration w/ Rage Mobility (mach64)

    It does not work for me. Here's a part of the log:

    Code:
    (II) ATI(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"
    (II) ATI(0): [drm] drmOpen failed
    (EE) ATI(0): [dri] DRIScreenInit Failed
    Here you can see the full Xorg.0.log:

    http://paste.ubuntu-nl.org/37353/

    I hope you can help me.

    greetz

  2. #82
    Join Date
    Dec 2006
    Beans
    1

    Re: HOWTO: enable 3d acceleration w/ Rage Mobility (mach64)

    Thanks!

    My card is
    ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
    Total Mem: 4096 kB

    It works with Edgy Eft Kernel 2.6.17-10 and the hacked Version @ Depth 16 Modes "800x600".

    $ glxgears -printfps
    456 frames in 6.1 seconds = 75.109 FPS -> 601 frames in 5.0 seconds = 120.161 FPS
    Last edited by sam2; December 17th, 2006 at 08:54 AM.

  3. #83
    Join Date
    Nov 2005
    Beans
    96

    Re: HOWTO: enable 3d acceleration w/ Rage Mobility (mach64)

    All was working fine up to today's update to kernel 2.6.20 (Feisty). I managed to compile the mach64 module a few days ago, but now it refuse to compile and the dri.log give me this:
    make DRM_MODULES=mach64.o modules
    make[1]: Entering directory `/home/mario/Download/Utils/mach64-20060403-linux.i
    make -C /lib/modules/2.6.20-2-generic/build SUBDIRS=`pwd` DRMSRCDIR=`pwd` modu
    make[2]: Entering directory `/usr/src/linux-headers-2.6.20-2-generic'
    CC [M] /home/mario/Download/Utils/mach64-20060403-linux.i386/drm/linux-core/
    /home/mario/Download/Utils/mach64-20060403-linux.i386/drm/linux-core/drm_stub.c
    make[3]: *** [/home/mario/Download/Utils/mach64-20060403-linux.i386/drm/linux-c
    make[2]: *** [_module_/home/mario/Download/Utils/mach64-20060403-linux.i386/drm
    make[2]: Leaving directory `/usr/src/linux-headers-2.6.20-2-generic'
    make[1]: *** [modules] Error 2
    make[1]: Leaving directory `/home/mario/Download/Utils/mach64-20060403-linux.i3
    make: *** [mach64.o] Error 2

    An this is the error message after ./install.sh:
    Compiling...
    ERROR: Kernel modules did not compile

    The DRI drivers can not be installed without the latest kernel modules.
    Installation will be aborted. See the dri.log file for information on
    what went wrong.

    Modules and headers (as well as the kernel-source and all the other development packages) are there...
    Some suggestion?

    Thanks!

  4. #84
    Join Date
    Nov 2005
    Location
    Where do I live
    Beans
    327

    Re: HOWTO: enable 3d acceleration w/ Rage Mobility (mach64)

    Well, I had to redo the whole process because of the new kernel, but it worked fine.
    Edit: including the modified ati_pcigart.c
    Code:
    glxinfo | grep direct
    libGL warning: 3D driver claims to not support visual 0x4b
    direct rendering: Yes
    Last edited by stalefries; February 1st, 2007 at 01:14 AM.

  5. #85
    Join Date
    Jun 2006
    Beans
    4

    Re: HOWTO: enable 3d acceleration w/ Rage Mobility (mach64)

    I don't know why I obtain next message in dri.log ...

    Code:
    make -C /lib/modules/2.6.19-gentoo-r1/source  SUBDIRS=`pwd` DRMSRCDIR=`pwd` modules
    make[2]: Entering directory `/usr/src/linux-2.6.19-gentoo-r1'
      CC [M]  /usr/src/mach64-20060403-linux.i386/drm/linux-core/drm_auth.o
    In file included from /usr/src/mach64-20060403-linux.i386/drm/linux-core/drm_auth.c:36:
    /usr/src/mach64-20060403-linux.i386/drm/linux-core/drmP.h:44:26: error: linux/config.h: No such file or directory
    make[3]: *** [/usr/src/mach64-20060403-linux.i386/drm/linux-core/drm_auth.o] Error 1
    make[2]: *** [_module_/usr/src/mach64-20060403-linux.i386/drm/linux-core] Error 2
    make[2]: Leaving directory `/usr/src/linux-2.6.19-gentoo-r1'
    make[1]: *** [modules] Error 2
    make[1]: Leaving directory `/usr/src/mach64-20060403-linux.i386/drm/linux-core'
    make: *** [mach64.o] Error 2

    Please, any help ???

    I'm in 2.6.19r1 kernel

  6. #86
    Join Date
    Dec 2006
    Beans
    Hidden!

    Re: HOWTO: enable 3d acceleration w/ Rage Mobility (mach64)

    It's dang obvious that mach64 is a sore point with Ubuntu. I've been trying to search for my own solution but no luck so far for me as well. I've tried using the binaries posted in the first post of this thread, the latest binaries available on the snapshots page (failing with the mysterious 'struct_page' error on the mach64 driver) and even attempted to build from CVS (since new snapshots are no longer being built and any issue with the kernel would not be resolved by using outdated code), all unsuccessfully.

    One of the main developers on the mach64 branch has stated that his laptop with the Rage Mobility chip has died and the project no longer affects him personally. It seems that it will be a cold day in hell before there will be a rewrite of the mach64 driver to fix the potential security issues and its eventual incorporation into the main Xorg source trees.

    It's frustrating and disenchanting to see this thread and its wiki version on 3dacceleration are the top hits on Google about getting DRI to work with a mach64-series card on Ubuntu. With close to 40 000 views of this thread, it's difficult to comprehend that there is no one out there with the technical expertise to make it work. If I knew how, I'd make it work.

    Yes, the Rage Mobility is an old graphics chip, but as evidenced from the search results, people still use it.

    So how the hell do you get DRI to work on Edgy Eft?!?

  7. #87
    Join Date
    Feb 2006
    Beans
    5

    Re: HOWTO: enable 3d acceleration w/ Rage Mobility (mach64)

    Quote Originally Posted by A2K View Post
    I have self-compiled kernel 2.6.18 and Xorg 7.1.1.
    Installed everything like in 1st post.

    Now when i start X-server, it writes to log:

    (II) Module ati: vendor="X.Org Foundation"
    compiled for 7.0.0, module version = 6.5.7
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 0.8
    (EE) module ABI major version (0) doesn't match the server's version (1)
    (II) UnloadModule: "ati"
    (II) Unloading /usr/lib/xorg/modules/drivers/ati_drv.so
    (EE) Failed to load module "ati" (module requirement mismatch, 0)

    does somebody know how to fix this?
    Messing around with the suggestions from this page (first post + installing xorg-dev and using the modified ati_pcigart.c), I got a similar fault. It can be fixed by reinstalling the xserver-xorg-video-ati package (I'm on Edgy).

    This can be done from the commandline as such
    Code:
     sudo dpkg --ignore-depends xserver-xorg-video-ati -r xserver-xorg-video-ati
    sudo apt-get install xserver-xorg-video-ati

    However I still get direct rendering: No from glxinfo.
    On the other hand the
    OpenGL renderer string: Mesa DRI Mach64 [Rage Pro] 20051019 AGP 2x further down says something's right. mach64 module is loaded and theres no errormessages regarding direct rendering in Xorg.0.log.

    oh, by the way, I had to make a symbolic link:
    Code:
    mkdir -p /home/felix/src/snapshots/inst/HEAD/lib/dri/
    cd /home/felix/src/snapshots/inst/HEAD/lib/dri/
    ln -s /usr/lib/dri/mach64_dri.so
    Otherwise AIGLX complained about not finding mach64_dri.so

    glxgears -iacknowledgethatthistoolisnotabenchmark goes from 150fps to 180-190 fps and the cpu utilisation is no longer dominated by user. So it works partly.

  8. #88
    Join Date
    Feb 2006
    Beans
    5

    Re: HOWTO: enable 3d acceleration w/ Rage Mobility (mach64)

    Quote Originally Posted by ppg View Post
    It seems that it will be a cold day in hell before there will be a rewrite of the mach64 driver to fix the potential security issues and its eventual incorporation into the main Xorg source trees.
    Maybe a complete rewrite is not nescessary, a lot of people seem not to worry about the potential security issues on their personal laptops. Of course the mach64 should not be enabled by default, but maybe it could be included into a nonsecure part, which is made available as a package "xserver-xorg-video-mach64-unsecure",

    Alternatively place mach64.ko so it need to be actively enabled (mach64.so placed in a directory where it can't be loaded, so that it would be a matter of a mv command to enable it?).

    Anyone with a working mach64 driver who knows how to build deb-packages?

    Otherwise great thread with good suggestions, I almost got it working myself.

  9. #89
    Join Date
    Aug 2006
    Location
    S/E Asia
    Beans
    11
    Distro
    Ubuntu

    Re: HOWTO: enable 3d acceleration w/ Rage Mobility (mach64)

    Worked for me! Cheers!!

    I had to reinstall libgl1-mesa-glx because of some earlier experiments (the error message was something like can't open libGL.so.1 or such)

    Thanks a lot!

    using googleearth still sucks, though, even if glxinfo tells me direct rendering is on
    I guess the mach64 series are a little outdated by now

  10. #90
    Join Date
    Nov 2006
    Location
    California, USA
    Beans
    43
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: HOWTO: enable 3d acceleration w/ Rage Mobility (mach64)

    How did you get this to work in Edgy? Are you using the 686 kernel?
    I haven't been able to get this to compile since get warning I need "latest" headers (which I do, but for the -generic kernel).

    Thx!Dominicus

Page 9 of 26 FirstFirst ... 789101119 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •