Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!uwm.edu!news.moneng.mei.com!howland.reston.ans.net!swrinde!sgiblab!gatekeeper.us.oracle.com!barrnet.net!Reason.cdrom.com!news.cdrom.com!jkh From: jkh@freefall.cdrom.com (Jordan K. Hubbard) Newsgroups: comp.os.386bsd.bugs Subject: Re: FreeBSD-2.0-ALPHA: problems Date: 15 Nov 1994 08:05:15 GMT Organization: Walnut Creek CDROM Lines: 26 Message-ID: <JKH.94Nov15000516@freefall.cdrom.com> References: <1994Nov14.220849.425@robkaos.ping.de> NNTP-Posting-Host: freefall.cdrom.com In-reply-to: robsch@robkaos.ping.de's message of Mon, 14 Nov 1994 22:08:49 GMT In article <1994Nov14.220849.425@robkaos.ping.de> robsch@robkaos.ping.de (Robert Schien) writes: After booting the boot floppy of FreeBSD-2.0-ALPHA, installation was no problem, but as I tried to boot from the SyQuest, I got endless reboots. I was able to boot, when the boot diskette is inserted and I entered 'hd(1,a)/kernel' at the boot prompt. Could you tell us a little more about this? It's interesting.. I don't think anyone here has tried booting off a syquest, certainly! You say if you reference it directly from the floppy, it works, but if you try booting from the bootblocks on the syquest, it's reboot city? Did you select "Write" from the fdisk menu as part of your setup? There is a bug that bootblocks aren't written unless you do that explicitly, and we'll fix this in the next revision of the boot floppies (soon), but for now... Next problem concerns the CD-ROM: Entering mount_cd9660 /dev/cd0d /cdrom causes the message 'Device not configured', although the CD-drive is accessed (I hear and see it:-)) and Substitute /dev/cd0a for /dev/cd0d. Jordan