2009/1/14 Glenn Burkhardt <gbburkhardt@xxxxxxxxxxx>: > I just upgraded my system to Suse 11.1, and it installed the ath5k driver. I > started having trouble with network access, and found that the response time > to the wireless router in my house was lousy: > > glenn@DepotRd:~> ping 192.168.2.1 > PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. > 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=1233 ms > 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1901 ms > 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1550 ms > > So I pulled the madwifi-0.9.4-1.src.rpm, and re-configured to use the ath_pci > driver. The results were much better: > > glenn@DepotRd:~> ping 192.168.2.1 > PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. > 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.493 ms > 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.485 ms > 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.501 ms > 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=0.518 ms > > The card I have is the Netgear WG311T, which reports with PCI ID > 0x168c:0x0013, and in the log as "Atheros Communications Inc. Atheros AR5001X+ > Wireless Network Adapter (rev 01)". > > I'd be happy to try to help figure out why the response time is so bad with > the ath5k driver, but I'm completely new to this code set. Can you please post the dmesg output from when ath5k loads ? -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
