https://bugzilla.novell.com/show_bug.cgi?id=675793 https://bugzilla.novell.com/show_bug.cgi?id=675793#c4 --- Comment #4 from Felix Miata <mrmazda@earthlink.net> 2011-03-08 14:43:04 UTC --- (In reply to comment #3)
Yes, it sets only a single mode - which is primarily for the console.
It should be exclusively for console, correct?
The list of modes is always according to a detection.
Unless the video BIOS doesn't support VESA correctly (original G400 BIOS) or at all (i810 only has old PC 80 column text modes plus proprietary 132 column text modes), and, apparently now with KMS, when EDID is bad or missing.
For X, you can have different mode - I just don't see why this should be defined by bootloader - often you change the mode via applets as needed.
AFAICT, cmdline parameters should normally (e.g.: default menu.lst stanza, as opposed to failsafe) not affect what mode X can or does use on initialization, which is not always the current case if a traditional framebuffer mode is specified using vga=. Really, my head is swimming in confusion over this right now, so I can understand if you're having trouble too. Do I need to build a table of video chips, valid vs invalid EDID, and various cmdline parameter combinations in order to get this sorted? cf. https://bugzilla.kernel.org/show_bug.cgi?id=27922 -- 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.