Horribly slow internet; fine under windows
This is a discussion about Horribly slow internet; fine under windows in the Linux Networking category; Hi. This is my first post here. So far I've been able to figure out most things I've needed concerning Linux, but this one has me stumped. When I start up a browser (in the most recent case Konqueror, but it happens for every one I've tried), it will download for the first few tenths of a second at an alright pace, ...
Hi. This is my first post here. So far I've been able to figure out most things I've needed concerning Linux, but this one has me stumped. When I start up a browser (in the most recent case Konqueror, but it happens for every one I've tried), it will download for the first few tenths of a second at an alright pace, but then I see the speed go down exponentially (in bits/s) until it says that the connection to the host is broken. This happens to all web pages I've tried. Very small pages load fine, but anything with an image on it will slow down until it stops. Right now I'm running Slackware 9.1 with a NetGear FA311 card behind a personal router and then a hub. The same thing happens in my dorm room at school, which is switched. The problem also occurred with Mandrake and Knoppix. wget is also slow, as is ftp. Here's what I got with ifconfig after loading Google and trying to do a search for linux forums, which stopped less than halfway through loading:
eth0 Link encap:Ethernet HWaddr 00:09:5B:20:C7:FD
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:13 dropped:0 overruns:0 frame:26
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:10076 (9.8 Kb) TX bytes:4679 (4.5 Kb)
Interrupt:5 Base address:0xa000
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 TX bytes:0 (0.0
I'm thinking that it might have something to do with RX packet errors, but have no idea how I could fix that. Like I said, everything works fine under Windows (it's a dual boot machine). I'd really like to use Linux as my primary operating system, but this problem is a major hurdle. Thanks for any help you can give me.
eth0 Link encap:Ethernet HWaddr 00:09:5B:20:C7:FD
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29 errors:13 dropped:0 overruns:0 frame:26
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:10076 (9.8 Kb) TX bytes:4679 (4.5 Kb)
Interrupt:5 Base address:0xa000
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 TX bytes:0 (0.0
I'm thinking that it might have something to do with RX packet errors, but have no idea how I could fix that. Like I said, everything works fine under Windows (it's a dual boot machine). I'd really like to use Linux as my primary operating system, but this problem is a major hurdle. Thanks for any help you can give me.
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Mar 14
Mar 14
0
3 minutes
Responses to this topic
Don't know about Slackware much, but try configuring the NIC using the natsemi module.
Look at the following post;
http://www.linuxquestions.org/questions/archive/14/2003/02/1/43437
From the thread;
Quote:From what I have been able to locate quickly, the fa311 card should use the natsemi driver. Perhaps another module has attempted to load and locked the resources, or maybe from netconfig probes. Power off and retry without running netconfig. Use "lsmod" to view the loaded modules. After you receive the error message, use the command "dmesg" and look at the end of the listing and see if any errors are reported that might point to where the problem is. If all else fails, then shutdown X to just a console unload all modules and then attempt to load the natsemi module. If it still fails with the same message, then perhaps the kernel is attempting to do something with it. Review the dmesg output just after booting to console mode to see what the kernel reports.
Look at the following post;
http://www.linuxquestions.org/questions/archive/14/2003/02/1/43437
From the thread;
Quote:From what I have been able to locate quickly, the fa311 card should use the natsemi driver. Perhaps another module has attempted to load and locked the resources, or maybe from netconfig probes. Power off and retry without running netconfig. Use "lsmod" to view the loaded modules. After you receive the error message, use the command "dmesg" and look at the end of the listing and see if any errors are reported that might point to where the problem is. If all else fails, then shutdown X to just a console unload all modules and then attempt to load the natsemi module. If it still fails with the same message, then perhaps the kernel is attempting to do something with it. Review the dmesg output just after booting to console mode to see what the kernel reports.
