Difference between revisions of "Mach64"

From ArchWiki
Jump to: navigation, search
m (fix letter)
(37 intermediate revisions by 9 users not shown)
Line 1: Line 1:
This page is a walk through on obtaining Direct Rendering on a mach64 graphics chipset.
+
[[Category:Graphics]]
If you are looking for the ATI Rage 128, this is not the correct page.
+
[[Category:X Server]]
 +
[http://en.wikipedia.org/wiki/ATI_Mach#Mach_64 The Mach 64 chip] is an old graphic accelerator developped by ATI. This board has basic 3D capabilites. Its support on Linux is poor but exists. This page is a walkthrough to setup Mach 64 graphics chipsets (including ATI Rage Pro) and obtain direct rendering on some of them.
  
==The Mach 64 Board==
+
== Installing the basic features ==
The Mach64 Chip is made by ATI, coming in several varieties. This page is targeted at the Rage Pro variant, which to my knowledge is the only 3D version of the mach64.
+
[http://en.wikipedia.org/wiki/ATI_Rage Wikipedia: Mach64/Rage Pro]
+
This board has basic 3D capabilites, but Arch's xf86-video-mach64 package does not provide the complete solution.
+
  
Most GNU/Linux 3D graphics drivers use the DRI/DRM system for direct rendering, which is what the Mach64 Driver uses this.
+
2D and Xv acceleration in X can be achieved [[pacman|installing]] {{Pkg|xf86-video-mach64}} from the [[official repositories]].
  
==Packages and References==
+
== 3D acceleration and direct rendering ==
[http://dri.freedesktop.org/wiki/Building Reference Building DRI - Check this for link updates.]
+
*mesa - installs the mesa GL libs - Install this with pacman.
+
*libgl - installs the gl libs (part of the 'official' mesa source tree) (). - install this with pacman
+
*libdrm - installs the drm libs - install this with pacman
+
*xf86-video-mach64 - installs the dri files.
+
  
Terminology
+
{{Warning|You may experience crashes if using the Mach 64 DRM module. Direct rendering on Mach 64 is not very reliable because it never got much support.}}
*DRM - the kernel module that controls DMA, AGP memory management, resource locking, and secure hardware access.
+
On Linux, the Mach 64 chip uses the DRI/DRM system for direct rendering. The DRI part is available in the official repositories, but the DRM module is not included in the mainline kernel. So we have to build it separately. A package in the [[AUR]] simplifies this task: {{AUR|mach64drm}}.
*DRI - Direct Rendering Infrastructure - The X Server Driver. This allows the X server to communicate with the Graphics Card, translating OpenGL into instructions for the video card.
+
  
 +
As soon as the DRM module is built and installed, make sure you installed the DRI part {{Pkg|mach64-dri}}.
  
==Building the Kernel Drm Module - with makepkg goodness==
+
== Configuration ==
Since kernel 2.6.27, The in tree DRM is no longer compatible with the mach64 drm. The kernel '''must''' be compiled as follows:
+
  
Device Drivers --->
+
Here is an example of X configuration for a Mach 64 chip (may not be mandatory in all cases):
        Graphics Support --->
+
                    < > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)  --->  (CONFIG_DRM=n) Must be disabled.
+
 
+
If you are using the standard Arch kernel, you must either recompile the kernel or obtain the AUR package "kernel26-nodrm."
+
 
+
After your kernel is properly configured, install the AUR package "mach64drm," which will install the kernel modules compiled from out of tree DRI sources.
+
 
+
==Installing the other end: DRI==
+
The new Xorg (1.5.3) brought with it a new driver structure, which included a separate package for the mach64, giving users a mach64 package without having to recompile like with previous Xorg servers. (previously, xf86-video-ati had to be modified to compile mach64 when it was built).
+
 
+
This has made the process of installing DRI much easier, entailing:
+
 
+
pacman -S xf86-video-mach64
+
 
+
==xorg.conf==
+
This is what my the Device section in my xorg.conf looks like:
+
  
 
  Section "Device"
 
  Section "Device"
 
         Identifier  "Card0"
 
         Identifier  "Card0"
         Driver      "mach64" #most important, allows you to use the mach64 driver
+
         Driver      "mach64"
 
         Card        "ATI Rage Pro - Mach64"
 
         Card        "ATI Rage Pro - Mach64"
         Option "DMAMode" "async" #async - default, sync (synchronous DMA), mmio (PIO/MMIO) - Dispatch Buffers.
+
         Option "DMAMode" "async"
         Option "ForcePCIMode" "false" #Boolean, disables AGP aperture. Set to True if you have a PCI card.
+
         Option "ForcePCIMode" "false"
         Option "AgpMode" "2" #(AGP 1x or 2x) valid options: 1 or 2. If not set, defaults to agpgart's mode
+
         Option "AgpMode" "2"
         Option "AgpSize" "32" #Sets the AGP aperture in MB - The video card can access this amount of system memory using AGP and shared access in order to expand its memory capacity - enlarging this allows more textures to be stored here.
+
         Option "AgpSize" "32"
         Option "BufferSize" "2" #Sets DMA buffer memory size in MB. Default is 2 MB. May be 1 or 2.
+
         Option "BufferSize" "2"
         Option "LocalTextures" "true" #By default, AGP cards will only use AGP memory for textures. To force using local card memory for textures in addition to AGP, you may set this option to true. boolean.
+
        Option "LocalTextures" "true"
         #The AgpSize option changes the amount of system memory used for the AGP aperture and is not limited by the size of the card's on-board video memory. This memory is used for the DMA buffers (BufferSize option), and the remainder is allocated for AGP textures. Of course, the AgpMode/AgpSize options are ignored for PCI cards or if ForcePCIMode is enabled on an AGP card. However, the BufferSize option can be used to change the size of the DMA buffers in system memory for both PCI and AGP cards (but it's not recommended to reduce the buffer size unless you are short on system RAM). http://www.retinalburn.net/linux/dri_status.html
+
        # Uncomment the following option if X segfaults as soon as anything using acceleration is called.
         #see "Status and known issues for mach64 branch of DRI
+
         # Option "ExaNoComposite" "true"
 +
        # The following line will also prevent segmentation faults, but is not recommended since
 +
        # it will disable all acceleration.
 +
        # Option "NoAccel" "true"
 +
         # The following enables the shadow framebuffer, which improves non-accelerated performance.
 +
        # Use only with the "NoAccel" option.
 +
         # Option "ShadowFB" "true"
 
  EndSection
 
  EndSection
 +
 +
Details:
 +
* Driver: most important, allows you to use the mach64 driver.
 +
* DMAMode: async - default, sync (synchronous DMA), mmio (PIO/MMIO) - Dispatch Buffers.
 +
* ForcePCIMode: boolean, disables AGP aperture. Set to True if you have a PCI card.
 +
* AgpMode (AGP 1x or 2x): 1 or 2. If not set, defaults to agpgart's mode.
 +
* AgpSize: sets the AGP aperture in MB - The video card can access this amount of system memory using AGP and shared access in order to expand its memory capacity - enlarging this allows more textures to be stored here.
 +
* BufferSize: sets DMA buffer memory size in MB. Default is 2 MB. May be 1 or 2.
 +
* LocalTextures: boolean, by default, AGP cards will only use AGP memory for textures. To force using local card memory for textures in addition to AGP, you may set this option to true.
 +
The AgpSize option changes the amount of system memory used for the AGP aperture and is not limited by the size of the card's on-board video memory. This memory is used for the DMA buffers BufferSize option), and the remainder is allocated for AGP textures. Of course, the AgpMode/AgpSize options are ignored for PCI cards or if ForcePCIMode is enabled on an AGP card. However, the BufferSize option can be used to change the size of the DMA buffers in system memory for both PCI and AGP cards (but it's not recommended to reduce the buffer size unless you are short on system RAM).
 +
* ExaNoComposite - Required to prevent segmentation faults in EXA handler.
  
 
The Modules Section:
 
The Modules Section:
Line 68: Line 61:
 
         Mode 0666 #allows anybody to use DRI
 
         Mode 0666 #allows anybody to use DRI
 
  EndSection
 
  EndSection
 
  
 
The DRI Section (For machines where security is a concern):
 
The DRI Section (For machines where security is a concern):
  
 
  Section "DRI"
 
  Section "DRI"
         Group "video" #Change to any desired group to restrict access
+
         Group "video" #change to any desired group to restrict access
 
         Mode 0660
 
         Mode 0660
 
  EndSection
 
  EndSection
  
==Testing DRI==
+
== Testing direct rendering ==
After you're in X, you can run the command <code>glxinfo | egrep "direct rendering|OpenGL renderer"</code>
+
 
 +
Restart X. After you are in X, you can run the command:
 +
$ glxinfo | egrep "direct rendering|OpenGL renderer"
 
This should return something like this:
 
This should return something like this:
  direct rendering: Yes
+
  Direct rendering: Yes
 
  OpenGL renderer string: Mesa DRI Mach64 [Rage Pro] 20051019 AGP 2x x86/MMX/SSE
 
  OpenGL renderer string: Mesa DRI Mach64 [Rage Pro] 20051019 AGP 2x x86/MMX/SSE
  
If OpenGL renderer string says "Software Rasterizer," DRI is not working, even if direct rendering says "yes"
+
If OpenGL renderer string says "Software Rasterizer", DRI is not working, even if direct rendering says "yes".
 
+
==Building the Kernel Drm Module - the Old Way without pacman==
+
warning: this does not use the makepkg method, which is recommended. Please use the AUR packages (top of this document) or create your own.
+
Skip this section if you did the section above, with makepkg. Go to "Installing the other end: DRI."
+
 
+
The standard ARCH kernel doesn't come with the mach64 DRM module, so building yourself is required.
+
 
+
*Create a build folder to keep things tidy - this folder will be referred to from now on as $BUILDDIR
+
*Now, obtain the drm source tree:
+
git clone git://anongit.freedesktop.org/git/mesa/drm
+
*Get the thing compiled: (the drm folder appeared out of git)
+
cd $BUILDDIR/drm/linux-core/
+
make DRM_MODULES="mach64"
+
*Go get some coffee or something since your machine is probably very old to have a mach64 chipset and wait while everything compiles.
+
*When it's done compiling, there will be two files, <code>mach64.ko</code>, the device kernel module, and <code>drm.ko</code>, the DRM generic module.
+
*Copy those two files to the appropriate kernel modules directory. (Before doing this you may want to backup the exisiting files to somewhere else just in case).
+
sudo cp mach64.ko drm.ko /lib/modules/`uname -r`/kernel/drivers/char/drm/
+
*Now get the modules registered and depedencies generated.
+
sudo depmod -a `uname -r`
+

Revision as of 12:54, 24 May 2013

The Mach 64 chip is an old graphic accelerator developped by ATI. This board has basic 3D capabilites. Its support on Linux is poor but exists. This page is a walkthrough to setup Mach 64 graphics chipsets (including ATI Rage Pro) and obtain direct rendering on some of them.

Installing the basic features

2D and Xv acceleration in X can be achieved installing xf86-video-mach64 from the official repositories.

3D acceleration and direct rendering

Warning: You may experience crashes if using the Mach 64 DRM module. Direct rendering on Mach 64 is not very reliable because it never got much support.

On Linux, the Mach 64 chip uses the DRI/DRM system for direct rendering. The DRI part is available in the official repositories, but the DRM module is not included in the mainline kernel. So we have to build it separately. A package in the AUR simplifies this task: mach64drmAUR.

As soon as the DRM module is built and installed, make sure you installed the DRI part mach64-dri.

Configuration

Here is an example of X configuration for a Mach 64 chip (may not be mandatory in all cases):

Section "Device"
       Identifier  "Card0"
       Driver      "mach64"
       Card        "ATI Rage Pro - Mach64"
       Option "DMAMode" "async"
       Option "ForcePCIMode" "false"
       Option "AgpMode" "2"
       Option "AgpSize" "32"
       Option "BufferSize" "2"
       Option "LocalTextures" "true"
       # Uncomment the following option if X segfaults as soon as anything using acceleration is called.
       # Option "ExaNoComposite" "true"
       # The following line will also prevent segmentation faults, but is not recommended since
       # it will disable all acceleration.
       # Option "NoAccel" "true"
       # The following enables the shadow framebuffer, which improves non-accelerated performance.
       # Use only with the "NoAccel" option.
       # Option "ShadowFB" "true"
EndSection

Details:

  • Driver: most important, allows you to use the mach64 driver.
  • DMAMode: async - default, sync (synchronous DMA), mmio (PIO/MMIO) - Dispatch Buffers.
  • ForcePCIMode: boolean, disables AGP aperture. Set to True if you have a PCI card.
  • AgpMode (AGP 1x or 2x): 1 or 2. If not set, defaults to agpgart's mode.
  • AgpSize: sets the AGP aperture in MB - The video card can access this amount of system memory using AGP and shared access in order to expand its memory capacity - enlarging this allows more textures to be stored here.
  • BufferSize: sets DMA buffer memory size in MB. Default is 2 MB. May be 1 or 2.
  • LocalTextures: boolean, by default, AGP cards will only use AGP memory for textures. To force using local card memory for textures in addition to AGP, you may set this option to true.

The AgpSize option changes the amount of system memory used for the AGP aperture and is not limited by the size of the card's on-board video memory. This memory is used for the DMA buffers BufferSize option), and the remainder is allocated for AGP textures. Of course, the AgpMode/AgpSize options are ignored for PCI cards or if ForcePCIMode is enabled on an AGP card. However, the BufferSize option can be used to change the size of the DMA buffers in system memory for both PCI and AGP cards (but it's not recommended to reduce the buffer size unless you are short on system RAM).

  • ExaNoComposite - Required to prevent segmentation faults in EXA handler.

The Modules Section:

Section "Module"
       <Your modules>
       Load  "glx"
       Load  "dri"
EndSection

The DRI Section:

Section "DRI"
       Mode 0666 #allows anybody to use DRI
EndSection

The DRI Section (For machines where security is a concern):

Section "DRI"
       Group "video" #change to any desired group to restrict access
       Mode 0660
EndSection

Testing direct rendering

Restart X. After you are in X, you can run the command:

$ glxinfo | egrep "direct rendering|OpenGL renderer"

This should return something like this:

Direct rendering: Yes
OpenGL renderer string: Mesa DRI Mach64 [Rage Pro] 20051019 AGP 2x x86/MMX/SSE

If OpenGL renderer string says "Software Rasterizer", DRI is not working, even if direct rendering says "yes".