Bill Sommerfeld wrote:
> 
> > How does one start looking for the cause of "ne1: device timeout"? This is
> > while trying to install NetBSD on a 486SX2-50 with some sort of clone ne2000.
> > Just prepared the disk, and ifconfig'd, but pinging itself gives the timeout.
> 
> For network interface drivers, this generally means "missed transmit
> complete interrupts", either because the IRQ isn't configured properly
> (mismatch between what the driver thinks and what the card thinks), or
> because the device isn't generating the interrupt (driver bug).

Yup - IRQ set to "jumperless" ie., whatever was left over from its DOS days.

Cheers,

Patrick