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 preamble, short slot
time, protection
wlan0: Associated with (hardware ID)
dhclient[3172]: send_packet: No buffer space available
wlan0: WPA: Key negotiation completed with (hardware ID) [PTK=TKIP GTK=TKIP]

Previous attempts had the following errors constantly cycling (having to
type all of it right now):

wlan0: link state changed to UP
dhclient[1170]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
dhclient[1170]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
dhclient[1170]: wlan0 link state up -> down
wlan0: link state changed to DOWN
wlan0: [hardware ID] station assoc via MLME
wlan0: [hardware ID] assoc success at aid 3: long preamble, short slot
time, protection
wlan0: link state changed to UP


On 04/08/14 16:03, Adrian Chadd wrote:
> Right. It sounds like it's not associated.
>
> Try wlandebug +assoc and then run wpa_supplicant
>
>
> -a
>
>
> On 8 April 2014 12:21, tzoi516 <tzoi...@gmail.com> 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_edma_recv_tasklet: sc_inreset_cnt > 0; skipping
>> dhclient[1001]: send_packet: Invalid argument
>> dhclient[1001]: send_packet: No buffer space available
>> ath0: ath_edma_recv_tasklet: sc_inreset_cnt > 0; skipping
>> dhclient[1001]: send_packet: No buffer space available
>> dhclient[1001]: send_packet: Invalid argument
>> dhclient[1001]: send_packet: Network is down
>>
>> Mike
>>
>> On 04/08/14 14:38, Adrian Chadd wrote:
>>> Ah. Can you post the buffer errors you're seeing?
>>>
>>>
>>> -a
>>>
>>>
>>> On 8 April 2014 11:37, tzoi516 <tzoi...@gmail.com> 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 <tzoi...@gmail.com> 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)
>>>>>>
>>>>>> 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 Controller Mode in the BIOS from
>>>>>> "AHCI" to "Compatibility". I don't know if this information helps, and
>>>>>> it's the only AHCI setting I can tweak.
>>>>>>
>>>>>> Mike
>>>>>> _______________________________________________
>>>>>> freebsd-wireless@freebsd.org mailing list
>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>>>>>> To unsubscribe, send any mail to 
>>>>>> "freebsd-wireless-unsubscr...@freebsd.org"
>>>> With SATA controller mode set to Compatibility then it works, but a
>>>> little wonky at startup - sometimes I'll have to run wpa_supplicant -i
>>>> wlan0 -c /etc/wpa_supplicant.conf. Infrequently a buffer error appears.
>>>> With SATA controller mode set to AHCI then I can ifconfig wlan0 list
>>>> scan and see available networks but I can't connect to any except for
>>>> unprotected networks.
>>>>
>>>> I'm currently running FreeBSD 10.0-STABLE
>>>>
>>>> Mike

_______________________________________________
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to