| View previous topic :: View next topic |
| Author |
Message |
samwichse
Member
Joined: 29 Aug 2025
Posts: 107
|
 Posted: Wed Oct 01, 2025 10:56 pm Post subject: Fedora 9: networking is SLOW |
 |
|
Ok, this is driving me nuts. I've got F9 on my desktop with an older atheros chipset in a wireless PCI card. What I don't get is why surfing is PATHETIC on my machine, but my fiance's WinXP laptop flies. It's definitely a local network problem, as I pinged my wireless router with these results:
| Quote: |
64 bytes from 192.168.1.1: icmp_seq=52 ttl=64 time=309 ms
64 bytes from 192.168.1.1: icmp_seq=53 ttl=64 time=678 ms
64 bytes from 192.168.1.1: icmp_seq=54 ttl=64 time=1583 ms
64 bytes from 192.168.1.1: icmp_seq=55 ttl=64 time=604 ms
64 bytes from 192.168.1.1: icmp_seq=56 ttl=64 time=179 ms
64 bytes from 192.168.1.1: icmp_seq=57 ttl=64 time=87.1 ms
64 bytes from 192.168.1.1: icmp_seq=58 ttl=64 time=267 ms
64 bytes from 192.168.1.1: icmp_seq=59 ttl=64 time=558 ms
64 bytes from 192.168.1.1: icmp_seq=60 ttl=64 time=8.48 ms
64 bytes from 192.168.1.1: icmp_seq=61 ttl=64 time=315 ms
64 bytes from 192.168.1.1: icmp_seq=62 ttl=64 time=45.9 ms
64 bytes from 192.168.1.1: icmp_seq=63 ttl=64 time=598 ms
64 bytes from 192.168.1.1: icmp_seq=64 ttl=64 time=223 ms
64 bytes from 192.168.1.1: icmp_seq=65 ttl=64 time=306 ms
64 bytes from 192.168.1.1: icmp_seq=66 ttl=64 time=845 ms
64 bytes from 192.168.1.1: icmp_seq=67 ttl=64 time=235 ms
64 bytes from 192.168.1.1: icmp_seq=68 ttl=64 time=54.5 ms
64 bytes from 192.168.1.1: icmp_seq=69 ttl=64 time=1159 ms
64 bytes from 192.168.1.1: icmp_seq=70 ttl=64 time=281 ms
64 bytes from 192.168.1.1: icmp_seq=71 ttl=64 time=6.18 ms
64 bytes from 192.168.1.1: icmp_seq=74 ttl=64 time=306 ms
|
It worked once for a while at full speed (ping times < 5ms). Same setup, same computer position, only difference was a reboot. But now, molasses. I tried unloading ath5k and switching to madwifi... it's EXACTLY the same behavior.
The signal strength is "29/70" in iwlist, but I got the < 5ms pings with a strength of about 20/70.
What gives here?
Sam
|
|
| Back to top |
|
tlmiller
Ultimate Member
Joined: 01 May 2025
Posts: 2434
Location: MD, USA
|
| Posted: Wed Oct 01, 2025 11:58 pm Post subject: |
|
|
| do you happen to know the model of atheros chipset? I know when I had a laptop with the 5212 it worked better than just about anything else for me (although never used Fedora on them).
_________________
Debian Squeeze, Arch, Kubuntu mostly. Some Mandriva. Some Windows.
Desktops: shadowdragon, medusa
Laptops: bluedrake, banelord, sandwyrm, aardvark.
|
|
| Back to top |
|
masinick
Linux Guru
Joined: 03 Apr 2025
Posts: 8615
Location: Concord, NH
|
| Posted: Thu Oct 02, 2025 1:37 am Post subject: Here is what I see on rare occasions |
|
|
I have had erratic service with Comcast lately in the WET weather. I am suspecting that it could be my outside box. It is eleven years old and maybe it is now affected by weather. Twice in the past month I have gotten dropped packets and several second response to 56 bit ping queries, which is terrible. A day later, though, things are back to normal.
Noirmal range for me is that I get around a 25 ms ping response to and from yahoo.com when the network is in tip top form, 70-120 ms when it is real busy (but this still yields pretty good throughput. But when I see 400-500 ms delays with spikes up to 2025-5000 ms with no response to one or more pings, I figure the hardware (not necessarily the entire network) is acting up. The correlation in my situation to moisture outside has been strong. If it keeps consistently happening I will make a service call.
You might want to check into this possibility too, or does this happen ALL the time?
I do seem to find wirelsss even more sensitive to this than the Ethernet connection to my router, but when it's bad, it's bad period, so I don't blame the router for causing it, but the router does almost seem to amplify the issue. |
|
| Back to top |
|
samwichse
Member
Joined: 29 Aug 2025
Posts: 107
|
| Posted: Thu Oct 02, 2025 9:49 pm Post subject: |
|
|
| Quote: | | Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01) |
Is what lspci gives me.
And again... the pings are to the router in my apartment, not the internet. I can unplug the DSL and get the same result (and I get nearly identical results pinging the open "linksys" network router elsewhere in my apartment building. That one is a 17/70 quality).
Sam
|
|
| Back to top |
|
masinick
Linux Guru
Joined: 03 Apr 2025
Posts: 8615
Location: Concord, NH
|
| Posted: Fri Oct 03, 2025 12:19 am Post subject: |
|
|
Something is wrong then, either with the wiring to the device, the device itself, or the software/firmware associated with the device. Those are the variables associated with the router.
Time for some detective work to eliminate all except the offending component. |
|
| Back to top |
|
tlmiller
Ultimate Member
Joined: 01 May 2025
Posts: 2434
Location: MD, USA
|
| Posted: Fri Oct 03, 2025 1:43 am Post subject: |
|
|
| Wow, that's the model I had, and it worked GREAT with most distros. In fact was the best mini-pci card I ever used. Definitely something wrong there. I would try blacklisting ath5k. I don't BELIEVE it starts any other modules up, but it's possible it does.
_________________
Debian Squeeze, Arch, Kubuntu mostly. Some Mandriva. Some Windows.
Desktops: shadowdragon, medusa
Laptops: bluedrake, banelord, sandwyrm, aardvark.
|
|
| Back to top |
|
samwichse
Member
Joined: 29 Aug 2025
Posts: 107
|
| Posted: Sat Oct 04, 2025 2:28 pm Post subject: |
|
|
And today, mysteriously:
| Quote: |
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.84 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=6.61 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=3.54 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.79 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.75 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=2.06 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.40 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.68 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=13.6 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.80 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=10.8 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1.74 ms
|
???
I guess I'll be running without a reboot till the next power outage.
Sam
|
|
| Back to top |
|
masinick
Linux Guru
Joined: 03 Apr 2025
Posts: 8615
Location: Concord, NH
|
| Posted: Sun Oct 05, 2025 2:28 am Post subject: |
|
|
| Compared to what you had before, that is rocket fast! You are not likely to find much better latency values than that on a public network! That is awesome! |
|
| Back to top |
|
Germ
Keeper of the BIG STICK
Joined: 30 Apr 2025
Posts: 12452
Location: Planet Earth
|
| Posted: Sun Oct 05, 2025 10:18 am Post subject: |
|
|
If you have the problem again add the following to modprobe.conf, reboot, and give it try.
| Code: | | install ipv6 /bin/true |
_________________
Laptop: Mandriva 2025 PowerPack - 2.6.33.5-0.2mnb
Desktop: Mandriva 2025 Free - kernel 2.6.33.2-1mib
|
|
| Back to top |
|
|
