[EMAIL PROTECTED] wrote:
>
> Hello,
>
> I was seeing this error message with an eepro100, however
> I was never able to ever get eth0 to come up.
>
> The problem was with an IRQ conflict, which was scrolling
> by in the kernel initialisation - took me a while to spot that :)
>
> Unfortunately, the very primitave bios on my ancient AST
> Manhatten doesn't give much scope for re-assigning any IRQs
> So I took out the video card (its been running on a serial
> console for over a year now anyway) and hey-presto.
>
> eth0 is up and happy and 100Mbs!
>
> Interesting numbers:
>
> kernel version 2.2.14 (although I was using a later version of
> eepro100)
> The system is based on Debain 2.1 rel 1
> Hardware: SMP dual 90MHz AST Manhatten with onboard NCR8xx SCSI
> controller
> eepro100 and ne2000 network cards
Hi Steve,
Yep, interrupt conflicts can be a cause for this type of behaviour.
But I claim my machine is configured 100% OK :-)
The problem *never* showed with 2.0.*, only when we had switched
to 2.2.*.
Haven't checked it in a while: we made a hack just to do a 2nd
ifconfig (exact the same options as the first one). This one
always succeeds. The machine boots OK now, so we don't notice
the problem anymore ..
Greetings,
Rob van Nieuwkerk
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
