*BSD News Article 66673


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!comp.vuw.ac.nz!HERMES!frc.niwa.cri.nz!news
From: wdk@frc.niwa.cri.nz (Wayne Knowles)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: ed0: device timeout (help)
Date: 21 Apr 1996 13:09:05 +1200
Organization: NIWA Fisheries Research, Wellington, NZ.
Lines: 26
Sender: wdk@neptune.niwa.cri.nz
Message-ID: <q3iveue632.fsf@neptune.niwa.cri.nz>
References: <4l695g$sup@river.biddeford.com> <4l7fgm$520@uriah.heep.sax.de>
NNTP-Posting-Host: neptune.niwa.cri.nz
In-reply-to: j@uriah.heep.sax.de's message of 19 Apr 1996 07:31:34 GMT
X-Newsreader: Gnus v5.1

In article <4l7fgm$520@uriah.heep.sax.de> j@uriah.heep.sax.de (J Wunsch) writes:

> >I'm getting 'ed0: device timeout' during boot and cant
> >get the (ethernet) netwoking working...
> >
> >The device is
> >ed0 irq 10 port 300 (this is correct and works under dos & NT)
> 
> Maybe the IRQ is incorrect nevertheless; NT might try to configure it
> itself.  (FreeBSD used to do this as well, but doesn't do it any
> longer since it was reported to modify the EEPROM of the cards in some
> cases.)
> 
> The only other alternative is that the wrong interface is active
> (AUI vs. UTP vs. BNC).

Agreed.

You may also want to check the BIOS settings for PCI PnP to make sure
INT 10 is available to the ISA bus.   If all else fails try changing
the cards interrupt and I/O address to ensure there is no conflict.
-- 
  _____    Wayne Knowles                 Title : Systems Manager
 / o   \/  NIWA Fisheries Research       Usenet: wdk@frc.niwa.cri.nz
 \/  v /\  PO. Box 14-901, Kilbirnie
  `---'    Wellington, NEW ZEALAND