Oddly enough, on a cold boot I was actually surprised to see the almost- forgotten Ubuntu startup splash bar rendered properly. I'm still seeing a different uvesafb error, but not the -22 error as some are still apparently seeing.
[EMAIL PROTECTED]:~$ dmesg | grep vesa [ 3.170630] uvesafb: Intel Corporation, Intel(r)915G/915GV/910GL Graphics Controller, Hardware Version 0.0, OEM: Intel(r)915G/915GV/910GL Graphics Chip Accelerated VGA BIOS, VBE v3.0 [ 3.180005] uvesafb: VBIOS/hardware supports DDC2 transfers [ 3.190005] uvesafb: monitor limits: vf = 75 Hz, hf = 80 kHz, clk = 140 MHz [ 3.190005] uvesafb: scrolling: redraw [ 3.200006] uvesafb: framebuffer at 0xc0000000, mapped to 0xf8880000, using 7872k, total 7872k [ 34.440635] uvesafb: mode switch failed (eax=0x14f, err=0). Trying again with default timings. [ 34.610635] uvesafb: mode switch failed (eax=0x14f, err=0). Trying again with default timings. This is on a Dell GX280 system with GMA900 graphics. I'll give it a try tomorrow on my work PC which is an Optiplex 755 with GMA3100 (?) Not even sure this has anything to do with the graphics card/IGP...I doubt it. But definitely interested in seeing if the new kernel really does do the trick or not -- Switched from vesafb to uvesafb, but uvesafb can't work without v86d https://bugs.launchpad.net/bugs/246269 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
