czy cytowany artykuł w sposób przejrzysty, "prosty" i zrozumiały przedstawia proces instalacji sterowników graficznych ATi oraz czy pozwolił na "bezbolesną" instalacje w/w sterowników ? |
TAK |
|
40% |
[2] |
NIE |
|
0% |
[0] |
CHCĘ PO POLSKU |
|
60% |
[3] |
|
Wszystkich Głosów : 5 |
|
Wysłano: Czwartek, 29 Stycznia 2004, 11:54 |
|
|
|
Witajcie ... znalazłem BARDZO ciekawy i doskonały dla początkujących artykuł dotyczący instalacji driverów od ATi dla Linuxa pod różnymi dystrybucjami i różnymi Kernelami ... w związku z tym ze ostatnio wiele ciekawych artów które znalazłem następnie gdzieś "znikła" pozwoliłem sobie skopiować i zacytować w/w artykuł, oto on:
źródło
ATI Linux How-To
Peter Gracar (who.knows@email.si)
v0.3.1, 12 January 2004
---------------------------------------------------------------------- ----------
This document describes how to install, configure, and maintain an ATI Graphics card on various Linux distributions.
---------------------------------------------------------------------- ----------
Contents
1 General HOWTO information
2 General Kernel configuration
3 AGPGart Kernel module install and setup
3.1 Getting the nForce drivers
3.2 Installing the nForce drivers
3.3 GART patch installation
3.4 Kernel configuration
4 Installing drivers on a ex-nVidia box
5 Installing ATI drivers on a RedHat Machine
5.1 Where to get the driver
5.2 Steps to take before installing the drivers
5.3 Installing the drivers
6 Installing ATI drivers on a Gentoo machine
6.1 Where to get the driver
6.2 Steps to take before installing the drivers
6.3 Installing the driver
6.4 Additional info/troubleshooting
7 Installing ATI drivers on a Slackware Machine
7.1 Where to get the driver
7.2 Steps to take before installing the drivers
7.3 Installing the driver
8 Installing the ATI drivers on a Mandrake machine
8.1 Where to get the driver
8.2 Steps to take before installing the drivers
8.3 Installing the drivers
9 Installing the ATI drivers on a SuSE machine
9.1 Where to get the driver
9.2 Steps to take before installing the drivers
9.3 Installing the drivers
10 Installing the drivers on a Debian machine
10.1 Where to get the driver
10.2 Steps to take before installing the drivers
10.3 Installing the drivers
11 Common steps for all distributions
11.1 Kernel 2.6 driver configuration
11.2 Building the module
11.3 Configuration of X Window
11.4 Fine tuning the installation
1 General HOWTO information
This HOWTO is divided into 2 main parts. In the first, there is information on how to enable 3D acceleration on nForce motherboards. Since a lot of users are having problems getting it to work, there are step-by-step instructions written there.
The second part is about the driver installation in most of the widely used distributions.
IMPORTANT!!!
For any of this to work, you have to have the kernel sources installed. RedHat (fedora), Mandrake and SuSE allow the user to install the sources using their package managers. Gentoo, Slackware and other similar distributions are built from the source, so they have it installed already.
It is very important, that you download the correct driver version. The 3 available choices are Xfree 4.1.0, 4.2.0 and 4.3.0. To find out which one to choose, run the Check.sh script, that comes with the ATI drivers.
sh check.sh (preform this in the directory to which you unpacked the ATI Driver zip archive.
You can also use the following command:
cat /var/log/XFree86.0.log | grep -i version | head
2 General Kernel configuration
This section applies to all distributions. It concerns the settings that must be enabled in the kernel for the driver to work. In this guide I will only look into the gfx specific settings, and completely ignore the other settings (IDE, eth...). For those you should look at your distributions kernel guide:
[Gentoo:]www.gentoo.org
[Slackware:]The guide you followed during the installation and kernel configuration
[Other:]Usualy there is a readme on kernel configuration found in the source directory (should be /usr/src/ )
First of all you should make sure your kernel sources are all set up. After you have them unpacked in /usr/src/your-kernel-sources you must make sure to link them to /usr/src/linux with the following command:
ln -s /usr/src/your-kernel-sources /usr/src/linux
If the linux link already exist you can remove it with the command:
rm /usr/src/linux
Once your sources are set up you should configure them. For this follow the specific distribution kernel guides, as each distribution requires their own settings to be enabled. Once you are done with setting up your kernel sources enter menuconfig again:
cd /usr/src/linux
make menuconfig
And enable the following options:
/dev/agpgart under ``character devices''
MTRR (Memory Type Range Register) under ``processor type and features''
Then disable:
Direct Rendering Manager (XFree86 DRI support) under ``character devices''
Once you have done this, exit the menuconfig (don't forget to save). After that run (as root in your /usr/src/linux folder):
make dep && make clean bzImage modules modules_install
With this command you will create a bzImage kernel file in your /usr/src/linux/arch/i386/boot/. The i386 part may change accordingly to your arch. Now you must copy the kernel image to /boot. (in some distros you will have to mount /boot first)
mount /boot # only do this if your /boot partition doesn't get mounted automaticaly
cp /usr/src/linux/arch/i386/boot/bzImage /boot/bzImage.new # change the bzImage.new to whatever you want your image to be named
After this you will have to edit your lilo/grub settings. For both it should be enough if you use the same data as for the already working kernel. The lilo conf file is in /etc/lilo.conf. After updating it you will have to run /sbin/lilo
/sbin/lilo
For grub you will have to edit /boot/grub/grub.conf. After the changes nothing else is needed.
3 AGPGart Kernel module install and setup
nForce users will have to enable the nVidia AGPGart module in their kernels, if they want the driver to support 3d acceleration. Newer kernels (2.4.22 and on) already support the nVidia specific AGPGart. For older kernels you will have to use a patch before being able to enable it.
3.1 Getting the nForce drivers
Go to http://www.nvidia.com/object/linux.html and select nForce drivers. Here you will be able to select the method of installation (and thus the package to download). If your distro is listed you should download the appropriate RPM. For others, simply download the tar.gz.
3.2 Installing the nForce drivers
Installing the drivers with the RPM is simple, just do this:
rpm -i nForce_driver.rpm
For the tar.gz package there is a little more to do:
cd /where/the/package/is/located
tar -xvzf nforce.tar.gz (substitute nforce with the package name)
cd nforce (substitute nforce with the package name)
make
su (become root)
make install
This should set almost everything up.
3.3 GART patch installation
This step has to be done by everybody, in order to enable nforce AGP Gart support in the kernel.
cd /usr/src/linux-2.4.20 (change this to your kernel path)
patch -p1 < linux-2.4.20-agpgart.diff (again, change to appropriate kernel)
3.4 Kernel configuration
First of all we must configure the kernel to support our new nForce AGP Gart.
cd /usr/src/linux-2.4.20
su (become root)
make menuconfig
In the 'Processor type and features', make sure that an x86 compatible CPU is selected.
In the 'Character devices' section, select '/dev/agpgart (AGP Support)' as a modularized kernel feature.
In the same section, enable 'NVIDIA chipset support'.
Now you can exit and save the config. Then you have to compile everything.
make dep && make clean bzImage modules modules_install
When the compilation is complete just copy the bzImage to /boot. If you already have a bzImage in /boot it is wise to back it up
cd /boot
mv bzImage bzImage.backup
cd /usr/src/linux-2.4.20/arch/i386/boot/
cp bzImage /boot/bzImage
With this copied you may need to either change your bootloader configuration, or just refresh your lilo parameters. When you boot into your new kernel, just install the ATI drivers normally (follow the guide for your distribution), with one exception. When, during the driver configuration, you are asked about the AGPGart, select the EXTERNAL AGPGART.
4 Installing drivers on a ex-nVidia box
nVidia's driver changes some files upon installation. To make sure that everything will work you MUST uninstall nVidia's driver first.
/path/to/nvidia/driver/driver.run -uninstall
This way everything will be returned to it's original value. From here on you can follow your distributions install instructions.
5 Installing ATI drivers on a RedHat Machine
5.1 Where to get the driver
The newest drivers can always be found at http://www.ati.com/support/driver.html.
5.2 Steps to take before installing the drivers
The first thing to do is to get the right driver version. In general RedHat 9.0 users have to get Xfree version 4.3.0 and RedHat 8.0 users must get the 4.2.0 Xfree version of the drivers. If you are unsure, or want to test it, you should use this file (http://www2.ati.com/drivers/Check.sh) to find out the right version for you (type sh Check.sh in the dir to which you downloaded the file). In some distributions it is possible to have a Xfree version, that doesn't match none of the driver versions (4.3.5 for example). In this case you should use the x.x.0 version of the driver (in the example this is version 4.3.0).
Once you know which Xfree version you need to download head here (http://www.ati.com/support/driver.html) select Linux as your operating system, select gfx driver (or FireGL if you own a FireGL card) and then select you gfx card. A page will open on which you can download the correct driver version for your PC. It is also important to have the kernel source installed on your PC. You can install it by using the Packet management tool found under System Settings.
5.3 Installing the drivers
It is important to understand that ATI drivers should be installed from the console/terminal. Thus, in this guide, everything will be done in the terminal.
Go into text mode (so no gfx modules interfere with the installation.
su (become root)
init 3
Here you will have to login again. Login as root. Go to the directory to which you downloaded the drivers.
cd /DIRECTORY_NAME/SUBDIRECTORY_NAME
1st try to install the drivers.
rpm -ihv fglrx-glc22-4.3.0-3.2.5.i586.rpm (change name accordingly to your file name)
If you are in luck everything should go smoothly and the driver should install and configure itself. Probably you will not be so lucky. The Xfree driver will be conflicting with your driver installation.
2nd try to install the drivers.
rpm -i -force fglrx-glc22-4.3.0-3.2.5.i586.rpm
OR
rpm -e -nodeps Conflicting_File_and_Version
rpm -ihv fglrx-glc22-4.3.0-3.2.5.i586.rpm
In the first case you will be forcing the driver installation, thus ignoring any files that are conflicting with it. In the second case you will first be removing the file that is conflicting and then normally installing the driver. This can cause some dependencies checks to fail, thus breaking your X installation. For that reason it is wiser to use the first command.
6 Installing ATI drivers on a Gentoo machine
6.1 Where to get the driver
You should use portage (emerge).
6.2 Steps to take before installing the drivers
The kernel has to be configured for the driver. Look at the Kernel configuration file for info.
6.3 Installing the driver
In gentoo installing the driver is pretty simple. All you have to do is to run emerge:
emerge ati-drivers
Emerge will then do all the work (taking care of all the dependencies). Once the emerging is done, all you have to do is to run fglrxconfig.
6.4 Additional info/troubleshooting
A Gentoo only HowTo already exists at http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html
7 Installing ATI drivers on a Slackware Machine
7.1 Where to get the driver
The newest drivers can always be found at http://www.ati.com/support/driver.html.
7.2 Steps to take before installing the drivers
You will have to make some changes to the kernel. Check the kernel configuration part for info on that.
7.3 Installing the driver
First of all, you have to convert the RPM from www.ati.com to a format Slackware understands. This can be done with the utility rpm2targz (in debian you can get it with the help of apt-get).
rpm2targz DRIVER_FILE_NAME.rpm
Now you have to extract the archive:
tar xvzf DRIVER_FILE_NAME.tar.gz
This will create a folder with all the files neatly inside it. Change directory to it:
cd DRIVER_FILE_NAME
(From here on you have to be root to continue)
su
Once inside the driver directory copy all of it's contents to / (yes root):
cp -r * /
Instead of using the above command you can use Slackwares instalpkg application
installpkg DRIVER_FILE_NAME.tar.gz
ldconfig # this is optional
Once this is finished you will have to build the kernel module. Info on how to do this can be found in the Common steps part later in this HowTo. After that it is just a matter of running fglrxconfig to set up X Windows. Info on how to do it can also be found in the Common steps part.
8 Installing the ATI drivers on a Mandrake machine
8.1 Where to get the driver
You can either download them from www.ati.com (and in that case follow the RedHat guide), or use RPMDrake/urpmi to get them. Note that you can only get the drivers via urpmi if you are a paying Mandrake Club Member.
8.2 Steps to take before installing the drivers
The only step to take before the installation is to make sure you have the kernel sources installed. You can get them by using RPMDrake.
8.3 Installing the drivers
Use RPMDrake to download the drivers. They will get configured automatically. You only have to run fglrxconfig to configure X Windows.
9 Installing the ATI drivers on a SuSE machine
9.1 Where to get the driver
You can either download them from www.ati.com, but it is advisable to get them from SuSE (www.suse.com)
9.2 Steps to take before installing the drivers
Just make sure you have your kernel sources installed. You can use Yast2 to get and install them. Also, make sure they are linked to /usr/src/linux. If they are not, just link them:
ln -s /usr/src/linux-kernel-2.X.X /usr/src/linux
If a symbolic link already exists, but you are sure it's not your kernels, just erase it before making the new one.
rm /usr/src/linux
9.3 Installing the drivers
It is important to understand that ATI drivers should be installed from the console/terminal. Thus, in this guide, everything will be done in the terminal.
Go into text mode (so no gfx modules interfere with the installation.
su (become root)
init 3
Here you will have to login again. Login as root. Go to the directory to which you downloaded the drivers.
cd /DIRECTORY_NAME/SUBDIRECTORY_NAME
1st try to install the drivers.
rpm -ihv fglrx-glc22-4.3.0-3.2.5.i586.rpm (change name accordingly to your file name)
If you are in luck everything should go smoothly and the driver should install and configure itself. Probably you will not be so lucky. The Xfree driver will be conflicting with your driver installation.
2nd try to install the drivers.
rpm -i -force fglrx-glc22-4.3.0-3.2.5.i586.rpm
OR
rpm -e -nodeps Conflicting_File_and_Version
rpm -ihv fglrx-glc22-4.3.0-3.2.5.i586.rpm
In the first case you will be forcing the driver installation, thus ignoring any files that are conflicting with it. In the second case you will first be removing the file that is conflicting and then normally installing the driver. This can cause some dependencies checks to fail, thus breaking your X installation. For that reason it is wiser to use the first command.
10 Installing the drivers on a Debian machine
10.1 Where to get the driver
You should get the driver from www.ati.com. You will then convert them to .deb (debian package). Unleass you are using the unstable branch of debian, you are using XFree 4.2.0. Download the according driver.
10.2 Steps to take before installing the drivers
First of all you should get your kernel sources ready. Unless you have them installed already do so now (use apt-get for that). Debian doesn't automaticaly unpact kernel sources, so you have to do it yourself:
cd /usr/src
tar xjvf kernel-source-2.X.X.tar.bz2 #substitute with your kernel sources
ln -s kernel-source-2.X.X linux #this way you will link your new sources with the expected sources directory. If /usr/src/linux exists you can delete the link: rm /usr/src/linux
Now we will make sure our sources are configured to the working kernel:
cp /boot/config-2.X.X-Y-YYY .config #change this according to your kernel version and config name
make oldconfig
make dep
ln -s /usr/src/linux /lib/modules/2.X.X-Y-YYY/build #this will link the modules to the right directory. Again make sure you change the path to your kernel version
Next, we will convert the ATI rpm to deb. To do this you will need alien. Use apt-get to get it. Once you have it run the following command:
alien /directory/subdirectory/ati-driver.rpm #this will create a .deb file in the directory you are currently in
10.3 Installing the drivers
Now we will use the .deb file we created earlier:
dpkg -i ati-driver.deb #you may have to use some of the -force options to get it to install (conflicts with libglx). Use ``dpkg -help'' for more info.
Once the drivers are installed, you will have to build the module. Look at the ``Building the module'' in the Common steps part of the HowTo.
11 Common steps for all distributions
11.1 Kernel 2.6 driver configuration
Currently the ATI fglrx driver have some problems compiling against the 2.6 kernel. To get it to work you will need to make some changes to the driver itself.
First you will have to get the driver and install it.
rpm -ihv -force fglrx-driver.rpm
Gentoo users have it easy here, as the emerge command automaticaly patches the driver, which then works correctly without any other changes.
However, if you are NOT using gentoo, than you will have to make two changes:
First you will have to apply the VMALLOC patch. The link to the patch can be found on top of the (online) page. First you will have to decompress it:
gzip -d vmalloc.patch.gz
Once decompressed copy it into /lib/modules/fglrx:
cp vmalloc.patch /lib/modules/fglrx
Then move to the build_mod directory and execute the patch:
cd /lib/modules/fglrx/build_mod
patch -p1 < ../vmalloc.patch
Once this is done, you will have to make some changes to /lib/modules/fglrx/build_mod/firegl_public.c
Open the file and change all instances of:
#if ( (PAGE_ATTR_FIX == 1) || (LINUX_VERSION_CODE == KERNEL_VERSION(2,4,19)) )
into this:
#if ( (PAGE_ATTR_FIX == 1) || (LINUX_VERSION_CODE >= KERNEL_VERSION(2,4,19)) )
Save the changes and exit. Now you can build the module (look at the following section).
11.2 Building the module
You have to do the following every time you change your kernel or somehow edit the driver module (like installing a newer version over the old one).
cd /lib/modules/fglrx/build_mod #(change directory to where our task lies)
sh make.sh #(gathering kernel information)
cd /lib/modules/fglrx/ #(change directory to where out second task lies)
sh make_install.sh #(configuring the the driver to our kernel)
If you already have a working Xfree86 from previous driver installations/configurations you can keep it, though it is advisable to rerun fglrxconfig.
11.3 Configuration of X Window
It is advisable you enter text mode before running fglrxconfig, as some modules in the GFX mode may interfere with the configuration. In most distributions it is just a matter of running as root:
init 3
In Gentoo and Debian however, you have to either run:
/etc/init.d/xdm stop # change xdm to your login manager (xdm, kdm...)
or simply quit the window manager if you have a text login. Once you are in text mode simply run fglrxconfig.
fglrxconfig
With the ``fglrxconfig'' command you will start the configuration program in which all you have to do is answer the questions that you are asked. Some info that might help:
- If you own a USB Wheel mouse select ``PS/2 or USB with PS/2 protocol'' and then ``PS/2 Wheel Mouse''
- When specifying the mouse mount point (default /dev/mouse) you may run into some issues with either X not starting or the mouse not responding. In that case you may want to try and specify the mount point as /dev/input/mice
- If your keyboard layout is not listed in the list simply select US. You will be able to change this later.
- Default settings (selected by simply pressing enter) are usually the best, but might not be correct in your case. Always be sure you select the right answer.
- It is best to select no ``restrictions - any user has access to the OpenGL ICD'' so any user can use OpenGL acceleration.
- For beginners it is best to select ``Default'' under Application Profiles.
- Select ``compatible operation (for WineX, VM emulators and some profilers)'' to be sure that no compatibility problems will appear in WineX.
Once this is done simply restart Linux, so that all the modules get loaded correctly.
11.4 Fine tuning the installation
You can also change any settings afterward.
Logged in as root go to /etc/X11 and open the file XF86Config-4. Inside it find these lines (pc105 and US can look different in your case):
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "US"
Here you can edit the last line to make sure that your keyboard layout is used.
You can also change the mouse mount point to be used. Just scroll to the mouse part of the file and change the directory. |
|
|
|
|
|
|
|
noclegi w ciechocinku
Kopiowanie i rozpowszechnianie materiałów w całości lub części jest niedozwolone. Wszelkie informacje zawarte w tym miejscu są chronione prawem autorskim.
|