On Tue, 12 Aug 2014 04:02:53 -0400
Felix Miata
On 2014-08-12 09:19 (GMT+0200) Josef Reidinger composed:
It is deprecation warning, yast2-bootloader sets new option there instead of vga one.
SiS and mga chips and other legacy chips are not affected by including video= on cmdline because there is no KMS support for them. Only KMS responds to video=. Only vga= can specify video mode on ttys for KMS-unsupported gfxchips.
gfxpayload for not help in such case?
What I do know is vga= not only still works, but also it's nice and short, a pleasure to use on cmdlines already swollen by multiple instances of UUIDs and/or device IDs plus the long-winded other options not in existence or needed before Grub2.
Reason is simple majority of people found gfxmode=1280x800 better then having vga=791 which is easier to read and understand. So it is pleasure for people who is already familiar with it, but for newcomers it is easier to use new syntax.
I've never been able to grok and retain man page explanation how to use /etc/default/grub's non-intuitive similar video options GRUB_GFXMODE, GRUB_GFXPAYLOAD_LINUX, GRUB_TERMINAL, GRUB_CMDLINE_LINUX, GRUB_CMDLINE_LINUX_DEFAULT et al for configuring Grub2 cmdline for video. It's nice if yast2 understands how it all plays together, but that's little comfort for a user familiar with Grub Legacy's shell prompt interactive editing of a stanza, looking instead at a Grub2 edit menu trying to interactively tweak the much more complex Grub2 stanza.
Well, vga is deprecated, but still works, so you can use until it is removed. I think there is enough tutorials and documents if you google around "grub2 gfxmode"
If Grub Legacy must go, it should at the same time be replaced by something that also embraces KISS principle favored by many. Grub2's complexity is unlikely to ever to fill such a role, unlike Syslinux/Extlinux, or Grub Legacy. A Yast installation menu choice only between Grub2 and install no bootloader at all is very sad, very much narrowing the gap between what has historically been the best Linux installer around, and the also-rans from other distros.
Problem is that current hardware no longer followed KISS and for your side GRUB looks like KISS, but from yast side grub is really complex stuff to be configured correctly. And we are alone for such task, now some low level stuff is moved to grub2, so such low level stuff is handled by grub maintainer which share work with other distributions. YaST then can focus on more important tasks like proposing working configuration in corner cases so everyone can boot his machine. JFYI I create list of supported boot scenarios (still in review) which can give you idea how hard task it is to propose correct bootloader configuration: https://github.com/yast/yast-bootloader/blob/supported_scenarios/SUPPORTED_S... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org