Re: can't get a correct resolution

[Andrei Borzenkov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

В Wed, 01 Jul 2015 17:25:16 +0200
François Patte <address@hidden> пишет:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Le 30/06/2015 18:17, Andrei Borzenkov a écrit :
> > В Tue, 30 Jun 2015 08:41:06 +0200 François Patte
> > <address@hidden> пишет:
> > 
> >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> > 
> >> Bonjour,
> > 
> >> I am facing a resolution problem with grub2.
> > 
> >> Install of Fedora 21
> > 
> >> grub version: grub2-2.02-0.13.fc21
> > 
> >> Here is my /etc/defaul/grub:
> > 
> >> <-------------------- GRUB_TIMEOUT="10" GRUB_DISTRIBUTOR="$(sed
> >> 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT="0" 
> >> #GRUB_SAVEDEFAULT="true" GRUB_DISABLE_SUBMENU="true" 
> >> GRUB_TERMINAL_OUTPUT="gfxterm" 
> >> GRUB_CMDLINE_LINUX="rd.md.uuid=81f15cb5:748fb5c1:42bef1a6:1ea1ce47
> >>
> >> 
> rd.lvm.lv=fedora/usr rd.md.uuid=4a28174a:f38b4938:233f85f7:6ce585a8
> >> rd.lvm.lv=fedora/racine
> >> rd.md.uuid=9f878179:a58f5c78:f645e22e:d7d3c896 
> >> rd.lvm.lv=systeme/swap rhgb quiet" GRUB_DISABLE_RECOVERY="true" 
> >> GRUB_GFXMODE="1280x1024x32" GRUB_GFXPAYLOAD_LINUX="keep" 
> >> GRUB_BACKGROUND="/boot/grub2/themes/system/fireworks.png"
> > 
> >> #GRUB_THEME="/boot/grub2/themes/system/theme.txt" export
> >> GRUB_COLOR_NORMAL="light-gray/black" export
> >> GRUB_COLOR_HIGHLIGHT="magenta/black" 
> >> GRUB_FONT="/boot/grub2/unicode.pf2" <-------------------------
> > 
> >> So, as far as I read the grub doc, because of 
> >> GRUB_GFXPAYLOAD_LINUX="keep"
> > 
> >> It is supposed to apply the 1280x1024 resolution to the console
> >> during the boot. But it is not the case! I get this resolution
> >> only with the grub first screen: fireworks image and the entry
> >> list.
> > 
> >> What is missing in my config?
> > 
> > 
> > If your kernel is using KMS drivers legacy VESA resolution is 
> > effectively ignored. Try passing video=1280x1024 on kernel command
> > line.
> 
> Thank you for answering. I tried this but nothing changed....
> 

Out of curiosity - what if you boot with nomodeset parameter
additionally? This should disable KMS completely.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlWUEloACgkQR6LMutpd94wDaQCgzEXvrkZZc84Kjf0EVIniji+f
7coAnRRmdfDw4NuVGG8rlq5gQdzxqIrT
=90dv
-----END PGP SIGNATURE-----