WLAN Problem: Raspbian friert ein

Beatfussel · February 14, 2018 at 9:13 PM

Hallo zusammen,

ich habe seit dem letzten Update auf meinem Raspberry Pi 3 folgendes Problem. Sobald der WIFI Interface in den "up" Status geht hängt sich der Pi auf und ich kann nicht mehr drauf zugreifen. Momentan deaktiviere ich nach dem Starten das WLAN mit sudo ifconfig wlan0 down. Somit kann ich zu mindestens per LAN arbeiten. Würde gerne aber wieder das WLAN nutzen. Daher meine Bitte um Hilfe.

Bis jetzt habe ich meinen WLAN Adapter zurückgesetzt und neu eingerichtet. Aber bisher alles ohne Erfolg.

Anbei das Update History log:

Start-Date: 2018-02-07 20:01:26

Commandline: apt-get upgrade

Requested-By: pi (1000)

Upgrade: firmware-realtek:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt1), pi-bluetooth:armhf (0.1.6, 0.1.7), firmware-atheros:armhf (1:20161130-3+rpi2, 1:20161

130-3+rpt1), firmware-libertas:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt1), firmware-brcm80211:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt1), firmware-misc-n

onfree:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt1)

End-Date: 2018-02-07 20:01:35

Da hier die Treiber upgedatet wurden vermute ich eine Zusammenhang.

Vielen Dank!

Bot · Vor 5 Minuten

WLAN Problem: Raspbian friert ein? Schau mal ob du hier fündig wirst!

rpi444 · February 14, 2018 at 9:58 PM

Quote from Beatfussel

Da hier die Treiber upgedatet wurden vermute ich eine Zusammenhang.

Könnte sein. Teste mal mit der vorletzten "brcmfmac43430-sdio.bin"-Datei (d. h. vor dem update).

Beatfussel · February 15, 2018 at 7:51 PM

Vielen Dank für den Tip.

Hatte vorhin noch ein rpi-update durchgeführt. Seit dem kann der WLAN Adapter auch im "up" bleiben. Allerdings verbindet er sich nicht mehr mit dem WLAN.

Bot · Vor einem Moment

STF · February 15, 2018 at 7:59 PM

Quote from Beatfussel

Hatte vorhin noch ein rpi-update durchgeführt.

Erkenne den Fehler. Klingt so, als hättest Du das immer mal gemacht...

rpi444 · February 15, 2018 at 8:01 PM

Quote from Beatfussel

Hatte vorhin noch ein rpi-update durchgeführt. Seit dem kann der WLAN Adapter auch im "up" bleiben. Allerdings verbindet er sich nicht mehr mit dem WLAN.

Hmm, ... auf meinem Test-PI3 geht das ohne Probleme:

Code

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.14.18-v7+ #1093 SMP Fri Feb 9 15:33:07 GMT 2018 armv7l GNU/Linux

Code

pi@raspberrypi:~ $ dmesg | grep brcm
[    3.604535] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[    3.610643] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[    3.626418] usbcore: registered new interface driver brcmfmac
[    3.871428] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[    3.872360] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-10-23 03:47:14 
[    5.443900] brcmfmac: power management disabled

Code

pi@raspberrypi:~ $ iwconfig wlan0
wlan0     IEEE 802.11  ESSID:"yxyxyxyxyxyxyxyxyx"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: ##:##:##:2B:52:E0   
          Bit Rate=65 Mb/s   Tx-Power=15 dBm   
          Retry short limit:7   RTS thr=500 B   Fragment thr=512 B   
          Power Management:off
          Link Quality=62/70  Signal level=-48 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Beatfussel · February 15, 2018 at 8:23 PM

Quote from STF

Erkenne den Fehler. Klingt so, als hättest Du das immer mal gemacht...

Diesen Beitrag habe ich natürlich vorher auch gelesen. Es hat ja am Ende auch den einen Fehler behoben.

Und nein, den Pi habe ich das erste Mal mir rpi-update upgedatet.

Bot · Vor einem Moment

Beatfussel · February 15, 2018 at 8:27 PM

Sieht bei mir ähnlich aus. Bis auf der verbundene Adapter

Code

pi@homepi:~ $ uname -a
Linux homepi 4.14.18-v7+ #1093 SMP Fri Feb 9 15:33:07 GMT 2018 armv7l GNU/Linux

Code

pi@homepi:~ $ dmesg | grep brcm
[    3.823421] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[    3.829148] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43430-sdio.bin for chip 0x00a9a6(43430) rev 0x000001
[    3.829374] usbcore: registered new interface driver brcmfmac
[    4.123226] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[    4.124137] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.39 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-10-23 03:47:14
[    5.320044] brcmfmac: power management disabled

Code

pi@homepi:~ $ iwconfig wlan0
wlan0     IEEE 802.11  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on

rpi444 · February 15, 2018 at 10:00 PM

Quote from Beatfussel

Bis auf der verbundene Adapter

Code

pi@homepi:~ $ iwconfig wlan0
wlan0     IEEE 802.11  ESSID:off/any
          Mode:Managed  Access Point: Not-Associated   Tx-Power=31 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on

Ja, evtl. ist das WLAN deines PI3 doch nicht optimal konfiguriert, wenn man sieht, dass das PM auf "on" ist.

Poste mal (richtig anonymisiert) alle relevanten Dateien/Einstellungen die das WLAN deines PI3 betreffen.

STF · February 16, 2018 at 8:32 AM

Quote from Beatfussel

Seit dem kann der WLAN Adapter auch im "up" bleiben. Allerdings verbindet er sich nicht mehr mit dem WLAN.

Quote from Beatfussel

Es hat ja am Ende auch den einen Fehler behoben.

Ey cool, das ist ja ein richtiger Fortschritt. scnr (Jaja, ich halt ja schon die Klappe, ist ja ein TestPi...)

Bot · Vor einem Moment

