| View previous topic :: View next topic |
| Author |
Message |
W3BMAST3R101
Apprentice
Joined: 19 Jun 2004
Posts: 197
|
 Posted: Tue Jul 25, 2006 6:07 am Post subject: ATI Rage XL |
 |
|
Hey. I'm trying to install gentoo on a slightly older box with a "VGA compatible controller: ATITechnologies Inc Rage XL AGP 2x (rev 27)" I can get 3d accel to work in 2 live cds, but they don't make it clear as to what module they use and the cds are about 3 years old. So i'm uncertain how to get 3d accel to work. Should i use stuff that is just in the kernel? And if so what should i use? Or should i use X11-drm. I tried to follow the howto, but basically i'm uncertain what module this would fall under. If some one could help me out with this i should be able to carry on from there.
thnx,
the w3b |
|
| Back to top |
|
 |
sugar
Guru
Joined: 07 Aug 2004
Posts: 579
Location: Morrinsville, New Zealand
|
| Posted: Tue Jul 25, 2006 10:19 am Post subject: |
|
|
I've got a rage. I'll make this quick as I have to go to bed soon. Some of this may be obsolete.
Don't enable the direct rendering manager in the kernel, so
| Quote: | | < > Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) |
the vesa framebuffer works fine, although I couldn't get the mach64 framebuffer working. If you want a framebuffer console, then thats another story. Also, make sure that agpgart is enabled with the correct hardware.
I have the following use flags and a VIDEO_CARDS line in my make.conf file
| Quote: |
USE="win32codecs insecure-drivers mp3 video_cards_mach64"
VIDEO_CARDS="vesa fbdev mach64" |
so, when I run emerge -vp x11-drm, I get the following.
| Quote: | mark linux # emerge -vp x11-drm
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] x11-base/x11-drm-20060608 VIDEO_CARDS="mach64 -i810 -mga -nv -r128 -radeon -savage -sis -tdfx -via" 556 kB
Total size of downloads: 556 kB
|
the mach64 and drm modules are also set to load on boot in the /etc/modules.autoload.d/kernel-2.6 file. after you compile x11-drm you should beable to start both of these modules.
hope this helps! |
|
| Back to top |
|
|
W3BMAST3R101
Apprentice
Joined: 19 Jun 2004
Posts: 197
|
| Posted: Tue Jul 25, 2006 7:52 pm Post subject: |
|
|
Could you also show me what your xorg.conf shows? I should be able to get the rest from there hopefully. Thanks alot dude you've saved me a lot of time so far. I had been looking for about 4 hours for info on the card.
the w3b |
|
| Back to top |
|
|
sugar
Guru
Joined: 07 Aug 2004
Posts: 579
Location: Morrinsville, New Zealand
|
| Posted: Wed Jul 26, 2006 5:17 am Post subject: |
|
|
| Quote: | # File generated by xorgconfig.
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
#Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"
EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "My Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 30-50
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-100
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "ATI Mach64 3D Rage Pro"
Driver "ati"
#VideoRam 8192
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "ATI Mach64 3D Rage Pro"
Monitor "My Monitor"
DefaultDepth 16
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "DRI"
Mode 0666
Group "video"
EndSection
#Section "Extensions"
# Option "Composite" "true"
#EndSection
|
I've taken out the totally irrelevant parts. The really important parts are the Section "Dri" at the end, the Section "Device", and the Section "Module" (ie Load Dri and Glx) |
|
| Back to top |
|
|
nextgen
Tux's lil' helper
Joined: 17 Jun 2004
Posts: 107
Location: Montreal, Quebec, Canada
|
| Posted: Wed Nov 15, 2006 10:44 pm Post subject: |
|
|
Can you guys get dri to work with your setting? I can't! 
| Code: | $ glxinfo | grep rendering
direct rendering: No |
If dri is working for you, that'll revive my hope. |
|
| Back to top |
|
|
W3BMAST3R101
Apprentice
Joined: 19 Jun 2004
Posts: 197
|
| Posted: Sat Nov 18, 2006 1:02 am Post subject: |
|
|
| I've just got DRI working on my laptop with a ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) |
|
| Back to top |
|
|
nextgen
Tux's lil' helper
Joined: 17 Jun 2004
Posts: 107
Location: Montreal, Quebec, Canada
|
| Posted: Sun Nov 19, 2006 7:21 pm Post subject: DRI with mach64 |
|
|
This does revive my hopes! Are you using an unsupported "mach64" driver?
What versions are you running for:
- kernel: (I'm running 2.6.18-gentoo-r2)
- xorg-x11: (I'm running 7.1)
I have these lines in my make.conf file:
| Code: | INPUT_DEVICES="keyboard mouse"
VIDEO_CARDS="mach64 vesa vga fbdev v4l" |
Can you please tell me what you did to get DRI to work with mach64?
I thought I was gonna make it work when I found this Ubuntu thread which seems to have worked for some, but no luck in the end...
http://www.ubuntuforums.org/showthread.php?t=7200
Regards, |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
