Re: Realtek wireless card support

[Vincent Hoffman-Kazlauskas]

Hi,
Odd its not working, from what you pasted below
rtwn0@pci0:7:0:0:class=0x028000 card=0x1629103c chip=0x817610ec
rev=0x01 hdr=0x00

Its showing the driver as attached.
whats the output of
grep rtwn /var/run/dmesg.boot

Also i'm bring the freebsd-wireless mailing list back in as more eyes
are better for solving this kind of stuff and also I can be a bit slow
at replying (work, small children, cats, etc etc)

Vince

On 19/02/2017 02:51, Kevin McErlean wrote:
> here  is the read out from pciconf -lv (just for Ethernet and wireless
> 
> none1@pci0:2:0:0:class=0xff card=0x3577103c chip=0x520910ec
> rev=0x01 hdr=0x00
> vendor = 'Realtek Semiconductor Co., Ltd.'
> device = 'RTS5209 PCI Express Card Reader'
> re0@pci0:6:0:0:class=0x02 card=0x3577103c chip=0x813610ec
> rev=0x05 hdr=0x00
> vendor = 'Realtek Semiconductor Co., Ltd.'
> device = 'RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller'
> class  = network
> subclass   = ethernet
> rtwn0@pci0:7:0:0:class=0x028000 card=0x1629103c chip=0x817610ec
> rev=0x01 hdr=0x00
> vendor = 'Realtek Semiconductor Co., Ltd.'
> device = 'RTL8188CE 802.11b/g/n WiFi Adapter'
> class  = network
> 
> 
> On Tue, Feb 14, 2017 at 3:45 AM, Vincent Hoffman-Kazlauskas
> mailto:vi...@unsane.co.uk>> wrote:
> 
> 
> 
> On 14/02/2017 08:21, Kevin McErlean wrote:
> > Dear sir, or ma'am,
> >   I am a novice/hobbyist and have recently put
> > FreeBSD 11 on an HP 2000 DX219 notebook; I have spent some time
> trying to
> > get drivers for the RTL8188CE wireless card, without much luck. It
> is only
> > after several attempts and forum searches that I am sending this
> email, as
> > this was a "practical application" to learn from. Any guidance on
> this will
> > be absolutely appreciated. Thank you for your time.
> 
> Hi,
> according to the manpage, rtwn should be the correct driver (based
> solely on a quick search using
> root@bsdpkgbuild:~ # apropos Realtek | grep -i 8188ce
> rtwn(4) - Realtek RTL8188CE PCIe IEEE 802.11b/g/n wireless network
> device )
> and a quick read of the manpage suggests adding
> 
> if_rtwn_load="YES"
> legal.realtek.license_ack=1
> rtwn-rtl8192cfwU_load="YES"
> rtwn-rtl8192cfwU_B_load="YES"
> 
> 
> to /boot/loader.conf
> and rebooting.
> check its been seen ok by running
> sysctl net.wlan.devices
> 
> which should return something like
> net.wlan.devices: rtwn0
> 
> from there you should be ok to follow the handbook on wireless.
> 
> 
> Hope that helps,
> Vince
> 
> > ___
> > freebsd-wireless@freebsd.org <mailto:freebsd-wireless@freebsd.org>
> mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> <https://lists.freebsd.org/mailman/listinfo/freebsd-wireless>
> > To unsubscribe, send any mail to
> "freebsd-wireless-unsubscr...@freebsd.org
> <mailto:freebsd-wireless-unsubscr...@freebsd.org>"
> >
> ___
> freebsd-wireless@freebsd.org <mailto:freebsd-wireless@freebsd.org>
> mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> <https://lists.freebsd.org/mailman/listinfo/freebsd-wireless>
> To unsubscribe, send any mail to
> "freebsd-wireless-unsubscr...@freebsd.org
> <mailto:freebsd-wireless-unsubscr...@freebsd.org>"
> 
> 
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Re: Realtek wireless card support

[Vincent Hoffman-Kazlauskas]

On 14/02/2017 08:21, Kevin McErlean wrote:
> Dear sir, or ma'am,
>   I am a novice/hobbyist and have recently put
> FreeBSD 11 on an HP 2000 DX219 notebook; I have spent some time trying to
> get drivers for the RTL8188CE wireless card, without much luck. It is only
> after several attempts and forum searches that I am sending this email, as
> this was a "practical application" to learn from. Any guidance on this will
> be absolutely appreciated. Thank you for your time.

Hi,
according to the manpage, rtwn should be the correct driver (based
solely on a quick search using
root@bsdpkgbuild:~ # apropos Realtek | grep -i 8188ce
rtwn(4) - Realtek RTL8188CE PCIe IEEE 802.11b/g/n wireless network device )
and a quick read of the manpage suggests adding

if_rtwn_load="YES"
legal.realtek.license_ack=1
rtwn-rtl8192cfwU_load="YES"
rtwn-rtl8192cfwU_B_load="YES"


to /boot/loader.conf
and rebooting.
check its been seen ok by running
sysctl net.wlan.devices

which should return something like
net.wlan.devices: rtwn0

from there you should be ok to follow the handbook on wireless.


Hope that helps,
Vince

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

Re: Odd issue with ath and 2 IPs on interface at boot

[Vincent Hoffman]

That makes sense. I just added a couple of lines to rc.local for now.
will update/test again in a month or so.
The other option I thought might work would be to make 2 nodes from the
ath0, wlan0 (station mode) and wlan1 (access point) and have the inside
addresses on a separate network, might try that later.

Vince

On 06/11/2013 23:22, Adrian Chadd wrote:
> There's bugs with how interfaces are setup and wpa_supplicant is being
> called. So I think this is just fallout from that.
>
>
> :(
>
>
> -adrian
>
>
> On 6 November 2013 15:20, Vincent Hoffman  wrote:
>> Hi,
>> I'm trying to bring up a wlan interface with 2 IPs on it so I can
>> NAT other devices on the wireless network.
>> If I try and configure both IPs at boot via rc.conf I get no link and
>> logs as follows
>> Many repeating
>> Nov  5 23:02:34 ostracod wpa_supplicant[676]: wlan0: Failed to initiate
>> AP scan
>> Nov  5 23:02:35 ostracod kernel: ath0: ath_legacy_rx_tasklet:
>> sc_inreset_cnt > 0; skipping
>> Nov  5 23:02:35 ostracod wpa_supplicant[676]: ioctl[SIOCS80211, op=103,
>> val=0, arg_len=128]: Operation now in progress
>> Nov  5 23:02:35 ostracod wpa_supplicant[676]: wlan0: Failed to initiate
>> AP scan
>> with the occasional
>> Nov  5 23:04:51 ostracod kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0;
>> bailing
>> Nov  5 23:04:51 ostracod kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0;
>> bailing
>>
>> in rc.conf I have:
>>wlans_ath0="wlan0"
>>ifconfig_wlan0="WPA inet 85.233.185.162/29 -bgscan"
>>ifconfig_wlan0_alias0="inet 10.10.10.1/24"
>>
>>
>> If however I add just one address and then create the alias manually
>> later It works fine.
>>
>> ath device details
>>
>> ath0:  mem 0xfebf-0xfebf irq 16 at device 0.0
>> on pci4
>> ath0: AR2425 mac 14.2 RF5424 phy 7.0
>> ath0: 2GHz radio: 0x; 5GHz radio: 0x00a2
>>
>> ath0@pci0:4:0:0:class=0x02 card=0x7131144f chip=0x001c168c
>> rev=0x01 hdr=0x00
>> vendor = 'Atheros Communications Inc.'
>> device = 'AR242x / AR542x Wireless Network Adapter (PCI-Express)'
>> class  = network
>> subclass   = ethernet
>>
>> OS details:
>> FreeBSD ostracod.unsane.co.uk 10.0-BETA2 FreeBSD 10.0-BETA2 #71 r257498:
>> Fri Nov  1 17:31:01 GMT 2013
>> t...@ostracod.unsane.co.uk:/scratch/obj/usr/src/sys/OSTRACOD  amd64
>>
>> It seems unlikely this is expected and i'm not even sure its ath based
>> but I dont have any other wireless interfaces to test with.
>> Any suggestions?
>> The system is in use at the moment but I can test from time to time.
>>
>> Vince
>>
>>
>> ___
>> 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"

___
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"

Odd issue with ath and 2 IPs on interface at boot

[Vincent Hoffman]

Hi,
I'm trying to bring up a wlan interface with 2 IPs on it so I can
NAT other devices on the wireless network.
If I try and configure both IPs at boot via rc.conf I get no link and
logs as follows
Many repeating
Nov  5 23:02:34 ostracod wpa_supplicant[676]: wlan0: Failed to initiate
AP scan
Nov  5 23:02:35 ostracod kernel: ath0: ath_legacy_rx_tasklet:
sc_inreset_cnt > 0; skipping
Nov  5 23:02:35 ostracod wpa_supplicant[676]: ioctl[SIOCS80211, op=103,
val=0, arg_len=128]: Operation now in progress
Nov  5 23:02:35 ostracod wpa_supplicant[676]: wlan0: Failed to initiate
AP scan
with the occasional
Nov  5 23:04:51 ostracod kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0;
bailing
Nov  5 23:04:51 ostracod kernel: ath0: ath_raw_xmit: sc_inreset_cnt > 0;
bailing

in rc.conf I have:
   wlans_ath0="wlan0"
   ifconfig_wlan0="WPA inet 85.233.185.162/29 -bgscan"
   ifconfig_wlan0_alias0="inet 10.10.10.1/24"


If however I add just one address and then create the alias manually
later It works fine.

ath device details

ath0:  mem 0xfebf-0xfebf irq 16 at device 0.0
on pci4
ath0: AR2425 mac 14.2 RF5424 phy 7.0
ath0: 2GHz radio: 0x; 5GHz radio: 0x00a2

ath0@pci0:4:0:0:class=0x02 card=0x7131144f chip=0x001c168c
rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
device = 'AR242x / AR542x Wireless Network Adapter (PCI-Express)'
class  = network
subclass   = ethernet

OS details:
FreeBSD ostracod.unsane.co.uk 10.0-BETA2 FreeBSD 10.0-BETA2 #71 r257498:
Fri Nov  1 17:31:01 GMT 2013
t...@ostracod.unsane.co.uk:/scratch/obj/usr/src/sys/OSTRACOD  amd64

It seems unlikely this is expected and i'm not even sure its ath based
but I dont have any other wireless interfaces to test with.
Any suggestions?
The system is in use at the moment but I can test from time to time.

Vince


___
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"

Re: [rfc] removing the NDISulator

[Vincent Hoffman]

On 23/10/2013 18:35, Eitan Adler wrote:
> On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd  wrote:
>> If there are drivers that people absolutely need fixed then they should
>> stand up and say "hey, I really would like X to work better!" and then
>> follow it up with some encouraging incentives. Right now the NDISulator
>> lets people work _around_ this by having something that kind of works for
>> them but it doesn't improve our general driver / stack ecosystems.
> I doubt most people prefer to use the ndisulator over a native driver.
> However, many people don't have the skills, time, or money to provide
> the incentives you are talking about.  At this point ndisulator
> provides a means to an end: working wireless and it isn't causing
> significant strain on the project in terms of development effort.
>
> Our end users are not always developers and I think removing this
> feature will hurt more than it will help.
>
>
As an end user, the main issue I have is that according to the manpage
it supports ndis 5.1
According to
http://en.wikipedia.org/wiki/Network_Driver_Interface_Specification this
is the version supported by
Windows XP , Server 2003
, Windows CE
 4.x, 5.0, 6.0

As you might guess most new devices wont be coming with drivers for XP,
so does this mean I wont be able to use drivers for a recent windows
version (my understanding is that it will but happy to learn differently)
If this is the case and there is no active development on it, a gradual
depreciation over the 10.x series is probably a good idea. If however
its likely to support current drivers/devices it does have a place (I've
used it once or twice in a pinch.)


Vince
^
___
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"

Re: Thinkpad T60 with Atheros working only after restart from Windows

[Vincent Hoffman]

As an easy test if you arent keen on making the leap just yet I'd
suggest getting a snapshot CD and just boot it as a liveCD to test.
either a snapshot
http://www.freebsd.org/snapshots/
or one of the daily builds from
https://pub.allbsd.org/FreeBSD-snapshots/
(for example
https://pub.allbsd.org/FreeBSD-snapshots/amd64-amd64/10.0-HEAD-r252115-JPSNAP/iso/FreeBSD-10.0-HEAD-r252115-JPSNAP-amd64-amd64-release.iso)

That said I run -CURRENT on my server at home (for the atheros driver)
and dont have any problems with it.

Vince


On 24/06/2013 21:01, Lyubomir Yotov wrote:
> Hi Adrian,
>
> I will try to get -HEAD on my T60 and will report back.
>
> Regards,
>
> Lyubomir
>
>
> On 24 June 2013 20:21, Adrian Chadd  wrote:
>
>> Hi,
>>
>> Would you be willing to try a -HEAD snapshot on your laptop?
>>
>> Maybe I've fixed it as part of the other driver work that I've done as
>> part of development in -HEAD.
>>
>> But right now I really have no idea. I don't have a T60 here that has
>> that chip in it. If all the T60 BIOSes allow AR5418 NICs then I can
>> try it out, but all of the T60's I've played with thus far have the
>> intel hardware in it.
>>
>>
>>
>> Adrian
>>
>>
>> On 21 June 2013 02:02, Lyubomir Yotov  wrote:
>>> Hello Adrian,
>>>
>>> Do you have any feedback on the matter?
>>>
>>> Regards,
>>>
>>> Lyubomir
>>>
>>>
>>> On 13 June 2013 10:09, Lyubomir Yotov  wrote:
 Hello Adrian,

 I enabled acpi_ibm.ko but this didn't help and after "halt" the wifi is
 not working again.

 Regards,

 Lyubomir


 On 13 June 2013 08:03, Lyubomir Yotov  wrote:
> Hello Adrian,
> I did some tests and discovered that the problem is related to
> "halt"/"shutdown" of system. If "reboot" is carried out than there is
>> no
> problem and the wifi works properly (even if done from Gnome - Gnome
>> seems
> to have no relation to the problem). So what could lead to "ath0: time
>> out"
> after shutting down or halting the system? I noticed that there are irq
> storms on irq 17 which is the wifi irq (interrupt storm detected on
> "irq17:"; throttling interrupt source). Something else that I am not
>> sure to
> have relevance - after shutdown during the start-up ath0 is reported
>> to use
> autoselect mode 11g:
> (below is from dmesg)
>
> ath0: flags=8843 metric 0 mtu
> 2290
>
> ether 00:19:7e:91:xx:xx
> nd6 options=29
> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g
> status: associated
>
> After the boot has finished the mode changes to 11a:
>
> #ifconfig ath0
>
> ath0: flags=8843 metric 0 mtu
> 2290
> ether 00:19:7e:91:xx:xx
> nd6 options=29
> media: IEEE 802.11 Wireless Ethernet autoselect mode 11a
> status: associated
>
> Do you have any idea where to look for now?
>
> Regards,
>
>
> Lyubomir
> P.S. I will try to play with acpi_ibm.ko and see if things change if I
> make it auto-load.
>
>
> On 10 June 2013 16:06, Lyubomir Yotov  wrote:
>> Hello Adrian,
>>
>> Attached are files with consecutive vmstat -i when the wlan is working
>> (vmstat-i_working.txt) and when the wlan is not working
>> (vmstat-i_not_working.txt). There is also output from ifconfig when
>> the wlan
>> is not working (ifconfig.txt).
>> After some more deeper investigation it seems to me that the problem
>> appears after starting X with Gnome. I will continue investigating
>> with
>> "reboot"/"halt -p" and inform you.
>> BTW do you think that starting Gnome session (using startx, as I
>> haven't
>> set auto start of X if this is of any importance) can cause problems
>> - in
>> Gnome I have no settings for the network in the "System->Network"
>> application and I start it with normal user?
>>
>> Regards,
>>
>> Lyubo
>>
>>
>> On 9 June 2013 18:28, Adrian Chadd  wrote:
>>> Can you please paste the vmstat -i output?
>>>
>>>
>>>
>>> adrian
>>>
>>> On 9 June 2013 06:53, Lyubomir Yotov  wrote:
 Hi,

 After restart from Windows and working wireless the number of
 interrupts
 increases and the rate increases. After next restart (the ath0
>> times
 out)
 the interrupts increase but the rate is going down.
 I noticed that after restart from Windows and working wifi if I
 restart
 /etc/rc.d/netif the wifi is working again. If I shutdown wlan0 and
 bring it
 up again then I wlan0 doesn't get address but ath0 is not timing
>> out.
 I can
 still get a list with the available APs around.

 Regards,

 Lyubo






 On 8 June 2013 18:28, Adrian Chadd  wrote:
> Hm!
>
> Ok, this should 

Re: wireless link flaps (ath ar9280)

[Vincent Hoffman]

Just an update that after updating to the latest -HEAD these have
disappeared again.


Vince

On 28/01/2013 01:45, Adrian Chadd wrote:
> Right, this looks like you're missing beacons.
>
> My latest -HEAD changes causes a non-loss hardware reset, in case it's
> gone deaf.
>
> But if you are going deaf and missing the occasional beacon, it
> shouldn't be disconnecting you. I wonder how that logic is working..
>
>
> Adrian
>
>
> On 27 January 2013 13:56, Vincent Hoffman  wrote:
>> On 27/01/2013 17:11, Adrian Chadd wrote:
>>> Hm, see if it's a beacon miss thing:
>>>
>>>
>>> sysctl dev.ath.0.debug=0x80
>> now with added debugging.
>>
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_proc: pending 1
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: nexttbtt
>> 33171100 intval 100 (100)
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: tsf
>> 33967936054 tsf:tu 33171814 intval 100 nexttbtt 33171900 dtim 100
>> nextdtim 33171900 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next
>> 33171900 timoffset 0
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_vap: tsf 33967937503
>> lastrx 727896 (33967209607) bmiss 716800
>> Jan 27 21:49:09 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED
>> bssid=e0:91:f5:48:5b:b9 reason=0
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_proc: pending 1
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: nexttbtt
>> 33171100 intval 100 (100)
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: tsf
>> 33968652767 tsf:tu 33172514 intval 100 nexttbtt 33172600 dtim 100
>> nextdtim 33172600 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next
>> 33172600 timoffset 0
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_vap: tsf 33968654221
>> lastrx 1444614 (33967209607) bmiss 716800
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: norm:
>> node 0xff800b388000: bf=0xff80008c3140: addbaw=0, dobaw=1,
>> seqno=2485, retry=0
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node
>> 0xff800b388000: bf=0xff80008c3140: txq[1] axq_depth=0,
>> axq_aggr_depth=0
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node
>> 0xff800b388000: bf=0xff80008c3140: tid txq_depth=4 hwq_depth=0,
>> bar_wait=1, isfiltered=0
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node
>> 0xff800b388000: tid 0: sched=0, paused=1, incomp=0, baw_head=98,
>> baw_tail=98 txa_start=2485, ni_txseqs=2489
>> Jan 27 21:49:09 ostracod kernel: TODS
>> 00:24:23:07:fb:5d->60:33:4b:0d:e1:f8(e0:91:f5:48:5b:b9) data QoS [TID 0]
>> WEP [IV 05 34 00 09 00 00 KID 0] 0M
>> Jan 27 21:49:09 ostracod kernel: 8841  e091 f548 5bb9 0024 2307 fb5d
>> 6033 4b0d e1f8 509b  dec0 0534 0020 0900   0300  0800
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
>> added: seqno 2485
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
>> added: seqno 2486
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
>> added: seqno 2487
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
>> added: seqno 2488
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf
>> 0xff80008c3140: seqno 2485: dobaw should've been cleared!
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf
>> 0xff80008c1e20: seqno 2486: dobaw should've been cleared!
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf
>> 0xff80008a6178: seqno 2487: dobaw should've been cleared!
>> Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf
>> 0xff80008b7b90: seqno 2488: dobaw should've been cleared!
>> Jan 27 21:49:09 ostracod kernel: wlan0: link state changed to DOWN
>> Jan 27 21:49:12 ostracod wpa_supplicant[568]: Trying to associate with
>> e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz)
>> Jan 27 21:49:12 ostracod wpa_supplicant[568]: Associated with
>> e0:91:f5:48:5b:b9
>> Jan 27 21:49:12 ostracod kernel: wlan0: link state changed to UP
>> Jan 27 21:49:12 ostracod kernel: ath0: ath_beacon_config: nexttbtt 7300
>> intval 100 (100)
>> Jan 27 21:49:12 ostracod kernel: ath0: ath_beacon_config: tsf
>> 33971573916 tsf:tu 33175367 intval 100 nexttbtt 33175400 dtim 100
>> nextdtim 33175400 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next
>> 33175400 timoffset 0
>> Jan 27 21:49:13 ostracod wpa_supplicant[568]: WPA: Key negotiation
>> completed with e0:91:f5:48:5b:b9 [P

Re: wireless link flaps (ath ar9280)

[Vincent Hoffman]

On 27/01/2013 17:11, Adrian Chadd wrote:
> Hm, see if it's a beacon miss thing:
>
>
> sysctl dev.ath.0.debug=0x80
now with added debugging.

Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_proc: pending 1
Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: nexttbtt
33171100 intval 100 (100)
Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: tsf
33967936054 tsf:tu 33171814 intval 100 nexttbtt 33171900 dtim 100
nextdtim 33171900 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next
33171900 timoffset 0
Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_vap: tsf 33967937503
lastrx 727896 (33967209607) bmiss 716800
Jan 27 21:49:09 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED
bssid=e0:91:f5:48:5b:b9 reason=0
Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_proc: pending 1
Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: nexttbtt
33171100 intval 100 (100)
Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: tsf
33968652767 tsf:tu 33172514 intval 100 nexttbtt 33172600 dtim 100
nextdtim 33172600 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next
33172600 timoffset 0
Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_vap: tsf 33968654221
lastrx 1444614 (33967209607) bmiss 716800
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: norm:
node 0xff800b388000: bf=0xff80008c3140: addbaw=0, dobaw=1,
seqno=2485, retry=0
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node
0xff800b388000: bf=0xff80008c3140: txq[1] axq_depth=0,
axq_aggr_depth=0
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node
0xff800b388000: bf=0xff80008c3140: tid txq_depth=4 hwq_depth=0,
bar_wait=1, isfiltered=0
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node
0xff800b388000: tid 0: sched=0, paused=1, incomp=0, baw_head=98,
baw_tail=98 txa_start=2485, ni_txseqs=2489
Jan 27 21:49:09 ostracod kernel: TODS
00:24:23:07:fb:5d->60:33:4b:0d:e1:f8(e0:91:f5:48:5b:b9) data QoS [TID 0]
WEP [IV 05 34 00 09 00 00 KID 0] 0M
Jan 27 21:49:09 ostracod kernel: 8841  e091 f548 5bb9 0024 2307 fb5d
6033 4b0d e1f8 509b  dec0 0534 0020 0900   0300  0800
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 2485
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 2486
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 2487
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 2488
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf
0xff80008c3140: seqno 2485: dobaw should've been cleared!
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf
0xff80008c1e20: seqno 2486: dobaw should've been cleared!
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf
0xff80008a6178: seqno 2487: dobaw should've been cleared!
Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf
0xff80008b7b90: seqno 2488: dobaw should've been cleared!
Jan 27 21:49:09 ostracod kernel: wlan0: link state changed to DOWN
Jan 27 21:49:12 ostracod wpa_supplicant[568]: Trying to associate with
e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz)
Jan 27 21:49:12 ostracod wpa_supplicant[568]: Associated with
e0:91:f5:48:5b:b9
Jan 27 21:49:12 ostracod kernel: wlan0: link state changed to UP
Jan 27 21:49:12 ostracod kernel: ath0: ath_beacon_config: nexttbtt 7300
intval 100 (100)
Jan 27 21:49:12 ostracod kernel: ath0: ath_beacon_config: tsf
33971573916 tsf:tu 33175367 intval 100 nexttbtt 33175400 dtim 100
nextdtim 33175400 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next
33175400 timoffset 0
Jan 27 21:49:13 ostracod wpa_supplicant[568]: WPA: Key negotiation
completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP]
Jan 27 21:49:13 ostracod wpa_supplicant[568]: CTRL-EVENT-CONNECTED -
Connection to e0:91:f5:48:5b:b9 completed (reauth) [id=0 id_str=]


Thanks as ever for all the work Adrian,

Vince


>
>
> adrian
>
> On 27 January 2013 04:31, Vincent Hoffman  wrote:
>> Hi all,
>> I'm running a recent -current (r245741) and seem to be getting
>> interface flaps. Since this machine is mainly used for home mail and a
>> little light file serving I'm not sure when they started occuring as i
>> only have logging going back to the 18th Jan.
>>
>> Sample log messages are:
>> Jan 24 16:26:22 ostracod kernel: ar5416StopDmaReceive: dma failed to
>> stop in 10ms
>> Jan 24 16:26:22 ostracod kernel: AR_CR=0x0024
>> Jan 24 16:26:22 ostracod kernel: AR_DIAG_SW=0x4220
>> Jan 24 16:26:23 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED
>> bssid=e0:91:f5:48:5b:b9 reason=0
>> Jan 24 16:26:23 ostracod kernel: wlan0: link state changed to DOWN
>> Jan 24 16:26:26 ostracod wpa_supplicant[568]: Trying to associate with
>> e0:91:f5:48:5b:b9 (SSID='vhoff&#

wireless link flaps (ath ar9280)

[Vincent Hoffman]

Hi all,
I'm running a recent -current (r245741) and seem to be getting
interface flaps. Since this machine is mainly used for home mail and a
little light file serving I'm not sure when they started occuring as i
only have logging going back to the 18th Jan.

Sample log messages are:
Jan 24 16:26:22 ostracod kernel: ar5416StopDmaReceive: dma failed to
stop in 10ms
Jan 24 16:26:22 ostracod kernel: AR_CR=0x0024
Jan 24 16:26:22 ostracod kernel: AR_DIAG_SW=0x4220
Jan 24 16:26:23 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED
bssid=e0:91:f5:48:5b:b9 reason=0
Jan 24 16:26:23 ostracod kernel: wlan0: link state changed to DOWN
Jan 24 16:26:26 ostracod wpa_supplicant[568]: Trying to associate with
e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz)
Jan 24 16:26:26 ostracod wpa_supplicant[568]: Associated with
e0:91:f5:48:5b:b9
Jan 24 16:26:26 ostracod kernel: wlan0: link state changed to UP
Jan 24 16:26:27 ostracod wpa_supplicant[568]: WPA: Key negotiation
completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP]

