Date: Thu, 11 Mar 1999 22:52:56 -0600 (CST) From: Craig Johnston <caj@lfn.org> To: freebsd-bugs@freebsd.org Subject: Re: failure to boot after 3.1-RELEASE install Message-ID: <Pine.GSO.3.96.990311223516.22101B-100000@jane.lfn.org> In-Reply-To: <199903112125.XAA03166@ceia.nordier.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> ----- Forwarded message from rnordier ----- > > [Cross-posted: replying to -bugs] > > > I saw the exact same problem mentioned once before on the lists > > and I was wondering if any headway had been made on the problem. > > (reference message id <199810181251.IAA17735@vger.foo.com> ) > > Five months is a long time, where the new boot code is concerned. > FWIW, there's actually no chance that the problem you have has > anything to do with that reported in PR 8368, mentioned above. > > > The system: Tyan Thunder II mobo, 2 x PII @ 266 > > 384 megs SDRAM > > adaptec 7895 onboard > > fast/wide 9 gig WD scsi disk > > > > I am installing 3.1-RELEASE I got off ftp.cdrom.com last night. > > > > The install goes fine, but when I reboot and it comes up off > > the hard disk, at the F1: Freebsd, etc. prompt, when it either > > times out or you press F1, it just beeps. Further keypresses > > elicit further beeps but nothing real ever happens. > > Is there an > > F5 Drive 0 > > line displayed? If so, this is a known BIOS compatibility issue, No, just F1 for my lone partition. > If not, something was almost certainly wrongly configured, somehow, > during the installation. If you can boot from floppy, sending along > the output of the commands Fully dedicating my disk fixed the problem. I did the installation twice with a partition entry to make sure I hadn't screwed something up. Both behaved the same way. FWIW I've done a lot of installs in the past. (I don't know if you meant I likely misconfigured something or if a script did.) > fdisk da0 > disklabel da0 > dd if=/dev/rda0 count=1 > dd if=/dev/rda0s1 count=17 (assuming FreeBSD is slice 1) > > will probably enable us to sort out what went wrong and get you > booting. If anyone is still interested in looking at it I could throw a new disk in the box (I don't want to trash my functional installation) and see if the same thing happens. If this isn't something anybody has an active desire to spend time on beyond getting me to boot, then doing it this way is fine -- FreeBSD is the only OS going on the machine. (or any other machine under my control, mouhaha.) -Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.96.990311223516.22101B-100000>