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!howland.erols.net!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD 2.1.5/EISA/AHA1740 not finding drives Date: 27 Nov 1996 10:19:07 GMT Organization: Private BSD site, Dresden Lines: 33 Message-ID: <57h4ir$pqb@uriah.heep.sax.de> References: <329B228D.167EB0E7@microware.com> <57fght$le8@raven.eva.net> <329B8DFC.41C67EA6@mindspring.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Ron Bolin <rlb@mindspring.com> wrote: > > To my knowledge, FreeBSD doesn't support EISA level triggered IRQs. The (side node: it does) > > 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. > 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 What machine? There are known problems with HP netservers and their motherboard AHA1740. > 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 The ahb0 driver _is_ active in the boot floppy. But you don't see it when booting with -c, since the system now has an eisa0 controller, so the EISA devices can be auto-configured. (I used to run an EISA system until very recently, though one with a Bt742A.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)