>>>>> "Brian" == Brian Pomerantz <[EMAIL PROTECTED]>
>>>>> wrote the following on Sun, 7 Nov 1999 11:04:09 -0800
<snip>
Brian> I haven't had any problems compiling the tulip module on my
Brian> miata in a 2.2.10 kernel. Though, I use the de4x5 driver
Brian> instead of the tulip. I found it to be more reliable for
Brian> the internal ethernet controller.
The de4x5 driver sounded promising. I neglected to think about that
because redhat had given me the tulip driver in conf.modules during
the install. Alas, things seem to be worse with the de4x5 -- I get
no activity at all and a "network unreachable" message even when I
ping dagmar, which is the alpha. I have the source for a slightly
later de4x5, but the changelog doesn't sound promising.
>> Now the original problem. I tried to setup networking as
>> closely as possible to what I have on an Intel RH6.1 box (which
>> also uses a tulip card) to get a very simple home network. The
>> Intel box seems to get along well with a win95 box that I use to
>> pay the bills. I can see activity at the hub from the alpha,
>> which is apparently arp who-has requests, but nothing else in
>> the network hears anything nor can the alpha hear anyone
>> else. Pinging the host under its network name works ok. It's
>> quite possible that I have overlooked something, and I'd very
>> much appreciate a hint if that's the case.
>>
Brian> Did you try a different cable and/or port on the hub?
Yes and yes.
Brian> BAPper
Thanks for looking at it, Brian.
