Atheros AR9460 and Acer Aspire V17 Nitro on FreeBSD 11 not working

14 views
Skip to first unread message

Anders Bolt-Evensen

unread,
Mar 20, 2015, 1:53:08 PM3/20/15
to
Hello!

Recently I had to buy a new computer as my Mac broke down.
I ended up with an Acer Aspire V17 Nitro, which, except for a couple of
problems, is all good.
One of the problems is that wifi does not work. The wifi driver is an
Atheros AR9460.
The problem is that when I attempt to scan for my wireless network,
nothing shows up at all.
On my previous computer, where I used an external Atheros card,
everything worked well.
Could the following line from dmesg be a symptom of my problems?
"ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000"

I'm using FreeBSD 11-CURRENT with sources updated today.

Hope you can help me, and thanks in advance.

A zip file, ath_error.zip should be attached. If not, it is available here:
https://www.dropbox.com/s/jfcjam3m63cmbcv/ath_error.zip?dl=0

Have a nice day, everyone.
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

Adrian Chadd

unread,
Mar 20, 2015, 2:01:23 PM3/20/15
to
On 20 March 2015 at 09:52, Anders Bolt-Evensen <ander...@icloud.com> wrote:
> Hello!
>
> Recently I had to buy a new computer as my Mac broke down.
> I ended up with an Acer Aspire V17 Nitro, which, except for a couple of
> problems, is all good.
> One of the problems is that wifi does not work. The wifi driver is an
> Atheros AR9460.
> The problem is that when I attempt to scan for my wireless network, nothing
> shows up at all.
> On my previous computer, where I used an external Atheros card, everything
> worked well.
> Could the following line from dmesg be a symptom of my problems?
> "ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000"
>
> I'm using FreeBSD 11-CURRENT with sources updated today.


What else does it log?


-adrian

Miguel Clara

unread,
Mar 20, 2015, 2:22:33 PM3/20/15
to
On Fri, Mar 20, 2015 at 6:01 PM, Adrian Chadd <adr...@freebsd.org> wrote:

> On 20 March 2015 at 09:52, Anders Bolt-Evensen <ander...@icloud.com>
> wrote:
> > Hello!
> >
> > Recently I had to buy a new computer as my Mac broke down.
> > I ended up with an Acer Aspire V17 Nitro, which, except for a couple of
> > problems, is all good.
> > One of the problems is that wifi does not work. The wifi driver is an
> > Atheros AR9460.
> > The problem is that when I attempt to scan for my wireless network,
> nothing
> > shows up at all.
> > On my previous computer, where I used an external Atheros card,
> everything
> > worked well.
> > Could the following line from dmesg be a symptom of my problems?
> > "ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000"
> >
> > I'm using FreeBSD 11-CURRENT with sources updated today.
>
>
> What else does it log?
>

I have this same card on a acer s3 (utltrabook)

@adrian this is the one I reported the performance issues but now seems to
be working ok.

For the record this is with --> r280273

commit d7efe7e99e68d52fa754f4e935814c492d818ece
Author: pfg <p...@FreeBSD.org>
Date: Fri Mar 20 01:07:48 2015 +0000

Permit multiple arguments for the nonnull attribute.

This is very useful for non-trivial functions and doesn't
affect existing uses.

MFC after: 5 days

Notes:
svn path=/head/; revision=280273


I'm noticing something wron with "ifconfig scan" too, it listed fine as a
normal user, but that's not really re-scanning...

% ifconfig wlan0 scan
SSID/MESH ID BSSID CHAN RATE S:N INT CAPS
**** *:1c:68 1 54M -93:-96 100 EP RSN HTCAP WPS WPA WME
**** *:13:c0 6 54M -80:-96 100 EP RSN HTCAP WPS WME
**** *:e2:0c 6 54M -83:-96 100 EP RSN HTCAP WME
**** *:f7:8c 6 54M -109:-96 100 EP RSN HTCAP WPS WPA WME
**** *:4a:12 11 54M -91:-96 100 EP RSN HTCAP WPS WPA WME
**** *:13:c4 48 54M -80:-96 100 EP RSN HTCAP WME

Trying with sudo gets in a hanged state...

