|
|
楼主 |
发表于 2004-4-12 01:00:46
|
显示全部楼层
http://www.alexandern.com/servle ... y&var.essayid=6
又找到一张好贴，几乎都说详尽了
不过是英文的，呵呵费点心。
ATI RADEON 3D driver installation on Linux
Essay explains how to get your ATI RADEON to play 3D OpenGL on your Linux box.
ATI RADEON 9700 PRO Made by ATI. (May not work for clones)
1. Get Driver
2. Installation
3. Mesa incompatibility
4. Configuration and XF86Config-4
5. Mouse wheel problem solution
I myself had tried to perform this installation many times without much luck until ATI at last released a working driver that many Linux users were waiting for. Though, as always there are some things that are not cool for all Linux users. For example ATI driver comes in RPM format. Many Linux users do not like RPM format since it is not supported on all Linux systems. I have a RedHat9 system that runs ATI 9700 Pro with this new driver, but if some one had made it run on a non RPM system I would be glad to know how it was done.
This procedure is for RedHat9 perhaps it is similar for Mandrake and SuSe. If you find any differences please let me know I will include it here and credit to you.
Updates:
Problems using ATI 9800 with 2.5 or 2.6 kernal
Based on some information I keep getting from people who read this HOW-TO I see that many have problems installing the driver on 2.6 kernal systems using ATI 9800. In many cases the card is not made by ATI.
Installing rpm on Debian
If you are running Debian you can install the rpm using the following command:
alien --to-deb fglrx-glc22-4.x.x-x.x.x.i386.rpm
dpkg -i --force-overwrite /path/to/fglrx-glc22-4.x.x-x.x.x.i386.deb
This was sent to me by Kostia. I am not including the email to prevent spammers from gathering it.
Thank you Kostia for the additional information.
(Mouse wheel problem solution is the last paragraph of this HOW-TO 
Installation procedure:
First
DOWNLAD THE ATI DRIVER
You need to go to ATI site and get the latest driver. So go here http://www.ati.com/support/driver.html and in the list boxes select:
Linux / Graphic Driver / Your RADEON ATI card
Get the driver for your XFree86 most likely you have 4.3.0 X11
Second
You need to make sure that you have the kernel sources installed on your machine so that the 3D module can be built for your kernel. Without kernel sources no cense in trying to install the driver since the installer will have to compile the module for your kernel at the end of RPM extraction.
Third
Backup your /etc/X11/XF86Config-4 file just in case. If you get no X after driver update you can restore your XF86Config-4 file and get back to X. (this tells the system to use the original driver that came with your distro)
Fourth
Know what refresh rate and resolution your monitor can support. Know your mouse and keyboard are.
Now proceed with the installation.
!WARNING!
DO NOT INSTALL THIS RPM IN INIT 5 RUNLEVEL! (desktop mode) SWITCH TO RUN LEVEL3 with init 3 command and then proceed. This is a common mistake that many do while performing the installation of a video driver. Installing in init 5 mode may cause your install to fail and your X to start.
Now that RPM is on your machine change to root (su and then password) and cd to the directory where you have placed the package. Run this command as root
rpm -Uhv --force fglrx-glc22-4.3.0-3.2.8.i586.rpm
Non RPM systems:
I have not tried it my self but this is a tip I got from Claudio Slva:
"...for Slackware there is a tool that converts RPM packages to .tgz (RPM2tgz). Next, just type installpkg fglrlxxxx.tgz. Run fglrxconfig..."
NOTE: that the rpm filename may change if by the time you actually get to do this the driver version changes.
Why --force? Well It will have a conflict with Mesa library. This package has it's own Mesa that is needed for ATI to run. The lib taints the GPL license on your current Mesa. If you are willing to live with a Mesa library that was patched with ATI nonpublic code go on and install.
Once the RPM does its magic and exits you will get a message stating that your 2D was enabled but that the 3D will not run since it failed to load the module. Do not panic! This is normal since the module has not been built yet. Before you will have a chance to do anything it will automatically go on to compiling your module. It will look around and it will find where your kernel sources are. It will then tell you the directory it thinks they are and will give you option to accept it by pressing Enter key or to type in an alternative location. If you have stock or updated installation of RedHat 9 it will find it just fine. Else you should know where you sources are. (On RedHat9 kernal sources are in /usr/src/linux-2.4)
The module will be built and the script will exit telling you to run fglrxconfig. Do it. This will configure your XF86Config-4 file.
Running fglrxconfig
Again this worked on my system, Some questions must be answered based on what your hardware is.
As root type:
fglrxconfig
Specify the mouse port type. Choose one from the following list:
2
Specify the mouse model. Choose one from the following list:
4
If your mouse has only two buttons, it is recommended that you enable
Emulate3Buttons.
n
Now give the full device name that the mouse is connected to, for example
/dev/tty00 or /dev/mouse or /dev/psaux (includes IBM Laptops).
/dev/mouse
Please select one of the following keyboard types that is the better
description of your keyboard. If nothing really matches,
choose 1 (Generic 101-key PC)
8
Please select the layout corresponding to your keyboard
1
Quad Buffer Stereo ("Active Stereo"):
This driver does support Quad Buffer Stereo ("Active Stereo")
in combination with a CRT monitor (refresh rate abt. 100 to 120 Hz)
and the appropiate stereo viewing subsystem hardware. This can be
e.g. a shutter glasses system (infrared or wired) or an active
polarisation device paired with passive stereo polarization glasses.
n
TV out Configuration
n
------------------------------------------------------------------------------
| Maximum resolution for OpenGL operation |
| |
| - R200 chip family (Radeon 8500-9100 Pro, FireGL 8700/8800/E1): |
| 2048x2048 |
| - R300 chip family (Radeon 9500-9700 Pro, FireGL T2/Z1/X1/X2): |
| 2560x2560 |
------------------------------------------------------------------------------
Choose configuration from the list below
1. Single Head (1 screen, second dark)
2. Laptop Mode (Ability to toggle between internal / external screen)
3. Clone Mode (2 screens - same content)
4. Big Desktop (2 screens - one framebuffer)
5. Dual Head (2 screens - two drivers)
1
==============================================================================
Monitor Settings
==============================================================================
Now we want to set the specifications of the monitor(s). The two critical
parameters are the vertical refresh rate, which is the rate at which the
the whole screen is refreshed, and most importantly the horizontal sync rate,
which is the rate at which scanlines are displayed.
The valid range for horizontal sync and vertical sync should be documented
in the manual of your monitor. If in doubt, check the monitor database
/usr/X11R6/lib/X11/doc/Monitors to see if your monitor is there.
Enter
You must indicate the horizontal sync range of your monitor. You can either
select one of the predefined ranges below that correspond to industry-
standard monitor types, or give a specific range.
It is VERY IMPORTANT that you do not specify a monitor type with a horizontal
sync range that is beyond the capabilities of your monitor. If in doubt,
choose a conservative setting.
hsync in kHz; monitor type with characteristic modes
1. 31.5 ; up to 640x480 @ 60 Hz (VGA)
2. 31.5 - 37.9; up to 800x600 @ 60 Hz (SVGA)
3. 31.5 - 48.4; up to 1024x768 @ 60 Hz (XGA)
4. 31.5 - 60.0; up to 1024x768 @ 75 Hz (XGA)
5. 31.5 - 68.7; up to 1024x768 @ 85 Hz (XGA)
6. 31.5 - 80.5; up to 1280x1024 @ 75 Hz (SXGA)
7. 31.5 - 91.1; up to 1280x1024 @ 85 Hz (SXGA)
8. Enter your own horizontal sync range
6
You must indicate the vertical sync range of your monitor. You can either
select one of the predefined ranges below or give a specific range.
1. 20 - 60 (e.g. slow scan flat panels with DVI cable)
2. 50 - 70 (VGA)
3. 60 - 75
4. 60 - 85
5. 60 - 100
6. Specify your own vertical sync range
4
The default resolution that the server will start-up with will be the first
listed mode that can be supported by the monitor and card.
Currently it is set to:
"640x480" for 24-bit
Modes that cannot be supported due to monitor or clock constraints will
be automatically skipped by the server.
1. Change the modes for 24-bit (24-bit color)
2. The modes are OK, continue.
1
Select your modes from the following list:
1 "640x480"
2 "800x600"
3 "1024x768"
4 "1152x864"
5 "1280x960"
6 "1280x1024"
7 "1400x1050"
8 "1600x1200"
9 "1792x1344"
Please list the digits and characters for the modes that you want to use.
For example, '632' selects "1280x1024" "1024x768" "800x600", with
the default mode of "1280x1024".
6
Modes that cannot be supported due to monitor or clock constraints will
be automatically skipped by the server.
1. Change the modes for 24-bit (24-bit color)
2. The modes are OK, continue.
2
Do you want to use a virtual desktop where the dimensions are bigger
n
Please specify which restriction sheme you want to implement:
1. no restrictions - any user has access to the OpenGL ICD
2. limited to group 'users' - only group members can access the OpenGL ICD
3. limited to group 'root' - only group members can access the OpenGL ICD
4. limited to group 'video' - only group members can access the OpenGL ICD
5. limited to group 'dri' - only group members can access the OpenGL ICD
1
==============================================================================
Application Profiles
==============================================================================
Please select application specific profile:
1. Default
2. Individual Configuration of Capabilities
3. Maya
4. SOFTIMAGE|XSI
5. SOFTIMAGE|3D
6. Houdini 4.0
7. Houdini 5.0
8. Houdini 5.5
1
Do you want to initialize xfree86-dga (y/n)? [n]
n
Do you want to export pseudo color visuals (y/n)? [n]
n
Do you want to synchronize buffer swaps
with the vertical sync signal (y/n)? [n]
n
Please select multi sample visuals you want to share:
1 = All (Visuals for 2,4 and 6 Samples per Pixel)
2 = Visuals for 2 Samples per Pixel
4 = Visuals for 4 Samples per Pixel
6 = Visuals for 6 Samples per Pixel
1
Do you want to force multi sample visuals
for every OpenGL application? (y/n)? [n]
n
Disable FSAA Gamma (y/n)? [n]
n
Customize FSAA Multi Sample Position (y/n)? [n]
n
Do you want to use the external AGP GART module (y/n)? [n]
n
Do you want to enable "AGP Locked User Pages" (y/n)? [y]
y (just in case you want to see logs)
0 - default (FireGL workstation boards: fast)
1 - fast operation (only for standard gnu C/C++ OpenGL applications)
2 - compatible operation (for WineX, VM emulators and some profilers)
Which storage method do you want to use? [0] 0
0
I am going to write the XF86Config-4 file now. Make sure you don't accidently
overwrite a previously configured one.
Shall I write it to '/etc/X11/XF86Config-4' (y/n)?
y
Or get my working XF86Config-4, (1600x1200 32bit ) but back up yours first, in case it does not work. Not sure but I think it is better to run the script then to use my config. You do have different hrdware after all.
When you are done with the script reboot.
You should now have 3D support. If you do not have 3D support then you have built your module against sources that are different from the kernal you are running. Or messed up something with the configuration script. You can run it again and try different values. I do not know what hardware you got...
The same would happen if you build the module and then update the kernal and boot to new kernal. If you did that you would have to re-run this procedure again to build the new module for the new kernal. Have your original XF86Config-4 backed somewhere safe so you can get in to X with default driver in case things do not workout the way they should.
Post-install possible mouse wheel problems
In some cases the mouse wheel stops working. To fix this open your /etc/X11/XF86Config-4, find Core Pointer's InputDevice section and under
Identifier "Mouse1"
add
Option "ZAxisMapping" "4 5"
Also my USB mouse was plugged in PS/2 thru an addupter. With the new driver I have to use the mouse in USB instead of PS/2. For some reason it would not take the USB to PS/2 mouse thing. Whatever really.
All Feedback is appritiated. Please use contact me link at the top menu if you wish to send your comments or suggestions.
© 2003 |
|
IP卡
狗仔卡
发表于 2004-4-12 00:25:19
显身卡