Bug #1181
open
Added by elekktretterr almost 16 years ago.
Updated over 3 years ago.
Description
Sorry about the picture size!
I tried to switch from my Atheros(because of the dropouts ive been having)
card back to my ACX111 card. With AMRR enabled, the card is unable to stay
connected to my network(connects and disconnects and keeps retrying). But
when I removed AMRR from the kernel, I get this panic(picture attached).
Verbose dmesg coming soon.
Petr
Files
verbose dmesg, and dumps attached.
Petr
Could you please put up such big pics and dumps on some external site
next time? It's really a pain in the ass.
Not to mention that embedded pics look like crap in nntp/mail archive
and are pretty much unusable because of that.
Sascha
Mmm, I think I have put MODULE_DEPEND(acx, wlan_ratectl_amrr ...) in
if_acx.c ... You should not remove AMRR from kernel config if you
have acx in the kernel config.
As about using different TX rate control algorithm, you could use:
ifconfig acx0 ratectl onoe
Best Regards,
sephe
On Tue, Dec 16, 2008 at 7:40 PM, Petr Janda
<elekktretterr@exemail.com.au> wrote:
verbose dmesg, and dumps attached.
Looks like acx0 never hears assoc-resp form AP. Try putting following
line in your /boot/loader.conf:
hw.acx.enable_pbcc="0"
Best Regards,
sephe
Hi,
This makes no difference.
Petr
- Description updated (diff)
- Category set to Driver
- Status changed from New to In Progress
- Target version set to 4.2
Hi Sephe,
Do you think this is still relevant?
Cheers,
Antonio Huete
Before this gets relevant, someone needs to port the acx(4) to the current 802.11 framework and hook it back into the build.
- Target version changed from 4.2 to 6.0
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
