http://wiki.cchtml.com/api.php?action=feedcontributions&user=Super+Jamie&feedformat=atomcchtml.com - User contributions [en]2024-03-28T21:31:38ZUser contributionsMediaWiki 1.39.4http://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8275Fedora 16 Installation Guide2012-03-22T21:05:24Z<p>Super Jamie: This is stupid.</p>
<hr />
<div>= Installing the Official AMD driver =<br />
<br />
== Requirements ==<br />
<br />
The AMD-supplied driver 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.<br />
<br />
You will need version 11.11 of the ATI driver or later for Fedora 16, earlier versions will not work with the version of XOrg that F16 ships with.<br />
<br />
You require a Radeon HD2000 series or better to use the latest AMD-supplied driver.<br />
<br />
=== kernel-3.2.9-2.fc16 and onwards ===<br />
<br />
Due to an upstream sourcecode change in the Fedora ''kernel-headers'' package, building of AMD's ''fglrx'' module will currently fail with kernels 3.2.9-2.fc16 and later.<br />
<br />
To fix this, we can revert a small edit. Open the file '''/usr/src/kernels/`uname -r`/arch/x86/include/asm/uaccess_64.h''' in a text editor.<br />
<br />
On line 56 and 57 you will see:<br />
<br />
<pre><br />
else<br />
WARN(1, "Buffer overflow detected!\n");<br />
</pre><br />
<br />
Comment this out so it reads:<br />
<br />
<pre><br />
// else<br />
// WARN(1, "Buffer overflow detected!\n"); <br />
</pre><br />
<br />
Your AMD kernel module will now build correctly. You may have to reboot into the new kernel and force the module rebuild with<br />
<br />
<pre><br />
su -<br />
akmods --force<br />
</pre><br />
<br />
then reboot again.<br />
<br />
* Reference: http://forums.fedoraforum.org/showthread.php?t=277547<br />
<br />
=== Multiple Monitor Setups ===<br />
<br />
If you have an existing multiple monitor setup, copy your existing xorg.conf to as safe place, follow one of the install procedures, then transfer relevant sections of your old xorg.conf into the new version generated with aticonfig if required.<br />
<br />
Here are some resources for those having difficulty getting their multiple monitors running:<br />
<br />
* http://www.thinkwiki.org/wiki/Xorg_RandR_1.2<br />
* http://wiki.debian.org/XStrikeForce/HowToRandR12<br />
* man aticonfig<br />
* One of the [[Ubuntu]] guides on this Wiki.<br />
* AMD's own Catalyst documentation<br />
<br />
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:<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
== Pre-built packages from RPMFusion ==<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous Offical AMD driver installation ===<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Official AMD Driver ==<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds the kernel module and a set of modules for XOrg. The Official AMD installer requires some development packages to be installed:<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
We'll also want to remove any kernel-devel packages from old versions of the kernel. Check your current kernel version with:<br />
<br />
<pre><br />
uname -a<br />
</pre><br />
<br />
Check all installed kernel packages with<br />
<br />
<pre><br />
su -<br />
rpm -qa | grep kernel<br />
</pre><br />
<br />
Remove any ''kernel-devel'' packages which do not match the latest kernel version. For example:<br />
<br />
<pre><br />
su -<br />
yum remove kernel-devel-3.2.9-1.fc16.x86_64<br />
</pre><br />
<br />
Note we are careful to specify the exact package name that was given to us by the rpm command above.<br />
<br />
Boot into the latest kernel before continuing. Building the module on a kernel which you don't have ''-devel'' packages for will fail. Building the module on one kernel then booting into another will result in the compiled module not working.<br />
<br />
=== Download driver ===<br />
<br />
Download the driver for your particular card from http://support.amd.com/<br />
<br />
It will look similar to: ''amd-driver-installer-XX-X-XXX.XXX_XX.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
sh ./amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log:<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked:<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Uninstalling Official AMD driver ===<br />
<br />
Run AMD's uninstall script:<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/fglrx-uninstall.sh<br />
</pre><br />
<br />
The following steps are not strictly required because the amd-driver-installer is written to put all files back as they were before the install. One set of files that amd-driver-installer alters is the mesa library set. To be sure of a mint-condition installation (especially if you are upgrading to the next Official driver version) reinstall the following package:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
For those running Wine or Crossover from Codeweavers.com, the following command will reinstall all the mesa libraries that (should) be on your system. This example is for users running Wine/Crossover on a 64 bit system:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-dri-filesystem.i686 mesa-libGL.x86_64 mesa-dri-drivers.x86_64 mesa-libGL.i686 mesa-dri-filesystem.x86_64 mesa-libEGL.x86_64 mesa-dri-drivers.i686 mesa-libGLU.x86_64<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 rdblacklist=radeon blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''rdblacklist=radeon blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8265Fedora 16 Installation Guide2012-03-22T12:05:15Z<p>Super Jamie: /* kernel-3.2.9-2.fc16 and onwards */</p>
<hr />
<div>= Two Driver Choices =<br />
<br />
There are two video drivers you can choose to run your ATI video card, one is called ''radeon'', the other is ''fglrx''.<br />
<br />
=== radeon - the in-kernel driver ===<br />
<br />
This is the Free Software driver included in the mainline Linux kernel. This driver is written by an open source community with no access to the hardware specs and is released under the GNU GPL. If software freedom is your main concern, this is the driver for you.<br />
<br />
Historically, the ''radeon'' driver couldn't do much, not even 2D acceleration. However, in Fedora 16's 3.1 and 3.2 kernels this driver is making real progress. It now supports 2D compositing, many 3D functions such as GLSL and Pixel Shaders, as well as other useful features like Kernel Mode Setting. There is currently a large push in graphics driver development upstream in the kernel, so this driver's expected to get even better in kernels 3.3 and 3.4.<br />
<br />
The ''radeon'' driver packaged with Fedora 16 will easily run desktop compositing (eg: gnome-shell, compiz, transparent terminal). It manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine, ''OpenArena'' Quake 3 engine) with no problems. Depending on your CPU, constant 45fps in 1080p ''Minecraft'' is easily doable.<br />
<br />
You can read more about the radeon driver on [http://www.x.org/wiki/radeon the XOrg Wiki]. You can also find a [http://www.x.org/wiki/RadeonFeature list of supported features] and [http://www.x.org/wiki/RadeonProgram list of supported software] if you'd like to investigate using this driver.<br />
<br />
It's worth noting that 2D performance is actually better in this driver than the proprietary driver. If you're only using Gnome 3 and typical Linux games, or not playing games at all, or wish to extend your laptop's battery life, this is probably your best choice.<br />
<br />
=== fglrx - the AMD-supplied driver ===<br />
<br />
This is the driver written and distributed by ATI, who have full access to the internal specs of the hardware, so can make a full-featured driver which supports all the capabilities of the hardware. The driver consists of a small kernel module which acts as a loader for the actual driver, which is distributed as a closed-source "[http://en.wikipedia.org/wiki/Binary_blob binary blob]".<br />
<br />
''fglrx'' was originally written only for ATI's FireGL professional workstation cards (targeting the same market as nVidia's Quadro range) however it was soon expanded to include almost the whole ATI range. AMD continue to extend the driver after their acquisition of ATI. This driver also includes the ''Catalyst Control Center'' tool for configuring features like forcing anti-aliasing and anistropic filtering on for all OpenGL processing.<br />
<br />
If you are running newer games, such as most things you'd get off Steam, ''fglrx'' is probably going to be your best choice. If you have a game which produces graphical glitches under the Free driver, it's worth trying this driver to see if the game works. Generally, performance in all 3D games and 3D applications will be measurably improved with this driver. As mentioned above, 2D performance is actually worse than the Free driver, though it's definitely fine for day-to-day desktop use.<br />
<br />
Each driver as pros and cons, try both and see which is most suitable for your needs. The best thing about Linux is the choice to run whatever software components you like.<br />
<br />
= Installing the AMD-supplied driver =<br />
<br />
== Requirements ==<br />
<br />
The AMD-supplied driver 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.<br />
<br />
You will need version 11.11 of the ATI driver or later for Fedora 16, earlier versions will not work with the version of XOrg that F16 ships with.<br />
<br />
You require a Radeon HD2000 series or better to use the latest AMD-supplied driver.<br />
<br />
=== kernel-3.2.9-2.fc16 and onwards ===<br />
<br />
Due to an upstream sourcecode change in the Fedora ''kernel-headers'' package, building of AMD's ''fglrx'' module will currently fail with kernels 3.2.9-2.fc16 and later.<br />
<br />
To fix this, we can revert a small edit. Open the file '''/usr/src/kernels/`uname -r`/arch/x86/include/asm/uaccess_64.h''' in a text editor.<br />
<br />
On line 56 and 57 you will see:<br />
<br />
<pre><br />
else<br />
WARN(1, "Buffer overflow detected!\n");<br />
</pre><br />
<br />
Comment this out so it reads:<br />
<br />
<pre><br />
// else<br />
// WARN(1, "Buffer overflow detected!\n"); <br />
</pre><br />
<br />
Your AMD kernel module will now build correctly. You may have to reboot into the new kernel and force the module rebuild with<br />
<br />
<pre><br />
su -<br />
akmods --force<br />
</pre><br />
<br />
then reboot again.<br />
<br />
* Reference: http://forums.fedoraforum.org/showthread.php?t=277547<br />
<br />
=== Multiple Monitor Setups ===<br />
<br />
If you have an existing multiple monitor setup, copy your existing xorg.conf to as safe place, follow one of the install procedures, then transfer relevant sections of your old xorg.conf into the new version generated with aticonfig if required.<br />
<br />
Here are some resources for those having difficulty getting their multiple monitors running:<br />
<br />
* http://www.thinkwiki.org/wiki/Xorg_RandR_1.2<br />
* http://wiki.debian.org/XStrikeForce/HowToRandR12<br />
* man aticonfig<br />
* One of the [[Ubuntu]] guides on this Wiki.<br />
* AMD's own Catalyst documentation<br />
<br />
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:<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
== Pre-built packages from RPMFusion ==<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous Offical AMD driver installation ===<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Official AMD Driver ==<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds the kernel module and a set of modules for XOrg. The Official AMD installer requires some development packages to be installed:<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
We'll also want to remove any kernel-devel packages from old versions of the kernel. Check your current kernel version with:<br />
<br />
<pre><br />
uname -a<br />
</pre><br />
<br />
Check all installed kernel packages with<br />
<br />
<pre><br />
su -<br />
rpm -qa | grep kernel<br />
</pre><br />
<br />
Remove any ''kernel-devel'' packages which do not match the latest kernel version. For example:<br />
<br />
<pre><br />
su -<br />
yum remove kernel-devel-3.2.9-1.fc16.x86_64<br />
</pre><br />
<br />
Note we are careful to specify the exact package name that was given to us by the rpm command above.<br />
<br />
Boot into the latest kernel before continuing. Building the module on a kernel which you don't have ''-devel'' packages for will fail. Building the module on one kernel then booting into another will result in the compiled module not working.<br />
<br />
=== Download driver ===<br />
<br />
Download the driver for your particular card from http://support.amd.com/<br />
<br />
It will look similar to: ''amd-driver-installer-XX-X-XXX.XXX_XX.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
sh ./amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log:<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked:<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Uninstalling Official AMD driver ===<br />
<br />
Run AMD's uninstall script:<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/fglrx-uninstall.sh<br />
</pre><br />
<br />
The following steps are not strictly required because the amd-driver-installer is written to put all files back as they were before the install. One set of files that amd-driver-installer alters is the mesa library set. To be sure of a mint-condition installation (especially if you are upgrading to the next Official driver version) reinstall the following package:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
For those running Wine or Crossover from Codeweavers.com, the following command will reinstall all the mesa libraries that (should) be on your system. This example is for users running Wine/Crossover on a 64 bit system:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-dri-filesystem.i686 mesa-libGL.x86_64 mesa-dri-drivers.x86_64 mesa-libGL.i686 mesa-dri-filesystem.x86_64 mesa-libEGL.x86_64 mesa-dri-drivers.i686 mesa-libGLU.x86_64<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 rdblacklist=radeon blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''rdblacklist=radeon blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=User_talk:67.239.165.48&diff=8264User talk:67.239.165.482012-03-22T11:48:41Z<p>Super Jamie: </p>
<hr />
<div>* I don't know who's editing the Fedora 16 Fglrx page, but the first paragraph titled "Please Consider" was originally written evidently to push a particular license (GPL) rather than present procedures and solutions. I've edited that to make it somewhat neutral but someone seems intent on pushing radeon first. Besides the fact that radeon is already the default installed driver on most distros, there isn't really a need to mention radeon at all other than to state that it exists, since a procedure is generally not needed for radeon installation. That makes a radeon driver discussion redundant unless you are pushing GPL. IMO this site should not be used for pimping licenses but rather for presenting solutions.<br />
<br />
** That's me, check the history. I actually like your idea of presenting two driver options and I've written a more impartial overview of each driver. I see you're still editing so I'll wait till you're done to apply it. I also disagree with some things you've stated: The broken module compilation is fixed with a two-line sourcecode comment, we should include the fix rather that just say "it's busted", I'm using fglrx on 3.2.9-2 fine. I'm also completely removing your dracut step, this is far too complex for a regular user who doesn't understand initramfs, it also leaves the system in a state where it may not actually have a graphics driver if fglrx stuffs up. Blacklisting on the kernel line is sufficient and is what the RPMFusion RPM scripts and the Official installation script do anyway. --[[User:Super Jamie|Super Jamie]] 06:02, 22 March 2012 (CDT)<br />
** Changes made. Feel free to contact me via the email address on my userpage if you'd like to discuss directly, here is fine too. --[[User:Super Jamie|Super Jamie]] 06:48, 22 March 2012 (CDT)</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8263Fedora 16 Installation Guide2012-03-22T11:46:36Z<p>Super Jamie: /* Multiple Monitor Setups */</p>
<hr />
<div>= Two Driver Choices =<br />
<br />
There are two video drivers you can choose to run your ATI video card, one is called ''radeon'', the other is ''fglrx''.<br />
<br />
=== radeon - the in-kernel driver ===<br />
<br />
This is the Free Software driver included in the mainline Linux kernel. This driver is written by an open source community with no access to the hardware specs and is released under the GNU GPL. If software freedom is your main concern, this is the driver for you.<br />
<br />
Historically, the ''radeon'' driver couldn't do much, not even 2D acceleration. However, in Fedora 16's 3.1 and 3.2 kernels this driver is making real progress. It now supports 2D compositing, many 3D functions such as GLSL and Pixel Shaders, as well as other useful features like Kernel Mode Setting. There is currently a large push in graphics driver development upstream in the kernel, so this driver's expected to get even better in kernels 3.3 and 3.4.<br />
<br />
The ''radeon'' driver packaged with Fedora 16 will easily run desktop compositing (eg: gnome-shell, compiz, transparent terminal). It manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine, ''OpenArena'' Quake 3 engine) with no problems. Depending on your CPU, constant 45fps in 1080p ''Minecraft'' is easily doable.<br />
<br />
You can read more about the radeon driver on [http://www.x.org/wiki/radeon the XOrg Wiki]. You can also find a [http://www.x.org/wiki/RadeonFeature list of supported features] and [http://www.x.org/wiki/RadeonProgram list of supported software] if you'd like to investigate using this driver.<br />
<br />
It's worth noting that 2D performance is actually better in this driver than the proprietary driver. If you're only using Gnome 3 and typical Linux games, or not playing games at all, or wish to extend your laptop's battery life, this is probably your best choice.<br />
<br />
=== fglrx - the AMD-supplied driver ===<br />
<br />
This is the driver written and distributed by ATI, who have full access to the internal specs of the hardware, so can make a full-featured driver which supports all the capabilities of the hardware. The driver consists of a small kernel module which acts as a loader for the actual driver, which is distributed as a closed-source "[http://en.wikipedia.org/wiki/Binary_blob binary blob]".<br />
<br />
''fglrx'' was originally written only for ATI's FireGL professional workstation cards (targeting the same market as nVidia's Quadro range) however it was soon expanded to include almost the whole ATI range. AMD continue to extend the driver after their acquisition of ATI. This driver also includes the ''Catalyst Control Center'' tool for configuring features like forcing anti-aliasing and anistropic filtering on for all OpenGL processing.<br />
<br />
If you are running newer games, such as most things you'd get off Steam, ''fglrx'' is probably going to be your best choice. If you have a game which produces graphical glitches under the Free driver, it's worth trying this driver to see if the game works. Generally, performance in all 3D games and 3D applications will be measurably improved with this driver. As mentioned above, 2D performance is actually worse than the Free driver, though it's definitely fine for day-to-day desktop use.<br />
<br />
Each driver as pros and cons, try both and see which is most suitable for your needs. The best thing about Linux is the choice to run whatever software components you like.<br />
<br />
= Installing the AMD-supplied driver =<br />
<br />
== Requirements ==<br />
<br />
The AMD-supplied driver 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.<br />
<br />
You will need version 11.11 of the ATI driver or later for Fedora 16, earlier versions will not work with the version of XOrg that F16 ships with.<br />
<br />
You require a Radeon HD2000 series or better to use the latest AMD-supplied driver.<br />
<br />
=== kernel-3.2.9-2.fc16 and onwards ===<br />
<br />
Due to an upstream sourcecode change in the Fedora ''kernel-headers'' package, building of AMD's ''fglrx'' module will currently fail with kernels 3.2.9-2.fc16 and later.<br />
<br />
To fix this, we can revert a small edit. Open the file '''/usr/src/kernels/`uname -r`/arch/x86/include/asm/uaccess_64.h''' in a text editor.<br />
<br />
On line 56 and 57 you will see:<br />
<br />
<pre><br />
else<br />
WARN(1, "Buffer overflow detected!\n");<br />
</pre><br />
<br />
Comment this out so it reads:<br />
<br />
<pre><br />
// else<br />
// WARN(1, "Buffer overflow detected!\n"); <br />
</pre><br />
<br />
Your AMD kernel module will now build correctly.<br />
<br />
* Reference: http://forums.fedoraforum.org/showthread.php?t=277547<br />
<br />
=== Multiple Monitor Setups ===<br />
<br />
If you have an existing multiple monitor setup, copy your existing xorg.conf to as safe place, follow one of the install procedures, then transfer relevant sections of your old xorg.conf into the new version generated with aticonfig if required.<br />
<br />
Here are some resources for those having difficulty getting their multiple monitors running:<br />
<br />
* http://www.thinkwiki.org/wiki/Xorg_RandR_1.2<br />
* http://wiki.debian.org/XStrikeForce/HowToRandR12<br />
* man aticonfig<br />
* One of the [[Ubuntu]] guides on this Wiki.<br />
* AMD's own Catalyst documentation<br />
<br />
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:<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
== Pre-built packages from RPMFusion ==<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous Offical AMD driver installation ===<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Official AMD Driver ==<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds the kernel module and a set of modules for XOrg. The Official AMD installer requires some development packages to be installed:<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
We'll also want to remove any kernel-devel packages from old versions of the kernel. Check your current kernel version with:<br />
<br />
<pre><br />
uname -a<br />
</pre><br />
<br />
Check all installed kernel packages with<br />
<br />
<pre><br />
su -<br />
rpm -qa | grep kernel<br />
</pre><br />
<br />
Remove any ''kernel-devel'' packages which do not match the latest kernel version. For example:<br />
<br />
<pre><br />
su -<br />
yum remove kernel-devel-3.2.9-1.fc16.x86_64<br />
</pre><br />
<br />
Note we are careful to specify the exact package name that was given to us by the rpm command above.<br />
<br />
Boot into the latest kernel before continuing. Building the module on a kernel which you don't have ''-devel'' packages for will fail. Building the module on one kernel then booting into another will result in the compiled module not working.<br />
<br />
=== Download driver ===<br />
<br />
Download the driver for your particular card from http://support.amd.com/<br />
<br />
It will look similar to: ''amd-driver-installer-XX-X-XXX.XXX_XX.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
sh ./amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log:<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked:<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Uninstalling Official AMD driver ===<br />
<br />
Run AMD's uninstall script:<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/fglrx-uninstall.sh<br />
</pre><br />
<br />
The following steps are not strictly required because the amd-driver-installer is written to put all files back as they were before the install. One set of files that amd-driver-installer alters is the mesa library set. To be sure of a mint-condition installation (especially if you are upgrading to the next Official driver version) reinstall the following package:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
For those running Wine or Crossover from Codeweavers.com, the following command will reinstall all the mesa libraries that (should) be on your system. This example is for users running Wine/Crossover on a 64 bit system:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-dri-filesystem.i686 mesa-libGL.x86_64 mesa-dri-drivers.x86_64 mesa-libGL.i686 mesa-dri-filesystem.x86_64 mesa-libEGL.x86_64 mesa-dri-drivers.i686 mesa-libGLU.x86_64<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 rdblacklist=radeon blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''rdblacklist=radeon blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8262Fedora 16 Installation Guide2012-03-22T11:44:48Z<p>Super Jamie: /* kernel-3.2.9-2.fc16 and onwards */</p>
<hr />
<div>= Two Driver Choices =<br />
<br />
There are two video drivers you can choose to run your ATI video card, one is called ''radeon'', the other is ''fglrx''.<br />
<br />
=== radeon - the in-kernel driver ===<br />
<br />
This is the Free Software driver included in the mainline Linux kernel. This driver is written by an open source community with no access to the hardware specs and is released under the GNU GPL. If software freedom is your main concern, this is the driver for you.<br />
<br />
Historically, the ''radeon'' driver couldn't do much, not even 2D acceleration. However, in Fedora 16's 3.1 and 3.2 kernels this driver is making real progress. It now supports 2D compositing, many 3D functions such as GLSL and Pixel Shaders, as well as other useful features like Kernel Mode Setting. There is currently a large push in graphics driver development upstream in the kernel, so this driver's expected to get even better in kernels 3.3 and 3.4.<br />
<br />
The ''radeon'' driver packaged with Fedora 16 will easily run desktop compositing (eg: gnome-shell, compiz, transparent terminal). It manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine, ''OpenArena'' Quake 3 engine) with no problems. Depending on your CPU, constant 45fps in 1080p ''Minecraft'' is easily doable.<br />
<br />
You can read more about the radeon driver on [http://www.x.org/wiki/radeon the XOrg Wiki]. You can also find a [http://www.x.org/wiki/RadeonFeature list of supported features] and [http://www.x.org/wiki/RadeonProgram list of supported software] if you'd like to investigate using this driver.<br />
<br />
It's worth noting that 2D performance is actually better in this driver than the proprietary driver. If you're only using Gnome 3 and typical Linux games, or not playing games at all, or wish to extend your laptop's battery life, this is probably your best choice.<br />
<br />
=== fglrx - the AMD-supplied driver ===<br />
<br />
This is the driver written and distributed by ATI, who have full access to the internal specs of the hardware, so can make a full-featured driver which supports all the capabilities of the hardware. The driver consists of a small kernel module which acts as a loader for the actual driver, which is distributed as a closed-source "[http://en.wikipedia.org/wiki/Binary_blob binary blob]".<br />
<br />
''fglrx'' was originally written only for ATI's FireGL professional workstation cards (targeting the same market as nVidia's Quadro range) however it was soon expanded to include almost the whole ATI range. AMD continue to extend the driver after their acquisition of ATI. This driver also includes the ''Catalyst Control Center'' tool for configuring features like forcing anti-aliasing and anistropic filtering on for all OpenGL processing.<br />
<br />
If you are running newer games, such as most things you'd get off Steam, ''fglrx'' is probably going to be your best choice. If you have a game which produces graphical glitches under the Free driver, it's worth trying this driver to see if the game works. Generally, performance in all 3D games and 3D applications will be measurably improved with this driver. As mentioned above, 2D performance is actually worse than the Free driver, though it's definitely fine for day-to-day desktop use.<br />
<br />
Each driver as pros and cons, try both and see which is most suitable for your needs. The best thing about Linux is the choice to run whatever software components you like.<br />
<br />
= Installing the AMD-supplied driver =<br />
<br />
== Requirements ==<br />
<br />
The AMD-supplied driver 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.<br />
<br />
You will need version 11.11 of the ATI driver or later for Fedora 16, earlier versions will not work with the version of XOrg that F16 ships with.<br />
<br />
You require a Radeon HD2000 series or better to use the latest AMD-supplied driver.<br />
<br />
=== kernel-3.2.9-2.fc16 and onwards ===<br />
<br />
Due to an upstream sourcecode change in the Fedora ''kernel-headers'' package, building of AMD's ''fglrx'' module will currently fail with kernels 3.2.9-2.fc16 and later.<br />
<br />
To fix this, we can revert a small edit. Open the file '''/usr/src/kernels/`uname -r`/arch/x86/include/asm/uaccess_64.h''' in a text editor.<br />
<br />
On line 56 and 57 you will see:<br />
<br />
<pre><br />
else<br />
WARN(1, "Buffer overflow detected!\n");<br />
</pre><br />
<br />
Comment this out so it reads:<br />
<br />
<pre><br />
// else<br />
// WARN(1, "Buffer overflow detected!\n"); <br />
</pre><br />
<br />
Your AMD kernel module will now build correctly.<br />
<br />
* Reference: http://forums.fedoraforum.org/showthread.php?t=277547<br />
<br />
=== Multiple Monitor Setups ===<br />
<br />
If you have an existing multiple monitor setup, follow one of the install procedures, then transfer relevant sections of your old xorg.conf into the new version generated with aticonfig if required.<br />
<br />
There are some excellent resource pages for those who are having difficulty in getting their multiple monitor setups running:<br />
<br />
* http://www.thinkwiki.org/wiki/Xorg_RandR_1.2<br />
* http://wiki.debian.org/XStrikeForce/HowToRandR12<br />
* man aticonfig<br />
* One of the [[Ubuntu]] guides on this Wiki.<br />
* AMD's own Catalyst documentation<br />
<br />
If you need to start with a clean slate and all your monitors are connected, you can do the following to force a fresh xorg.conf to be generated taking into account the monitors present:<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
== Pre-built packages from RPMFusion ==<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous Offical AMD driver installation ===<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Official AMD Driver ==<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds the kernel module and a set of modules for XOrg. The Official AMD installer requires some development packages to be installed:<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
We'll also want to remove any kernel-devel packages from old versions of the kernel. Check your current kernel version with:<br />
<br />
<pre><br />
uname -a<br />
</pre><br />
<br />
Check all installed kernel packages with<br />
<br />
<pre><br />
su -<br />
rpm -qa | grep kernel<br />
</pre><br />
<br />
Remove any ''kernel-devel'' packages which do not match the latest kernel version. For example:<br />
<br />
<pre><br />
su -<br />
yum remove kernel-devel-3.2.9-1.fc16.x86_64<br />
</pre><br />
<br />
Note we are careful to specify the exact package name that was given to us by the rpm command above.<br />
<br />
Boot into the latest kernel before continuing. Building the module on a kernel which you don't have ''-devel'' packages for will fail. Building the module on one kernel then booting into another will result in the compiled module not working.<br />
<br />
=== Download driver ===<br />
<br />
Download the driver for your particular card from http://support.amd.com/<br />
<br />
It will look similar to: ''amd-driver-installer-XX-X-XXX.XXX_XX.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
sh ./amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log:<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked:<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Uninstalling Official AMD driver ===<br />
<br />
Run AMD's uninstall script:<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/fglrx-uninstall.sh<br />
</pre><br />
<br />
The following steps are not strictly required because the amd-driver-installer is written to put all files back as they were before the install. One set of files that amd-driver-installer alters is the mesa library set. To be sure of a mint-condition installation (especially if you are upgrading to the next Official driver version) reinstall the following package:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
For those running Wine or Crossover from Codeweavers.com, the following command will reinstall all the mesa libraries that (should) be on your system. This example is for users running Wine/Crossover on a 64 bit system:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-dri-filesystem.i686 mesa-libGL.x86_64 mesa-dri-drivers.x86_64 mesa-libGL.i686 mesa-dri-filesystem.x86_64 mesa-libEGL.x86_64 mesa-dri-drivers.i686 mesa-libGLU.x86_64<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 rdblacklist=radeon blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''rdblacklist=radeon blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8261Fedora 16 Installation Guide2012-03-22T11:42:29Z<p>Super Jamie: </p>
<hr />
<div>= Two Driver Choices =<br />
<br />
There are two video drivers you can choose to run your ATI video card, one is called ''radeon'', the other is ''fglrx''.<br />
<br />
=== radeon - the in-kernel driver ===<br />
<br />
This is the Free Software driver included in the mainline Linux kernel. This driver is written by an open source community with no access to the hardware specs and is released under the GNU GPL. If software freedom is your main concern, this is the driver for you.<br />
<br />
Historically, the ''radeon'' driver couldn't do much, not even 2D acceleration. However, in Fedora 16's 3.1 and 3.2 kernels this driver is making real progress. It now supports 2D compositing, many 3D functions such as GLSL and Pixel Shaders, as well as other useful features like Kernel Mode Setting. There is currently a large push in graphics driver development upstream in the kernel, so this driver's expected to get even better in kernels 3.3 and 3.4.<br />
<br />
The ''radeon'' driver packaged with Fedora 16 will easily run desktop compositing (eg: gnome-shell, compiz, transparent terminal). It manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine, ''OpenArena'' Quake 3 engine) with no problems. Depending on your CPU, constant 45fps in 1080p ''Minecraft'' is easily doable.<br />
<br />
You can read more about the radeon driver on [http://www.x.org/wiki/radeon the XOrg Wiki]. You can also find a [http://www.x.org/wiki/RadeonFeature list of supported features] and [http://www.x.org/wiki/RadeonProgram list of supported software] if you'd like to investigate using this driver.<br />
<br />
It's worth noting that 2D performance is actually better in this driver than the proprietary driver. If you're only using Gnome 3 and typical Linux games, or not playing games at all, or wish to extend your laptop's battery life, this is probably your best choice.<br />
<br />
=== fglrx - the AMD-supplied driver ===<br />
<br />
This is the driver written and distributed by ATI, who have full access to the internal specs of the hardware, so can make a full-featured driver which supports all the capabilities of the hardware. The driver consists of a small kernel module which acts as a loader for the actual driver, which is distributed as a closed-source "[http://en.wikipedia.org/wiki/Binary_blob binary blob]".<br />
<br />
''fglrx'' was originally written only for ATI's FireGL professional workstation cards (targeting the same market as nVidia's Quadro range) however it was soon expanded to include almost the whole ATI range. AMD continue to extend the driver after their acquisition of ATI. This driver also includes the ''Catalyst Control Center'' tool for configuring features like forcing anti-aliasing and anistropic filtering on for all OpenGL processing.<br />
<br />
If you are running newer games, such as most things you'd get off Steam, ''fglrx'' is probably going to be your best choice. If you have a game which produces graphical glitches under the Free driver, it's worth trying this driver to see if the game works. Generally, performance in all 3D games and 3D applications will be measurably improved with this driver. As mentioned above, 2D performance is actually worse than the Free driver, though it's definitely fine for day-to-day desktop use.<br />
<br />
Each driver as pros and cons, try both and see which is most suitable for your needs. The best thing about Linux is the choice to run whatever software components you like.<br />
<br />
= Installing the AMD-supplied driver =<br />
<br />
== Requirements ==<br />
<br />
The AMD-supplied driver 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.<br />
<br />
You will need version 11.11 of the ATI driver or later for Fedora 16, earlier versions will not work with the version of XOrg that F16 ships with.<br />
<br />
You require a Radeon HD2000 series or better to use the latest AMD-supplied driver.<br />
<br />
=== kernel-3.2.9-2.fc16 and onwards ===<br />
<br />
Due to an upstream sourcecode change in the Fedora ''kernel-headers'' package, building of AMD's ''fglrx'' module will currently fail with kernels 3.2.9-2.fc16 and later.<br />
<br />
To fix this, we can revert a small edit. Open the file '''/usr/src/kernels/3.2.9-2.fc16.x86_64/arch/x86/include/asm/uaccess_64.h''' in a text editor.<br />
<br />
On line 56 and 57 you will see:<br />
<br />
<pre><br />
else<br />
WARN(1, "Buffer overflow detected!\n");<br />
</pre><br />
<br />
Comment this out so it reads:<br />
<br />
<pre><br />
// else<br />
// WARN(1, "Buffer overflow detected!\n"); <br />
</pre><br />
<br />
Your AMD kernel module will now build correctly.<br />
<br />
* Reference: http://forums.fedoraforum.org/showthread.php?t=277547<br />
<br />
=== Multiple Monitor Setups ===<br />
<br />
If you have an existing multiple monitor setup, follow one of the install procedures, then transfer relevant sections of your old xorg.conf into the new version generated with aticonfig if required.<br />
<br />
There are some excellent resource pages for those who are having difficulty in getting their multiple monitor setups running:<br />
<br />
* http://www.thinkwiki.org/wiki/Xorg_RandR_1.2<br />
* http://wiki.debian.org/XStrikeForce/HowToRandR12<br />
* man aticonfig<br />
* One of the [[Ubuntu]] guides on this Wiki.<br />
* AMD's own Catalyst documentation<br />
<br />
If you need to start with a clean slate and all your monitors are connected, you can do the following to force a fresh xorg.conf to be generated taking into account the monitors present:<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
== Pre-built packages from RPMFusion ==<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous Offical AMD driver installation ===<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Official AMD Driver ==<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds the kernel module and a set of modules for XOrg. The Official AMD installer requires some development packages to be installed:<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
We'll also want to remove any kernel-devel packages from old versions of the kernel. Check your current kernel version with:<br />
<br />
<pre><br />
uname -a<br />
</pre><br />
<br />
Check all installed kernel packages with<br />
<br />
<pre><br />
su -<br />
rpm -qa | grep kernel<br />
</pre><br />
<br />
Remove any ''kernel-devel'' packages which do not match the latest kernel version. For example:<br />
<br />
<pre><br />
su -<br />
yum remove kernel-devel-3.2.9-1.fc16.x86_64<br />
</pre><br />
<br />
Note we are careful to specify the exact package name that was given to us by the rpm command above.<br />
<br />
Boot into the latest kernel before continuing. Building the module on a kernel which you don't have ''-devel'' packages for will fail. Building the module on one kernel then booting into another will result in the compiled module not working.<br />
<br />
=== Download driver ===<br />
<br />
Download the driver for your particular card from http://support.amd.com/<br />
<br />
It will look similar to: ''amd-driver-installer-XX-X-XXX.XXX_XX.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
sh ./amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log:<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked:<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Uninstalling Official AMD driver ===<br />
<br />
Run AMD's uninstall script:<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/fglrx-uninstall.sh<br />
</pre><br />
<br />
The following steps are not strictly required because the amd-driver-installer is written to put all files back as they were before the install. One set of files that amd-driver-installer alters is the mesa library set. To be sure of a mint-condition installation (especially if you are upgrading to the next Official driver version) reinstall the following package:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
For those running Wine or Crossover from Codeweavers.com, the following command will reinstall all the mesa libraries that (should) be on your system. This example is for users running Wine/Crossover on a 64 bit system:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-dri-filesystem.i686 mesa-libGL.x86_64 mesa-dri-drivers.x86_64 mesa-libGL.i686 mesa-dri-filesystem.x86_64 mesa-libEGL.x86_64 mesa-dri-drivers.i686 mesa-libGLU.x86_64<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 rdblacklist=radeon blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''rdblacklist=radeon blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8260Fedora 16 Installation Guide2012-03-22T11:41:39Z<p>Super Jamie: </p>
<hr />
<div>= Two Driver Choices =<br />
<br />
There are two video drivers you can choose to run your ATI video card, one is called ''radeon'', the other is ''fglrx''.<br />
<br />
=== radeon - the in-kernel driver ===<br />
<br />
This is the Free Software driver included in the mainline Linux kernel. This driver is written by an open source community with no access to the hardware specs and is released under the GNU GPL. If software freedom is your main concern, this is the driver for you.<br />
<br />
Historically, the ''radeon'' driver couldn't do much, not even 2D acceleration. However, in Fedora 16's 3.1 and 3.2 kernels this driver is making real progress. It now supports 2D compositing, many 3D functions such as GLSL and Pixel Shaders, as well as other useful features like Kernel Mode Setting. There is currently a large push in graphics driver development upstream in the kernel, so this driver's expected to get even better in kernels 3.3 and 3.4.<br />
<br />
The ''radeon'' driver packaged with Fedora 16 will easily run desktop compositing (eg: gnome-shell, compiz, transparent terminal). It manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine, ''OpenArena'' Quake 3 engine) with no problems. Depending on your CPU, constant 45fps in 1080p ''Minecraft'' is easily doable.<br />
<br />
You can read more about the radeon driver at [[http://www.x.org/wiki/radeon]]. You can also find a [http://www.x.org/wiki/RadeonFeature list of supported features] and [http://www.x.org/wiki/RadeonProgram list of supported software] if you'd like to investigate using this driver.<br />
<br />
It's worth noting that 2D performance is actually better in this driver than the proprietary driver. If you're only using Gnome 3 and typical Linux games, or not playing games at all, or wish to extend your laptop's battery life, this is probably your best choice.<br />
<br />
=== fglrx - the AMD-supplied driver ===<br />
<br />
This is the driver written and distributed by ATI, who have full access to the internal specs of the hardware, so can make a full-featured driver which supports all the capabilities of the hardware. The driver consists of a small kernel module which acts as a loader for the actual driver, which is distributed as a closed-source "[http://en.wikipedia.org/wiki/Binary_blob binary blob]".<br />
<br />
''fglrx'' was originally written only for ATI's FireGL professional workstation cards (targeting the same market as nVidia's Quadro range) however it was soon expanded to include almost the whole ATI range. AMD continue to extend the driver after their acquisition of ATI. This driver also includes the ''Catalyst Control Center'' tool for configuring features like forcing anti-aliasing and anistropic filtering on for all OpenGL processing.<br />
<br />
If you are running newer games, such as most things you'd get off Steam, ''fglrx'' is probably going to be your best choice. If you have a game which produces graphical glitches under the Free driver, it's worth trying this driver to see if the game works. Generally, performance in all 3D games and 3D applications will be measurably improved with this driver. As mentioned above, 2D performance is actually worse than the Free driver, though it's definitely fine for day-to-day desktop use.<br />
<br />
Each driver as pros and cons, try both and see which is most suitable for your needs. The best thing about Linux is the choice to run whatever software components you like.<br />
<br />
= Installing the AMD-supplied driver =<br />
<br />
== Requirements ==<br />
<br />
The AMD-supplied driver 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.<br />
<br />
You will need version 11.11 of the ATI driver or later for Fedora 16, earlier versions will not work with the version of XOrg that F16 ships with.<br />
<br />
You require a Radeon HD2000 series or better to use the latest AMD-supplied driver.<br />
<br />
=== kernel-3.2.9-2.fc16 and onwards ===<br />
<br />
Due to an upstream sourcecode change in the Fedora ''kernel-headers'' package, building of AMD's ''fglrx'' module will currently fail with kernels 3.2.9-2.fc16 and later.<br />
<br />
To fix this, we can revert a small edit. Open the file '''/usr/src/kernels/3.2.9-2.fc16.x86_64/arch/x86/include/asm/uaccess_64.h''' in a text editor.<br />
<br />
On line 56 and 57 you will see:<br />
<br />
<pre><br />
else<br />
WARN(1, "Buffer overflow detected!\n");<br />
</pre><br />
<br />
Comment this out so it reads:<br />
<br />
<pre><br />
// else<br />
// WARN(1, "Buffer overflow detected!\n"); <br />
</pre><br />
<br />
Your AMD kernel module will now build correctly.<br />
<br />
* Reference: http://forums.fedoraforum.org/showthread.php?t=277547<br />
<br />
=== Multiple Monitor Setups ===<br />
<br />
If you have an existing multiple monitor setup, follow one of the install procedures, then transfer relevant sections of your old xorg.conf into the new version generated with aticonfig if required.<br />
<br />
There are some excellent resource pages for those who are having difficulty in getting their multiple monitor setups running:<br />
<br />
* http://www.thinkwiki.org/wiki/Xorg_RandR_1.2<br />
* http://wiki.debian.org/XStrikeForce/HowToRandR12<br />
* man aticonfig<br />
* One of the [[Ubuntu]] guides on this Wiki.<br />
* AMD's own Catalyst documentation<br />
<br />
If you need to start with a clean slate and all your monitors are connected, you can do the following to force a fresh xorg.conf to be generated taking into account the monitors present:<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
== Pre-built packages from RPMFusion ==<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous Offical AMD driver installation ===<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Official AMD Driver ==<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds the kernel module and a set of modules for XOrg. The Official AMD installer requires some development packages to be installed:<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
We'll also want to remove any kernel-devel packages from old versions of the kernel. Check your current kernel version with:<br />
<br />
<pre><br />
uname -a<br />
</pre><br />
<br />
Check all installed kernel packages with<br />
<br />
<pre><br />
su -<br />
rpm -qa | grep kernel<br />
</pre><br />
<br />
Remove any ''kernel-devel'' packages which do not match the latest kernel version. For example:<br />
<br />
<pre><br />
su -<br />
yum remove kernel-devel-3.2.9-1.fc16.x86_64<br />
</pre><br />
<br />
Note we are careful to specify the exact package name that was given to us by the rpm command above.<br />
<br />
Boot into the latest kernel before continuing. Building the module on a kernel which you don't have ''-devel'' packages for will fail. Building the module on one kernel then booting into another will result in the compiled module not working.<br />
<br />
=== Download driver ===<br />
<br />
Download the driver for your particular card from http://support.amd.com/<br />
<br />
It will look similar to: ''amd-driver-installer-XX-X-XXX.XXX_XX.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
sh ./amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log:<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked:<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Uninstalling Official AMD driver ===<br />
<br />
Run AMD's uninstall script:<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/fglrx-uninstall.sh<br />
</pre><br />
<br />
The following steps are not strictly required because the amd-driver-installer is written to put all files back as they were before the install. One set of files that amd-driver-installer alters is the mesa library set. To be sure of a mint-condition installation (especially if you are upgrading to the next Official driver version) reinstall the following package:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
For those running Wine or Crossover from Codeweavers.com, the following command will reinstall all the mesa libraries that (should) be on your system. This example is for users running Wine/Crossover on a 64 bit system:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-dri-filesystem.i686 mesa-libGL.x86_64 mesa-dri-drivers.x86_64 mesa-libGL.i686 mesa-dri-filesystem.x86_64 mesa-libEGL.x86_64 mesa-dri-drivers.i686 mesa-libGLU.x86_64<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 rdblacklist=radeon blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''rdblacklist=radeon blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8259Fedora 16 Installation Guide2012-03-22T11:41:22Z<p>Super Jamie: </p>
<hr />
<div>= Two Driver Choices =<br />
<br />
There are two video drivers you can choose to run your ATI video card, one is called ''radeon'', the other is ''fglrx''.<br />
<br />
=== radeon - the in-kernel driver ===<br />
<br />
This is the Free Software driver included in the mainline Linux kernel. This driver is written by an open source community with no access to the hardware specs and is released under the GNU GPL. If software freedom is your main concern, this is the driver for you.<br />
<br />
Historically, the ''radeon'' driver couldn't do much, not even 2D acceleration. However, in Fedora 16's 3.1 and 3.2 kernels this driver is making real progress. It now supports 2D compositing, many 3D functions such as GLSL and Pixel Shaders, as well as other useful features like Kernel Mode Setting. There is currently a large push in graphics driver development upstream in the kernel, so this driver's expected to get even better in kernels 3.3 and 3.4.<br />
<br />
The ''radeon'' driver packaged with Fedora 16 will easily run desktop compositing (eg: gnome-shell, compiz, transparent terminal). It manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine, ''OpenArena'' Quake 3 engine) with no problems. Depending on your CPU, constant 45fps in 1080p ''Minecraft'' is easily doable.<br />
<br />
You can read more about the radeon driver at [[http://www.x.org/wiki/radeon]]. You can also find a [http://www.x.org/wiki/RadeonFeature list of supported features] and [http://www.x.org/wiki/RadeonProgram list of supported software] if you'd like to investigate using this driver.<br />
<br />
It's worth noting that 2D performance is actually better in this driver than the proprietary driver. If you're only using Gnome 3 and typical Linux games, or not playing games at all, or wish to extend your laptop's battery life, this is probably your best choice.<br />
<br />
=== fglrx - the AMD-supplied driver ===<br />
<br />
This is the driver written and distributed by ATI, who have full access to the internal specs of the hardware, so can make a full-featured driver which supports all the capabilities of the hardware. The driver consists of a small kernel module which acts as a loader for the actual driver, which is distributed as a closed-source "[http://en.wikipedia.org/wiki/Binary_blob | binary blob]".<br />
<br />
''fglrx'' was originally written only for ATI's FireGL professional workstation cards (targeting the same market as nVidia's Quadro range) however it was soon expanded to include almost the whole ATI range. AMD continue to extend the driver after their acquisition of ATI. This driver also includes the ''Catalyst Control Center'' tool for configuring features like forcing anti-aliasing and anistropic filtering on for all OpenGL processing.<br />
<br />
If you are running newer games, such as most things you'd get off Steam, ''fglrx'' is probably going to be your best choice. If you have a game which produces graphical glitches under the Free driver, it's worth trying this driver to see if the game works. Generally, performance in all 3D games and 3D applications will be measurably improved with this driver. As mentioned above, 2D performance is actually worse than the Free driver, though it's definitely fine for day-to-day desktop use.<br />
<br />
Each driver as pros and cons, try both and see which is most suitable for your needs. The best thing about Linux is the choice to run whatever software components you like.<br />
<br />
= Installing the AMD-supplied driver =<br />
<br />
== Requirements ==<br />
<br />
The AMD-supplied driver 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.<br />
<br />
You will need version 11.11 of the ATI driver or later for Fedora 16, earlier versions will not work with the version of XOrg that F16 ships with.<br />
<br />
You require a Radeon HD2000 series or better to use the latest AMD-supplied driver.<br />
<br />
=== kernel-3.2.9-2.fc16 and onwards ===<br />
<br />
Due to an upstream sourcecode change in the Fedora ''kernel-headers'' package, building of AMD's ''fglrx'' module will currently fail with kernels 3.2.9-2.fc16 and later.<br />
<br />
To fix this, we can revert a small edit. Open the file '''/usr/src/kernels/3.2.9-2.fc16.x86_64/arch/x86/include/asm/uaccess_64.h''' in a text editor.<br />
<br />
On line 56 and 57 you will see:<br />
<br />
<pre><br />
else<br />
WARN(1, "Buffer overflow detected!\n");<br />
</pre><br />
<br />
Comment this out so it reads:<br />
<br />
<pre><br />
// else<br />
// WARN(1, "Buffer overflow detected!\n"); <br />
</pre><br />
<br />
Your AMD kernel module will now build correctly.<br />
<br />
* Reference: http://forums.fedoraforum.org/showthread.php?t=277547<br />
<br />
=== Multiple Monitor Setups ===<br />
<br />
If you have an existing multiple monitor setup, follow one of the install procedures, then transfer relevant sections of your old xorg.conf into the new version generated with aticonfig if required.<br />
<br />
There are some excellent resource pages for those who are having difficulty in getting their multiple monitor setups running:<br />
<br />
* http://www.thinkwiki.org/wiki/Xorg_RandR_1.2<br />
* http://wiki.debian.org/XStrikeForce/HowToRandR12<br />
* man aticonfig<br />
* One of the [[Ubuntu]] guides on this Wiki.<br />
* AMD's own Catalyst documentation<br />
<br />
If you need to start with a clean slate and all your monitors are connected, you can do the following to force a fresh xorg.conf to be generated taking into account the monitors present:<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
== Pre-built packages from RPMFusion ==<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous Offical AMD driver installation ===<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Official AMD Driver ==<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds the kernel module and a set of modules for XOrg. The Official AMD installer requires some development packages to be installed:<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
We'll also want to remove any kernel-devel packages from old versions of the kernel. Check your current kernel version with:<br />
<br />
<pre><br />
uname -a<br />
</pre><br />
<br />
Check all installed kernel packages with<br />
<br />
<pre><br />
su -<br />
rpm -qa | grep kernel<br />
</pre><br />
<br />
Remove any ''kernel-devel'' packages which do not match the latest kernel version. For example:<br />
<br />
<pre><br />
su -<br />
yum remove kernel-devel-3.2.9-1.fc16.x86_64<br />
</pre><br />
<br />
Note we are careful to specify the exact package name that was given to us by the rpm command above.<br />
<br />
Boot into the latest kernel before continuing. Building the module on a kernel which you don't have ''-devel'' packages for will fail. Building the module on one kernel then booting into another will result in the compiled module not working.<br />
<br />
=== Download driver ===<br />
<br />
Download the driver for your particular card from http://support.amd.com/<br />
<br />
It will look similar to: ''amd-driver-installer-XX-X-XXX.XXX_XX.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
sh ./amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log:<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked:<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Uninstalling Official AMD driver ===<br />
<br />
Run AMD's uninstall script:<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/fglrx-uninstall.sh<br />
</pre><br />
<br />
The following steps are not strictly required because the amd-driver-installer is written to put all files back as they were before the install. One set of files that amd-driver-installer alters is the mesa library set. To be sure of a mint-condition installation (especially if you are upgrading to the next Official driver version) reinstall the following package:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
For those running Wine or Crossover from Codeweavers.com, the following command will reinstall all the mesa libraries that (should) be on your system. This example is for users running Wine/Crossover on a 64 bit system:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-dri-filesystem.i686 mesa-libGL.x86_64 mesa-dri-drivers.x86_64 mesa-libGL.i686 mesa-dri-filesystem.x86_64 mesa-libEGL.x86_64 mesa-dri-drivers.i686 mesa-libGLU.x86_64<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 rdblacklist=radeon blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''rdblacklist=radeon blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8258Fedora 16 Installation Guide2012-03-22T11:39:40Z<p>Super Jamie: expanded driver choice, re-organised a few bits from the previous editor, removed dracut steps as per your talk page</p>
<hr />
<div>= Two Driver Choices =<br />
<br />
There are two video drivers you can choose to run your ATI video card, one is called ''radeon'', the other is ''fglrx''.<br />
<br />
=== radeon - the in-kernel driver ===<br />
<br />
This is the Free Software driver included in the mainline Linux kernel. This driver is written by an open source community with no access to the hardware specs and is released under the GNU GPL. If software freedom is your main concern, this is the driver for you.<br />
<br />
Historically, the ''radeon'' driver couldn't do much, not even 2D acceleration. However, in Fedora 16's 3.1 and 3.2 kernels this driver is making real progress. It now supports 2D compositing, many 3D functions such as GLSL and Pixel Shaders, as well as other useful features like Kernel Mode Setting. There is currently a large push in graphics driver development upstream in the kernel, so this driver's expected to get even better in kernels 3.3 and 3.4.<br />
<br />
The ''radeon'' driver packaged with Fedora 16 will easily run desktop compositing (eg: gnome-shell, compiz, transparent terminal). It manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine, ''OpenArena'' Quake 3 engine) with no problems. Depending on your CPU, constant 45fps in 1080p ''Minecraft'' is easily doable.<br />
<br />
You can read more about the radeon driver at [[http://www.x.org/wiki/radeon]]. You can also find a [http://www.x.org/wiki/RadeonFeature | list of supported features] and [http://www.x.org/wiki/RadeonProgram | list of supported software] if you'd like to investigate using this driver.<br />
<br />
It's worth noting that 2D performance is actually better in this driver than the proprietary driver. If you're only using Gnome 3 and typical Linux games, or not playing games at all, or wish to extend your laptop's battery life, this is probably your best choice.<br />
<br />
=== fglrx - the AMD-supplied driver ===<br />
<br />
This is the driver written and distributed by ATI, who have full access to the internal specs of the hardware, so can make a full-featured driver which supports all the capabilities of the hardware. The driver consists of a small kernel module which acts as a loader for the actual driver, which is distributed as a closed-source "[http://en.wikipedia.org/wiki/Binary_blob | binary blob]".<br />
<br />
''fglrx'' was originally written only for ATI's FireGL professional workstation cards (targeting the same market as nVidia's Quadro range) however it was soon expanded to include almost the whole ATI range. AMD continue to extend the driver after their acquisition of ATI. This driver also includes the ''Catalyst Control Center'' tool for configuring features like forcing anti-aliasing and anistropic filtering on for all OpenGL processing.<br />
<br />
If you are running newer games, such as most things you'd get off Steam, ''fglrx'' is probably going to be your best choice. If you have a game which produces graphical glitches under the Free driver, it's worth trying this driver to see if the game works. Generally, performance in all 3D games and 3D applications will be measurably improved with this driver. As mentioned above, 2D performance is actually worse than the Free driver, though it's definitely fine for day-to-day desktop use.<br />
<br />
Each driver as pros and cons, try both and see which is most suitable for your needs. The best thing about Linux is the choice to run whatever software components you like.<br />
<br />
= Installing the AMD-supplied driver =<br />
<br />
== Requirements ==<br />
<br />
The AMD-supplied driver 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.<br />
<br />
You will need version 11.11 of the ATI driver or later for Fedora 16, earlier versions will not work with the version of XOrg that F16 ships with.<br />
<br />
You require a Radeon HD2000 series or better to use the latest AMD-supplied driver.<br />
<br />
=== kernel-3.2.9-2.fc16 and onwards ===<br />
<br />
Due to an upstream sourcecode change in the Fedora ''kernel-headers'' package, building of AMD's ''fglrx'' module will currently fail with kernels 3.2.9-2.fc16 and later.<br />
<br />
To fix this, we can revert a small edit. Open the file '''/usr/src/kernels/3.2.9-2.fc16.x86_64/arch/x86/include/asm/uaccess_64.h''' in a text editor.<br />
<br />
On line 56 and 57 you will see:<br />
<br />
<pre><br />
else<br />
WARN(1, "Buffer overflow detected!\n");<br />
</pre><br />
<br />
Comment this out so it reads:<br />
<br />
<pre><br />
// else<br />
// WARN(1, "Buffer overflow detected!\n"); <br />
</pre><br />
<br />
Your AMD kernel module will now build correctly.<br />
<br />
* Reference: http://forums.fedoraforum.org/showthread.php?t=277547<br />
<br />
=== Multiple Monitor Setups ===<br />
<br />
If you have an existing multiple monitor setup, follow one of the install procedures, then transfer relevant sections of your old xorg.conf into the new version generated with aticonfig if required.<br />
<br />
There are some excellent resource pages for those who are having difficulty in getting their multiple monitor setups running:<br />
<br />
* http://www.thinkwiki.org/wiki/Xorg_RandR_1.2<br />
* http://wiki.debian.org/XStrikeForce/HowToRandR12<br />
* man aticonfig<br />
* One of the [[Ubuntu]] guides on this Wiki.<br />
* AMD's own Catalyst documentation<br />
<br />
If you need to start with a clean slate and all your monitors are connected, you can do the following to force a fresh xorg.conf to be generated taking into account the monitors present:<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
== Pre-built packages from RPMFusion ==<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous Offical AMD driver installation ===<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
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.<br />
<br />
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.<br />
<br />
== Official AMD Driver ==<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds the kernel module and a set of modules for XOrg. The Official AMD installer requires some development packages to be installed:<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
We'll also want to remove any kernel-devel packages from old versions of the kernel. Check your current kernel version with:<br />
<br />
<pre><br />
uname -a<br />
</pre><br />
<br />
Check all installed kernel packages with<br />
<br />
<pre><br />
su -<br />
rpm -qa | grep kernel<br />
</pre><br />
<br />
Remove any ''kernel-devel'' packages which do not match the latest kernel version. For example:<br />
<br />
<pre><br />
su -<br />
yum remove kernel-devel-3.2.9-1.fc16.x86_64<br />
</pre><br />
<br />
Note we are careful to specify the exact package name that was given to us by the rpm command above.<br />
<br />
Boot into the latest kernel before continuing. Building the module on a kernel which you don't have -devel packages for will fail. Building the module on one kernel then booting into another will result in the module not working.<br />
<br />
=== Download driver ===<br />
<br />
Download the driver for your particular card from http://support.amd.com/<br />
<br />
It will look similar to: ''amd-driver-installer-XX-X-XXX.XXX_XX.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
sh ./amd-driver-installer-XX-X-XXX.XXX_XX.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log:<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked:<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Uninstalling Official AMD driver ===<br />
<br />
Run AMD's uninstall script:<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/fglrx-uninstall.sh<br />
</pre><br />
<br />
The following steps are not strictly required because the amd-driver-installer is written to put all files back as they were before the install. One set of files that amd-driver-installer alters is the mesa library set. To be sure of a mint-condition installation (especially if you are upgrading to the next Official driver version) reinstall the following package:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
For those running Wine or Crossover from Codeweavers.com, the following command will reinstall all the mesa libraries that (should) be on your system. This example is for users running Wine/Crossover on a 64 bit system:<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-dri-filesystem.i686 mesa-libGL.x86_64 mesa-dri-drivers.x86_64 mesa-libGL.i686 mesa-dri-filesystem.x86_64 mesa-libEGL.x86_64 mesa-dri-drivers.i686 mesa-libGLU.x86_64<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 rdblacklist=radeon blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''rdblacklist=radeon blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=User:Super_Jamie&diff=8257User:Super Jamie2012-03-22T11:03:14Z<p>Super Jamie: Created page with "<pre>jamie at superjamie dot net</pre>"</p>
<hr />
<div><pre>jamie at superjamie dot net</pre></div>Super Jamiehttp://wiki.cchtml.com/index.php?title=User_talk:67.239.165.48&diff=8256User talk:67.239.165.482012-03-22T11:02:40Z<p>Super Jamie: </p>
<hr />
<div>* I don't know who's editing the Fedora 16 Fglrx page, but the first paragraph titled "Please Consider" was originally written evidently to push a particular license (GPL) rather than present procedures and solutions. I've edited that to make it somewhat neutral but someone seems intent on pushing radeon first. Besides the fact that radeon is already the default installed driver on most distros, there isn't really a need to mention radeon at all other than to state that it exists, since a procedure is generally not needed for radeon installation. That makes a radeon driver discussion redundant unless you are pushing GPL. IMO this site should not be used for pimping licenses but rather for presenting solutions.<br />
<br />
** That's me, check the history. I actually like your idea of presenting two driver options and I've written a more impartial overview of each driver. I see you're still editing so I'll wait till you're done to apply it. I also disagree with some things you've stated: The broken module compilation is fixed with a two-line sourcecode comment, we should include the fix rather that just say "it's busted", I'm using fglrx on 3.2.9-2 fine. I'm also completely removing your dracut step, this is far too complex for a regular user who doesn't understand initramfs, it also leaves the system in a state where it may not actually have a graphics driver if fglrx stuffs up. Blacklisting on the kernel line is sufficient and is what the RPMFusion RPM scripts and the Official installation script do anyway. --[[User:Super Jamie|Super Jamie]] 06:02, 22 March 2012 (CDT)</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Help:Editing&diff=8255Help:Editing2012-03-22T10:18:03Z<p>Super Jamie: Created page with "[http://meta.wikimedia.org/wiki/MediaWiki_User%27s_Guide:_Editing_overview MediaWiki User's Guide: Editing overview]"</p>
<hr />
<div>[http://meta.wikimedia.org/wiki/MediaWiki_User%27s_Guide:_Editing_overview MediaWiki User's Guide: Editing overview]</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8233Fedora 16 Installation Guide2012-03-22T07:21:20Z<p>Super Jamie: hooray edit war! feel free to discuss on the talk page</p>
<hr />
<div>= Please consider =<br />
<br />
The Free Software ''radeon'' driver is making real progress in F16's kernel 3.1 and 3.2, it's expected to get even better in kernel 3.3 and 3.4.<br />
<br />
The kernel 3.1 driver will easily run desktop compositing (eg: ''gnome-shell'', transparent terminal). It even manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine) with no problems. Depending on your CPU, constant 45fps in 1080p Minecraft is easily doable.<br />
<br />
It is true that the AMD-supplied driver is the only real choice for running newer games, such as most things you'd buy through Steam, however the Free driver is more than capable for everyday desktop needs such as compositing and most native Linux games. Please research and test your requirements, and consider using the Free Software ''radeon'' driver before installing ATI's non-Free proprietary ''flgrx'' driver.<br />
<br />
= Pre-built packages from RPMFusion =<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous AMD-supplied driver installation ===<br />
<br />
If you're coming from the AMD-supplied driver to RPMFusion's driver, you'll need to reinstall this package as the AMD driver installation changes files it contains.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
Note that there are individual ''kmod-catalyst-'' packages which supply kernel modules for specific Fedora kernel versions. If you are using 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 package.<br />
<br />
The ''akmod-catalyst'' package we installed above automatically builds a new kernel module at boot-time when the kernel is upgraded, so you never have to worry about this.<br />
<br />
= Official AMD Driver =<br />
<br />
=== Requirements ===<br />
<br />
At F16's release, the ATI driver did not support the version of X.Org that Fedora shipped with. This has been resolved in Catalyst 11.11 onwards. You will need version 11.11 of the ATI driver or later for F16, earlier versions will not work.<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds a kernel module which loads AMD's proprietary binary blob, so we're going to install some development packages.<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
If you're on 64-bit you may also have to install this package too.<br />
(''you need this for 64-bit nVidia drivers so I had it installed anyway, could someone please confirm/deny this requirement?'')<br />
<br />
<pre><br />
su -c<br />
yum install glibc-devel<br />
</pre><br />
<br />
=== Download driver ===<br />
<br />
Download the appropriate driver from http://support.amd.com/<br />
<br />
It will be called something like ''ati-driver-installer-version.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x ati-driver-installer-version.run<br />
sh ./ati-driver-installer-version.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log.<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked.<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Generate a new xorg.conf ===<br />
<br />
This should do fine for most people.<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
If you have multiple monitors or X2 cards then you'll need to do some other stuff. Try ''man aticonfig'', read the Catalyst documentation, or check one of the [[Ubuntu]] guides for the correct syntax.<br />
<br />
=== Uninstalling AMD-supplied driver ===<br />
<br />
Run AMD's uninstall script.<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/amd-uninstall.sh<br />
</pre><br />
<br />
Reinstall this package as the AMD driver installation changes files it contains.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8231Fedora 16 Installation Guide2012-03-21T21:03:26Z<p>Super Jamie: Disagree with the last edit, though made a compromise.</p>
<hr />
<div>= Please consider =<br />
<br />
The Free Software ''radeon'' driver is making real progress in F16's kernel 3.1 and 3.2, it's expected to get even better in kernel 3.3 and 3.4.<br />
<br />
The kernel 3.1 driver will easily run desktop compositing (eg: ''gnome-shell'', transparent terminal). It even manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine) with no problems. Depending on your CPU, constant 45fps in 1080p Minecraft is easily doable.<br />
<br />
It is true that the AMD-supplied driver is the only real choice for running newer games, such as most things you'd buy through Steam, however the Free driver is more than capable for everyday desktop needs such as compositing and most native Linux games. Please research and test your requirements, and consider using the Free Software ''radeon'' driver before installing ATI's non-Free proprietary ''flgrx'' driver.<br />
<br />
= Pre-built packages from RPMFusion =<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous AMD-supplied driver installation ===<br />
<br />
If you're coming from the AMD-supplied driver to RPMFusion's driver, you'll need to reinstall this package as the AMD driver installation changes files it contains.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
Note that there are individual ''kmod-catalyst-'' packages which supply kernel modules for specific Fedora kernel versions. If you are using 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 package.<br />
<br />
The ''akmod-catalyst'' package we installed above automatically builds a new kernel module at boot-time when the kernel is upgraded, so you never have to worry about this.<br />
<br />
= Official AMD Driver =<br />
<br />
=== Requirements ===<br />
<br />
At F16's release, the ATI driver did not support the version of X.Org that Fedora shipped with. This has been resolved in Catalyst 11.11 onwards. You will need version 11.11 of the ATI driver or later for F16, earlier versions will not work.<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds a kernel module which loads AMD's proprietary binary blob, so we're going to install some development packages.<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
If you're on 64-bit you may also have to install this package too.<br />
(''you need this for 64-bit nVidia drivers so I had it installed anyway, could someone please confirm/deny this requirement?'')<br />
<br />
<pre><br />
su -c<br />
yum install glibc-devel<br />
</pre><br />
<br />
=== Download driver ===<br />
<br />
Download the appropriate driver from http://support.amd.com/<br />
<br />
It will be called something like ''ati-driver-installer-version.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x ati-driver-installer-version.run<br />
sh ./ati-driver-installer-version.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log.<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked.<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Generate a new xorg.conf ===<br />
<br />
This should do fine for most people.<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
If you have multiple monitors or X2 cards then you'll need to do some other stuff. Try ''man aticonfig'', read the Catalyst documentation, or check one of the [[Ubuntu]] guides for the correct syntax.<br />
<br />
=== Uninstalling AMD-supplied driver ===<br />
<br />
Run AMD's uninstall script.<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/amd-uninstall.sh<br />
</pre><br />
<br />
Reinstall this package as the AMD driver installation changes files it contains.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8222Fedora 16 Installation Guide2012-03-11T00:35:25Z<p>Super Jamie: </p>
<hr />
<div>= Please consider =<br />
<br />
The Free Software ''radeon'' driver is making real progress in F16's kernel 3.1 and 3.2, it's expected to get even better in kernel 3.3 and 3.4.<br />
<br />
The kernel 3.1 driver will easily run desktop compositing (eg: ''gnome-shell'', transparent terminal). It even manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine) with no problems. Depending on your CPU, constant 45fps in 1080p Minecraft is easily doable.<br />
<br />
Please test your requirements and consider using the Free Software ''radeon'' driver before installing ATI's non-Free proprietary ''flgrx'' driver.<br />
<br />
= Pre-built packages from RPMFusion =<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous AMD-supplied driver installation ===<br />
<br />
If you're coming from the AMD-supplied driver to RPMFusion's driver, you'll need to reinstall this package as the AMD driver installation changes files it contains.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
Note that there are individual ''kmod-catalyst-'' packages which supply kernel modules for specific Fedora kernel versions. If you are using 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 package.<br />
<br />
The ''akmod-catalyst'' package we installed above automatically builds a new kernel module at boot-time when the kernel is upgraded, so you never have to worry about this.<br />
<br />
= Official AMD Driver =<br />
<br />
=== Requirements ===<br />
<br />
At F16's release, the ATI driver did not support the version of X.Org that Fedora shipped with. This has been resolved in Catalyst 11.11 onwards. You will need version 11.11 of the ATI driver or later for F16, earlier versions will not work.<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds a kernel module which loads AMD's proprietary binary blob, so we're going to install some development packages.<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
If you're on 64-bit you may also have to install this package too.<br />
(''you need this for 64-bit nVidia drivers so I had it installed anyway, could someone please confirm/deny this requirement?'')<br />
<br />
<pre><br />
su -c<br />
yum install glibc-devel<br />
</pre><br />
<br />
=== Download driver ===<br />
<br />
Download the appropriate driver from http://support.amd.com/<br />
<br />
It will be called something like ''ati-driver-installer-version.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x ati-driver-installer-version.run<br />
sh ./ati-driver-installer-version.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log.<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked.<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Generate a new xorg.conf ===<br />
<br />
This should do fine for most people.<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
If you have multiple monitors or X2 cards then you'll need to do some other stuff. Try ''man aticonfig'', read the Catalyst documentation, or check one of the [[Ubuntu]] guides for the correct syntax.<br />
<br />
=== Uninstalling AMD-supplied driver ===<br />
<br />
Run AMD's uninstall script.<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/amd-uninstall.sh<br />
</pre><br />
<br />
Reinstall this package as the AMD driver installation changes files it contains.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8221Fedora 16 Installation Guide2012-03-11T00:34:49Z<p>Super Jamie: </p>
<hr />
<div>= Please consider =<br />
<br />
The Free Software ''radeon'' driver is making real progress in F16's kernel 3.1 and 3.2, it's expected to get even better in kernel 3.3 and 3.4.<br />
<br />
The kernel 3.1 driver will easily run desktop compositing (eg: ''gnome-shell'', transparent terminal). It even manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine) with no problems. Depending on your CPU, constant 45fps in 1080p Minecraft is easily doable.<br />
<br />
Please test your requirements and consider using the Free Software ''radeon'' driver before installing ATI's non-Free proprietary ''flgrx'' driver.<br />
<br />
= Pre-built packages from RPMFusion =<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous AMD-supplied driver installation ===<br />
<br />
If you're coming from the AMD-supplied driver to RPMFusion's driver, you'll need to reinstall this package as the AMD driver installation changes files it contains.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' 32-bit Libraries on 64-bit OS'''<br />
<br />
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.<br />
<br />
<pre><br />
su -<br />
yum install xorg-x11-drv-catalyst-libs.i686<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
Note that there are individual ''kmod-catalyst-'' packages which supply kernel modules for specific Fedora kernel versions. If you are using 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 package.<br />
<br />
The ''akmod-catalyst'' package we installed above automatically builds a new kernel module at boot-time when the kernel is upgraded, so you never have to worry about this.<br />
<br />
= Official AMD Driver =<br />
<br />
=== Requirements ===<br />
<br />
At F16's release, the ATI driver did not support the version of X.Org that Fedora shipped with. This has been resolved in Catalyst 11.11 onwards. You will need version 11.11 of the ATI driver or later for F16, earlier versions will not work.<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds a kernel module which loads AMD's proprietary binary blob, so we're going to install some development packages.<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
If you're on 64-bit you may also have to install this package too.<br />
(''you need this for 64-bit nVidia drivers so I had it installed anyway, could someone please confirm/deny this requirement?'')<br />
<br />
<pre><br />
su -c<br />
yum install glibc-devel<br />
</pre><br />
<br />
=== Download driver ===<br />
<br />
Download the appropriate driver from http://support.amd.com/<br />
<br />
It will be called something like ''ati-driver-installer-version.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x ati-driver-installer-version.run<br />
sh ./ati-driver-installer-version.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log.<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked.<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Generate a new xorg.conf ===<br />
<br />
This should do fine for most people.<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
If you have multiple monitors or X2 cards then you'll need to do some other stuff. Try ''man aticonfig'', read the Catalyst documentation, or check one of the [[Ubuntu]] guides for the correct syntax.<br />
<br />
=== Uninstalling AMD-supplied driver ===<br />
<br />
Run AMD's uninstall script.<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/amd-uninstall.sh<br />
</pre><br />
<br />
Reinstall this package as the AMD driver installation changes files it contains.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
= Troubleshooting =<br />
<br />
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.<br />
<br />
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.<br />
<br />
Add the entries '''radeon.modeset=0 blacklist=radeon 3''' to the end. For example, if your kernel line is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8</pre><br />
<br />
we'll want to edit it so it is<br />
<br />
<pre>linux /vmlinuz-3.2.9-1.fc16.x86_64 LANG=en_US.UTF-8 radeon.modeset=0 blacklist=radeon</pre><br />
<br />
These entries do the following:<br />
* '''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)<br />
* '''blacklist=radeon''' stops the kernel from loading the Free Software ''radeon'' driver altogether<br />
<br />
From here you can manually remove and reinstall the proprietary drivers, either with yum or with PackageKit's ''Add/Remove Software'' application, as desired.</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora&diff=8060Fedora2012-01-27T15:07:15Z<p>Super Jamie: </p>
<hr />
<div>Fedora is a free, stable and popular general-purpose GNU/Linux distribution developed by the [http://www.fedoraproject.org/ Fedora Project] and sponsored by [http://www.redhat.com Red Hat, Inc].<br />
<br />
== Overview ==<br />
<br />
When Red Hat discontinued Red Hat Linux in 2003, the RHL code forked into two branches. One branch is the enterprise distribution called [[Red Hat Enterprise Linux]] which is the central component of Red Hat's business model, the other branch is the general-purpose community distribution called Fedora. The Fedora code is periodically cloned and undergoes added additional refinement for stability, business-readiness and a smaller package base. This matured clone then becomes the next RHEL release.<br />
<br />
Red Hat often use Fedora as a platform for testing public readiness of new features which are eventually destined for RHEL and other Red Hat products. The Fedora Project still maintains a very strict software inclusion policy and testing process, so releases are not "unstable" or "bleeding-edge". Some example features which have migrated from Fedora to RHEL in the past are the yum package manager, NetworkManager and KVM virtualization. Some current testing features are systemd as a replacement for init, and the brtfs filesystem.<br />
<br />
== General Status ==<br />
<br />
* Currently packaged by [http://www.rpmfusion.org/ RPM Fusion].<br />
* Older versions (FC9 and earlier) were packaged by [http://rpm.livna.org/rlowiki/LivnaSwitcher Thorsten Leemhuis] and [http://freshrpms.net/ Matthias Saou].<br />
* Official AMD/ATI binary package available at [http://support.amd.com/ support.amd.com].<br />
<br />
== Installation ==<br />
<br />
'''Current maintenance cycle'''<br />
<br />
*[[Fedora 16 Installation Guide]]<br />
*[[Fedora 15 Installation Guide]]<br />
<br />
'''Maintenance cycle ended'''<br />
<br />
*[[Fedora 14 Installation Guide]]<br />
*[[Fedora 13 Installation Guide]]<br />
*[[Fedora 12 Installation Guide]]<br />
*[[Fedora 11 Installation Guide]]<br />
*[[Fedora 10 Installation Guide]]<br />
*[[Fedora 9 Installation Guide]]<br />
*[[Fedora 8 Installation Guide]]<br />
*[[Fedora 7 Installation Guide]]<br />
*[[Fedora Core 6 Installation Guide]]<br />
*[[Fedora Core 5 Installation Guide]]<br />
*[[Fedora Core 4 Installation Guide]]<br />
<br />
== Related Links ==<br />
<br />
* [http://fedoraproject.org/ Fedora Project] - the community who develop the Fedora distribution<br />
* [http://en.wikipedia.org/wiki/Fedora_%28operating_system%29 Fedora (operating system)] - from Wikipedia, the free encyclopedia<br />
* [http://distrowatch.com/fedora DistroWatch.com: Fedora] - Third most popular distro for a very long time<br />
* [http://www.phoronix.com/forums/forumdisplay.php?19-AMD-ATI-Linux Phoronix Forum: AMD/ATI Linux]<br />
<br />
== References ==<br />
<references/><br />
<br />
{{VCT}}<br />
<br />
[[Category: Distributions]]</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora&diff=8059Fedora2012-01-27T15:06:40Z<p>Super Jamie: Added lots about Fedora Project, corrected and expanded relationship to RHL and RHEL</p>
<hr />
<div>Fedora is a free GNU/Linux distribution developed by the [http://www.fedoraproject.org/ Fedora Project] and sponsored by [http://www.redhat.com Red Hat, Inc].<br />
<br />
== Overview ==<br />
<br />
When Red Hat discontinued Red Hat Linux in 2003, the RHL code forked into two branches. One branch is the enterprise distribution called [[Red Hat Enterprise Linux]] which is the central component of Red Hat's business model, the other branch is the general-purpose community distribution called Fedora. The Fedora code is periodically cloned and undergoes added additional refinement for stability, business-readiness and a smaller package base. This matured clone then becomes the next RHEL release.<br />
<br />
Red Hat often use Fedora as a platform for testing public readiness of new features which are eventually destined for RHEL and other Red Hat products. The Fedora Project still maintains a very strict software inclusion policy and testing process, so releases are not "unstable" or "bleeding-edge". Some example features which have migrated from Fedora to RHEL in the past are the yum package manager, NetworkManager and KVM virtualization. Some current testing features are systemd as a replacement for init, and the brtfs filesystem.<br />
<br />
== General Status ==<br />
<br />
* Currently packaged by [http://www.rpmfusion.org/ RPM Fusion].<br />
* Older versions (FC9 and earlier) were packaged by [http://rpm.livna.org/rlowiki/LivnaSwitcher Thorsten Leemhuis] and [http://freshrpms.net/ Matthias Saou].<br />
* Official AMD/ATI binary package available at [http://support.amd.com/ support.amd.com].<br />
<br />
== Installation ==<br />
<br />
'''Current maintenance cycle'''<br />
<br />
*[[Fedora 16 Installation Guide]]<br />
*[[Fedora 15 Installation Guide]]<br />
<br />
'''Maintenance cycle ended'''<br />
<br />
*[[Fedora 14 Installation Guide]]<br />
*[[Fedora 13 Installation Guide]]<br />
*[[Fedora 12 Installation Guide]]<br />
*[[Fedora 11 Installation Guide]]<br />
*[[Fedora 10 Installation Guide]]<br />
*[[Fedora 9 Installation Guide]]<br />
*[[Fedora 8 Installation Guide]]<br />
*[[Fedora 7 Installation Guide]]<br />
*[[Fedora Core 6 Installation Guide]]<br />
*[[Fedora Core 5 Installation Guide]]<br />
*[[Fedora Core 4 Installation Guide]]<br />
<br />
== Related Links ==<br />
<br />
* [http://fedoraproject.org/ Fedora Project] - the community who develop the Fedora distribution<br />
* [http://en.wikipedia.org/wiki/Fedora_%28operating_system%29 Fedora (operating system)] - from Wikipedia, the free encyclopedia<br />
* [http://distrowatch.com/fedora DistroWatch.com: Fedora] - Third most popular distro for a very long time<br />
* [http://www.phoronix.com/forums/forumdisplay.php?19-AMD-ATI-Linux Phoronix Forum: AMD/ATI Linux]<br />
<br />
== References ==<br />
<references/><br />
<br />
{{VCT}}<br />
<br />
[[Category: Distributions]]</div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_16_Installation_Guide&diff=8043Fedora 16 Installation Guide2012-01-25T13:24:44Z<p>Super Jamie: Rewrote guide to nicer standard of old F14 guide. Added radeon plea, intregrated former author's confirmation step and uninstall info.</p>
<hr />
<div>= Please consider =<br />
<br />
The free ''radeon'' driver is making real progress in F16's kernel 3.1 and 3.2, it's expected to get even better in kernel 3.3 and 3.4.<br />
<br />
The kernel 3.1 driver will easily run desktop compositing (eg: ''gnome-shell'', transparent terminal). It even manages 60fps VSync at 1920x1200 in many 3D games (eg: ''Darkplaces'' Quake engine) with no problems. Depending on your CPU, constant 45fps in 1080p Minecraft is easily doable.<br />
<br />
Please test your requirements and consider using the Free Software ''radeon'' driver before installing ATI's non-Free proprietary ''flgrx'' driver.<br />
<br />
= Pre-built packages from RPMFusion =<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
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.<br />
<br />
=== Clean up previous AMD-supplied driver installation ===<br />
<br />
If you're coming from the AMD-supplied driver to RPMFusion's driver, you'll need to reinstall this package as the AMD driver installation changes files it contains.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install Catalyst driver packages ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
''' Kernel module packages '''<br />
<br />
Note that there are individual ''kmod-catalyst-'' packages which supply kernel modules for specific Fedora kernel versions. If you are using 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 package.<br />
<br />
The ''akmod-catalyst'' package we installed above automatically builds a new kernel module at boot-time when the kernel is upgraded, so you never have to worry about this.<br />
<br />
= Offical AMD Driver =<br />
<br />
=== Requirements ===<br />
<br />
At F16's release, the ATI driver did not support the version of X.Org that Fedora shipped with. This has been resolved in Catalyst 11.11 onwards. You will need version 11.11 of the ATI driver or later for F16, earlier versions will not work.<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds a kernel module which loads AMD's proprietary binary blob, so we're going to install some development packages.<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel kernel-headers gcc gcc-c++<br />
</pre><br />
<br />
If you're on 64-bit you may also have to install this package too.<br />
(''you need this for 64-bit nVidia drivers so I had it installed anyway, could someone please confirm/deny this requirement?'')<br />
<br />
<pre><br />
su -c<br />
yum install glibc-devel<br />
</pre><br />
<br />
=== Download driver ===<br />
<br />
Download the appropriate driver from http://support.amd.com/<br />
<br />
It will be called something like ''ati-driver-installer-version.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the ''sh'' shell.<br />
<br />
<pre><br />
su -<br />
chmod +x ati-driver-installer-version.run<br />
sh ./ati-driver-installer-version.run<br />
</pre><br />
<br />
Select the default install, do not generate distribution packages.<br />
<br />
=== Confirming Installation ===<br />
<br />
Check the build install log.<br />
<br />
<pre>tail /usr/share/ati/fglrx-install.log</pre><br />
<br />
You should see data confirming the module build worked.<br />
<br />
<pre>build succeeded with return value 0<br />
duplicating results into driver repository...<br />
done.</pre><br />
<br />
=== Generate a new xorg.conf ===<br />
<br />
This should do fine for most people.<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
If you have multiple monitors or X2 cards then you'll need to do some other stuff. Try ''man aticonfig'', read the Catalyst documentation, or check one of the [[Ubuntu]] guides for the correct syntax.<br />
<br />
=== Uninstalling AMD-supplied driver ===<br />
<br />
Run AMD's uninstall script.<br />
<br />
<pre><br />
su -<br />
sh /usr/share/ati/amd-uninstall.sh<br />
</pre><br />
<br />
Reinstall this package as the AMD driver installation changes files it contains.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre></div>Super Jamiehttp://wiki.cchtml.com/index.php?title=Fedora_14_Installation_Guide&diff=7567Fedora 14 Installation Guide2011-11-05T23:55:18Z<p>Super Jamie: Re-wrote entire page. RPMFusion method verified, copied the AMD install from fedoraforum.org</p>
<hr />
<div>== Pre-built packages from RPMFusion ==<br />
<br />
'''RECOMMENDED METHOD'''<br />
<br />
This is easier than building the driver from AMD as you don't need to worry about passing kernel options via GRUB, configuring DKMS or rebuilding the kernel module every time you do a kernel upgrade.<br />
<br />
=== Clean up previous AMD-supplied driver installation ===<br />
<br />
If you're coming from the AMD-supplied driver to RPMFusion's driver, you'll need to reinstall this package as the AMD driver changes files it contains.<br />
<br />
<pre><br />
su -<br />
yum reinstall mesa-libGL<br />
</pre><br />
<br />
=== Setup RPMFusion ===<br />
<br />
There are instructions on http://www.rpmfusion.org/ but this should do it.<br />
<br />
<pre><br />
su -<br />
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm<br />
</pre><br />
<br />
=== Install AMD driver ===<br />
<br />
This procedure is the same for 32-bit and 64-bit, yum will automatically install the correct driver and libs for your architecture.<br />
<br />
<pre><br />
su -<br />
yum install akmod-catalyst xorg-x11-drv-catalyst xorg-x11-drv-catalyst-libs<br />
</pre><br />
<br />
==== Kernel Modules ====<br />
<br />
Note that there are individual "kmod-catalyst-" packages which supply kernel modules for specific Fedora kernel versions. If you are using these and you upgrade the kernel without upgrading the kmod package, 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 package.<br />
<br />
The "akmod-catalyst" package we install automatically builds a new kernel module at boot-time when the kernel is upgraded, so you never have to worry about this.<br />
<br />
<br />
<br />
= Offical AMD Driver =<br />
<br />
''Note: This procedure is untested.''<br />
<br />
=== Preinstall required packages ===<br />
<br />
The script from AMD builds a kernel module, so we're going to need to install some development packages.<br />
<br />
<pre><br />
su -<br />
yum install kernel-devel gcc<br />
</pre><br />
<br />
If you're on 64-bit you may also have to install this package too. (''you do for 64-bit nVidia drivers so I had it installed anyway'')<br />
<br />
<pre><br />
su -c<br />
yum install glibc-devel<br />
</pre><br />
<br />
=== Download driver ===<br />
<br />
Download the appropriate driver from http://support.amd.com/<br />
<br />
It will be called something like ''ati-driver-installer-version.run''.<br />
<br />
=== Install driver ===<br />
<br />
Run the file as root in the "sh" shell.<br />
<br />
<pre><br />
su -<br />
chmod +x ati-driver-installer-version.run<br />
sh ./ati-driver-installer-version.run<br />
</pre><br />
<br />
=== Generate a new xorg.conf ===<br />
<br />
This should do fine for most people.<br />
<br />
<pre><br />
su -<br />
aticonfig --initial -f<br />
</pre><br />
<br />
If you have multiple monitors or X2 cards then you'll need to do some other stuff, check one of the [[Ubuntu]] guides for the correct syntax.<br />
<br />
=== GRUB boot config ===<br />
<br />
Ensure there's a '''radeon.modeset=0''' entry on the end of your kernel line in '''/boot/grub/menu.lst''' file, you could also use '''nomodeset''' here.<br />
<br />
I expect the AMD install script will do this for you.<br />
<br />
<pre><br />
title Fedora (2.6.35.14-103.fc14.x86_64)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.6.35.14-103.fc14.x86_64 ro root=UUID=blah LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet radeon.modeset=0<br />
initrd /initramfs-2.6.35.14-103.fc14.x86_64.img<br />
</pre></div>Super Jamie