Beatfussel · February 16, 2018 at 12:48 PM

Quote from STF

Ey cool, das ist ja ein richtiger Fortschritt. scnr (Jaja, ich halt ja schon die Klappe, ist ja ein TestPi...)

Bitte spare dir doch diese Kommentare wenn Du nicht helfen möchtest. Finde das ziemlich unangebracht. Aber das nur am Rande.

Ich dachte das ist hier ein Forum in dem Hilfe von anderen bekommen kann und man sich nicht für sein handeln rechtfertigen muss.

STF · February 16, 2018 at 2:09 PM

Quote from Beatfussel

Bitte spare dir doch diese Kommentare wenn Du nicht helfen möchtest. Finde das ziemlich unangebracht. Aber das nur am Rande.

Ich dachte das ist hier ein Forum in dem Hilfe von anderen bekommen kann und man sich nicht für sein handeln rechtfertigen muss.

Du hast völlig recht.

Allerdings habe ich es noch nie erlebt, dass ein durch rpi-update in einen instabilen Zustand gebrachtes / "verschlimmbessertes" System irgendwie wieder "repariert" werden konnte. Da ist es sicher sinnvoller, die Ursache des tatsächlichen Problems Deines ersten Posts anzugehen. Warum auch immer, mein Pi3 hat das selbe Update auch schon installiert und WLan/Lan funktionieren nach wie vor. Ich würde erst mal mit einem testweise installierten neuen System prüfen, ob dieser Effekt nachvollziehbar für Deinen Pi aus dem Update entsteht (so, wie es auch gerade den einen oder anderen Pi0W erwischt). Wenn nicht, musst Du in Deiner jetzt laufenden Konstellation suchen.

Display Spoiler

Start-Date: 2018-02-15 06:18:24

Commandline: apt upgrade -y

Requested-By: pi (1000)

Install: wolframscript:armhf (1.2.0-11, automatic), libexiv2-14:armhf (0.25-3.1, automatic)

