https://bugzilla.novell.com/show_bug.cgi?id=675793 https://bugzilla.novell.com/show_bug.cgi?id=675793#c6 --- Comment #6 from Felix Miata <mrmazda@earthlink.net> 2011-03-10 12:44:55 UTC --- (In reply to comment #5)
Felix, I don't think that you need to build the table. I guess most chips can provide their modes correctly, in case they cannot, there is a hardcoded list of modes as a fallback solution. If you miss some mode there, it can be extended.
Extended how and where?
See http://svn.opensuse.org/svn/yast/trunk/yast2/library/system/src/Initrd.ycp
Other than its list of known modes, it's virtually all gibberish to me. Conspicuously absent in the list of known modes are SXGA+ (4:3, which 5:4 SXGA is not) and _any_ widescreen modes, which means fallback usage on any modern display resulting from what that file does will never be to the native/best mode for that display to use. Shouldn't 1920x1200, 1920x1080, 1280x800 (the most common laptop mode prior to the marketers' switch from 16:10 to 16:9), 1680x1050, 1600x900, 1440x900, 1366x768, 1280x720 & 1024x640 at least be included there?
Except for that (and possibly changing the label in YaST), I still don't see what can be improbed here :-/
Even assuming you meant s/improbed/improved/, I'm not sure what you meant. by this statement. Did you mean to include an "else" in that sentence? Is provision for using "video=" syntax in Initrd.ycp somewhere? Don't yast2-bootloader and/or perl-Bootloader need changes? What happens if cmdline for installation includes video= parameter but "unspecified" is selected from the list in YaST? Maybe I just need to see the results of whatever you've done or plan to do before commenting further. -- 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.