Re: Configuration of Grub?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Stanford wrote: >> Good question; not sure about that one, since the BIOS may or may not >> count the EIDE channels as 0 and 1, and the SATA as 2 and 3. Needless to >> say, this little numbering scheme with grub has become confusing, esp >> with the introduction of new technology (SATA) >.>. Not sure how >> numbering would work with SCSI either (something I should try sometime), >> because I don't know how the BIOS numbers drives with SCSI cards or SATA >> drives put into the mix. >> > > Another good point. I suppose it's documented somewhere, but who has > time to > RTFM? :) > > -David Erm... although I don't mind the examples, the documentation for GRUB seems a bit lacking (manpage yields almost nothing, but there's a bit in "info grub"). Though, specifics like this aren't really explained. - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFe3y16CkrZkzMC68RAjEKAJ0dkl9N9qVxC2uvt1mdGyyhKAFgLQCeIL1o PGwdKfJ8an0hwfgM+dybPZc= =jVLX -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuration of Grub?
Good question; not sure about that one, since the BIOS may or may not count the EIDE channels as 0 and 1, and the SATA as 2 and 3. Needless to say, this little numbering scheme with grub has become confusing, esp with the introduction of new technology (SATA) >.>. Not sure how numbering would work with SCSI either (something I should try sometime), because I don't know how the BIOS numbers drives with SCSI cards or SATA drives put into the mix. Another good point. I suppose it's documented somewhere, but who has time to RTFM? :) -David -- [EMAIL PROTECTED] ~]# fortune Happiness is just an illusion, filled with sadness and confusion. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuration of Grub?
On 12/9/06, Karl Sinn <[EMAIL PROTECTED]> wrote: Hi, Am Samstag, 9. Dezember 2006 23:19 schrieb David Stanford: > title FreeBSD > root (hd1,0,a) > kernel /boot/loader This worked. But I have to say, I don't know why. It is the third harddisk in the system, and it's definitifly the slave on the second IDE-port. During the installation I had to identify the disk with ad3. How can grub mix the harddisks up and set this one to hd1? Is there any logic behind? Can't definitively explain this one. I'm assuming your first IDE port has a CD/DVD drive and the first disk? The *only* guess I have is that Grub, in fact, does only count existing hard drives and didn't find one of the first two (for whatever reason). Other than that, I got nothing. Anyway, glad you got it working. Anyway I already have the next problem: How to start KDE But I'll check the Handbook first and start a new thread if I don't manage. http://freebsd.kde.org/instructions.php Good luck! -David -- [EMAIL PROTECTED] ~]# fortune Happiness is just an illusion, filled with sadness and confusion. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuration of Grub?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Stanford wrote: >> Incorrect. If you installed the filesystem on ad3s1, it should be: >> >> root (hd3,0,a) > > > Thank you, I stand corrected. Not sure what I was thinking there... :) > > Many people goof up GRUB by accident because it's numbering system is >> zero-based and linux-like to a certain extent, so /dev/hda in Linux >> translates to hd0 in GRUB, which is also ad0 in FreeBSD. > > > This now leads me to a thought: does Grub count only *existing* hard drives > on your system or does it count the hard drive channels on your system? In > this case, Karl says he has installed FreeBSD on ad3, which makes me think > he has installed on a second SATA drive (more likely that on a fourth hard > drive I would think), and FreeBSD has counted two IDE channels as ad0 and > ad1, and two SATA channels as ad2 and ad3. If this is the case, and Grub > counts only the *existing* drives on his system, then he would have to use > (hd1,0,a), no? This would also explain the "disk is not existing" error he > was recieving. > > I'd be interested in hearing thoughts (or facts ;) on this as I hate being > left confused... :) > > -David Good question; not sure about that one, since the BIOS may or may not count the EIDE channels as 0 and 1, and the SATA as 2 and 3. Needless to say, this little numbering scheme with grub has become confusing, esp with the introduction of new technology (SATA) >.>. Not sure how numbering would work with SCSI either (something I should try sometime), because I don't know how the BIOS numbers drives with SCSI cards or SATA drives put into the mix. As an example, I'll use my Linux box (which has just EIDE drives in it): Filesystem (as basis for understanding what's going on): sprsd gcooper # fdisk -l Disk /dev/hda: 80.0 GB, 800 bytes 16 heads, 63 sectors/track, 155009 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/hda1 1 18601 9374872+ 83 Linux Partition 1 does not end on cylinder boundary. /dev/hda2 18602 20799 1107508+ 83 Linux Partition 2 does not end on cylinder boundary. /dev/hda3 * 20799 53311163863007 HPFS/NTFS Partition 3 does not end on cylinder boundary. /dev/hda4 53311 15500951255823+ 5 Extended Partition 4 does not end on cylinder boundary. /dev/hda5 53312 53427 58432+ 83 Linux /dev/hda6 53428 15500951197328 83 Linux For determining what's what, he could just load up the grub shell and type in... grub> root (hd0,0) Filesystem type is reiserfs, partition type 0x83 Note that it says what the partition type is and so you have an idea of where you are and what's going on. Yet, GRUB's understanding is limited because it doesn't directly understand NTFS, and hence I think that's what the chainloader command is present when booting Windows since it passes the ball for loading the OS to NTLDR (although a more technical document could help tell why): grub> root (hd0,1) Filesystem type unknown, partition type 0x83 - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFe1E+6CkrZkzMC68RAliBAJsHgkz/MlQ2tTHTvEkRZ4S64OWa6ACggsmu RgVBQbEE0IR74tInOPTX0RM= =Mch+ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuration of Grub?
Hi, Am Samstag, 9. Dezember 2006 23:19 schrieb David Stanford: > title FreeBSD > root (hd1,0,a) > kernel /boot/loader This worked. But I have to say, I don't know why. It is the third harddisk in the system, and it's definitifly the slave on the second IDE-port. During the installation I had to identify the disk with ad3. How can grub mix the harddisks up and set this one to hd1? Is there any logic behind? Anyway I already have the next problem: How to start KDE But I'll check the Handbook first and start a new thread if I don't manage. Thanks for all the help and information Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuration of Grub?
Incorrect. If you installed the filesystem on ad3s1, it should be: root (hd3,0,a) Thank you, I stand corrected. Not sure what I was thinking there... :) Many people goof up GRUB by accident because it's numbering system is zero-based and linux-like to a certain extent, so /dev/hda in Linux translates to hd0 in GRUB, which is also ad0 in FreeBSD. This now leads me to a thought: does Grub count only *existing* hard drives on your system or does it count the hard drive channels on your system? In this case, Karl says he has installed FreeBSD on ad3, which makes me think he has installed on a second SATA drive (more likely that on a fourth hard drive I would think), and FreeBSD has counted two IDE channels as ad0 and ad1, and two SATA channels as ad2 and ad3. If this is the case, and Grub counts only the *existing* drives on his system, then he would have to use (hd1,0,a), no? This would also explain the "disk is not existing" error he was recieving. I'd be interested in hearing thoughts (or facts ;) on this as I hate being left confused... :) -David -- [EMAIL PROTECTED] ~]# fortune Happiness is just an illusion, filled with sadness and confusion. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuration of Grub?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Stanford wrote:
>
> ad3 may be (and probably is) correct for you, but this has no relationship
> with the 'hdx' format that Grub uses. Using 'hd3' in your Grub config would
> suggest that you have installed FreeBSD on the fourth (counting 0, 1, 2, 3)
> hard drive on your machine. If you have only one hard drive on your machine
> and have installed FreeBSD on it, you would have to use 'hd0' (the *first*
> hard drive) in your config. You would use 'hd1' if you installed on your
> second hard drive, and so on. I would guess, since you mentioned ad3, that
> you have installed FreeBSD on a second hard drive; if so, try the
> following:
>
> title FreeBSD
>root (hd1,0,a)
>kernel /boot/loader
Incorrect. If you installed the filesystem on ad3s1, it should be:
root (hd3,0,a)
Many people goof up GRUB by accident because it's numbering system is
zero-based and linux-like to a certain extent, so /dev/hda in Linux
translates to hd0 in GRUB, which is also ad0 in FreeBSD.
The second argument refers to the partition itself (which may or may not
be 0), and the third argument refers to the slice.
So, in /dev/ad0s1a, this would translate to what I show shortly, in Grub:
root (hd0,0,a)
Another method for accomplishing the same thing from info grub. This may
or may not be outdated information:
4.2.3 FreeBSD
- -
GRUB can load the kernel directly, either in ELF or a.out format. But
this is not recommended, since FreeBSD's bootstrap interface sometimes
changes heavily, so GRUB can't guarantee to pass kernel parameters
correctly.
Thus, we'd recommend loading the very flexible loader `/boot/loader'
instead. See this example:
grub> root (hd0,a)
grub> kernel /boot/loader
grub> boot
> Right now Linux can not read the FreeBSD disk. Does FreeBSD have its own
>> filesystem?
>
>
> Yes, by default FreeBSD uses UFS2. There is almost certainly a third party
> app out there that will allow you to read UFS2 from Linux if this is what
> you want to do at some point. You can also check 'man mount' under SUSE to
> see if there is built-in support for mounting UFS2 filesystems (though this
> is probably a long shot).
UFS2 is supported with a custom kernel IIRC. So, you'll have to
recompile a kernel from sources on your Suse system.
> Ans if it has its own filesystem how can grub read the /boot/loader in
>> there?
>
>
> SUSE may not be able to read it, but remember that Grub is independent (so
> to speak) from Linux and has support for booting *BSD OS's.
Grub knows how to deal with different filesystem formats, but this may
or may not be due to the fact that it depends upon other things
available in the kernel that it bootstraps (grub has 2 boot stages). I
will have to look into this a bit further..
> Do I have to copy the loader on my Linux drive, configure it there so
>> FreeBSD
>> can then start?
No. Set it up on linux, making sure that you reference the correct
locations for kernels, and root disks, and you will be fine. If you have
a (GRUB) bootloader setup from Linux, configure everything from there;
don't worry about configuring any other bootloader in any OS, since
everything else is managed by your Linux bootloader.
> Is there any other way to start the system on that disk? From the
> install-CD
>> maybe?
>
>
> Hmm, never tried. You may have to use FreeSBIE for something like this,
> but,
> again, try your config first.
You can try booting from the grub shell as well (similar to bash). It
should say what the relevant key to enter in for entering the shell (C,
E, etc). Entering in the individual commands as noted above ("root...
loader") will help you test boot your FreeBSD OS.
Cheers,
- -Garrett
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFe0F96CkrZkzMC68RAuEaAJ9/8SrNjbgsUB0TsDluK1jSHqi25ACfa0rQ
dEGuwK4DP2JlcAVDu/xRb08=
=hVBk
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuration of Grub?
I tried this with (hd3,0,a) and (hd3,1,a). It didn't work. I got a message like: disk is not existing (don't remember the exact message) See below. If I understood right the hdd in Linux translates to ad3 in FreeBSD? > 1.) the hard drive and 2.) > the partition you installed FreeBSD on. hdd/ad3 I used all the disk for FreeBSD and I used the automatic configuration. ad3 may be (and probably is) correct for you, but this has no relationship with the 'hdx' format that Grub uses. Using 'hd3' in your Grub config would suggest that you have installed FreeBSD on the fourth (counting 0, 1, 2, 3) hard drive on your machine. If you have only one hard drive on your machine and have installed FreeBSD on it, you would have to use 'hd0' (the *first* hard drive) in your config. You would use 'hd1' if you installed on your second hard drive, and so on. I would guess, since you mentioned ad3, that you have installed FreeBSD on a second hard drive; if so, try the following: title FreeBSD root (hd1,0,a) kernel /boot/loader Right now Linux can not read the FreeBSD disk. Does FreeBSD have its own filesystem? Yes, by default FreeBSD uses UFS2. There is almost certainly a third party app out there that will allow you to read UFS2 from Linux if this is what you want to do at some point. You can also check 'man mount' under SUSE to see if there is built-in support for mounting UFS2 filesystems (though this is probably a long shot). Ans if it has its own filesystem how can grub read the /boot/loader in there? SUSE may not be able to read it, but remember that Grub is independent (so to speak) from Linux and has support for booting *BSD OS's. Do I have to copy the loader on my Linux drive, configure it there so FreeBSD can then start? No, not at all. Like I said, I'm sure your error is in your menu.lst 'root' config. Many people have dual-boot Linux/FreeBSD setups, and I myself used to have a Gentoo/FreeBSD/Windows setup using Grub way back, and copying files from one filesystem to another was never necessary. Is there any other way to start the system on that disk? From the install-CD maybe? Hmm, never tried. You may have to use FreeSBIE for something like this, but, again, try your config first. Good luck! -David -- [EMAIL PROTECTED] ~]# fortune Happiness is just an illusion, filled with sadness and confusion. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuration of Grub?
Hi, Am Samstag, 9. Dezember 2006 21:29 schrieb David Stanford: > What are you using now for your menu.lst? Still this?... > > title FreeBSD > root (hd3,0) > chainloader +1 no > I can almost guarantee that you have your 'root' specified incorrectly. You > should have something similar to the following (as mentioned earlier by > Pieter): > > title FreeBSD > root (hd0,1,a) > kernel /boot/loader I tried this with (hd3,0,a) and (hd3,1,a). It didn't work. I got a message like: disk is not existing (don't remember the exact message) If I understood right the hdd in Linux translates to ad3 in FreeBSD? > 1.) the hard drive and 2.) > the partition you installed FreeBSD on. hdd/ad3 I used all the disk for FreeBSD and I used the automatic configuration. Right now Linux can not read the FreeBSD disk. Does FreeBSD have its own filesystem? Ans if it has its own filesystem how can grub read the /boot/loader in there? Do I have to copy the loader on my Linux drive, configure it there so FreeBSD can then start? Is there any other way to start the system on that disk? From the install-CD maybe? > P.S. Welcome to FreeBSD! :) Thanks Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuration of Grub?
On 12/9/06, Karl Sinn <[EMAIL PROTECTED]> wrote: Hi, > I'm using this: > > title FreeBSD 6.2-STABLE > root (hd1,0,a) > kernel /boot/loader > > title FreeBSD 7.0-CURRENT > root (hd0,2,a) > kernel /boot/loader I tried, but it still does not work. Grub is giving a "file not found" message. If I understand it right it searches the /boot/loader on my Linux hard disk. I have found loader and loader.conf on the FreeBSD installation disk can I just copy them? What are you using now for your menu.lst? Still this?... title FreeBSD root (hd3,0) chainloader +1 I can almost guarantee that you have your 'root' specified incorrectly. You should have something similar to the following (as mentioned earlier by Pieter): title FreeBSD root (hd0,1,a) kernel /boot/loader Unlike a Linux boot entry, you have to specify the 'a' portion of 'root' in the menu.lst config. And remember that 'hd0' is defining exactly which hard drive you have FreeBSD installed on (in this example, the first hard drive), and '1' refers to the partition (in this example, the second partition). The 'a' will not have to be changed, assuming you performed a standard FreeBSD installation as this is the slice / is installed on by default. Give it another try with this info and reply back if you still have trouble. If you reply back, please include 1.) the hard drive and 2.) the partition you installed FreeBSD on. P.S. Welcome to FreeBSD! :) -David -- [EMAIL PROTECTED] ~]# fortune Happiness is just an illusion, filled with sadness and confusion. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuration of Grub?
Hi, > I'm using this: > > title FreeBSD 6.2-STABLE > root (hd1,0,a) > kernel /boot/loader > > title FreeBSD 7.0-CURRENT > root (hd0,2,a) > kernel /boot/loader I tried, but it still does not work. Grub is giving a "file not found" message. If I understand it right it searches the /boot/loader on my Linux hard disk. I have found loader and loader.conf on the FreeBSD installation disk can I just copy them? Thanks Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Configuration of Grub?
On Friday 08 December 2006 20:18, Karl Sinn wrote: > Hi, > > I am completely new here, and I did not find the answer to my problem. Not > in the FreeBSD Handbook and not in the Installations instruction. > > I have SuSE 10.1 installed with Grub. > > I wanted to try FreeBSD, and I installed it on hdd (Linux-name) I think it > is ad3 for FreeBSD. > > During the installation I chose "A" for automatic configuration and I > said "none" for the boot-manager. > > Now I wonder what I have write in the grub configuration file menu.lst to > finally start FreeBSD? > > I tried: > > title FreeBSD > kernel (hd0,1)/boot/loader root=/dev/hdd1 Hi, I'm using this: title FreeBSD 6.2-STABLE root (hd1,0,a) kernel /boot/loader title FreeBSD 7.0-CURRENT root (hd0,2,a) kernel /boot/loader to switch between -CURRENT and -STABLE. You need to specify the FreeBSD root partition, normally 'a'. For more information about FreeBSD partitions and slices, see http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disk-organization.html Regards, Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Configuration of Grub?
Hi, I am completely new here, and I did not find the answer to my problem. Not in the FreeBSD Handbook and not in the Installations instruction. I have SuSE 10.1 installed with Grub. I wanted to try FreeBSD, and I installed it on hdd (Linux-name) I think it is ad3 for FreeBSD. During the installation I chose "A" for automatic configuration and I said "none" for the boot-manager. Now I wonder what I have write in the grub configuration file menu.lst to finally start FreeBSD? I tried: title FreeBSD kernel (hd0,1)/boot/loader root=/dev/hdd1 AND title FreeBSD root (hd3,0) chainloader +1 First wasmade by YaST and the second is what I found on the Internet. None of them worked. Where is my mistake? Thanks Karl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
