Page 11 of 26 FirstFirst ... 91011121321 ... LastLast
Results 101 to 110 of 256

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

  1. #101
    Join Date
    Dec 2006
    Beans
    38
    Distro
    Ubuntu 7.10 Gutsy Gibbon

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

    Quote Originally Posted by Dominicus View Post
    Well this was short-lived...just upgraded to the new Kernel linux-generic-17-11 and mach64 won't compile anymore, even with Ally_S's modified ati_pcigart.c

    It was good while it lasted. Dominipater.
    Well, it does compile for me with Ally_S's ati_pciart.c on a fresh generic-17-11 edgy..

    The joy was short-lived as I soon discovered the LT Rage Pro in my compaq m300 notebook has only 4mb memory
    Quote Originally Posted by mrgamer View Post
    hi everyone, i've an old laptop Dell L400 with a mach64 onboard with 4MB of ram

    [..]

    the only way i succeeded to run direct rendering with the above HOWTO is @ 800x600

    so the main problem is 1024*768*3*1 = more than mine 4MBs of onboard ram!

    that means i will never get the direct rendering with a resolution of 1024x768 (that's also the "default" lcd resolution....)?
    I guess. For 1024x768 with 4mb to work DRI should be able to do 13 bit or lower . Btw, wether I set xorg.conf to 15,16 or 24 bit I get artifacts, you? Guess also cause of memory shortage, but I don't remember having this problem in windows.
    Last edited by Sebastral; February 20th, 2007 at 02:13 PM.

  2. #102
    Join Date
    Apr 2007
    Location
    North Dakota, USA
    Beans
    Hidden!
    Distro
    Ubuntu 7.04 Feisty Fawn

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

    The process detailed in this tutorial is for an old version of X.org. I have successfully enable DRI with my ATI Rage Mobility M1 in 7.04 Feisty Fawn (X.org 7.2). The steps are a bit involved, but it's all quite nicely documented on xorg.freedesktop.org. Also, it's entirely possible that there is an easier way to grab the necessary sources than via GIT, but this way you will have the newest ATI driver.

    NOTE: I have not tried this on anything other than 7.04! Follow these steps at your own risk with earlier versions of Ubuntu.

    EDIT: After the Ubuntu upgrade to 2.6.20-14, I downloaded everything again and tried to duplicate the process with these instructions with one hitch. The source for /tmp/working/drm/linux-core/drm_compat.c needs to have the vm_insert_pfn() function block-commented out. This is kind of a pain in the butt way to go about doing things!

    SOURCES:
    Compiling Modular X.org Source
    Compiling DRI/DRM Support

    The rough steps are as follows:

    1. install the needed sources, headers, and software
    Code:
    sudo apt-get build-dep mesa
    sudo apt-get build-dep libdrm
    sudo apt-get install git-core autoconf automake libtool
    sudo apt-get install libxmu-headers libxmu-dev libxi-dev libdrm-dev libxfixes-dev libxdamage-dev mesa-common-dev
    sudo apt-get install xserver-xorg-dev
    2. install the latest source trees for drm and mesa in a new directory
    Code:
    mkdir /tmp/working
    cd /tmp/working
    wget 'http://xorg.freedesktop.org/wiki/ModularDevelopersGuide?action=AttachFile&do=get&target=git_xorg.sh' -O git_xorg.sh
    chmod a+x git_xorg.sh
    ./git_xorg.sh
    git clone git://anongit.freedesktop.org/git/mesa/mesa
    and finally, in the event that this doesn't download the 'drm' folder:
    Code:
    git clone git://anongit.freedesktop.org/git/mesa/drm
    3. prepare the build directory
    Code:
    mkdir /tmp/build-dir
    mkdir /tmp/build-dir/mesalibs
    mkdir /tmp/build-dir/drm
    4. prepare to build the new ati driver
    sometimes running 'make' during steps 3 and 4 will result in a 'nothing to make' message. don't panic! the documentation for the build states this is normal and to run the 'make' instruction prior to a 'make install' regardless.
    Code:
    cd /tmp/working/util/macros
    ./autogen.sh --prefix=/tmp/build-dir
    make
    make install
    export PKG_CONFIG_PATH=/tmp/build-dir/lib/pkgconfig
    export ACLOCAL="aclocal -I /tmp/build-dir/share/aclocal"
    5. build the necessary protos for the driver build step
    Code:
    cd /tmp/working/proto/fontsproto
    ./autogen.sh --prefix=/tmp/build-dir
    make
    make install
    cd /tmp/working/proto/xineramaproto
    ./autogen.sh --prefix=/tmp/build-dir
    make
    make install
    cd /tmp/working/proto/xf86miscproto
    ./autogen.sh --prefix=/tmp/build-dir
    make
    make install
    cd /tmp/working/proto/xf86driproto
    ./autogen.sh --prefix=/tmp/build-dir
    make
    make install
    cd /tmp/working/proto/randrproto
    ./autogen.sh --prefix=/tmp/build-dir
    make
    make install
    cd /tmp/working/proto/randerproto
    ./autogen.sh --prefix=/tmp/build-dir
    make
    make install
    cd /tmp/working/proto/videoproto
    ./autogen.sh --prefix=/tmp/build-dir
    make
    make install
    6. build the new ati driver
    Code:
    cd /tmp/working/driver/xf86-video-ati
    ./autogen.sh --prefix=/tmp/build-dir
    make
    make install
    7. build dri in the mesa tree (use make linux-dri-x86 for x86-specific optimizations)
    Code:
    cd /tmp/working/mesa
    nano configs/linux-dri
    //locate the line that begins 'DRI_DIRS = ....' (near the bottom) and edit it to be 'DRI_DIRS = mach64'
    //this will build only the DRI module that you need
    make linux-dri
    cp -P /tmp/working/mesa/lib/* /tmp/build-dir/mesalibs
    8. build drm NOTE: if you see "error: previous declaration of ‘vm_insert_pfn’ was here", you will need to comment out the function "vm_insert_pfn" in drm_compat.c and run make again.
    Code:
    cd /tmp/working/drm/linux-core
    make mach64.o
    cp *.ko /tmp/build-dir/drm
    9. make backups of files from the following locations:
    /lib/modules/$KERNEL/kernel/drivers/char/drm/ (make a backup of drm.ko)
    /usr/lib/xorg/modules/drivers/ (at least backup ati_drv.so, atimisc_drv.so, r128_drv.so, and radeon_drv.so)
    /usr/lib/dri/ (backup everything)

    10. install everything (the last command will cause X to quit, and it will come back using the new driver... but you'll still need to reboot for DRI to load)
    Code:
    sudo cp -P /tmp/build-dir/mesalibs/* /usr/lib/dri/
    sudo cp /tmp/build-dir/drm/* /lib/modules/$KERNEL/kernel/drivers/char/drm/
    sudo depmod -a
    sudo cp /tmp/build-dir/lib/xorg/modules/drivers/* /usr/lib/xorg/modules/drivers/
    11. reboot and check glxinfo. if X won't work, at least you made backups in step 9. you DID do that, didn't you?
    Last edited by audiophyl; May 30th, 2007 at 10:06 PM. Reason: don't download the protos we need, make them.

  3. #103
    Join Date
    Apr 2007
    Beans
    2

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

    when I'm doing ./autogen.sh --prefix=/tmp/build-dir , I get an error like this:
    ./configure: line 20021: syntax error near unexpected token 'XINERAMA,'
    ./configure: line 20021: 'XORG_DRIVER_CHECK_EXT(XINERAMA, xineramaproto)'

    And it won't create Makefile, so I cannot continue. Could someone help me?

  4. #104
    Join Date
    Apr 2007
    Location
    North Dakota, USA
    Beans
    Hidden!
    Distro
    Ubuntu 7.04 Feisty Fawn

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

    i did some searching regarding your error, and came across something related to libdrm needing to be rebuilt, as well. give this a shot:

    Code:
    cd /tmp/working/drm
    ./autogen.sh
    ./configure --prefix=/tmp/build-dir
    make install
    this will create libdrm files in /tmp/build-dir/lib/, and these will need to be copied into your /usr/lib folder using the following command:

    Code:
    cd /tmp/build-dir/lib/
    cp -P libdrm* /usr/lib/
    after you've done this, back up in the build process to step 4. hope this works out for you! i may need to add this to the instructions...

    -philip

    p.s. - another possibility is that the source was broken at the time that you downloaded it... in which case you can just run ./git_xorg.sh again and it will only download updates to the source.
    Last edited by audiophyl; April 20th, 2007 at 08:27 PM. Reason: mistake in code

  5. #105
    Join Date
    Dec 2006
    Beans
    Hidden!

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

    I too am getting the 'syntax error near unexpected token' message after trying to run the autogen.sh for the ati driver (step 6). I thought it was a problem with XINERAMA so I tried commenting out that line to no avail; the error message just comes up with the next line.

    If this is indeed faulty code, what would be a way to get older sources?

  6. #106
    Join Date
    Apr 2007
    Location
    North Dakota, USA
    Beans
    Hidden!
    Distro
    Ubuntu 7.04 Feisty Fawn

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

    Out of curiosity, do you have the file /usr/include/xorg/xorg-server.h in your installation?

    There was an omission in Step 1, as I had previously installed xserver-xorg-dev for a different reason... It didn't even cross my mind that this would depend on it, as well.

    Code:
    sudo apt-get install xserver-xorg-dev
    This is now included in Step 1 above.
    Last edited by audiophyl; April 21st, 2007 at 10:10 PM. Reason: fixed

  7. #107
    Join Date
    Dec 2006
    Beans
    Hidden!

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

    Nope. There isn't even an xorg folder.

    Edit: got the xserver-xorg-dev package and now there is. Trying it all again now.

    Extra edit: turned out that I needed to download extra dev packages (randr, render and video) before it would go past step 5. I have completed all the steps but I still do not have DRI, according to GLXinfo.


    Edit 3: YES it works. Thank you, kind sir!
    Last edited by ppg; April 22nd, 2007 at 01:18 AM.

  8. #108
    Join Date
    Apr 2007
    Location
    North Dakota, USA
    Beans
    Hidden!
    Distro
    Ubuntu 7.04 Feisty Fawn

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

    Thank YOU for helping me locate the error in my instructions! I'm glad it works for you now.

    -Philip

  9. #109
    Join Date
    Apr 2007
    Beans
    12

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

    Well after hours of mucking around (I had tons of problems getting the modules to compile until I updated automake to ver 1.9), i got this working to a degree. I clearly have 3D accelleration working now, but missing things like some textures and transparency. in glxinfo I get 4 "DISPATCH ERROR!" Messages.
    DISPATCH ERROR! _glapi_add_dispatch failed to add glAreTexturesResident!
    DISPATCH ERROR! _glapi_add_dispatch failed to add glGenTextures!
    DISPATCH ERROR! _glapi_add_dispatch failed to add glIsTexture!
    DISPATCH ERROR! _glapi_add_dispatch failed to add glGetVertexAttribPointerv!
    followed by:
    libGL warning: 3D driver claims to not support visual 0x4b

    Any tweaks you could recommend? Thanks!
    (using a Dell Inspiron 3800 with integrated Mobility M1 with Xubuntu 6.10)

  10. #110
    Join Date
    Aug 2006
    Beans
    9

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

    Hi!!

    I am hanging on step seven: There is no directory /tmp/working/mesa

    Whats my mistake?

    Richie

Page 11 of 26 FirstFirst ... 91011121321 ... 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
  •