Upgrade: libdns-export162:armhf (1:9.10.3.dfsg.P4-12.3+deb9u3, 1:9.10.3.dfsg.P4-12.3+deb9u4), libavformat57:armhf (7:3.2.9-1~deb9u1, 7:3.2.10-1~deb9u1+rpt1), python2.7-dev:armhf (2.7.13-2, 2.7.13-2+deb9u2), poppler-utils:armhf (0.48.0-2, 0.48.0-2+deb9u2), dbus-x11:armhf (1.10.22-0+deb9u1, 1.10.24-0+deb9u1), libavfilter6:armhf (7:3.2.9-1~deb9u1, 7:3.2.10-1~deb9u1+rpt1), firmware-realtek:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt1), rc-gui:armhf (1.13, 1.14), libisccfg140:armhf (1:9.10.3.dfsg.P4-12.3+deb9u3, 1:9.10.3.dfsg.P4-12.3+deb9u4), libdbus-1-3:armhf (1.10.22-0+deb9u1, 1.10.24-0+deb9u1), raspberrypi-ui-mods:armhf (1.20171115, 1.20180209), python3-scrollphathd:armhf (1.0.1, 1.1.1), libcurl3:armhf (7.52.1-5+deb9u2, 7.52.1-5+deb9u4), lxplug-ptbatt:armhf (0.2, 0.3), lxpanel-data:armhf (0.9.3-1+rpi5, 0.9.3-1+rpi6), gir1.2-gdkpixbuf-2.0:armhf (2.36.5-2+deb9u1, 2.36.5-2+deb9u2), libgdk-pixbuf2.0-0:armhf (2.36.5-2+deb9u1, 2.36.5-2+deb9u2), rpd-icons:armhf (0.12, 0.13), libswresample2:armhf (7:3.2.9-1~deb9u1, 7:3.2.10-1~deb9u1+rpt1), erlang-base:armhf (1:19.2.1+dfsg-2, 1:19.2.1+dfsg-2+deb9u1), libfm4:armhf (1.2.5-1+rpi3, 1.2.5-1+rpi4), raspi-config:armhf (20171109, 20171201), libfm-modules:armhf (1.2.5-1+rpi3, 1.2.5-1+rpi4), libfm-extra4:armhf (1.2.5-1+rpi3, 1.2.5-1+rpi4), erlang-syntax-tools:armhf (1:19.2.1+dfsg-2, 1:19.2.1+dfsg-2+deb9u1), wolfram-engine:armhf (11.0.1+2017071100, 11.2.0+2018011502), dbus:armhf (1.10.22-0+deb9u1, 1.10.24-0+deb9u1), python2.7-minimal:armhf (2.7.13-2, 2.7.13-2+deb9u2), libsqlite3-0:armhf (3.16.2-5, 3.16.2-5+deb9u1), libicu57:armhf (57.1-6, 57.1-6+deb9u1), gstreamer1.0-omx:armhf (1.10.4-1+rpt2, 1.10.4-1+rpt3), pi-bluetooth:armhf (0.1.6, 0.1.7), bind9-host:armhf (1:9.10.3.dfsg.P4-12.3+deb9u3, 1:9.10.3.dfsg.P4-12.3+deb9u4), gstreamer1.0-omx-rpi:armhf (1.10.4-1+rpt2, 1.10.4-1+rpt3), libpython2.7:armhf (2.7.13-2, 2.7.13-2+deb9u2), python2.7:armhf (2.7.13-2, 2.7.13-2+deb9u2), gstreamer1.0-omx-rpi-config:armhf (1.10.4-1+rpt2, 1.10.4-1+rpt3), libxcursor1:armhf (1:1.1.14-1+b1, 1:1.1.14-1+deb9u1), openssh-sftp-server:armhf (1:7.4p1-10+deb9u1, 1:7.4p1-10+deb9u2), libfm-gtk4:armhf (1.2.5-1+rpi3, 1.2.5-1+rpi4), libisc160:armhf (1:9.10.3.dfsg.P4-12.3+deb9u3, 1:9.10.3.dfsg.P4-12.3+deb9u4), libvorbisfile3:armhf (1.3.5-4, 1.3.5-4+deb9u1), libpython2.7-dev:armhf (2.7.13-2, 2.7.13-2+deb9u2), gtk2-engines-clearlookspix:armhf (1:2.20.4, 1:2.20.5), firmware-atheros:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt1), pishutdown:armhf (0.8, 0.9), libobrender32v5:armhf (3.6.1-4+rpi4, 3.6.1-4+rpi6), firmware-libertas:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt1), libpostproc54:armhf (7:3.2.9-1~deb9u1, 7:3.2.10-1~deb9u1+rpt1), libxkbcommon-x11-0:armhf (0.7.1-1, 0.7.1-2~deb9u1), libtiff5:armhf (4.0.8-2+deb9u1, 4.0.8-2+deb9u2), libisc-export160:armhf (1:9.10.3.dfsg.P4-12.3+deb9u3, 1:9.10.3.dfsg.P4-12.3+deb9u4), lxplug-bluetooth:armhf (0.4, 0.5), firmware-brcm80211:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt1), idle-python2.7:armhf (2.7.13-2, 2.7.13-2+deb9u2), libvorbisenc2:armhf (1.3.5-4, 1.3.5-4+deb9u1), ssh:armhf (1:7.4p1-10+deb9u1, 1:7.4p1-10+deb9u2), bluez-firmware:armhf (1.2-3+rpt1, 1.2-3+rpt2), liblwres141:armhf (1:9.10.3.dfsg.P4-12.3+deb9u3, 1:9.10.3.dfsg.P4-12.3+deb9u4), libavcodec57:armhf (7:3.2.9-1~deb9u1, 7:3.2.10-1~deb9u1+rpt1), erlang-crypto:armhf (1:19.2.1+dfsg-2, 1:19.2.1+dfsg-2+deb9u1), realvnc-vnc-server:armhf (6.2.0.29523, 6.2.1.32538), libavutil55:armhf (7:3.2.9-1~deb9u1, 7:3.2.10-1~deb9u1+rpt1), lxplug-network:armhf (0.5, 0.6), openssh-server:armhf (1:7.4p1-10+deb9u1, 1:7.4p1-10+deb9u2), iproute2:armhf (4.9.0-1, 4.9.0-1+deb9u1), libswscale4:armhf (7:3.2.9-1~deb9u1, 7:3.2.10-1~deb9u1+rpt1), libgdk-pixbuf2.0-common:armhf (2.36.5-2+deb9u1, 2.36.5-2+deb9u2), openssh-client:armhf (1:7.4p1-10+deb9u1, 1:7.4p1-10+deb9u2), firmware-misc-nonfree:armhf (1:20161130-3+rpi2, 1:20161130-3+rpt1), rpi-chromium-mods:armhf (20171113, 20180207), libdns162:armhf (1:9.10.3.dfsg.P4-12.3+deb9u3, 1:9.10.3.dfsg.P4-12.3+deb9u4), openbox:armhf (3.6.1-4+rpi4, 3.6.1-4+rpi6), libobt2v5:armhf (3.6.1-4+rpi4, 3.6.1-4+rpi6), libxml2:armhf (2.9.4+dfsg1-2.2+deb9u1, 2.9.4+dfsg1-2.2+deb9u2), libfm-data:armhf (1.2.5-1+rpi3, 1.2.5-1+rpi4), pipanel:armhf (20170707~125920, 20180126~074441), libpython2.7-minimal:armhf (2.7.13-2, 2.7.13-2+deb9u2), rsync:armhf (3.1.2-1, 3.1.2-1+deb9u1), libisccc140:armhf (1:9.10.3.dfsg.P4-12.3+deb9u3, 1:9.10.3.dfsg.P4-12.3+deb9u4), dbus-user-session:armhf (1.10.22-0+deb9u1, 1.10.24-0+deb9u1), libvorbis0a:armhf (1.3.5-4, 1.3.5-4+deb9u1), libbind9-140:armhf (1:9.10.3.dfsg.P4-12.3+deb9u3, 1:9.10.3.dfsg.P4-12.3+deb9u4), python-scrollphathd:armhf (1.0.1, 1.1.1), lxpanel:armhf (0.9.3-1+rpi5, 0.9.3-1+rpi6), libtasn1-6:armhf (4.10-1.1, 4.10-1.1+deb9u1), pcmanfm:armhf (1.2.5-3+rpi3, 1.2.5-3+rpi4), raspberrypi-sys-mods:armhf (20171127, 20180103), libpython2.7-stdlib:armhf (2.7.13-2, 2.7.13-2+deb9u2), libpoppler64:armhf (0.48.0-2, 0.48.0-2+deb9u2), curl:armhf (7.52.1-5+deb9u2, 7.52.1-5+deb9u4), libxkbcommon0:armhf (0.7.1-1, 0.7.1-2~deb9u1), libavresample3:armhf (7:3.2.9-1~deb9u1, 7:3.2.10-1~deb9u1+rpt1), libcurl3-gnutls:armhf (7.52.1-5+deb9u2, 7.52.1-5+deb9u4), sensible-utils:armhf (0.0.9, 0.0.9+deb9u1), libssl1.0.2:armhf (1.0.2l-2+deb9u1, 1.0.2l-2+deb9u2), base-files:armhf (9.9+rpi1+deb9u1, 9.9+rpi1+deb9u3), libfm-gtk-data:armhf (1.2.5-1+rpi3, 1.2.5-1+rpi4), tzdata:armhf (2017b-1, 2017c-0+deb9u1)

End-Date: 2018-02-15 06:36:56

coyotelinux · February 16, 2018 at 10:39 PM

