Carrott wrote:
<snip>
> What does the line(s) above say? My kernel log shows a probe for the net
> card (NE2000) and then reports the IRQ and Address of the card. Don't know
> what make or type of card you have.
>
> Are you autoprobing as this can cause problems? I use IRQ 10 and Address
> 0x300 and works every time.
>
> May be a dumb question but has this card ever worked under Linux or
> Windoze? If you know what the setup of the card is, manually probe these
> settings.
>
> Test the card in another machine to prove it (even if it's Win95), you may
> have a faulty card (even if it's new!!!).
</snip>
At work today I was welding something for the shop and I remembered
where this error came up at before, it was when I was running the
same Intel EExpress on my faster P166 and the docs said it stalls
on faster boxes so I swapped it with my 3c509 and put the Intel in
the other slower 586/120mz box, all was fine.
The difference now as I see it is the 2.0.36 (Red Hat 5.2) kernel
is *just* faster enough on the slower machine to stall this card.
This same "machine/nic" works fine with the earlier Red Hat 5.1, I
also noticed an additional driver loads for the Intel (3 total)
EExpress in 5.2 so I figured it had to the fix, guess not.
--
"If your life was nothing but sunshine, you'd just be a desert."
_____________ Linux/Unix "Future Guru" Anthem _________________
Bill Schoolcraft
http://home.att.net/~wiliweld
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
