Comment 21 for bug 1300557

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Well, I did some bisecting but the results are disappointing. Actually I ended up trisecting. On Saucy, kernel...

3.11.0-12 was OK. Recognised my full native resolution and enabled it by default. Wonderful.

3.11.0-13 to 3.11.0.24 inclusive were completely messed up. They booted in some ultra-low resolution and were not responsive to my mouse and keyboard.

3.11.0-25 wasn't available in the archive.

3.11.0-26 gives me a maximum resolution of 1920 by 1200, which is the same behaviour I observed with 14.04, 14.10, and the daily 15.04 test versions.

So it looks like between 3.11.0-12 and 3.11.0-13 something broke, and it took until 3.11.0-26 to get it more or less working again, but the old functionality was never completely regained. I guess that means there are no easy answers for this one.