On 23 January 2015 at 12:45, Anthony Jenkins wrote:
> Here's a patch that works on my laptop's AR9565 - it just allows GPIO BIT_11
> accesses. No idea why that works; I thought I discovered BIT_8 was the
> rfkill bit. I tried allowing both BIT_11 /and/ BIT_8, but that doesn't work
> (wpa_supplic
). Why would building the kernel
module that way cause that behavior?
Anthony
From: Adrian Chadd
To: Anthony Jenkins
Cc: Anthony Jenkins ; "wirel...@freebsd.org"
Sent: Friday, January 9, 2015 4:00 PM
Subject: Re: Atheros AR9565 detected, not working
H
;wirel...@freebsd.org"
>
> Sent: Friday, January 9, 2015 4:00 PM
>
> Subject: Re: Atheros AR9565 detected, not working
>
> Hm, are you buliding as a module by doing "make" in the module dir? or
> by doing a buildkernel?
>
>
>
> -a
>
>
>
>
&g
quot;wirel...@freebsd.org"
Sent: Friday, January 9, 2015 4:00 PM
Subject: Re: Atheros AR9565 detected, not working
Hm, are you buliding as a module by doing "make" in the module dir? or
by doing a buildkernel?
-a
On 7 January 2015 at 21:10, Anthony Jenkins wrote:
> Re
Hm, are you buliding as a module by doing "make" in the module dir? or
by doing a buildkernel?
-a
On 7 January 2015 at 21:10, Anthony Jenkins wrote:
> Removing just the ar9300_enable_rf_kill() bit works too, but now ath(4)
> endlessly spews
>
> ath0: ath_edma_rxfifo_alloc: Q1: alloc fail
Removing just the ar9300_enable_rf_kill() bit works too, but now ath(4)
endlessly spews
ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=3, nbufs=128?
ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?!
ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128?
ath0: ath_edma_rxbuf
Hi Adrian,
Just letting you know I haven't died in a shootout with the US FBI or anything,
just been working on (and suprisingly fixing) issues with my HP Envy Sleekbook
6 since the holidays. I'll be cleaning up my patches and posting to the wiki
this week (hopefully). Also still sitting on t
On 22 December 2014 at 14:57, Adrian Chadd wrote:
> Ok, let me go see what's going on.
I dislike when I say "let me see what's going on" and then I .. see
what's going on.
So:
* the ar5212 HAL does the right thing - it checks the rfkill setup in
ar5212Reset() and enables it if required
* it al
On 22 December 2014 at 13:59, Anthony Jenkins wrote:
> On 12/22/2014 15:22, Adrian Chadd wrote:
>> On 22 December 2014 at 11:59, Anthony Jenkins wrote:
>>> I'll have to re-add the printf()s, but I'm pretty sure I saw 0x0B (of
>>> course it could have been 0x08 I saw, but neither of those would m
On 12/22/2014 15:22, Adrian Chadd wrote:
> On 22 December 2014 at 11:59, Anthony Jenkins wrote:
>> I'll have to re-add the printf()s, but I'm pretty sure I saw 0x0B (of course
>> it could have been 0x08 I saw, but neither of those would make it through
>> the function - both 0x0B and 0x08 are bl
On 22 December 2014 at 11:59, Anthony Jenkins wrote:
> I'll have to re-add the printf()s, but I'm pretty sure I saw 0x0B (of course
> it could have been 0x08 I saw, but neither of those would make it through the
> function - both 0x0B and 0x08 are blocked).
Please do. I'd like to fix up the HAL
box) to get it
>>>> working in FreeBSD - the keyboard wi-fi LED and hotkey work perfectly
>>>> there.
>>>>
>>>> Thanks,
>>>> Anthony
>>>>
>>>>
>>>> From: Adr
t;>> return;
>>>> }
>>>>
>>>>
>>>> Haven't narrowed down which is responsible for me being able to send this
>>>> email using my AR9565. Also I'm getting flooded with these messages since
>>>> moving ath & wlan out of the kernel...my patch br
he box) to get it
> working in FreeBSD - the keyboard wi-fi LED and hotkey work perfectly there.
>
> Thanks,
> Anthony
>
>
> From: Adrian Chadd
> To: Anthony Jenkins
> Cc: "wirel...@freebsd.org"
> Sent: Sunday, December
box) to get it working
in FreeBSD - the keyboard wi-fi LED and hotkey work perfectly there.
Thanks,
Anthony
From: Adrian Chadd
To: Anthony Jenkins
Cc: "wirel...@freebsd.org"
Sent: Sunday, December 21, 2014 9:39 PM
Subject: Re: Atheros AR9565 detect
Oh, and ath_hal_enable_rfkill() maps to setting the capability bit:
#define ath_hal_enable_rfkill(_ah, _v) \
ath_hal_setcapability(_ah, HAL_CAP_RFSILENT, 1, _v, AH_NULL)
.. so, the AR9300 HAL code is enabling RFKILL in the HAL and then the
call to ar9300_enable_rf_kill() is unconditionally tu
_alloc: Q1: alloc failed: i=1, nbufs=128?
> ath0: ath_edma_rxbuf_alloc: nothing on rxbuf?!
> ath0: ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128?
>
>
> Anthony
> ____
> From: Adrian Chadd
> To: Anthony Jenkins
> Cc: "freebsd-wireless@fre
From: Adrian Chadd
To: Anthony Jenkins
Cc: "freebsd-wireless@freebsd.org"
Sent: Monday, July 29, 2013 10:44 AM
Subject: Re: Atheros AR9565 detected, not working
Cool, thanks.
Please make sure you post patches for all the things you fix. I'd love
to see this k
debug messages or whatever, or can send the
> device (I kinda wanna keep the laptop :-) ).
>
> Anthony
>
>
> - Original Message -
> From: Adrian Chadd
> To: Anthony Jenkins
> Cc: tzoi516 ; "freebsd-wireless@freebsd.org"
>
> Sent: Thursday, April 10, 2
7;wpa_supplicant
-d -d' or ath(4) debug messages or whatever, or can send the device (I kinda
wanna keep the laptop :-) ).
Anthony
- Original Message -
From: Adrian Chadd
To: Anthony Jenkins
Cc: tzoi516 ; "freebsd-wireless@freebsd.org"
Sent: Thursday, April 10, 2014 1
evice).
>>>
>>>
>>> Anthony
>>>
>>>
>>> ____
>>> From: Adrian Chadd
>>> To: tzoi516
>>> Cc: "freebsd-wireless@freebsd.org"
>>> Sent: Wednesday, April 9, 2014 3:02 PM
>&
n have it back (can make do with an
>> external wireless device).
>>
>>
>> Anthony
>>
>>
>>
>> From: Adrian Chadd
>> To: tzoi516
>> Cc: "freebsd-wireless@freebsd.org"
>> Sent: Wednesday, April
ugging if I can have it back (can make do with an
> external wireless device).
>
>
> Anthony
>
>
>
> From: Adrian Chadd
> To: tzoi516
> Cc: "freebsd-wireless@freebsd.org"
> Sent: Wednesday, April 9, 2014 3:02 PM
>
k (can make do with an
> external wireless device).
>
>
> Anthony
>
>
>
> From: Adrian Chadd
> To: tzoi516
> Cc: "freebsd-wireless@freebsd.org"
> Sent: Wednesday, April 9, 2014 3:02 PM
> Subject: Re: Re: Atheros AR9
My computer is a laptop - the link to it is in my first email. I haven't
touched code out of a Windows IDE since the mid-90's, so this might be a
good learning experience for me. Thanks.
On 04/09/14 15:44, Adrian Chadd wrote:
> The driver source is in sys/dev/ath/ and sys/contrib/dev/ath/ath_hal/a
Anthony
From: Adrian Chadd
To: tzoi516
Cc: "freebsd-wireless@freebsd.org"
Sent: Wednesday, April 9, 2014 3:02 PM
Subject: Re: Re: Atheros AR9565
Hi,
The AR9565 is a relatively new chip that hasn't really been thoroughly
tested in FreeBSD. Laptop manufacturers have also gone a
The driver source is in sys/dev/ath/ and sys/contrib/dev/ath/ath_hal/ar9300/
I have all of the linux driver source and the atheros internal driver
source for their AP products but their desktop drivers are .. very
laptop specific and it's hard to get the driver source out of the
relevant group(s).
Hi,
Thanks for all of the help. Where is the driver source code? I'll submit
a PR today.
Thanks,
Mike
On 04/09/14 15:02, Adrian Chadd wrote:
> Hi,
>
> The AR9565 is a relatively new chip that hasn't really been thoroughly
> tested in FreeBSD. Laptop manufacturers have also gone and done some
> r
(.. and my standard offer applies here. I'm much better likely to fix
things if I have one of them. I likely can't buy that specific NIC;
I'd have to have the whole laptop. So if someone wishes to buy me one
of these things, I'll endeavour to improve upon power saving and wifi
support.)
-a
__
Hi,
The AR9565 is a relatively new chip that hasn't really been thoroughly
tested in FreeBSD. Laptop manufacturers have also gone and done some
rather silly things to save cost on the wireless NIC itself and I'm
not sure those patches / work arounds are in -HEAD.
please file a PR with this proble
I'm using the GENERIC kernel. Want me to create a custom kernel?
pciconf info:
hostb0@pci0:0:0:0:class=0x06 card=0xfa401179 chip=0x0c048086
rev=0x06 hdr=0x00
vendor = 'Intel Corporation'
device = 'Haswell DRAM Controller'
class = bridge
subclass = HOST-PCI
p
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
Cool, thanks.
Please make sure you post patches for all the things you fix. I'd love
to see this kind of thing work out of the box. :)
-adrian
On 29 July 2013 07:36, Anthony Jenkins wrote:
> Thanks Adrian,
>
> I've managed to fix a few things on this laptop, the remaining stuff is
> BIOS/ACPI
Thanks Adrian,
I've managed to fix a few things on this laptop, the remaining stuff is
BIOS/ACPI related. acpi_hp(4) isn't working, has something to do with
WMI. Hoping if I fix the ACPI stuff I can have me AR9565 working. I'll
poke around and report back; the RFKill suggestion is a good pl
Hm, maybe rfkill is set?
The AR9565 is supported. I have the reference NICs from Atheros; they
work just fine.
It may be some kind of ACPI setting to enable/disable RFKill so the
radio side is actually enabled.
I'm sorry, I don't have much more than that to offer without having
the laptop here.
44 matches
Mail list logo
