Date: Sun, 5 Nov 2006 10:09:21 -1000 From: spoggle <dcornejo@gmail.com> To: "=?ISO-8859-1?Q?Sten_Daniel_S=F8rsdal?=" <lists@wm-access.no> Cc: freebsd-embedded@freebsd.org Subject: Re: bootmgr on pc engines wrap board Message-ID: <6b8e8f4f0611051209y1e982d48m36da34fba89e08e3@mail.gmail.com> In-Reply-To: <454DFEED.5@wm-access.no> References: <BA04243B-9E9C-4E60-9525-21C90E52A6FB@develooper.com> <6b8e8f4f0611011548r3b015849g6c851df99ede4242@mail.gmail.com> <454DFEED.5@wm-access.no>
next in thread | previous in thread | raw e-mail | index | archive | help
I've never really investigated it beyond finding that using the "-o packet" option on boot0cfg results in cards that don't boot. That I can get it to boot somehow is good enough for me... dave c On 11/5/06, Sten Daniel S=F8rsdal <lists@wm-access.no> wrote: > spoggle wrote: > > 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. > > > > Are you saying WRAP doesn't support BIOS INT 13h or just that it doesn't > work correctly? > Which int 13h function doesn't work or what is it that it's missing? > > -- > Sten Daniel S=F8rsdal > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6b8e8f4f0611051209y1e982d48m36da34fba89e08e3>