Hi,
On Tue, 8 Apr 2014 20:40:01 -0700
Adrian Chadd wrote:
> I'm not sure. I'd really like to see what the story is with
> coexistence somehow.
one other note. I start my machine randomly with a kernel built from
sources dated 26.03.14. I never faced this problem with these sources.
Erich
>
>
Hi,
On Tue, 8 Apr 2014 20:40:01 -0700
Adrian Chadd wrote:
> I'm not sure. I'd really like to see what the story is with
> coexistence somehow.
>
I cannot help there as my own access points do not have this feature.
Erich
___
freebsd-wireless@freebsd.
I'm not sure. I'd really like to see what the story is with coexistence somehow.
-a
On 8 April 2014 20:32, Erich Dollansky wrote:
> Hi,
>
> On Tue, 8 Apr 2014 20:07:39 -0700
> Adrian Chadd wrote:
>
>> Coexistence is to deal with the fact that a 40MHz channel may overlap
>> a 20MHz-only AP in
Hi,
On Tue, 8 Apr 2014 20:07:39 -0700
Adrian Chadd wrote:
> Coexistence is to deal with the fact that a 40MHz channel may overlap
> a 20MHz-only AP in the extension channel.
>
> If the AP finds a 20MHz AP in the extension channel (ie, the other
> half of its 40MHz) channel then it'll flip itsel
Coexistence is to deal with the fact that a 40MHz channel may overlap
a 20MHz-only AP in the extension channel.
If the AP finds a 20MHz AP in the extension channel (ie, the other
half of its 40MHz) channel then it'll flip itself to 20MHz. If it
determines it isn't there any more, it'll flip the BS
Hi,
On Tue, 08 Apr 2014 18:18:40 -0700
Sean Bruno wrote:
> On Mon, 2014-03-31 at 07:30 +0800, Erich Dollansky wrote:
> >
> > since I upgraded to r263767, I have the following problem:
> >
> > Wireless does not start all the while. When it does not start, it
> >
> > iwn0: mem 0xf250-0xf25
On Tue, 2014-04-08 at 18:21 -0700, Adrian Chadd wrote:
> Hi,
>
> 20/40 coex is supposed to be some corner of the spec that notices
> whether there's a 20mhz only AP on the extension channel and if so,
> flip everyone over to 20MHz.
>
> Is your DIR825 2GHz channel set to 20mhz or 40mhz?
>
>
> -a
Hi,
20/40 coex is supposed to be some corner of the spec that notices
whether there's a 20mhz only AP on the extension channel and if so,
flip everyone over to 20MHz.
Is your DIR825 2GHz channel set to 20mhz or 40mhz?
-a
On 8 April 2014 18:18, Sean Bruno wrote:
> On Mon, 2014-03-31 at 07:30
On Mon, 2014-03-31 at 07:30 +0800, Erich Dollansky wrote:
> Hi,
>
> since I upgraded to r263767, I have the following problem:
>
> Wireless does not start all the while. When it does not start, it hangs
> then forever. wpa_supplicant's state in top is then '-'. If I start
> wpa_supplicant by hand
hi,
ok. Can you please do a pciconf -lv and attach it here?
Oh. Erm, did you compile a kernel from source? is ATH_ENABLE_11N in your kernel?
Do a 'sysctl dev.ath.0.txagg=1' and then paste the output in dmesg here.
-a
On 8 April 2014 13:38, tzoi516 wrote:
> OK, killed wpa_supplicant and dow
OK, killed wpa_supplicant and downed wlan0 and ath0. After ifconfig ath0
up I received a ton of these:
ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?!
ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128?
received those about 20 times then this:
ath0: ath_edma_recv_proc_queue: Q1: NULL b
This is what I have now, after 5 attempts, and at 41.2% packet loss:
ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping
wlan0: Trying to associate with (hardware ID) (SSID='Base SSID'
freq=1234 MHz
wlan0: [hardware ID] station assoc via MLME
wlan0: [hardware ID] assoc success at aid 3: long
OK. The odd part is after I received those errors I did ifconfig and saw
the network was up. ping google.com with 75% packet loss. Pings now are
around 35.585 ms with 50.0% packet loss.
FreeBSD 10.0-RELEASE system with Intel (iwn0) approximately 80.833 ms
with 0% packet loss.
Mike
On 04/08/14 1
Right. It sounds like it's not associated.
Try wlandebug +assoc and then run wpa_supplicant
-a
On 8 April 2014 12:21, tzoi516 wrote:
> Sorry for another email, the errors are sporadic. I'm trying to find the
> ioctl errors that I get on shutdown.
> These are after logging in:
>
> ath0: ath_ed
Sorry for another email, the errors are sporadic. I'm trying to find the
ioctl errors that I get on shutdown.
These are after logging in:
ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping
dhclient[1001]: send_packet: Invalid argument
dhclient[1001]: send_packet: No buffer space available
a
dhclient[1014]: send_packet: No buffer space available - is one of them,
the other has occurred during portmaster installs.
I have two FreeBSD laptops side-by-side with the same settings to the
same router and the Intel (iwn0, with FreeBSD 10.0-RELEASE) isn't giving
me any errors.
Mike
On 04/08/
Ah. Can you post the buffer errors you're seeing?
-a
On 8 April 2014 11:37, tzoi516 wrote:
> On 04/08/14 14:23, Adrian Chadd wrote:
>> It should work fine on -10 and HEAD. Is it not working fine?
>>
>>
>> -a
>>
>>
>> On 8 April 2014 09:12, tzoi516 wrote:
>>> I have a Toshiba Satellite S55-A51
On 04/08/14 14:23, Adrian Chadd wrote:
> It should work fine on -10 and HEAD. Is it not working fine?
>
>
> -a
>
>
> On 8 April 2014 09:12, tzoi516 wrote:
>> I have a Toshiba Satellite S55-A5169
>> This specific one:
>> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7
It should work fine on -10 and HEAD. Is it not working fine?
-a
On 8 April 2014 09:12, tzoi516 wrote:
> I have a Toshiba Satellite S55-A5169
> This specific one:
> http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html)
>
> I
Hi,
Which hardware is it?
The driver hasn't changed _that_ much since 2013. I'd really like some
help in figuring out which commit(s) broke the driver for you. Would
you mind bisecting the driver from HEAD from 2013 to now and tell me
when the first break was?
I'm happy to fix bugs, but I can on
I have a Toshiba Satellite S55-A5169
This specific one:
http://www.bhphotovideo.com/c/product/1024074-REG/toshiba_pskk6u_08c08t_s55_i7_4700mq_12gb_1tb_windows_8_1_15_6_silver.html)
It has the Atheros combo Wi-Fi/NIC, and the Wi-Fi uses the AR9565. For
it to work I have to change the SATA Controlle
Adrian,
On Thu, Apr 03, 2014 at 04:42:07PM -0700, Adrian Chadd wrote:
A> I've had no time to continue looking at this, I'm sorry.
A>
A> I'm very overworked and I'm not able to be both the net80211, ath and
A> iwn maintainer given how much actual attention they all require.
A> Someone has to ste
Hi,
I've just committed a bunch of things to -HEAD that fix ath(4) hangs
in 11n A-MPDU transmission.
If you're doing 11n AP stuff then please update and re-test.
I'd like someone else to MFC the commits to stable/10 so people there
can benefit from it.
Thanks,
-a
__
23 matches
Mail list logo
