Fedora 13 Installation Guide: Difference between revisions

From cchtml.com
No edit summary
No edit summary
Line 1: Line 1:
ATI's latest Catalyst 10.8 now well supports Xorg-server 1.8 after our wait.  Fedora users should of course be used to this.
ATI's latest Catalyst 10.9 now well supports Xorg-server 1.8.


Catalyst 10.8 provided productional support for OpenSUSE 11.3, while also supporting all other distros using X.org server 1.8 like Fedora 13. Recent builds of Ubuntu 10.10 uses X.org server 1.9 and is yet not supported.
Pre-built .rpm packages should be in the non-official RPMForge repository and corresponding version matching 10.9 should be there soon. I strongly recommend all of you use this method since it automatically configures the grub config file.


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.
 
You must 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.
 
Kernel versioned 2.6.34.6-47.fc13 has problems with this driver, which blanks the screen at boot and causes grey artifacts to manifest in X. Using fglrx under the new kernel also causes acpi wake-up problems.

Revision as of 19:33, 16 September 2010

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

Pre-built .rpm packages should be in the non-official RPMForge repository and corresponding version matching 10.9 should be there soon. I strongly recommend all of you use this method since it automatically configures the grub config file.

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.