https://bugzilla.novell.com/show_bug.cgi?id=772059 https://bugzilla.novell.com/show_bug.cgi?id=772059#c5 --- Comment #5 from Michael Chang <mchang@suse.com> 2012-07-24 10:35:07 UTC --- (In reply to comment #3)
(In reply to comment #2)
If it works, then you could try something in grub2's command line by typing "c". Type help would list all the available commands and you could try the two.
grub > videoinfo
Interestingly, this doesn't return any available mode. So I guess the autodetection can't work, which would explain many things.
Thanks this did make a lot of sense .. The background to use auto-detection is because grub 2.0 release claims it works better in auto mode and the default config had change to it, which is in replace of 640x480. Before grub2 2.0, the yast2 used highest mode detected from hwinfo --framebuffer as default (thus not use 640x480) but has received bug reports about mode-setting not found or incorrect, use grub2 2.0 and "auto" somehow fixed their problem. So I really didn't know how to fix this by "choosing a correct mode". :(
I've just switched everything to 1024x768 in yast2 bootloader, and now it seems to work. I then switched to 1280x800, and it also works. I then switched again to 1440x900, and there it's corrupted.
If 1440x900 is listed but not not work if you set your mode number to it. This would probably be a buggy vbios. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.