Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 341383 - sys-freebsd/boot0-7.2: can't boot gentoo/freebsd-7.2 inside virtualbox-ose-3.1.8
Summary: sys-freebsd/boot0-7.2: can't boot gentoo/freebsd-7.2 inside virtualbox-ose-3.1.8
Status: RESOLVED FIXED
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: FreeBSD (show other bugs)
Hardware: x86 FreeBSD
: High normal (vote)
Assignee: Gentoo/BSD Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-16 20:17 UTC by i.Dark_Templar
Modified: 2013-08-27 20:22 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
boot0-7.2.ebuild.diff (boot0-7.2.ebuild.diff,658 bytes, patch)
2011-04-23 22:18 UTC, Dmitri Bogomolov
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description i.Dark_Templar 2010-10-16 20:17:24 UTC
Using ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/7.3/FreeBSD-7.3-RELEASE-i386-livefs.iso as livecd and http://www.gentoo.org/doc/en/gentoo-freebsd.xml as guide, I'm installing gentoo/freebsd-7.2 inside virtualbox-ose-3.1.8. All installation goes fine. But then I can't boot gentoo/freebsd-7.2.

I'm getting next message:
can't work out which disk we are booting from
Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0


Reproducible: Always

Steps to Reproduce:
1. Inside virtualbox-ose-3.1.8, using ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/7.3/FreeBSD-7.3-RELEASE-i386-livefs.iso as livecd and http://www.gentoo.org/doc/en/gentoo-freebsd.xml as guide, install gentoo/freebsd with portage profile x86/freebsd-7.2
2. install boot0 or grub (doesn't really matter) during step 1
3. boot into installed system

Actual Results:  
System doesn't boot, says
can't work out which disk we are booting from
Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0

Expected Results:  
System should boot fine

I've tried both grub and boot0, but looks like it's issue with /boot/loader.
If I tell to boot /boot/kernel/kernel directly, first it says something like "loader(8) metadata is missing", then it asks about root partition, I type: "ufs:ad0s1a", then it boots fine, but when it comes to login prompt, keyword stops working. I think that's because "loader(8) metadata is missing".

By the way, host is gentoo/amd64 if this is relevant.
Comment 1 i.Dark_Templar 2010-10-16 20:19:05 UTC
not "keyword", it's "keyboard", fix
Comment 2 i.Dark_Templar 2010-10-16 21:36:01 UTC
During experiments I found out that emerging sys-freebsd/boot0 with CFLAGS="-march=i686 -pipe" and CXXFLAGS="-march=i686 -pipe" solves problem.

Before that I used CFLAGS="-O2 -march=i686 -pipe" with same CXXFLAGS

So, "-O2", and probably other optimization flags should be filtered in this package.

Please, update ebuild and then close bug.
Comment 3 Dmitri Bogomolov 2011-04-23 22:16:12 UTC
(In reply to comment #2)

> So, "-O2", and probably other optimization flags should be filtered in this
> package.

I confirm. After filter-flags I can boot g/fbsd-7.2.
Comment 4 Dmitri Bogomolov 2011-04-23 22:18:46 UTC
Created attachment 270981 [details, diff]
boot0-7.2.ebuild.diff

diff vs sys-freebsd/boot0-7.2 in tree
Comment 5 Dmitri Bogomolov 2011-04-23 22:21:24 UTC
Before filter-flags I can't boot g/fbsd-7 on real hardware and on qemu-kvn.
Comment 6 Alexis Ballier gentoo-dev 2013-08-27 20:22:54 UTC
shouldnt be a problem with recent boot0 versions