It's weird but it's not working for me. Somehow update-grub (as well as
update-grub2, in case they are different) ignore all modifications to
/etc/default/grub. I'm giving up. Should I report a bug?



Hi, I use a slightly different way, I put:

GRUB_GFXMODE="1440x900 640x480"

in /etc/defaults/grub (native resolution first, fall-back one isn't
necessary, it's the default).

Then in /etc/grub.d/00_header I add gfxpayload=keep to this section
(around line 80):
[...]
if loadfont `make_system_path_relative_to_its_root ${GRUB_FONT_PATH}` ; then
set gfxmode=${GRUB_GFXMODE}
set gfxpayload=keep <<<<<<< here it is

insmod gfxterm
insmod ${GRUB_VIDEO_BACKEND}

if terminal_output gfxterm ; then true ; else
[...]
It's working for me on Debian Squeeze and Ubuntu, but needs to be
updated if 00_header is overwritten during update (not often). It's just
a workaround until gfxpayload= is picked up in /etc/default/grub.

My 2 cents.




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

> It's weird but it's not working for me. *Somehow update-grub (as well as
> update-grub2, in case they are different) ignore all modifications to
> /etc/default/grub. *I'm giving up. *Should I report a bug?

Are you making all the changes that have been suggested?

In short:

In
/etc/default/grub
add
GRUB_GFXPAYLOAD=keep
on the line after
GRUB_GFXMODE=<resolution>

In
/etc/grub.d/00_header
add
if [ "x${GRUB_GFXPAYLOAD}" = "x" ] ; then GRUB_GFXPAYLOAD=640x480 ; fi
on the line after
if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=640x480 ; fi

In
/etc/grub.d/00_header
add
set gfxpayload=${GRUB_GFXPAYLOAD}
on the line after
set gfxmode=${GRUB_GFXMODE}

Run
update-grub
or
update-grub2


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

>>tv.debian wrote:
>> Hi, I use a slightly different way, I put:
>>
>> GRUB_GFXMODE="1440x900 640x480"
>>
>> in /etc/defaults/grub (native resolution first, fall-back one isn't
>> necessary, it's the default).
>>
>> Then in /etc/grub.d/00_header I add gfxpayload=keep to this section
>> (around line 80):
>> [...]
>> if loadfont `make_system_path_relative_to_its_root ${GRUB_FONT_PATH}`
>> ; then
>> set gfxmode=${GRUB_GFXMODE}
>> set gfxpayload=keep <<<<<<< here it is
>>
>> insmod gfxterm
>> insmod ${GRUB_VIDEO_BACKEND}
>>
>> if terminal_output gfxterm ; then true ; else
>> [...]
>> It's working for me on Debian Squeeze and Ubuntu, but needs to be
>> updated if 00_header is overwritten during update (not often). It's just
>> a workaround until gfxpayload= is picked up in /etc/default/grub.
>>
>> My 2 cents.
>>
>
> Nima Azarbayjany wrote:
> It's weird but it's not working for me. Somehow update-grub (as well as
> update-grub2, in case they are different) ignore all modifications to
> /etc/default/grub. I'm giving up. Should I report a bug?
>

[I re-arranged the message in chronological order to remove top posting]

This could mean your grub install is somehow broken, try to renew it
from scratch, not mixing both grub-pc ("grub2") and grub-legacy. Or
maybe you have typos somewhere in the variables so that they are not
picked up by update-grub (you can also call "grub-mkconfig -o
/boot/grub/grub.cfg" for grub-pc).

No need to Cc me, I am all eyes on the list.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

I was able to achieve the desired resolution of 1280x800 (equivalent to,
I think, 0x361) by manually editing grub.cfg but the grub menu does not
show correctly. It only fills the left top quarter of the screen and
parts of it cannot be seen. The rest was fine (the boot up of linux I
mean) with a good resolution. I will try setting the resolutions
separately, i.e., not using gfxpayload=keep.



Are you making all the changes that have been suggested?

In short:

In
/etc/default/grub
add
GRUB_GFXPAYLOAD=keep
on the line after
GRUB_GFXMODE=<resolution>

In
/etc/grub.d/00_header
add
if [ "x${GRUB_GFXPAYLOAD}" = "x" ] ; then GRUB_GFXPAYLOAD=640x480 ; fi
on the line after
if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=640x480 ; fi

In
/etc/grub.d/00_header
add
set gfxpayload=${GRUB_GFXPAYLOAD}
on the line after
set gfxmode=${GRUB_GFXMODE}

Run
update-grub
or
update-grub2

I did install grub-legacy at some point but removed it almost
immediately. I have reinstalled the grub-pc package and done everything
to make sure it's a clean install not mixed with grub-legacy. It seems
to be so.

This could mean your grub install is somehow broken, try to renew it
from scratch, not mixing both grub-pc ("grub2") and grub-legacy. Or
maybe you have typos somewhere in the variables so that they are not
picked up by update-grub (you can also call "grub-mkconfig -o
/boot/grub/grub.cfg" for grub-pc).





--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sun, Jan 24, 2010 at 05:52:22AM EST, Nima Azarbayjany wrote:

> I was able to achieve the desired resolution of 1280x800 (equivalent
> to, I think, 0x361) by manually editing grub.cfg but the grub menu
> does not show correctly. It only fills the left top quarter of the
> screen and parts of it cannot be seen. The rest was fine (the boot
> up of linux I mean) with a good resolution. I will try setting the
> resolutions separately, i.e., not using gfxpayload=keep.

I was able to get everything grub2 to work in about a couple of hours
hanging out at freenode.net/#grub and I never looked back.

CJ


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Jeffrey Cao <jcao.linux@gmail.com>:
> On 2010-01-22, Nima Azarbayjany <i.adore.debian@gmail.com> wrote:
> >
> > I have recently installed Squeeze on my laptop and most things
> > seem to work fine right now.
> >
> > I used to add vga=xxx to the kernel parameters line to adjust the
> > console resolution but this is now deprecated as a message printed
> > at the startup says. What should be passed to the kernel instead
> > of, for example, vga=0x361? Let me add that I have upgraded the
> > kernel to 2.6.32 from sid.
> >
> For the new grub, edit the file /etc/default/grub, add the
> following line:
>
> GRUB_CMDLINE_LINUX="vga=xxx"
>
> And then run 'update-grub' to update /boot/grub/grub.cfg

Isn't it strange that we now need to `update-grub`, when having to run
"lilo" was such a hardship before?

That does it. I'm going back to lilo.

Grumble, mumble, wtf doesn't OpenBSD ever show up in the grub* boot
menu, grumble, mumble, ... Grr.


--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

s. keeling wrote:
> Jeffrey Cao <jcao.linux@gmail.com>:
>> On 2010-01-22, Nima Azarbayjany <i.adore.debian@gmail.com> wrote:
>>> I have recently installed Squeeze on my laptop and most things
>>> seem to work fine right now.
>>>
>>> I used to add vga=xxx to the kernel parameters line to adjust the
>>> console resolution but this is now deprecated as a message printed
>>> at the startup says. What should be passed to the kernel instead
>>> of, for example, vga=0x361? Let me add that I have upgraded the
>>> kernel to 2.6.32 from sid.
>>>
>> For the new grub, edit the file /etc/default/grub, add the
>> following line:
>>
>> GRUB_CMDLINE_LINUX="vga=xxx"
>>
>> And then run 'update-grub' to update /boot/grub/grub.cfg
>
> Isn't it strange that we now need to `update-grub`, when having to run
> "lilo" was such a hardship before?
>
> That does it. I'm going back to lilo.
>
> Grumble, mumble, wtf doesn't OpenBSD ever show up in the grub* boot
> menu, grumble, mumble, ... Grr.
>
>
Hi grumpy,

"update-grub" is only needed when configuration is manually edited,
which seems fair to me as I don't see grub poling it's configuration
scripts every few minutes to see if the volatile user made some change.
We sure lost a bit of user-friendliness having several configuration to
edit instead of just the "menu.lst" from grub-legacy, I guess that's the
price to pay for flexibility, but judging by the number of messages
about grub-legacy problems all over the Internet it's wasn't that much
user-friendly anyway...
Can't comment on OpenBSD, maybe a filesystem compatibility problem ?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Okay... I finally got it to work. I set two different resolutions, that
is, I did not use gfxpayload=keep.


Thanks all.

Nima


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

tv.debian@googlemail.com <tv.debian@googlemail.com>:
> s. keeling wrote:
> >
> > Isn't it strange that we now need to `update-grub`, when having to run
> > "lilo" was such a hardship before?
> >
> > Grumble, mumble, wtf doesn't OpenBSD ever show up in the grub* boot
> > menu, grumble, mumble, ... Grr.
>
> Hi grumpy,

It's a fair cop. :-|

> "update-grub" is only needed when configuration is manually edited,

My complaint is neither grub-legacy nor grub2 ever pick up my OBSD
install, yet /etc/grub.d/40_custom is there and describes it, and
/boot/grub/menu.lst is there to upgrade from.

"aptitude reinstall $blah" never gets OBSD into the boot menu.
Never works (not complaining, just reporting; I'll check
bugs.debian.org for similar when I've time).

> Can't comment on OpenBSD, maybe a filesystem compatibility problem ?

Debian's fdisk manages it (type a6 OpenBSD). I'll keep banging my
head on it.


--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Jan 25, 2010 at 10:26:45PM EST, s. keeling wrote:

[..]

> My complaint is neither grub-legacy nor grub2 ever pick up my OBSD
> install, yet /etc/grub.d/40_custom is there and describes it, and
> /boot/grub/menu.lst is there to upgrade from.

Just be aware that auto-detecting kernels is not done by grub, but by a
separate utility called os-prober.

The os-prober conmprises a bunch of shell scripts, which you will have
to read to investigate further, since it ships with absolutely zero
documentation.

Due in part to these aspects, but mostly because I have a bunch of
legacy systems that have all kind of unmaintained junk in the grub part
of their /boot directory, I have removed os-prober and entered my stuff
manually in /etc/grub/40-custom on the system where the active grub
dwells so I know what I'm doing.

CJ


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org