Fedora 13 Installation Guide: Difference between revisions

From cchtml.com
(corrected punctuation, grammar.)
m (Protected "Fedora 13 Installation Guide": Excessive vandalism ([edit=autoconfirmed] (expires 04:32, 16 June 2012 (UTC)) [move=autoconfirmed] (expires 04:32, 16 June 2012 (UTC))))
 
(7 intermediate revisions by 6 users not shown)
Line 1: Line 1:
ATI's latest Catalyst 10.7 now supports Xorg-server 1.8 after our 3-month wait.  Fedora users should of course be used to this.
ATI's latest Catalyst 10.9 now well supports Xorg-server 1.8.


Although 10.7 is designed for OpenSUSE 11.3, it supports all other distros using Xorg 7.6 like Fedora 13 and Ubuntu 10.10.
Pre-built .rpm packages should be in the non-official RPMFusion repository and corresponding version matching 10.9 is now out there. I strongly recommend all of you use this method since it automatically configures the grub config file and configure DKMS settings.


Just download the .run installer, run it using root privileges, follow the instructions on the screen and reboot.
An alternate way is, to download the .run installer, run it using root privileges, follow the instructions on the screen and reboot afterwards. However, you must manually add a 'nomodeset' parameter in the grub entry, or the computer will hang with a black screen after plymouth bootscreen due to a conflict against kernel modesetting and fglrx.
 
Maybe you should add a 'nomodeset' parameter in the grub entry, or you might encounter a black screen hang after plymouth, at least on my laptop.

Latest revision as of 04:32, 16 May 2012

ATI's latest Catalyst 10.9 now well supports Xorg-server 1.8.

Pre-built .rpm packages should be in the non-official RPMFusion repository and corresponding version matching 10.9 is now out there. I strongly recommend all of you use this method since it automatically configures the grub config file and configure DKMS settings.

An alternate way is, to download the .run installer, run it using root privileges, follow the instructions on the screen and reboot afterwards. However, you must manually add a 'nomodeset' parameter in the grub entry, or the computer will hang with a black screen after plymouth bootscreen due to a conflict against kernel modesetting and fglrx.