Re: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error
On Wed, Jun 26, 2013 at 7:10 PM, Anton Shterenlikht me...@bris.ac.uk wrote: The following reply was made to PR kern/176104; it has been noted by GNATS. From: Anton Shterenlikht me...@bris.ac.uk To: bug-follo...@freebsd.org Cc: Subject: RE: kern/176104: [iwn] iwn0: iwn_intr: fatal firmware error Date: Tue, 25 Jun 2013 14:28:51 +0100 (BST) One thing I noticed is that this problem occurs more often when running on battery, and less frequently when running from mains. Could this be related to some energy saving code? AFAIK, no. Hiren ___ 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
Re: kern/180094: [iwn] Incorrect id for Intel Centrino Wireless-N 130
The following reply was made to PR kern/180094; it has been noted by GNATS.
From: hiren panchasara hi...@freebsd.org
To: Cedric c...@cgross.info
Cc: freebsd-gnats-sub...@freebsd.org
Subject: Re: kern/180094: [iwn] Incorrect id for Intel Centrino Wireless-N 130
Date: Sat, 29 Jun 2013 11:00:59 -0700
On Sat, Jun 29, 2013 at 8:52 AM, Cedric c...@cgross.info wrote:
Number: 180094
Category: kern
Synopsis: [iwn] Incorrect id for Intel Centrino Wireless-N 130
Confidential: no
Severity: non-critical
Priority: low
Responsible:freebsd-bugs
State: open
Quarter:
Keywords:
Date-Required:
Class: sw-bug
Submitter-Id: current-users
Arrival-Date: Sat Jun 29 16:00:00 UTC 2013
Closed-Date:
Last-Modified:
Originator: Cedric
Release:9.1-release-p4
Organization:
Environment:
FreeBSD Test.RP614v4 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0 r252335: Fri
Jun 28 19:04:30 CEST 2013
root@Test.RP614v4:/usr/obj/amd64.amd64/usr/src/sys/GENERIC amd64
Description:
iwn_ident_table indicate a wrong id for Intel Centrino Wireless-N 130.
In /head/sys/dev/iwn/if_iwn.c :
{ 0x8086, 0x0887, Intel Centrino Wireless-N 130 }
0x0887 is wrong. Must be 0x0897.
Cf. : http://pci-ids.ucw.cz/read/PC/8086
Looks correct.
Will patch it.
Thanks,
Hiren
How-To-Repeat:
Fix:
Release-Note:
Audit-Trail:
Unformatted:
___
freebsd-b...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to freebsd-bugs-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
ath0 monitor mode mystery
I am trying to enable (what I think is) monitor mode on PicoStation M2HP. I am confused though. man ifconfig is also showing 2 different monitor things. I tried both below: # ifconfig wlan0 create wlandev ath0 wlan0: Ethernet address: dc:9f:db:6a:3e:9e # ifconfig wlan0 down # ifconfig wlan0 monitor # ifconfig wlan0 channel 4 # ifconfig wlan0 up # # ifconfig wlan0 wlan0: flags=48843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,MONITOR metric 0 mtu 1500 ether dc:9f:db:6a:3e:9e media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid channel 4 (2427 MHz 11g) regdomain FCC3 country US indoor ecm authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60 protmode CTS wme burst bintval 0 # And now I get things via: # tcpdump -ni wlan0 -y IEEE802_11_RADIO wlan0: promiscuous mode enabled wlan0: promiscuous mode disabled wlan0: promiscuous mode enabled tcpdump: data link type IEEE802_11_RADIO tcpdump: WARNING: wlan0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on wlan0, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 65535 bytes 18:56:23.803065 9838362989us tsft 1.0 Mb/s 60dBm tx power antenna 0 2427 MHz 11g Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] 18:56:23.994159 9838553735us tsft 1.0 Mb/s -75dB signal -96dB noise antenna 1 2427 MHz 11g Probe Request () [1.0 2.0 5.5 11.0 6.0 9.0 12.0 18.0 Mbit] 18:56:23.995089 9838554678us tsft 1.0 Mb/s -75dB signal -96dB noise antenna 1 2427 MHz 11g Probe Request (Y!Office) [1.0 2.0 5.5 11.0 6.0 9.0 12.0 18.0 Mbit] 18:56:23.995979 983875us tsft 1.0 Mb/s -75dB signal -96dB noise antenna 1 2427 MHz 11g Probe Request () [1.0 2.0 5.5 11.0 6.0 9.0 12.0 18.0 Mbit] 18:56:24.002484 9838562077us tsft 1.0 Mb/s -76dB signal -96dB noise antenna 1 2427 MHz 11g Probe Request () [1.0 2.0 5.5 11.0 6.0 9.0 12.0 18.0 Mbit] 18:56:24.016082 9838576006us tsft 1.0 Mb/s 60dBm tx power antenna 0 2427 MHz 11g ht/40+ Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] But is this really a monitor mode? Not according to tcpdump. What we are seeing above are beacons sent out by APs? How do we get probe requests sent to APs by devices? man tcpdump says: -I Put the interface in monitor mode; this is supported only on IEEE 802.11 Wi-Fi interfaces, and supported only on some operat- ing systems. Note that in monitor mode the adapter might disassociate from the network with which it's associated, so that you will not be able to use any wireless networks with that adapter. This could prevent accessing files on a network server, or resolving host names or network addresses, if you are capturing in monitor mode and are not connected to another network with another adapter. This flag will affect the output of the -L flag. If -I isn't specified, only those link-layer types available when not in monitor mode will be shown; if -I is specified, only those link- layer types available when in monitor mode will be shown. So I tried -I, # tcpdump -Ii wlan0 -y IEEE802_11_RADIO tcpdump: wlan0 is not a monitor mode VAP To create a new monitor mode VAP use: ifconfig wlan1 create wlandev ath0 wlanmode monitor and use wlan1 as the tcpdump interface # Okay, lets create wlan1 as suggested: # ifconfig wlan1 create wlandev ath0 wlanmode monitor wlan1: Ethernet address: dc:9f:db:6a:3e:9e # ifconfig wlan1 wlan1: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ether dc:9f:db:6a:3e:9e media: IEEE 802.11 Wireless Ethernet autoselect monitor (autoselect monitor) status: no carrier ssid channel 4 (2427 MHz 11g) regdomain FCC3 country US indoor ecm authmode OPEN privacy OFF txpower 30 scanvalid 60 protmode CTS wme burst bintval 0 # See subtle difference between wlan0 and wlan1. Still no success (but new error): code # tcpdump -Ii wlan1 -y IEEE802_11_RADIO wlan1: promiscuous mode enabled tcpdump: data link type IEEE802_11_RADIO tcpdump: WARNING: wlan1: no IPv4 address assigned ar5416StopDmaReceive: dma failed to stop in 10ms AR_CR=0x0024 AR_DIAG_SW=0x4220 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on wlan1, link-type IEEE802_11_RADIO (802.11 plus radiotap header), capture size 65535 bytes ar5416StopDmaReceive: dma failed to stop in 10ms AR_CR=0x0024 AR_DIAG_SW=0x4220 ar5416StopDmaReceive: dma failed to stop in 10ms AR_CR=0x0024 AR_DIAG_SW=0x4220 ar5416StopDmaReceive: dma failed to stop in 10ms AR_CR=0x0024 AR_DIAG_SW=0x4220 ar5416StopDmaReceive: dma failed to stop in 10ms AR_CR=0x0024 AR_DIAG_SW=0x4220 ar5416StopDmaReceive: dma failed to stop in 10ms AR_CR=0x0024 AR_DIAG_SW=0x4220 ar5416StopDmaReceive:
Re: ath0 monitor mode mystery
On Mon, Sep 23, 2013 at 5:14 AM, Mark Moes mark_m...@hotmail.com wrote: 18:56:23.803065 9838362989us tsft 1.0 Mb/s 60dBm tx power antenna 0 2427 MHz 11g Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] That's what you're gonna see if it captures 802.11 frames; you already had it working :) I think you are right :-) I got confused with the tcpdump terminology. Just to conclude, for me, specifying flag MONITOR mode worked. But creating monitor mode vap did not. And a Probe Request is not a Beacon frame, it is sent by a device (laptop/smartphone) when it actively scans for APs. See http://www.wi-fiplanet.com/tutorials/print.php/1447501 Thanks a lot! Cheers, Hiren ___ 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: [iwn] Cedric's stuff is in -HEAD
On Mon, Nov 11, 2013 at 10:21 PM, Adrian Chadd adr...@freebsd.org wrote: Hi, I've just committed Cedric's stuff to -HEAD. I also fixed the MRR stuff to work. With latest everything + http://people.freebsd.org/~adrian/iwn/2013-iwn-linkq-2stream-ant-fix-1.diff flymockour-l7% sysctl dev.iwn.0 dev.iwn.0.%desc: Intel Centrino Advanced-N 6205 dev.iwn.0.%driver: iwn dev.iwn.0.%location: slot=0 function=0 dev.iwn.0.%pnpinfo: vendor=0x8086 device=0x0085 subvendor=0x8086 subdevice=0x1311 class=0x028000 dev.iwn.0.%parent: pci3 dev.iwn.0.debug: 1 It stayed up for good 15 mins and then I saw this: Nov 12 10:25:47 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 114 retries 0 nkill 0 rate 8000e10d duration 139 status 201 Nov 12 10:25:48 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 0: nr=16, rate=0x8d, rateentry=0x8f Nov 12 10:25:48 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 1: nr=16, rate=0x8d, rateentry=0x8e Nov 12 10:25:48 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 2: nr=16, rate=0x8d, rateentry=0x8d Nov 12 10:25:48 flymockour-l7 kernel: iwn_tx_data: qid 0 idx 115 len 108 nsegs 2 rate 008d plcp 0xe10d Nov 12 10:25:48 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 115 retries 0 nkill 0 rate 8000e10d duration 139 status 201 Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 0: nr=16, rate=0x8d, rateentry=0x8f Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 1: nr=16, rate=0x8d, rateentry=0x8e Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 2: nr=16, rate=0x8d, rateentry=0x8d Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_data: qid 0 idx 116 len 0 nsegs 0 rate 008d plcp 0xe10d Nov 12 10:25:49 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 116 retries 0 nkill 0 rate 8000e10d duration 132 status 201 Nov 12 10:25:49 flymockour-l7 kernel: iwn_notif_intr: scanning channel 1 status 1 Nov 12 10:25:49 flymockour-l7 kernel: iwn_notif_intr: scanning channel 6 status 1 Nov 12 10:25:49 flymockour-l7 kernel: iwn_notif_intr: scanning channel 11 status 1 Nov 12 10:25:49 flymockour-l7 kernel: iwn_notif_intr: scanning channel 7 status 1 Nov 12 10:25:49 flymockour-l7 kernel: iwn_notif_intr: scanning channel 13 status 1 Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 0: nr=16, rate=0x8d, rateentry=0x8f Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 1: nr=16, rate=0x8d, rateentry=0x8e Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 2: nr=16, rate=0x8d, rateentry=0x8d Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_data: qid 0 idx 117 len 0 nsegs 0 rate 008d plcp 0xe10d Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 0: nr=16, rate=0x8d, rateentry=0x8f Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 1: nr=16, rate=0x8d, rateentry=0x8e Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 2: nr=16, rate=0x8d, rateentry=0x8d Nov 12 10:25:49 flymockour-l7 kernel: iwn_tx_data: qid 0 idx 118 len 108 nsegs 2 rate 008d plcp 0xe10d Nov 12 10:25:49 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 117 retries 0 nkill 0 rate 8000e10d duration 132 status 201 Nov 12 10:25:49 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 118 retries 0 nkill 0 rate 8000e10d duration 139 status 201 Nov 12 10:25:50 flymockour-l7 kernel: iwn_notif_intr: scanning channel 13 status 1 Nov 12 10:25:50 flymockour-l7 kernel: received statistics without RSSI Nov 12 10:25:50 flymockour-l7 wpa_supplicant[8743]: wlan0: Trying to associate with 6c:f3:7f:4d:88:27 (SSID='Y!Office' freq=2437 MHz) Nov 12 10:25:50 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 0: nr=16, rate=0x8d, rateentry=0x8f Nov 12 10:25:50 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 1: nr=16, rate=0x8d, rateentry=0x8e Nov 12 10:25:50 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 2: nr=16, rate=0x8d, rateentry=0x8d Nov 12 10:25:50 flymockour-l7 kernel: iwn_tx_data: qid 0 idx 119 len 0 nsegs 0 rate 008d plcp 0xe10d Nov 12 10:25:50 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 119 retries 0 nkill 0 rate 8000e10d duration 132 status 201 Nov 12 10:25:50 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 0: nr=16, rate=0x8d, rateentry=0x8f Nov 12 10:25:50 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 1: nr=16, rate=0x8d, rateentry=0x8e Nov 12 10:25:50 flymockour-l7 kernel: iwn_tx_rate_to_linkq_offset: idx 2: nr=16, rate=0x8d, rateentry=0x8d Nov 12 10:25:50 flymockour-l7 kernel: iwn_tx_data: qid 0 idx 120 len 0 nsegs 0 rate 008d plcp 0xe10d Nov 12 10:25:50 flymockour-l7 kernel: iwn5000_tx_done: qid 0 idx 120 retries 0 nkill 0 rate 8000e10d duration 132 status 201 Nov 12 10:25:50 flymockour-l7 kernel: wlan0: link state changed to DOWN Nov 12 10:25:50 flymockour-l7 wpa_supplicant[8743]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Can't assign requested address Nov 12 10:25:50 flymockour-l7 wpa_supplicant[8743]: wlan0:
Re: [iwn] Cedric's stuff is in -HEAD
On Tue, Nov 12, 2013 at 10:45 AM, Adrian Chadd adr...@freebsd.org wrote: Run with wlandebug +assoc +state +debug +output +scan +crypto http://people.freebsd.org/~hiren/20131112_iwnfail_atwork.txt Thanks a bunch 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
Re: [iwn] Cedric's stuff is in -HEAD
On Tue, Nov 12, 2013 at 12:19 PM, Adrian Chadd adr...@freebsd.org wrote: On 12 November 2013 11:13, hiren panchasara hiren.panchas...@gmail.com wrote: On Tue, Nov 12, 2013 at 10:45 AM, Adrian Chadd adr...@freebsd.org wrote: Run with wlandebug +assoc +state +debug +output +scan +crypto http://people.freebsd.org/~hiren/20131112_iwnfail_atwork.txt What's this showing? What was going on at this time? I keep pings going on another window just to see when it stops. It was doing alright (pings going through) and suddenly stops working around following lines in logs: Nov 12 10:59:51 flymockour-l7 kernel: wlan0: ieee80211_bg_scan: active scan, ticks 7165936 duration 150 Nov 12 10:59:51 flymockour-l7 kernel: wlan0: [6c:f3:7f:4d:88:47] send QoS null data frame on channel 1, pwr mgt ena and then it tries scanning and what not but never recovers. Funny (read annoying) thing is, its not failing in the same way every time it disconnects. I do not see the same pattern. And by stops working I see, it still has ip and ssid but status: no carrier in ifconfig. Thanks a bunch Adrian! so, I have a feeling that for best iwn(4) behaviour, we should likely extend net80211 to not do its own scan stuff (by putting the VAP into power save mode whilst doing scanning) but just to fire off a scan request. I _think_ iwn(4) will do it itself. We should however still fix the scan code to not be a racy, unpredictable thing. I am not sure if I follow. Any more clues you can throw based on the logs? Thanks again, Hiren ___ 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: Cannot get wireless to work
On Fri, Jan 24, 2014 at 10:09 PM, Harshad D harsha...@gmail.com wrote: hello! Hi all, first post here. Installed FreeBSD for the first time on my laptop. Have followed the Handbook and got most things like X, XFCE, X config etc working. However, I am really having trouble trying to get wireless working. I have tried the following till now: This is an extract about the wireless hardware from [cmd]pciconf[/cmd]: vendor = 'Broadcom Corporation' device = 'BCM4312 802.11b/g LP-PHY' class = network So, as per the Handbook, I should use the bwn (4) driver. i have done the following till now: Installed [file]bwn-firmware-kmod[/file] from ports Added the following to [file]/boot/loader.conf[/file] if_bwn_load=YES bwn_v4__lp_ucode_load=YES Is this just a typo in email? (the double underscores) Should be bwn_v4_lp_ucode_load=YES Also, once you boot up, what do you see when you do kldstat? cheers, Hiren # if_bwi_load=YES wlan_scan_ap_load=YES wlan_scan_sta_load=YES wlan_wep_load=YES wlan_ccmp_load=YES wlan_tkip_load=YES[/code] added this to rc.conf wlans_bwn0=wlan0 ifconfig_wlan0=ssid HSD DHCP I am not sure about the DHCP part here. just something I have tried. And tried all that's shown here [url] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html[/url] . But still it doesn't work. ifconfig wlan0 up scan gives nothing: root@BSDbox:~ # ifconfig wlan0 scan root@BSDbox:~ # dmesg output is: root@BSDbox:~ # dmesg|tail bwn0: the fw file(bwn_v4_lp_ucode15) not found bwn-open_v4_lp_ucode15: could not load firmware image, error 2 bwn0: the fw file(bwn-open_v4_lp_ucode15) not found ubt0: Broadcom Corp HP Integrated Module, class 224/1, rev 2.00/1.65, addr 2 on usbus0 WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() bwn_v4_lp_ucode15: could not load firmware image, error 2 bwn0: the fw file(bwn_v4_lp_ucode15) not found bwn-open_v4_lp_ucode15: could not load firmware image, error 2 bwn0: the fw file(bwn-open_v4_lp_ucode15) not found ifconfig output: root@BSDbox:~ # ifconfig bwn0: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:26:5e:46:3e:ba nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE ether 00:23:5a:c6:da:5b inet6 fe80::223:5aff:fec6:da5b%re0 prefixlen 64 scopeid 0x2 inet 192.168.0.104 netmask 0xff00 broadcast 192.168.0.255 nd6 options=23PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=63RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL wlan0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:26:5e:46:3e:ba nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid HSD channel 1 (2412 MHz 11b) country US authmode WPA1+WPA2/802.11i privacy OFF txpower 30 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 1 wme bintval 0 I can see that the firmware file is not being loaded. How do I get it to load? I checked the /boot/firmware folder and it's empty. So I manually copied.fw files from the bwn ports directory, but that didn't work either. I tried renaming the module files (.ko) in /boot/modules to what the OS is looking for, but that failed too. I am almost at my wit's end now, and don't know how to go on from here. What do I need to do? ___ 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
Re: CAMBRIA and more than one atheros card
On Mon, Jul 7, 2014 at 11:31 AM, Adrian Chadd adr...@freebsd.org wrote: On 7 July 2014 11:28, John Hay j...@meraka.org.za wrote: On Mon, Jul 07, 2014 at 11:22:46AM -0700, Adrian Chadd wrote: On 7 July 2014 10:12, Ian Lepore i...@freebsd.org wrote: On Mon, 2014-07-07 at 09:25 -0700, Adrian Chadd wrote: hi, That call is returning ENOMEM. I'm not sure why. It allocated an mbuf fine, but it couldn't allocate the DMA map. What's the output of vmstat -z ? I wonder if it's failing an allocation. -a Lack of bounce buffers is a posibility that won't show up in vmstat output. right, but there's a bunch of already failing vmstat entries. John - there's a vmscale parameter somewhere. Hiren had to drop it down for his APs to work in 64MB of RAM. I think it's vm.kmem_size_scale . What's it say for you? :~ # sysctl vm.kmem_size_scale vm.kmem_size_scale: 3 Ok. Search the archives for an email from Hiren titled mbuf autotuning effect. TL;DR - set it to 1 and recompile. There's a kernel option somewhere to do exactly that. Yes. http://lists.freebsd.org/pipermail/freebsd-mips/2013-September/003081.html I went through this for my tplink. John, can you show o/p of: sysctl -a | grep hw | grep mem and sysctl -a | grep maxmbuf Cheers, Hiren ___ 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: Recommend Off the Shelf USB Wireless N - FreeBSD 9.3/10.0
On Tue, Aug 12, 2014 at 11:29 AM, Patrick Powell papow...@astart.com wrote: Could anybody please please recommend a USB adapter for Wireless N that: a) works with the current set of drivers for FreeBSD 9.3-RELEASE or 10.0-RELEASE I think Edimax EW-7811Un - http://www.amazon.com/Edimax-EW-7811Un-Adapter-Raspberry-Supports/dp/B003MTTJOY/ref=sr_1_1?ie=UTF8qid=1407874904sr=8-1keywords=Edimax+EW-7811Un should work on 10.0-RELEASE. 'man 4 urtwn' for more details. [skip] I'll bet there are other folks besides myself who would be grateful for such a posting. Also, this would be an opportunity to update the FreeBSD USB Adapter list. If there are responses to this posting, I would suggest that a summary be posted to one of the more general FreeBSD mailing lists. fwiw, http://www.freebsd.org/relnotes/CURRENT/hardware/support.html mentions urtwn and the chipset. cheers, Hiren ___ 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
