SYSFB/simpleframebuffer did not exist before 3.12 (iirc). When having CONFIG_X86_SYSFB=N there is no way to force it since it does not get built (as before). And given the other issues I do not think we should.
The difference with vesafb is not necessarily in code (and as that has been around for quite a while its rather unlikely the code changed there). The change just made the same code being part of the kernel instead of a loadable module. What I think has changed is the way that grub might be setting up a framebuffer device and passing that into the kernel. Which is the reason I suggested playing around with that. Beside of generally preferring 80x24 in a server environment, I think I generally prefer to keep grub not changing anything there (which is what the GRUB_TERM=console should do + running update-grup to make that active). Then switching to the higher resolution is postponed until the kernel is taking over. There should be messages in dmesg about any switching over and afaik /proc/fb would contain the currently used one (if switching was successful, might lie if that fails). -- 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
