Thanks Thomas. I tried reverting it back to the previous kernel and all is ok. Seems like a bug in the 2.4.18 kerenel because no other configs were changed. Has anybody seen this before? What does one do to report a bug like this?
Regards, Mark ============== Hello, Looks like the RX section of the NIC is not working. After pinging another box, does it add the remote box's MAC address in the ARP table ? I had similar problem with RH 7.1, do not remember which card it was, I trashed it. It would respond only if I ping from its console. After replacing the NIC with an intel 82557 based one, the computer is still working fine. RGDS thomas At 01:44 AM 11/23/2002, you wrote: >Hi there, > >I'm running RH7.1 on x386. Just upgraded to 2.4.18-18.7.x using RHN. Reboot >process looked fine. After reboot the machine is not visible on the ethenet >network. I can ping localhost & the eth0 interface on 192.168.1.6 however, >cannot ping any other devices. eth0 seems ok. Watching the boot load process >all looks ok. Can access the web server locally etc - all seems fine >locally. > >I'm using a NetGear FA311 (natsemi) card. PentiumPro200, 4Gb ide >drive...nothing fancy. > >If I ping to another box I can see the leds for both boxes flashing, however >the ping response is "Destination Host Unreachable". >If I ping from another box I can't see the upgraded box's led respond. > >Is there anybody out there who can point me in the right direction? Or >suggest where to start looking? > >Many thanks, >Mark -------------------------------------------- Thomas Joseph Spectrum Software Solutions Inc. 1035 7th North Street, Liverpool, New York 13088 315-457-7700 _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
