Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!newspump.sol.net!www.nntp.primenet.com!nntp.primenet.com!howland.erols.net!EU.net!usenet2.news.uk.psi.net!uknet!usenet1.news.uk.psi.net!uknet!dispatch.news.demon.net!demon!awfulhak.demon.co.uk!awfulhak.demon.co.uk!usenet From: brian@anorak.coverform.lan (Brian Somers) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Q: Install can't find Adaptec drive Date: 3 Oct 1996 13:42:12 GMT Organization: Coverform Ltd. Lines: 24 Message-ID: <530frk$8t@anorak.coverform.lan> References: <3251DCED.C74@a.crl.com> Reply-To: brian@awfulhak.demon.co.uk NNTP-Posting-Host: anorak.coverform.lan X-NNTP-Posting-Host: awfulhak.demon.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Newsreader: knews 0.9.8 In article <3251DCED.C74@a.crl.com>, Allan Young <young@a.crl.com> writes: > I have an Adaptect 154x. I don't have an internal drive, so the adaptect > controls my external boot scsi HD. > > When I installed, I chose the -C (configuration) option, and removed > some conflicts. > > When I went to perform the installation, however, it immediately told me > that no drives were found. This also happens if I don't remove the > conflicts. Do the probes see the controller (aha0) ? If it does, it's probably a termination/cabeling problem - FreeBSD is not very tollerant of bad wiring. If the controller isn't seen, check its IRQ & DMA channel. FreeBSD will default to 11 & 5. On PCI machines, the IRQ (in my experience) tends to get grabbed by the PCI devices. Try changing the IRQ to (say) 15 and booting -c to change aha0 to 15 too. -- Brian <brian@awfulhak.demon.co.uk> Don't _EVER_ lose your sense of humour....