Trouble with Macbook Pro 8,2 (broadcom 4331) and latest b43
Hi,
----------------------
I'm apologize in advance if this posting repeats another posting I made on 26 Nov. I submitted it but don't see it in the archives. I'm thinking it never arrived so I am sending it again.
-----------------------
I'm wondering if anybody has any clues about why I cannot get a Broadcom 4331-based wireless device to work in my Macbook Pro (Model 8,2). When I try to load the driver with "modprobe b43" I get the following in dmesg:
[ 3279.117137] bcma-pci-bridge 0000:03:00.0: PCI INT A disabled [ 3281.301279] bcma-pci-bridge 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 3281.301297] bcma-pci-bridge 0000:03:00.0: setting latency timer to 64 [ 3281.301381] bcma: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x25, class 0x0) [ 3281.301405] bcma: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x1D, class 0x0) [ 3281.301459] bcma: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x13, class 0x0) [ 3281.301581] bcma: PMU resource config unknown for device 0x4331 [ 3281.301583] bcma: Enabling Ext PA lines not implemented [ 3281.310508] bcma: Bus registered [ 3281.312814] cfg80211: Calling CRDA to update world regulatory domain [ 3281.316215] b43-phy0: Broadcom 4331 WLAN found (core revision 29) [ 3281.316383] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 9, Type 7, Revision 1) [ 3281.316391] b43: probe of bcma0:0 failed with error -95 [ 3281.316417] Broadcom 43xx driver loaded [ Features: PMNLS, Firmware-ID: FW13 ] [ 3281.319930] cfg80211: World regulatory domain updated: [ 3281.319933] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 3281.319935] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 3281.319937] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 3281.319939] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 3281.319941] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 3281.319943] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
I had this working a few weeks ago with the same Macbook Pro model (Core i7 Quad Core 15 inch), but then an Apple firmware update (applied via OS X) bricked the laptop and I had to exchange it. I'm suspecting that the replacement has slightly revised hardware but I cannot be sure. According to lspci, the hardware still seems the same as before, as far as I can remember.
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet PCIe [14e4:16b4] (rev 10)
Subsystem: Broadcom Corporation NetXtreme BCM57765 Gigabit
Ethernet PCIe [14e4:16b4]
02:00.1 SD Host controller [0805]: Broadcom Corporation Device [14e4:16bc] (rev 10) (prog-if 01)
Subsystem: Broadcom Corporation Device [14e4:0000]
03:00.0 Network controller [0280]: Broadcom Corporation Device [14e4:4331] (rev 02)
Subsystem: Broadcom Corporation Device [14e4:4331]
I have in tried the b43 driver that comes with the 3.1.2 kernel. I have tried installing the "bleeding edge linux-next" version of b43 as of 26 November (compat-wireless-2011-11-08-11-gd32558f) as well as the "3.2-rc1" version. I have installed the broadcom firmware with b43-fwcutter with "broadcom-wl-5.100.138" and also with the version recommended with Mandriva 2011.
I did get the same error when installing the linux-next and 3.2-rc1 versions. It seemed to compile properly but then:
make -C /lib/modules/3.1.2-1.1-desktop/build M=/home/andy/kernel/compat-wireless-2011-11-22 modules make[1]: Entering directory `/usr/src/devel/3.1.2-1.1-desktop'
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/compat/main.o LD [M] /home/andy/kernel/compat-wireless-2011-11-22/compat/compat.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/main.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/scan.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/core.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/sprom.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/driver_chipcommon.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/driver_chipcommon_pmu.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/driver_pci.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/host_pci.o
LD [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/bcma.o CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/main.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/bus.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/tables.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/tables_nphy.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/radio_2055.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/radio_2056.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/phy_common.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/phy_g.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/phy_a.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/phy_n.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/phy_lp.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/tables_lpphy.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/phy_ht.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/tables_phy_ht.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/radio_2059.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/sysfs.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/xmit.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/lo.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/wa.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/dma.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/pio.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/rfkill.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/leds.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/pcmcia.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/sdio.o
LD [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/b43.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/main.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/scan.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/sprom.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/pci.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/pcihost_wrapper.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/pcmcia.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/sdio.o CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/driver_chipcommon.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/driver_chipcommon_pmu.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/driver_pcicore.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/b43_pci_bridge.o
LD [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/ssb.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/main.o CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/status.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/sta_info.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/wep.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/wpa.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/scan.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/offchannel.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/ht.o CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/agg-tx.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/agg-rx.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/ibss.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/mlme.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/work.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/iface.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/rate.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/michael.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/tkip.o CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/aes_ccm.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/aes_cmac.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/cfg.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/rx.o CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/spectmgmt.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/tx.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/key.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/util.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/wme.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/event.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/chan.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/led.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/mesh.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/mesh_pathtbl.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/mesh_plink.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/mesh_hwmp.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/pm.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/rc80211_pid_algo.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/rc80211_minstrel.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/rc80211_minstrel_ht.o
LD [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/mac80211.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/core.o/home/andy/kernel/compat-wireless-2011-11-22/net/wireless/core.c:7:0: warning: "pr_fmt" redefined [enabled by default] include/linux/printk.h:152:0: note: this is the location of the previous definition /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/core.c:7:0: warning: "pr_fmt" redefined [enabled by default] include/linux/printk.h:152:0: note: this is the location of the previous definition
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/sysfs.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/wireless/radiotap.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/util.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/reg.o/home/andy/kernel/compat-wireless-2011-11-22/net/wireless/reg.c:36:0: warning: "pr_fmt" redefined [enabled by default] include/linux/printk.h:152:0: note: this is the location of the previous definition /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/reg.c:36:0: warning: "pr_fmt" redefined [enabled by default] include/linux/printk.h:152:0: note: this is the location of the previous definition
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/scan.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/wireless/nl80211.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/mlme.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/ibss.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/sme.o CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/chan.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/wireless/ethtool.o
CC [M] /home/andy/kernel/compat-wireless-2011-11-22/net/wireless/mesh.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/wireless/wext-compat.o
CC [M]/home/andy/kernel/compat-wireless-2011-11-22/net/wireless/wext-sme.o
LD [M]/home/andy/kernel/compat-wireless-2011-11-22/net/wireless/cfg80211.o
Building modules, stage 2.
MODPOST 6 modules
CC /home/andy/kernel/compat-wireless-2011-11-22/compat/compat.mod.o
LD [M] /home/andy/kernel/compat-wireless-2011-11-22/compat/compat.ko
CC/home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/bcma.mod.o
LD [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/bcma.ko
CC/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/b43.mod.o
LD [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/b43.ko
CC/home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/ssb.mod.o
LD [M] /home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/ssb.ko
CC/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/mac80211.mod.o
LD [M]/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/mac80211.ko
CC/home/andy/kernel/compat-wireless-2011-11-22/net/wireless/cfg80211.mod.o
LD [M]/home/andy/kernel/compat-wireless-2011-11-22/net/wireless/cfg80211.ko
make[1]: Leaving directory `/usr/src/devel/3.1.2-1.1-desktop'
make -C /lib/modules/3.1.2-1.1-desktop/build M=/home/andy/kernel/compat-wireless-2011-11-22 "INSTALL_MOD_DIR=updates" \
modules_install
make[1]: Entering directory `/usr/src/devel/3.1.2-1.1-desktop'
INSTALL /home/andy/kernel/compat-wireless-2011-11-22/compat/compat.ko
INSTALL/home/andy/kernel/compat-wireless-2011-11-22/drivers/bcma/bcma.ko
INSTALL/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/b43.ko
INSTALL /home/andy/kernel/compat-wireless-2011-11-22/drivers/ssb/ssb.ko
INSTALL/home/andy/kernel/compat-wireless-2011-11-22/net/mac80211/mac80211.ko
INSTALL/home/andy/kernel/compat-wireless-2011-11-22/net/wireless/cfg80211.ko
DEPMOD 3.1.2-1-desktop
WARNING: /lib/modules/3.1.2-1-desktop/updates/net/wireless/cfg80211.ko needs unknown symbol rfkill_unregister
WARNING: /lib/modules/3.1.2-1-desktop/updates/net/wireless/cfg80211.ko needs unknown symbol rfkill_blocked
WARNING: /lib/modules/3.1.2-1-desktop/updates/net/wireless/cfg80211.ko needs unknown symbol rfkill_destroy
WARNING: /lib/modules/3.1.2-1-desktop/updates/net/wireless/cfg80211.ko needs unknown symbol rfkill_resume_polling
WARNING: /lib/modules/3.1.2-1-desktop/updates/net/wireless/cfg80211.ko needs unknown symbol rfkill_pause_polling
WARNING: /lib/modules/3.1.2-1-desktop/updates/net/wireless/cfg80211.ko needs unknown symbol rfkill_set_hw_state
WARNING: /lib/modules/3.1.2-1-desktop/updates/net/wireless/cfg80211.ko needs unknown symbol rfkill_alloc
WARNING: /lib/modules/3.1.2-1-desktop/updates/net/wireless/cfg80211.ko needs unknown symbol rfkill_register
WARNING: /lib/modules/3.1.2-1-desktop/updates/net/wireless/cfg80211.ko needs unknown symbol rfkill_set_sw_state
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol sdio_release_host
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol sdio_disable_func
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol sdio_set_block_size
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol pcmcia_disable_device
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol hwrng_unregister
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol sdio_claim_host
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol sdio_register_driver
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol pcmcia_unregister_driver
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol pcmcia_map_mem_page
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol hwrng_register
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol sdio_release_irq
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol sdio_unregister_driver
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol pcmcia_request_window
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol sdio_claim_irq
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol sdio_enable_func
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol pcmcia_register_driver
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/net/wireless/b43/b43.ko needs unknown symbol pcmcia_enable_device
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol sdio_release_host
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol sdio_claim_host
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol sdio_readw
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol sdio_writew
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol sdio_readsb
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol sdio_readl
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol pcmcia_write_config_byte
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol sdio_writel
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol sdio_writesb
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol pcmcia_read_config_byte
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol pcmcia_loop_tuple
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol sdio_readb
WARNING: /lib/modules/3.1.2-1-desktop/updates/drivers/ssb/ssb.ko needs unknown symbol sdio_writeb make[1]: *** [_emodinst_post] Error 1
make[1]: Leaving directory `/usr/src/devel/3.1.2-1.1-desktop'
make: *** [install-modules] Error 2
Any help here would be appreciated. Thanks in advance.
Andy Liebman
2011/11/28 AndrewL733 <[email protected]>:
Quoted 28 lines
Hi,
----------------------
I'm apologize in advance if this posting repeats another posting I made on 26 Nov. I submitted it but don't see it in the archives. I'm thinking it never arrived so I am sending it again.
-----------------------I'm wondering if anybody has any clues about why I cannot get a Broadcom 4331-based wireless device to work in my Macbook Pro (Model 8,2). When I try to load the driver with "modprobe b43" I get the following in dmesg:
[ 3279.117137] bcma-pci-bridge 0000:03:00.0: PCI INT A disabled [ 3281.301279] bcma-pci-bridge 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 3281.301297] bcma-pci-bridge 0000:03:00.0: setting latency timer to 64 [ 3281.301381] bcma: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x25, class 0x0) [ 3281.301405] bcma: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x1D, class 0x0) [ 3281.301459] bcma: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x13, class 0x0) [ 3281.301581] bcma: PMU resource config unknown for device 0x4331 [ 3281.301583] bcma: Enabling Ext PA lines not implemented [ 3281.310508] bcma: Bus registered [ 3281.312814] cfg80211: Calling CRDA to update world regulatory domain [ 3281.316215] b43-phy0: Broadcom 4331 WLAN found (core revision 29) [ 3281.316383] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 9, Type 7,
Quoted 1 line
Revision 1)
This seems to be standard HT PHY:
#define B43_PHYTYPE_HT 0x07
So your b43 must be compiled without support for HT.
Quoted 6 lines
CC [M]
/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/phy_ht.oCC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/tables_phy_ht.oCC [M]/home/andy/kernel/compat-wireless-2011-11-22/drivers/net/wireless/b43/radio_2059.o
Here we can see you compile b43 from compat-wireless with HT-PHY support. So there must be something wrong with the way you install compat-wireless.
I can give you some hints:
1) find -name "b43.ko" /lib/modules
2) modinfo b43
3) modinfo b43 | grep filename
But I don't know what exactly are you doing wrong.
Signature · 1 line
Rafał
W dniu 28 listopada 2011 16:59 użytkownik Rafał Miłecki
Quoted 2 lines · <[email protected]> napisał:
I can give you some hints:
1) find -name "b43.ko"/lib/modules
I meant
find /lib/modules -name "b43.ko"
Anyway, the problem lies in compat-wireless installation. I don't understand the following part:
make[1]: *** [_emodinst_post] Error 1
make[1]: Leaving directory `/usr/src/devel/3.1.2-1.1-desktop'
make: *** [install-modules] Error 2
(don't know where it comes from)
Signature · 1 line
Rafał
Quoted 8 lines · Rafał Miłecki
W dniu 28 listopada 2011 16:59 użytkownik Rafał Miłecki
Quoted 2 lines · <[email protected]> napisał:
I can give you some hints:
1) find -name "b43.ko"/lib/modulesI meant
find/lib/modules-name "b43.ko"
Quoted 6 lines
Anyway, the problem lies in compat-wireless installation. I don't understand the following part:
make[1]: *** [_emodinst_post] Error 1
make[1]: Leaving directory `/usr/src/devel/3.1.2-1.1-desktop'
make: *** [install-modules] Error 2
(don't know where it comes from)
It appears that your system is not building rfkill. Does it help if you add the following lines at the bottom of config.mk in the compat-wireless directory?
CONFIG_RFKILL=mCONFIG_RFKILL_LEDS=yCONFIG_RFKILL_INPUT=y
Larry
A message that is not in the archive (sent off-list or not yet received): [email protected]
2011/11/28 AndrewL733 <[email protected]>:
Quoted 9 lines
Hi,
Thanks for the suggestions. Nothing solving the problem so far.
I meant
find/lib/modules-name "b43.ko"What is the point of looking for b43.ko? It exists for my running kernel.
I believe b43.ko from compat-wireless should be put in some specific subdirectory, probably "extra". AFAIR it's /lib/modules/SOMEKERNEL/extra/...
If you can see only default b43.ko, it means compat-wireless didn't install successfully.
Signature · 1 line
Rafał
Quoted 9 lines · Rafał Miłecki
2011/11/28 AndrewL733<[email protected]>:
Quoted 8 lines
Hi,
Thanks for the suggestions. Nothing solving the problem so far.
I meant
find/lib/modules-name "b43.ko"
Quoted 8 lines
Quoted 1 line
What is the point of looking for b43.ko? It exists for my running kernel.
I believe b43.ko from compat-wireless should be put in some specific subdirectory, probably "extra". AFAIR it's
/lib/modules/SOMEKERNEL/extra/...If you can see only default b43.ko, it means compat-wireless didn't install successfully.
Thanks for your reply.
You are absolutely right. My Mandriva kernel's name is 3.1.2-1.1-desktop but the compat-wireless "make install" is installing everything in the directory /lib/modules/3.1.2-1-desktop/updates. The path is missing the ".1" before the "-desktop".
I'm not sure why this is happening. I am running a Mandriva kernel from "Cooker" (running Mandriva 2011, which comes with 2.6.38.x, but the Macbook Pro 8,2 DVD isn't recognized until the 3.1 kernel. I also compiled my own 3.2-rc3 kernel but then I can't get fglrx to work properly.
The joys of Macs and Linux..
But getting back to b43. How can I instruct "make install" to put the drivers in the correct path? I'm going to try to just copy everything to the correct place and run depmod and see what happens. Maybe that'll work??
Andy
Making Progress Re: Trouble with Macbook Pro 8,2 (broadcom 4331) and latest b43
Quoted 17 lines
Quoted 9 lines
Quoted 9 lines
Hi,
Thanks for the suggestions. Nothing solving the problem so far.
I meant
find/lib/modules-name "b43.ko"Quoted 8 lines
Quoted 1 line
What is the point of looking for b43.ko? It exists for my running kernel.
I believe b43.ko from compat-wireless should be put in some specific subdirectory, probably "extra". AFAIR it's
/lib/modules/SOMEKERNEL/extra/...If you can see only default b43.ko, it means compat-wireless didn't install successfully.
Quoted 8 lines
Thanks for your reply.
You are absolutely right. My Mandriva kernel's name is 3.1.2-1.1-desktop but the compat-wireless "make install" is installing everything in the directory
/lib/modules/3.1.2-1-desktop/updates. The install path is missing the ".1" before the "-desktop".
.....How can I instruct "make install" to put the drivers in the correct path? I'm going to try to just copy everything to the correct place and run depmod and see what happens. Maybe that'll work??
Andy
Okay, I copied the contents of /lib/modules/3.1.2-1-desktop/updates to /lib/modules/3.1.2-1.1-desktop/. I then renamed "updates" to "extra" and ran depmod. Now when I run "modinfo b43" it points to the new compat-wireless version of b43 instead of pointing to the distro version. When I LOAD b43, iwconfig shows a wlan0. So, we are making progress.
But now, to do things the "Mandriva way", I am supposed to launch the "Mandriva Control Center" (drakconf), go to the "Manage you network devices" section and "add" the wlan0 interface to my system. (The idea is to then allow Network Manager to manage the connection moving forward, but first you have to enable the connection.) When I try to add wlan0 to my network configuration, I get a dialog box asking me which firmware file to use? Basically, it wants me to navigate to /lib/firmware/b43/ and select one of the "ucode" files. With the previous Macbook Pro 8,2, I think I selected ucode13.fw and it worked fine. But what is the correct way to select the proper firmware without guessing?
When I was trying to load the "distro b43" driver, dmesg was telling me the driver needed "FW13". Does that mean anything?
Andy
Quoted 12 lines · On 11/29/2011 12:00 PM, AndrewL733 wrote:
Thanks for your reply.
You are absolutely right. My Mandriva kernel's name is 3.1.2-1.1-desktop but the compat-wireless "make install" is installing everything in the directory
/lib/modules/3.1.2-1-desktop/updates. The path is missing the ".1" before the "-desktop".I'm not sure why this is happening. I am running a Mandriva kernel from "Cooker" (running Mandriva 2011, which comes with 2.6.38.x, but the Macbook Pro 8,2 DVD isn't recognized until the 3.1 kernel. I also compiled my own 3.2-rc3 kernel but then I can't get fglrx to work properly.
Quoted 5 lines
The joys of Macs and Linux..
But getting back to b43. How can I instruct "make install" to put the drivers in the correct path? I'm going to try to just copy everything to the correct place and run depmod and see what happens. Maybe that'll work??
That path is derived from the current kernel version. It should get it right.
You should already have the directory /lib/modules/3.1.2-1.1-desktop. The command 'mv /lib/modules/3.1.2-1-desktop/updates to /lib/modules/3.1.2-1.1-desktop/.' followed by 'depmod -a' should be OK.
Larry
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 15 lines · On 11/29/2011 03:49 PM, AndrewL733 wrote:
Quoted 7 lines · Larry Finger
That path is derived from the current kernel version. It should get it right.
You should already have the directory
/lib/modules/3.1.2-1.1-desktop. The command 'mv/lib/modules/3.1.2-1-desktop/updatesto/lib/modules/3.1.2-1.1-desktop/.' followed by 'depmod -a' should be OK.Larry
I found that at least with Mandriva, simply putting the new b43 modules in
/lib/modules/{mykernel}/updates and then running depmod (or depmod -a) did not work. After doing that, when I ran "modinfo b43", the result was still pointing to the in-kernel b43 modules and not the one in "updates". However, renaming the "updates" directory to "extra" and then running "depmod" again DID work. So, putting out-of-kernel modules in a directory named "updates" did not work!
Quoted 6 lines
I have never seen out-of-kernel modules in "updates". I compile many out-of-kernel modules (Myricom, ATTO, 3ware, LSI, Intel) and their installers always, always, put the new modules in the "extra" directory and never in an "updates" directory.
Why does compat-wireless install these in the "updates" directory?
Because that works with MOST distros.
Quoted 12 lines
Quoted 12 lines
But now, to do things the "Mandriva way", I am supposed to launch the "Mandriva Control Center" (drakconf), go to the "Manage you network devices" section and "add" the wlan0 interface to my system. (The idea is to then allow Network Manager to manage the connection moving forward, but first you have to enable the connection.) When I try to add wlan0 to my network configuration, I get a dialog box asking me which firmware file to use? Basically, it wants me to navigate to
/lib/firmware/b43/and select one of the "ucode" files. With the previous Macbook Pro 8,2, I think I selected ucode13.fw and it worked fine. But what is the correct way to select the proper firmware without guessing?
Quoted 2 lines
Quoted 2 lines
When I was trying to load the "distro b43" driver, dmesg was telling me the driver needed "FW13". Does that mean anything?
No.
Quoted 8 lines
Okay, I got impatient and decided to just tell the Mandriva network device manager to associate
/lib/firmware/b43/ucode13.fwwith my wlan0. But how do I know if that's really the correct firmware for the Broadcom 4331 (rev 02) chipset? I'm finding that the wireless connection goes down once in a while. So far, I have only tried with one access point and maybe the access point itself is flaky, but it would be nice how to know which firmware to use. Is the choice supposed to happen automagically when the b43 driver is loaded? Is there some table somewhere that says which ucodeXX.fw goes with which chipset?
The table is found at http://bcm-v4.sipsolutions.net/802.11/Init/Firmware. For my distro and most others, it is done automagically. The kernel reads the version of the 802.11 core and looks up the firmware using logic derived from this table. In the dmesg output, you will find a place where the versions of the various cores is printed. Using ucode13.fw is certainly not right for a 4331. I'm surprised that it works at all.
Larry
2011/11/30 Larry Finger <[email protected]>:
Quoted 73 lines · On 11/29/2011 03:49 PM, AndrewL733 wrote:
Quoted 24 lines · Larry Finger
Quoted 9 lines
That path is derived from the current kernel version. It should get it right.
You should already have the directory
/lib/modules/3.1.2-1.1-desktop. The command 'mv/lib/modules/3.1.2-1-desktop/updatesto/lib/modules/3.1.2-1.1-desktop/.' followed by 'depmod -a' should be OK.Larry
I found that at least with Mandriva, simply putting the new b43 modules in
/lib/modules/{mykernel}/updates and then running depmod (or depmod -a) did not
work. After doing that, when I ran "modinfo b43", the result was still pointing
to the in-kernel b43 modules and not the one in "updates". However, renaming
the "updates" directory to "extra" and then running "depmod" again DID work.
So, putting out-of-kernel modules in a directory named "updates" did not work!Quoted 8 lines
I have never seen out-of-kernel modules in "updates". I compile many out-of-kernel modules (Myricom, ATTO, 3ware, LSI, Intel) and their installers
always, always, put the new modules in the "extra" directory and never in an
"updates" directory.Why does compat-wireless install these in the "updates" directory?
Because that works with MOST distros.
Quoted 18 lines
Quoted 18 lines
But now, to do things the "Mandriva way", I am supposed to launch the "Mandriva Control Center" (drakconf), go to the "Manage you network devices"
section and "add" the wlan0 interface to my system. (The idea is to then allow
Network Manager to manage the connection moving forward, but first you have to
enable the connection.) When I try to add wlan0 to my network configuration, I
get a dialog box asking me which firmware file to use? Basically, it wants me
to navigate to/lib/firmware/b43/and select one of the "ucode" files. With
the previous Macbook Pro 8,2, I think I selected ucode13.fw and it worked fine. But what is the correct way to select the proper firmware without guessing?Quoted 3 lines
Quoted 3 lines
When I was trying to load the "distro b43" driver, dmesg was telling me the
driver needed "FW13". Does that mean anything?No.
Quoted 4 lines
Okay, I got impatient and decided to just tell the Mandriva network device manager to associate
/lib/firmware/b43/ucode13.fwwith my wlan0. But how do I
know if that's really the correct firmware for the Broadcom 4331 (rev 02)Quoted 8 lines
chipset? I'm finding that the wireless connection goes down once in a while.
So far, I have only tried with one access point and maybe the access point itself is flaky, but it would be nice how to know which firmware to use. Is the
choice supposed to happen automagically when the b43 driver is loaded? Is there
some table somewhere that says which ucodeXX.fw goes with which chipset?
Quoted 6 lines
The table is found at http://bcm-v4.sipsolutions.net/802.11/Init/Firmware.
For my distro and most others, it is done automagically. The kernel reads the version of the 802.11 core and looks up the firmware using logic derived from this table. In the dmesg output, you will find a place where the versions of the various cores is printed. Using ucode13.fw is certainly not right for a 4331. I'm surprised that it works at all.
I'm quite sure it's some Mandriva... well - dumb... configuration that doesn't affect driver at all.
b43 uses ucode29_mimo for BCM4331
Signature · 1 line
Rafał
Quoted 10 lines · Rafał Miłecki
Quoted 6 lines
Quoted 6 lines
The table is found athttp://bcm-v4.sipsolutions.net/802.11/Init/Firmware. For my distro and most others, it is done automagically. The kernel reads the version of the 802.11 core and looks up the firmware using logic derived from this table. In the dmesg output, you will find a place where the versions of the various cores is printed. Using ucode13.fw is certainly not right for a 4331. I'm surprised that it works at all.
I'm quite sure it's some Mandriva... well - dumb... configuration that doesn't affect driver at all.
b43 uses
ucode29_mimofor BCM4331
Hello,
I am pleased to report that I got the 4331 chipset to work, thanks to your help, Rafal. Indeed, the correct firmware was ucode29_mimo. Larry, I'm not sure how I could find that out from the table you referred me to. The table doesn't directly say which firmware goes with 4331. It implies which goes with the HT phy, but then again, there are two listings for HT.
Anyway, is Mandriva supposed to have that table stored somewhere? Do they have an outdated version of the table (or should the table have been built with the kernel or driver). In my case, I installed an updated kernel that is more recent than the distro, so that could be the source of some of the problem. Then again, I needed the updated kernel to get DVD support on this machine.
Now I have one more problem. I'm not sure where it the best place to report this issue.
With Mandriva 2011, the distro switched from Mandriva's own "drakx-net-applet" to "networkmanager". With Network Manager, I can connect to my wireless router. However, the connection drops after a few minutes and it continually tries to renew, succeeds, drops, renews, succeeds, in an endless loop. I see many postings on various distro forums about similar problems with Network Manager. It seems to be that when there is a scan for new Access Points, the current connection drops.
After unininstalling Network Manager, I can now get a reliable connection to my office network by running
"iwconfig wlan0 essid mynetworkname", then
"wpa_supplicant -Dwext -i wlan0 -c /etc/wpa_supplicant.conf" (to not run in the background) "dhclient wlan0"
Now the connection is stable. The question is, why is it unstable with Network Manager? Any ideas? Is it related to the way Network Manager is working with the 4331 chipset? I have an identical Mandriva 2011 OS installed on a slightly older Macbook Pro 5,1 with the Broadcom 4322 chipset, also using the b43 driver, and Network Manager does not cause these disconnections. Is there another forum where it would be better to post this question?
Here are various outputs that may be relevant. Am I stable because scanning has somehow been disabled (output of wpa_supplicant says "Failed to initiate AP scan").
-------------------------
After "modprobe b43"
[ 253.681728] bcma-pci-bridge 0000:03:00.0: PCI INT A disabled [ 261.220288] bcma-pci-bridge 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 261.220304] bcma-pci-bridge 0000:03:00.0: setting latency timer to 64 [ 261.220385] Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x25, class 0x0) [ 261.220413] Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x1D, class 0x0) [ 261.220475] Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x13, class 0x0) [ 261.220619] PMU resource config unknown for device 0x4331 [ 261.268986] Bus registered [ 261.275824] cfg80211: Calling CRDA to update world regulatory domain [ 261.282877] cfg80211: World regulatory domain updated: [ 261.282880] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 261.282883] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 261.282885] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 261.282887] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 261.282889] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 261.282891] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 261.292595] b43-phy0: Broadcom 4331 WLAN found (core revision 29) [ 261.293318] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 261.293635] Broadcom 43xx driver loaded [ Features: PMNLS ] [ 291.326731] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) [ 291.366628] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 291.395832] NET: Registered protocol family 17
After running "iwconfig wlan0 essid mynetworkname" wpa_supplicant (output below) plus "dhclient wlan0"
[ 292.520204] wlan0: authenticate with 48:5b:39:5b:67:27 (try 1) [ 292.521879] wlan0: authenticated [ 292.522267] wlan0: associate with 48:5b:39:5b:67:27 (try 1) [ 292.524671] wlan0: RX AssocResp from 48:5b:39:5b:67:27 (capab=0x411 status=0 aid=7) [ 292.524674] wlan0: associated [ 292.525629] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 302.842854] wlan0: no IPv6 routers present
[root@andynewmac andy]# wpa_supplicant -Dwext -i wlan0 -c /etc/wpa_supplicant.conf ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412 MHz) Associated with 48:5b:39:5b:67:27
WPA: Key negotiation completed with 48:5b:39:5b:67:27 [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 48:5b:39:5b:67:27 completed (auth) [id=1 id_str=]
Andy
Quoted 41 lines · On Fri, 2011-12-02 at 13:13 -0500, AndrewL733 wrote:
Quoted 10 lines · Rafał Miłecki
Quoted 6 lines
Quoted 6 lines
The table is found athttp://bcm-v4.sipsolutions.net/802.11/Init/Firmware. For my distro and most others, it is done automagically. The kernel reads the version of the 802.11 core and looks up the firmware using logic derived from this table. In the dmesg output, you will find a place where the versions of the various cores is printed. Using ucode13.fw is certainly not right for a 4331. I'm surprised that it works at all.
I'm quite sure it's some Mandriva... well - dumb... configuration that doesn't affect driver at all.
b43 uses
ucode29_mimofor BCM4331Hello,
I am pleased to report that I got the 4331 chipset to work, thanks to your help, Rafal. Indeed, the correct firmware was
ucode29_mimo. Larry, I'm not sure how I could find that out from the table you referred me to. The table doesn't directly say which firmware goes with 4331. It implies which goes with the HT phy, but then again, there are two listings for HT.Anyway, is Mandriva supposed to have that table stored somewhere? Do they have an outdated version of the table (or should the table have been built with the kernel or driver). In my case, I installed an updated kernel that is more recent than the distro, so that could be the source of some of the problem. Then again, I needed the updated kernel to get DVD support on this machine.
Now I have one more problem. I'm not sure where it the best place to report this issue.
With Mandriva 2011, the distro switched from Mandriva's own "drakx-net-applet" to "networkmanager". With Network Manager, I can connect to my wireless router. However, the connection drops after a few minutes and it continually tries to renew, succeeds, drops, renews, succeeds, in an endless loop. I see many postings on various distro forums about similar problems with Network Manager. It seems to be that when there is a scan for new Access Points, the current connection drops.
After unininstalling Network Manager, I can now get a reliable connection to my office network by running
Quoted 8 lines
"iwconfig wlan0 essid mynetworkname", then
"wpa_supplicant-Dwext -i wlan0 -c/etc/wpa_supplicant.conf" (to not run in the background)
"dhclient wlan0"Now the connection is stable. The question is, why is it unstable with Network Manager? Any ideas? Is it related to the way Network Manager is working with the 4331 chipset? I have an identical Mandriva 2011 OS
There have in the past been issues with the periodic scanning that NM uses, but if there are these issues, they are purely driver bugs. A driver that cannot perform a scan while connected, and automatically re-establish that connection after the scan is broken and should be fixed. This has not been a problem with the existing drivers, but might be when support for a new driver or chipset is added to the kernel. It just takes a bit of time to work out all the bugs.
Quoted 4 lines
installed on a slightly older Macbook Pro 5,1 with the Broadcom 4322 chipset, also using the b43 driver, and Network Manager does not cause these disconnections. Is there another forum where it would be better to post this question?
Given that it's a problem on 4331 and not on 4322 probably points to the driver, and thus this is the correct place to discuss it for now.
If you see scan failures, that could be a problem, and it certainly causes latency in connecting to the AP. One thing to do to debug NetworkManager is to:
1) stop NM
2) killall -TERM wpa_supplicant
3) wpa_supplicant -dddtu
4) start NM again
and then grab the supplicants debug output (there will be a lot of it) and see what's going on with the supplicant when the connection drops, and why it cannot be re-established automatically.
Dan
Quoted 74 lines
Here are various outputs that may be relevant. Am I stable because scanning has somehow been disabled (output of
wpa_supplicantsays "Failed to initiate AP scan").
-------------------------After "modprobe b43"
[ 253.681728] bcma-pci-bridge 0000:03:00.0: PCI INT A disabled [ 261.220288] bcma-pci-bridge 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 261.220304] bcma-pci-bridge 0000:03:00.0: setting latency timer to 64 [ 261.220385] Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x25, class 0x0) [ 261.220413] Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x1D, class 0x0) [ 261.220475] Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x13, class 0x0) [ 261.220619] PMU resource config unknown for device 0x4331 [ 261.268986] Bus registered [ 261.275824] cfg80211: Calling CRDA to update world regulatory domain [ 261.282877] cfg80211: World regulatory domain updated: [ 261.282880] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 261.282883] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 261.282885] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 261.282887] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 261.282889] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 261.282891] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 261.292595] b43-phy0: Broadcom 4331 WLAN found (core revision 29) [ 261.293318] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 261.293635] Broadcom 43xx driver loaded [ Features: PMNLS ] [ 291.326731] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) [ 291.366628] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 291.395832] NET: Registered protocol family 17After running "iwconfig wlan0 essid mynetworkname"
wpa_supplicant(output below) plus "dhclient wlan0"[ 292.520204] wlan0: authenticate with 48:5b:39:5b:67:27 (try 1) [ 292.521879] wlan0: authenticated [ 292.522267] wlan0: associate with 48:5b:39:5b:67:27 (try 1) [ 292.524671] wlan0: RX AssocResp from 48:5b:39:5b:67:27 (capab=0x411 status=0 aid=7) [ 292.524674] wlan0: associated [ 292.525629] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 302.842854] wlan0: no IPv6 routers present[root@andynewmac andy]#
wpa_supplicant-Dwext -i wlan0 -c/etc/wpa_supplicant.conf
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412 MHz)
Associated with 48:5b:39:5b:67:27
WPA: Key negotiation completed with 48:5b:39:5b:67:27 [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 48:5b:39:5b:67:27 completed (auth) [id=1 id_str=]Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi
Quoted 9 lines
After unininstalling Network Manager, I can now get a reliable connection to my office network by running
"iwconfig wlan0 essid mynetworkname", then
"wpa_supplicant-Dwext -i wlan0 -c/etc/wpa_supplicant.conf" (to not run in the background) "dhclient wlan0"Now the connection is stable. The question is, why is it unstable with Network Manager? Any ideas? Is it related to the way Network Manager is working with the 4331 chipset? I have an identical Mandriva 2011 OS installed on a slightly older Macbook Pro 5,1 with the Broadcom 4322 chipset, also using the b43 driver, and Network Manager does not cause these disconnections. Is there another forum where it would be better to post this question?
The problem is definitely with Network Manager. Re-installing Network Manager causes the same disconnection problem again, even when running wpa_supplicant manually. Who should I report this to?
wpa on the command line:
[root@andynewmac andy]# wpa_supplicant -Dwext -i wlan0 -c /etc/wpa_supplicant.conf CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0 ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412 MHz) Associated with 48:5b:39:5b:67:27
WPA: Key negotiation completed with 48:5b:39:5b:67:27 [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 48:5b:39:5b:67:27 completed (auth) [id=1 id_str=] CTRL-EVENT-DISCONNECTED bssid=48:5b:39:5b:67:27 reason=0 ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412 MHz) Associated with 48:5b:39:5b:67:27
WPA: Key negotiation completed with 48:5b:39:5b:67:27 [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 48:5b:39:5b:67:27 completed (reauth) [id=1 id_str=] CTRL-EVENT-DISCONNECTED bssid=48:5b:39:5b:67:27 reason=0 ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412 MHz) Associated with 48:5b:39:5b:67:27
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Could not verify EAPOL-Key MIC - dropping packet
Authentication with 48:5b:39:5b:67:27 timed out.
CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412 MHz) Associated with 48:5b:39:5b:67:27
WPA: Key negotiation completed with 48:5b:39:5b:67:27 [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 48:5b:39:5b:67:27 completed (reauth) [id=1 id_str=]
In /var/log/messages:
Dec 2 18:47:06 andynewmac kernel: [ 211.957785] cfg80211: Calling CRDA to update world regulatory domain Dec 2 18:47:06 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: completed -> disconnected Dec 2 18:47:06 andynewmac kernel: [ 211.961641] cfg80211: World regulatory domain updated: Dec 2 18:47:06 andynewmac kernel: [ 211.961643] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Dec 2 18:47:06 andynewmac kernel: [ 211.961646] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:06 andynewmac kernel: [ 211.961648] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:06 andynewmac kernel: [ 211.961650] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:06 andynewmac kernel: [ 211.961651] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:06 andynewmac kernel: [ 211.961653] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:06 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:06 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:07 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:07 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:07 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> associating Dec 2 18:47:07 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: associating -> associated Dec 2 18:47:07 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: associated -> 4-way handshake Dec 2 18:47:08 andynewmac kernel: [ 213.594392] cfg80211: Calling CRDA to update world regulatory domain Dec 2 18:47:08 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: 4-way handshake -> disconnected Dec 2 18:47:08 andynewmac kernel: [ 213.598387] cfg80211: World regulatory domain updated: Dec 2 18:47:08 andynewmac kernel: [ 213.598390] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Dec 2 18:47:08 andynewmac kernel: [ 213.598392] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:08 andynewmac kernel: [ 213.598394] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:08 andynewmac kernel: [ 213.598396] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:08 andynewmac kernel: [ 213.598398] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:08 andynewmac kernel: [ 213.598400] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:08 andynewmac avahi-daemon[2391]: Interface wlan0.IPv4 no longer relevant for mDNS. Dec 2 18:47:08 andynewmac avahi-daemon[2391]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.42.66.138. Dec 2 18:47:08 andynewmac dhclient: receive_packet failed on wlan0: Network is down Dec 2 18:47:08 andynewmac avahi-daemon[2391]: Withdrawing address record for 10.42.66.138 on wlan0. Dec 2 18:47:08 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:08 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:09 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:09 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:10 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:10 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:11 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:11 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:12 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:12 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:12 andynewmac NetworkManager[2513]: <info> (wlan0): roamed from BSSID 48:5B:39:5B:67:27 (es-network2) to (none) ((none)) Dec 2 18:47:13 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:13 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:14 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:14 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:14 andynewmac drakconf.real[9067]: ### Program is starting ### Dec 2 18:47:15 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:15 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:16 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:16 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:17 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:17 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:18 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:18 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:18 andynewmac drakconf.real[9354]: ### Program is starting ### Dec 2 18:47:19 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:19 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:20 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:20 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:21 andynewmac rpmdrake[9366]: ### Program is starting ### Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 8 -> 3 (reason 11) Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): deactivating device (reason: 11). Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 8334 Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): removing resolv.conf from /sbin/resolvconf Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) starting connection 'System es-network2' Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 3 -> 4 (reason 0) Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 4 -> 5 (reason 0) Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): bringing up device. Dec 2 18:47:22 andynewmac kernel: [ 227.305220] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) Dec 2 18:47:22 andynewmac kernel: [ 227.345070] ADDRCONF(NETDEV_UP): wlan0: link is not ready Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0/wireless): access point 'System es-network2' has security, but secrets are required. Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 5 -> 6 (reason 0) Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 6 -> 4 (reason 0) Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 4 -> 5 (reason 0) Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0/wireless): connection 'System es-network2' has security, and secrets exist. No new secrets needed. Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: added 'ssid' value 'es-network2' Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: added 'scan_ssid' value '1' Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: added 'psk' value '<omitted>' Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: added 'proto' value 'WPA RSN' Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: set interface ap_scan to 1 Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:22 andynewmac rpmdrake[9366]: opening the RPM database Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> associating Dec 2 18:47:23 andynewmac kernel: [ 228.848305] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: associating -> associated Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: associated -> 4-way handshake Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: 4-way handshake -> group handshake Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: group handshake -> completed Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'es-network2'. Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 5 -> 7 (reason 0) Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds) Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> dhclient started with pid 9446 Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Dec 2 18:47:23 andynewmac dhclient: Internet Systems Consortium DHCP Client 4.2.1-P1 Dec 2 18:47:23 andynewmac dhclient: Copyright 2004-2011 Internet Systems Consortium. Dec 2 18:47:23 andynewmac dhclient: All rights reserved. Dec 2 18:47:23 andynewmac dhclient: For info, please visit https://www.isc.org/software/dhcp/ Dec 2 18:47:23 andynewmac dhclient: Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): DHCPv4 state changed nbi -> preinit Dec 2 18:47:23 andynewmac dhclient: Listening on LPF/wlan0/68:a8:6d:24:e7:0a Dec 2 18:47:23 andynewmac dhclient: Sending on LPF/wlan0/68:a8:6d:24:e7:0a Dec 2 18:47:23 andynewmac dhclient: Sending on Socket/fallback Dec 2 18:47:23 andynewmac dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Dec 2 18:47:23 andynewmac dhclient: DHCPACK from 10.42.66.1 Dec 2 18:47:23 andynewmac dhclient: bound to 10.42.66.138 -- renewal in 127382 seconds. Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): DHCPv4 state changed preinit -> reboot Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled... Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started... Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> address 10.42.66.138 Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> prefix 24 (255.255.255.0) Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> gateway 10.42.66.1 Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> hostname 'andynewmac' Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> nameserver '10.42.66.1' Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> domain name 'editshare.boston' Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Scheduling stage 5 Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Done scheduling stage 5 Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete. Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... Dec 2 18:47:23 andynewmac avahi-daemon[2391]: Joining mDNS multicast group on interface wlan0.IPv4 with address 10.42.66.138. Dec 2 18:47:23 andynewmac avahi-daemon[2391]: New relevant interface wlan0.IPv4 for mDNS. Dec 2 18:47:23 andynewmac avahi-daemon[2391]: Registering new address record for 10.42.66.138 on wlan0.IPv4. Dec 2 18:47:24 andynewmac NetworkManager[2513]: <info> (wlan0): writing resolv.conf to /sbin/resolvconf Dec 2 18:47:24 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 7 -> 8 (reason 0) Dec 2 18:47:24 andynewmac NetworkManager[2513]: <info> Policy set 'System es-network2' (wlan0) as default for IPv4 routing and DNS. Dec 2 18:47:24 andynewmac NetworkManager[2513]: <info> Activation (wlan0) successful, device activated. Dec 2 18:47:24 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Quoted 18 lines · On Fri, 2011-12-02 at 14:06 -0500, AndrewL733 wrote:
Hi
Quoted 9 lines
After unininstalling Network Manager, I can now get a reliable connection to my office network by running
"iwconfig wlan0 essid mynetworkname", then "
wpa_supplicant-Dwext -i wlan0 -c/etc/wpa_supplicant.conf" (to not run in the background)
"dhclient wlan0"Quoted 8 lines
Now the connection is stable. The question is, why is it unstable with Network Manager? Any ideas? Is it related to the way Network Manager is working with the 4331 chipset? I have an identical Mandriva 2011 OS installed on a slightly older Macbook Pro 5,1 with the Broadcom 4322 chipset, also using the b43 driver, and Network Manager does not cause these disconnections. Is there another forum where it would be better to post this question?
Quoted 3 lines
The problem is definitely with Network Manager. Re-installing Network Manager causes the same disconnection problem again, even when running
wpa_supplicantmanually. Who should I report this to?
See my other mail on this... it's not really NM, but I believe it's a bug in the driver exposed by some behavior that NM has that static wpa_supplicant does not. You should be able to trigger the same behavior by periodically executing 'iwlist wlan0 scan' on the command line, or by asking wpa_supplicant to scan by using wpa_cli.
Grabbing more debugging info using "-dddt" as arguments to the supplicant would help.
Also, are you sure your manually started copy of wpa_supplicant is the only copy that's running?
Quoted 9 lines
wpa on the command line:
[root@andynewmac andy]#
wpa_supplicant-Dwext -i wlan0 -c/etc/wpa_supplicant.conf
CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0 ioctl[SIOCSIWSCAN]: Device or resource busy Failed to initiate AP scan.
ioctl[SIOCSIWSCAN]: Device or resource busy Failed to initiate AP scan.
These aren't necessarily a good start, though sometimes they are expected.
Quoted 11 lines
Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412 MHz)
Associated with 48:5b:39:5b:67:27
WPA: Key negotiation completed with 48:5b:39:5b:67:27 [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 48:5b:39:5b:67:27 completed (auth) [id=1 id_str=]
CTRL-EVENT-DISCONNECTED bssid=48:5b:39:5b:67:27 reason=0 ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
There's not enough debugging output from the supplicant to figure out why the disconnect event occurred though. That's the real reason there are problems here. WEXT doesn't give us enough information about why the disconnect occurred. Instead of using "-Dwext", can you use "-Dnl80211" instead? WEXT is an old API and is replaced by nl80211, which gives us much more usable information.
Dan
Quoted 312 lines
Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412 MHz)
Associated with 48:5b:39:5b:67:27
WPA: Key negotiation completed with 48:5b:39:5b:67:27 [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 48:5b:39:5b:67:27 completed (reauth) [id=1 id_str=]
CTRL-EVENT-DISCONNECTED bssid=48:5b:39:5b:67:27 reason=0 ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412 MHz)
Associated with 48:5b:39:5b:67:27
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Could not verify EAPOL-Key MIC - dropping packet Authentication with 48:5b:39:5b:67:27 timed out. CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0 Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412 MHz)
Associated with 48:5b:39:5b:67:27
WPA: Key negotiation completed with 48:5b:39:5b:67:27 [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 48:5b:39:5b:67:27 completed (reauth) [id=1 id_str=]In
/var/log/messages:Dec 2 18:47:06 andynewmac kernel: [ 211.957785] cfg80211: Calling CRDA to update world regulatory domain Dec 2 18:47:06 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: completed -> disconnected Dec 2 18:47:06 andynewmac kernel: [ 211.961641] cfg80211: World regulatory domain updated: Dec 2 18:47:06 andynewmac kernel: [ 211.961643] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Dec 2 18:47:06 andynewmac kernel: [ 211.961646] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:06 andynewmac kernel: [ 211.961648] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:06 andynewmac kernel: [ 211.961650] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:06 andynewmac kernel: [ 211.961651] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:06 andynewmac kernel: [ 211.961653] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:06 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:06 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:07 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:07 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:07 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> associating Dec 2 18:47:07 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: associating -> associated Dec 2 18:47:07 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: associated -> 4-way handshake Dec 2 18:47:08 andynewmac kernel: [ 213.594392] cfg80211: Calling CRDA to update world regulatory domain Dec 2 18:47:08 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: 4-way handshake -> disconnected Dec 2 18:47:08 andynewmac kernel: [ 213.598387] cfg80211: World regulatory domain updated: Dec 2 18:47:08 andynewmac kernel: [ 213.598390] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Dec 2 18:47:08 andynewmac kernel: [ 213.598392] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:08 andynewmac kernel: [ 213.598394] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:08 andynewmac kernel: [ 213.598396] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:08 andynewmac kernel: [ 213.598398] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:08 andynewmac kernel: [ 213.598400] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Dec 2 18:47:08 andynewmac avahi-daemon[2391]: Interface wlan0.IPv4 no longer relevant for mDNS. Dec 2 18:47:08 andynewmac avahi-daemon[2391]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.42.66.138. Dec 2 18:47:08 andynewmac dhclient: receive_packet failed on wlan0: Network is down Dec 2 18:47:08 andynewmac avahi-daemon[2391]: Withdrawing address record for 10.42.66.138 on wlan0. Dec 2 18:47:08 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:08 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:09 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:09 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:10 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:10 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:11 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:11 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:12 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:12 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:12 andynewmac NetworkManager[2513]: <info> (wlan0): roamed from BSSID 48:5B:39:5B:67:27 (es-network2) to (none) ((none)) Dec 2 18:47:13 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:13 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:14 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:14 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:14 andynewmac drakconf.real[9067]: ### Program is starting ### Dec 2 18:47:15 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:15 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:16 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:16 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:17 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:17 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:18 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:18 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:18 andynewmac drakconf.real[9354]: ### Program is starting ### Dec 2 18:47:19 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:19 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:20 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:20 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:21 andynewmac rpmdrake[9366]: ### Program is starting ### Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> disconnected Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 8 -> 3 (reason 11) Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): deactivating device (reason: 11). Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 8334 Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): removing resolv.conf from /sbin/resolvconf Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) starting connection 'System es-network2' Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 3 -> 4 (reason 0) Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 4 -> 5 (reason 0) Dec 2 18:47:21 andynewmac NetworkManager[2513]: <info> (wlan0): bringing up device. Dec 2 18:47:22 andynewmac kernel: [ 227.305220] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07) Dec 2 18:47:22 andynewmac kernel: [ 227.345070] ADDRCONF(NETDEV_UP): wlan0: link is not ready Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0/wireless): access point 'System es-network2' has security, but secrets are required. Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 5 -> 6 (reason 0) Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 6 -> 4 (reason 0) Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 4 -> 5 (reason 0) Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0/wireless): connection 'System es-network2' has security, and secrets exist. No new secrets needed. Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: added 'ssid' value 'es-network2' Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: added 'scan_ssid' value '1' Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: added 'psk' value '<omitted>' Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: added 'proto' value 'WPA RSN' Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> Config: set interface ap_scan to 1 Dec 2 18:47:22 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: disconnected -> scanning Dec 2 18:47:22 andynewmac rpmdrake[9366]: opening the RPM database Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: scanning -> associating Dec 2 18:47:23 andynewmac kernel: [ 228.848305] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: associating -> associated Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: associated -> 4-way handshake Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: 4-way handshake -> group handshake Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): supplicant connection state: group handshake -> completed Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'es-network2'. Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 5 -> 7 (reason 0) Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds) Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> dhclient started with pid 9446 Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Dec 2 18:47:23 andynewmac dhclient: Internet Systems Consortium DHCP Client 4.2.1-P1 Dec 2 18:47:23 andynewmac dhclient: Copyright 2004-2011 Internet Systems Consortium. Dec 2 18:47:23 andynewmac dhclient: All rights reserved. Dec 2 18:47:23 andynewmac dhclient: For info, please visit https://www.isc.org/software/dhcp/ Dec 2 18:47:23 andynewmac dhclient: Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): DHCPv4 state changed nbi -> preinit Dec 2 18:47:23 andynewmac dhclient: Listening on LPF/wlan0/68:a8:6d:24:e7:0a Dec 2 18:47:23 andynewmac dhclient: Sending on LPF/wlan0/68:a8:6d:24:e7:0a Dec 2 18:47:23 andynewmac dhclient: Sending on Socket/fallback Dec 2 18:47:23 andynewmac dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Dec 2 18:47:23 andynewmac dhclient: DHCPACK from 10.42.66.1 Dec 2 18:47:23 andynewmac dhclient: bound to 10.42.66.138 -- renewal in 127382 seconds. Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> (wlan0): DHCPv4 state changed preinit -> reboot Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled... Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started... Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> address 10.42.66.138 Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> prefix 24 (255.255.255.0) Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> gateway 10.42.66.1 Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> hostname 'andynewmac' Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> nameserver '10.42.66.1' Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> domain name 'editshare.boston' Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Scheduling stage 5 Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Done scheduling stage 5 Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete. Dec 2 18:47:23 andynewmac NetworkManager[2513]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... Dec 2 18:47:23 andynewmac avahi-daemon[2391]: Joining mDNS multicast group on interface wlan0.IPv4 with address 10.42.66.138. Dec 2 18:47:23 andynewmac avahi-daemon[2391]: New relevant interface wlan0.IPv4 for mDNS. Dec 2 18:47:23 andynewmac avahi-daemon[2391]: Registering new address record for 10.42.66.138 on wlan0.IPv4. Dec 2 18:47:24 andynewmac NetworkManager[2513]: <info> (wlan0): writing resolv.conf to /sbin/resolvconf Dec 2 18:47:24 andynewmac NetworkManager[2513]: <info> (wlan0): device state change: 7 -> 8 (reason 0) Dec 2 18:47:24 andynewmac NetworkManager[2513]: <info> Policy set 'System es-network2' (wlan0) as default for IPv4 routing and DNS. Dec 2 18:47:24 andynewmac NetworkManager[2513]: <info> Activation (wlan0) successful, device activated. Dec 2 18:47:24 andynewmac NetworkManager[2513]: <info> Activation(wlan0) Stage 5 of 5 (IP Configure Commit) complete.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi
Quoted 8 lines
See my other mail on this... it's not really NM, but I believe it's a bug in the driver exposed by some behavior that NM has that static
wpa_supplicantdoes not. You should be able to trigger the same behavior by periodically executing 'iwlist wlan0 scan' on the command line, or by askingwpa_supplicantto scan by usingwpa_cli.Grabbing more debugging info using "-dddt" as arguments to the supplicant would help.
Sure, I will do that
Quoted 3 lines
Also, are you sure your manually started copy of
wpa_supplicantis the only copy that's running?
Yes, I'm sure. I did "ps aux | grep wpa" before starting wpa_supplicant.
Quoted 23 lines
Quoted 9 lines
wpa on the command line:
[root@andynewmac andy]#
wpa_supplicant-Dwext -i wlan0 -c/etc/wpa_supplicant.conf
CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0 ioctl[SIOCSIWSCAN]: Device or resource busy Failed to initiate AP scan.
ioctl[SIOCSIWSCAN]: Device or resource busy Failed to initiate AP scan.These aren't necessarily a good start, though sometimes they are expected.
Quoted 11 lines
Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412 MHz)
Associated with 48:5b:39:5b:67:27
WPA: Key negotiation completed with 48:5b:39:5b:67:27 [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 48:5b:39:5b:67:27 completed (auth) [id=1 id_str=]
CTRL-EVENT-DISCONNECTED bssid=48:5b:39:5b:67:27 reason=0 ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
ioctl[SIOCSIWSCAN]: Device or resource busy
Failed to initiate AP scan.
Quoted 6 lines
There's not enough debugging output from the supplicant to figure out why the disconnect event occurred though. That's the real reason there are problems here. WEXT doesn't give us enough information about why the disconnect occurred. Instead of using "-Dwext", can you use "-Dnl80211" instead? WEXT is an old API and is replaced by nl80211, which gives us much more usable information.
Will try and report back.
Quoted 3 lines
Dan
Andy