Mailinglist Archive: yast-devel (58 mails)

< Previous Next >
Re: [yast-devel] controlling X/GUI/QT mode of HTTP installation started via HD/Grub (no F3 available)
On Mon, 4 Aug 2014, Andrey Borzenkov wrote:

В Mon, 4 Aug 2014 15:00:05 +0200 (CEST)
Steffen Winterfeldt <snwint@xxxxxxx> пишет:

[...]

In fact, you currently can't influence the video mode (without a-priory
knowledge of the driver that's going to be used).


I think this statement need some qualification

a) without KMS it is possible - just select video mode during boot (or
explicitly pass vga=...) and X server will respect this setting

b) with KMS it is possible to set Linux console frame buffer video mode
using video=NxM option. But the problem here is, X server ignores it and
always selects some "best fit" resolution.

So the real question probably is - is it possible to make X server
respect currently chosen console resolution? If it is not possible - is
it possible to force fbdev X driver during installation?

There is in fact a bug open that the boot loader video mode menu should work
again. But it's really not that simple and I've dropped the issue for now.

For some nice state-of-the-art mode setting follow Takashi's comments in
https://bugzilla.novell.com/853350.

Sure, with enough knowledge about the hardware and some kernel parameters
you can probably force the mode you like.

But - then what? Do you want to keep the mode forced after install or do you
trust Xorg? Do you switch to a proprietary driver that maybe needs different
options or suddenly just works without any? Do you care about console
resolution?

There's at least 3 common ways to set your video mode: vesa/uefi fb / kms /
xorg. All need to be configured differently. And the little bootloader
should provide and easy-to-use shortcut that fits all. :-(


Steffen
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >