© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On Tue, Mar 23, 2010 at 11:15:26PM -0000, Robert Hooker wrote:
> Ok, after finding one of the dupes that was having this issue on the
> same machine I'm using where I couldn't reproduce it I looked into it a
> bit more. It looks like having vga16fb loaded (which I had blacklisted)
> is what's causing the problem and I can reproduce it on a livecd.
From IRC discussion...
vga16fb was added to the kernel in november or december for plymouth.
But it doesn't interact well with KMS, so results in errors like this.
Could make lshw ignore vga16fb when drmfb is present... or could force
vga16fb fail to load when there is a real framebuffer...