http://wiki.cchtml.com/api.php?action=feedcontributions&user=78.84.45.19&feedformat=atomcchtml.com - User contributions [en]2024-03-28T23:51:59ZUser contributionsMediaWiki 1.39.4http://wiki.cchtml.com/index.php?title=Fedora_8_Installation_Guide&diff=5717Fedora 8 Installation Guide2009-10-22T07:20:19Z<p>78.84.45.19: -83</p>
<hr />
<div>Rottencrotch through her pertty pink panties are over! ,<br />
<br />
doors.txt;10;15<br />
<br />
Prices can reach well into the hundreds and sometimes thousands of dollars, and depending on the method and location of installation, plumbing can also add to the cost. ,<br />
<br />
Good, I thought, we can use some Sunshine on a Sunday. ,<br />
<br />
==Issues==<br />
* AMD/ATI Catalist Control Center (amdcccle) fails to start, see [http://ati.cchtml.com/show_bug.cgi?id=672 this bugzilla entry].<br />
<br />
FYI: this patch (and others like it) is incomplete. It fails miserably with the drm module loaded. It will not work without drm either, and what would be the point?<br />
As seen by dmesg:<br />
<br />
[drm] Initialized drm 1.1.0 20060810<br />
[fglrx] Maximum main memory to use for locked dma buffers: 1898 MBytes.<br />
[fglrx] ASYNCIO init succeed!<br />
[fglrx:KCL_enable_pat] *ERROR* Pat entry 2 is already configured<br />
[fglrx] PAT is disabled!<br />
[fglrx:firegl_init_module] *ERROR* firegl_stub_register failed<br />
<br />
The livna rpm incurs the same failure. Stick with F7 and kernel 2.6.22, or use the radeon driver instead.<br />
<br />
----<br />
Updated by yangyud:<br><br />
You need to remove the loaded "drm" module from kernel before install the fglrx module.<br><br />
'''rmmod radeon; rmmod drm''' <br><br />
<br />
==See Also==<br />
* [[Frequently Asked Questions#Why does fglrx not work for my bleeding-edge kernel?]]<br />
<br />
[[Category:Installation Documentation]]<br />
Ok, the problem is gdm. I can `startx`, but gdm fails to load with fglrx, and there is no indication in any log as to why.<br />
This continues with new 7.11 Catalyst driver.<br />
Because of this, the problem is NOT with the driver, rather it is the default GDM time value of 10-seconds. To remedy:<br />
<br />
vi /etc/gdm/custom.conf<br />
<br />
[daemon]<br />
GdmXserverTimeout=60<br />
<br />
This allows enough time for X to startup before gdm considers it dead and aborts the X startup process.</div>78.84.45.19