I to have a multi boot system with linux and freebsd and windows.
GRUB is my boot loader.
I did not chain load FreeBSD.

This is my menu file for GRUB
title Red Hat Linux 9 (2.4.20-8)
        root (hd0,4)
        kernel /vmlinuz-2.4.20-8 ro root=LABEL=/
        initrd /initrd-2.4.20-8.img
title Windows 2000
        rootnoverify (hd0,0)
        chainloader +1
title FreeBSD 4.8
        root (hd0,3,a)
        kernel /boot/loader

And my fdisk -l
   Device Boot    Start       End    Blocks   Id  System
/dev/hda1             1       892   7164958+   7  HPFS/NTFS
/dev/hda2           893       956    514080    b  Win95 FAT32
/dev/hda3           957      2522  12578895    5  Extended
/dev/hda4   *      2523      4865  18820147+  a5  FreeBSD
/dev/hda5           957       969    104391   83  Linux
/dev/hda6           970      2457  11952328+  83  Linux
/dev/hda7          2458      2522    522081   82  Linux swap

This works fine for me.
I to am a beginner and still gathering info

Hope it helps

-----Original Message-----
[mailto:[EMAIL PROTECTED] On Behalf Of Loren M. Lang
Sent: Monday, December 08, 2003 7:26 AM
Subject: Dual-boot does not work with GRUB

I've been trying to setup a dual boot Linux/FreeBSD system so I can
tryout freebsd and compare it to linux, my current main os.  I had the
freebsd easyboot bootloader installed, but I couldn't get it to boot
linux so I reinstalled GRUB as lilo doesn't even load properly on my
system.  I can now boot into linux and use the freebsd install disk to
boot into freebsd.

I've tried to get grub to boot freebsd directly, but it's not working.
I've had it chainloader the first sector of the slice with freebsd on it
and chainload /boot/boot1 directly, both just print a - in the upper
left corner and stop, like it loaded boot1 successfully but boot1
couldn't find boot2.  Chainloading /boot/boot0 does a similar result,
with that boot loader.  Using grub to try and load /boot/loader and
/kernel with the kernel command doesn't do much either.

Any suggestions.

Also, in my short experience with freebsd, it seems relatively fast, but
when there is massive i/o in the background, like untarring a massive
tarball, the system becomes rather unresponsive with certain things, is
something misconfigured on my system?  Harddrive dma is turned on
according to sysctl.  On linux there is also an option to unmask irqs
while handling a disk interrupt, is there a similar option in freebsd
and will it help?

I sense much NT in you.
NT leads to Bluescreen.
Bluescreen leads to downtime.
Downtime leads to suffering.
NT is the path to the darkside.
Powerful Unix is.

Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc
Fingerprint: B3B9 D669 69C9 09EC 1BCD  835A FAF3 7A46 E4A3 280C

Confidentiality Notice

The information contained in this electronic message and any attachments to this 
message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged 
information. If
you are not the intended recipient, please notify the sender at Wipro or [EMAIL 
PROTECTED] immediately
and destroy all copies of this message and any attachments.
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to