Current problem reports assigned to freebsd-wireless@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o kern/185478 wireless [iwi] panic in iwi0 driver o kern/185425 wireless [iwn] iwn difficulties in busy radio environments o kern/185223 wireless Intel Centrino AdvancedN + WiMAX 6250: WEP vs WPA o kern/185025 wireless [iwi] iwi driver panic on 10.0rc2 o kern/184762 wireless Wlan(Intel Centrino Wireless-N 1000) can't connect to o kern/184756 wireless [iwn] iwn(4) (5100 model) radio peridiocally gets disa o kern/184692 wireless [iwi] [panic] kernel panic in iwi0 driver o conf/184657 wireless freebsd 10 unable to connect hidden wifi o kern/184631 wireless [iwn] [patch] hook in iwn2000fw and iwn2030fw to kerne o kern/184626 wireless [wlan] wlan0 missing some ifmib(4) data o kern/183759 wireless [iwn] [wlan] Interface dies, OACTIVE set on wlan0 o kern/183727 wireless [wlan] ENOBUFFS incorrectly returned when tx packet is o kern/183644 wireless [ath] [patch] ath(4) stops working o kern/183430 wireless [iwn] latest change to the rate code setup uses 11n ra o kern/183428 wireless [net80211] [iwn] Some APs seem to announce HT but no H o kern/181898 wireless [iwn] [patch] Centrino Advanced-N 6235 with latest iwn o kern/181694 wireless [iwn] [patch] Initialize hardware in iwn(4) resume cod o kern/181161 wireless [wl] config a old compaq wl-110 wireless card make ker o kern/181132 wireless [iwn] stream calculation is wrong for the Intel 4965 o kern/181100 wireless [bwi] Turning up bwi0 crashes / deadlocks the kernel o kern/180816 wireless [iwl] Intel Centrino Wireless-N 2200 not supported o kern/179847 wireless [ath] [patch] Update regdomain in ath drivers includin o kern/179709 wireless [ath] Atheros 5212 does not work: stuck beacon; resett o kern/179547 wireless [ath] Add AR9485 custom board fixes (CUS198) o kern/179482 wireless [ath] [patch] Fix AR9462 external LNA configuration o kern/179269 wireless [ath] [AR9285] RX antenna diversity is not functioning o kern/179232 wireless [ath] panic in ath o kern/178986 wireless [ath] Change mac address of ath(4) is not reflected wh o kern/178492 wireless [ath] ath0 (AR9287) panic o kern/178491 wireless [ath] ath0 (AR9287) stuck beacon o kern/178477 wireless [ath] missed beacon / soft reset in STA mode results i o kern/178470 wireless [panic][ath] bss vap can and does change o kern/178411 wireless [ral] [panic] FreeBSD kernel crash in rt2860 o kern/178379 wireless [net80211] [ath] WPA rekey on the STA side fails when o kern/178378 wireless [net80211] crypto state isn't reset during a reassocia o kern/178263 wireless [ath] review the use of ic_freq / ic_ieee / ic_flags / o kern/177847 wireless [ath] With TPC enabled, TX power values aren't clamped o kern/177846 wireless [ath] [net80211] net80211 TX power limit isn't correct o conf/177688 wireless WiFi regodmains information is inconsistent between e o kern/177530 wireless [ath] ath driver isn't 32 bit int clean o kern/177465 wireless [iwn] 20%-100% packet loss with iwn driver o kern/177451 wireless [ieee80211] page fault in ieee80211_tx_mgt_timeout o kern/176238 wireless [ath] [patch] Correct buffer size calculation and simp o kern/176201 wireless [net80211] [patch] 11n station includes unrelated ht p o kern/176104 wireless [iwn] iwn0: iwn_intr: fatal firmware error o kern/175722 wireless [ath]lot of bad seriesx hwrate in kernel messages o kern/175446 wireless [ath] high volumes of PHY errors lead to BB/MAC hangs o kern/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174891 wireless [ieee80211] struct ieee80211_node is freed during acti o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173898 wireless [iwn] [patch] iwn(4) DOES support 6235 chip. o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff
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: IWN hangs periodically on 10.0RC3
On Fri, Jan 10, 2014 at 9:51 PM, Kevin Oberman rkober...@gmail.com wrote: On Fri, Jan 10, 2014 at 9:37 AM, Adrian Chadd adr...@freebsd.org wrote: .. when you see it hang, does anything get logged in dmesg (eg a firmware panic) ? Try recompiling your kernel with: IEEE80211_DEBUG IWN_DEBUG That way it can be debugged :) The first thing I'd check is whether there's more fun races going on in the crypto code - try wlandebug +crypto . -a I just sent a message about issues I am seeing with my IWN to wireless@. Then I saw these responses. Sorry. As far as logs go, I wee a number if cases of the following sequence: Jan 1 18:00:12 rogue dbus[1451]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Jan 1 18:00:12 rogue dbus[1451]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jan 1 18:28:56 rogue wpa_supplicant[620]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:26:b8:67:c3:2d reason=0 Jan 1 18:28:56 rogue kernel: wlan0: link state changed to DOWN Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: Trying to associate with 00:26:b8:67:c3:2d (SSID='babcom' freq=2437 MHz) Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: Associated with 00:26:b8:67:c3:2d Jan 1 18:28:59 rogue kernel: wlan0: link state changed to UP Jan 1 18:28:59 rogue dhclient[652]: send_packet: No buffer space available Jan 1 18:28:59 rogue devd: Executing '/etc/rc.d/dhclient quietstart wlan0' Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: WPA: Key negotiation completed with 00:26:b8:67:c3:2d [PTK=CCMP GTK=CCMP] Jan 1 18:28:59 rogue wpa_supplicant[620]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:26:b8:67:c3:2d completed [id=1 id_str=] Jan 1 18:29:02 rogue dhclient: New IP Address (wlan0): 192.168.1.5 Jan 1 18:29:02 rogue dhclient: New Subnet Mask (wlan0): 255.255.255.0 Jan 1 18:29:02 rogue dhclient: New Broadcast Address (wlan0): 192.168.1.255 Jan 1 18:29:02 rogue dhclient: New Routers (wlan0): 192.168.1.1 So it seems that the bounce is happening fairly often, but the system usually recovers. It seems to be pretty consistently 2-3 time4s a day. Note that the dbus messages about packagekit always immediately precede the link going down. Every tthe or four of these fail to recover: Jan 3 14:09:05 rogue kernel: wlan0: link state changed to DOWN Jan 3 14:09:56 rogue ntpd[1303]: sendto(198.129.254.218) (fd=25): Network is down Jan 3 14:10:15 rogue ntpd[1303]: sendto(208.79.18.86) (fd=25): Network is down Jan 3 14:10:29 rogue ntpd[1303]: sendto(198.124.252.90) (fd=25): Network is down Jan 3 14:10:49 rogue ntpd[1303]: sendto(198.55.111.5) (fd=25): Network is down Jan 3 14:11:00 rogue ntpd[1303]: sendto(192.95.38.104) (fd=25): Network is down Jan 3 14:14:02 rogue ntpd[1303]: sendto(198.129.252.38) (fd=25): Network is down Jan 3 14:14:12 rogue wpa_supplicant[620]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Operation not supported Jan 3 14:14:12 rogue wpa_supplicant[620]: ioctl[SIOCS80211, op=26, val=0, arg_len=0]: Operation not supported Jan 3 14:14:12 rogue wpa_supplicant[620]: wlan0: CTRL-EVENT-TERMINATING Jan 3 14:14:12 rogue dhclient[652]: connection closed Jan 3 14:14:12 rogue dhclient[652]: exiting. Jan 3 14:14:12 rogue wpa_supplicant[67153]: Successfully initialized wpa_supplicant Jan 3 14:14:16 rogue wpa_supplicant[67154]: wlan0: Trying to associate with 00:26:b8:67:c3:2d (SSID='babcom' freq=2437 MHz) Jan 3 14:14:16 rogue wpa_supplicant[67154]: wlan0: Associated with 00:26:b8:67:c3:2d Jan 3 14:14:16 rogue kernel: wlan0: link state changed to UP Jan 3 14:14:16 rogue devd: Executing '/etc/rc.d/dhclient quietstart wlan0' Jan 3 14:14:16 rogue dhclient[67191]: send_packet: No buffer space available Jan 3 14:14:17 rogue wpa_supplicant[67154]: wlan0: WPA: Key negotiation completed with 00:26:b8:67:c3:2d [PTK=CCMP GTK=CCMP] Jan 3 14:14:17 rogue wpa_supplicant[67154]: wlan0: CTRL-EVENT-CONNECTED - Connection to 00:26:b8:67:c3:2d completed [id=1 id_str=] Jan 3 14:14:18 rogue dhclient: New IP Address (wlan0): 192.168.1.5 Jan 3 14:14:18 rogue dhclient: New Subnet Mask (wlan0): 255.255.255.0 Jan 3 14:14:18 rogue dhclient: New Broadcast Address (wlan0): 192.168.1.255 Jan 3 14:14:18 rogue dhclient: New Routers (wlan0): 192.168.1.1 The restart took place when I restarted the interface about 5 minutes after it went down and, as you can see, it came up normally. I'll admit that I am completely baffled by the dbus/packagekit tie-in as I can't see what packagekit would do to touch the network. I'll be building a new kernel with debug shortly. In my other message (to wireless) I also mentioned the (possibly unrelated) issue of poor performance and and periodic sub-second connectivity drops. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com I was about to send a report that removing bgscan fixed the issue, but, then it happened again. Nothing new
