mactel-support team mailing list archive

["Luis R. Rodriguez" <mcgrof@xxxxxxxxx>]

On Mon, Jun 1, 2009 at 12:00 PM, Alex <alexanderlane@xxxxxxxxx> wrote:
> Sorry, that could have been more clear.
>
> My first instinct was to build compat-wireless (from linuxwireless.org) in
> attempt to resolve the aforementioned problem. Unfortunately,
> compat-wireless itself did not help at all, so I uninstalled it and then
> installed lbm, which did indeed fix it.

Then in that case lbm hasn't yet been updated to reflect new
compat-wireless changes.

  Luis

-- 
MacBook Pro 3.1 Very Weak Wireless Performance Using Jaunty (Intrepid Works Fine)
https://bugs.launchpad.net/bugs/362985
You received this bug notification because you are a member of Mactel
Support, which is the registrant for Mactel Support.

Status in Mactel Support: New
Status in “linux” source package in Ubuntu: New

Bug description:
Hi,

I updated to jaunty yesterday and want to report on wifi problems. running newer atheros chips with ubuntu was always difficult but IMO intrepid and ath9k solved these kind of issues more or less. surprisingly they are back in jaunty (rc1) now. my connection is very weak which especially affects surfing, in fact you always have to reload a page several times to get it working. the connection always stops for some seconds (!) before it works again, see ping example below. maybe this corresponds to the comment on another bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/342802/comments/5 (however in my case it only disconnects very rarely).

ping example:
64 bytes from www.heise.de (193.99.144.85): icmp_seq=175 ttl=250 time=42.7 ms
64 bytes from www.heise.de (193.99.144.85): icmp_seq=176 ttl=250 time=39.2 ms
64 bytes from www.heise.de (193.99.144.85): icmp_seq=177 ttl=250 time=42.5 ms
64 bytes from www.heise.de (193.99.144.85): icmp_seq=221 ttl=250 time=5413 ms
64 bytes from www.heise.de (193.99.144.85): icmp_seq=222 ttl=250 time=4414 ms
64 bytes from www.heise.de (193.99.144.85): icmp_seq=223 ttl=250 time=3407 ms
64 bytes from www.heise.de (193.99.144.85): icmp_seq=224 ttl=250 time=2407 ms
64 bytes from www.heise.de (193.99.144.85): icmp_seq=225 ttl=250 time=1409 ms
64 bytes from www.heise.de (193.99.144.85): icmp_seq=226 ttl=250 time=403 ms
64 bytes from www.heise.de (193.99.144.85): icmp_seq=227 ttl=250 time=42.5 ms
64 bytes from www.heise.de (193.99.144.85): icmp_seq=228 ttl=250 time=41.6 ms
64 bytes from www.heise.de (193.99.144.85): icmp_seq=229 ttl=250 time=42.0 ms

i was using ndiswrapper in 8.04 but ath9k since 8.10.

modprobe wl results in:
...@simbox:~$ sudo modprobe wl
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/nvidia-kernel-nkc, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/mactel-support-srosa-sound-fix, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/oss-compat, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/mactel-support-fnmode-fix, it will be ignored in a future release.

lscpi:
0b:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)

dmesg:
...
[   16.911078] ath9k: 0.1
[   16.911120] ath9k 0000:0b:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   16.911131] ath9k 0000:0b:00.0: setting latency timer to 64
[   17.038580] phy0: Selected rate control algorithm 'ath9k_rate_control'
[   17.077654] Registered led device: ath9k-phy0:radio
[   17.077670] Registered led device: ath9k-phy0:assoc
[   17.077682] Registered led device: ath9k-phy0:tx
[   17.077696] Registered led device: ath9k-phy0:rx
[   17.078037] phy0: Atheros 5416: mem=0xffffc200043c0000, irq=16
...


anyway, thanks for jaunty and for putting so much work in to linux making it a great alternative.