John Menerick wrote:
For those wondering it was a case where when the machine got rebooted it swapped the NIC's around so eth0 became eth1 and vice versa. Loading the modules in the correct order via /etc/modules fixed the problem. This took a resnet appointment and rightly so because I don't think anyone would have thought to ask about that. There's one more for the memory to check on if a situation like this presents itself again.Have you tried to reset the IP stack? Wouldn't hurt and solves most "my internet doesn't work, I tried everything other than reinstall" problems/challenges Spheraice On Thu, 10 Mar 2005 15:48:24 -0500, David O Torrey <tj@xxxxxxx> wrote:I had a similar experience (though with audio drivers, which may be of use to sgelliot). I converted my wife's machine to Linux-only, but it required a hard power-down reset to actually clear up the problems. Best guess is that Windows left the audio system in some wierd state. Works fine since, but hung up the first few times until I powered it down (meaning, unplug it too -- ATX, remember). At any rate, I highly doubt the problem is with Debian itself, and would stop just short of staking my life on the claim that reinstalling won't make a diff of bitterence. Dave On Thu, 2005-03-10 at 13:06, Jacob Fugal wrote:Oops. No, I mean I notice no problems with my windows networking. That is, DNS, subnet, internet, http, and all that works just fine with windows. I can't so much as ping anything in my subnet under Debian right now. Jacob Fugal jpfugal@xxxxxxxWhen you say that it works well enough to post this, it sounds like you're implying that there are problems with networking in Windows too. If this is the case, it sounds like a bad network card/cable. Are you being assigned an IP address in Debian? On Mar 10, 2005, at 12:49 PM, Jacob Fugal wrote:Hello, I have a dual boot Windows XP Pro/Debian "sarge" machine. The network under Debian used to work just fine. Then my wife restarted the machine during Debian bootup because she wanted Windows. (I can only guess that that was the cause of the problem.) Now I can ping my own machine but not the gateway or any other machine under Debian. Windows networking works well enough for me to post this. I tried unloading and loading the network module (using modprobe), ifdown and ifup the interface, I even tried recovery mode. When I run ifconfig, it shows that both eth0 and lo have Tx and Rx errors that increase every time I try to ping anything other than my own machine. Further, when I type ifup eth0, it replies "eth0: link down" when clearly the link is up and running just fine. The only way I can think of fixing this problem is a new install of Debian. Any ideas on what the problem is or how to fix the networking under Debian short of reformat and reinstallation? I'd appreciate it. Jacob Fugal jpfugal@xxxxxxx-- Kyle Schneider Social Sciences - Secondary Education Concentration CAEL Partner MTU Linux Users Group member Resnet Student Consultant 483-9955 Telcom Information Technology 487-2581
Tim