habe das gleiche Problem, mit light und der normalen stretch vom November 2017. Vor Upgrade läuft alles prima. Danach hängt sich der Raspi auf. Konnte mit der firmware-brcm80211 nachvollziehen. Wenn ich rpi-update durchführe läuft der, leider aber kein Aufbau der WLAN Verbindung. Mit anderen Distris z.B. KALI läuft alles prima. Ist bereits der zweite Raspi.

Kann das mal jemand bitte mit einer frischen Installation nachvollziehen?

Der Bug muss doch alle aktuell treffen, die frisch aufsetzen.

Bot · Vor einem Moment

rpi444 · February 16, 2018 at 10:47 PM

Quote from coyotelinux

Wenn ich rpi-update durchführe läuft der, leider aber kein Aufbau der WLAN Verbindung.

Versuch mal die WLAN-Verbindung im Terminal/Konsole herzustellen, mit z. B.:

Code

sudo -k wpa_supplicant -i wlan0 -D nl80211 -c /etc/wpa_supplicant/wpa_supplicant.conf -d

Wenn so die Verbindung nicht zustande kommt, dann poste die Ausgaben.

coyotelinux · February 16, 2018 at 10:51 PM

leider klappt es nicht:

wpa_supplicant v2.4

random: Trying to read entropy from /dev/random

Successfully initialized wpa_supplicant

Initializing interface 'wlan0' conf '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'nl80 211' ctrl_interface 'N/A' bridge 'N/A'

Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' -> '/etc/wpa_supplicant/wpa_s upplicant.conf'

Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'

ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=netdev'

update_config=1

country='DE'

Priority group 0

id=0 ssid='@smart'

rfkill: initial event: idx=0 type=2 op=0 soft=0 hard=0

Could not read interface wlan0 flags: No such device

nl80211: Driver does not support authentication/association or connect commands

nl80211: deinit ifname=wlan0 disabled_11b_rates=0

nl80211: Remove monitor interface: refcount=0

netlink: Operstate: ifindex=0 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)

Could not read interface wlan0 flags: No such device

nl80211: Set mode ifindex 0 iftype 2 (STATION)

nl80211: Failed to set interface 0 to mode 2: -19 (No such device)

wlan0: Failed to initialize driver interface

Failed to add interface wlan0

wlan0: Cancelling scan request

wlan0: Cancelling authentication timeout

rpi444 · February 16, 2018 at 11:01 PM

Quote from coyotelinux

leider klappt es nicht:

Could not read interface wlan0 flags: No such device

nl80211: Driver does not support authentication/association or connect commands

nl80211: deinit ifname=wlan0 disabled_11b_rates=0

nl80211: Remove monitor interface: refcount=0

Display More

Wie sind die Ausgaben von:

Code

lsmod | grep -i brcm
modinfo brcmfmac
iwconfig
ifconfig
sudo -k iwlist wlan0 scan

?

EDIT:

... und die Ausgaben von:

Code

ls -la /var/run/wpa_supplicant
cat /etc/group | grep -i netdev

?

Bot · Vor einem Moment

coyotelinux · February 16, 2018 at 11:11 PM

habe nochmal "sudo -k wpa_supplicant -i wlan0 -D nl80211 -c /etc/wpa_supplicant/wpa_supplicant.conf -d" nachdem ich die firmware-brcm80211 installiert habe, anscheinend habe ich es davor test weise runter genommen, hier die Ausgabe:

pi@raspi:~ $ sudo -k wpa_supplicant -i wlan0 -D nl80211 -c /etc/wpa_supplicant/wpa_supplicant.conf -d

wpa_supplicant v2.4

random: Trying to read entropy from /dev/random

Successfully initialized wpa_supplicant

Initializing interface 'wlan0' conf '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A'

Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' -> '/etc/wpa_supplicant/wpa_supplicant.conf'

Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'

ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=netdev'

update_config=1

country='DE'

Priority group 0

id=0 ssid='@smart'

rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0

rfkill: initial event: idx=1 type=2 op=0 soft=0 hard=0

nl80211: Supported cipher 00-0f-ac:1

nl80211: Supported cipher 00-0f-ac:5

nl80211: Supported cipher 00-0f-ac:2

nl80211: Supported cipher 00-0f-ac:4

nl80211: Using driver-based off-channel TX

nl80211: Supported vendor command: vendor_id=0x1018 subcmd=1

nl80211: Use separate P2P group interface (driver advertised support)

nl80211: Enable multi-channel concurrent (driver advertised support)

nl80211: use P2P_DEVICE support

nl80211: interface wlan0 in phy phy0

nl80211: Set mode ifindex 3 iftype 2 (STATION)

nl80211: Subscribe to mgmt frames with non-AP handle 0x1a658a0

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=040a

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 04 0a

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=040b

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 04 0b

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=040c

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 04 0c

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=040d

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 04 0d

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=090a

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 09 0a

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=090b

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 09 0b

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=090c

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 09 0c

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=090d

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 09 0d

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=0409506f9a09

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=6): 04 09 50 6f 9a 09

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=7f506f9a09

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=5): 7f 50 6f 9a 09

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=0801

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 08 01

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=06

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=1): 06

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=0a07

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 0a 07

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=0a11

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 0a 11

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=1101

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 11 01

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=1102

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 11 02

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1a658a0 match=0505

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 05 05

nl80211: Failed to register Action frame processing - ignore for now

netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT)

nl80211: driver param='(null)'

Add interface wlan0 to a new radio phy0

nl80211: Regulatory information - country=DE (DFS-ETSI)

nl80211: 2400-2483 @ 40 MHz 20 mBm

nl80211: 5150-5250 @ 80 MHz 20 mBm (no outdoor)

nl80211: 5250-5350 @ 80 MHz 20 mBm (no outdoor) (DFS)

nl80211: 5470-5725 @ 160 MHz 26 mBm (DFS)

nl80211: 5725-5875 @ 80 MHz 13 mBm

