Bootloader/Replace GRUB
Hello, I replaced a Linux partition on my laptop with FreeBSD. Now it will not but giving me an GRUB error. I assume I have to remove/replace GRUB, as I will want to dual boot this with a windows partition. So being the FreeBSD newbie that I am I am stumped on what to do to correct this. Thanks, Lou ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bootloader/Replace GRUB
On 05/13/2013 19:41, Louis Ciotti wrote: Hello, I replaced a Linux partition on my laptop with FreeBSD. Now it will not but giving me an GRUB error. I assume I have to remove/replace GRUB, as I will want to dual boot this with a windows partition. So being the FreeBSD newbie that I am I am stumped on what to do to correct this. Thanks, Lou ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Hi, If it's an MBR partition, you can boot from a live CD (or installation CD and choose Live CD), log in as root and: /sbin/gpart bootcode -b /boot/boot0 ada0 where ada0 is the HDD device. (Check gpart man page for more examples and parameters) This will create a simple boot selector where you can choose between Windows/FreeBSD. There's also grub and grub2 in the ports but I've not tried. -Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Bootloader/Replace GRUB
On Mon, 2013-05-13 at 12:41 -0400, Louis Ciotti wrote:
Hello,
I replaced a Linux partition on my laptop with FreeBSD. Now it will not
but giving me an GRUB error. I assume I have to remove/replace GRUB, as I
will want to dual boot this with a windows partition.
So being the FreeBSD newbie that I am I am stumped on what to do to correct
this.
Unfortunately I need to install Windows to test hardware that is less
good supported by Linux and FreeBSD, I guess it should be able to boot
Windows by a chainloader. I'm using GRUB2 from Linux to boot between
FreeBSD and Linux installs.
I converted a GRUB legacy menu.lst to a GRUB 2 grub.cfg using an
application doing the work for me, that's why there are strange commands
in my grub.cfg [1].
I planned to install Windows first and after that to edit the grub.cfg,
but because you need help, I'll google now to help myself too ;).
I found this:
menuentry Microsoft Windows XP Home Edition (on /dev/sda1) {
insmod fat
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 2629-16f0
drivemap -s (hd0) ${root}
chainloader +1
}
But I guess, it can be written as it's done for my FreeBSD [1], the
above entry perhaps is done by this GRUB-auto-thingy, something I don't
use.
Backup your MBRs (or what ever you're using ;), before you continue ;)!
[1]
set timeout=8
set default='0'; if [ x$default = xsaved ]; then load_env; set
default=$saved_entry; fi
set color_normal='light-blue/black'; set
color_highlight='light-cyan/blue'
menuentry FreeBSD{
set root=(hd0,msdos1)
chainloader +1
}
menuentry 'Ubuntu Quantal,kernel 3.6.5-rt14' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
'root=/dev/sdb9' 'ro' 'quiet' ''
legacy_initrd '/boot/initrd.img-3.6.5-rt14'
'/boot/initrd.img-3.6.5-rt14'
}
menuentry 'Ubuntu Quantal,kernel 3.5.0-18-lowlatency
threadirqs' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb9' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Quantal,kernel 3.5.0-18-lowlatency (recovery
mode)' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb9' 'ro' 'single'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Studio Quantal, Kernel 3.6.5-rt14' {
set root='(hd1,13)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
'root=/dev/sdb13' 'ro' 'quiet'
legacy_initrd '/boot/initrd.img-3.6.5-rt14'
'/boot/initrd.img-3.6.5-rt14'
}
menuentry 'Ubuntu Studio Quantal, Kernel 3.5.0-18-lowlatency
threadirqs' {
set root='(hd1,13)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.5.0-18-lowlatency'
'/boot/vmlinuz-3.5.0-18-lowlatency' 'root=/dev/sdb13' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.5.0-18-lowlatency'
'/boot/initrd.img-3.5.0-18-lowlatency'
}
menuentry 'Ubuntu Studio Precise, Kernel 3.0.30 threadirqs' {
#set root='(hd1,1)'; set legacy_hdbias='0'
#legacy_kernel '/boot/vmlinuz-3.0.30' '/boot/vmlinuz-3.0.30'
'root=UUID=338316fb-364e-4a43-8deb-738127f878ce' 'ro' 'quiet'
'threadirqs'
set root='(hd2,1)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.0.30' '/boot/vmlinuz-3.0.30'
'root=UUID=948e9fa0-1bb5-4fd4-847c-a7cfbc816a40' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.0.30' '/boot/initrd.img-3.0.30'
}
menuentry 'Ubuntu Studio Precise, Kernel 3.2.0-23-lowlatency
threadirqs' {
#set root='(hd1,1)'; set legacy_hdbias='0'
#legacy_kernel '/boot/vmlinuz-3.2.0-23-lowlatency'
'/boot/vmlinuz-3.2.0-23-lowlatency'
'root=UUID=338316fb-364e-4a43-8deb-738127f878ce' 'ro' 'quiet'
'threadirqs'
set root='(hd2,1)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.2.0-23-lowlatency'
'/boot/vmlinuz-3.2.0-23-lowlatency'
'root=UUID=948e9fa0-1bb5-4fd4-847c-a7cfbc816a40' 'ro' 'quiet'
'threadirqs'
legacy_initrd '/boot/initrd.img-3.2.0-23-lowlatency'
'/boot/initrd.img-3.2.0-23-lowlatency'
}
menuentry 'AVlinux 5.0.3, Kernel 3.0.23-rt40' {
set root='(hd1,11)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.0.23-rt40'
'/boot/vmlinuz-3.0.23-rt40' 'root=/dev/sdb11' 'ro' 'quiet'
legacy_initrd '/boot/initrd.img-3.0.23-rt40'
'/boot/initrd.img-3.0.23-rt40'
}
menuentry 'AVlinux 5.0.3, Kernel 3.0.23-avl-7-pae threadirqs' {
set root='(hd1,11)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.0.23-avl-7-pae'
'/boot/vmlinuz-3.0.23-avl-7-pae' 'root=/dev/sdb11' 'ro' 'threadirqs'
'quiet'
legacy_initrd '/boot/initrd.img-3.0.23-avl-7-pae'
'/boot/initrd.img-3.0.23-avl-7-pae'
}
menuentry 'Edubuntu 10.10,Kernel 2.6.33.9-rt31' {
set root
Re: Bootloader/Replace GRUB
This one is tricky, but it does work.
I've got two SATA HDDs, Linux names are sda and sdb.
/dev/sda1 is ufs including my FreeBSD and /dev/sdb1 is ntfs including
the Windows XP install, there are many other installs, all of them are
Linux distros.
To install XP on /dev/sdb1 I had to disconnect /dev/sda1.
With Windows
This assumes that your Windows partition is sda3. Remember you need to
point set root and chainloader to the system reserve partition that
windows made when it installed, not the actual partition windows is on.
This example works if your system reserve partition is sda3.
# (2) Windows XP
menuentry Windows XP {
set root=(hd0,3)
chainloader (hd0,3)+1
}
If the Windows bootloader is on an entirely different hard drive than
GRUB, it may be necessary to trick Windows into believing that it is the
first hard drive. This was possible with drivemap. Assuming GRUB is on
hd0 and Windows is on hd2, you need to add the following after set root:
drivemap -s hd0 hd2 - https://wiki.archlinux.org/index.php/Grub#Dual-booting
So for my grub.cfg on a Linux on /dev/sdb9, resp. inside the MBR of sda,
I need to add a chainloader.
[rocketmouse@archlinux ~]$ cat /mnt/q/boot/grub/grub.cfg
set timeout=8
set default='0'; if [ x$default = xsaved ]; then load_env; set
default=$saved_entry; fi
set color_normal='light-blue/black'; set color_highlight='light-cyan/blue'
menuentry FreeBSD{
set root=(hd0,msdos1)
chainloader +1
}
menuentry XP{
set root=(hd1,1)
drivemap -s hd0 hd1
chainloader +1
}
menuentry 'Ubuntu Quantal,kernel 3.6.5-rt14' {
set root='(hd1,9)'; set legacy_hdbias='0'
legacy_kernel '/boot/vmlinuz-3.6.5-rt14' '/boot/vmlinuz-3.6.5-rt14'
'root=/dev/sdb9' 'ro' 'quiet' ''
legacy_initrd '/boot/initrd.img-3.6.5-rt14' '/boot/initrd.img-3.6.5-rt14'
}
[snip]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
which media type I must use when booting ISO from grub
HI I want to install freebse and boot it from grub as: title FreeBSD 8.0 (USB) map --mem (hd0,0)/iso/FreeBSD8.iso (hd32) map --hook chainloader (hd32) boot Which media type I must use when choosing 'media type' in menu? as one way to solve problem is extract 8.2-RELEASE and packages directories to root of FlashDrive. but how to skip coping files from .iso? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dual Booting Linux with FreeBSD 9.0 - Grub in MBR
On Fri, 27 Jan 2012 21:32:10 +
Kaya Saman kayasa...@gmail.com wrote:
Hi,
am just wondering if anyone has successfully managed to boot FreeBSD
9.0 and Linux.
I run Fedora 16 x64 with Grub installed in my MBR.
FBSD9 installed as the new disk scheme GPT. I think (I manually
partitioned as my disk is quite crowded).
Anyway I found this:
http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234858.html
and at the moment I have this in my Grub config:
menuentry 'FreeBSD 9.0' {
set root=(ada0,1,a)
kfreebsd /boot/loader
boot
}
But unfortunately no boot :-(
I have tried using (hd0,0), (hd0,1,a), (hd0,0,a), and (hd0,a) but
unfortunately nothing is working.
The Grub version is 2.
Can anyone help me?
Hi
I have the following partition layout
P1 linux swap
P2 FreeBSD
P3 linux
P4 extended which holds 2 more linux partitions
FreeBSD 9 installed on P2 and the FreeBSD bootloader on P2
In /etc/grub.d/40_custom I have put the following:
menuentry FreeBSD {
set root=(hd0,2)
chainloader +1
}
Then run update-grub as root.
The (hd0,2) entry means first harddisk (this laptop only has one) and
the second partition, which holds the FreeBSD bootloader that gets
loaded with the enry chainloader +1.
This works for me. Hope it helps.
I think with the way you have the setup now, a module must be loaded
first in the grub config. Insmod ufs or similair.
Disclaimer: http://www.ose.nl/email
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dual Booting Linux with FreeBSD 9.0 - Grub in MBR
On 01/28/2012 08:54 AM, Bas Smeelen wrote:
On Fri, 27 Jan 2012 21:32:10 +
Kaya Samankayasa...@gmail.com wrote:
Hi,
am just wondering if anyone has successfully managed to boot FreeBSD
9.0 and Linux.
I run Fedora 16 x64 with Grub installed in my MBR.
FBSD9 installed as the new disk scheme GPT. I think (I manually
partitioned as my disk is quite crowded).
Anyway I found this:
http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234858.html
and at the moment I have this in my Grub config:
menuentry 'FreeBSD 9.0' {
set root=(ada0,1,a)
kfreebsd /boot/loader
boot
}
But unfortunately no boot :-(
I have tried using (hd0,0), (hd0,1,a), (hd0,0,a), and (hd0,a) but
unfortunately nothing is working.
The Grub version is 2.
Can anyone help me?
Hi
I have the following partition layout
P1 linux swap
P2 FreeBSD
P3 linux
P4 extended which holds 2 more linux partitions
FreeBSD 9 installed on P2 and the FreeBSD bootloader on P2
In /etc/grub.d/40_custom I have put the following:
menuentry FreeBSD {
set root=(hd0,2)
chainloader +1
}
Then run update-grub as root.
The (hd0,2) entry means first harddisk (this laptop only has one) and
the second partition, which holds the FreeBSD bootloader that gets
loaded with the enry chainloader +1.
This works for me. Hope it helps.
I think with the way you have the setup now, a module must be loaded
first in the grub config. Insmod ufs or similair.
Disclaimer: http://www.ose.nl/email
Thanks for the response!!
Actually I got this working but eventually was up for nearly 24 hours
which meant I was too tired to post back here :-)
My Grub is just weird! Which is why I couldn't work things out. For
anyone running Fedora 16 or alike this may help; I have this partition
layout:
1. FreeBSD UFS2
4. Extended Partition
5. Linux / Ext4
2 Linux Swap
3 Linux JFS
Don't ask why 4,5 partitions but Fedora installer took over and left me
with no control otherwise Fedora should have been on 2.
Now the Grub entry is as follows:
menuentry 'FreeBSD 9.0' {
insmod part_msdos
set root='(hd0,msdos1)'
chainloader +1
}
I have no idea why my version of grub is sooo different from everyone
elses as finding many dualboot bsd/linux combos with Grub entries being
more like yours, Bas, this is certainly puzzling.
Anyhow the situation is solved :-)
Regards,
Kaya
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Dual Booting Linux with FreeBSD 9.0 - Grub in MBR
Hi,
am just wondering if anyone has successfully managed to boot FreeBSD 9.0
and Linux.
I run Fedora 16 x64 with Grub installed in my MBR.
FBSD9 installed as the new disk scheme GPT. I think (I manually
partitioned as my disk is quite crowded).
Anyway I found this:
http://lists.freebsd.org/pipermail/freebsd-questions/2011-October/234858.html
and at the moment I have this in my Grub config:
menuentry 'FreeBSD 9.0' {
set root=(ada0,1,a)
kfreebsd /boot/loader
boot
}
But unfortunately no boot :-(
I have tried using (hd0,0), (hd0,1,a), (hd0,0,a), and (hd0,a) but
unfortunately nothing is working.
The Grub version is 2.
Can anyone help me?
Thanks
Kaya
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ot :stuck in GRUB
Hi all, A Friend of mine has some version of either *nux or bsd installed (he does not even know for sure), turns out he clicked yes for some updates to install and upon restarting he now winds up at GRUB , I told him to type boot and it reports kernel must loaded prior to booting I really have no time to get out there, so he shipped me his hard drive which I should be receiving today or tomorrow. It *seems* to me the update may have corrupted some type of conf file, am I on the right track here? Does anyone have any suggestion, since its an old friend I can't charge him, but nor do I want to spend a significant amount of time on it. TIA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ot :stuck in GRUB
Hi all, A Friend of mine has some version of either *nux or bsd installed (he does not even know for sure), turns out he clicked yes for some updates to install and upon restarting he now winds up at GRUB , I told him to type boot and it reports kernel must loaded prior to booting I really have no time to get out there, so he shipped me his hard drive which I should be receiving today or tomorrow. It *seems* to me the update may have corrupted some type of conf file, am I on the right track here? Does anyone have any suggestion, since its an old friend I can't charge him, but nor do I want to spend a significant amount of time on it. TIA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ot : stuck in GRUB
GRUB is the boot program for several versions of Linux, not for FreeBSD. For a useful answer, ask where Linux weenies hang out, not here. Or even better, just google for the text of the error message. R's, John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ot : stuck in GRUB
On Tue, 27 Sep 2011, John Levine wrote: GRUB is the boot program for several versions of Linux, not for FreeBSD. But many people also use it to boot FreeBSD in multi-boot situations. The pkg-message in sysutils/grub and sysutils/grub2 might help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Grub demage my boot loader
Hello, I am new in this mailing list and my english is very poor :) I have installed FBSD 8.0 on my first SATA disk. I downloaded Ubuntu 9.10 CD and boot into the Ubuntu installation. After booting proces a choose 4GB USB memory for installation as hard drive. There is option: delete and use whole disk for Ubuntu. After installation and reboot I have error message - error: no such disk and something like CLI (grub rescue). A tried steps by this link: http://lists.freebsd.org/pipermail/ freebsd-questions/2004-May/047549.html but without luck - there is still Grub! Also I tried step from this page: https://help.ubuntu.com/community/ Grub2 but advices/commands (like boot, normal or dump, etc) doesn't work! Is there any way to solve my issue? Thank you very much for any advices! Jindra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Grub demage my boot loader
On Fri, Mar 26, 2010 at 3:56 PM, Jindřich Káňa jindr...@kana.at wrote: Hello, I am new in this mailing list and my english is very poor :) I have installed FBSD 8.0 on my first SATA disk. I downloaded Ubuntu 9.10 CD and boot into the Ubuntu installation. After booting proces a choose 4GB USB memory for installation as hard drive. There is option: delete and use whole disk for Ubuntu. After installation and reboot I have error message - error: no such disk and something like CLI (grub rescue). A tried steps by this link: http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/047549.html but without luck - there is still Grub! Also I tried step from this page: https://help.ubuntu.com/community/Grub2 but advices/commands (like boot, normal or dump, etc) doesn't work! Is there any way to solve my issue? Looks like you are not that fluent in dual/multiple boot schemes. I would suggest that you buy another sata disk and install FBSD in one and Linux on the other and boot selection with your BIOS. Either that, or RTFM on multiple boot systems, whether it's booting FBSD from Linux (grub) or the other way around. You could start by Googling this: dual boot linux freebsd there are many references on the list archives on the subject and many other references as well. Best, Alejandro Imass Thank you very much for any advices! Jindra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Grub demage my boot loader
I love the RTFM - who came up with that anyway? That said Jindřich, your English is more than passable! Have a good weekend! G -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Alejandro Imass Sent: Friday, March 26, 2010 4:46 PM To: freebsd-questions@freebsd.org Subject: Re: Grub demage my boot loader On Fri, Mar 26, 2010 at 3:56 PM, Jindřich Káňa jindr...@kana.at wrote: Hello, I am new in this mailing list and my english is very poor :) I have installed FBSD 8.0 on my first SATA disk. I downloaded Ubuntu 9.10 CD and boot into the Ubuntu installation. After booting proces a choose 4GB USB memory for installation as hard drive. There is option: delete and use whole disk for Ubuntu. After installation and reboot I have error message - error: no such disk and something like CLI (grub rescue). A tried steps by this link: http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/047549.html but without luck - there is still Grub! Also I tried step from this page: https://help.ubuntu.com/community/Grub2 but advices/commands (like boot, normal or dump, etc) doesn't work! Is there any way to solve my issue? Looks like you are not that fluent in dual/multiple boot schemes. I would suggest that you buy another sata disk and install FBSD in one and Linux on the other and boot selection with your BIOS. Either that, or RTFM on multiple boot systems, whether it's booting FBSD from Linux (grub) or the other way around. You could start by Googling this: dual boot linux freebsd there are many references on the list archives on the subject and many other references as well. Best, Alejandro Imass Thank you very much for any advices! Jindra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Dual booting Windows 7 and FreeBSD (and possibly GRUB)
Well, Windows 7 isn't playing nicely with FreeBSD (and some other OS systems). I have my first primary partition (MBR scheme) installed with Windows 7 and I want to have FreeBSD as second primary partition. Eventually, I want to have Ubuntu on my first and second extended partitions. Any suggestions? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dual booting Windows 7 and FreeBSD (and possibly GRUB)
On Tue, 23 Feb 2010 14:20:27 +0200, Angelin Lalev lalev.ange...@gmail.com wrote: Well, Windows 7 isn't playing nicely with FreeBSD (and some other OS systems). I have my first primary partition (MBR scheme) installed with Windows 7 and I want to have FreeBSD as second primary partition. Eventually, I want to have Ubuntu on my first and second extended partitions. Any suggestions? FreeBSD brings its own boot manager that can be installed. As far as I know, it should be installed after the Windows installation, because it would be overwritten otherwise. If you're planning to also use Linux, I think GRUB may be a good solution. As I am not using multi-boot environments, I can't be more precise. But go ahead and try the presented suggestions. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dual booting Windows 7 and FreeBSD (and possibly GRUB)
Angelin Lalev skrev 2010-02-23 13:20: Well, Windows 7 isn't playing nicely with FreeBSD (and some other OS systems). I have my first primary partition (MBR scheme) installed with Windows 7 and I want to have FreeBSD as second primary partition. Eventually, I want to have Ubuntu on my first and second extended partitions. Any suggestions? ___ I use the following boot manager because when I set this up there was new behaviour of the Windows Vista boot method and it didn't play well with Freebsd's bootmanager. Today I run Windows 7 and Freebsd 8 on this system. http://neosmart.net/dl.php?id=1 You can find instructions in bsdmag on how to set it up. http://bsdmag.org/app/files/download?attachment=attachment1model=Articlemodel_id=9300portal_id=134 Or http://bsdmag.org/pdf-articles And choose Download Free Issue: FreeBSD Ins Outs /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dual booting Windows 7 and FreeBSD (and possibly GRUB)
On Tue, 23 Feb 2010 08:23:44 -0500, Leslie Jensen les...@eskk.nu wrote: Angelin Lalev skrev 2010-02-23 13:20: Well, Windows 7 isn't playing nicely with FreeBSD (and some other OS systems). I have my first primary partition (MBR scheme) installed with Windows 7 and I want to have FreeBSD as second primary partition. Eventually, I want to have Ubuntu on my first and second extended partitions. Any suggestions? ___ I use the following boot manager because when I set this up there was new behaviour of the Windows Vista boot method and it didn't play well with Freebsd's bootmanager. Today I run Windows 7 and Freebsd 8 on this system. http://neosmart.net/dl.php?id=1 You can find instructions in bsdmag on how to set it up. I'm using GAG http://gag.sourceforge.net/ -- Using Opera's 10.50 pre-Alpha -- because I'm a f*cking maniac! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dual booting Windows 7 and FreeBSD (and possibly GRUB)
Even if you installed FreeBSD *before* Windows, you can restore the FreeBSD boot manager with sysinstall (select the Custom installation from the main menu), for example. Or GRUB can also be another way to go, of course. -- AngryWolf On 2010.02.23. 13:58, Polytropon wrote: FreeBSD brings its own boot manager that can be installed. As far as I know, it should be installed after the Windows installation, because it would be overwritten otherwise. If you're planning to also use Linux, I think GRUB may be a good solution. As I am not using multi-boot environments, I can't be more precise. But go ahead and try the presented suggestions. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dual booting Windows 7 and FreeBSD (and possibly GRUB)
or simply do an fdisk -B bsdlabel -B /dev/ad0s2 or similar On 23 February 2010 13:16, AngryWolf angrywolf2...@gmail.com wrote: Even if you installed FreeBSD *before* Windows, you can restore the FreeBSD boot manager with sysinstall (select the Custom installation from the main menu), for example. Or GRUB can also be another way to go, of course. -- AngryWolf On 2010.02.23. 13:58, Polytropon wrote: FreeBSD brings its own boot manager that can be installed. As far as I know, it should be installed after the Windows installation, because it would be overwritten otherwise. If you're planning to also use Linux, I think GRUB may be a good solution. As I am not using multi-boot environments, I can't be more precise. But go ahead and try the presented suggestions. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dual booting Windows 7 and FreeBSD (and possibly GRUB)
On Tue, 23 Feb 2010 14:16:53 +0100, AngryWolf angrywolf2...@gmail.com wrote: Even if you installed FreeBSD *before* Windows, you can restore the FreeBSD boot manager with sysinstall (select the Custom installation from the main menu), for example. Well... in fact, that's not restoring the boot manager, this is re-installing the boot manager. :-) You can install the boot manager also from a FreeBSD live file system or fixit console, using the boot0cfg command, if I remember that procedure correctly. Or GRUB can also be another way to go, of course. Especially in conjunction with Linux as another OS on the disk, I think this would be the most comfortable solution. But as I said, I'm no multi-booter. =^_^= -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot0 / LILO / GRUB: dual boot FreeBSD and Linux
Thanks, this is great! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
boot0 / LILO / GRUB: dual boot FreeBSD and Linux
I'm getting a new desktop through my university which will come installed with Windows Vista. Obviously, my first action item will be removing Vista and installing a reasonable OS. Due to the need to be up-and-running immediately with an OS that I'm comfortable with, I'll be installing Linux (probably Ubuntu). But I'd like to set-up FreeBSD also. Which of the boot managers do you suggest I use? Which OS should I install first? Since I've never set-up a FreeBSD/Linux dual-boot system, I don't know what, if any, pitfalls to avoid. I'm hoping some of you will have experience I can learn from. Any relevant advice would be greatly appreciated. TIA, Daniel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot0 / LILO / GRUB: dual boot FreeBSD and Linux
I'm getting a new desktop through my university which will come installed with Windows Vista. Obviously, my first action item will be removing Vista and installing a reasonable OS. Due to the need to be up-and-running immediately with an OS that I'm comfortable with, I'll be installing Linux (probably Ubuntu). But I'd like to set-up FreeBSD also. Which of the boot managers do you suggest I use? Which OS should I install first? Since I've never set-up a FreeBSD/Linux dual-boot system, I don't know what, if any, pitfalls to avoid. I'm hoping some of you will have experience I can learn from. Any relevant advice would be greatly appreciated. Hi, I'm primarily an Ubuntu Linux user, but I've experimented with FreeBSD desktops and servers quite a bit (servers especially). One thing I found to be really cool is the FreeBSD boot manager. I would strongly recommend using the FreeBSD boot manager because it's completely standalone; it does not depend on any files or data sitting in your partitions. The boot manager sits within the first 512 bytes of your hard drive (the MBR) and it does not need any other data to function. The way it works is simple. Well first a disclaimer. What I describe here, I'm pretty confident that I know what I'm talking about, but there is a chance that my knowledge is wrong. In that case please correct me, someone. The FreeBSD boot manager (I don't know the official name for it off the top of my head), when run, looks at the partitions on the hard drive. It then presents a menu, where you press a function key to select which partition to boot. It basically delegates the booting to the boot record on the partition of your choice. The way to set this up is as follows. Well, I'm sure it's possible to install FreeBSD first and then Linux, but I will describe it the other way. First install Linux normally (well leaving space on your hard drive for a FreeBSD partition, which needs to be primary and not extended). After you install Linux, boot up and do some magic where you install the boot manager (such as Grub or Lilo) onto the boot record of the Linux parttion. Normally the boot manager for Linux will be installed in the MBR, but put it on the partition's boot sector as well. Now install FreeBSD. Install the FreeBSD boot manager. It will not touch the Linux partition at all, the FreeBSD install will only write to the FreeBSD partition and to the MBR. I would not recommend using Grub as a boot manager (for the MBR) because it depends on files sitting on your Linux partition as far as I know. So when you wipe your Linux partition for some reason you won't be able to boot any more. Same goes for Lilo I think. The FreeBSD boot manager does not depend on any data outside of the MBR, so it will continue working properly after you wipe a partition clean. See here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html It appears that the boot manager is called boot0. If you ever want to back up your MBR for some reason, which includes the partition table and the boot program, you can do something like this: dd if=/dev/hda of=my-mbr-saved-file bs=512 count=1 where /dev/hda would be changed depending on OS and hard disk configuration. Then you can restore the MBR: dd if=my-mbr-saved-file of=/dev/hda bs=512 count=1 But restoring should be done with extreme caution because it will rewrite your partition table and could lead to lost data because of that. I have installed the FreeBSD boot manager by using dd after combining the 446-byte long program with an existing partition table ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: GRUB: Filesystem type unknown (ufs2)
--- On Thu, 11/13/08, Unga [EMAIL PROTECTED] wrote: From: Unga [EMAIL PROTECTED] Subject: GRUB: Filesystem type unknown (ufs2) To: freebsd-questions@FreeBSD.org Date: Thursday, November 13, 2008, 6:24 PM Hi all I have compiled and installed grub-0.97.tar.gz on FreeBSD 7.0 (i386). It shows the grub cannot recognize ufs2 file systems. grub root (hd1,0, Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 All stage1, stage2 and *_stage1_5 are in /boot/grub/. The fstype used for bsdlabel for b is swap and for others its 4.2BSD. Files systems were created as follows: newfs -U /dev/ad2s1a newfs /dev/ad2s1d newfs -U /dev/ad2s1e newfs -U /dev/ad2s1f Ok, found the problem. Its the newfs. The problem is GRUB cannot recognize ufs2 file systems created by newfs. The GRUB can recognize ufs2 file systems created by sysinstall. I have even tried newfs -O 2 -U /dev/ad2s1a, the GRUB still cannot recognize ufs2 file systems. Now the question is, how to properly create a ufs2 file system manually? Is it by newfs? Also appreciate if someone could let me know where does it create ufs2 file systems in sysinstall. Best regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
On Thursday 13 November 2008, Unga wrote: --- On Thu, 11/13/08, Pieter de Goeje [EMAIL PROTECTED] wrote: I've used GRUB in the past to boot FreeBSD. The GRUB boot directory was located on the FreeBSD root partition, so it can work. I did use the port though. Now the issue is the root partition itself cannot access. Were your partitions ufs2? Which version of GRUB you used? Any possibility to give it a try again? Yes, the root was UFS2. I don't know which version I used at the time. When I get home from work, I'll give it a try. -- 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]
Re: GRUB: Filesystem type unknown (ufs2)
On Thu, Nov 13, 2008 at 02:24:33AM -0800, Unga wrote: Hi all I have compiled and installed grub-0.97.tar.gz on FreeBSD 7.0 (i386). It shows the grub cannot recognize ufs2 file systems. grub root (hd1,0, Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 All stage1, stage2 and *_stage1_5 are in /boot/grub/. The fstype used for bsdlabel for b is swap and for others its 4.2BSD. Files systems were created as follows: newfs -U /dev/ad2s1a newfs /dev/ad2s1d newfs -U /dev/ad2s1e newfs -U /dev/ad2s1f Do others experience this issue? Do I need to patch the Grub to recognize ufs2 file systems? Your reply is very much appreciated. How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. ftp://alpha.gnu.org/gnu/grub/ -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
--- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
On Thu, Nov 13, 2008 at 03:16:40AM -0800, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. I think these kinds of questions should probably go to the GNU GRUB folks though, don't you think? I don't mean to sound like I'm stepping on your efforts, but the sysutils/grub port has very little to it (meaning, issues/problems of this type should very likely be issues with GRUB itself and not with the port or FreeBSD). It would be really cool if since you're working on getting GRUB2 working, you could make a port for it, e.g. sysutils/grub2. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
On Thursday 13 November 2008, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: GRUB: Filesystem type unknown (ufs2) To: Unga [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Thursday, November 13, 2008, 7:21 PM On Thu, Nov 13, 2008 at 03:16:40AM -0800, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. I think these kinds of questions should probably go to the GNU GRUB folks though, don't you think? I don't mean to sound like I'm stepping on your efforts, but the sysutils/grub port has very little to it (meaning, issues/problems of this type should very likely be issues with GRUB itself and not with the port or FreeBSD). Well, I thought FreeBSD guys use GRUB. Its easy to communicate with those who use FreeBSD rather than those who use Linux and discuss mostly on a theoretical basis. I mostly wanted to know does GRUB works for other FreeBSD users. If so, I could investigate what went wrong on mine. Btw, I did not use the port, its straight away compiled from sources. That I mentioned as the first line in my original post. Regards Unga I've used GRUB in the past to boot FreeBSD. The GRUB boot directory was located on the FreeBSD root partition, so it can work. I did use the port though. -- 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]
Re: GRUB: Filesystem type unknown (ufs2)
--- On Thu, 11/13/08, Pieter de Goeje [EMAIL PROTECTED] wrote: I've used GRUB in the past to boot FreeBSD. The GRUB boot directory was located on the FreeBSD root partition, so it can work. I did use the port though. Now the issue is the root partition itself cannot access. Were your partitions ufs2? Which version of GRUB you used? Any possibility to give it a try again? Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
--- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: GRUB: Filesystem type unknown (ufs2) To: Unga [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Thursday, November 13, 2008, 7:21 PM On Thu, Nov 13, 2008 at 03:16:40AM -0800, Unga wrote: --- On Thu, 11/13/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: How about asking the GNU GRUB folks if GRUB 0.97 supports UFS2? It seems some old version of GRUB on a old version of FreeBSD has worked: http://lists.freebsd.org/pipermail/freebsd-hackers/2004-May/006944.html Also, GRUB is up to 1.96, and does work with amd64. The port is horribly outdated. I don't mind try GRUB 1.96. The problem is I have never used GRUB2 and I have no idea how to configure it. Is there a good notes/documentation on how to use GRUB2? What I need basically is where to put files (eg. stage1, stage2 and *_stage1_5 of GRUB1 in /boot/grub/.) and a sample configuration file. Anyway meanwhile I'll try to find some documentation. ftp://alpha.gnu.org/gnu/grub/ I got my file from above location. I think these kinds of questions should probably go to the GNU GRUB folks though, don't you think? I don't mean to sound like I'm stepping on your efforts, but the sysutils/grub port has very little to it (meaning, issues/problems of this type should very likely be issues with GRUB itself and not with the port or FreeBSD). Well, I thought FreeBSD guys use GRUB. Its easy to communicate with those who use FreeBSD rather than those who use Linux and discuss mostly on a theoretical basis. I mostly wanted to know does GRUB works for other FreeBSD users. If so, I could investigate what went wrong on mine. Btw, I did not use the port, its straight away compiled from sources. That I mentioned as the first line in my original post. Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
GRUB: Filesystem type unknown (ufs2)
Hi all I have compiled and installed grub-0.97.tar.gz on FreeBSD 7.0 (i386). It shows the grub cannot recognize ufs2 file systems. grub root (hd1,0, Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 All stage1, stage2 and *_stage1_5 are in /boot/grub/. The fstype used for bsdlabel for b is swap and for others its 4.2BSD. Files systems were created as follows: newfs -U /dev/ad2s1a newfs /dev/ad2s1d newfs -U /dev/ad2s1e newfs -U /dev/ad2s1f Do others experience this issue? Do I need to patch the Grub to recognize ufs2 file systems? Your reply is very much appreciated. Kind regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB: Filesystem type unknown (ufs2)
I'm using GRUB and it has no problem recognizing UFS2 slices. Same version than you, GRUB 0.97. Regards Ezequiel R. Aguerre 2008/11/13 Unga [EMAIL PROTECTED] --- On Thu, 11/13/08, Pieter de Goeje [EMAIL PROTECTED] wrote: I've used GRUB in the past to boot FreeBSD. The GRUB boot directory was located on the FreeBSD root partition, so it can work. I did use the port though. Now the issue is the root partition itself cannot access. Were your partitions ufs2? Which version of GRUB you used? Any possibility to give it a try again? Regards Unga ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Dual booting FreeBSD and Linux using GRUB fails
I have an all-SCSI system with FreeBSD 6.3 on one disk and 7.0 on the other. It booted using GRUB and worked OK. I installed Mandriva Linux on the disk that had 7.0 on it (replacing 7.0) The setup now is: SCSI ID 15 73GB /dev/sda - running FreeBSD SCSI ID 14 36GB /dev/sdb - Mandriva The device names above are as reported by Mandriva when doing the install. Mandriva installed OK onto the 36GB HDD and wrote this menu.lst: Code: timeout 10 color black/cyan yellow/cyan gfxmenu (hd0,0)/boot/gfxmenu default 0 title linux kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=77a15e0a-b9f5-46ab-8236-886418dbbfd8 resume=/dev/sdb5 splash=silent vga=788 initrd (hd0,0)/boot/initrd.img title linux-nonfb kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=77a15e0a-b9f5-46ab-8236-886418dbbfd8 resume=/dev/sdb5 initrd (hd0,0)/boot/initrd.img title failsafe kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=77a15e0a-b9f5-46ab-8236-886418dbbfd8 failsafe initrd (hd0,0)/boot/initrd.img Note that it has used hd0 even though the disk is /dev/sdb (which implies the second disk). The problem is that when it boots the Adaptec SCSI BIOS searches for bootable drives from the highest SCSI ID downwards. Since the 73GB (FreeBSD) disk is id 15 it boots from that. That disk also has GRUB installed with an entry for FreeBSD which is also hd0. The FreeBSD entry works. Because the disks are seen by the SCSI BIOS as id 15 first, id 14 second, id 14 - the disk with Mandriva installed, is hd1 so I copied the Mandriva menu.lst file into the one on the FreeBSD partition and edited hd0 to hd1 (for both the lernel and initrd lines) but Mandriva won't boot, I get Error 2: Bad File or Directory type In fact, the FreeBSD GRUB seems unable to read the Linux disk - it knows it's there, but can't access anything on it. I've tried numerous things as suggested on the Mandriva forums but nothing works: grub root (hd0,0,a) Filesystem type is ufs2, partition type is 0xa5 grub cat /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/da0 (hd1) /dev/da1 grub root (hd1,0) Filesystem type is ext2, partition type is 0x83 grub cat /boot/grub/device.map Error 2: Bad file or directory type grub root (hd TAB Possible disks are: hd0 hd1 grub root (hd1, TAB Possible partitions are: Partition num: 0, Filesystem type is ext2fs, partition type 0x83 Partition num: 4, Filesystem type is unknown, partition type 0x82 Partition num: 5, Filesystem type is ext2fs, partition type 0x83 grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type is ufs2, partition type 0xa5 BSD Partition num: 'b', Filesystem type is unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type is ufs2, partition type 0xa5 BSD Partition num: 'e', Filesystem type is ufs2, partition type 0xa5 BSD Partition num: 'f', Filesystem type is ufs2, partition type 0xa5 Can anyone suggest how to make this work? The root of the problem is that both OSes think their disk is hd0. Regards, Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB / boot easy problems w / USB stick
Some thoughts: 1. bsdlabel -Brw /dev/da0s1 - What is the option r? - bsdlabel is supposed to create standard label which probably means creating da0s1a partition (can you call bsdlabel /dev/da0s1 to see what was created?) So your next command should be newfs /dev/da0s1a rather than newfs /dev/da0s1. And commands after that will need to be adjusted as well. 2. boot0cfg -B -s 1 -t -v 182 /dev/da0 It should be -v -t 182 rather than -t -v 182. Not sure if it matters though. Hope this helps. Andrey Thanks Andrey, great news! placing newfs on /dev/da0s1a instead of /dev/da0s1 really helped. Now GRUB recognizes the filesystem on my usb partition. Here's what's new. #I placed 1 UFS2 partition on my USB key at #/dev/da0s1a. mount /dev/da0s1a /usb mkdir -p /usb/boot/grub #copied all files from /boot to /usb/boot and all files #from /boot/grub to /usb/boot/grub (I know I can make #it smaller but just copying all for now). Next I #invoked the grub shell and did the following: grub root (hd1,0,a) Filesystem type is ufs2, partition type is 0xa5. grub setup (hd1) Checking if /boot/grub/stage1 exists... yes Checking if /boot/grub/stage2 exists... yes Checking if /boot/grub/ufs2_stage1_5 exists... yes Running embed /boot/grub/ufs2_stage1_5 (hd1)... 16 sectors are embedded. Succeeded Running install /boot/grub/stage1 (hd1) (hd1)1+16 p (hd1,0,a)/boot/grub/stage2 /boot/grub/menu.lst... Succeeded Done. #I reboot, and am excited to see the grub menu I've set #up. Here is my menu.lst: default=0 timeout=30 title NewOS root (hd0,0,a) kernel /boot/loader #You might notice I made root hd0. This is actually #helpful for anyone setting GRUB up for the first time. #You see when setting up grub from the shell within #your computer, your first hard drive is always hd0, #and your usb stick can be anything after that (in my #case hd1). You can test this by placing an oddly #named text file in each of your grub directories (1 in #hard drive, 1 in usb stick), then using find from the #grub shell to indicate where that oddly named file is #located: grub find /boot/grub/weirdfile (hd0,0,a) #The main point is that when you reboot to your USB #key, because it's now the first drive, it's probably #going to be hd0, instead of hdx, thus my menu.lst. # Anyway, back to the menu selection. When I choose the 'NewOS', this is what I get: Booting 'NewOS' root (hd0,0,a) Filesystem type is ufs2, partition type is 0xa5 kernel /boot/loader [FreeBSD-a.out, loadaddr=0x20, text=0x1000, data=0x32000, bss=0x0, entry=0x20] BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 631kB/980480kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (root @barney.msu.edu, Sun May 8 03:20:03 UTC 2006) #This is the last line, and if I wait about five #minutes it prints these additional lines: can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK _ #Again I'm pretty sure I must have the right 'hd' #addressing. I tested this by changing the root #location to (hd1,0,a) which found the boot loader off #of my hard drive and booted. I tested this by moving #the loader from my hard drive out of /boot, and #rebooting, where upon it couldn't find loader anymore. Alright I'll leave it there. (Starving for that little morsel of knowledge out there that will unlock this!) -Fred (p.s. I'm new to the mailing lists, and can't find the charter for any of the groups, anyone have a link? :) Need Mail bonding? Go to the Yahoo! Mail QA for great tips from Yahoo! Answers users. http://answers.yahoo.com/dir/?link=listsid=396546091 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB / boot easy problems w / USB stick
It seems like this thread isn't getting updated when I post for some reason. This will be the last one I try until I figure out what's wrong. #I've done some more tests. In my last post I had booted # from the usb key. the results of lsdev from the boot #loader prompt were: OK lsdev cd devices: disk devices: disk0: BIOS drive C: disk1: BIOS drive D: disk1s1a: FFS disk1s1b: swap disk1s1d: FFS # If I booted from the hard drive first I got: cd devices: disk devices: disk0: BIOS Drive C: disk0s1a: FFS disk0s1b: swap disk1s1d: FFS disk1L BIOS Drive D: #So it's clear that which ever drive is booted from #first between the hard drive and the usb key drive is #going to show up as disk0: BIOS Drive C, but I was #wondering why the disk slices/partition letters for #the USB key don't #show up when I boot from it. Or #even when I boot from the HD and use the loader #prompt? # Again just to quickly restate the problem, when # booting from the USB key, the BTX loader hangs, and # after about 5 minutes I get the loader prompt. The # loader apparently can't find the kernel. When #booting normally I have double checked that the #bsdlabels, filesystems, and required files are at #least present on the key. # I'll keep learning the intimate details of various #config files, and loader commands, and post back if I #find a solution. Thanks again for any bits of know #how you send my way. -Fred Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
GRUB / boot easy problems w / USB stick
--- Andrey Shuvikov [EMAIL PROTECTED] wrote: Did you copy it recursively (with sub-directories)? If yes then you didn't need to copy /boot/grub separately. If no, you'll probably need to copy at least /boot/defaults . And /boot/kernel as well if you really want to boot... Andrey # In /boot I did cp -Rpv * /usb/boot #I'm not sure why it can get as far as the BTX loader #info, but can't manage to load the kernel. It clearly #can read the ufs2 now. I don't really know much about #the specifics of the startup process, but I thought #as soon as the loader was invoked, the first thing it #tries to do is load the kernel into memory. I just #double checked and the kernel is located on the stick #at USB/boot/kernel/kernel. This must have happened to #someone else before. -Fred p.s. just a shot in the dark, but does anyone think grub might not be able to load the kernel because it runs out of some kind of internal allotment of memory? Looking for earth-friendly autos? Browse Top Cars by Green Rating at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
GRUB / boot easy problems w / USB stick
Some thoughts: 1. bsdlabel -Brw /dev/da0s1 - What is the option r? - bsdlabel is supposed to create standard label which probably means creating da0s1a partition (can you call bsdlabel /dev/da0s1 to see what was created?) So your next command should be newfs /dev/da0s1a rather than newfs /dev/da0s1. And commands after that will need to be adjusted as well. 2. boot0cfg -B -s 1 -t -v 182 /dev/da0 It should be -v -t 182 rather than -t -v 182. Not sure if it matters though. Hope this helps. Andrey Thanks Andrey, great news! placing newfs on /dev/da0s1a instead of /dev/da0s1 really helped. Now GRUB recognizes the filesystem on my usb partition. Here's what's new. #I placed 1 UFS2 partition on my USB key at #/dev/da0s1a. mount /dev/da0s1a /usb mkdir -p /usb/boot/grub #copied all files from /boot to /usb/boot and all files #from /boot/grub to /usb/boot/grub (I know I can make #it smaller but just copying all for now). Next I #invoked the grub shell and did the following: grub root (hd1,0,a) Filesystem type is ufs2, partition type is 0xa5. grub setup (hd1) Checking if /boot/grub/stage1 exists... yes Checking if /boot/grub/stage2 exists... yes Checking if /boot/grub/ufs2_stage1_5 exists... yes Running embed /boot/grub/ufs2_stage1_5 (hd1)... 16 sectors are embedded. Succeeded Running install /boot/grub/stage1 (hd1) (hd1)1+16 p (hd1,0,a)/boot/grub/stage2 /boot/grub/menu.lst... Succeeded Done. #I reboot, and am excited to see the grub menu I've set #up. Here is my menu.lst: default=0 timeout=30 title NewOS root (hd0,0,a) kernel /boot/loader #You might notice I made root hd0. This is actually #helpful for anyone setting GRUB up for the first time. #You see when setting up grub from the shell within #your computer, your first hard drive is always hd0, #and your usb stick can be anything after that (in my #case hd1). You can test this by placing an oddly #named text file in each of your grub directories (1 in #hard drive, 1 in usb stick), then using find from the #grub shell to indicate where that oddly named file is #located: grub find /boot/grub/weirdfile (hd0,0,a) #The main point is that when you reboot to your USB #key, because it's now the first drive, it's probably #going to be hd0, instead of hdx, thus my menu.lst. # Anyway, back to the menu selection. When I choose the 'NewOS', this is what I get: Booting 'NewOS' root (hd0,0,a) Filesystem type is ufs2, partition type is 0xa5 kernel /boot/loader [FreeBSD-a.out, loadaddr=0x20, text=0x1000, data=0x32000, bss=0x0, entry=0x20] BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 631kB/980480kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (root @barney.msu.edu, Sun May 8 03:20:03 UTC 2006) #This is the last line, and if I wait about five #minutes it prints these additional lines: can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK _ #Again I'm pretty sure I must have the right 'hd' #addressing. I tested this by changing the root #location to (hd1,0,a) which found the boot loader off #of my hard drive and booted. I tested this by moving #the loader from my hard drive out of /boot, and #rebooting, where upon it couldn't find loader anymore. Alright I'll leave it there. (Starving for that little morsel of knowledge out there that will unlock this!) -Fred (p.s. I'm new to the mailing lists, and can't find the charter for any of the groups, anyone have a link? :) Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
GRUB / boot easy problems w / USB stick
I am looking for some help to enable booting from a USB stick. After weeks of reading, and attempting I am at a total loss. This all began while I was trying to follow the many excellent tutorials on encrypting whole laptop disks with GELI[1]. These tutorials were great except they didn't really cover how to make the sticks bootable. Here is some of the many things I have tried. Background: My laptop BIOS allows me to pick the boot order from 7 devices, I set them as follows: (1) USB Key (2) USB HDD (3) USB CDROM (4) USB FDC (5) IDE CD (6) IDE HDD (7) PCI BEV Attempt 1: FreeBSD Boot Manager # created a dedicated slice on my 512MB stick with a #UFS2 filesystem. (after fdisk) bsdlabel -Brw /dev/da0s1 newfs /dev/da0s1 # Copied over boot files to usb filesystem. mount /dev/da0s1 /usb mkdir /usb/boot cd /boot cp -Rpv * /usb/boot # Placed FreeBSD boot manager on MBR of USB stick. boot0cfg -B -s 1 -t -v 182 /dev/da0 Problem: When I reboot the laptop keyboard won't allow me to select a partition with the F keys. Attempt 2: GRUB # make install grub from the ports collection. copy #over the files from #/usr/local/share/grub/i386-freebsd/* to /boot/grub. #My understanding was that Grub can read write UFS2 #because of patches since version 0.94. So on my first #attempt I made a single UFS2 partition. mount /dev/da0s1 /usb mkdir -p /usb/boot/grub cd /boot cp -Rpv * /usb/boot cd /boot/grub cp -Rpv * /usb/boot/grub #I invoke the grub shell. There are two devices in my #device map: (hd0) /dev/ad0 (hd1) /dev/da0 # Now if I try to set root in the following ways I'll #get the following: grub root (hd0,0,a) Filesystem type is ufs2, partition type 0xa5 grub root (hd1,0) Filesystem type is unknown, partition type 0xa5 # now before you say it, I also tried (hd1,0,a) but #this is even worse in some situations. Basically I #can't get grub to read or write to the USB stick with #a UFS2 filesystem. Yet it will read write to the #UFS2 filesystem of the native disk. Does anyone know #why? I have tried grub-install which apparently is #successful, but once I attempt to reboot, it hangs #with the word, GRUB printed. Attempt 3: Chainloading GRUB #This time I though I had it. I created S1 FAT #partition and S2 UFS2 partition on the stick. I # was able to use setup from the grub shell to setup #the FAT slice as the location for stage2. On the #ufs2 partition I set up the proper /boot setup above. #I read on an old post and someone mentioned that #boot2 does something stupid, and won't work with a #chainload scenario. I tried it anyways, and it didn't #work. I had heard that it might work if you bounce #boot0 to the beginning of the slice instead of the #disk MBR so I did. boot0cfg -B -s 2 -t 182 -v /dev/da0s2 #seemed to go well. I rebooted, and got as far as #the F key menu, but again nothing worked, and I #couldn't boot. Just to add, I also tried the whole booting FreeBSD from a FAT partition but that just plain doesn't work [2]. Well that's where I am. I can't tell you how much you will rock my world if you can show me how to fix this. These are some ideas I have, but don't know enough to do anything about: (1) BIOS issues; from what I understand each computer manufacturer takes a base bios (phoenix in my case) and proprietories it up. I'm dreading that maybe my BIOS will prevent any of this from working. Doesn't seem to be documentation anywhere on my manufac's site. (2) Bootblocks; Maybe there's some easy modifications or config files for boot blocks I don't know about? Maybe there are some alternatives? (3) GRUB patches; I've been downloading ports from another PC (no network yet)burning to CD, then making. done it twice now. Is there some wonderful patch to GRUB that makes it work with FreeBSD I don't know about? Do any of you have it working? if so , can I copy how you built exactly? Alright, that's all. I'm sorry for the length of this post, it's my first one, and I have seriously dredged pretty hard on my own for a solution. Thanks again. Fred [1] http://www.proportion.ch/index.php?page=31 http://www.daimi.au.dk/~u063592/ http://www.bsdforums.org/forums/showthread.php?threadid=43796 [2] http://docs.FreeBSD.org/cgi/mid.cgi?2002003159.A46044 Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more. http://mobile.yahoo.com/go?refer=1GNXIC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
GRUB / boot easy problems w / USB stick
I am looking for some help to enable booting from a USB stick. After weeks of reading, and attempting I am at a total loss. This all began while I was trying to follow the many excellent tutorials on encrypting whole laptop disks with GELI[1]. These tutorials were great except they didn't really cover how to make the sticks bootable. Here is some of the many things I have tried. Background: My laptop BIOS allows me to pick the boot order from 7 devices, I set them as follows: (1) USB Key (2) USB HDD (3) USB CDROM (4) USB FDC (5) IDE CD (6) IDE HDD (7) PCI BEV Attempt 1: FreeBSD Boot Manager # created a dedicated slice on my 512MB stick with a #UFS2 filesystem. (after fdisk) bsdlabel -Brw /dev/da0s1 newfs /dev/da0s1 # Copied over boot files to usb filesystem. mount /dev/da0s1 /usb mkdir /usb/boot cd /boot cp -Rpv * /usb/boot # Placed FreeBSD boot manager on MBR of USB stick. boot0cfg -B -s 1 -t -v 182 /dev/da0 Problem: When I reboot the laptop keyboard won't allow me to select a partition with the F keys. Attempt 2: GRUB # make install grub from the ports collection. copy #over the files from #/usr/local/share/grub/i386-freebsd/* to /boot/grub. #My understanding was that Grub can read write UFS2 #because of patches since version 0.94. So on my first #attempt I made a single UFS2 partition. mount /dev/da0s1 /usb mkdir -p /usb/boot/grub cd /boot cp -Rpv * /usb/boot cd /boot/grub cp -Rpv * /usb/boot/grub #I invoke the grub shell. There are two devices in my #device map: (hd0) /dev/ad0 (hd1) /dev/da0 # Now if I try to set root in the following ways I'll #get the following: grub root (hd0,0,a) Filesystem type is ufs2, partition type 0xa5 grub root (hd1,0) Filesystem type is unknown, partition type 0xa5 # now before you say it, I also tried (hd1,0,a) but #this is even worse in some situations. Basically I #can't get grub to read or write to the USB stick with #a UFS2 filesystem. Yet it will read write to the #UFS2 filesystem of the native disk. Does anyone know #why? I have tried grub-install which apparently is #successful, but once I attempt to reboot, it hangs #with the word, GRUB printed. Attempt 3: Chainloading GRUB #This time I though I had it. I created S1 FAT #partition and S2 UFS2 partition on the stick. I # was able to use setup from the grub shell to setup #the FAT slice as the location for stage2. On the #ufs2 partition I set up the proper /boot setup above. #I read on an old post and someone mentioned that #boot2 does something stupid, and won't work with a #chainload scenario. I tried it anyways, and it didn't #work. I had heard that it might work if you bounce #boot0 to the beginning of the slice instead of the #disk MBR so I did. boot0cfg -B -s 2 -t 182 -v /dev/da0s2 #seemed to go well. I rebooted, and got as far as #the F key menu, but again nothing worked, and I #couldn't boot. Just to add, I also tried the whole booting FreeBSD from a FAT partition but that just plain doesn't work [2]. Well that's where I am. I can't tell you how much you will rock my world if you can show me how to fix this. These are some ideas I have, but don't know enough to do anything about: (1) BIOS issues; from what I understand each computer manufacturer takes a base bios (phoenix in my case) and proprietories it up. I'm dreading that maybe my BIOS will prevent any of this from working. Doesn't seem to be documentation anywhere on my manufac's site. (2) Bootblocks; Maybe there's some easy modifications or config files for boot blocks I don't know about? Maybe there are some alternatives? (3) GRUB patches; I've been downloading ports from another PC (no network yet)burning to CD, then making. done it twice now. Is there some wonderful patch to GRUB that makes it work with FreeBSD I don't know about? Do any of you have it working? if so , can I copy how you built exactly? Alright, that's all. I'm sorry for the length of this post, it's my first one, and I have seriously dredged pretty hard on my own for a solution. Thanks again. Fred [1] http://www.proportion.ch/index.php?page=31 http://www.daimi.au.dk/~u063592/ http://www.bsdforums.org/forums/showthread.php?threadid=43796 [2] http://docs.FreeBSD.org/cgi/mid.cgi?2002003159.A46044 Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB / boot easy problems w / USB stick
On 6/2/07, Fred Davidson [EMAIL PROTECTED] wrote: I am looking for some help to enable booting from a USB stick. After weeks of reading, and attempting I am at a total loss. This all began while I was trying to follow the many excellent tutorials on encrypting whole laptop disks with GELI[1]. These tutorials were great except they didn't really cover how to make the sticks bootable. Here is some of the many things I have tried. Background: My laptop BIOS allows me to pick the boot order from 7 devices, I set them as follows: (1) USB Key (2) USB HDD (3) USB CDROM (4) USB FDC (5) IDE CD (6) IDE HDD (7) PCI BEV Attempt 1: FreeBSD Boot Manager # created a dedicated slice on my 512MB stick with a #UFS2 filesystem. (after fdisk) bsdlabel -Brw /dev/da0s1 newfs /dev/da0s1 # Copied over boot files to usb filesystem. mount /dev/da0s1 /usb mkdir /usb/boot cd /boot cp -Rpv * /usb/boot # Placed FreeBSD boot manager on MBR of USB stick. boot0cfg -B -s 1 -t -v 182 /dev/da0 Problem: When I reboot the laptop keyboard won't allow me to select a partition with the F keys. Attempt 2: GRUB # make install grub from the ports collection. copy #over the files from #/usr/local/share/grub/i386-freebsd/* to /boot/grub. #My understanding was that Grub can read write UFS2 #because of patches since version 0.94. So on my first #attempt I made a single UFS2 partition. mount /dev/da0s1 /usb mkdir -p /usb/boot/grub cd /boot cp -Rpv * /usb/boot cd /boot/grub cp -Rpv * /usb/boot/grub #I invoke the grub shell. There are two devices in my #device map: (hd0) /dev/ad0 (hd1) /dev/da0 # Now if I try to set root in the following ways I'll #get the following: grub root (hd0,0,a) Filesystem type is ufs2, partition type 0xa5 grub root (hd1,0) Filesystem type is unknown, partition type 0xa5 # now before you say it, I also tried (hd1,0,a) but #this is even worse in some situations. Basically I #can't get grub to read or write to the USB stick with #a UFS2 filesystem. Yet it will read write to the #UFS2 filesystem of the native disk. Does anyone know #why? I have tried grub-install which apparently is #successful, but once I attempt to reboot, it hangs #with the word, GRUB printed. Attempt 3: Chainloading GRUB #This time I though I had it. I created S1 FAT #partition and S2 UFS2 partition on the stick. I # was able to use setup from the grub shell to setup #the FAT slice as the location for stage2. On the #ufs2 partition I set up the proper /boot setup above. #I read on an old post and someone mentioned that #boot2 does something stupid, and won't work with a #chainload scenario. I tried it anyways, and it didn't #work. I had heard that it might work if you bounce #boot0 to the beginning of the slice instead of the #disk MBR so I did. boot0cfg -B -s 2 -t 182 -v /dev/da0s2 #seemed to go well. I rebooted, and got as far as #the F key menu, but again nothing worked, and I #couldn't boot. Just to add, I also tried the whole booting FreeBSD from a FAT partition but that just plain doesn't work [2]. Well that's where I am. I can't tell you how much you will rock my world if you can show me how to fix this. These are some ideas I have, but don't know enough to do anything about: (1) BIOS issues; from what I understand each computer manufacturer takes a base bios (phoenix in my case) and proprietories it up. I'm dreading that maybe my BIOS will prevent any of this from working. Doesn't seem to be documentation anywhere on my manufac's site. (2) Bootblocks; Maybe there's some easy modifications or config files for boot blocks I don't know about? Maybe there are some alternatives? (3) GRUB patches; I've been downloading ports from another PC (no network yet)burning to CD, then making. done it twice now. Is there some wonderful patch to GRUB that makes it work with FreeBSD I don't know about? Do any of you have it working? if so , can I copy how you built exactly? Alright, that's all. I'm sorry for the length of this post, it's my first one, and I have seriously dredged pretty hard on my own for a solution. Thanks again. Fred [1] http://www.proportion.ch/index.php?page=31 http://www.daimi.au.dk/~u063592/ http://www.bsdforums.org/forums/showthread.php?threadid=43796 [2] http://docs.FreeBSD.org/cgi/mid.cgi?2002003159.A46044 Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more. http://mobile.yahoo.com/go?refer=1GNXIC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Some thoughts: 1. bsdlabel -Brw /dev/da0s1 - What is the option r? - bsdlabel is supposed to create standard label which probably means creating da0s1a partition (can you call
grub
Hi, I had freebsd installed on my 1st hardrive withour difficuties. I then installed Debian Linux on my 2nd hard drive and the grub bootloader overwrote my mbr and now I can only boot debian. How can I get my freebsd back ? Thanks Rick Rick Knebel [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub
In the last episode (May 29), Richard Knebel said: I had freebsd installed on my 1st hardrive withour difficuties. I then installed Debian Linux on my 2nd hard drive and the grub bootloader overwrote my mbr and now I can only boot debian. How can I get my freebsd back ? Assuming grub is functional, you might want to just keep it and add another entry like this: title FreeBSD root (hd1,1,a) kernel /boot/loader savedefault replacing (hd1,1,a) with whatever find /boot/loader at the grub CLI returns. If your grub doesn't have UFS support, then the find and kernel commands won't work, and you'll have to chainload to the FreeBSD slice's bootblock instead of using the kernel command. If you really want booteasy back, boot into FreeBSD and run boot0cfg -B /dev/ad0 (or whatever your 1st hardrive's device is) -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub
On 5/30/07, Dan Nelson [EMAIL PROTECTED] wrote: In the last episode (May 29), Richard Knebel said: I had freebsd installed on my 1st hardrive withour difficuties. I then installed Debian Linux on my 2nd hard drive and the grub bootloader overwrote my mbr and now I can only boot debian. How can I get my freebsd back ? Assuming grub is functional, you might want to just keep it and add another entry like this: title FreeBSD root (hd1,1,a) kernel /boot/loader savedefault replacing (hd1,1,a) with whatever find /boot/loader at the grub CLI returns. If your grub doesn't have UFS support, then the find and kernel commands won't work, and you'll have to chainload to the FreeBSD slice's bootblock instead of using the kernel command. If you really want booteasy back, boot into FreeBSD and run boot0cfg -B /dev/ad0 (or whatever your 1st hardrive's device is) -- Dan Nelson [EMAIL PROTECTED] Boot into your linux box, edit /boot/grub/menu.lst And add the following lines: title FreeBSD root (hd0,1)# this changes based on where on the partition/drive the FreeBSD is installed. chainloader +1 savedefault run, # grub-install /dev/hda # sda if sata disk reboot. this should help to solve your problem ___ 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 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, 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?
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?
-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?
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?
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?
-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?
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?
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?
-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]
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]
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]
Boot Live CDROM with Grub
Hello, I can make a bootable CD using GRUB + El Torito no-emulation mode. It's almost completely explained in the GRUB manual, section 3.4. I want to do more, I want to offer the user who boots from the CD Live or from a hard disk partition, it's a CD Live with XORP. So I built the following menu.lst file: default=0 timeout=10 title FreeBSD 6.1 root (hd0,0,a) kernel /boot/loader title CD Live XORP 1.3 root (hd1) kernel /boot/loader From GRUB manual, the device syntax is like this: `(DEVICE[,PART-NUM][,BSD-SUBPART-LETTER])' `[]' means the parameter is optional. DEVICE should be either `fd' or `hd' followed by a digit, like `fd0'. Can I set CDROM device? I have added last line in device.map $ cat /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/ad0 (hd1) /dev/acd0 Using this file I can boot FreeBSD 6.1, but not CD Live XORP 1.3. However when I try set CDROM on grub: grub root (hd1) Error 21: Selected disk does not exist So the question is: how can I create a GRUB configuration to boot CD Live XORP 1.3.? Thanks in advance, David __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restoring FreeBSD grub loader
Hello, Thank you for your response. On 10/1/06, backyard [EMAIL PROTECTED] wrote: --- Ivan \Rambius\ Ivanov [EMAIL PROTECTED] wrote: Hello, I installed FreeBSD 6.1 on one machine with grub boot loader. In the beginning there was only one entry in grub - namely FreeBSD. Later, I had to install Windows XP on the machine and of course, it destroyed grub and now I cannot boot FreeBSD. I tried with booting from the FreeBSD installation disk choosing Fixit option, but I could not use successfully grub-install command. My question is: how can I restore the FreeBSD grub loader? Could you please give me any hints or advance. Thank you very much in advance. Regards Ivan -- I would suggest you make a grub booting floppy disk then you can escape to command mode once the disk loades and install grub with root (hd0,0,a) # or wherever it is setup (hd0 # again wherever it is assuming you have already placed the grub bootfiles on your hard drive and configured menu.lst you should be all set. I have only encountered one computer this method failed. In fact, I am using a laptop that does not have a floppy drive, so I could not use booting floppy disks. you could alternatively flip the kernel tunable that allows raw writes to the boot sectors of the disks. I don't recall what it is but I think the grub docs talk about it in the man or info pages. I'm supprised XP messed it up, 2000 seemed to respect existing bootloaders... I fixed the problem in the following way: I have another FreeBSD laptop, so I copied its boot sector using the command # dd if=/dev/ad0s1a of=/mnt/bootsect.bsd bs=512 count=1 Then I used bootsect.bsd to to boot in FreeBSD via the NT loader (I found this link useful: http://www.unixguide.net/freebsd/faq/09.10.shtml). After I boot to FreeBSD I installed the grub loader. Regards Ivan -- Tangra Mega Rock: http://www.radiotangra.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restoring FreeBSD grub loader
--- Ivan \Rambius\ Ivanov [EMAIL PROTECTED] wrote: Hello, Thank you for your response. On 10/1/06, backyard [EMAIL PROTECTED] wrote: --- Ivan \Rambius\ Ivanov [EMAIL PROTECTED] wrote: Hello, I installed FreeBSD 6.1 on one machine with grub boot loader. In the beginning there was only one entry in grub - namely FreeBSD. Later, I had to install Windows XP on the machine and of course, it destroyed grub and now I cannot boot FreeBSD. I tried with booting from the FreeBSD installation disk choosing Fixit option, but I could not use successfully grub-install command. My question is: how can I restore the FreeBSD grub loader? Could you please give me any hints or advance. Thank you very much in advance. Regards Ivan -- I would suggest you make a grub booting floppy disk then you can escape to command mode once the disk loades and install grub with root (hd0,0,a) # or wherever it is setup (hd0 # again wherever it is assuming you have already placed the grub bootfiles on your hard drive and configured menu.lst you should be all set. I have only encountered one computer this method failed. In fact, I am using a laptop that does not have a floppy drive, so I could not use booting floppy disks. I use a USB floppy drive to boot my laptop and install grub. Although I haven't been able to use fdformat with the floppy drive so I use one of my desktops to prapare the disks. you could alternatively flip the kernel tunable that allows raw writes to the boot sectors of the disks. I don't recall what it is but I think the grub docs talk about it in the man or info pages. I'm supprised XP messed it up, 2000 seemed to respect existing bootloaders... I fixed the problem in the following way: I have another FreeBSD laptop, so I copied its boot sector using the command # dd if=/dev/ad0s1a of=/mnt/bootsect.bsd bs=512 count=1 I've used that method myself when grub hadn't been updated to support UFS2. I had completely forgotten about it though. Then I used bootsect.bsd to to boot in FreeBSD via the NT loader (I found this link useful: http://www.unixguide.net/freebsd/faq/09.10.shtml). After I boot to FreeBSD I installed the grub loader. to each their own; the beauty of Unix... glad you got it working. Regards Ivan -- -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Restoring FreeBSD grub loader
Hello, I installed FreeBSD 6.1 on one machine with grub boot loader. In the beginning there was only one entry in grub - namely FreeBSD. Later, I had to install Windows XP on the machine and of course, it destroyed grub and now I cannot boot FreeBSD. I tried with booting from the FreeBSD installation disk choosing Fixit option, but I could not use successfully grub-install command. My question is: how can I restore the FreeBSD grub loader? Could you please give me any hints or advance. Thank you very much in advance. Regards Ivan -- Tangra Mega Rock: http://www.radiotangra.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Restoring FreeBSD grub loader
--- Ivan \Rambius\ Ivanov [EMAIL PROTECTED] wrote: Hello, I installed FreeBSD 6.1 on one machine with grub boot loader. In the beginning there was only one entry in grub - namely FreeBSD. Later, I had to install Windows XP on the machine and of course, it destroyed grub and now I cannot boot FreeBSD. I tried with booting from the FreeBSD installation disk choosing Fixit option, but I could not use successfully grub-install command. My question is: how can I restore the FreeBSD grub loader? Could you please give me any hints or advance. Thank you very much in advance. Regards Ivan -- I would suggest you make a grub booting floppy disk then you can escape to command mode once the disk loades and install grub with root (hd0,0,a) # or wherever it is setup (hd0 # again wherever it is assuming you have already placed the grub bootfiles on your hard drive and configured menu.lst you should be all set. I have only encountered one computer this method failed. you could alternatively flip the kernel tunable that allows raw writes to the boot sectors of the disks. I don't recall what it is but I think the grub docs talk about it in the man or info pages. I'm supprised XP messed it up, 2000 seemed to respect existing bootloaders... -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB Problems with Dell Optiplex GX1
On Aug 21, 2006, at 6:41 PM, backyard wrote: --- Garrett Cooper [EMAIL PROTECTED] wrote: backyard wrote: I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian FreeBSD folks tend not to use Grub, but some of us do use it as opposed to FreeBSD's bootmanager. Please post the steps you use to install grub and the output those steps give you, and your grub.conf. -Garrett #menu.lst default 0 timeout 7 fallback 1 #password --md5 some kind of password that is encypted splashimage (fd0)/boot/grub/opt/smurffed.xpm.gz title BSD root (hd0,0,a) kernel /boot/loader title Hold the Phone halt title Reset me reboot title Floppy Boot lock root (fd0) chainloader #EOF menu.lst here is my menu.lst off my grub install floppy. this was created by building grub 0.97 from ports on my HP Kayak. the floppy was then prepared as below: fdformat /dev/fd0 newfs -O1 -n /dev/fd0 mount /dev/fd0 /mnt mkdir -p /mnt/boot/grub/opt I then copied the grub files from the /usr/local/share/grub/i386-freebsd if memory serves me correct to the /mnt/boot/grub folder. then copied in my splashimages, then prepared menu.lst as described. I then ran grub and setup the floppy to boot grub. now to install on a system I: mkdir -p /boot/grub/opt mount /dev/fd0 /mnt; cp -R /mnt/boot/grub /boot/grub change menu.lst as required to reference hardrives or different boot options like a windows partition or linux or whatever needs to be started up. boot the system with the floppy and go to grub console. make sure I can find /boot/grub/menu.lst then... root (hd0,0,a) # or whatever setup (hd0) # again depends and usually I take the floppy out, reboot, and grub asks me what I want to boot up. as far as the exact output from grub I don't know, but it didn't give any errors. it just said: checking for /boot/grub/menu.lst found installing stage1 success installing stage1_5 success installing stage2. success the typical everything is ok message. I have heard in later reading that a missing splashimage can mess things up, I will have to make sure I remembered to change the root for the image to the harddrive. But I have also read that this just happens sometimes with grub and certain machines. this is the only time I've seen it happen. I personally love me some grub. it just makes things easier in my world; at least usually. -brian Ok, it seems like your installation process at least is ok; perhaps the location of the installed grub is incorrect though. Could you do the following? 1. Run fdisk and verify that the partition you actually have your root installed on is the first one. 2. Replace all references to just / (root) in all partition names to the proper device name, plus root, e.g.: root (hd0,0,a) kernel (hd0,0,a)/boot/loader I know it seems a bit redundant, but it's saved me from some issues with installing grub on my linux box. 3. Remove the splashedimage reference. It's referring to your floppy and if the floppy isn't there I could see some possible issues occurring with booting grub, as you mentioned earlier in the email. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB Problems with Dell Optiplex GX1
--- Garrett Cooper [EMAIL PROTECTED] wrote: On Aug 21, 2006, at 6:41 PM, backyard wrote: --- Garrett Cooper [EMAIL PROTECTED] wrote: backyard wrote: I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian FreeBSD folks tend not to use Grub, but some of us do use it as opposed to FreeBSD's bootmanager. Please post the steps you use to install grub and the output those steps give you, and your grub.conf. -Garrett #menu.lst default 0 timeout 7 fallback 1 #password --md5 some kind of password that is encypted splashimage (fd0)/boot/grub/opt/smurffed.xpm.gz title BSD root (hd0,0,a) kernel /boot/loader title Hold the Phone halt title Reset me reboot title Floppy Boot lock root (fd0) chainloader #EOF menu.lst here is my menu.lst off my grub install floppy. this was created by building grub 0.97 from ports on my HP Kayak. the floppy was then prepared as below: fdformat /dev/fd0 newfs -O1 -n /dev/fd0 mount /dev/fd0 /mnt mkdir -p /mnt/boot/grub/opt I then copied the grub files from the /usr/local/share/grub/i386-freebsd if memory serves me correct to the /mnt/boot/grub folder. then copied in my splashimages, then prepared menu.lst as described. I then ran grub and setup the floppy to boot grub. now to install on a system I: mkdir -p /boot/grub/opt mount /dev/fd0 /mnt; cp -R /mnt/boot/grub /boot/grub change menu.lst as required to reference hardrives or different boot options like a windows partition or linux or whatever needs to be started up. boot the system with the floppy and go to grub console. make sure I can find /boot/grub/menu.lst then... root (hd0,0,a) # or whatever setup (hd0) # again depends and usually I take the floppy out, reboot, and grub asks me what I want to boot up. as far as the exact output from grub I don't know, but it didn't give any errors. it just said: checking for /boot/grub/menu.lst found installing stage1 success installing stage1_5 success installing stage2. success the typical everything is ok message. I have heard in later reading that a missing splashimage can mess things up, I will have to make sure I remembered to change the root for the image to the harddrive. But I have also read that this just happens sometimes with grub and certain machines. this is the only time I've seen it happen. I personally love me some grub. it just makes things easier in my world; at least usually. -brian Ok, it seems like your installation process at least is ok; perhaps the location of the installed grub is incorrect though. Could you do the following? 1.Run fdisk and verify that the partition you actually have your root installed on is the first one. 2.Replace all references to just / (root) in all partition names to the proper device name, plus root, e.g.: root (hd0,0,a) kernel (hd0,0,a)/boot/loader I know it seems a bit redundant, but it's saved me from some issues with installing grub on my linux box. 3.Remove the splashedimage reference. It's referring to your floppy and if the floppy isn't there I could see some possible issues occurring with booting grub, as you mentioned earlier in the email. -Garrett I'll give this a whirl and report back as to what happens, but I think I just have one of the machines that grub just doesn't like very much. Its just a good thing it happened to be the one machine I have that will never see anything but BSD on it. Like I said GRUB was just to put an inappropriate splash screen up to tick off my friends should they ever turn the thing on with a monitor plugged into it... That being said it's still annoying when things don't work out the way you want. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
GRUB Problems with Dell Optiplex GX1
I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB Problems with Dell Optiplex GX1
backyard wrote: I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian FreeBSD folks tend not to use Grub, but some of us do use it as opposed to FreeBSD's bootmanager. Please post the steps you use to install grub and the output those steps give you, and your grub.conf. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB Problems with Dell Optiplex GX1
--- Garrett Cooper [EMAIL PROTECTED] wrote: backyard wrote: I'm having problems installing GRUB on my Dell Optiplex GX1 pentium3 500 BIOS A10. I'm setting this server up for a friend and not having GRUB isn't the biggest deal; I just wanted to have a nice inappropriate boot image when they turn it on... It will boot from a floppy, but installing it to the hard drive seems to corrupt the root filesystem. It claims to install fine and during boot will load grub_stage1.5 from the disk, but instead of loading stage2 it begins to boot the system, but the console font has become completely corrupted, and I'm not certain if anything else has. It will boot, and appears to function but the font is messed up. Has anyone else had issues with the particular Dell and GRUB? I've never had problems with GRUB before this machine. I'm at a loss, any help would be appreciated. It would be nice to get GRUB on this thing, but if I can't oh well. -brian FreeBSD folks tend not to use Grub, but some of us do use it as opposed to FreeBSD's bootmanager. Please post the steps you use to install grub and the output those steps give you, and your grub.conf. -Garret #menu.lst default 0 timeout 7 fallback 1 #password --md5 some kind of password that is encypted splashimage (fd0)/boot/grub/opt/smurffed.xpm.gz title BSD root (hd0,0,a) kernel /boot/loader title Hold the Phone halt title Reset me reboot title Floppy Boot lock root (fd0) chainloader #EOF menu.lst here is my menu.lst off my grub install floppy. this was created by building grub 0.97 from ports on my HP Kayak. the floppy was then prepared as below: fdformat /dev/fd0 newfs -O1 -n /dev/fd0 mount /dev/fd0 /mnt mkdir -p /mnt/boot/grub/opt I then copied the grub files from the /usr/local/share/grub/i386-freebsd if memory serves me correct to the /mnt/boot/grub folder. then copied in my splashimages, then prepared menu.lst as described. I then ran grub and setup the floppy to boot grub. now to install on a system I: mkdir -p /boot/grub/opt mount /dev/fd0 /mnt; cp -R /mnt/boot/grub /boot/grub change menu.lst as required to reference hardrives or different boot options like a windows partition or linux or whatever needs to be started up. boot the system with the floppy and go to grub console. make sure I can find /boot/grub/menu.lst then... root (hd0,0,a) # or whatever setup (hd0) # again depends and usually I take the floppy out, reboot, and grub asks me what I want to boot up. as far as the exact output from grub I don't know, but it didn't give any errors. it just said: checking for /boot/grub/menu.lst found installing stage1 success installing stage1_5 success installing stage2. success the typical everything is ok message. I have heard in later reading that a missing splashimage can mess things up, I will have to make sure I remembered to change the root for the image to the harddrive. But I have also read that this just happens sometimes with grub and certain machines. this is the only time I've seen it happen. I personally love me some grub. it just makes things easier in my world; at least usually. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub on FreeBSD
Nikolas Britton [EMAIL PROTECTED] writes: IIRC grub can't see UFS2, only UFS. I belive there is a work around though. google for it GRUB has been able to read UFS2 filesystems for a long time. That doesn't help Ask with his particular problem though. -- Christian Laursen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub on FreeBSD
On Mon, 29 May 2006, Ask Bj?rn Hansen wrote: Hi, I am trying to use grub instead of the usual boot0 thing on a Compact Flash card I use in Soekris and PC Engines WRAP systems. I installed grub from ports/sysutils/grub and put the package on my nanobsd system on the CF card. Booting on a Soekris box and running grub, I get this: grub root (hd0,1) Filesystem type unknown, partition type 0xa5 grub root (hd0,1,a) Filesystem type unknown, partition type 0xa5 It seems like it can't read the ufs filesystem? Any ideas? Did you copy the stage1, stage2, and ufs2_stage1_5 files to /boot/grub on the CF card? As I understand it, grub needs these files to understand UFS2. Just a guess. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
grub on FreeBSD
Hi, I am trying to use grub instead of the usual boot0 thing on a Compact Flash card I use in Soekris and PC Engines WRAP systems. I installed grub from ports/sysutils/grub and put the package on my nanobsd system on the CF card. Booting on a Soekris box and running grub, I get this: grub root (hd0,1) Filesystem type unknown, partition type 0xa5 grub root (hd0,1,a) Filesystem type unknown, partition type 0xa5 It seems like it can't read the ufs filesystem? Any ideas? - ask -- http://www.askbjoernhansen.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub on FreeBSD
On 5/29/06, Ask Bjørn Hansen [EMAIL PROTECTED] wrote: Hi, I am trying to use grub instead of the usual boot0 thing on a Compact Flash card I use in Soekris and PC Engines WRAP systems. I installed grub from ports/sysutils/grub and put the package on my nanobsd system on the CF card. Booting on a Soekris box and running grub, I get this: grub root (hd0,1) Filesystem type unknown, partition type 0xa5 grub root (hd0,1,a) Filesystem type unknown, partition type 0xa5 It seems like it can't read the ufs filesystem? Any ideas? IIRC grub can't see UFS2, only UFS. I belive there is a work around though. google for it -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
grub+freebsd
Hi Help to install please grub-0.95 on FreeBSD-5.4. At attempt to install grub the following message is deduced: Error 29: Disk write error Part Mount Size Newfs - - - - ad0s1none 30003MB DOS ad0s2a /256MB UFS2 Y ad0s2b SWAP 1006MBSWAP ad0s2d /var 256MB UFS2+S Y ad0s2e /tmp 256MB UFS2+S Y ad0s2f /usr 6383MBUFS2+S Y offset SizeEndName PTypeDesc Sutype -- --- - -- 0 63 62 - 12 unused0 63 6144761761447679 ad0s1 7fat 12 61447680 1670760078155279 ad0s2 165 freebsd 165 78155280 10080 78165359 - 12 unused0 # grub grub root (hd0,1,a) File system type is ufs2, partition type 0xa5 grub kernel /boot/loader [FreeBSD-a .out, loadaddr=0x2,text=0x1000, data=0x32000, bss=0x0, entry=0x20] grubboot # And another: #grub-install /dev/hd0 grub root (hd0,1,a) File system type is ufs2, partition type 0xa5 grubsetup --stage2=/boot/grub/stage2 --prefix=/boot/grub (hd0) Checking if /boot/grub/stage1exists.yes Checking if /boot/grub/stage2exists.yes Checking if /boot/grub/ufs2_stage1_5..exists.yes Running embed /boot/grub/ufs2_stage1_5 (hd0)...failed (this is not fatal) Running embed /boot/grub/ufs2_stage1_5 (hd0,1,a)...failed (this is not fatal) Running install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0) /boot/grub/stage2 p /boot/grub.lst...failed ***Error 29: Disk write error grubquite # In what here a problem, prompt please. -- Best regards, serge mailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub+freebsd
+++ serge [freebsd] [28-01-06 15:53 +0300]: | Hi | | Help to install please grub-0.95 on FreeBSD-5.4. | At attempt to install grub the following message is deduced: Error 29: Disk write error | | | Part Mount Size Newfs | - - - - | ad0s1none 30003MB DOS | ad0s2a /256MB UFS2 Y | ad0s2b SWAP 1006MBSWAP | ad0s2d /var 256MB UFS2+S Y | ad0s2e /tmp 256MB UFS2+S Y | ad0s2f /usr 6383MBUFS2+S Y | | | offset SizeEndName PTypeDesc Sutype | -- --- - -- | 0 63 62 - 12 unused0 | 63 6144761761447679 ad0s1 7fat 12 | 61447680 1670760078155279 ad0s2 165 freebsd 165 | 78155280 10080 78165359 - 12 unused0 | | | # grub | grub root (hd0,1,a) | File system type is ufs2, partition type 0xa5 | grub kernel /boot/loader | [FreeBSD-a .out, loadaddr=0x2,text=0x1000, data=0x32000, bss=0x0, | entry=0x20] | grubboot | # | | And another: | | #grub-install /dev/hd0 | grub root (hd0,1,a) | File system type is ufs2, partition type 0xa5 | grubsetup --stage2=/boot/grub/stage2 --prefix=/boot/grub (hd0) | Checking if /boot/grub/stage1exists.yes | Checking if /boot/grub/stage2exists.yes | Checking if /boot/grub/ufs2_stage1_5..exists.yes | Running embed /boot/grub/ufs2_stage1_5 (hd0)...failed (this is not fatal) | Running embed /boot/grub/ufs2_stage1_5 (hd0,1,a)...failed (this is not fatal) | Running install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0) | /boot/grub/stage2 p /boot/grub.lst...failed | | ***Error 29: Disk write error | | grubquite | # | | In what here a problem, prompt please. IIRC, you need to change sysctl setting of 'kern.geom.debugflags' from 0 to 16. Shantanoo pgpH2ZgSvDfnj.pgp Description: PGP signature
Re: grub doesn't know ufs filesystem
On Wednesday 14 December 2005 21:42, Micah wrote: I used chainloading for a while until I wanted multiple installs of FreeBSD on the same drive. Using chainloading from grub always booted the first FreeBSD regardless of which slice was specified in menu.lst. Changing it to use /boot/loader allowed me to actually have more than one FreeBSD on the same drive. I pretty sure you did something wrong, I've chainloaded multiple FreeBSD slices on the same drive using Lilo and other bootloaders. Also, grub places some files on a host filesystem. It may be more convenient to have those files stored on UFS rather than FAT or EXT. ... In that case, if you use grub (rather than FreeBSD's manager), you'd have to make a partition solely for grub. But is it a good idea for a bootloader to require external files at boot-time? I assume there are cases were grub does things that other loaders can't, but it seems to me that for most people booting FreeBSD it's an overcomplicated and awkward solution. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub doesn't know ufs filesystem
Hi Micah and Harley, Thanks for your answer. Humm.. I don't have any other grub on my path, and running which returns: # which grub /usr/local/sbin/grub The ports were updated quite recently.. in occasion of last update world. I did some more testing.. the strange thing is that I use the same grub boot floppy and the results are ok on the newly installed freebsd boxes, while on the two that are already installed the results are bad.. test 1: === - made a grub floppy - boot the existing FreeBSD boxes (2 boxes) from grub floppy result -- grub doesn't know the ufs filesystem test 2: === - installed a brand new FreeBSD 5-3-RELEASE with default partitioning on the whole disk on a separate pc - boot with grub floppy result -- grub recognizes the ufs filesystem test 3: === - same as test2, but / root has now soft-updates option - boot with grub floppy result -- grub recognizes the ufs filesystem test 4: === - same as test2, but partitioning done with partition magic as was done on the computers of test1 - boot with grub floppy result -- grub recognizes the ufs filesystem All that seams to point out that there's something wrong with the existing FreeBSD boxes.. but What? I must say that both boxes had all filesystem dumped and restored after repartitioning for permitting the use of dumping software such as ghost (that didn't like the partitioning done by freebsd during installation..) Any more ideas? Harley D. Eades III wrote: On Wed, 2005-12-14 at 08:36 -0800, Micah wrote: Roberto Nunnari wrote: Hello list. Please also reply to my mailbox, as I'm not on the list. Thank you. I have a old grub floppy that I use time to time to boot/recover pc with different OS.. Today I wanted to boot a freebsd 5.3-RELEASE-p23 box, but to my surprise grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader So I thought I'd make a grub floppy with a recent version, but even with version 0.97 things won't change.. # cd /usr/ports/sysutils/grub # make install # grub [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,0,a) Filesystem type unknown, partition type 0xa5 grub kernel /boot/loader Error 17: Cannot mount selected partition grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 grub quit # mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) Any hint/thought/advice? Best regards. I just installed grub from ports and duplicated your test and it works fine. I'd start by checking your installation and making sure you don't have any other grubs in your path. Some of the grubs that ship with Linux distros do not support ufs. Do a find/locate on grub to see what turns up. Do a which grub, you should get /usr/local/sbin/grub. If not, issue /usr/local/sbin/grub from a command prompt and duplicate your test. If that's broken, make sure your ports tree is up to date, make sure /usr/ports/devel/autoconf259 /usr/ports/devel/automake19 /usr/ports/devel/gmake are up to date (grub's build dependancies) then deinstall, clean, and reintsall the grub port. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I can second this, I use grub all the time, as well as test grub2 on FreeBSD and both work great for me. --Harley -BEGIN GEEK CODE BLOCK- G: GCS-- d- a? C B- E+++ W+++ N++ w--- X+++ b++ G e* r x+ z+ --END GEEK CODE BLOCK-- -- Roberto Nunnari -software engineer- mailto:[EMAIL PROTECTED] Scuola Universitaria Professionale della Svizzera Italiana Dipartimento Tecnologie Innovative http://www.dti.supsi.ch SUPSI-DTI Via Cantonaletel: +41-91-6108561 6928 Mannofax: +41-91-6108570 Switzerland (o o) ===oOO==(_)==OOo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions
Re: grub doesn't know ufs filesystem
One more note.. let's call 'bad' the pc that grub doesn't like and ok the others.. and note that the two pc have identical disk drives.. so.. bad# fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 30009357 (14653 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED ok# fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 30009357 (14653 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 3/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED as you can see, there's a difference in the end head.. bad says end head is 254, while ok says end head is 3 Could that be a source of trouble? bad# disklabel ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 1048576 524288 swap c: 300093570unused0 0 # raw part, don't edit d: 524288 15728644.2BSD 2048 16384 32776 e: 524288 20971524.2BSD 2048 16384 32776 f: 27387917 26214404.2BSD 2048 16384 28552 ok# disklabel ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 996992 524288 swap c: 300093570unused0 0 # raw part, don't edit d: 524288 15212804.2BSD 2048 16384 32776 e: 524288 20455684.2BSD 2048 16384 32776 f: 27387917 25698564.2BSD 2048 16384 28552 the disklabel is essentialy the same.. apart from the size of the swap and consequently the offset of the rest of the internal partitions.. Again.. any ideas? -- Robi Harley D. Eades III wrote: On Wed, 2005-12-14 at 08:36 -0800, Micah wrote: Roberto Nunnari wrote: Hello list. Please also reply to my mailbox, as I'm not on the list. Thank you. I have a old grub floppy that I use time to time to boot/recover pc with different OS.. Today I wanted to boot a freebsd 5.3-RELEASE-p23 box, but to my surprise grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader So I thought I'd make a grub floppy with a recent version, but even with version 0.97 things won't change.. # cd /usr/ports/sysutils/grub # make install # grub [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,0,a) Filesystem type unknown, partition type 0xa5 grub kernel /boot/loader Error 17: Cannot mount selected partition grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 grub quit # mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) Any hint/thought/advice? Best regards. I just installed grub from ports and duplicated your test and it works fine. I'd start by checking your installation and making sure you don't have any other grubs in your path. Some of the grubs that ship with Linux distros do not support ufs. Do a find/locate on grub to see what turns up. Do a which grub, you should get /usr/local/sbin/grub
Re: grub doesn't know ufs filesystem
Roberto Nunnari wrote: One more note.. let's call 'bad' the pc that grub doesn't like and ok the others.. and note that the two pc have identical disk drives.. so.. bad# fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 30009357 (14653 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED ok# fdisk *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=29777 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 30009357 (14653 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 3/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED as you can see, there's a difference in the end head.. bad says end head is 254, while ok says end head is 3 Could that be a source of trouble? bad# disklabel ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 1048576 524288 swap c: 300093570unused0 0 # raw part, don't edit d: 524288 15728644.2BSD 2048 16384 32776 e: 524288 20971524.2BSD 2048 16384 32776 f: 27387917 26214404.2BSD 2048 16384 28552 ok# disklabel ad0s1 # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 996992 524288 swap c: 300093570unused0 0 # raw part, don't edit d: 524288 15212804.2BSD 2048 16384 32776 e: 524288 20455684.2BSD 2048 16384 32776 f: 27387917 25698564.2BSD 2048 16384 28552 the disklabel is essentialy the same.. apart from the size of the swap and consequently the offset of the rest of the internal partitions.. Again.. any ideas? -- Robi Harley D. Eades III wrote: On Wed, 2005-12-14 at 08:36 -0800, Micah wrote: Roberto Nunnari wrote: Hello list. Please also reply to my mailbox, as I'm not on the list. Thank you. I have a old grub floppy that I use time to time to boot/recover pc with different OS.. Today I wanted to boot a freebsd 5.3-RELEASE-p23 box, but to my surprise grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader So I thought I'd make a grub floppy with a recent version, but even with version 0.97 things won't change.. # cd /usr/ports/sysutils/grub # make install # grub [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,0,a) Filesystem type unknown, partition type 0xa5 grub kernel /boot/loader Error 17: Cannot mount selected partition grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 grub quit # mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) Any hint/thought/advice? Best regards. I just installed grub from ports and duplicated your test and it works fine. I'd start by checking your installation and making sure you don't have any other grubs in your path. Some of the grubs that ship with Linux distros do not support ufs. Do a find/locate on grub to see what turns up. Do a which grub, you should get
Re: grub doesn't know ufs filesystem
On Wed, Dec 14, 2005 at 03:52:33PM +0100, Roberto Nunnari wrote: grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader You are correct. Old versions of grub don't know about UFS2 filesystem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
grub doesn't know ufs filesystem
Hello list. Please also reply to my mailbox, as I'm not on the list. Thank you. I have a old grub floppy that I use time to time to boot/recover pc with different OS.. Today I wanted to boot a freebsd 5.3-RELEASE-p23 box, but to my surprise grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader So I thought I'd make a grub floppy with a recent version, but even with version 0.97 things won't change.. # cd /usr/ports/sysutils/grub # make install # grub [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,0,a) Filesystem type unknown, partition type 0xa5 grub kernel /boot/loader Error 17: Cannot mount selected partition grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 grub quit # mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) Any hint/thought/advice? Best regards. -- Robi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub doesn't know ufs filesystem
Roberto Nunnari wrote: Hello list. Please also reply to my mailbox, as I'm not on the list. Thank you. I have a old grub floppy that I use time to time to boot/recover pc with different OS.. Today I wanted to boot a freebsd 5.3-RELEASE-p23 box, but to my surprise grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader So I thought I'd make a grub floppy with a recent version, but even with version 0.97 things won't change.. # cd /usr/ports/sysutils/grub # make install # grub [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,0,a) Filesystem type unknown, partition type 0xa5 grub kernel /boot/loader Error 17: Cannot mount selected partition grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 grub quit # mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) Any hint/thought/advice? Best regards. I just installed grub from ports and duplicated your test and it works fine. I'd start by checking your installation and making sure you don't have any other grubs in your path. Some of the grubs that ship with Linux distros do not support ufs. Do a find/locate on grub to see what turns up. Do a which grub, you should get /usr/local/sbin/grub. If not, issue /usr/local/sbin/grub from a command prompt and duplicate your test. If that's broken, make sure your ports tree is up to date, make sure /usr/ports/devel/autoconf259 /usr/ports/devel/automake19 /usr/ports/devel/gmake are up to date (grub's build dependancies) then deinstall, clean, and reintsall the grub port. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub doesn't know ufs filesystem
On Wed, 2005-12-14 at 08:36 -0800, Micah wrote: Roberto Nunnari wrote: Hello list. Please also reply to my mailbox, as I'm not on the list. Thank you. I have a old grub floppy that I use time to time to boot/recover pc with different OS.. Today I wanted to boot a freebsd 5.3-RELEASE-p23 box, but to my surprise grub reported: Filesystem type unknown, partition type 0xa5 and thus cannot mount /boot/loader So I thought I'd make a grub floppy with a recent version, but even with version 0.97 things won't change.. # cd /usr/ports/sysutils/grub # make install # grub [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub root (hd0,0,a) Filesystem type unknown, partition type 0xa5 grub kernel /boot/loader Error 17: Cannot mount selected partition grub root (hd0, TAB Possible partitions are: Partition num: 0, [BSD sub-partitions immediately follow] BSD Partition num: 'a', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'b', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'd', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'e', Filesystem type unknown, partition type 0xa5 BSD Partition num: 'f', Filesystem type unknown, partition type 0xa5 grub quit # mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) Any hint/thought/advice? Best regards. I just installed grub from ports and duplicated your test and it works fine. I'd start by checking your installation and making sure you don't have any other grubs in your path. Some of the grubs that ship with Linux distros do not support ufs. Do a find/locate on grub to see what turns up. Do a which grub, you should get /usr/local/sbin/grub. If not, issue /usr/local/sbin/grub from a command prompt and duplicate your test. If that's broken, make sure your ports tree is up to date, make sure /usr/ports/devel/autoconf259 /usr/ports/devel/automake19 /usr/ports/devel/gmake are up to date (grub's build dependancies) then deinstall, clean, and reintsall the grub port. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I can second this, I use grub all the time, as well as test grub2 on FreeBSD and both work great for me. --Harley -BEGIN GEEK CODE BLOCK- G: GCS-- d- a? C B- E+++ W+++ N++ w--- X+++ b++ G e* r x+ z+ --END GEEK CODE BLOCK-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub doesn't know ufs filesystem
On Wednesday 14 December 2005 16:36, Micah wrote: Some of the grubs that ship with Linux distros do not support ufs. I'm curious as to why people care about this so much. There are numerous threads about whether or not particular bootloaders support UFS. A bootloader needs to understand Linux filesystems to boot Linux off a logical partition, but BSDs slices are always on primary partitions. Is there really any advantage to going directly to /boot/loader, rather than simply chaining? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: grub doesn't know ufs filesystem
RW wrote: On Wednesday 14 December 2005 16:36, Micah wrote: Some of the grubs that ship with Linux distros do not support ufs. I'm curious as to why people care about this so much. There are numerous threads about whether or not particular bootloaders support UFS. A bootloader needs to understand Linux filesystems to boot Linux off a logical partition, but BSDs slices are always on primary partitions. Is there really any advantage to going directly to /boot/loader, rather than simply chaining? I used chainloading for a while until I wanted multiple installs of FreeBSD on the same drive. Using chainloading from grub always booted the first FreeBSD regardless of which slice was specified in menu.lst. Changing it to use /boot/loader allowed me to actually have more than one FreeBSD on the same drive. Also, grub places some files on a host filesystem. It may be more convenient to have those files stored on UFS rather than FAT or EXT. Or you may have a system that consists only of multiple FreeBSD installs. In that case, if you use grub (rather than FreeBSD's manager), you'd have to make a partition solely for grub. HTH, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diskless FreeBSD with grub
--- Ursprüngliche Nachricht --- Von: Richard Burakowski [EMAIL PROTECTED] An: Daniel Hepper [EMAIL PROTECTED] Kopie: freebsd-questions@freebsd.org Betreff: Re: diskless FreeBSD with grub Datum: Thu, 03 Nov 2005 10:22:15 +1100 Daniel Hepper wrote: Hi, I want to boot diskless into FreeBSD-5.4 with grub. snip title bsd-nfsroot kernel (nd)/kernel/kernel ip=dhcp root=/dev/nfs nfsroot=141.2.71.253:/dta/fBSD_diskless boot /snip It loads the kernel, but does not boot. My guess is that it doesn't find the root partition. if you look carefully, it's telling you where it thinks the root partition is. if that looks right, then check your nfs server log. you have seen the diskless booting howto on freebsd.org (among others) and recompiled your kernel for diskless booting? IIRC the kernel goes through a second round of querying dhcp for info. Thanks for your hints! I've read the diskless booting howto before, but I did not yet built a custom kernel. Now I have a custom kernel with: options BOOTP # Use BOOTP to obtain IP address/hostname options BOOTP_NFSROOT # NFS mount root file system using BOOTP info hints GENERIC.hints When I boot this kernel from disk, it shows the device hints, sends out dhcp-requests and tries to mount / with nfs. But when I load it over the net, i get the following: grub root (nd) Filesytem type is tftp, using hole disk. grub kernel --type=freebsd /freebsd-boot/kernel/kernel [FreeBSD-elf, 0x40:0x446f54:0x0,0x847f60:0x7d600:0x4fce0, shtab=0 16438, entry=0x43f2b0] grub boot The prompt disappears and the system reboots after approx. 25 sec. (The custom kernel has the same behaviour as the default kernel from the FreeBSD installationdisk) Where does it tell me where it thinks the root filesystem is? Greetings, Daniel Hepper -- Telefonieren Sie schon oder sparen Sie noch? NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
diskless FreeBSD with grub
Hi, I want to boot diskless into FreeBSD-5.4 with grub. I've setup dhcp to provide boot and ip information, tftp to load the kernel and nfs to share the root filesystem. It runs smoothly when I use the pxeloader from FreeBSD, but I can't get it working with Grub. I tried this grub configuration: snip title bsd-nfsroot kernel (nd)/kernel/kernel ip=dhcp root=/dev/nfs nfsroot=141.2.71.253:/dta/fBSD_diskless boot /snip It loads the kernel, but does not boot. My guess is that it doesn't find the root partition. This one: snip title bsd-nfsroot kernel (nd)/loader ip=dhcp root=/dev/nfs nfsroot=141.2.71.253:/dta/fBSD_diskless boot /snip loader says it can't find the kernel. And this one: snip title bsd-nfsroot kernel (nd)/pxeboot ip=dhcp root=/dev/nfs nfsroot=141.2.71.253:/dta/fBSD_diskless boot /snip grub complains that pxeboot is not a correct executable I have spent hours digging the web without a solution. I would really appreciate it, if someone could help or give me a pointer to helpful resources. The background of the problem: I manage the software installation on a router-testbed. It consist of 24 identical x86-systems, with different local OS installation. When a system boots, it load GRUB via PXE from a server. The grub menu is generated dynamically from a configuration file, which determines what OS the system should start. For administration purposes, among other things software distribution, you can configure the systems to boot a diskless linux system via nfs (this works). But as some users run FreeBSD and Linux can't access UFS2-partitions, a diskless FreeBSD-image is required. Greetings, Daniel Hepper ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diskless FreeBSD with grub
Daniel Hepper wrote: Hi, I want to boot diskless into FreeBSD-5.4 with grub. snip title bsd-nfsroot kernel (nd)/kernel/kernel ip=dhcp root=/dev/nfs nfsroot=141.2.71.253:/dta/fBSD_diskless boot /snip It loads the kernel, but does not boot. My guess is that it doesn't find the root partition. if you look carefully, it's telling you where it thinks the root partition is. if that looks right, then check your nfs server log. you have seen the diskless booting howto on freebsd.org (among others) and recompiled your kernel for diskless booting? IIRC the kernel goes through a second round of querying dhcp for info. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Add FreeBSD_AMD64__5.4 and keep GRUB
I have an AMD64 system with : WindowsXP Suse 9.3 GRUB I want to install from CDs How can I install FreeBSD_AMD64__5.4 and add it to the GRUB later without harming Windows and Suse ? Kind regards John Vandeput ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Install GRUB for FreeBSD
Anyone know how to install GRUB for FreeBSD when you can't boot to it? I am totally lost now guys with the booting. FreeBSD bootloader has me so frustrated Linux GRUB is simple and intuitive to use and BSD loader has me lost after weeks :( I even installed GRUB into MBR and the BSD bootloader won't go away! :( Someone please tell me what the best way to install grub is I guess you need it in the MBR but where will the menu.lst be stored? Please help thx __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install GRUB for FreeBSD
hi! On Sun, 18 Sep 2005 12:08:08 -0400 (EDT) John Do [EMAIL PROTECTED] wrote: Anyone know how to install GRUB for FreeBSD when you can't boot to it? you need at least one bootable operating system. try a livecd if youre system doesnt boot at all. I even installed GRUB into MBR and the BSD bootloader won't go away! :( make sure you install it to the correct disk! Someone please tell me what the best way to install grub is I guess you need it in the MBR but where will the menu.lst be stored? AFAIK grub has problems with reading ufs (please correct me if i'm wrong! maybe it's just because my grub version is a bit old ;) ). you can get around this by putting the grub config on a partition grub can read (like ext2fs or fat32) and then just chainload the freebsd loader installed into the freebsd partition. of course this is not the best solution but it works for me :) greets, jonas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install GRUB for FreeBSD
John Do [EMAIL PROTECTED] writes: Linux GRUB is simple and intuitive to use and BSD loader has me lost after weeks :( I know both enough to say that BSD's is way more intuitive and much simpler to configure and install. I even installed GRUB into MBR and the BSD bootloader won't go away! :( I've made mine go away several times. Note that you shouldn't need to get rid of the MBR on the second disk, with Grub on the first. I don't know if Grub can be made to boot the second disk's MBR, or not. Probably. Someone please tell me what the best way to install grub is I guess you need it in the MBR but where will the menu.lst be stored? It starts out on a floppy file system. Then you either just boot off the floppy, or you install it to the hard disk MBR, other first-track sectors, and maybe your OS's root FS. I don't recall if you need a menu.lst or not. That is, I don't know if Grub can be installed only to the first track, or needs the menu.lst in an FS; it seems like a bad requirement, if so. You might search the Internet for a pre-build Grub floppy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install GRUB for FreeBSD
jonas wrote: AFAIK grub has problems with reading ufs (please correct me if i'm wrong! maybe it's just because my grub version is a bit old ;) ). you can get around this by putting the grub config on a partition grub can read (like ext2fs or fat32) and then just chainload the freebsd loader installed into the freebsd partition. of course this is not the best solution but it works for me :) greets, jonas I use grub installed on a ufs filesystem and it has absolutely no problems reading config files, stages, or splash screens from it. Later, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install GRUB for FreeBSD
Gary W. Swearingen wrote: It starts out on a floppy file system. Then you either just boot off the floppy, or you install it to the hard disk MBR, other first-track sectors, and maybe your OS's root FS. I don't recall if you need a menu.lst or not. That is, I don't know if Grub can be installed only to the first track, or needs the menu.lst in an FS; it seems like a bad requirement, if so. In order for grub to work as a menu, it requires a stage 2 loader that resides somewhere on your hardrive outside of the MBR. It's my understanding that grub was too big to fit just in the MBR and that necessitated this arrangement. If you don't mind manually typing in commands such as root(hdx,x,x) and kernel /boot/loader then you don't need grub installed anywhere other than the MBR. Though the ufs stage 1.5 might cause problems with freebsd in that regard. I haven't tried grub without /some/ aspect of it installed to a freebsd partition. Later, Micah ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install GRUB for FreeBSD
Micah [EMAIL PROTECTED] writes: In order for grub to work as a menu, it requires a stage 2 loader that resides somewhere on your hardrive outside of the MBR. It's my understanding that grub was too big to fit just in the MBR and that necessitated this arrangement. If you don't mind manually typing in Yeah, but I definitely remember that Grub installs stuff on other sectors of the first track, probably staring with the second sector. So it should be able to store the menu stuff there too, but I don't know if it actual can (I also had it using the menu file in /boot/boot/grub, I think it was for some odd reason). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stand-alone GRUB HELP
On Sep 12, 2005, at 2:17 PM, John Do wrote: Hi Glen, Thanks for the reply I tried the following and there was no change to the boot menu: boot0cfg -B -s 5 ad0 boot0cfg -B -s 2 ad2 All I can say is, have you read the handbook yet, and please bottom post from now on in emails. Thanks :). -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stand-alone GRUB HELP
At 10:17 PM 9/11/2005, John Do wrote: Hi Glen, Thanks for the reply I tried the following and there was no change to the boot menu: boot0cfg -B -s 5 ad0 boot0cfg -B -s 2 ad2 What does boot0cfg -v show for the two disks you have? Output from fdisk and bsdlabel for both would be helpful too. -Glenn --- Glenn Dawson [EMAIL PROTECTED] wrote: At 09:18 PM 9/11/2005, John Do wrote: Hi guys I have been reading documentation and I'm still confused. I have Windows on ad0 and FreeBSD on ad2 I installed the BSD bootloader but it is only booting Windows. There is some limitation or problem and no matter what I try in the emergency shell I cannot configure boot0cfg to work properly. So I need two solutions to try: How do I configure the BSD boot loader to work to boot both Windows and FreeBSD? I have tried commands like boot0cfg -B -s 2 ad2 and it doesn't seem to help or boot I think what you want is: test54# boot0cfg -B -s 5 ad0 test54# boot0cfg -B -s 1 ad2 If you reboot, you should end up booting from the first slice on ad2. This is what everything looks like on one of my test boxes: test54# boot0cfg -v ad4 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0x07 1023:254:63 63 20964762 2 0x80 1023:255:63 0xa5 1023:254:63 20964825 20964825 3 0x00 1023:255:63 0x07 1023:254:63 41929650 61432560 4 0x00 1023:255:63 0xa5 1023: 80:63 103362210287359758 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F5 (Drive 1) test54# boot0cfg -v ad6 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 1023:254:63 63156296322 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F1 (Slice 1) Not exactly the same as your setup, but close. On ad4, 1 is windows, 2 is FreeBSD, 3 and 4 are non-bootable. On ad6, 1 is FreeBSD. -Glenn Second solution: Stand-alone GRUB install How can I install GRUB stand-alone? How do I install it into /boot? I guess /boot = some mounted partition of a unix OS? Would it be best to make /boot under the existing FreeBSD partition? The more exact details the better. I've been scratching my head over this for days thx! __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] __ Find your next car at http://autos.yahoo.ca --- was it the same cat? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Stand-alone GRUB HELP
Hi guys I have been reading documentation and I'm still confused. I have Windows on ad0 and FreeBSD on ad2 I installed the BSD bootloader but it is only booting Windows. There is some limitation or problem and no matter what I try in the emergency shell I cannot configure boot0cfg to work properly. So I need two solutions to try: How do I configure the BSD boot loader to work to boot both Windows and FreeBSD? I have tried commands like boot0cfg -B -s 2 ad2 and it doesn't seem to help or boot Second solution: Stand-alone GRUB install How can I install GRUB stand-alone? How do I install it into /boot? I guess /boot = some mounted partition of a unix OS? Would it be best to make /boot under the existing FreeBSD partition? The more exact details the better. I've been scratching my head over this for days thx! __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stand-alone GRUB HELP
At 09:18 PM 9/11/2005, John Do wrote: Hi guys I have been reading documentation and I'm still confused. I have Windows on ad0 and FreeBSD on ad2 I installed the BSD bootloader but it is only booting Windows. There is some limitation or problem and no matter what I try in the emergency shell I cannot configure boot0cfg to work properly. So I need two solutions to try: How do I configure the BSD boot loader to work to boot both Windows and FreeBSD? I have tried commands like boot0cfg -B -s 2 ad2 and it doesn't seem to help or boot I think what you want is: test54# boot0cfg -B -s 5 ad0 test54# boot0cfg -B -s 1 ad2 If you reboot, you should end up booting from the first slice on ad2. This is what everything looks like on one of my test boxes: test54# boot0cfg -v ad4 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0x07 1023:254:63 63 20964762 2 0x80 1023:255:63 0xa5 1023:254:63 20964825 20964825 3 0x00 1023:255:63 0x07 1023:254:63 41929650 61432560 4 0x00 1023:255:63 0xa5 1023: 80:63103362210287359758 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F5 (Drive 1) test54# boot0cfg -v ad6 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 1023:254:63 63156296322 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F1 (Slice 1) Not exactly the same as your setup, but close. On ad4, 1 is windows, 2 is FreeBSD, 3 and 4 are non-bootable. On ad6, 1 is FreeBSD. -Glenn Second solution: Stand-alone GRUB install How can I install GRUB stand-alone? How do I install it into /boot? I guess /boot = some mounted partition of a unix OS? Would it be best to make /boot under the existing FreeBSD partition? The more exact details the better. I've been scratching my head over this for days thx! __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stand-alone GRUB HELP
Hi Glen, Thanks for the reply I tried the following and there was no change to the boot menu: boot0cfg -B -s 5 ad0 boot0cfg -B -s 2 ad2 --- Glenn Dawson [EMAIL PROTECTED] wrote: At 09:18 PM 9/11/2005, John Do wrote: Hi guys I have been reading documentation and I'm still confused. I have Windows on ad0 and FreeBSD on ad2 I installed the BSD bootloader but it is only booting Windows. There is some limitation or problem and no matter what I try in the emergency shell I cannot configure boot0cfg to work properly. So I need two solutions to try: How do I configure the BSD boot loader to work to boot both Windows and FreeBSD? I have tried commands like boot0cfg -B -s 2 ad2 and it doesn't seem to help or boot I think what you want is: test54# boot0cfg -B -s 5 ad0 test54# boot0cfg -B -s 1 ad2 If you reboot, you should end up booting from the first slice on ad2. This is what everything looks like on one of my test boxes: test54# boot0cfg -v ad4 # flag start chs type end chs offset size 1 0x00 0: 1: 1 0x07 1023:254:63 63 20964762 2 0x80 1023:255:63 0xa5 1023:254:63 20964825 20964825 3 0x00 1023:255:63 0x07 1023:254:63 41929650 61432560 4 0x00 1023:255:63 0xa5 1023: 80:63 103362210287359758 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F5 (Drive 1) test54# boot0cfg -v ad6 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 1023:254:63 63156296322 version=1.0 drive=0x80 mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F1 (Slice 1) Not exactly the same as your setup, but close. On ad4, 1 is windows, 2 is FreeBSD, 3 and 4 are non-bootable. On ad6, 1 is FreeBSD. -Glenn Second solution: Stand-alone GRUB install How can I install GRUB stand-alone? How do I install it into /boot? I guess /boot = some mounted partition of a unix OS? Would it be best to make /boot under the existing FreeBSD partition? The more exact details the better. I've been scratching my head over this for days thx! __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
