Re: hang on reboot

Ken <[email protected]> Wed, 12 Jun 2002 18:11:48 -0400 (EDT)
Newsgroups gmane.os.openbsd.embedded
Message-ID <[email protected]>
Just for reference sake and for those that have the older BIOS revs what
rev is that boot loader included with?

On Wed, 12 Jun 2002, Soren Kristensen wrote:

> Hi David,
>
> First you might want to try the new builtin BIOS master boot loader, at
> the monitor promt enter:
>
> > boot :X
>
> X can be 1 to 4, that will boot the X partition on the CF disk, assuming
> that the partition table is still there.... I believe that OpenBSD for
> some reason as default use partition 4, right ?
>
>
> Regards,
>
>
> Soren
>
>
> David Simmons wrote:
> >
> > > try installing the 3.1 boot loader and making sure you have
> > > the latest rev of firmware from soren...
> > >
> > > The 3.1 boot loader seems to play nicer
> >
> > Guys....I'll apologize up-front for being the Moron Of the Year...but I've
> > really monkey'ed by system up.  Was having this same ReBoot problem -
> > downloaded the 3.1 BootEasy program
> > (ftp://ftp.openbsd.org/OpenBSD/3.1/tools/booteasy/Boot.bin ) and issued
> > (according to the FAQ) the following to reinitilize the MBR:
> >
> > fdisk -i -f /root/Boot.bin wd0
> >
> > no errors...but when I reboot, I get the following:
> >
> > Soekris Engineering net4501               CPU 80486 134 Mhz
> >
> > 0064 Mbyte Memory
> >
> > Primary   Master Micron MTCF032A                         31 Mbyte
> >
> > PXE-M00: BootManage UNDI, PXE-2.0 (build 082)
> >
> > Slot Vend Dev  ClassRev Cmd  Stat CL LT HT  Base1    Base2   Int
> > -----------------------------------------------------------------
> > 0:00 1022 3000 06000000 0006 2280 00 00 00 00000000 00000000 00
> > 0:18 100B 0020 02000000 0107 0290 00 3F 00 0000E001 A0000000 10
> > 0:19 100B 0020 02000000 0107 0290 00 3F 00 0000E101 A0001000 11
> > 0:20 100B 0020 02000000 0107 0290 00 3F 00 0000E201 A0002000 05
> >
> >  1 Seconds to automatic boot.   Press Ctrl-P for entering Monitor.
> >
> > F4 . . . ??
> >
> > Default: F?
> >
> > But the machine now seems to be LOCKED?!?!  I've tried two different
> > terminal softwares to see if it was a problem with the term program NOT
> > being able to transmit a F4...no luck...any advice?  It seem I'll have to
> > connect the CF to an OpenBSD machine and redo - any advice on which CF
> > connection to get?
> >
> > Thanks again - Dave
>

-Ken

---
"Lies, Damned Lies, And Micro$oft Press Releases" - Tilda, From TechTV