Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!cancer.vividnet.com!hunter.premier.net!news.mathworks.com!fu-berlin.de!news-ber1.dfn.de!news-ham1.dfn.de!news-han1.dfn.de!news.gwdg.de!news From: switzel@uni-goettingen.de (Stefan Witzel) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD 2.1.5/EISA/AHA1740 not finding drives Date: 27 Nov 1996 11:13:12 GMT Organization: Universitaet Goettingen Lines: 69 Message-ID: <57h7o8$7dj@gwdu19.gwdg.de> References: <329B228D.167EB0E7@microware.com> <57fght$le8@raven.eva.net> <329B8DFC.41C67EA6@mindspring.com> NNTP-Posting-Host: dv104.zvw.uni-goettingen.de Mime-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII X-Newsreader: WinVN 0.99.8 (x86 32bit) In article <329B8DFC.41C67EA6@mindspring.com>, rlb@mindspring.com says... > >J.C. Archambeau wrote: >> >> Kim Kempf (kim@microware.com) wrote: >> >> : I'm trying to install FreeBSD 2.1.5 on an EISA system with a AHA1740 >> : scsi controller. The system is running DOS/Win95 with no problems from >> : two scsi drives (540mg Maxtor, 1.0GB seagate). I've made a boot floppy >> : to boot the install. It finds the device ahb0, but it can't find any >> : drives. Maybe the controller needs to be configured a certain way in >> : the EISA setup? Anyone have one of these running? >> >> Also, check ECU and see what it says is in the slot. Remember, EISA >> is a PnP bus similiar to MCA and PCI. Perhaps you have it configured >> for a port address, IRQ, DMA and BIOS other than the defaults which is >> causing the conflict. The 174x family has the same defaults as the >> AHA-154x family; port 330h, IRQ 11 (edge triggered), DMA 5 and BIOS >> DC000. >> >> The IRQ mode you also check from ECU. Adaptec also has an updated EISA >> config file for the 174x on their website to force the 174x to go into edge >> triggered IRQ mode which eliminates the problem completely. You only >> really need level triggered IRQs in EISA if you're doing IRQ sharing and >> even then the device driver has to support it plus your motherboard has >> to impliment it correctly in hardware. >> >> To my knowledge, FreeBSD doesn't support EISA level triggered IRQs. The >> only benefit you'll get from EISA is burst DMA at 33 Mb/sec and you won't >> need bounce buffers for DMA transfers into the physical address space above >> 16 Mb. >> -- >> /* >> ** Internet: jca@accessnv.com | Don't blame me, I didn't vote for Clinton. >> ** jca@anv.net | Intel is the word for 'errata.' >> */ >Say FYI, > >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. >Ron >-- >**************************************************************************** >Ron Bolin rlb@mindspring.com, http://www.mindspring.com/~rlb/ >GSU: gs01rlb@panther.gsu.edu matrlbx@indigo4.cs.gsu.edu Home: >770-992-8877 >**************************************************************************** I had no problem using 1742 running FreeBSD 2.1, but when I cannot install 2.1.5 on the same system. So I re-installed 2.1 - no problem. (I wrote this to comp.unix.bsd.freebsd.misc some weeks ago - but got no answer :-( ). -- Stefan Witzel switzel@uni-goettingen.de Universitaet Goettingen / Stabsstelle DV ------------------------- Gosslerstrasse 5-7 fon: +49 551 394160 37073 Goettingen fax: +49 551 399612 Germany -------------------------