Greetings gang,
While testing a radeon driver issue, I had to disable modesetting to help identify the scope of the problem. Thankfully, all I had to do was follow along in the steps posted to https://fedoraproject.org/wiki/How_to_debug_Xorg_problems.
However, it seems that 'nomodeset' wasn't sufficient to disable modesetting on my radeon x300 adapter. After quick inspection, it seems I needed to also provide "radeon.modeset=0". There appear to be additional driver-specific modesetting parameters (nouveau, i915, radeonhd).
Is it worth updating the above wiki page to include these driver specific tunables as well?
Thanks, James
On Thu, 2009-08-20 at 12:54 -0400, James Laska wrote:
Greetings gang,
While testing a radeon driver issue, I had to disable modesetting to help identify the scope of the problem. Thankfully, all I had to do was follow along in the steps posted to https://fedoraproject.org/wiki/How_to_debug_Xorg_problems.
However, it seems that 'nomodeset' wasn't sufficient to disable modesetting on my radeon x300 adapter. After quick inspection, it seems I needed to also provide "radeon.modeset=0". There appear to be additional driver-specific modesetting parameters (nouveau, i915, radeonhd).
Is it worth updating the above wiki page to include these driver specific tunables as well?
I believe this is actually a bug. nomodeset is supposed to be all you need, but it's not working at present for some reason.
I think nomodeset is basically a no-op at present and just 'radeon.modeset=0' alone would do the job. I can't remember exactly what it is that's causing nomodeset to fail.
If the bug's not going to be fixed soon, we should probably include this information there too, yep.
2009/8/20 Adam Williamson
I believe this is actually a bug. nomodeset is supposed to be all you need, but it's not working at present for some reason.
I think nomodeset is basically a no-op at present and just 'radeon.modeset=0' alone would do the job. I can't remember exactly what it is that's causing nomodeset to fail.
If the bug's not going to be fixed soon, we should probably include this information there too, yep.
On Thu, 2009-08-20 at 23:31 +0200, Christoph Frieben wrote:
2009/8/20 Adam Williamson I believe this is actually a bug. nomodeset is supposed to be all you need, but it's not working at present for some reason.
I think nomodeset is basically a no-op at present and just 'radeon.modeset=0' alone would do the job. I can't remember exactly what it is that's causing nomodeset to fail. If the bug's not going to be fixed soon, we should probably include this information there too, yep.
Thanks for the bz. I've requested adding this to the 'Common F12 bugs' page [1] by adding keyword:CommonBugs. I then took a stab at drafting an entry for this issue at https://fedoraproject.org/wiki/Common_F12_bugs#alpha-nomodeset-ignore. Please feel free to review and adjust as needed.
Thanks, James
[1]
-
Adam Williamson -
Christoph Frieben -
James Laska