>> I think that you mean "set gfxpayload=keep". I did not mention it >> because it has not worked for me (my boot-up stops with a black >> screen) but I have seen various sites that recommend it.
> That would (should?) work if you also set $GRUB_GFXMODE to the desired > mode (which resulted in strange effects for me). > I'm using "GRUB_GFXPAYLOAD=1680x1050x8" instead with the attached patch > (based on the patch in [0]) that I keep in /root and apply after every > update of the grub package. > WARNING: due to some recent changes in the grub package the patch needs > some refreshing, but I'm not familiar enough with diff/patch to > regenerate it. Use only if you know how the resulting grub.cfg should > look like. > [0] http://savannah.gnu.org/bugs/?27094 Thinking back, I can only assume that I may have mistyped something and not noticed or changed a few too many grub2 options simultaneously or set too many options simultaneously. I will have to try again. Thanks for the link. If I understand correctly, its purpose is to add a grub_gfxpayload line to /etc/default/grub so that the /etc/grub.d scripts have a value to plug in to grub.cfg. I edit my grub.cfg manually so it does not really matter to me. I would love to know though from where the gfxpayload variable came from and why the gfxmode variable is not enough. One of the reasons that I tried it and avoided it almost immediately is that it seemed to pop out of nowhere in some fora but was not referenced in the grub.enbug.org, Ubuntu, or ArchLinux documentation. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
