Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: WLAN wird (meistens) nicht mehr aktiviert beim Start

  1. #1

    Default WLAN wird (meistens) nicht mehr aktiviert beim Start

    Hallo Forum!
    Mein Laptop läuft mit Leap 15.0 und KDE Plasma 5.12.8. Am 2. Mai gab es ein Update für NetworkManager, und seitdem wird beim Start des Rechners meist nur die kabelgebundene Schnittstelle aktiviert, die WLAN-Verbindung meistens nicht.

    Entferne ich den Haken bei "Drahtlose Verbindungen aktivieren" und setze ihn erneut, werden mögliche WLAN-Verbindungen angezeigt, und zu meiner eigenen wird - erfolglos - eine Verbindung versucht ("Schnittstelle wird eingerichtet").

    Nach einem Neustart des Rechners bekomme ich entweder wie gewohnt eine automatische Verbindung zu kabelgebundenem und drahtlosem Netzwerk, oder aber es wird wiederum nur die wired connection gestartet.

    Ich weiß nicht recht, wo ich mit der Fehlersuche anfangen soll, zumal das eben nicht immer passiert - hat jemand eine Idee?

    Falls das von Belang ist: ich nutze nicht den auto-login für KDE Plasma und kwallet läuft mit leerem Passwort.

  2. #2
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,820

    Default AW: WLAN wird (meistens) nicht mehr aktiviert beim Start

    Benutzt du dhcp (automatische IP Vergabe)?

  3. #3

    Default Re: WLAN wird (meistens) nicht mehr aktiviert beim Start

    Ehrlich gesagt weiß ich nicht mal, wie ich das nachsehen kann...?

  4. #4
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,820

    Default AW: WLAN wird (meistens) nicht mehr aktiviert beim Start

    Dann solltest du mal in den logs nachschauen, wenns mal wieder nicht tut:
    als root:
    Code:
    journalctl -b

  5. #5

    Default Re: WLAN wird (meistens) nicht mehr aktiviert beim Start

    Werde ich tun und die Ausgabe hier posten. Danke einstweilen!

  6. #6

    Default Re: WLAN wird (meistens) nicht mehr aktiviert beim Start

    So, heute geht es wieder nicht. Hier mal die Ausgabe von
    Code:
    journalctl -b
    Code:
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000d9e05000-0x00000000da881fff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000da882000-0x00000000da882fff] usable
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000da883000-0x00000000da8c5fff] ACPI NVS
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000da8c6000-0x00000000dacdafff] usable
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000dacdb000-0x00000000daff0fff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000daff1000-0x00000000daffffff] usable
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000db800000-0x00000000df9fffff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x0000000100000000-0x000000011f5fffff] usable
    Mai 14 18:20:48 linux-z3pw kernel: NX (Execute Disable) protection: active
    Mai 14 18:20:48 linux-z3pw kernel: e820: update [mem 0x95cf3018-0x95d03057] usable ==> usable
    Mai 14 18:20:48 linux-z3pw kernel: e820: update [mem 0x95cf3018-0x95d03057] usable ==> usable
    Mai 14 18:20:48 linux-z3pw kernel: e820: update [mem 0x95ce5018-0x95cf2057] usable ==> usable
    Mai 14 18:20:48 linux-z3pw kernel: e820: update [mem 0x95ce5018-0x95cf2057] usable ==> usable
    Mai 14 18:20:48 linux-z3pw kernel: extended physical RAM map:
    Mai 14 18:20:48 linux-z3pw kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
    Mai 14 18:20:48 linux-z3pw kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: reserve setup_data: [mem 0x0000000000100000-0x000000001fffffff] usable
    Mai 14 18:20:48 linux-z3pw kernel: reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
    Mir fiel aber ein, dass ich var/log/messages benutze (gehört glaube ich nicht mehr zur Standardinstallation, aber ist evtl. aufschlußreicher?)

    Code:
    Mai 14 18:20:48 linux-z3pw kernel: Linux version 4.12.14-lp150.12.58-default (geeko@buildhost) (gcc version 7.3.1 20180323 [gcc-7-branch revision 258812] (SUSE Linux) ) #1 SMP Mon Apr 1 15>
    2019-05-13T16:57:23.243572+02:00 linux-z3pw kernel: [   47.298014] NET: Registered protocol family 17
    2019-05-13T16:57:25.755711+02:00 linux-z3pw kernel: [   49.810329] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    2019-05-13T16:57:26.364439+02:00 linux-z3pw btrfsmaintenance-refresh-cron.sh[1129]: Refresh timer btrfs-trim for weekly
    2019-05-13T16:57:26.364571+02:00 linux-z3pw echo[1319]: Starting mail service (Postfix)
    2019-05-13T16:57:26.364740+02:00 linux-z3pw denyhosts[1295]: Starting DenyHosts ..done
    2019-05-13T16:57:26.365974+02:00 linux-z3pw dbus-daemon[1136]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.6' (uid=0 pid=1214 comm="/usr/sbin/NetworkManager --no-daemon ")
    2019-05-13T16:57:26.367721+02:00 linux-z3pw dbus-daemon[1136]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
    2019-05-13T16:57:26.368973+02:00 linux-z3pw systemd[1]: Started Discard unused blocks.
    2019-05-13T16:57:26.369433+02:00 linux-z3pw systemd[1]: Started Balance block groups on a btrfs filesystem.
    2019-05-13T16:57:26.369701+02:00 linux-z3pw rsyslogd:  [origin software="rsyslogd" swVersion="8.33.1" x-pid="1222" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
    2019-05-13T16:57:26.369897+02:00 linux-z3pw systemd[1]: Reloading.
    2019-05-13T16:57:26.370168+02:00 linux-z3pw avahi-daemon[1217]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.20.
    2019-05-13T16:57:26.370392+02:00 linux-z3pw systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped
    2019-05-13T16:57:26.370577+02:00 linux-z3pw postfix[1421]: find: '/etc/postfix/./ssl/cacerts/e36a6752.0': No such file or directory
    2019-05-13T16:57:26.370659+02:00 linux-z3pw postfix[1421]: find: '/etc/postfix/./ssl/cacerts/b872f2b4.0': No such file or directory
    2019-05-13T16:57:26.370835+02:00 linux-z3pw avahi-daemon[1217]: New relevant interface eth0.IPv4 for mDNS.
    2019-05-13T16:57:26.371209+02:00 linux-z3pw postfix[1421]: find: '/etc/postfix/./ssl/cacerts/d7746a63.0': No such file or directory
    2019-05-13T16:57:26.371436+02:00 linux-z3pw avahi-daemon[1217]: Registering new address record for 192.168.178.20 on eth0.IPv4.
    2019-05-13T16:57:26.372024+02:00 linux-z3pw avahi-daemon[1217]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::4:69d1:8969:667f.
    2019-05-13T16:57:26.372409+02:00 linux-z3pw avahi-daemon[1217]: New relevant interface eth0.IPv6 for mDNS.
    2019-05-13T16:57:26.372744+02:00 linux-z3pw avahi-daemon[1217]: Registering new address record for fe80::4:69d1:8969:667f on eth0.*.
    2019-05-13T16:57:26.373070+02:00 linux-z3pw dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
    2019-05-13T16:57:26.373356+02:00 linux-z3pw dns-resolver: You can find my version in /etc/resolv.conf.netconfig
    2019-05-13T16:57:26.374851+02:00 linux-z3pw ModemManager[1218]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0': not supported by any plugin
    2019-05-13T16:57:26.375184+02:00 linux-z3pw ModemManager[1218]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0': not supported by any plugin
    2019-05-13T16:57:26.375669+02:00 linux-z3pw systemd[1]: Starting WPA Supplicant daemon...
    2019-05-13T16:57:26.376017+02:00 linux-z3pw systemd[1]: Reloading.
    2019-05-13T16:57:26.376165+02:00 linux-z3pw dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
    2019-05-13T16:57:26.376257+02:00 linux-z3pw systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped
    2019-05-13T16:57:26.376408+02:00 linux-z3pw dns-resolver: You can find my version in /etc/resolv.conf.netconfig
    2019-05-13T16:57:26.376500+02:00 linux-z3pw systemd[1]: Started WPA Supplicant daemon.
    2019-05-13T16:57:26.376808+02:00 linux-z3pw systemd[1]: Started Update cron periods from /etc/sysconfig/btrfsmaintenance.
    2019-05-13T16:57:26.376964+02:00 linux-z3pw cron[1784]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 56% if used.)
    2019-05-13T16:57:26.377151+02:00 linux-z3pw systemd[1]: Started LSB: denyhosts daemon to block ssh attempts.
    2019-05-13T16:57:26.377299+02:00 linux-z3pw cron[1784]: (CRON) INFO (running with inotify support)
    2019-05-13T16:57:26.377460+02:00 linux-z3pw systemd[1]: Reloading System Logging Service.
    2019-05-13T16:57:26.378788+02:00 linux-z3pw systemd[1]: Started Modem Manager.
    2019-05-13T16:57:26.379294+02:00 linux-z3pw systemd[1]: Reloaded System Logging Service.
    2019-05-13T16:57:26.381870+02:00 linux-z3pw systemd-hostnamed[1246]: Changed host name to 'linux-z3pw.suse'
    2019-05-13T16:57:26.382041+02:00 linux-z3pw systemd[1]: Started Backup /etc/sysconfig directory.
    2019-05-13T16:57:26.383904+02:00 linux-z3pw systemd[1]: Started Update system wide CA certificates.
    Das passiert, wenn ich
    Code:
    tail -f /var/log/messages
    laufen lasse, während ich versuche, die WLAN-Verbindung per Klick auf den Netzwerk-Manager im Systemabschnitt der Kontrollleiste starten will:

    Code:
    2019-05-14T18:47:42.688555+02:00 linux-z3pw kwin_x11[2122]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 12370, resource id: 0, major code: 14 (GetGeometry), minor code: 0
    2019-05-14T18:47:45.819798+02:00 linux-z3pw kernel: [ 1620.315646] iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
    2019-05-14T18:47:46.123805+02:00 linux-z3pw kernel: [ 1620.620297] iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
    2019-05-14T18:47:46.207798+02:00 linux-z3pw kernel: [ 1620.703289] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    2019-05-14T18:47:46.219491+02:00 linux-z3pw kdeinit5[2086]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags"
    2019-05-14T18:47:46.220170+02:00 linux-z3pw plasmashell[2135]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags"
    2019-05-14T18:47:46.225558+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: Unhandled active connection state change:  1
    2019-05-14T18:47:46.227976+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: virtual NMVariantMapMap SecretAgent::GetSecrets(const NMVariantMapMap&, const QDBusObjectPath&, const QString&, const QStringList&, uint)
    2019-05-14T18:47:46.228316+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: Path: "/org/freedesktop/NetworkManager/Settings/1"
    2019-05-14T18:47:46.228576+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: Setting name: "802-11-wireless-security"
    2019-05-14T18:47:46.228834+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: Hints: ()
    2019-05-14T18:47:46.229076+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: Flags: 13
    2019-05-14T18:47:49.479784+02:00 linux-z3pw kernel: [ 1623.976361] wlan0: authenticate with 38:10:d5:cc:b4:03
    2019-05-14T18:47:49.483780+02:00 linux-z3pw kernel: [ 1623.978547] wlan0: send auth to 38:10:d5:cc:b4:03 (try 1/3)
    2019-05-14T18:47:50.279778+02:00 linux-z3pw kernel: [ 1624.772578] wlan0: send auth to 38:10:d5:cc:b4:03 (try 2/3)
    2019-05-14T18:47:51.283774+02:00 linux-z3pw kernel: [ 1625.777962] wlan0: send auth to 38:10:d5:cc:b4:03 (try 3/3)
    2019-05-14T18:47:52.307775+02:00 linux-z3pw kernel: [ 1626.801876] wlan0: authentication with 38:10:d5:cc:b4:03 timed out
    Nach dem "timed out" wiederholt sich das dann.
    Ich hoffe, das war jetzt nicht zu viel, aber wer das lesen und verstehen kann, ist jetzt schlauer als ich, nehme ich an...

  7. #7
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,820

    Default AW: WLAN wird (meistens) nicht mehr aktiviert beim Start

    Poste mal:
    Code:
    zypper lr -d
    und versuch mal wenns nicht geht als root:
    Code:
    netconfig update -f

  8. #8
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    829

    Default Re: WLAN wird (meistens) nicht mehr aktiviert beim Start

    Quote Originally Posted by JuergenGr View Post
    So, heute geht es wieder nicht. Hier mal die Ausgabe von
    Code:
    journalctl -b
    Code:
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000d9e05000-0x00000000da881fff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000da882000-0x00000000da882fff] usable
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000da883000-0x00000000da8c5fff] ACPI NVS
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000da8c6000-0x00000000dacdafff] usable
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000dacdb000-0x00000000daff0fff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000daff1000-0x00000000daffffff] usable
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000db800000-0x00000000df9fffff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: BIOS-e820: [mem 0x0000000100000000-0x000000011f5fffff] usable
    Mai 14 18:20:48 linux-z3pw kernel: NX (Execute Disable) protection: active
    Mai 14 18:20:48 linux-z3pw kernel: e820: update [mem 0x95cf3018-0x95d03057] usable ==> usable
    Mai 14 18:20:48 linux-z3pw kernel: e820: update [mem 0x95cf3018-0x95d03057] usable ==> usable
    Mai 14 18:20:48 linux-z3pw kernel: e820: update [mem 0x95ce5018-0x95cf2057] usable ==> usable
    Mai 14 18:20:48 linux-z3pw kernel: e820: update [mem 0x95ce5018-0x95cf2057] usable ==> usable
    Mai 14 18:20:48 linux-z3pw kernel: extended physical RAM map:
    Mai 14 18:20:48 linux-z3pw kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
    Mai 14 18:20:48 linux-z3pw kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
    Mai 14 18:20:48 linux-z3pw kernel: reserve setup_data: [mem 0x0000000000100000-0x000000001fffffff] usable
    Mai 14 18:20:48 linux-z3pw kernel: reserve setup_data: [mem 0x0000000020000000-0x00000000201fffff] reserved
    Mir fiel aber ein, dass ich var/log/messages benutze (gehört glaube ich nicht mehr zur Standardinstallation, aber ist evtl. aufschlußreicher?)

    Code:
    Mai 14 18:20:48 linux-z3pw kernel: Linux version 4.12.14-lp150.12.58-default (geeko@buildhost) (gcc version 7.3.1 20180323 [gcc-7-branch revision 258812] (SUSE Linux) ) #1 SMP Mon Apr 1 15>
    2019-05-13T16:57:23.243572+02:00 linux-z3pw kernel: [   47.298014] NET: Registered protocol family 17
    2019-05-13T16:57:25.755711+02:00 linux-z3pw kernel: [   49.810329] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    2019-05-13T16:57:26.364439+02:00 linux-z3pw btrfsmaintenance-refresh-cron.sh[1129]: Refresh timer btrfs-trim for weekly
    2019-05-13T16:57:26.364571+02:00 linux-z3pw echo[1319]: Starting mail service (Postfix)
    2019-05-13T16:57:26.364740+02:00 linux-z3pw denyhosts[1295]: Starting DenyHosts ..done
    2019-05-13T16:57:26.365974+02:00 linux-z3pw dbus-daemon[1136]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.6' (uid=0 pid=1214 comm="/usr/sbin/NetworkManager --no-daemon ")
    2019-05-13T16:57:26.367721+02:00 linux-z3pw dbus-daemon[1136]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
    2019-05-13T16:57:26.368973+02:00 linux-z3pw systemd[1]: Started Discard unused blocks.
    2019-05-13T16:57:26.369433+02:00 linux-z3pw systemd[1]: Started Balance block groups on a btrfs filesystem.
    2019-05-13T16:57:26.369701+02:00 linux-z3pw rsyslogd:  [origin software="rsyslogd" swVersion="8.33.1" x-pid="1222" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
    2019-05-13T16:57:26.369897+02:00 linux-z3pw systemd[1]: Reloading.
    2019-05-13T16:57:26.370168+02:00 linux-z3pw avahi-daemon[1217]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.178.20.
    2019-05-13T16:57:26.370392+02:00 linux-z3pw systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped
    2019-05-13T16:57:26.370577+02:00 linux-z3pw postfix[1421]: find: '/etc/postfix/./ssl/cacerts/e36a6752.0': No such file or directory
    2019-05-13T16:57:26.370659+02:00 linux-z3pw postfix[1421]: find: '/etc/postfix/./ssl/cacerts/b872f2b4.0': No such file or directory
    2019-05-13T16:57:26.370835+02:00 linux-z3pw avahi-daemon[1217]: New relevant interface eth0.IPv4 for mDNS.
    2019-05-13T16:57:26.371209+02:00 linux-z3pw postfix[1421]: find: '/etc/postfix/./ssl/cacerts/d7746a63.0': No such file or directory
    2019-05-13T16:57:26.371436+02:00 linux-z3pw avahi-daemon[1217]: Registering new address record for 192.168.178.20 on eth0.IPv4.
    2019-05-13T16:57:26.372024+02:00 linux-z3pw avahi-daemon[1217]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::4:69d1:8969:667f.
    2019-05-13T16:57:26.372409+02:00 linux-z3pw avahi-daemon[1217]: New relevant interface eth0.IPv6 for mDNS.
    2019-05-13T16:57:26.372744+02:00 linux-z3pw avahi-daemon[1217]: Registering new address record for fe80::4:69d1:8969:667f on eth0.*.
    2019-05-13T16:57:26.373070+02:00 linux-z3pw dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
    2019-05-13T16:57:26.373356+02:00 linux-z3pw dns-resolver: You can find my version in /etc/resolv.conf.netconfig
    2019-05-13T16:57:26.374851+02:00 linux-z3pw ModemManager[1218]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0': not supported by any plugin
    2019-05-13T16:57:26.375184+02:00 linux-z3pw ModemManager[1218]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0': not supported by any plugin
    2019-05-13T16:57:26.375669+02:00 linux-z3pw systemd[1]: Starting WPA Supplicant daemon...
    2019-05-13T16:57:26.376017+02:00 linux-z3pw systemd[1]: Reloading.
    2019-05-13T16:57:26.376165+02:00 linux-z3pw dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
    2019-05-13T16:57:26.376257+02:00 linux-z3pw systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped
    2019-05-13T16:57:26.376408+02:00 linux-z3pw dns-resolver: You can find my version in /etc/resolv.conf.netconfig
    2019-05-13T16:57:26.376500+02:00 linux-z3pw systemd[1]: Started WPA Supplicant daemon.
    2019-05-13T16:57:26.376808+02:00 linux-z3pw systemd[1]: Started Update cron periods from /etc/sysconfig/btrfsmaintenance.
    2019-05-13T16:57:26.376964+02:00 linux-z3pw cron[1784]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 56% if used.)
    2019-05-13T16:57:26.377151+02:00 linux-z3pw systemd[1]: Started LSB: denyhosts daemon to block ssh attempts.
    2019-05-13T16:57:26.377299+02:00 linux-z3pw cron[1784]: (CRON) INFO (running with inotify support)
    2019-05-13T16:57:26.377460+02:00 linux-z3pw systemd[1]: Reloading System Logging Service.
    2019-05-13T16:57:26.378788+02:00 linux-z3pw systemd[1]: Started Modem Manager.
    2019-05-13T16:57:26.379294+02:00 linux-z3pw systemd[1]: Reloaded System Logging Service.
    2019-05-13T16:57:26.381870+02:00 linux-z3pw systemd-hostnamed[1246]: Changed host name to 'linux-z3pw.suse'
    2019-05-13T16:57:26.382041+02:00 linux-z3pw systemd[1]: Started Backup /etc/sysconfig directory.
    2019-05-13T16:57:26.383904+02:00 linux-z3pw systemd[1]: Started Update system wide CA certificates.
    Das passiert, wenn ich
    Code:
    tail -f /var/log/messages
    laufen lasse, während ich versuche, die WLAN-Verbindung per Klick auf den Netzwerk-Manager im Systemabschnitt der Kontrollleiste starten will:

    Code:
    2019-05-14T18:47:42.688555+02:00 linux-z3pw kwin_x11[2122]: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 12370, resource id: 0, major code: 14 (GetGeometry), minor code: 0
    2019-05-14T18:47:45.819798+02:00 linux-z3pw kernel: [ 1620.315646] iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
    2019-05-14T18:47:46.123805+02:00 linux-z3pw kernel: [ 1620.620297] iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
    2019-05-14T18:47:46.207798+02:00 linux-z3pw kernel: [ 1620.703289] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    2019-05-14T18:47:46.219491+02:00 linux-z3pw kdeinit5[2086]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags"
    2019-05-14T18:47:46.220170+02:00 linux-z3pw plasmashell[2135]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags"
    2019-05-14T18:47:46.225558+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: Unhandled active connection state change:  1
    2019-05-14T18:47:46.227976+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: virtual NMVariantMapMap SecretAgent::GetSecrets(const NMVariantMapMap&, const QDBusObjectPath&, const QString&, const QStringList&, uint)
    2019-05-14T18:47:46.228316+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: Path: "/org/freedesktop/NetworkManager/Settings/1"
    2019-05-14T18:47:46.228576+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: Setting name: "802-11-wireless-security"
    2019-05-14T18:47:46.228834+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: Hints: ()
    2019-05-14T18:47:46.229076+02:00 linux-z3pw kdeinit5[2086]: plasma-nm: Flags: 13
    2019-05-14T18:47:49.479784+02:00 linux-z3pw kernel: [ 1623.976361] wlan0: authenticate with 38:10:d5:cc:b4:03
    2019-05-14T18:47:49.483780+02:00 linux-z3pw kernel: [ 1623.978547] wlan0: send auth to 38:10:d5:cc:b4:03 (try 1/3)
    2019-05-14T18:47:50.279778+02:00 linux-z3pw kernel: [ 1624.772578] wlan0: send auth to 38:10:d5:cc:b4:03 (try 2/3)
    2019-05-14T18:47:51.283774+02:00 linux-z3pw kernel: [ 1625.777962] wlan0: send auth to 38:10:d5:cc:b4:03 (try 3/3)
    2019-05-14T18:47:52.307775+02:00 linux-z3pw kernel: [ 1626.801876] wlan0: authentication with 38:10:d5:cc:b4:03 timed out
    Nach dem "timed out" wiederholt sich das dann.
    Ich hoffe, das war jetzt nicht zu viel, aber wer das lesen und verstehen kann, ist jetzt schlauer als ich, nehme ich an...
    Die obigen Logs sind sehr unspezifisch und mühsam zu lesen. Übersichtlicher und zweckdienlicher ist möglicherweise die Ausgabe von:

    Code:
    erlangen:~ # journalctl -b -1 -u wpa*
    -- Logs begin at Wed 2019-04-10 09:08:16 CEST, end at Wed 2019-05-15 07:38:39 CEST. --
    May 12 18:58:24 erlangen systemd[1]: Starting WPA Supplicant daemon (interface wlp3s0)...
    May 12 18:58:24 erlangen systemd[1]: Started WPA Supplicant daemon (interface wlp3s0).
    May 14 07:27:13 erlangen systemd[1]: Stopping WPA Supplicant daemon (interface wlp3s0)...
    May 14 07:27:14 erlangen systemd[1]: wpa_supplicant@wlp3s0.service: Succeeded.
    May 14 07:27:14 erlangen systemd[1]: Stopped WPA Supplicant daemon (interface wlp3s0).
    erlangen:~ #
    Ändere die Boot Nummer -b -1 entsprechend ab. Der Inhalt von /var/log/wpa_supplicant.log wäre auch interessant. Der Zeitangabe kann hier umgerechnet werden: https://www.epochconverter.com/
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  9. #9

    Default Re: WLAN wird (meistens) nicht mehr aktiviert beim Start

    Heute wurde wieder klaglos ins WLAN verbunden, aber hier schon mal die Ausgabe von
    Code:
    zypper lr -d
    Code:
    Die Repository-Prioritäten sind ohne Effekt. Alle aktivierten Repositorys teilen sich die gleiche Priorität.
    
    #  | Alias                           | Name                                                    | Aktiviert | GPG-Überprüfung | Aktualisierung | Priorität | Typ      | URI                                                                         | Dienst
    ---+---------------------------------+---------------------------------------------------------+-----------+-----------------+----------------+-----------+----------+-----------------------------------------------------------------------------+-------
     1 | download.opensuse.org-non-oss   | Haupt-Repository (NON-OSS)                              | Ja        | (r ) Ja         | Ja             |   99      | rpm-md   | http://download.opensuse.org/distribution/leap/15.0/repo/non-oss/           |      
     2 | download.opensuse.org-non-oss_1 | Aktualisierungs-Repository (Nicht-Open-Source-Software) | Ja        | (r ) Ja         | Ja             |   99      | rpm-md   | http://download.opensuse.org/update/leap/15.0/non-oss/                      |      
     3 | download.opensuse.org-oss       | Haupt-Repository (OSS)                                  | Ja        | (r ) Ja         | Ja             |   99      | rpm-md   | http://download.opensuse.org/distribution/leap/15.0/repo/oss/               |      
     4 | download.opensuse.org-oss_1     | Hauptaktualisierungs-Repository                         | Ja        | (r ) Ja         | Ja             |   99      | rpm-md   | http://download.opensuse.org/update/leap/15.0/oss                           |      
     5 | install                         | Lokaler Ordner                                          | Ja        | ( p) Ja         | Nein           |   99      | plaindir | dir:///home/gringmuth/install                                               |      
     6 | openSUSE-Leap-15.0-1            | openSUSE-Leap-15.0-1                                    | Nein      | ----            | ----           |   99      | rpm-md   | cd:///?devices=/dev/disk/by-id/ata-MATSHITA_DVD-RAM_UJ8E1_1343TP216683ESR6H |      
     7 | opensuse-guide.org-repo         | Libdvdcss Repository                                    | Ja        | (r ) Ja         | Ja             |   99      | rpm-md   | http://opensuse-guide.org/repo/openSUSE_Leap_15.0/                          |      
     8 | packman.inode.at-suse           | Packman Repository                                      | Ja        | (r ) Ja         | Ja             |   99      | rpm-md   | http://packman.inode.at/suse/openSUSE_Leap_15.0/                            |      
     9 | repo-debug                      | openSUSE-Leap-15.0-Debug                                | Nein      | ----            | ----           |   99      | rpm-md   | http://download.opensuse.org/debug/distribution/leap/15.0/repo/oss/         |      
    10 | repo-debug-non-oss              | openSUSE-Leap-15.0-Debug-Non-Oss                        | Nein      | ----            | ----           |   99      | rpm-md   | http://download.opensuse.org/debug/distribution/leap/15.0/repo/non-oss/     |      
    11 | repo-debug-update               | openSUSE-Leap-15.0-Update-Debug                         | Nein      | ----            | ----           |   99      | rpm-md   | http://download.opensuse.org/debug/update/leap/15.0/oss/                    |      
    12 | repo-debug-update-non-oss       | openSUSE-Leap-15.0-Update-Debug-Non-Oss                 | Nein      | ----            | ----           |   99      | rpm-md   | http://download.opensuse.org/debug/update/leap/15.0/non-oss/                |      
    13 | repo-source                     | openSUSE-Leap-15.0-Source                               | Nein      | ----            | ----           |   99      | rpm-md   | http://download.opensuse.org/source/distribution/leap/15.0/repo/oss/        |      
    14 | repo-source-non-oss             | openSUSE-Leap-15.0-Source-Non-Oss                       | Nein      | ----            | ----           |   99      | rpm-md   | http://download.opensuse.org/source/distribution/leap/15.0/repo/non-oss/    |      
    15 | x86_64                          | Google Chrome                                           | Ja        | (r ) Ja         | Ja             |   99      | rpm-md   | http://dl.google.com/linux/chrome/rpm/stable/x86_64                         |
    Ich nehme an, der Rest macht nur Sinn, wenn es nicht funktioniert

  10. #10

    Default Re: WLAN wird (meistens) nicht mehr aktiviert beim Start

    Quote Originally Posted by karlmistelberger View Post
    [/CODE]Ändere die Boot Nummer -b -1 entsprechend ab. Der Inhalt von /var/log/wpa_supplicant.log wäre auch interessant. Der Zeitangabe kann hier umgerechnet werden: https://www.epochconverter.com/
    Das mit dem ändern der Boot-Nummer hab' ich nicht kapiert, sorry.

    Hier der Inhalt von /var/log/wpa_supplicant.log - auch wenn ich annehme, dass auch das interessanter wäre, wenn es nicht läuft:


    Code:
    1546298689.251863: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546299289.287384: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546299889.322656: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546300489.358218: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546301089.393331: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546301689.428315: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546302289.463408: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546302889.499290: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546303489.533202: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546303589.593297: wlan0: CTRL-EVENT-DISCONNECTED bssid=38:10:d5:cc:b4:03 reason=3 locally_generated=1
    1546303590.518821: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
    1546303594.805435: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
    1546303594.829387: wlan0: CTRL-EVENT-TERMINATING
    1546354488.309664: Successfully initialized wpa_supplicant
    1546354556.186258: wlan0: Reject scan trigger since one is already pending
    1546354594.232534: wlan0: SME: Trying to authenticate with 38:10:d5:cc:b4:03 (SSID='FRITZ!Box 7490' freq=5180 MHz)
    1546354594.251341: wlan0: Trying to associate with 38:10:d5:cc:b4:03 (SSID='FRITZ!Box 7490' freq=5180 MHz)
    1546354594.273920: wlan0: Associated with 38:10:d5:cc:b4:03
    1546354594.273976: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
    1546354594.276971: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE
    1546354595.756672: wlan0: WPA: Key negotiation completed with 38:10:d5:cc:b4:03 [PTK=CCMP GTK=CCMP]
    1546354595.756715: wlan0: CTRL-EVENT-CONNECTED - Connection to 38:10:d5:cc:b4:03 completed [id=0 id_str=]
    1546354595.786020: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-41 noise=9999 txrate=6000
    1546354626.200755: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546355226.290526: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546355826.299913: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546356426.321519: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546357026.301033: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546357626.327104: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546358226.352642: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546358826.377230: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546359426.402638: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546360026.428060: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546360626.453339: wlan0: WPA: Group rekeying completed with 38:10:d5:cc:b4:03 [GTK=CCMP]
    1546360879.844005: wlan0: CTRL-EVENT-DISCONNECTED bssid=38:10:d5:cc:b4:03 reason=3
    1546360880.346011: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •