Dear people,
Is there other people having problems with recent 2.4 kernels
and the ethernet driver MACE?
I have a PowerMac 9500/180MP here where I'm trying to install
a new kernel (2.4.17-ben0) with SMP support, but I can't get
the ethernet to connect to my pc (also a router to the
Internet).
This ppc has a brand new installation (installed with
boot-floppies 3.0.17).
The ethernet works perfectly with Debian's default kernel or
with my custom-compiled 2.2.20, *BUT* as soon as I boot with a
recent 2.4 kernel, I can't get it to work.
The behavior is a bit strange:
Say I try to ping the pc from the mac. The mac (192.168.1.3)
tries to contact the pc (192.168.1.1), sending arp requests.
The pc sees the requests and correctly sends the replies. The
mac seems to ignore the replies (although I'm not exactly sure
of this) and repeats the arp requests ad infinitum. If I
interrupt ping, it tells that there was a 100% packet loss.
At this point, after arp -n on the mac, the output shows that
the HWaddress field is "(incomplete)", but the pc shows
information about the mac:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
dumont:/home/rbrito> arp -n
Address HWtype HWaddress Flags Mask Iface
192.168.1.3 ether 00:05:02:1C:29:41 C eth0
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
A tcpdump taken from the pc side shows the following (the pc
is 192.168.1.1 and the mac is 192.168.1.3):
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
03:10:38.275837 arp who-has 192.168.1.1 tell 192.168.1.3
03:10:38.275873 arp reply 192.168.1.1 is-at 0:e0:7d:96:28:8f
03:10:39.276178 arp who-has 192.168.1.1 tell 192.168.1.3
03:10:39.276216 arp reply 192.168.1.1 is-at 0:e0:7d:96:28:8f
03:10:40.275844 arp who-has 192.168.1.1 tell 192.168.1.3
03:10:40.275881 arp reply 192.168.1.1 is-at 0:e0:7d:96:28:8f
03:10:41.275810 arp who-has 192.168.1.1 tell 192.168.1.3
03:10:41.275846 arp reply 192.168.1.1 is-at 0:e0:7d:96:28:8f
03:10:42.276176 arp who-has 192.168.1.1 tell 192.168.1.3
03:10:42.276213 arp reply 192.168.1.1 is-at 0:e0:7d:96:28:8f
03:10:43.275818 arp who-has 192.168.1.1 tell 192.168.1.3
03:10:43.275854 arp reply 192.168.1.1 is-at 0:e0:7d:96:28:8f
03:10:44.275781 arp who-has 192.168.1.1 tell 192.168.1.3
03:10:44.275815 arp reply 192.168.1.1 is-at 0:e0:7d:96:28:8f
03:10:45.276124 arp who-has 192.168.1.1 tell 192.168.1.3
03:10:45.276160 arp reply 192.168.1.1 is-at 0:e0:7d:96:28:8f
03:10:46.275786 arp who-has 192.168.1.1 tell 192.168.1.3
03:10:46.275823 arp reply 192.168.1.1 is-at 0:e0:7d:96:28:8f
03:10:47.275755 arp who-has 192.168.1.1 tell 192.168.1.3
03:10:47.275791 arp reply 192.168.1.1 is-at 0:e0:7d:96:28:8f
03:10:48.276128 arp who-has 192.168.1.1 tell 192.168.1.3
03:10:48.276167 arp reply 192.168.1.1 is-at 0:e0:7d:96:28:8f
(...)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
The thing that puzzles me is that some time ago (say, around
kernel 2.4.9 or 2.4.10), I had Linux installed in this
computer and I could use the ethernet correctly with a 2.4
kernel. :-(
Were there any relevant modifications to the MACE code?
Thanks for any help, Roger...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rog�rio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