nl80211: 57000-66000 @ 2160 MHz 40 mBm

nl80211: Added 802.11b mode based on 802.11g information

wlan0: Own MAC address: b8:27:eb:17:be:af

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=4 set_tx=0 seq_len=0 key_len=0

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=5 set_tx=0 seq_len=0 key_len=0

wlan0: RSN: flushing PMKID list in the driver

nl80211: Flush PMKIDs

TDLS: TDLS operation not supported by driver

TDLS: Driver uses internal link setup

TDLS: Driver does not support TDLS channel switching

wlan0: WPS: UUID based on MAC address: 63da1e29-d778-515a-b16c-146656ee9410

ENGINE: Loading dynamic engine

EAPOL: SUPP_PAE entering state DISCONNECTED

EAPOL: Supplicant port status: Unauthorized

nl80211: Skip set_supp_port(unauthorized) while not associated

EAPOL: KEY_RX entering state NO_KEY_RECEIVE

EAPOL: SUPP_BE entering state INITIALIZE

EAP: EAP entering state DISABLED

Using existing control interface directory.

ctrl_interface_group=108 (from group name 'netdev')

ctrl_iface bind(PF_UNIX) failed: Address already in use

ctrl_iface exists and seems to be in use - cannot override it

Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore

Failed to initialize control interface 'DIR=/var/run/wpa_supplicant GROUP=netdev'.

You may have another wpa_supplicant process already running or the file was

left by an unclean termination of wpa_supplicant in which case you will need

to manually remove this file before starting wpa_supplicant again.

Failed to add interface wlan0

wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:00:00:00:00 reason=3 state=DISCONNECTED

TDLS: Tear down peers

wlan0: State: DISCONNECTED -> DISCONNECTED

nl80211: Set wlan0 operstate 0->0 (DORMANT)

netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)

EAPOL: External notification - portEnabled=0

EAPOL: External notification - portValid=0

wlan0: WPA: Clear old PMK and PTK

wlan0: Cancelling delayed sched scan

wlan0: Cancelling scan request

wlan0: Cancelling authentication timeout

Remove interface wlan0 from radio phy0

Remove radio phy0

nl80211: deinit ifname=wlan0 disabled_11b_rates=0

nl80211: Remove monitor interface: refcount=0

netlink: Operstate: ifindex=3 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)

nl80211: Set mode ifindex 3 iftype 2 (STATION)

nl80211: Unsubscribe mgmt frames handle 0x892ed029 (mode change)

rpi444 · February 16, 2018 at 11:14 PM

Quote from coyotelinux
habe nochmal "sudo -k wpa_supplicant -i wlan0 -D nl80211 -c /etc/wpa_supplicant/wpa_supplicant.conf -d" nachdem ich die firmware-brcm80211 installiert habe, anscheinend habe ich es davor test weise runter genommen, hier die Ausgabe:
Code
ctrl_interface_group=108 (from group name 'netdev')
ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface 'DIR=/var/run/wpa_supplicant GROUP=netdev'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.


Failed to add interface wlan0
Display More

Ja, siehe meinen vorletzten Beitrag.

EDIT:

Hast Du z. Zt. einen NM (oder gleichwertig) aktiv, der das WLAN auch starten will? Wenn ja, diesen deaktivieren bzw. ruhig stellen.

coyotelinux · February 16, 2018 at 11:24 PM

ich bin echt froh, dass hier im Forum so schnell und kompetent geholfen wir, danke Dir rpi444 für deine Unterstützung vorab. Im Gegensatz zum meinem Nickname (war mal in der Jugend ein Hype) habe ich leider nicht so viel Ahnung von Linux und Raspberry Pi, will mich aber da einarbeiten und vor allem meinem Sohn anschließend was beibringen.

So wie ich deinen Hinweis aus dem LOG erkennen kann, ist der Hinweis darauf die Datei /var/run/wpa_supplicant/wlan0 zu löschen. Reicht das alleine aus, oder soll ich noch was beachten?

Bot · Vor einem Moment

rpi444 · February 16, 2018 at 11:27 PM

Quote from coyotelinux

..., ist der Hinweis darauf die Datei /var/run/wpa_supplicant/wlan0 zu löschen. Reicht das alleine aus, oder soll ich noch was beachten?

Ob das reicht werden wir sehen. Jetzt geht es erstmal darum, ob der wpa_supplicant bzw. das WLAN aus dem Terminal gestartet werden kann. Wenn ja, dann schauen wir weiter.

coyotelinux · February 16, 2018 at 11:30 PM

sorry für den riesen LOG:

pi@raspi:~ $ sudo -k wpa_supplicant -i wlan0 -D nl80211 -c /etc/wpa_supplicant/wpa_supplicant.conf -d

wpa_supplicant v2.4

random: Trying to read entropy from /dev/random

Successfully initialized wpa_supplicant

Initializing interface 'wlan0' conf '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A'

Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' -> '/etc/wpa_supplicant/wpa_supplicant.conf'

Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'

ctrl_interface='DIR=/var/run/wpa_supplicant GROUP=netdev'

update_config=1

country='DE'

Priority group 0

id=0 ssid='@smart'

rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0

rfkill: initial event: idx=1 type=2 op=0 soft=0 hard=0

nl80211: Supported cipher 00-0f-ac:1

nl80211: Supported cipher 00-0f-ac:5

nl80211: Supported cipher 00-0f-ac:2

nl80211: Supported cipher 00-0f-ac:4

nl80211: Using driver-based off-channel TX

nl80211: Supported vendor command: vendor_id=0x1018 subcmd=1

nl80211: Use separate P2P group interface (driver advertised support)

nl80211: Enable multi-channel concurrent (driver advertised support)

nl80211: use P2P_DEVICE support

nl80211: interface wlan0 in phy phy0

nl80211: Set mode ifindex 3 iftype 2 (STATION)

