It does appear this bug is due to an Ubuntu specific change, since none of the upstream kernels have this bug. The key is to identify the last kernel that did not have this bug, and the first kernel that did. That will allow us to bisect down to the commit that introduced the regression.
Instead of trying each kernel going back in time, can you test the following kernels: v3.5.0-1.1: https://launchpad.net/ubuntu/+source/linux/3.5.0-1.1 v3.5.0-5.5: https://launchpad.net/ubuntu/+source/linux/3.5.0-5.5 3.5.0-10.10 https://launchpad.net/ubuntu/+source/linux/3.5.0-10.10 Based on these results, we should know if we need to test in-between versions, or test older/newer kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057532 Title: Monitor goes black ("no signal") after Grub, comes back to life when X starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1057532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
