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
___
freebsd-current@freebsd.org mailing list
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?
On 21 March 2015 at 21:55, Miguel Clara miguelmcl...@gmail.com wrote:
ok, then hm, where's the gpio pin configured..
-a
On 21 March 2015 at 21:55, Miguel Clara miguelmcl...@gmail.com wrote:
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
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: ath021 0
The second time I ran that last command I got
irq18: ath0
On Sat, Mar 21, 2015 at 8:17 AM, Anders Bolt-Evensen andersb...@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:
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
___
freebsd-current@freebsd.org mailing list
On 21 March 2015 at 17:33, Miguel Clara miguelmcl...@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
On Sun, Mar 22, 2015 at 12:38 AM, Adrian Chadd adr...@freebsd.org wrote:
On 21 March 2015 at 17:33, Miguel Clara miguelmcl...@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
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
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.
-adrian
___
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
IEEE_80211_DEBUG is compiled into the kernel.
When I ran wlandebug +scan, I got the following output:
net.wlan.0.debug: 0x0 = 0x20
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
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
On 20 March 2015 at 15:19, Anders Bolt-Evensen andersb...@icloud.com wrote:
IEEE_80211_DEBUG
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
___
freebsd-current@freebsd.org mailing list
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
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 andersb...@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
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
On 20 March 2015 at
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
On 20 March 2015 at 09:52, Anders Bolt-Evensen andersb...@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
19 matches
Mail list logo