I sometime get just



Jan 25 00:57:36 ostracod kernel: ar5416StopDmaReceive: dma failed to
stop in 10ms
Jan 25 00:57:36 ostracod kernel: AR_CR=0x0024
Jan 25 00:57:36 ostracod kernel: AR_DIAG_SW=0x4220

or

Jan 25 09:39:24 ostracod wpa_supplicant[568]: WPA: Group rekeying
completed with e0:91:f5:48:5b:b9 [GTK=TKIP]
Jan 25 09:41:13 ostracod kernel: ar5416StopDmaReceive: dma failed to
stop in 10ms
Jan 25 09:41:13 ostracod kernel: AR_CR=0x0024
Jan 25 09:41:13 ostracod kernel: AR_DIAG_SW=0x4220
Jan 25 09:46:50 ostracod kernel: ar5416StopDmaReceive: dma failed to
stop in 10ms
Jan 25 09:46:50 ostracod kernel: AR_CR=0x0024
Jan 25 09:46:50 ostracod kernel: AR_DIAG_SW=0x4220
Jan 25 09:49:24 ostracod wpa_supplicant[568]: WPA: Group rekeying
completed with e0:91:f5:48:5b:b9 [GTK=TKIP]
Jan 25 09:52:10 ostracod kernel: ar5416StopDmaReceive: dma failed to
stop in 10ms
Jan 25 09:52:10 ostracod kernel: AR_CR=0x0024
Jan 25 09:52:10 ostracod kernel: AR_DIAG_SW=0x4220
Jan 25 09:57:07 ostracod kernel: ath0: bb hang detected (0x4), resetting