nl80211: Subscribe to mgmt frames with non-AP handle 0x6378a0

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=040a

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 04 0a

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=040b

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 04 0b

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=040c

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 04 0c

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=040d

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 04 0d

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=090a

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 09 0a

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=090b

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 09 0b

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=090c

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 09 0c

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=090d

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 09 0d

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=0409506f9a09

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=6): 04 09 50 6f 9a 09

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=7f506f9a09

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=5): 7f 50 6f 9a 09

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=0801

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 08 01

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=06

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=1): 06

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=0a07

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 0a 07

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=0a11

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 0a 11

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=1101

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 11 01

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=1102

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 11 02

nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x6378a0 match=0505

nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)

nl80211: Register frame match - hexdump(len=2): 05 05

nl80211: Failed to register Action frame processing - ignore for now

netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT)

nl80211: driver param='(null)'

Add interface wlan0 to a new radio phy0

nl80211: Regulatory information - country=DE (DFS-ETSI)

nl80211: 2400-2483 @ 40 MHz 20 mBm

nl80211: 5150-5250 @ 80 MHz 20 mBm (no outdoor)

nl80211: 5250-5350 @ 80 MHz 20 mBm (no outdoor) (DFS)

nl80211: 5470-5725 @ 160 MHz 26 mBm (DFS)

nl80211: 5725-5875 @ 80 MHz 13 mBm

nl80211: 57000-66000 @ 2160 MHz 40 mBm

nl80211: Added 802.11b mode based on 802.11g information

wlan0: Own MAC address: b8:27:eb:17:be:af

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=4 set_tx=0 seq_len=0 key_len=0

wpa_driver_nl80211_set_key: ifindex=3 (wlan0) alg=0 addr=(nil) key_idx=5 set_tx=0 seq_len=0 key_len=0

wlan0: RSN: flushing PMKID list in the driver

nl80211: Flush PMKIDs

TDLS: TDLS operation not supported by driver

TDLS: Driver uses internal link setup

TDLS: Driver does not support TDLS channel switching

wlan0: WPS: UUID based on MAC address: 63da1e29-d778-515a-b16c-146656ee9410

ENGINE: Loading dynamic engine

EAPOL: SUPP_PAE entering state DISCONNECTED

EAPOL: Supplicant port status: Unauthorized

nl80211: Skip set_supp_port(unauthorized) while not associated

EAPOL: KEY_RX entering state NO_KEY_RECEIVE

EAPOL: SUPP_BE entering state INITIALIZE

EAP: EAP entering state DISABLED

Using existing control interface directory.

ctrl_interface_group=108 (from group name 'netdev')

wlan0: Added interface wlan0

wlan0: State: DISCONNECTED -> DISCONNECTED

nl80211: Set wlan0 operstate 0->0 (DORMANT)

netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)

nl80211: Create interface iftype 10 (P2P_DEVICE)

Failed to create interface p2p-dev-wlan0: -16 (Device or resource busy)

nl80211: Failed to create a P2P Device interface p2p-dev-wlan0

P2P: Failed to create P2P Device interface

P2P: Failed to enable P2P Device interface

random: Got 20/20 bytes from /dev/random

RTM_NEWLINK: ifi_index=3 ifname=wlan0 operstate=2 linkmode=1 ifi_family=0 ifi_flags=0x1003 ([UP])

RTM_NEWLINK: ifi_index=3 ifname=wlan0 wext ifi_family=0 ifi_flags=0x1003 ([UP])

nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan0

wlan0: nl80211: New scan results available

nl80211: Scan probed for SSID ''

nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472

wlan0: Event SCAN_RESULTS (3) received

nl80211: Received scan results (7 BSSes)

wlan0: BSS: Start scan result update 1

wlan0: BSS: Add new id 0 BSSID b8:be:bf:ff:eb:50 SSID '\x00'

wlan0: BSS: Add new id 1 BSSID 34:31:c4:09:c2:04 SSID 'Anyong04012016'

wlan0: BSS: Add new id 2 BSSID 10:8c:cf:ea:e9:70 SSID '\x00'

wlan0: BSS: Add new id 3 BSSID c4:27:95:85:48:25 SSID 'Tech_D0041238'

wlan0: BSS: Add new id 4 BSSID 84:a8:e4:99:cd:ad SSID 'pistoriusnet'

wlan0: BSS: Add new id 5 BSSID 18:60:24:2b:ae:8e SSID 'DIRECT-8D-HP ENVY 5640 series'

wlan0: BSS: Add new id 6 BSSID 6e:56:97:bd:83:2a SSID '\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'

BSS: last_scan_res_used=7/32

wlan0: New scan results available (own=0 ext=0)

WPS: AP 34:31:c4:09:c2:04 type 0 added

WPS: AP 84:a8:e4:99:cd:ad type 0 added

WPS: AP 18:60:24:2b:ae:8e type 0 added

WPS: AP 6e:56:97:bd:83:2a type 0 added

WPS: AP[0] 34:31:c4:09:c2:04 type=0 tries=0 last_attempt=-1 sec ago blacklist=0

WPS: AP[1] 84:a8:e4:99:cd:ad type=0 tries=0 last_attempt=-1 sec ago blacklist=0

WPS: AP[2] 18:60:24:2b:ae:8e type=0 tries=0 last_attempt=-1 sec ago blacklist=0

WPS: AP[3] 6e:56:97:bd:83:2a type=0 tries=0 last_attempt=-1 sec ago blacklist=0

wlan0: Selecting BSS from priority group 0

wlan0: 0: b8:be:bf:ff:eb:50 ssid='\x00' wpa_ie_len=0 rsn_ie_len=20 caps=0x431 level=-40

wlan0: skip - SSID mismatch

wlan0: 1: 34:31:c4:09:c2:04 ssid='Anyong04012016' wpa_ie_len=0 rsn_ie_len=20 caps=0x431 level=-69 wps

