Resend. Sorry, forgot to "reply all" on the last 2 emails
because wpa_supplicant 1.0 (at least on LMDE/Debian testing) always
tries nl80211 first
# grep -i wext /etc/wpa_supplicant/*
/etc/wpa_supplicant/functions.sh:# -D driver backend ('wext' if none given)
/etc/wpa_supplicant/functions.sh:
WPA_SUP_OPTIONS="$WPA_SUP_OPTIONS
-D nl80211,wext"
/etc/wpa_supplicant/functions.sh:
wpa_msg stderr "using
\"nl80211,wext\" wpa-driver instead ..."
/etc/wpa_supplicant/functions.sh:
WPA_SUP_OPTIONS="$WPA_SUP_OPTIONS
-D nl80211,wext"
/etc/wpa_supplicant/functions.sh: wpa_msg verbose "wpa-driver
nl80211,wext (default)"
--
And to answer your other question, attached the complete snipped part
--
Jasmine
On Mon, Oct 1, 2012 at 2:06 PM, Arend van Spriel <ar...@broadcom.com> wrote:
> On 09/27/2012 04:24 PM, Jasmine Hassan wrote:
>>
>> Update on 3.6-rc7 problems with wpasupplicant-1.0-2 and broadcom-sta
>> 6.20.55.19 (r300276)
>> 1. Fails to associate to AP (WPA encryption used) when wl.ko built with
>> wext
>> 2. Kernel bug when wl.ko built with nl/cfg80211
>
>
> Commenting on issue 1 only, here.
>
>
>>> Updated deb:
>>> http://jas.gemnetworks.com/debian/wireless-bcm43142-dkms-6.20.55.19_amd64.deb
>>>
>>> Also tested on linux 3.5.0-4.dmz.1-liquorix-amd64, and it works for me
>>>
>>> Now, given a power regression in kernel 3.5, I was eager to test drive
>>> 3.6-rc6, and found rc7 out already!
>>> So yesterday I installed linux 3.6-rc7.towo.1-siduction-amd64, the
>>> "wl" module compiles and installs, and loads okay upon boot to
>>> 3.6-rc7. However, I'm unable to associate to my AP:
>>>
>>> Pointers in syslog
>>> Sep 25 21:34:10 terra wpa_supplicant[2787]: nl80211: 'nl80211' generic
>>> netlink not found
>>> Sep 25 21:34:10 terra wpa_supplicant[2787]: Failed to initialize
>>> driver 'nl80211'
>>> [..snip]
>
>
> Not sure what is snipped here. Your wpa_supplicant seems to try nl80211.
> Maybe it goes and try WEXT instead, but that is missing from the log. Do you
> recall or still have the entire syslog?
>
>
>>> Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Trying to associate
>>> with 00:xx:xx:xx:xx:xx (SSID='xxxxxxx' freq=2452 MHz)
>>> Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Association request
>>> to the driver failed
>>>
>>> As bcm43142 is fairly new, this proprietary driver is all that's there
>>> to support it. Sad face.
>>>
>>> Cheers,
>>> Jasmine
>
>
> Gr. AvS
>
>
Sep 25 21:34:10 terra kernel: [ 18.223028] NET: Registered protocol family 17
Sep 25 21:34:10 terra NetworkManager[2750]: <info> (eth2): supplicant interface
state: starting -> ready
Sep 25 21:34:10 terra NetworkManager[2750]: <info> (eth2): device state change:
unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Sep 25 21:34:10 terra NetworkManager[2750]: <info> (eth2): supplicant interface
state: ready -> inactive
Sep 25 21:34:10 terra NetworkManager[2750]: <warn> Trying to remove a
non-existant call id.
Sep 25 21:34:10 terra acpid: client connected from 2811[0:0]
Sep 25 21:34:10 terra acpid: 1 client rule loaded
Sep 25 21:34:11 terra laptop-mode: enabled, not active
Sep 25 21:34:12 terra kernel: [ 20.272321] radeon: switched off
Sep 25 21:34:12 terra kernel: [ 20.716266] elevator: type bfq not found
Sep 25 21:34:12 terra kernel: [ 20.716270] elevator: switch to bfq
Sep 25 21:34:12 terra kernel: [ 20.716270] failed
Sep 25 21:34:23 terra dbus[2635]: [system] Activating service
name='org.freedesktop.ConsoleKit' (using servicehelper)
Sep 25 21:34:23 terra dbus[2635]: [system] Successfully activated service
'org.freedesktop.ConsoleKit'
Sep 25 21:34:28 terra dbus[2635]: [system] Activating service
name='org.freedesktop.UDisks' (using servicehelper)
Sep 25 21:34:28 terra dbus[2635]: [system] Successfully activated service
'org.freedesktop.UDisks'
Sep 25 21:34:29 terra pulseaudio[3688]: [pulseaudio] pid.c: Daemon already
running.
Sep 25 21:34:30 terra dbus[2635]: [system] Activating service
name='org.freedesktop.UPower' (using servicehelper)
Sep 25 21:34:30 terra dbus[2635]: [system] Successfully activated service
'org.freedesktop.UPower'
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Auto-activating connection
'xxxxxxx'.
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Activation (eth2) starting
connection 'xxxxxxx'
Sep 25 21:34:30 terra NetworkManager[2750]: <info> (eth2): device state change:
disconnected -> prepare (reason 'none') [30 40 0]
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Activation (eth2) Stage 1 of
5 (Device Prepare) scheduled...
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Activation (eth2) Stage 1 of
5 (Device Prepare) started...
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Activation (eth2) Stage 2 of
5 (Device Configure) scheduled...
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Activation (eth2) Stage 1 of
5 (Device Prepare) complete.
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Activation (eth2) Stage 2 of
5 (Device Configure) starting...
Sep 25 21:34:30 terra NetworkManager[2750]: <info> (eth2): device state change:
prepare -> config (reason 'none') [40 50 0]
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Activation (eth2/wireless):
connection 'xxxxxxx' has security, and secrets exist. No new secrets needed.
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Config: added 'ssid' value
'xxxxxxx'
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Config: added 'scan_ssid'
value '1'
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Config: added 'key_mgmt'
value 'WPA-PSK'
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Config: added 'auth_alg'
value 'OPEN'
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Config: added 'psk' value
'<omitted>'
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Activation (eth2) Stage 2 of
5 (Device Configure) complete.
Sep 25 21:34:30 terra NetworkManager[2750]: <info> Config: set interface
ap_scan to 1
Sep 25 21:34:30 terra NetworkManager[2750]: <info> (eth2): supplicant interface
state: inactive -> scanning
