9:18 a.m.
Severn is my first time using grub... I've been cowering behind
lilo for quite a while.
I'm guessing its pretty easy to do but not so clear just how to set
up an `other' os to be started by grub.
In this case its a solaris (x86) install on /dev/hda. With past RH
releases I've been starting it with the tried and tru lilo technique:
[..]
other=/dev/hda1
label=sol
table=/dev/hda
[...]
Severn is on /dev/hdc1 and bootloader is installed in MBR of /dev/hda
How is this done with grub?
9:32 a.m.
On Tue, 2003-10-14 at 09:18, Harry Putnam wrote:
Severn is my first time using grub... I've been cowering behind
lilo for quite a while.
I'm guessing its pretty easy to do but not so clear just how to set
up an `other' os to be started by grub.
In this case its a solaris (x86) install on /dev/hda. With past RH
releases I've been starting it with the tried and tru lilo technique:
[..]
other=/dev/hda1
label=sol
table=/dev/hda
[...]
Severn is on /dev/hdc1 and bootloader is installed in MBR of /dev/hda
How is this done with grub?
Grub creates a file /etc/grub.conf in which the boot loader records are
listed. For example:
=======================================
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,10)
# kernel /boot/vmlinuz-version ro root=/dev/hda11
# initrd /boot/initrd-version.img
#boot=/dev/hda11
default=0
timeout=10
splashimage=(hd0,10)/boot/grub/splash.xpm.gz
title Fedora Core (2.4.22-1.2088.nptl)
root (hd0,10)
kernel /boot/vmlinuz-2.4.22-1.2088.nptl ro root=LABEL=/1 hdc=ide-scsi
initrd /boot/initrd-2.4.22-1.2088.nptl.img
title DOS
rootnoverify (hd0,0)
chainloader +1
=======================================
is the file created by a fresh install of Fedora Test 3 where I have a
windows partition on /dev/hda1 (called DOS above).
To add another OS, a similar record is added, and the next boot contains
that choice in the boot menu. You do not have to run grub to make the
change as you do in lilo.
For a complete explanation, visit
http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-grub-w...
Gerry
10:01 a.m.
On Tue, 14 Oct 2003, Harry Putnam wrote:
Severn is my first time using grub... I've been cowering behind
lilo for quite a while.
I'm guessing its pretty easy to do but not so clear just how to set
up an `other' os to be started by grub.
In this case its a solaris (x86) install on /dev/hda. With past RH
releases I've been starting it with the tried and tru lilo technique:
[..]
other=/dev/hda1
label=sol
table=/dev/hda
[...]
Severn is on /dev/hdc1 and bootloader is installed in MBR of /dev/hda
How is this done with grub?
Grub config is similar but different. :-)
Here is a copy of my grub conf:
grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/hdc5
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd1,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-18.9)
root (hd1,0)
kernel /vmlinuz-2.4.20-18.9 ro root=LABEL=/
initrd /initrd-2.4.20-18.9.img
title Red Hat Linux (2.4.20-13.9)
root (hd1,0)
kernel /vmlinuz-2.4.20-13.9 ro root=LABEL=/
initrd /initrd-2.4.20-13.9.img
title Solaris 9
rootnoverify (hd0,0)
chainloader +1
This should give you an idea of how to do it.
HTH,
--
......Tom Registered Linux User #14522 http://counter.li.org
tdiehl(a)rogueind.com My current SpamTrap -------> mtd123(a)rogueind.com
10:33 a.m.
Tom Diehl <tdiehl(a)rogueind.com> writes:
This should give you an idea of how to do it.
Sure did, to both of you. Sorry .. it was embarrassingly easy to
find that info in the `info' file. But your exact files made it real
easy.
It gives examples of setting vga by appending to the root line like:
kernel /vmlinuz root=/dev/hda1 vga=ask
doing this and selectinbg various of those offered I see the selected
size only lasts about 100 or so lines then the standard size
re-emerges so that most of teh boot messages are in the standard size
instead of what ever was selected.
Anyone know what that is the case?
10:13 p.m.
On Tue, 2003-10-14 at 11:33, Harry Putnam wrote:
It gives examples of setting vga by appending to the root line like:
kernel /vmlinuz root=/dev/hda1 vga=ask
doing this and selectinbg various of those offered I see the selected
size only lasts about 100 or so lines then the standard size
re-emerges so that most of teh boot messages are in the standard size
instead of what ever was selected.
Anyone know what that is the case?
You can get a better resolution by using your video cards frame buffer.
From the file /usr/src/linux/Documentation/fb/vesafb.txt
| 640x480 800x600 1024x768 1280x1024
----+-------------------------------------
256 | 0x301 0x303 0x305 0x307
32k | 0x310 0x313 0x316 0x319
64k | 0x311 0x314 0x317 0x31A
16M | 0x312 0x315 0x318 0x31B
Use one of these numbers instead of the ask value for vga. On my
laptop, I use 800x600 @ 64k by appending vga=0x314 to my kernel line
in grub.conf.
Jim Drabb
--
James Drabb
Senior Programmer Analyst
Davenport, FL USA
5:24 a.m.
James Drabb <JDrabb(a)tampabay.rr.com> writes:
>From the file /usr/src/linux/Documentation/fb/vesafb.txt
| 640x480 800x600 1024x768 1280x1024
----+-------------------------------------
256 | 0x301 0x303 0x305 0x307
32k | 0x310 0x313 0x316 0x319
64k | 0x311 0x314 0x317 0x31A
16M | 0x312 0x315 0x318 0x31B
Use one of these numbers instead of the ask value for vga. On my
laptop, I use 800x600 @ 64k by appending vga=0x314 to my kernel line
in grub.conf.
Ah yes, this avoids those horrible looking fonts that get used at
vga=3 or 6, and the size remains in place throughout bootup.
vga=0x318 seems about right here....
Thanks.
5:59 p.m.
On Oct 14, 2003 at 23:13, James Drabb in a soothing rage wrote:
On Tue, 2003-10-14 at 11:33, Harry Putnam wrote:
[...]
> It gives examples of setting vga by appending to the root line
like:
>
> kernel /vmlinuz root=/dev/hda1 vga=ask
>
> doing this and selectinbg various of those offered I see the selected
> size only lasts about 100 or so lines then the standard size
> re-emerges so that most of teh boot messages are in the standard size
> instead of what ever was selected.
>
> Anyone know what that is the case?
This gets reset by something in
/etc/rc.sysinit. It happened
to me eons ago before I started using the method mentioned
below.
You can get a better resolution by using your video cards frame
buffer.
From the file /usr/src/linux/Documentation/fb/vesafb.txt
| 640x480 800x600 1024x768 1280x1024
----+-------------------------------------
256 | 0x301 0x303 0x305 0x307
32k | 0x310 0x313 0x316 0x319
64k | 0x311 0x314 0x317 0x31A
16M | 0x312 0x315 0x318 0x31B
Use one of these numbers instead of the ask value for vga. On my
laptop, I use 800x600 @ 64k by appending vga=0x314 to my kernel line
in grub.conf.
I happen to have a Matrox G550 and in RH9 used
append="video=matrox:vesa:447" in my /etc/lilo.conf.
While using the 2.6-test kernels, this changed to
'video=matroxfb:vesa:447' in grub.conf. I now use
vga=791 in FC Test 3 and have tried vga=447, vga=0x1BF
and video=matrox:vesa:447 to no avail. I want to run
my monitor at 1600x1200@32bpp or 24bpp. I'd really
appreciate any help I can get for the correct parameter
to pass to grub.
TIA
--
Registered Linux User # 125653 (http://counter.li.org)
Switch to: http://www.speakeasy.net/refer/190653
A wife lasts only for the length of the marriage, but an ex-wife is there
*for the rest of your life*.
-- Jim Samuels
18:48:16 up 52 days, 6:22, 4 users, load average: 0.00, 0.00, 0.00
8:47 p.m.
ne... schrieb:
On Oct 14, 2003 at 23:13, James Drabb in a soothing rage wrote:
>On Tue, 2003-10-14 at 11:33, Harry Putnam wrote:
>
>
[...]
>>It gives examples of setting vga by appending to the root line like:
>>
>> kernel /vmlinuz root=/dev/hda1 vga=ask
>>
>>doing this and selectinbg various of those offered I see the selected
>>size only lasts about 100 or so lines then the standard size
>>re-emerges so that most of teh boot messages are in the standard size
>>instead of what ever was selected.
>>
>>Anyone know what that is the case?
>>
>>
This gets reset by something in /etc/rc.sysinit. It happened
to me eons ago before I started using the method mentioned
below.
/etc/sysconfig/init, there's something about "colums", set to ~120
Christoph
--
"Wenn zu perfekt - Gott böse."
Nam June Paik
_______________________________
Christoph Wickert
mailto:christoph.wickert@web.de
7507
days inactive
7509
days old
7 comments
6 participants
participants (6)
-
Christoph Wickert -
Gerry Tool -
Harry Putnam -
James Drabb -
ne... -
Tom Diehl