That's correct, the VESA framebuffer (vesafb) is what I saw on lsmod on older kernels. I can do any other testing you'd like with different kernels or versions of Ubuntu as the system I'm doing this on is purely test. Pre-setting the desired resolution results in a slow console and setting GRUB_TERMINAL=console results in a good speed console, but the resolution is too low.
What you stated about checking the dmesg and see what framebuffer driver is actually being used made me wonder if I had missed something, so I did a bit of investigation. In 3.13 with CONFIG_X86_SYSFB=on I get simple-framebuffer in my dmesg. With it off, I get vesafb. Is there a way for me to force simple-framebuffer? Is it possible that either the system isn't using vesafb in older kernels even though it lists it? Is it possible there was regression in vesafb when it was merged into the kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434581 Title: Console extremely slow with 3.13 and newer kernels for certified servers with Matrox G200er2 or similar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434581/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