wlan0: skip - SSID mismatch

wlan0: 2: 10:8c:cf:ea:e9:70 ssid='\x00' wpa_ie_len=0 rsn_ie_len=22 caps=0x431 level=-76

wlan0: skip - SSID mismatch

wlan0: 3: c4:27:95:85:48:25 ssid='Tech_D0041238' wpa_ie_len=28 rsn_ie_len=24 caps=0x511 level=-84

wlan0: skip - SSID mismatch

wlan0: 4: 84:a8:e4:99:cd:ad ssid='pistoriusnet' wpa_ie_len=28 rsn_ie_len=24 caps=0x411 level=-84 wps

wlan0: skip - SSID mismatch

wlan0: 5: 18:60:24:2b:ae:8e ssid='DIRECT-8D-HP ENVY 5640 series' wpa_ie_len=0 rsn_ie_len=20 caps=0x511 level=-86 wps p2p

wlan0: skip - SSID mismatch

wlan0: 6: 6e:56:97:bd:83:2a ssid='\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' wpa_ie_len=0 rsn_ie_len=20 caps=0x411 level=-87 wps p2p

wlan0: skip - SSID mismatch

wlan0: No suitable network found

wlan0: Use normal scan instead of sched_scan for initial scans (normal_scans=0)

wlan0: Setting scan request: 5.000000 sec

wlan0: Starting delayed sched scan

wlan0: Use normal scan instead of sched_scan for initial scans (normal_scans=0)

wlan0: Rescheduling scan request: 0.000000 sec

wlan0: State: DISCONNECTED -> SCANNING

wlan0: Starting AP scan for wildcard SSID

wlan0: Add radio work 'scan'@0x647d28

wlan0: First radio work item in the queue - schedule start immediately

wlan0: Starting radio work 'scan'@0x647d28 after 0.000038 second wait

wlan0: nl80211: scan request

Scan requested (ret=0) - scan timeout 30 seconds

nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlan0

wlan0: nl80211: Scan trigger

wlan0: Event SCAN_STARTED (47) received

wlan0: Own scan request started a scan in 0.000112 seconds

nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan0

wlan0: nl80211: New scan results available

nl80211: Scan probed for SSID ''

nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472

wlan0: Event SCAN_RESULTS (3) received

wlan0: Scan completed in 0.564656 seconds

nl80211: Received scan results (7 BSSes)

wlan0: BSS: Start scan result update 2

wlan0: BSS: Do not update scan IEs for 18:60:24:2b:ae:8e since that would remove P2P IE information

BSS: last_scan_res_used=7/32

wlan0: New scan results available (own=1 ext=0)

WPS: AP[0] 34:31:c4:09:c2:04 type=0 tries=0 last_attempt=-1 sec ago blacklist=0

WPS: AP[1] 84:a8:e4:99:cd:ad type=0 tries=0 last_attempt=-1 sec ago blacklist=0

WPS: AP[2] 18:60:24:2b:ae:8e type=0 tries=0 last_attempt=-1 sec ago blacklist=0

WPS: AP[3] 6e:56:97:bd:83:2a type=0 tries=0 last_attempt=-1 sec ago blacklist=0

wlan0: Radio work 'scan'@0x647d28 done in 0.599696 seconds

wlan0: Selecting BSS from priority group 0

wlan0: 0: b8:be:bf:ff:eb:50 ssid='\x00' wpa_ie_len=0 rsn_ie_len=20 caps=0x431 level=-39

wlan0: skip - SSID mismatch

wlan0: 1: 34:31:c4:09:c2:04 ssid='Anyong04012016' wpa_ie_len=0 rsn_ie_len=20 caps=0x431 level=-69 wps

wlan0: skip - SSID mismatch

wlan0: 2: 10:8c:cf:ea:e9:70 ssid='\x00' wpa_ie_len=0 rsn_ie_len=22 caps=0x431 level=-75

wlan0: skip - SSID mismatch

wlan0: 3: c4:27:95:85:48:25 ssid='Tech_D0041238' wpa_ie_len=28 rsn_ie_len=24 caps=0x511 level=-86

wlan0: skip - SSID mismatch

wlan0: 4: 84:a8:e4:99:cd:ad ssid='pistoriusnet' wpa_ie_len=28 rsn_ie_len=24 caps=0x411 level=-86 wps

wlan0: skip - SSID mismatch

wlan0: 5: 18:60:24:2b:ae:8e ssid='DIRECT-8D-HP ENVY 5640 series' wpa_ie_len=0 rsn_ie_len=20 caps=0x511 level=-87 wps p2p

wlan0: skip - SSID mismatch

wlan0: 6: 6e:56:97:bd:83:2a ssid='\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' wpa_ie_len=0 rsn_ie_len=20 caps=0x411 level=-87 wps p2p

wlan0: skip - SSID mismatch

wlan0: No suitable network found

wlan0: Use normal scan instead of sched_scan for initial scans (normal_scans=1)

wlan0: Setting scan request: 5.000000 sec

RTM_NEWLINK: ifi_index=3 ifname=wlan0 wext ifi_family=0 ifi_flags=0x1003 ([UP])

EAPOL: disable timer tick

nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlan0

wlan0: nl80211: Scan trigger

wlan0: Event SCAN_STARTED (47) received

wlan0: External program started a scan

RTM_NEWLINK: ifi_index=3 ifname=wlan0 wext ifi_family=0 ifi_flags=0x1003 ([UP])

nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan0

wlan0: nl80211: New scan results available

nl80211: Scan probed for SSID ''

nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472

wlan0: Event SCAN_RESULTS (3) received

wlan0: Scan completed in 0.567791 seconds

nl80211: Received scan results (7 BSSes)

wlan0: BSS: Start scan result update 3

BSS: last_scan_res_used=7/32

wlan0: New scan results available (own=0 ext=1)

wlan0: Do not use results from externally requested scan operation for network selection

