Vesafb was a module in the 3.11 and older kernels. It is now built into the kernel, which is why that file does not exist.
There some vesa specific SAUCE patches in Ubuntu that are not upstream, so that may be why the upstream kernels don't work. We could bisect between the Ubuntu kernels instead of the mainline kernel. We would first need to identify the last Ubuntu kernel that did not have the bug and the first that did. Can you test the following two kernels: 3.11.0-12.19: https://launchpad.net/ubuntu/+source/linux/3.11.0-12.19/+build/5088396 3.13.0-1.16: https://launchpad.net/ubuntu/+source/linux/3.13.0-1.16/+build/5421709 The 3.11.0-12.19 is that last 3.11 based kernel Trusty used before moving to the 3.12 kernel. The 3.13.0-1.16 kernel is the first 3.13 based kernel that Trusty used. All of the Trust kernels can be found at: https://launchpad.net/ubuntu/trusty/+source/linux ** Tags removed: needs-bisect ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Also affects: linux (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Utopic) Status: New => Confirmed ** Changed in: linux (Ubuntu Trusty) Status: New => Confirmed ** Changed in: linux (Ubuntu Utopic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium ** Tags added: utopic vivid -- 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
