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
> Thanks,
>>> Anthony
>>>
>>>
>>> From: Adrian Chadd
>>> To: Anthony Jenkins
>>> Cc: "wirel...@freebsd.org"
>>> Sent: Sunday, December 21, 2014 9:39 PM
>>> Subject: Re: Atheros AR
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
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.
I just got an HP ENVY Sleekbook 6z-1100 laptop hoping it came with a
FreeBSD-supported wireless NIC. It has an Atheros AR9565 and looking at
the logs it _seems_ like it should be working, but I get no network
traffic. I haven't started the Atheros debugging procedure yet, save to
compile in o
22 matches
Mail list logo
