Here is my original post: http://www.linuxquestions.org/questi...hreadid=173082

Here is what is going on now.

I installed Fedora to see if a newer kernel would help (since everytime I tried to compile a kernel with RH8, it didn't work). I just have two pc's hooked into a 4 port switch which is part of a router. One is a compaq armada m700 running windows 2000, and the other is a celeron 2.0, with a soyo p4is2 mb that dual boots fedora and windows. When I boot to windows with my desktop I can ping everything just fine (192.168.2.1 router and 192.168.2.2 laptop). When I reboot and load Fedora, I can only ping my local interface. All nic's, ports on the hub, and cables are known good.

I have installed linux before successfully and had a mail/web/ftp server running.

Any help you can provide will be great.

Thanks,

Jon

More information need

paste the output of "ifconfig eth0" and "route -n"
what is the error message that you get when you ping something
have you tired running a sniffer on another computer to see if the packet even gets to the wire or if its a network driver issue.

Here is my ifconfig and route -n commands.

eth0 Link encap:Ethernet HWaddr 00:48:54:67:16:E6
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x7000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2071 errors:0 dropped:0 overruns:0 frame:0
TX packets:2071 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1767326 (1.6 Mb) TX bytes:1767326 (1.6 Mb)

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0

I read through you last post and the things that you have been through.
It seems to be that if you have switched out the network cards and it is still doing the same thing then it would mean that either its some other hardware problem or its a problem with something else on the network.

You say that you have switched out the network card did you put it back into the same pci slot or a different one.
If it was the same then try putting it into a different one.
I may be wrong but from what i gather its a AMD K6-2 system. If it is then make sure that the network card is NOT next to the video card Its given me similar problems in the past.

I need to see a network packet capture (ethereal or something like it) from you network like ping from you windows hosts and log the packages and then ping from linux and record that too it could provide you with what you need as to why its not talking.

zatriz,

You are awesome. I put the card a few slots down and it started working. Wonder why that is? Oh well, I'll figure that part out later, I'm too excited to think about it now. Thanks my friend.

Jon

The pci slots right next to the video card tends to want to share the same irq when it gets moved to a different slot it works fine. The problem seems to be limited to Amd boards with the K5, K6, K6-2 , K6-3 chipsets but other boards seem to suffer from the same problem occasionally.

Well good luck with everything else.

Actually, one of my working computers was a k6-2, this was a soyo with a celeron 2.0. Just fyi

Thanks,

Jon