Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!newsfeed.internetmci.com!raven.eva.net!usenet From: "J.C. Archambeau" <jca@accessnv.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD 2.1.5/EISA/AHA1740 not finding drives Date: Tue, 26 Nov 1996 18:25:32 -0800 (PST) Organization: Access Nevada Inc. Lines: 26 Message-ID: <Pine.SUN.3.90.961126180822.23868B-100000@bighorn.accessnv.com> References: <329B228D.167EB0E7@microware.com> <57fght$le8@raven.eva.net> <329B8DFC.41C67EA6@mindspring.com> NNTP-Posting-Host: bighorn.accessnv.com Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <329B8DFC.41C67EA6@mindspring.com> On Tue, 26 Nov 1996, Ron Bolin wrote: > I ran 2.0 on a Adaptec 1742 system, but when I tried to update to 2.1.5 > it would never recognize the 1742 controller. This seems to be broken, > and I am not sure anyone will or has fix it. I posted the problem a few > months ago when 2.1.5 came out. I configured the ahb0 driver (not active > anymore in the boot floppy) but it would not work. So I just took the > drive out of the 48650 EISA machine and put it in a Pent PCI 2940 machine > and upgraded without any problems. Well, you need to submit a problem report. It is quite possible that the 174x driver was broken during the upgrade process. One harsh reality with EISA systems is that there is little support for EISA cards and what little support may end up getting broken during a kernel upgrade. I would personally start looking into the diffs between 2.0 and 2.1.5 at the device driver level. I haven't tried FreeBSD with my EISA system yet, but if the Buslogic driver is solid I shouldn't have any problems with my system which has a Buslogic BT-757C. -- /* ** Internet: jca@accessnv.com | Don't blame me, I didn't vote for Clinton. ** jca@anv.net | Intel is the word for 'errata.' */