On Nov 1, 2006, at 3:48 PM, spoggle wrote:
You can prove it by running boot0cfg with the -o nopacket option on
the CF card.
Whee - that worked, thank you!
- ask
--
http://askask.com/ - http://develooper.com/
___
freebsd-stable@freebsd.org
Hi,
bootmgr hangs on the PC Engines WRAP board.
It's been brought up before on the small@ list (IIRC), but with no
solution.
It hangs just after
1 FreeBSD
2 FreeBSD
I have a stack of the WRAP boards I was going to use for the NTP
Pool, but I really want to use a nanobsd style
On Wed, Nov 01, 2006 at 01:45:45PM -0800, Ask Bj?rn Hansen wrote:
Hi,
bootmgr hangs on the PC Engines WRAP board.
It's been brought up before on the small@ list (IIRC), but with no
solution.
It hangs just after
1 FreeBSD
2 FreeBSD
Have you set the bootloader to use serial?
On Nov 1, 2006, at 2:00 PM, Andrew Thompson wrote:
Have you set the bootloader to use serial? Set -h in /boot.config
Yes.
(the nanobsd build process does that by default,
echo -h ${NANO_WORLDDIR}/boot.config
)
- ask
--
http://www.askbjoernhansen.com/
In message: [EMAIL PROTECTED]
Andrew Thompson [EMAIL PROTECTED] writes:
: On Wed, Nov 01, 2006 at 01:45:45PM -0800, Ask Bj?rn Hansen wrote:
: Hi,
:
: bootmgr hangs on the PC Engines WRAP board.
:
: It's been brought up before on the small@ list (IIRC), but with no
: solution.
NanoBSD write the boot block to use the disk packet (BIOS INT 0x13)
interface. This doesn't work on any of the WRAP or Soekris (45xx or
48xx) boards I've got.
From memory: look for the boot0cfg line at around line 367 of the
nanobsd.sh script and delete -o packet from it.
You can prove it by