or

Jan 26 17:24:46 ostracod kernel: ar5416StopDmaReceive: dma failed to
stop in 10ms
Jan 26 17:24:46 ostracod kernel: AR_CR=0x0024
Jan 26 17:24:46 ostracod kernel: AR_DIAG_SW=0x4220
Jan 26 17:25:31 ostracod kernel: ar5416PerCalibrationN: NF calibration
didn't finish; delaying CCA

with no interface flaps.
And sometimes much more info

Jan 25 16:56:27 ostracod kernel: ar5416StopDmaReceive: dma failed to
stop in 10ms
Jan 25 16:56:27 ostracod kernel: AR_CR=0x0024
Jan 25 16:56:27 ostracod kernel: AR_DIAG_SW=0x4220
Jan 25 16:56:28 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED
bssid=e0:91:f5:48:5b:b9 reason=0
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: norm:
node 0xff8014828000: bf=0xff80008b23e8: addbaw=1, dobaw=1,
seqno=3447, retry=6
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node
0xff8014828000: bf=0xff80008b23e8: txq[1] axq_depth=0,
axq_aggr_depth=0
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node
0xff8014828000: bf=0xff80008b23e8: tid txq_depth=10 hwq_depth=0,
bar_wait=1, isfiltered=0
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node
0xff8014828000: tid 0: sched=0, paused=1, incomp=0, baw_head=114,
baw_tail=116 txa_start=3446, ni_txseqs=3456
Jan 25 16:56:28 ostracod kernel: TODS
00:24:23:07:fb:5d->e0:91:f5:48:5b:b9(e0:91:f5:48:5b:b9) data QoS [TID 0]
WEP [IV b6 89 00 0c 00 00 KID 0] 0M
Jan 25 16:56:28 ostracod kernel: 8849  e091 f548 5bb9 0024 2307 fb5d
e091 f548 5bb9 70d7  dec0 b689 0020 0c00   0300  0800
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 3448
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 3449
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 3450
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 3451
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 3452
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 3453
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 3454
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't
added: seqno 3455
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf
0xff80008a9e08: seqno 3448: dobaw should've been cleared!
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf
0xff80008aa468: seqno 3449: dobaw should've been cleared!
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf
0xff80008c8a80: seqno 3450: dobaw should've been cleared!
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf
0xff80008cf080: seqno 3451: dobaw should've been cleared!
Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf
0xff80008a8488: seqno 3452: dobaw should've been cleared!
Jan 

Re: freebsd-head and spectral scan

[Vincent Hoffman]

On 09/01/2013 00:07, Adrian Chadd wrote:
> I hereby give you, AR9280 doing spectral + channel scanning:
>
> http://people.freebsd.org/~adrian/ath/fft_snapshot_5ghz.7.png
>
This looks pretty :) as a bit of a clueless end user, what can I use
this for? :)
>
> adrian
> ___
> 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"
>

___
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"