Page 14 of 26 FirstFirst ... 4121314151624 ... LastLast
Results 131 to 140 of 256

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

  1. #131
    Join Date
    Feb 2007
    Location
    New Zealand
    Beans
    11
    Distro
    Ubuntu 7.04 Feisty Fawn

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

    audiophyl is awesome. After trying no fewer than four separate HOWTOs online for this very problem, I ran through his guide without a hitch and now have both direct rendering and OpenGL functionality on my Rage Mobility card for this Compaq Armada E500, a problem I had thought was insoluble.

    glxgears gives me a framerate of more than six times what I had previously, and the OpenGL screensavers I've tested look gorgeous. I'm now about to install Quake II in order to play it as God intended it.

    Thank you very much audiophyl, it's folks like you that make the free software community great.

  2. #132
    Join Date
    Apr 2006
    Beans
    Hidden!

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

    drwxr-xr-x 2 root root 1024 2007-05-08 16:53 .
    drwxr-xr-x 11 root root 1024 2007-05-07 13:14 ..
    -rw-r--r-- 1 root root 3194321 2007-05-20 12:15 drm.ko
    -rw-r--r-- 1 root root 24580 2007-04-15 10:07 i810.ko
    -rw-r--r-- 1 root root 30544 2007-04-15 10:07 i830.ko
    -rw-r--r-- 1 root root 29884 2007-04-15 10:07 i915.ko
    -rw-r--r-- 1 root root 584550 2007-05-20 12:15 mach64.ko
    -rw-r--r-- 1 root root 69512 2007-04-15 10:07 mga.ko
    -rw-r--r-- 1 root root 127016 2007-04-15 10:07 radeon.ko
    -rw-r--r-- 1 root root 39868 2007-04-15 10:07 savage.ko
    -rw-r--r-- 1 root root 11004 2007-04-15 10:07 sis.ko
    -rw-r--r-- 1 root root 5564 2007-04-15 10:07 tdfx.ko
    -rw-r--r-- 1 root root 48840 2007-04-15 10:07 via.ko

    but dmesg still gives me : [drm] Initialized drm 1.1.0 20060810

  3. #133
    Join Date
    May 2007
    Beans
    3

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

    I have followed the guide by audiophyl and compiled the mach64 and drm modules and loaded them, but glxinfo still reports no for direct rendering. I have changed my xorg config default color to 16 bit but that still does not help. I'm using feisty with kernel 2.6.20-15. I just don't understand how lsmod can show the modules that i compiled as being loaded but glxinfo still indicates no direct rendering.

  4. #134
    Join Date
    Apr 2007
    Beans
    2

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

    Hi, first of all: sorry for my bad english

    This solution works for me, very easy:

    1. Aply Ally_S patch on mach64 driver: http://ubuntuforums.org/showpost.php...0&postcount=63

    2. Delete this line in file /mach64-20060403-linux.i386/drm/linux-core/drm_stub.c:51:

    module_param_named(debug, drm_debug, int, S_IRUGO|S_IWUGO);

    3. Remove all linux/config.h reference in every file that give us a compilation error.

    Thats all... this works for me with the initial method.

    If any error at restart (like "ati driver not found"), just reinstall xserver-xorg-video-ati package and restart again.


    Found it here: https://bugs.launchpad.net/ubuntu/+s....15/+bug/34590

    Hope this helps someone
    Last edited by swangsongforyou; May 23rd, 2007 at 03:17 PM.

  5. #135
    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)

    Tyr Norian: Many thanks for the kind words. Nice Sinfest avatar, too. Are you using 6.10 as your details show, or are you using 7.04? Quake II was my main motivation for figuring this all out, honestly. Once I got everything working, I discovered that Return to Castle Wolfenstein works, as well... It never did in Windows!

    redrum: I should've checked this the first time around, but your version number is right. Use this command and let me know what the output is -
    Code:
    dmesg | grep mach64
    spieslikeus: It's possible for the kernel modules to load (which lsmod will show) without the X.org modules loading. Check the contents of /var/log/Xorg.0.log for any errors pertaining to mach64 or drm. Hopefully we can find something there!

    -Philip

  6. #136
    Join Date
    May 2007
    Beans
    3

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

    Hi audiophyl, thanks for responding... here are some relevant lines from my Xorg.0.log file...
    Note that there are no errors in the file, only warnings as follows...this particular log was generated with the laptop in its docking station, but no direct rendering either way. I am open to any and all suggestions, thanks in advace

    (**) |-->Screen "Default Screen" (0)
    (**) | |-->Monitor "Generic Monitor"
    (**) | |-->Device "ATI Technologies Inc Rage Mobility P/M AGP 2x"
    ...
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: Open failed
    drmOpenByBusid: Searching for BusID pci:0000:01:00.0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 7, (OK)
    drmOpenByBusid: drmOpenMinor returns 7
    drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
    (II) ATI(0): [drm] loaded kernel module for "mach64" driver
    (II) ATI(0): [drm] DRM interface version 1.3
    (II) ATI(0): [drm] created "mach64" driver at busid "pci:0000:01:00.0"
    (II) ATI(0): [drm] added 8192 byte SAREA at 0xe4c40000
    (II) ATI(0): [drm] mapped SAREA 0xe4c40000 to 0xb724b000
    (II) ATI(0): [drm] framebuffer handle = 0x40000000
    (II) ATI(0): [drm] added 1 reserved context for kernel
    (II) ATI(0): [drm] Will request asynchronous DMA mode
    (==) ATI(0): [agp] Using AGP 2x Mode
    (==) ATI(0): [agp] Using 8 MB AGP aperture
    (II) ATI(0): [agp] Mode 0x1f000203 [AGP 0x8086/0x7190; Card 0x1002/0x4c4d]
    (II) ATI(0): [agp] 8192 kB allocated with handle 0x00000001
    (II) ATI(0): [agp] Using 16 kB for DMA descriptor ring
    (==) ATI(0): [drm] Using 2 MB for DMA buffers
    (II) ATI(0): [agp] Using 6016 kB for AGP textures
    (II) ATI(0): [agp] ring handle = 0x50000000
    (II) ATI(0): [agp] Ring mapped at 0xb7247000
    (II) ATI(0): [agp] vertex buffers handle = 0x50004000
    (II) ATI(0): [agp] Vertex buffers mapped at 0xb7047000
    (II) ATI(0): [agp] AGP texture region handle = 0x50204000
    (II) ATI(0): [agp] AGP Texture region mapped at 0xb6a67000
    (II) ATI(0): [drm] register handle = 0x41000000
    (II) ATI(0): [dri] Visual configs initialized
    (II) ATI(0): [dri] Block 0 base at 0x41000400
    (II) ATI(0): Memory manager initialized to (0,0) (1024,2047)
    (II) ATI(0): Largest offscreen area available: 1024 x 1279
    (II) ATI(0): Will use 511 kB of offscreen memory for XAA
    (II) ATI(0): Will use back buffer at offset 0x37f000
    (II) ATI(0): Will use depth buffer at offset 0x67f000
    (II) ATI(0): Using XFree86 Acceleration Architecture (XAA)
    Screen to screen bit blits
    Solid filled rectangles
    8x8 mono pattern filled rectangles
    Indirect CPU to Screen color expansion
    Solid Lines
    Offscreen Pixmaps
    Setting up tile and stipple cache:
    32 128x128 slots
    10 256x256 slots
    (==) ATI(0): Backing store disabled
    (==) ATI(0): Silken mouse enabled
    (II) ATI(0): X context handle = 0x1
    (II) ATI(0): [drm] installed DRM signal handler
    (II) ATI(0): [DRI] installation complete
    (II) ATI(0): [drm] Added 128 16384 byte DMA buffers
    (II) ATI(0): [drm] Mapped 128 DMA buffers at 0xb6867000
    (II) ATI(0): [drm] Installed interrupt handler, using IRQ 11
    (II) ATI(0): Direct rendering enabled
    (==) RandR enabled
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-APPGROUP
    (II) Initializing built-in extension XAccessControlExtension
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension XFree86-Bigfont
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) Initializing built-in extension XEVIE
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 8, (OK)
    drmOpenByBusid: Searching for BusID pci:0000:01:00.0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 8, (OK)
    drmOpenByBusid: drmOpenMinor returns 8
    drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
    (WW) AIGLX: 3D driver claims to not support visual 0x23
    (WW) AIGLX: 3D driver claims to not support visual 0x24
    (WW) AIGLX: 3D driver claims to not support visual 0x25
    (WW) AIGLX: 3D driver claims to not support visual 0x26
    (WW) AIGLX: 3D driver claims to not support visual 0x27
    (WW) AIGLX: 3D driver claims to not support visual 0x28
    (WW) AIGLX: 3D driver claims to not support visual 0x29
    (WW) AIGLX: 3D driver claims to not support visual 0x2a
    (WW) AIGLX: 3D driver claims to not support visual 0x2b
    (WW) AIGLX: 3D driver claims to not support visual 0x2c
    (WW) AIGLX: 3D driver claims to not support visual 0x2d
    (WW) AIGLX: 3D driver claims to not support visual 0x2e
    (WW) AIGLX: 3D driver claims to not support visual 0x2f
    (WW) AIGLX: 3D driver claims to not support visual 0x30
    (WW) AIGLX: 3D driver claims to not support visual 0x31
    (WW) AIGLX: 3D driver claims to not support visual 0x32
    (II) AIGLX: Loaded and initialized /usr/lib/dri/mach64_dri.so
    (II) GLX: Initialized DRI GL provider for screen 0

  7. #137
    Join Date
    Feb 2007
    Location
    New Zealand
    Beans
    11
    Distro
    Ubuntu 7.04 Feisty Fawn

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

    Quote Originally Posted by audiophyl View Post
    ... Are you using 6.10 as your details show, or are you using 7.04?
    I'm using 7.04. I forgot to change my profile after I upgraded.

  8. #138
    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)

    spieslikeus:

    Here is what my /etc/X11/xorg.conf looks like (just the pertinent spots, though):

    ...
    Section "Module"
    Load "i2c"
    Load "bitmap"
    Load "ddc"
    Load "dri"
    Load "extmod"
    Load "freetype"
    Load "glx"
    Load "int10"
    Load "type1"
    Load "vbe"
    EndSection
    ...
    //this is at the very bottom
    Section "DRI"
    Mode 0666
    EndSection

    -Philip

  9. #139
    Join Date
    May 2007
    Location
    Goettingen, Germany
    Beans
    2
    Distro
    Ubuntu 7.04 Feisty Fawn

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

    First of all: Thanks for the excellent tutorial audiophyl! Helped me a lot!

    spieslikeus: Had the same problem. Take a look at http://dri.freedesktop.org/wiki/DriTroubleshooting
    I found out what was wrong when I tried:

    export LIBGL_DEBUG=verbose
    glxinfo

    It told me that the library /usr/X11R6/lib/modules/dri/mach64_dri.so couldn't be found. I made a link to the /usl/lib directory:

    cd /usr/X11R6/lib
    ln -s /usr/lib modules

    then glxinfo said Direct Rendering: Yes.
    Still some games are really slow, but that might just be the card I have a Duron 700 and the ATI Rage XL AGP 2X (aka Xpert 98 RXL AGP 2X) with 16MB VRAM here. What framerates should I expect from glxgears in 32bit? I get ~100fps...
    The driver is identified as: " Mesa DRI Mach64 [Rage Pro] 20051019 AGP 2x x86/MMX+/3DNow!+" which seems pretty old to me...

    hope it helps...
    Last edited by rarefluid; May 26th, 2007 at 12:09 AM.

  10. #140
    Join Date
    May 2007
    Beans
    3

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

    "spieslikeus: Had the same problem. Take a look at http://dri.freedesktop.org/wiki/DriTroubleshooting
    I found out what was wrong when I tried:

    export LIBGL_DEBUG=verbose
    glxinfo

    It told me that the library /usr/X11R6/lib/modules/dri/mach64_dri.so couldn't be found."

    Yes yes this is what I get too thanks rarefluid!

    I did:

    cd /usr/X11R6/lib/modules/dri
    sudo ln -s /usr/lib/dri/mach64_dri.so mach64_dri.so

    "then glxinfo said Direct Rendering: Yes."

    Now running glxgears gives:

    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 glIsTextures!
    libGL warning: 3D driver claims to not support visual 0x4b

    And I get 183 fps with my shiny old Rage Mobility P/M AGP 2x (rev 64)

    Any ideas on these errors guys?
    Thanks again audiophyl and rarefluid!

Page 14 of 26 FirstFirst ... 4121314151624 ... 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
  •