Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!gatech!usenet.eel.ufl.edu!news.mathworks.com!fu-berlin.de!zib-berlin.de!news.tu-chemnitz.de!irz401!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: ed0: device timeout (help) Date: 21 Apr 1996 21:20:42 GMT Organization: Private FreeBSD site, Dresden Lines: 25 Message-ID: <4le8ra$f8r@uriah.heep.sax.de> References: <4l695g$sup@river.biddeford.com> <Pine.BSF.3.91.960419105319.12453A-100000@enteract.com> <4ldmsn$16ku@pulp.ucs.ualberta.ca> 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 george@ee.ualberta.ca (Jason George) writes: >I have had _many_ device timeouts from _many_ different network cards. >The only thing these network cards (a selection of Intel, SMC and NE2000 >clones) had in common was that they were at least 18 months old. Some >were close to 5 years old. FreeBSD would give me a timeout error >everytime, but Linux would work fine _with all of them_. No idea on the EtherExpress. As for the `ed' driver: it's documented. This driver used to adjust the card for the IRQ it has been configured in FreeBSD 1 and 2.0. (I think Linux does it still this way.) Since there are known situations where this has been changing the EEPROM of these cards, causing them failing to work under DOS later on, starting with FreeBSD 2.0.5, the `ed' driver doesn't attempt to adjust the card any longer, instead you are supposed to boot with `-c' and adjust the kernel's IRQ setting to the hardware. -- 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. ;-)