[user@host:/usr/src ]% sudo ifconfig wlan0 scan
load: 0.17 cmd: ifconfig 11320 [sbwait] 35.72r 0.00u 0.00s 0% 2132k
load: 0.17 cmd: ifconfig 11320 [sbwait] 36.20r 0.00u 0.00s 0% 2132k
load: 0.19 cmd: ifconfig 11320 [sbwait] 187.79r 0.00u 0.00s 0% 2132k
load: 0.19 cmd: ifconfig 11320 [sbwait] 187.94r 0.00u 0.00s 0% 2132k
load: 0.19 cmd: ifconfig 11320 [sbwait] 188.08r 0.00u 0.00s 0% 2132k

^C

but after the ^C as a normal user again and:
ifconfig wlan0 scan
SSID/MESH ID BSSID CHAN RATE S:N INT CAPS
***** *:1c:68 1 54M -94:-96 100 EP RSN HTCAP WPS WPA WME
***** *:13:c0 6 54M -80:-96 100 EP RSN HTCAP WPS WME
***** *:e2:0c 6 54M -83:-96 100 EP RSN HTCAP WME
***** *:f7:8c 6 54M -130:-96 100 EP RSN HTCAP WPS WPA WME
***** *:4a:12 1 54M -91:-96 100 EP RSN HTCAP WPS WPA WME
***** *:13:c4 48 54M -80:-96 100 EP RSN HTCAP WME
***** ... *:99:01 6 54M -96:-96 100 E <------- This is new so it
re-scanned


I see nothing in dmesg

Adrian Chadd

unread,
Mar 20, 2015, 3:02:49 PM3/20/15
to
compile in IEEE80211_DEBUG, then "wlandebug +scan", then do the scan.

I wonder if you're hitting some scan bug where the sheer amount of
traffic going on is causing problems.

Also, seeing RX'ed frames at -130dB is .. oddly wrong for this NIC.
Something odd is going on.


-a

Anders Bolt-Evensen

unread,
Mar 20, 2015, 7:19:51 PM3/20/15
to

IEEE_80211_DEBUG is compiled into the kernel.
When I ran "wlandebug +scan", I got the following output:
net.wlan.0.debug: 0x0 => 0x200000
Then I ran "ifconfig wlan0 up" and then "ifconfig wlan0 scan".
The scan now took a few seconds, but still nothing shows up.
Then I took a look at dmesg -a which was now filled with a loop of the
following messages:

