Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!math.ohio-state.edu!news2.uunet.ca!uunet.ca!promis.com!modtor.uucp!modtor.emp.promis.com!pz From: pz@modtor.uucp (Peter Ziobrzynski) Subject: Re: More *BSD installation grief. Message-ID: <pz.749322777@modtor.emp.promis.com> Organization: Modular References: <280eic$eu4@acsc.com> <CE0LC6.AzI@wang.com> <pz.749186750@modtor.emp.promis.com> <JKH.93Sep28230737@whisker.lotus.ie> Date: Wed, 29 Sep 1993 17:12:57 GMT Lines: 26 jkh@whisker.lotus.ie (Jordan K. Hubbard) writes: >In article <pz.749186750@modtor.emp.promis.com> pz@modtor.uucp (Peter Ziobrzynski) writes: > I successfully installed FreeBSD and NetBSD on ESDI WD1007 controller and > Micropolis-1558 drive. > Unfortunately both systems in their original kernels have SCSI disabled > and I had to convert my QIC tapes to floppies to complete installations. > This is going backwards from the 0.1 fixit floppies where all including > SCSI and Ethenet worked fine. I guess to many people pull this project > their own way these days. >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. If this works for you I would love to hear about it. -- Peter Ziobrzynski, pz@modtor.emp.promis.com, Toronto, Ont. Canada