Eric on 14 Oct 2007 22:06:08 -0000 |
Brent: Agreed - It's not the hardware. I [strongly] suspect - it's the driver which is part of the kernel software. That's why, as you point out, it works after bringing it down and then up. At least that's what I figure at this point. After the NIC swap I'll have more feedback :-) Thanks, Eric Brent Saner wrote: > just to offer my (possibly worthless) $.02: > > it is my understanding that if it was HARDWARE related (the actual > NIC(s)), then you would not be able to bring them down and then bring > them back up again . > since, from a cursory read, it seems you are able to do this then i'd > have to guess it's either software or service provider > > On 10/14/07, * Eric* <eric@lucii.org <mailto:eric@lucii.org>> wrote: > > James: > > I had not seen these results before but they, like the other results > I've seen, > strongly indicate the tulip driver. I'll have to figure out which > NIC has the > tulip driver and deep-6 it. Now I'm convinced this has the highest > probability > of being the answer. > > Thanks! > > Eric > > James Barrett wrote: > > What is the model of your NIC? Blacklist the tulip kernel module > and use the > > dmfe module. Some google results ('tulip_stop_rxtx eth') seem to > point to > > that being a problem, particularly these two results: > > > > http://www.suseforums.net/index.php?showtopic=18730 > > > http://www.linuxquestions.org/questions/slackware-14/can-ping-router-but-cant-connect-to-it-nor-internet-451918/ > > > > HTH > > > > --------CUT--------- -- # Eric Lucas # # "Oh, I have slipped the surly bond of earth # And danced the skies on laughter-silvered wings... # -- John Gillespie Magee Jr ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|