https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082008-12-16T19:43:03ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #1181: ACX111 panichttps://bugs.dragonflybsd.org/issues/1181?journal_id=56412008-12-16T19:43:03Zelekktretterr
<ul></ul><p>verbose dmesg, and dumps attached.</p>
<p>Petr</p> DragonFlyBSD - Bug #1181: ACX111 panichttps://bugs.dragonflybsd.org/issues/1181?journal_id=56422008-12-16T20:07:00Zswildner
<ul></ul><p>Could you please put up such big pics and dumps on some external site <br />next time? It's really a pain in the ass.</p>
<p>Not to mention that embedded pics look like crap in nntp/mail archive <br />and are pretty much unusable because of that.</p>
<p>Sascha</p> DragonFlyBSD - Bug #1181: ACX111 panichttps://bugs.dragonflybsd.org/issues/1181?journal_id=56432008-12-16T20:12:01Zswildner
<ul></ul><p>See <a class="external" href="http://yoyodyne.ath.cx/tmp/acx_onoe.JPG">http://yoyodyne.ath.cx/tmp/acx_onoe.JPG</a> e.g.</p>
<p>S.</p> DragonFlyBSD - Bug #1181: ACX111 panichttps://bugs.dragonflybsd.org/issues/1181?journal_id=56442008-12-16T20:36:01Zsepherosa
<ul></ul><p>Mmm, I think I have put MODULE_DEPEND(acx, wlan_ratectl_amrr ...) in<br />if_acx.c ... You should not remove AMRR from kernel config if you<br />have acx in the kernel config.<br />As about using different TX rate control algorithm, you could use:<br />ifconfig acx0 ratectl onoe</p>
<p>Best Regards,<br />sephe</p> DragonFlyBSD - Bug #1181: ACX111 panichttps://bugs.dragonflybsd.org/issues/1181?journal_id=56452008-12-16T20:47:01Zsepherosa
<ul></ul><p>On Tue, Dec 16, 2008 at 7:40 PM, Petr Janda<br /><<a class="email" href="mailto:elekktretterr@exemail.com.au">elekktretterr@exemail.com.au</a>> wrote:</p>
<blockquote>
<p>verbose dmesg, and dumps attached.</p>
</blockquote>
<p>Looks like acx0 never hears assoc-resp form AP. Try putting following<br />line in your /boot/loader.conf:<br />hw.acx.enable_pbcc="0"</p>
<p>Best Regards,<br />sephe</p> DragonFlyBSD - Bug #1181: ACX111 panichttps://bugs.dragonflybsd.org/issues/1181?journal_id=56522008-12-17T11:27:02Zelekktretterr
<ul></ul><p>Hi,<br />This makes no difference.</p>
<p>Petr</p> DragonFlyBSD - Bug #1181: ACX111 panichttps://bugs.dragonflybsd.org/issues/1181?journal_id=58382009-01-20T16:04:21Zsepherosa
<ul></ul><p>grab</p> DragonFlyBSD - Bug #1181: ACX111 panichttps://bugs.dragonflybsd.org/issues/1181?journal_id=124382015-01-15T00:43:53Ztuxillo
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/12438/diff?detail_id=2076">diff</a>)</li><li><strong>Category</strong> set to <i>Driver</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Target version</strong> set to <i>4.2</i></li></ul><p>Hi Sephe,</p>
<p>Do you think this is still relevant?</p>
<p>Cheers,<br />Antonio Huete</p> DragonFlyBSD - Bug #1181: ACX111 panichttps://bugs.dragonflybsd.org/issues/1181?journal_id=124492015-01-15T08:04:18Zswildner
<ul></ul><p>Before this gets relevant, someone needs to port the acx(4) to the current 802.11 framework and hook it back into the build.</p> DragonFlyBSD - Bug #1181: ACX111 panichttps://bugs.dragonflybsd.org/issues/1181?journal_id=140162021-05-11T11:00:13Ztuxillo
<ul><li><strong>Target version</strong> changed from <i>4.2</i> to <i>6.0</i></li></ul>