Radeon driver conflicting with vesa fb in Fedora 17
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
Radeon driver conflicting with vesa fb in Fedora 17
Machine: the netbook as specified in my signature.
When I installed F17 it choose to use a "nomodeset" kernel parameter -- obviously with good reason because boot stops somewhere in the middle of nowhere when nomodeset is removed. With nomodeset I get a resolution of 1024 x 768 (stretched horizontally) instead of the optimal 1366 x 768.
Thus I gave the kernel for boot the parameters "udev.log-priority=info" and udev.children-max=1" but removed "nomodeset". These are the last lines of the boot messages:
Code:
...
[drm] initialized drm 1.1.0 20060810
[drm] Radeon defaulting to kernel modesetting.
[drm] Radeon kernel modesetting enabled.
fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
The 'puter then hangs for a minute and at last switches to an outwashed screen / picture refusing shortly further input (which means I have a few seconds to press <ctrl><alt><del> or be forced to initiate a cold start).
Anybody with an idea how to handle this? What is the "generic driver", radeon or something built into the x-drivers?
I was about to ask "what the hell - vesafb and KMS ?".
However I see some comments out there. Time I updated that Radeon system of mine to F17. This is a reminder to myself to post back.
Last edited by syg00; 09-16-2012 at 03:24 AM.
Reason: s/KSM/KMS/
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Original Poster
Rep:
Thanks, amani, I'm not (yet) in the business to compile my own modules . And before posting a bug I'll have to make sure the system is on the up to date, I think I ran the last update two or three weeks ago. I'll look into this.
Quote:
Originally Posted by syg00
...
However I see some comments out there. Time I updated that Radeon system of mine to F17. This is a reminder to myself to post back.
What comments? I'm looking forward to your back posts in the meanwhile .
So I just upgraded an old P4 with a 9600 to F17. Worked like a dream - radeon driver and all. Runs the screen at its native 1600x900.
I see both CONFIG_FB_BOOT_VESA_SUPPORT and CONFIG_FB_VESA compiled into the default kernel. Bit of a surprise that - comments re that compiled in support was what I was referring to above.
As I said, works fine on this desktop - will keep looking for any relevant info online.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Original Poster
Rep:
Arrgh. Internet is broken. I'll have to wait until my provider upgrades his infrastructure. Currently I have only about 5 kBit/sec and that is no real fun for updating...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
. And before posting a bug I'll have to make sure the system is on the up to date, I think I ran the last update two or three weeks ago. I'll look into this.
.
