Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!news.uta.edu!cse.uta.edu!turbo From: turbo@cse.uta.edu (Chris Turbeville) Subject: Re: More *BSD installation grief. Message-ID: <1993Oct13.055757.10094@news.uta.edu> Sender: news@news.uta.edu (USENET News System) Nntp-Posting-Host: cse.uta.edu Organization: Computer Science Engineering at the University of Texas at Arlington References: <JKH.93Sep28230737@whisker.lotus.ie> <pz.749322777@modtor.emp.promis.com> <29f8ts$33s@gwynedd.frmug.fr.net> Date: Wed, 13 Oct 1993 05:57:57 GMT Lines: 38 In article <29f8ts$33s@gwynedd.frmug.fr.net> fcb@gwynedd.frmug.fr.net (Francois Berjon) writes: >pz@modtor.uucp (Peter Ziobrzynski) writes: >|> jkh@whisker.lotus.ie (Jordan K. Hubbard) writes: >|> >Excuse me?? What do you mean by "SCSI disabled"? FreeBSD supports >|> >two different boot sets, one for Adaptec SCSI controllers and one for >|> >Ultrastore/Bustek. That's hardly "SCSI disabled" to me! And our >|> >ethernet drivers are bundled in as well. >|> >|> When you install FreeBSD with kcopy-ah-floppy images and try to >|> access device nodes for SCSI you get message: device not configured. >|> I use Adaptec 1540, and QIC tape drive on ID 2 - worked fine with old >|> 386bsd kernels. > >It did indeed (and still does). > >|> If this works for you I would love to hear about it. > >As a matter of fact, it does. I also have an Adaptec 1540, and a QIC-150 tape drive >(on ID 4). I installed FreeBSD from a tape using the kcopy-ah-floppy image with no >problems whatsoever. The streamer was correctly recognized, and everything went >fine... Incidentally, my disk is a SCSI too, and is hooked to the same 1540 as >the streamer. A friend of mine also had no problem at all. > >I think your problem must come from some configuration peculiarity. >Just my $0.02... > I think there is something wrong because I have this same problem timeouts and device not configured. This is on a bl747s and a mxt1240s. I think it must have to do with controller disk pairs as another fellow reported this to me and said changing the drive fixed it. I have to agree that it obviously works with many controller/disk pairs but some have problems. Perhaps a corrupted dist at cdrom or did you get yours there? Scsi disabled is too strong a term but there are a few bugs. (In either the software or the hardware). I guess we have $0.04 now I smell some sort of pyrimid scheam here:). -Chris