FA-2
January 17th, 2010, 03:13 PM
I was using a previous version of ubuntu that came with grub 0.97 (I think). I was able to boot to BeOS on its own partition using the following:
BeOS
rootnoverify (hd0,5)
chainloader +1
rootnoverify is what made it work. Without rootnoverify, BeOS would not boot.
When I upgraded to ubuntu 9.10, it "comes with" Grub 2. grub didn't find the partition automatically, so I added the entry above to the /etc/grub.d/40_custom file, ran update-grub, and rebooted.
Grub 2 no longer supports rootnoverify. It told me so when I attempted to boot BeOS. I did some searching, and rootnoverify has apparently been declared "useless' (I found that on a Grub 2 page on the ubuntu site). I tried changing it to root=(hd0,5) and I get a signature error & no boot.
What should be used in place of rootnoverify? It does not seem too useless to me! :confused:
on edit: I forgot to mention, I am trying to boot BeOS PE5 MAX, if it makes a difference.
BeOS
rootnoverify (hd0,5)
chainloader +1
rootnoverify is what made it work. Without rootnoverify, BeOS would not boot.
When I upgraded to ubuntu 9.10, it "comes with" Grub 2. grub didn't find the partition automatically, so I added the entry above to the /etc/grub.d/40_custom file, ran update-grub, and rebooted.
Grub 2 no longer supports rootnoverify. It told me so when I attempted to boot BeOS. I did some searching, and rootnoverify has apparently been declared "useless' (I found that on a Grub 2 page on the ubuntu site). I tried changing it to root=(hd0,5) and I get a signature error & no boot.
What should be used in place of rootnoverify? It does not seem too useless to me! :confused:
on edit: I forgot to mention, I am trying to boot BeOS PE5 MAX, if it makes a difference.