Fedora 16 Installation Guide: Difference between revisions
| Line 99: | Line 99: | ||
The ''akmod-catalyst'' package we installed above automatically builds a new kernel module at boot-time when the kernel is upgraded, so you'll never have to worry about this. | The ''akmod-catalyst'' package we installed above automatically builds a new kernel module at boot-time when the kernel is upgraded, so you'll never have to worry about this. | ||
Гонялись (и гоняются) коды вида Numeric Weather Simulation. На x86_64 это Infiniband кластер, а на IA64 это SGI Altix 4700. Дровишки --- из конторы которая поменяла dropped "e" в своем логотипе. | |||
= Troubleshooting = | = Troubleshooting = | ||
Revision as of 22:34, 21 June 2012
Installing the Official AMD driver
Introduction
There are two methods to get the Official AMD driver installed on Fedora. The first is by running the amd-driver-installer package supplied by amd.com. This method is covered in the section "Official AMD Driver Package from Amd.com". The second is to use the rpm packages supplied by the rpm fusion repos. This method is covered in the section "Pre-built packages from RPMFusion".
The sections titled Amd-driver-installer Compilation Problems on x86_64 Fedora 16 and Amd-driver-installer Compilation Problems on i686 Fedora 16 are subject to being resolved by Catalyst updates and therefore may not be relevant to installations after Catalyst version 12.4.
Requirements
The Amd-driver-installer from Amd.com will work best in most cases if there is no xorg.conf file present before you begin the installation process. Move any existing xorg.conf files out of the /etc/X11 directory before installation.
You will need at least version 11.11 (or greater) of the ATI driver for Fedora 16, earlier versions will not work with the version of Xorg that F16 ships with.
For Catalyst 12.5 or above, a Radeon HD5000 series (or greater) is required. Radeon HD 2000/3000/4000 series GPU's will not be recognized by 12.5 Catalyst and above.
Hi men I believe this is a great pblsiuh I'll definetely continue reading through your functions, congratulations. It is very important to have high quality material on the web, we are able to rely on them as a reliable source for the tasks.I have see clearly along with enjoyment and Im sure I'm gonna study the rest of the stuff you will create, great work man!.
Multiple Monitor Setups
If you have an existing multiple monitor setup, move your existing xorg.conf to a safe place. Let amd-driver-installer generate a fresh working xorg.conf file for you based on what it probes from EDID monitor info. If you are having difficulties after generating a new xorg.conf, use your old xorg.conf as a reference and transfer sections of that file as needed to the new one.
Here are some resources for those having difficulty getting their multiple monitors running:
- http://www.thinkwiki.org/wiki/Xorg_RandR_1.2
- http://wiki.debian.org/XStrikeForce/HowToRandR12
- aticonfig --help
- One of the Ubuntu guides on this Wiki.
- AMD's own Catalyst documentation
If you need to start with a clean slate and all your monitors are connected, you can force a fresh xorg.conf to be generated taking into account the monitors present:
su - aticonfig --initial -f
Pre-built packages from RPMFusion
Note: This section does not apply to users using the Official amd-driver-installer package downloaded from amd.com
RECOMMENDED METHOD
This is easier than manually building the driver from AMD as you don't need to worry about passing kernel options via GRUB2, configuring DKMS, rebuilding the kernel module every time you do a kernel upgrade, or cleaning up any mess if you want to remove the driver.
Clean up previous Offical AMD driver installation
If you're coming from the Official AMD driver to RPMFusion's AMD driver, you'll need to reinstall the mesa-libGL package as the Official AMD driver installation changes files it contains.
su - yum reinstall mesa-libGL
Other issues before install driver
On Acer Aspire 722 (A0722) with Radeon HD 6290 (and i suppose on other machines with the same card) you must disable SELinux or the follow error will occured :
SELinux is preventing gnome-session-c from execmod access on the file /usr/lib/dri/fglrx_dri.so. For complete SELinux messages run sealert -l <SELinux alert id>
To disable SELinux open /etc/selinux/config file as root and set SELINUX to disabled (SELINUX=disabled).
After that driver will work as expected.
Note: Disabling SELinux is not a very good idea. It's better to just modify the policy, by running these two commands (as root):
semanage fcontext -a -t textrel_shlib_t '/usr/lib/dri/fglrx_dri.so' restorecon -v '/usr/lib/dri/fglrx_dri.so'
glxinfo
direct rendering : Yes ... OpenGL vendor string : Advanced Microd Devices Inc. OpenGL render string : AMD Radeon HD 6290 Graphics ...
anderson laud - Yes it can. This post was originally wreittn after release of Fedora Core 10. I used this install "mplayer" procedure for every Fedora release up to Fedora Core 14. In a few weeks, FC15 will be available so keep on eye this "mplayer" cookbook - it will surely be useful ... Cheers!
Install Catalyst driver packages
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.
su - yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs
32-bit Libraries on 64-bit OS
If you want to play 32-bit games on a 64-bit Fedora installation, you will need to install the 32-bit libraries in addition to the above step.
su - yum install xorg-x11-drv-catalyst-libs.i686
Kernel module packages
Note that there are individual kmod-catalyst- packages in RPMFusion which supply kernel modules for specific Fedora kernel versions. If you use these and you upgrade the kernel without upgrading the kmod-catalyst- package, loading the proprietary driver will fail and you'll revert back to the Free radeon graphics driver. Sometimes there is a day or so between Fedora upgrading their kernel and RPMFusion building a new kmod-catalyst- package.
The akmod-catalyst package we installed above automatically builds a new kernel module at boot-time when the kernel is upgraded, so you'll never have to worry about this.
Гонялись (и гоняются) коды вида Numeric Weather Simulation. На x86_64 это Infiniband кластер, а на IA64 это SGI Altix 4700. Дровишки --- из конторы которая поменяла dropped "e" в своем логотипе.
Troubleshooting
In the event you install the driver and are greeted with a blank screen or corrupted video signal when starting X, you are able to manually disable the Free Software radeon driver to troubleshoot.
There are two methods to disable radeon module. The first is a two-step process and the other approach is listed below.
Approach #1:
1) Edit the /etc/modprobe.d/blacklist.conf and add radeon to the list.
2) Run the following:
su - /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --install $(uname -r)
That's it. This will generate a new initramfs that does not have radeon built in. This method has the advantage of not affecting kernel mode setting as well as not needing any grub edits. On the next boot, the radeon module should be gone. You can now reboot to console and execute steps in section above titled "Official AMD Driver Package from Amd.com"
Approach #2:
Turn your system off and on again. On the GRUB boot screen, press e to edit the default boot entry, scroll down to the kernel line (which begins linux), then press e again to edit the line.
Add the entries radeon.modeset=0 blacklist=radeon to the end. For example, if your kernel line is
linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8
we'll want to edit it so it is
linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 rdblacklist=radeon blacklist=radeon
These entries do the following:
- radeon.modeset=0 disables "Kernel Mode Settting" for the Free Software driver (ie: the driver telling the kernel to setup the screen resolution, instead of XOrg doing it)
- rdblacklist=radeon blacklist=radeon stops the kernel from loading the Free Software radeon driver altogether
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's Add/Remove Software application, as desired.
