usually the SIO errors happen when you try to do address/other config
stuff on an improperly initialized piece of hardware or if the actions
trying to be performed are illegal (including not possible)... could be a
bad NIC (mind you I didn't read the whole original post) or just a bad config
file or files <shrug>
On Mon, 18 Dec 2000, Micah Yoder wrote:
> > Funky NIC? I would swap the cards to try and isolate the problem. If the
>
> Aaargh. Now that you mention that, I bet you're right. I'll try that
> at some point... being a hardware clutz I'm not up to it right now...
>
> I just thought of a couple other things to try...
>
> 1. putting a hub between the two computers. Perhaps eclipse, when
> either the card is initialized or when eth0 is brought up, sends some
> kind of arp ping (OK, I'm not an ethernet guru so I don't know how that
> all works) to see if something's there. If not, it does weird things.
> An ethernet hub between them MIGHT take the place of that other card.
>
> 2. removing the 3c905 kernel module and reinserting it. Perhaps it
> would get straightened out if the module was COMPLETELY reset, instead
> of just an ifdown/ifup.
>
> I'll try both of those this week, then probably swap the cards if no
> luck there.
>
> Thanks for the reply.
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
--
-Statux
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
