> > > In article <E11XUvI-00018j-00@quartz.newn.cam.ac.uk>,
> > > 	"Patrick Welche" <prlw1@newn.cam.ac.uk> writes:
> > > > How does one start looking for the cause of "ne1: device timeout"?
> > > Check the configuration of the card. It is probably not configured to
> > > use IRQ 10.
> > Hole in one! It was set to "jumperless"...

On Mon, Dec 20, 1999 at 11:50:12AM -0600, fission wrote:
> This is confusing me - I had the exact same problem yesterday when trying
> to install NetBSD on an old 486 with a Kingston NE2000 card.  Why is the
> IRQ in the kernel set to 10?  I know that Linux autodetects the IRQ for
> this card; why doesn't NetBSD do the same, instead of insisting on 10?

If the card is set for P&P, yes, NetBSD will auto detect it. If it is
set for 'jumperless' though, it is hardwired to a particular IRQ/IO
combination. These cards are of course becomming less common now.

The INSTALL + GENERIC kernels will accept an ne2000 card hardwired
at IRQ9/IO280, or IRQ10/IO300.

There is no perfect way to detect every type of hardwired card. Finding
the card at all means it is on IO 280, or 300 - Device timeout almost
always means the IRQ is wrong. (Or, in the BIOS, that IRQ has not been
reserved for ISA devices.)

-- 
David Maxwell, david@vex.net|david@maxwell.net -->
If you don't spend energy getting what you want,
	You'll have to spend it dealing with what you get.
					      - Unknown