I was connecting to my AP when suddenly Networkmanager crashed. I tried three-four times and everytime it did crash. Even restarting the deamon didn't help neither restarting hald+NetworkManager. Actually I'm connecting through init script (wpa_supplicant.conf). Reproducible: Sometimes Steps to Reproduce: I haven't found a way to reproduce the errors. It happened a couple of times in a row (and sometimes when I boot my system up it happens). Actual Results: Results in NM crash (see attachment for the logs) Expected Results: NM should complete all the 5 steps instead of crashing at step 2. Nothing was running, only gnome with anything else (dropbox too, I got the applet in the tray). My computer is a Macbook 3,1 so the wifi card is a "02:00.0 Network controller: Broadcom Corporation Device 4328 (rev 03)" actually running with ndiswrapper. ndiswrapper version 1.53 loaded (smp=yes, preempt=yes) ndiswrapper: driver bcmwl5 (Broadcom,01/08/2007, 4.80.75.0) loaded Emerge --info: whitebox emesene # emerge --info Portage 2.1.6.4 (default/linux/x86/2008.0/desktop, gcc-4.1.2, glibc-2.6.1-r0, 2.6.27-gentoo-r7 i686) ================================================================= System uname: Linux-2.6.27-gentoo-r7-i686-Intel-R-_Core-TM-2_Duo_CPU_T7300_@_2.00GHz-with-glibc2.0 Timestamp of tree: Wed, 07 Jan 2009 10:00:02 +0000 app-shells/bash: 3.2_p39 dev-java/java-config: 1.3.7-r1, 2.1.6-r1 dev-lang/python: 2.5.2-r7 dev-util/cmake: 2.4.6-r1 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.63 sys-devel/automake: 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=nocona -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-O2 -march=nocona -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="it_IT.UTF-8" LC_ALL="it_IT.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="it en" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="/ X acl acpi alsa berkdb bluetooth branding bzip2 cairo cdr cli cracklib crypt cups dbus dri dvd dvdr dvdread eds emboss encode esd evo firefox flac fortran gdbm gif gnome gpm gstreamer gtk hal hddtemp iconv imap ipod ipv6 isdnlog jpeg kde kerberos libnotify lm_sensors mad midi mikmod mp3 mpeg mudflap ncurses nls nptl nptlonly nsplugin ogg opengl openmp pam pcre pdf perl png ppds pppd python qt3 qt3support qt4 quicktime readline reflection samba sdl session spell spl ssl startup-notification svg sysfs tcpd tiff truetype unicode usb vorbis win32codecs x86 xml xorg xulrunner xv zlib" ALSA_CARDS="hda-intel" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse synaptics evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="it en" USERLAND="GNU" VIDEO_CARDS="intel vesa" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Created attachment 177742 [details] Networkmanager metalog's log (/var/log/everything/current ) Hope this could help
Hi Fabiano, It seems this issue it not NetworkManager related. From your log: Jan 8 10:38:46 [NetworkManager] <info> Activation (wlan0/wireless): association took too long (>20s), failing activation._ Jan 8 10:38:46 [NetworkManager] <info> Activation (wlan0) failed for access point (homewifi)_ Jan 8 10:38:46 [NetworkManager] <info> Activation (wlan0) failed._ Jan 8 10:38:46 [NetworkManager] <info> Deactivating device wlan0._ Jan 8 10:38:46 [NetworkManager] <info> Activation (wlan0) failure scheduled..._ it seems NM instructed wpa_supplicant to associate with AP. wpa_supplicant passed that request to driver, but driver didn't achieve it in requested time. It's clearly driver problem. I would suggest you could give native b43 driver a change. I'm pretty sure your results will be much better. This driver is included in kernel you're using. If you need any further help regarding this issue, please let me know.
Hi Robert, thanks for replying. Unforunately Broadcom 4328 isn't supported (yet, I hope) by the current version of driver (linuxwireless.org). Anyway, I tried to use the built-in kernel driver but it didn't work. The only way is through ndiswrapper. I know it's a pain in the ass but better than nothing. But this made me think about a thing.. I've noticed that this bug appears only when my system crashes. I mean, today it crashed twice (becouse of X issues :P) and in both of them situations I had to switch to "/etc/init.d/net.wlan0 start" configured manually with wpa_supplicant. Moreover I had to type "ifconfig wlan0 up" otherwise neither that way would have worked. (omg sorry for this ugly sentence, I'm not English .. ) Is it possible that, after a crash, the device needs to be "esplicitally awakened"? Maybe this could be the right track. Let me know if you need more tests.
(In reply to comment #3) > Hi Robert, > thanks for replying. > > Unforunately Broadcom 4328 isn't supported (yet, I hope) by the current version > of driver (linuxwireless.org). > > Anyway, I tried to use the built-in kernel driver but it didn't work. > The only way is through ndiswrapper. I know it's a pain in the ass but better > than nothing. > I could swear I've got network card on the same chip (hmm or maybe I'm wrong and it was 4318... can't remember) in one of the machines on my network and it works ok with b43 driver. b43 officially doesn't support 4328 yet though. > Moreover I had to type "ifconfig wlan0 up" otherwise neither that way would > have worked. (omg sorry for this ugly sentence, I'm not English .. ) ndiswrapper is a doggy hack to get windows drivers up and running. But I have to admit it does great job. It still has many problems. > Is it possible that, after a crash, the device needs to be "esplicitally > awakened"? Maybe this could be the right track. I had similar experience with ndiswrapper. In my case crash wasn't required for card to stop working. It could die just out of the blue. No reason - nothing. The only way to get it back was to remove ndiswrapper module (which _very often_ ended up with system crash) and modprobe it again. My conclusion is - never use it, until there is no alternative. after few minutes of googleing I found this: http://www.broadcom.com/support/802.11/linux_sta.php read some reports it works with 4328
(In reply to comment #4) > My conclusion is - never use it, until there is no alternative. > > after few minutes of googleing I found this: > http://www.broadcom.com/support/802.11/linux_sta.php > read some reports it works with 4328 > Thanks for the link. I tried to install these driver and with it I can see my wlan0. The problems come when I try to connect to the wifi (that's encrypted in WPA/PSK pairwise TKIP). Networkmanager gives me these errors: an 10 02:01:01 [kernel] wl 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Jan 10 02:01:01 [kernel] eth1: Broadcom BCM4328 802.11 Wireless Controller 5.10.27.12 Jan 10 02:01:01 [kernel] udev: renamed network interface eth1 to wlan0 Jan 10 02:01:01 [rc-scripts] net.wlan0 is not allowed to be hotplugged Jan 10 02:01:01 [NetworkManager] nm_ip4_config_set_hostname: assertion `config != NULL' failed Jan 10 02:01:01 [NetworkManager] <info> wlan0: Device is fully-supported using driver '(null)'._ Jan 10 02:01:01 [NetworkManager] <info> wlan0: driver does not support SSID scans (scan_capa 0x00)._ Jan 10 02:01:01 [NetworkManager] <info> nm_device_init(): waiting for device's worker thread to start_ Jan 10 02:01:01 [NetworkManager] <info> nm_device_init(): device's worker thread started, continuing._ Jan 10 02:01:01 [NetworkManager] <info> Now managing wireless (802.11) device 'wlan0'._ Jan 10 02:01:01 [NetworkManager] <info> Deactivating device wlan0._ Jan 10 02:01:03 [NetworkManager] <WARN> nm_device_802_11_wireless_set_wep_enc_key(): error setting key for device wlan0: Invalid argument_ Jan 10 02:01:11 [NetworkManager] <WARN> request_and_convert_scan_results(): unknown error, or the card returned too much scan info: Invalid argument_ Jan 10 02:01:16 [NetworkManager] <WARN> nm_signal_handler(): Caught signal 15, shutting down normally._ Jan 10 02:01:16 [NetworkManager] <info> Caught terminiation signal_ Jan 10 02:01:16 [NetworkManager] <info> Deactivating device eth0._ Jan 10 02:01:16 [kernel] sky2 eth0: disabling interface Jan 10 02:01:16 [NetworkManager] <info> Deactivating device wlan0._ Jan 10 02:01:18 [NetworkManager] <WARN> nm_device_802_11_wireless_set_wep_enc_key(): error setting key for device wlan0: Invalid argument_ Jan 10 02:01:18 [NetworkManager] <info> starting..._ Jan 10 02:01:18 [NetworkManager] nm_ip4_config_set_hostname: assertion `config != NULL' failed Jan 10 02:01:18 [NetworkManager] <info> wlan0: Device is fully-supported using driver '(null)'._ Jan 10 02:01:18 [NetworkManager] <info> wlan0: driver does not support SSID scans (scan_capa 0x00)._ Jan 10 02:01:18 [NetworkManager] <info> nm_device_init(): waiting for device's worker thread to start_ Jan 10 02:01:18 [NetworkManager] <info> nm_device_init(): device's worker thread started, continuing._ Jan 10 02:01:18 [NetworkManager] <info> Now managing wireless (802.11) device 'wlan0'._ Jan 10 02:01:18 [NetworkManager] <info> Deactivating device wlan0._ Jan 10 02:01:20 [NetworkManager] <WARN> nm_device_802_11_wireless_set_wep_enc_key(): error setting key for device wlan0: Invalid argument_ Jan 10 02:01:20 [kernel] sky2 eth0: enabling interface Jan 10 02:01:20 [kernel] ADDRCONF(NETDEV_UP): eth0: link is not ready Jan 10 02:01:20 [NetworkManager] nm_ip4_config_set_hostname: assertion `config != NULL' failed Jan 10 02:01:20 [NetworkManager] <info> eth0: Device is fully-supported using driver '(null)'._ Jan 10 02:01:20 [NetworkManager] <info> nm_device_init(): waiting for device's worker thread to start_ Jan 10 02:01:20 [NetworkManager] <info> nm_device_init(): device's worker thread started, continuing._ Jan 10 02:01:20 [NetworkManager] <info> Now managing wired Ethernet (802.3) device 'eth0'._ Jan 10 02:01:20 [NetworkManager] <info> Deactivating device eth0._ Jan 10 02:01:21 [rc-scripts] WARNING: net.lo has already been started. Jan 10 02:01:21 [NetworkManager] <info> Updating allowed wireless network lists._ Jan 10 02:01:29 [NetworkManager] <WARN> request_and_convert_scan_results(): unknown error, or the card returned too much scan info: Invalid argument_ Jan 10 02:01:42 [kernel] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jan 10 02:01:54 [wpa_cli] interface wlan0 CONNECTED Jan 10 02:01:55 [rc-scripts] Configuration not set for wlan0 - assuming DHCP Jan 10 02:01:55 [dhcpcd] wlan0: dhcpcd 4.0.2 starting Jan 10 02:01:55 [dhcpcd] wlan0: broadcasting for a lease Infact networkmanager is unable to populate the list of surrounding wireless networks. Now I've reswitched to ndiswrapper becouse wpa_supplicant seems to be unable to manage encrypted connection through driver you linked to me. What could I do?
Little update. I made it working with NetworkManager. As I posted before, it's unable to populate the wireless network lists. So I added "homewifi" manually and it connected in 2-3 attempts. This is what Networkmanager printed in logs: Jan 10 12:09:37 [kernel] udev: renamed network interface eth1 to wlan0 Jan 10 12:09:37 [NetworkManager] nm_ip4_config_set_hostname: assertion `config != NULL' failed Jan 10 12:09:37 [NetworkManager] <info> wlan0: Device is fully-supported using driver '(null)'._ Jan 10 12:09:37 [NetworkManager] <info> wlan0: driver does not support SSID scans (scan_capa 0x00)._ Jan 10 12:09:37 [NetworkManager] <info> nm_device_init(): waiting for device's worker thread to start_ Jan 10 12:09:37 [NetworkManager] <info> nm_device_init(): device's worker thread started, continuing._ Jan 10 12:09:37 [NetworkManager] <info> Now managing wireless (802.11) device 'wlan0'._ Jan 10 12:09:37 [NetworkManager] <info> Deactivating device wlan0._ Jan 10 12:09:37 [rc-scripts] net.wlan0 is not allowed to be hotplugged Jan 10 12:09:39 [NetworkManager] <WARN> nm_device_802_11_wireless_set_wep_enc_key(): error setting key for device wlan0: Invalid argument_ Jan 10 12:09:47 [NetworkManager] <WARN> request_and_convert_scan_results(): unknown error, or the card returned too much scan info: Invalid argument_ Jan 10 12:10:12 [dhcdbd] message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason Jan 10 12:10:12 [NetworkManager] <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / homewifi_ Jan 10 12:10:12 [NetworkManager] <info> Deactivating device wlan0._ Jan 10 12:10:14 [NetworkManager] <WARN> nm_device_802_11_wireless_set_wep_enc_key(): error setting key for device wlan0: Invalid argument_ Jan 10 12:10:14 [NetworkManager] <info> Device wlan0 activation scheduled..._ Jan 10 12:10:14 [NetworkManager] <info> Activation (wlan0) started..._ Jan 10 12:10:14 [NetworkManager] <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled..._ Jan 10 12:10:14 [NetworkManager] <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started..._ Jan 10 12:10:14 [NetworkManager] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled..._ Jan 10 12:10:14 [NetworkManager] <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete._ Jan 10 12:10:14 [NetworkManager] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting..._ Jan 10 12:10:14 [NetworkManager] <info> Activation (wlan0/wireless): access point 'homewifi' is encrypted, and a key exists. No new key needed._ Jan 10 12:10:15 [NetworkManager] <info> SUP: sending command 'INTERFACE_ADD wlan0__wext_/var/run/wpa_supplicant_'_ Jan 10 12:10:15 [kernel] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jan 10 12:10:15 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: sending command 'AP_SCAN 2'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: sending command 'ADD_NETWORK'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: response was '0'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: sending command 'SET_NETWORK 0 ssid 686f6d6577696669'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: sending command 'SET_NETWORK 0 scan_ssid 1'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: sending command 'SET_NETWORK 0 proto WPA'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: sending command 'SET_NETWORK 0 psk <key>'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: sending command 'ENABLE_NETWORK 0'_ Jan 10 12:10:15 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:10:15 [NetworkManager] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete._ Jan 10 12:10:18 [NetworkManager] <info> Old device 'wlan0' activating, won't change._ Jan 10 12:10:55 [NetworkManager] <info> Activation (wlan0/wireless): association took too long (>40s), failing activation._ Jan 10 12:10:55 [NetworkManager] <info> Activation (wlan0) failure scheduled..._ Jan 10 12:10:55 [NetworkManager] <info> Activation (wlan0) failed for access point (homewifi)_ Jan 10 12:10:55 [NetworkManager] <info> Activation (wlan0) failed._ Jan 10 12:10:55 [NetworkManager] <info> Deactivating device wlan0._ Jan 10 12:10:56 [kernel] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jan 10 12:10:57 [NetworkManager] <WARN> nm_device_802_11_wireless_set_wep_enc_key(): error setting key for device wlan0: Invalid argument_ Jan 10 12:11:05 [dhcdbd] message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason Jan 10 12:11:05 [NetworkManager] <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / homewifi_ Jan 10 12:11:05 [NetworkManager] <info> Deactivating device wlan0._ Jan 10 12:11:07 [NetworkManager] <WARN> nm_device_802_11_wireless_set_wep_enc_key(): error setting key for device wlan0: Invalid argument_ Jan 10 12:11:07 [NetworkManager] <info> Device wlan0 activation scheduled..._ Jan 10 12:11:07 [NetworkManager] <info> Activation (wlan0) started..._ Jan 10 12:11:07 [NetworkManager] <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled..._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started..._ Jan 10 12:11:08 [NetworkManager] <info> Old device 'wlan0' activating, won't change._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled..._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting..._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0/wireless): access point 'homewifi' is encrypted, but NO valid key exists. New key needed._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) New wireless user key requested for network 'homewifi'._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) New wireless user key for network 'homewifi' received._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled..._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started..._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled..._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting..._ Jan 10 12:11:08 [NetworkManager] <info> Activation (wlan0/wireless): access point 'homewifi' is encrypted, and a key exists. No new key needed._ Jan 10 12:11:09 [NetworkManager] <info> SUP: sending command 'INTERFACE_ADD wlan0__wext_/var/run/wpa_supplicant_'_ Jan 10 12:11:09 [kernel] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jan 10 12:11:09 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: sending command 'AP_SCAN 1'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: sending command 'ADD_NETWORK'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: response was '0'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: sending command 'SET_NETWORK 0 ssid 686f6d6577696669'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: sending command 'SET_NETWORK 0 proto WPA'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: sending command 'SET_NETWORK 0 psk <key>'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: sending command 'ENABLE_NETWORK 0'_ Jan 10 12:11:09 [NetworkManager] <info> SUP: response was 'OK'_ Jan 10 12:11:09 [NetworkManager] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete._ Jan 10 12:11:14 [NetworkManager] <info> Supplicant state changed: 1_ Jan 10 12:11:14 [NetworkManager] <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'homewifi'._ Jan 10 12:11:14 [NetworkManager] <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled._ Jan 10 12:11:14 [NetworkManager] <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started..._ Jan 10 12:11:15 [NetworkManager] <info> Activation (wlan0) Beginning DHCP transaction._ Jan 10 12:11:15 [NetworkManager] <info> DHCP daemon state is now 12 (successfully started) for interface wlan0_ Jan 10 12:11:15 [NetworkManager] <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete._ Jan 10 12:11:16 [NetworkManager] <info> DHCP daemon state is now 1 (starting) for interface wlan0_ Jan 10 12:11:16 [dhclient] DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 Jan 10 12:11:20 [dhclient] DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 Jan 10 12:11:20 [dhclient] DHCPOFFER from 192.168.0.254 Jan 10 12:11:20 [dhclient] DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Jan 10 12:11:20 [dhclient] DHCPACK from 192.168.0.254 Jan 10 12:11:20 [NetworkManager] <info> DHCP daemon state is now 2 (bound) for interface wlan0_ Jan 10 12:11:20 [NetworkManager] <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled..._ Jan 10 12:11:20 [NetworkManager] <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started..._ Jan 10 12:11:20 [dhclient] bound to 192.168.0.15 -- renewal in 41191 seconds. Jan 10 12:11:21 [dhcdbd] message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain Jan 10 12:11:21 [dhcdbd] message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers Jan 10 12:11:21 [NetworkManager] <info> Retrieved the following IP4 configuration from the DHCP daemon:_ Jan 10 12:11:21 [NetworkManager] <info> address 192.168.0.15_ Jan 10 12:11:21 [NetworkManager] <info> netmask 255.255.255.0_ Jan 10 12:11:21 [NetworkManager] <info> broadcast 192.168.0.255_ Jan 10 12:11:21 [NetworkManager] <info> gateway 192.168.0.254_ Jan 10 12:11:21 [NetworkManager] <info> nameserver 85.37.17.56_ Jan 10 12:11:21 [NetworkManager] <info> nameserver 85.38.28.98_ Jan 10 12:11:21 [NetworkManager] <info> nameserver 192.168.0.254_ Jan 10 12:11:21 [NetworkManager] <info> hostname 'whitebox'_ Jan 10 12:11:21 [NetworkManager] <info> domain name 'domain_not_set.invalid'_ Jan 10 12:11:21 [dhcdbd] message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.interface_mtu Jan 10 12:11:21 [NetworkManager] <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled..._ Jan 10 12:11:21 [NetworkManager] <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete._ Jan 10 12:11:21 [NetworkManager] <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started..._ Jan 10 12:11:22 [NetworkManager] <info> Setting hostname to 'whitebox'_ Jan 10 12:11:22 [NetworkManager] <info> Activation (wlan0) successful, device activated._ Jan 10 12:11:22 [NetworkManager] <info> Activation (wlan0) Finish handler scheduled._ Jan 10 12:11:22 [NetworkManager] <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete._
Sorry to post again (sounds like I'm spamming ahah) I've found a patched driver here: http://www.cenolan.com/broadcom-wl/ This version is quite good, better than official one altough even this one conflicts with Networkmanager about populating the wireless network list. Jan 10 12:45:33 [NetworkManager] <info> Updating allowed wireless network lists._ Jan 10 12:45:57 [NetworkManager] <WARN> request_and_convert_scan_results(): unknown error, or the card returned too much scan info: Invalid argument_ Instead of official one, this version works like a charm with wpa_supplicant whitebox elbryan # wpa_supplicant -Dwext -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf CTRL-EVENT-SCAN-RESULTS Trying to associate with 00:14:bf:e6:7d:bd (SSID='homewifi' freq=2447 MHz) ioctl[SIOCSIWAP]: Device or resource busy Association request to the driver failed Associated with 00:14:bf:e6:7d:bd WPA: Key negotiation completed with 00:14:bf:e6:7d:bd [PTK=TKIP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to 00:14:bf:e6:7d:bd completed (auth) [id=0 id_str=] Hope this helps!
Hi Fabiano, You might want to give NM 0.7 a try. 0.6.6 is pretty old and 0.7 brings tons of new features. It should be much better than 0.6.6. About current logs - it seems driver is returning different information than NM expects. Hopefully 4328 should have a proper driver soon.
(In reply to comment #8) > Hi Fabiano, > > You might want to give NM 0.7 a try. 0.6.6 is pretty old and 0.7 brings tons of > new features. It should be much better than 0.6.6. > > About current logs - it seems driver is returning different information than NM > expects. Hopefully 4328 should have a proper driver soon. > I had tried NM 0.7 before you asked me to do it. It crashes without reason (I didn't get the log but was similar to my first crash log. I thought the problem was mine and unrelated to broadcom's driver because it's hardmasked in portage. If you want me to, I could try NM 0.7 and report something more reliable. I think would be better to open a new ticked indeed.
personally I think this ticket should be closed as the issue has nothing directly related to NM. It's the driver issue. If you're willing to try NM 0.7 I will be glad to help you with any problem you might have. Rob
You're right :) I close the ticket. As posted above this is not NM related issue.
