Hi On Thu, Dec 19, 2013 at 1:03 AM, One Thousand Gnomes <gnomes@xxxxxxxxxxxxxxxxxxx> wrote: >> > That bug always existed, simplefb is just the first driver to hit it >> > (vesafb/efifb didn't use resources). I'm aware of the issue but as a >> > workaround you can simply disable CONFIG_X86_SYSFB. That restores >> > the old behavior. >> >> This looks like a regression, so we'll either need a fix or we'll have >> to mark CONFIG_X86_SYSFB as CONFIG_BROKEN. > > Kernel bugzilla has entries for simplefb breaking both vesafb and matrox > mga. Thanks for the hints. I've read through all I could find and tried to provide some help. I'm kind of confused, most of them enable CONFIG_X86_SYSFB (which is 'n' by default) but don't read the help text. I did my best to tell people that this option requires CONFIG_FB_SIMPLE, but if you don't read the help-text you won't notice that. Don't know what to do about that.. Thanks David -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html