wlan0: ieee80211_start_scan_locked: active scan, duration 2147483647
mindwell 0 maxdwell 0, desired mode auto, append, nojoin, once
wlan0: scan set 1g, 6g, 11g, 7g, 13g, 52a, 56a, 60a, 64a, 36a, 40a, 44a,
48a, 2g, 3g, 4g, 5g, 8g, 9g, 10g, 12g, 149a, 153a, 157a, 161a, 165a,
100a, 104a, 108a, 112a, 116a, 120a, 124a, 128a, 132a, 136a, 140a dwell
min 20ms max 200ms
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 140a -> 1g [active, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 1g -> 6g [active, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 6g -> 11g [active, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 11g -> 7g [active, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 7g -> 13g [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 13g -> 52a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 52a -> 56a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 56a -> 60a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 60a -> 64a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 64a -> 36a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 36a -> 40a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 40a -> 44a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 44a -> 48a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 48a -> 2g [active, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 2g -> 3g [active, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 3g -> 4g [active, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 4g -> 5g [active, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 5g -> 8g [active, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 8g -> 9g [active, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 9g -> 10g [active, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 10g -> 12g [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 12g -> 149a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 149a -> 153a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 153a -> 157a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 157a -> 161a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 161a -> 165a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 165a -> 100a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 100a -> 104a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 104a -> 108a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 108a -> 112a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 112a -> 116a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 116a -> 120a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 120a -> 124a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 124a -> 128a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 128a -> 132a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 132a -> 136a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=0
wlan0: scan_task: chan 136a -> 140a [passive, dwell min 20ms max 200ms]
wlan0: scan_curchan: calling; maxdwell=200
wlan0: scan_task: waiting
wlan0: scan_task: loop start; scandone=1
wlan0: scan_task: out
wlan0: sta_pick_bss: no scan candidate
wlan0: scan_task: done, [ticks 2147275107, dwell min 20 scanend 4294748797]
wlan0: notify scan done
wlan0: ieee80211_scanreq: flags 0x20052 duration 0x7fffffff mindwell 0
maxdwell 0 nssid 1
wlan0: ieee80211_check_scan: active scan, append, nojoin, once
wlan0: sta_pick_bss: no scan candidate

The system kept on printing these messages until I rebooted this machine
back to Windows (in order to write this reply).

Adrian Chadd

unread,
Mar 20, 2015, 7:32:03 PM3/20/15
to
Hm, ok. either interrupts arne't working, or the thing is deaf. :(

can you do that and then in another screen run vmstat -ia | grep ath0 ?

I'd like to see if it's at least posting interrupts.



-a

Kevin Oberman

unread,
Mar 21, 2015, 12:22:54 AM3/21/15
to
On Fri, Mar 20, 2015 at 4:31 PM, Adrian Chadd <adr...@freebsd.org> wrote:

> Hm, ok. either interrupts aren't working, or the thing is deaf. :(
>
> can you do that and then in another screen run vmstat -ia | grep ath0 ?
>
> I'd like to see if it's at least posting interrupts.
>

Could a bad antenna connection (loose plug/broken conductor/pinch to
chassis shorting to ground) explain this? Or would the hardware notice and
report this in all cases?
--
Kevin Oberman, Network Engineer, Retired
E-mail: rkob...@gmail.com

Rui Paulo

unread,
Mar 21, 2015, 12:51:49 AM3/21/15
to

It's worth noting that some laptops have special keys to enable/disable WiFi and sometimes that just kills the radio. Do you have that function key and does toggling it have any effect?

--
Rui Paulo

Anders Bolt-Evensen

unread,
Mar 21, 2015, 4:18:11 AM3/21/15
to
Do you mean to check dmesg -a while doing "vmstat -ia | grep ath0"?
I did run "wlandebug +scan", then ifconfig wlan0 up scan and then
"vmstat -ia | grep ath0".
The only output I got from "vmstat -ia | grep ath0" is:
irq18: ath0 21 0
The second time I ran that last command I got
irq18: ath0 22 0

It is worth mentioning that wifi with this Atheros card works just fine
on Windows (I am using this wlan when typing this answer on Windows).
There is a button that seems to enable airplane mode, but pressing this
button does not seem to change anything as far as FreeBSD is concerned.
Other than that button I can't find any button that enables or disables
wifi.

On 3/21/2015 5:22 AM, Kevin Oberman wrote:
> On Fri, Mar 20, 2015 at 4:31 PM, Adrian Chadd <adr...@freebsd.org> wrote:
>
>> Hm, ok. either interrupts aren't working, or the thing is deaf. :(
>>
>> can you do that and then in another screen run vmstat -ia | grep ath0 ?
>>
>> I'd like to see if it's at least posting interrupts.
>>
> Could a bad antenna connection (loose plug/broken conductor/pinch to
> chassis shorting to ground) explain this? Or would the hardware notice and
> report this in all cases?
> --
> Kevin Oberman, Network Engineer, Retired
> E-mail: rkob...@gmail.com

Miguel Clara

unread,
Mar 21, 2015, 11:08:31 AM3/21/15
to
On Sat, Mar 21, 2015 at 8:17 AM, Anders Bolt-Evensen <ander...@icloud.com>
wrote:

> Do you mean to check dmesg -a while doing "vmstat -ia | grep ath0"?
> I did run "wlandebug +scan", then ifconfig wlan0 up scan and then "vmstat
> -ia | grep ath0".
> The only output I got from "vmstat -ia | grep ath0" is:
> irq18: ath0 21 0
> The second time I ran that last command I got
> irq18: ath0 22 0
>
> It is worth mentioning that wifi with this Atheros card works just fine on
> Windows (I am using this wlan when typing this answer on Windows).
> There is a button that seems to enable airplane mode, but pressing this
> button does not seem to change anything as far as FreeBSD is concerned.
> Other than that button I can't find any button that enables or disables
> wifi.
>
>
> On 3/21/2015 5:22 AM, Kevin Oberman wrote:
>
>> On Fri, Mar 20, 2015 at 4:31 PM, Adrian Chadd <adr...@freebsd.org> wrote:
>>
>> Hm, ok. either interrupts aren't working, or the thing is deaf. :(
>>>
>>> can you do that and then in another screen run vmstat -ia | grep ath0 ?
>>>
>>> I'd like to see if it's at least posting interrupts.
>>>
>>> Could a bad antenna connection (loose plug/broken conductor/pinch to
>> chassis shorting to ground) explain this? Or would the hardware notice and
>> report this in all cases?
>>
>
Guess it depends on the laptop model, on my acer I do have Fn-F3 (antena
icon) playing with with seems to have some effect:
ugen1.4: <vendor 0x0489> at usbus1 (disconnected)
ugen1.4: <vendor 0x0489> at usbus1

But I didn't loose connection.

If relevant:
ugen0.1: <XHCI root HUB 0x8086> at usbus0, cfg=0 md=HOST spd=SUPER
(5.0Gbps) pwr=SAVE (0mA)
ugen1.1: <EHCI root HUB Intel> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=SAVE (0mA)
ugen2.1: <EHCI root HUB Intel> at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=SAVE (0mA)
ugen0.2: <Targus Soft-Touch Cordless Mouse SONiX> at usbus0, cfg=0 md=HOST
spd=FULL (12Mbps) pwr=ON (100mA)
ugen1.2: <product 0x0024 vendor 0x8087> at usbus1, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=SAVE (0mA)
ugen2.2: <product 0x0024 vendor 0x8087> at usbus2, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=SAVE (0mA)
ugen0.3: <1.3M HD WebCam SuYin> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=ON (500mA)
ugen1.3: <USB2.0-CRW Generic> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=ON (500mA)
ugen1.4: <product 0xe04e vendor 0x0489> at usbus1, cfg=0 md=HOST spd=FULL
(12Mbps) pwr=ON (100mA)

Adrian Chadd

unread,
Mar 21, 2015, 11:22:01 AM3/21/15
to
Hi,

It may be rfkill then. It may be that there's a GPIO pin wired up
somewhere that needs updating. Erk.

Someone buy me one of these laptops so I can see what's going on? :)


-a

Miguel Clara

unread,
Mar 21, 2015, 8:34:19 PM3/21/15
to
On Sat, Mar 21, 2015 at 3:21 PM, Adrian Chadd <adr...@freebsd.org> wrote:

> Hi,
>
> It may be rfkill then. It may be that there's a GPIO pin wired up
> somewhere that needs updating. Erk.
>
> Someone buy me one of these laptops so I can see what's going on? :)
>
>

Mine (Acer Acer Aspire S3-391) costs around 650€ I think... The V17 has
"air plain mode" instead of the Wi-FI on/off, but I guess it does the same
thing... it also costs much more because of all the other hardware.

I gladly give you one if I could afford it... :P

Id be happy to join in a group donation if that's even possible.


On another note this module is wifi+bluetooth, I wonder if in my case this
dmesg log showing:


ugen1.4: <vendor 0x0489> at usbus1 (disconnected)
ugen1.4: <vendor 0x0489> at usbus1

Is acctaully refering to turning off(hardware) bluetooth since I keep the
wireless?

Adrian Chadd

unread,
Mar 21, 2015, 8:39:06 PM3/21/15
to
On 21 March 2015 at 17:33, Miguel Clara <miguel...@gmail.com> wrote:
>
>
> On Sat, Mar 21, 2015 at 3:21 PM, Adrian Chadd <adr...@freebsd.org> wrote:
>>
>> Hi,
>>
>> It may be rfkill then. It may be that there's a GPIO pin wired up
>> somewhere that needs updating. Erk.
>>
>> Someone buy me one of these laptops so I can see what's going on? :)
>>
>
> Mine (Acer Acer Aspire S3-391) costs around 650€ I think... The V17 has "air
> plain mode" instead of the Wi-FI on/off, but I guess it does the same
> thing... it also costs much more because of all the other hardware.
>
> I gladly give you one if I could afford it... :P
>
> Id be happy to join in a group donation if that's even possible.
>
>
> On another note this module is wifi+bluetooth, I wonder if in my case this
> dmesg log showing:
> ugen1.4: <vendor 0x0489> at usbus1 (disconnected)
> ugen1.4: <vendor 0x0489> at usbus1
>
> Is acctaully refering to turning off(hardware) bluetooth since I keep the
> wireless?

Yup.

(Reminds me, I should update ath3kfw in the base system already; I
have updated it locally to load in firmware for all the newer NICs.)

It may just be RFKILL. Hm, I wonder how you'd go about fixing that.

What are the contents of sysctl dev.ath.0 ? Can you put it up
somewhere? I think the rfkill setup/gpio pins are there.


-adrian

Miguel Clara

unread,
Mar 21, 2015, 8:45:28 PM3/21/15
to
On Sun, Mar 22, 2015 at 12:38 AM, Adrian Chadd <adr...@freebsd.org> wrote:

> On 21 March 2015 at 17:33, Miguel Clara <miguel...@gmail.com> wrote:
> >
> >
> > On Sat, Mar 21, 2015 at 3:21 PM, Adrian Chadd <adr...@freebsd.org>
> wrote:
> >>
> >> Hi,
> >>
> >> It may be rfkill then. It may be that there's a GPIO pin wired up
> >> somewhere that needs updating. Erk.
> >>
> >> Someone buy me one of these laptops so I can see what's going on? :)
> >>
> >
> > Mine (Acer Acer Aspire S3-391) costs around 650€ I think... The V17 has
> "air
> > plain mode" instead of the Wi-FI on/off, but I guess it does the same
> > thing... it also costs much more because of all the other hardware.
> >
> > I gladly give you one if I could afford it... :P
> >
> > Id be happy to join in a group donation if that's even possible.
> >
> >
> > On another note this module is wifi+bluetooth, I wonder if in my case
> this
> > dmesg log showing:
> > ugen1.4: <vendor 0x0489> at usbus1 (disconnected)
> > ugen1.4: <vendor 0x0489> at usbus1
> >
>
> Is acctaully refering to turning off(hardware) bluetooth since I keep the
> > wireless?
>

ugen1.4: <product 0xe04e vendor 0x0489> at usbus1, cfg=0 md=HOST spd=FULL
(12Mbps) pwr=ON (100mA)

Interesting find:
http://lkml.org/lkml/2013/4/7/162 (guess you're already aware of that... I
was already typing this when I noticed you're reply)


>
> Yup.
>
> (Reminds me, I should update ath3kfw in the base system already; I
> have updated it locally to load in firmware for all the newer NICs.)
>
> It may just be RFKILL. Hm, I wonder how you'd go about fixing that.
>
>

> What are the contents of sysctl dev.ath.0 ? Can you put it up
> somewhere? I think the rfkill setup/gpio pins are there.
>

Full:
http://pastebin.com/raw.php?i=SnMRV7zX

sysctl dev.ath.0 | eg 'rfkill|gpio|setup'

dev.ath.0.rfkill: 1

Adrian Chadd

unread,
Mar 22, 2015, 12:19:37 AM3/22/15
to
Ok, so I'd cycle that rfkill gpio from 1 -> uhm, whatever the max for
that thing is (16?)

Each time:

ifconfig wlan0 down
sysctl dev.ath.0.rfkill=X
ifconfig wlan0 up
ifconfig wlan0 list scan

See if it sees anything.

Miguel Clara

unread,
Mar 22, 2015, 12:56:13 AM3/22/15
to


On March 22, 2015 4:19:23 AM WET, Adrian Chadd <adr...@freebsd.org> wrote:
>Ok, so I'd cycle that rfkill gpio from 1 -> uhm, whatever the max for
>that thing is (16?)
>
>Each time:
>
>ifconfig wlan0 down
>sysctl dev.ath.0.rfkill=X
>ifconfig wlan0 up
>ifconfig wlan0 list scan
>
>See if it sees anything.

It seems to accept only 0 and 1.


I'll have to play with that tomorrow as its almost 5am here.
But it seems to show no scan results with either 0 or 1 (when running just scan... list scan works the first time.. but its not really re-scaning)

>
>
>
>-adrian

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Adrian Chadd

unread,
Mar 22, 2015, 2:22:39 AM3/22/15
to
ok, then hm, where's the gpio pin configured..


-a

Anders Bolt-Evensen

unread,
Mar 23, 2015, 2:04:23 PM3/23/15
to


On 3/22/2015 7:22 AM, Adrian Chadd wrote:
> ok, then hm, where's the gpio pin configured..
>
>
> -a

How do I check where this gpio pin is configured? I guess I have to
enable gpio in the kernel in order to somehow do that?

Adrian Chadd

unread,
Mar 23, 2015, 3:03:17 PM3/23/15
to
No, it's something in the ath driver and ath_hal code.

I'm sorry, I've been busy debugging other things in my limited spare
time; I just haven't had the chance to sit down and look at the rfkill
code. :(


-a

dcj...@gmail.com

unread,
Apr 21, 2018, 4:02:40 PM4/21/18
to
Just to add my experience to this thread.
I am convering an old Asus P5G41T-MLX machine to run FreeBSD 11.1
Initally it would not find the Atheros AR8131-BL1A device.
Updating the BIOS resolved the problem
Reply all
Reply to author
Forward
0 new messages