Prev: Upgrading OO.o, right hand doesn't know what left hand is doing
Next: Debian per Packard Bell
From: Chris Jones on 24 Jan 2010 19:20
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(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Nima Azarbayjany on 25 Jan 2010 10:40
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(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Chris Jones on 26 Jan 2010 01:10
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(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Tom H on 26 Jan 2010 01:50
> 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.

From
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/432254


I finally got the boot into FreeBSD to work.

Here's what I put in 40_custom before running update-grub:

....
menuentry "freebsd" {
set root=(hd0,2,a)
chainloader +1
boot
}

So the root specification is based on the FreeBSD slice (number) and
partition (letter) method of specifying a partition, as in the legacy
GRUB, except that the primary partition ("slice") numbering starts at
1 rather than 0.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Andrei Popescu on 27 Jan 2010 14:20
On Sun,24.Jan.10, 14:22:22, 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.

As far as I can tell this is due to the background image being too small
and the text is now black on black. Try using a bigger picture ;)

Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Upgrading OO.o, right hand doesn't know what left hand is doing
Next: Debian per Packard Bell