wlan0: Starting AP scan for wildcard SSID

wlan0: Determining shared radio frequencies (max len 2)

wlan0: Shared frequencies (len=0): completed iteration

wlan0: Add radio work 'scan'@0x64df00

wlan0: First radio work item in the queue - schedule start immediately

wlan0: Starting radio work 'scan'@0x64df00 after 0.000080 second wait

wlan0: nl80211: scan request

Scan requested (ret=0) - scan timeout 30 seconds

nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlan0

wlan0: nl80211: Scan trigger

wlan0: Event SCAN_STARTED (47) received

wlan0: Own scan request started a scan in 0.000216 seconds

nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlan0

wlan0: nl80211: New scan results available

nl80211: Scan probed for SSID ''

nl80211: Scan included frequencies: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472

wlan0: Event SCAN_RESULTS (3) received

wlan0: Scan completed in 0.567120 seconds

nl80211: Received scan results (7 BSSes)

wlan0: BSS: Start scan result update 4

wlan0: BSS: Do not update scan IEs for 18:60:24:2b:ae:8e since that would remove P2P IE information

BSS: last_scan_res_used=7/32

wlan0: New scan results available (own=1 ext=0)

WPS: AP[0] 34:31:c4:09:c2:04 type=0 tries=0 last_attempt=-1 sec ago blacklist=0

WPS: AP[1] 84:a8:e4:99:cd:ad type=0 tries=0 last_attempt=-1 sec ago blacklist=0

WPS: AP[2] 18:60:24:2b:ae:8e type=0 tries=0 last_attempt=-1 sec ago blacklist=0

WPS: AP[3] 6e:56:97:bd:83:2a type=0 tries=0 last_attempt=-1 sec ago blacklist=0

wlan0: Radio work 'scan'@0x64df00 done in 0.603342 seconds

wlan0: Selecting BSS from priority group 0

wlan0: 0: b8:be:bf:ff:eb:50 ssid='\x00' wpa_ie_len=0 rsn_ie_len=20 caps=0x431 level=-43

wlan0: skip - SSID mismatch

wlan0: 1: 34:31:c4:09:c2:04 ssid='Anyong04012016' wpa_ie_len=0 rsn_ie_len=20 caps=0x431 level=-71 wps

wlan0: skip - SSID mismatch

wlan0: 2: 10:8c:cf:ea:e9:70 ssid='\x00' wpa_ie_len=0 rsn_ie_len=22 caps=0x431 level=-76

wlan0: skip - SSID mismatch

wlan0: 3: c4:27:95:85:48:25 ssid='Tech_D0041238' wpa_ie_len=28 rsn_ie_len=24 caps=0x511 level=-83

wlan0: skip - SSID mismatch

wlan0: 4: 18:60:24:2b:ae:8e ssid='DIRECT-8D-HP ENVY 5640 series' wpa_ie_len=0 rsn_ie_len=20 caps=0x511 level=-84 wps p2p

wlan0: skip - SSID mismatch

wlan0: 5: 84:a8:e4:99:cd:ad ssid='pistoriusnet' wpa_ie_len=28 rsn_ie_len=24 caps=0x411 level=-85 wps

wlan0: skip - SSID mismatch

wlan0: 6: 6e:56:97:bd:83:2a ssid='\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' wpa_ie_len=0 rsn_ie_len=20 caps=0x411 level=-87 wps p2p

wlan0: skip - SSID mismatch

wlan0: No suitable network found

wlan0: Use normal scan instead of sched_scan for initial scans (normal_scans=2)

wlan0: Setting scan request: 5.000000 sec

RTM_NEWLINK: ifi_index=3 ifname=wlan0 wext ifi_family=0 ifi_flags=0x1003 ([UP])

^Cwlan0: Removing interface wlan0

wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:00:00:00:00 reason=3 state=SCANNING

TDLS: Tear down peers

wlan0: State: SCANNING -> DISCONNECTED

nl80211: Set wlan0 operstate 0->0 (DORMANT)

netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)

EAPOL: External notification - portEnabled=0

EAPOL: External notification - portValid=0

wlan0: WPA: Clear old PMK and PTK

wlan0: BSS: Remove id 0 BSSID b8:be:bf:ff:eb:50 SSID '\x00' due to wpa_bss_flush

wlan0: BSS: Remove id 1 BSSID 34:31:c4:09:c2:04 SSID 'Anyong04012016' due to wpa_bss_flush

wlan0: BSS: Remove id 2 BSSID 10:8c:cf:ea:e9:70 SSID '\x00' due to wpa_bss_flush

wlan0: BSS: Remove id 3 BSSID c4:27:95:85:48:25 SSID 'Tech_D0041238' due to wpa_bss_flush

wlan0: BSS: Remove id 5 BSSID 18:60:24:2b:ae:8e SSID 'DIRECT-8D-HP ENVY 5640 series' due to wpa_bss_flush

wlan0: BSS: Remove id 4 BSSID 84:a8:e4:99:cd:ad SSID 'pistoriusnet' due to wpa_bss_flush

wlan0: BSS: Remove id 6 BSSID 6e:56:97:bd:83:2a SSID '\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' due to wpa_bss_flush

wlan0: Cancelling delayed sched scan

wlan0: Cancelling scan request

wlan0: Cancelling authentication timeout

Remove interface wlan0 from radio phy0

Remove radio phy0

nl80211: deinit ifname=wlan0 disabled_11b_rates=0

nl80211: Remove monitor interface: refcount=0

netlink: Operstate: ifindex=3 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)

nl80211: Set mode ifindex 3 iftype 2 (STATION)

nl80211: Unsubscribe mgmt frames handle 0x88ebf029 (mode change)

wlan0: CTRL-EVENT-TERMINATING

Control interface directory not empty - leaving it behind

WLAN Problem: Raspbian friert ein

Participate now!

Tags