- 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.
- 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. --Super Jamie 06:02, 22 March 2012 (CDT)
- 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. --Super Jamie 06:48, 22 March 2012 (CDT)
- Ok, I see. It's nice to put a name to the text. As far as the 3.2.9-1 fix goes, I assumed you would have gleaned that there was no other solution afaik. But I am glad there is a solution and that it's being published. I personally tested it last night and it works on 64 bit Fedora; however there seems to be a problem getting the method to work on 32 bit.
- Ah I don't have a 32-bit install to check, it has worked on the last two 64-bit kernels tho. The commit that broke it is referenced on the forum page I linked to, maybe look for that commit in the 32-bit source? I took out the first part of the document, you're right, let's just give people information about installing the damn driver :) Thanks for your help in making this better, I maintained the F14 document as well, it's come a long way since then but has always been lacking in multi-monitor suggestions. I used to have three screens in 2007 but gave up and bought a massive single screen, then XRandR became popular a few releases later. --220.127.116.11 15:59, 23 March 2012 (CDT)
Note: I've verified a procedure for getting amd-driver-installer to work on i686 F16 and I've integrated it into the doc with adjustments for greater conciseness and precision. I also verified the x86_64 F16 procedure here on two machines and with other users on the latest 64 bit kernel, which as of today is 3.3.0-4.fc16.x86_64.
This is the discussion page for an anonymous user who has not created an account yet, or who does not use it. We therefore have to use the numerical IP address to identify him/her. Such an IP address can be shared by several users. If you are an anonymous user and feel that irrelevant comments have been directed at you, please create an account or log in to avoid future confusion with other anonymous users.