Oh, and you need to print out the tx->rate field using "0x%04x",
rather than %d. The completion value is in hex.
-adrian
On 9 November 2013 22:18, Adrian Chadd wrote:
> Sure, flip on 'wlandebug +rate' (assuming you compiled with IEEE80211_DEBUG)
>
>
> -a
>
> On 9 November 2013 21:08, Brandon Go
Sure, flip on 'wlandebug +rate' (assuming you compiled with IEEE80211_DEBUG)
-a
On 9 November 2013 21:08, Brandon Gooch wrote:
> On Sat, Nov 9, 2013 at 8:46 PM, Adrian Chadd wrote:
>> Hi!
>>
>> On 9 November 2013 18:29, Brandon Gooch wrote:
>>> Turns out that not enabling MRR causes my Intel
On Sat, Nov 9, 2013 at 8:46 PM, Adrian Chadd wrote:
> Hi!
>
> On 9 November 2013 18:29, Brandon Gooch wrote:
>> Turns out that not enabling MRR causes my Intel Ultimate N WiFi Link
>> 5300 to hang after only a few moments of use.
>
> That's .. odd. Ok.
>
>> For now, I've just reverted only those
Hi!
On 9 November 2013 18:29, Brandon Gooch wrote:
> Turns out that not enabling MRR causes my Intel Ultimate N WiFi Link
> 5300 to hang after only a few moments of use.
That's .. odd. Ok.
> For now, I've just reverted only those aspects of r257133, enabling
> MRR and keeping the rate index loo
should be easy to solve - they
> should already have (somewhat) worked with -HEAD.
http://people.freebsd.org/~adrian/iwn/20131109-iwn-works-full-5100-14.diff
I got the 6250 to work - Cedric's patch enabled the wrong calibrations
for the 6050 NIC series.
The whole chip configuration s
followup:
* 6205 works
* 6230 works
* 6200 works
* 2230 works
* 1030 works
* 5100 works
What i haven't yet tested:
* 4965, mostly because I'm scared to
* Whichever NIC Eitan has, as he has it and I don't (2200?)
* (and obviously whatever other NICs exist that I don't have)
What doesn't work:
*
Hi!
Well, I'd start by checking to see what is being transmitted and received.
* is it transmitting beacons?
* is it transmitting anything data-like? eg, is it transmitting
broadcast/multicast frames?
* can it receive frames?
You can use athstats to see what's going on.
wlandebug -i ath(0,1,2..
OK will ignore the stuck beacon stuff :-). Warm reboot is indeed typing
"reboot". That did not resolve this morning's matter. Actually, after I
unplugged the ALIX for a couple of seconds, it came back up... same
problem! Second time, I unplugged it for 30 seconds... problem solved...!
Hardware issu
