Ok, I tested the new 3.2.0-14 and discovered that GFXMODE had nothing to do 
with it. I was timing the holding of 'shift' such that I would only sometimes 
get the grub screen (ie, I pressed it while I could still see the bios screen 
rather than immediately after it went away-- sometimes it worked, sometimes 
not). Now that I can reliably bring up the grub menu I can say:
* a default /etc/default/grub or any valid value for GFXMODE works fine (ie, 
1024x768) *if* I just let the system boot
* only when I access the grub menu will I hit the X corruption
* this is still a regression in 3.2-- the oneiric 3.0 still works fine even 
after accessing the grub menu

I will update the description and summary accordingly.

** Changed in: linux (Ubuntu)
       Status: Incomplete => Confirmed

** Summary changed:

- [precise] bad interplay between grub detected GFXMODE and 3.2.0 kernel
+ [precise] bad interplay between grub menu, X driver and 3.2.0 kernel

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925098

Title:
  [precise] bad interplay between grub menu, X driver and 3.2.0 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/925098/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to