ethernet not working.
So, here is what I see: I can send packets. I can get interrupts on recieve packets. What I don't get is the packets into the nic itself. The packets on send are received, and responded to, by a dhcp server.
this sounds like phy to me. any ideas?
This is the bad output: Using /lib/modules/2.6.14-i386/kernel/drivers/net/via-rhine.ko via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker PCI: Found IRQ 11 for device 0000:00:12.0 eth0: VIA Rhine II at 0xfec00000, 00:40:63:d3:4f:61, IRQ 11. eth0: MII PHY found at address 1, status 0x7869 advertising 05e1 Link 45e1.
This is the good:
Using /lib/modules/2.6.14-i386/kernel/drivers/netvia-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker PCI: Found IRQ 11 for device 0000:00:12.0
eth0: MII PHY found at address 1, status 0x7869 advertising 05e1 Link 45e1.
ron
So, here is what I see: I can send packets. I can get interrupts on recieve packets. What I don't get is the packets into the nic itself.
Are you _really_ sure you get interrupts on receive? I had a similar problem when the PCI INT routing was not correct.
-- Richard A. Smith
Richard Smith wrote:
So, here is what I see: I can send packets. I can get interrupts on recieve packets. What I don't get is the packets into the nic itself.
Are you _really_ sure you get interrupts on receive? I had a similar problem when the PCI INT routing was not correct.
I am really sure I am not getting that interrupt. Her'es the weird part:
/ # cat /proc/interrupts CPU0 0: 790617 XT-PIC timer 2: 0 XT-PIC cascade 4: 4592 XT-PIC serial 11: 11599 XT-PIC eth0 14: 175 XT-PIC ide0 NMI: 0 LOC: 0 ERR: 0 MIS: 0
lotsa interrupts (apparently) on 11.
this is weird.
ron
Richard Smith wrote:
So, here is what I see: I can send packets. I can get interrupts on recieve packets. What I don't get is the packets into the nic itself.
Are you _really_ sure you get interrupts on receive? I had a similar problem when the PCI INT routing was not correct.
oh, I forgot: why I might be getting ints.
The reject packet count on eth0 is through the roof. For ever packet sent to it, it increments the reject count.
This sounds like badly setup enet hardware to me.
ron