Re: Kein WiFi mehr - Probleme mit dem Kernelmodul?!?
-- TL; DR --
Jetzt geht es wieder und ich habe nur Windows zwischendurch gestartet.
-- TL; DR --
Das Gute: Es geht wieder.
Das Schlechte: Ich bin nicht schlauer geworden.
>> Es ist ein klassicher Fall von: "Letze Woche ging's noch und ich hab'
>> wirklich nichts getan."
> Was hast Du denn nun wirklich geändert?
Wenn ich das nur wüsste! Wie oben schon geschrieben, habe ich zwischen
dem Verfassen der Mail (unter Windows) nur die Details unter Debian
gesammelt, die ich in der letzten Mail schon beschrieben habe.
Für das Sammeln der Infos wie dmesg oder dem Inhalt von /var/log/syslog
habe ich heute Debian gestartet und finde ein funktionierendes wlp5s0
Interface vor. :-/
>> root@debtop:~# modprobe iwlwifi -vvv
>> modprobe: INFO: ../libkmod/libkmod.c:364 kmod_set_log_fn() custom
>> logging function 0x55d314259150 registered
>> modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open()
>> file=/lib/modules/4.19.0-10-amd64/modules.dep.bin
>> modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open()
>> file=/lib/modules/4.19.0-10-amd64/modules.alias.bin
>> (...)
>> modprobe: DEBUG: ../libkmod/libkmod-module.c:1393
>> kmod_module_get_options() modname=bonding mod->name=iwlwifi
>> mod->alias=(null)
>> modprobe: DEBUG: ../libkmod/libkmod-module.c:1393
>> kmod_module_get_options() modname=dummy mod->name=iwlwifi mod->alias=(null)
>> modprobe: DEBUG: ../libkmod/libkmod-module.c:1750
>> kmod_module_get_initstate() could not open
>> '/sys/module/iwlwifi/initstate': No such file or directory
>
>
> Hier wäre es jetzt gut zu wissen wie das im Gutfall aussieht.
So sieht der Gutfall aus:
root@debtop:~# modprobe -vvv iwlwifi
modprobe: INFO: ../libkmod/libkmod.c:364 kmod_set_log_fn() custom
logging function 0x55ed0b432150 registered
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open()
file=/lib/modules/4.19.0-10-amd64/modules.dep.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open()
file=/lib/modules/4.19.0-10-amd64/modules.alias.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open()
file=/lib/modules/4.19.0-10-amd64/modules.symbols.bin
modprobe: DEBUG: ../libkmod/libkmod-index.c:755 index_mm_open()
file=/lib/modules/4.19.0-10-amd64/modules.builtin.bin
modprobe: DEBUG: ../libkmod/libkmod-module.c:556
kmod_module_new_from_lookup() input alias=iwlwifi, normalized=iwlwifi
modprobe: DEBUG: ../libkmod/libkmod-module.c:562
kmod_module_new_from_lookup() lookup modules.dep iwlwifi
modprobe: DEBUG: ../libkmod/libkmod.c:574 kmod_search_moddep() use
mmaped index 'modules.dep' modname=iwlwifi
modprobe: DEBUG: ../libkmod/libkmod.c:402 kmod_pool_get_module() get
module name='iwlwifi' found=(nil)
modprobe: DEBUG: ../libkmod/libkmod.c:410 kmod_pool_add_module() add
0x55ed0bc00fe0 key='iwlwifi'
modprobe: DEBUG: ../libkmod/libkmod.c:402 kmod_pool_get_module() get
module name='cfg80211' found=(nil)
modprobe: DEBUG: ../libkmod/libkmod.c:402 kmod_pool_get_module() get
module name='cfg80211' found=(nil)
modprobe: DEBUG: ../libkmod/libkmod.c:410 kmod_pool_add_module() add
0x55ed0bc011a0 key='cfg80211'
modprobe: DEBUG: ../libkmod/libkmod-module.c:196
kmod_module_parse_depline() add dep:
/lib/modules/4.19.0-10-amd64/kernel/net/wireless/cfg80211.ko
modprobe: DEBUG: ../libkmod/libkmod.c:402 kmod_pool_get_module() get
module name='rfkill' found=(nil)
modprobe: DEBUG: ../libkmod/libkmod.c:402 kmod_pool_get_module() get
module name='rfkill' found=(nil)
modprobe: DEBUG: ../libkmod/libkmod.c:410 kmod_pool_add_module() add
0x55ed0bc01320 key='rfkill'
modprobe: DEBUG: ../libkmod/libkmod-module.c:196
kmod_module_parse_depline() add dep:
/lib/modules/4.19.0-10-amd64/kernel/net/rfkill/rfkill.ko
modprobe: DEBUG: ../libkmod/libkmod-module.c:202
kmod_module_parse_depline() 2 dependencies for iwlwifi
modprobe: DEBUG: ../libkmod/libkmod-module.c:583
kmod_module_new_from_lookup() lookup iwlwifi=0, list=0x55ed0bc005e0
modprobe: DEBUG: ../libkmod/libkmod.c:501 lookup_builtin_file() use
mmaped index 'modules.builtin' modname=iwlwifi
modprobe: DEBUG: ../libkmod/libkmod-module.c:468 kmod_module_unref()
kmod_module 0x55ed0bc00fe0 released
modprobe: DEBUG: ../libkmod/libkmod.c:418 kmod_pool_del_module() del
0x55ed0bc00fe0 key='iwlwifi'
modprobe: DEBUG: ../libkmod/libkmod-module.c:468 kmod_module_unref()
kmod_module 0x55ed0bc01320 released
modprobe: DEBUG: ../libkmod/libkmod.c:418 kmod_pool_del_module() del
0x55ed0bc01320 key='rfkill'
modprobe: DEBUG: ../libkmod/libkmod-module.c:468 kmod_module_unref()
kmod_module 0x55ed0bc011a0 released
modprobe: DEBUG: ../libkmod/libkmod.c:418 kmod_pool_del_module() del
0x55ed0bc011a0 key='cfg80211'
modprobe: INFO: ../libkmod/libkmod.c:331 kmod_unref() context
0x55ed0bc00440 released
root@debtop:~#
> Leider
> schreibst Du ja auch nicht, welches Debian, welche Kernelversion oder
> welche Wifi-Karte.
Das Debian ist ein Debian 10.5 mit Kernel 4.19.132-1.
Die Wifi-Karte stellt sich in lspci so dar:
05:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
Subsystem: Intel Corporation Wireless-AC 9260
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f7400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] L1 PM Substates
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
> Bei meiner IWL 8260 mit Kernel 5.8.9 gibt es
> /sys/module/iwlwifi/initstate jedenfalls, aber ich hab das Modul ja
> auch geladen.
Mit meinem geladenen iwlwifi gibt es die Ordner und Dateien jetzt
(natürlich) auch.
>> insmod
>> /lib/modules/4.19.0-10-amd64/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
>>
>> modprobe: DEBUG: ../libkmod/libkmod-module.c:744 kmod_module_get_path()
>> name='iwlwifi'
>> path='/lib/modules/4.19.0-10-amd64/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko'
>
> Interessant wäre ob das dann erfolgreich ist.
Ein insmod funktioniert nicht, weil das Modul geladen ist.
Interessant ist, dass ein "rmmod iwlwifi" auch nicht funktioniert, weil
es vom Modul iwlmvm genutzt wird. Das war beim Schreiben der ersten Mail
nicht der Fall.
> Was steht in dmesg bzw. im syslog?
Das ist dmesg im Gutfall:
[ 53.155185] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[ 53.208900] r8169 0000:08:00.0: firmware: direct-loading firmware
rtl_nic/rtl8168h-2.fw
[ 53.209135] Generic PHY r8169-800:00: attached PHY driver [Generic
PHY] (mii_bus:phy_addr=r8169-800:00, irq=IGNORE)
[ 53.319045] r8169 0000:08:00.0 enp8s0: Link is Down
[ 53.319133] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready
[ 53.452033] resource sanity check: requesting [mem
0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem
0x000c0000-0x000dffff window]
[ 53.452144] caller _nv000936rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
[ 54.906213] r8169 0000:08:00.0 enp8s0: Link is Up - 100Mbps/Full -
flow control rx/tx
[ 54.906222] IPv6: ADDRCONF(NETDEV_CHANGE): enp8s0: link becomes ready
[ 56.890732] wlp5s0: authenticate with c0:25:06:f5:7f:07
[ 56.892299] wlp5s0: send auth to c0:25:06:f5:7f:07 (try 1/3)
[ 56.934424] wlp5s0: authenticated
[ 56.936050] wlp5s0: associate with c0:25:06:f5:7f:07 (try 1/3)
[ 56.939262] wlp5s0: RX AssocResp from c0:25:06:f5:7f:07 (capab=0x1511
status=0 aid=4)
[ 56.941012] wlp5s0: associated
[ 56.944388] wlp5s0: Limiting TX power to 27 (30 - 3) dBm as
advertised by c0:25:06:f5:7f:07
[ 57.458653] iwlwifi 0000:05:00.0: Unhandled alg: 0x707
[ 59.402540] iwlwifi 0000:05:00.0: Unhandled alg: 0x707
[ 60.940800] iwlwifi 0000:05:00.0: Unhandled alg: 0x707
[ 60.940926] iwlwifi 0000:05:00.0: Unhandled alg: 0x707
[ 60.981783] wlp5s0: disassociated from c0:25:06:f5:7f:07 (Reason:
2=PREV_AUTH_NOT_VALID)
[ 63.185289] wlp5s0: authenticate with c0:25:06:f5:7f:06
[ 63.188906] wlp5s0: send auth to c0:25:06:f5:7f:06 (try 1/3)
[ 63.226707] wlp5s0: authenticated
[ 63.228033] wlp5s0: associate with c0:25:06:f5:7f:06 (try 1/3)
[ 63.233156] wlp5s0: RX AssocResp from c0:25:06:f5:7f:06 (capab=0x1431
status=0 aid=6)
[ 63.233829] wlp5s0: associated
[ 63.274816] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready
[ 63.282018] wlp5s0: Limiting TX power to 20 (20 - 0) dBm as
advertised by c0:25:06:f5:7f:06
So sieht /var/log/syslog im Gutfall aus:
Sep 25 14:07:32 debtop systemd[1]: Started NVIDIA Persistence Daemon.
Sep 25 14:07:32 debtop NetworkManager[724]: <info> [1601035652.6091]
device (enp8s0): carrier: link connected
Sep 25 14:07:32 debtop kernel: [ 54.906213] r8169 0000:08:00.0 enp8s0:
Link is Up - 100Mbps/Full - flow control rx/tx
Sep 25 14:07:32 debtop kernel: [ 54.906222] IPv6:
ADDRCONF(NETDEV_CHANGE): enp8s0: link becomes ready
Sep 25 14:07:33 debtop ModemManager[714]: <info> Couldn't check support
for device
'/sys/devices/pci0000:00/0000:00:01.3/0000:01:00.2/0000:02:04.0/0000:05:00.0':
not supported by any plugin
Sep 25 14:07:33 debtop ModemManager[714]: <info> Couldn't check support
for device
'/sys/devices/pci0000:00/0000:00:01.3/0000:01:00.2/0000:02:07.0/0000:08:00.0':
not supported by any plugin
Sep 25 14:07:34 debtop wpa_supplicant[850]: wlp5s0:
CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=DE
Sep 25 14:07:34 debtop wpa_supplicant[850]: wlp5s0: SME: Trying to
authenticate with c0:25:06:f5:7f:07 (SSID='o..frosch5' freq=5500 MHz)
Sep 25 14:07:34 debtop kernel: [ 56.890732] wlp5s0: authenticate with
c0:25:06:f5:7f:07
Sep 25 14:07:34 debtop kernel: [ 56.892299] wlp5s0: send auth to
c0:25:06:f5:7f:07 (try 1/3)
Sep 25 14:07:34 debtop avahi-daemon[710]: Joining mDNS multicast group
on interface enp8s0.IPv6 with address fe80::7285:c2ff:fec5:98c9.
Sep 25 14:07:34 debtop avahi-daemon[710]: New relevant interface
enp8s0.IPv6 for mDNS.
Sep 25 14:07:34 debtop avahi-daemon[710]: Registering new address record
for fe80::7285:c2ff:fec5:98c9 on enp8s0.*.
Sep 25 14:07:34 debtop wpa_supplicant[850]: wlp5s0: Trying to associate
with c0:25:06:f5:7f:07 (SSID='o..frosch5' freq=5500 MHz)
Sep 25 14:07:34 debtop kernel: [ 56.934424] wlp5s0: authenticated
Sep 25 14:07:34 debtop kernel: [ 56.936050] wlp5s0: associate with
c0:25:06:f5:7f:07 (try 1/3)
Sep 25 14:07:34 debtop kernel: [ 56.939262] wlp5s0: RX AssocResp from
c0:25:06:f5:7f:07 (capab=0x1511 status=0 aid=4)
Sep 25 14:07:34 debtop wpa_supplicant[850]: wlp5s0: Associated with
c0:25:06:f5:7f:07
Sep 25 14:07:34 debtop wpa_supplicant[850]: wlp5s0:
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 25 14:07:34 debtop kernel: [ 56.941012] wlp5s0: associated
Sep 25 14:07:34 debtop kernel: [ 56.944388] wlp5s0: Limiting TX power
to 27 (30 - 3) dBm as advertised by c0:25:06:f5:7f:07
Sep 25 14:07:34 debtop systemd[1]: systemd-rfkill.service: Succeeded.
Sep 25 14:07:35 debtop kernel: [ 57.458653] iwlwifi 0000:05:00.0:
Unhandled alg: 0x707
Sep 25 14:07:37 debtop kernel: [ 59.402540] iwlwifi 0000:05:00.0:
Unhandled alg: 0x707
Sep 25 14:07:37 debtop dhclient[770]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 10
Sep 25 14:07:37 debtop sh[741]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 10
Sep 25 14:07:38 debtop dhclient[855]: DHCPDISCOVER on wlp5s0 to
255.255.255.255 port 67 interval 10
Sep 25 14:07:38 debtop sh[673]: DHCPDISCOVER on wlp5s0 to
255.255.255.255 port 67 interval 10
Sep 25 14:07:38 debtop kernel: [ 60.940800] iwlwifi 0000:05:00.0:
Unhandled alg: 0x707
Sep 25 14:07:38 debtop kernel: [ 60.940926] iwlwifi 0000:05:00.0:
Unhandled alg: 0x707
Sep 25 14:07:38 debtop kernel: [ 60.981783] wlp5s0: disassociated from
c0:25:06:f5:7f:07 (Reason: 2=PREV_AUTH_NOT_VALID)
Sep 25 14:07:38 debtop wpa_supplicant[850]: wlp5s0:
CTRL-EVENT-DISCONNECTED bssid=c0:25:06:f5:7f:07 reason=2
Sep 25 14:07:38 debtop wpa_supplicant[850]: wlp5s0: WPA: 4-Way Handshake
failed - pre-shared key may be incorrect
Sep 25 14:07:38 debtop wpa_supplicant[850]: wlp5s0:
CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="o..frosch5" auth_failures=1
duration=10 reason=WRONG_KEY
Sep 25 14:07:40 debtop wpa_supplicant[850]: wlp5s0: SME: Trying to
authenticate with c0:25:06:f5:7f:06 (SSID='o..frosch' freq=2412 MHz)
Sep 25 14:07:40 debtop kernel: [ 63.185289] wlp5s0: authenticate with
c0:25:06:f5:7f:06
Sep 25 14:07:40 debtop kernel: [ 63.188906] wlp5s0: send auth to
c0:25:06:f5:7f:06 (try 1/3)
Sep 25 14:07:40 debtop wpa_supplicant[850]: wlp5s0: Trying to associate
with c0:25:06:f5:7f:06 (SSID='o..frosch' freq=2412 MHz)
Sep 25 14:07:40 debtop kernel: [ 63.226707] wlp5s0: authenticated
Sep 25 14:07:40 debtop kernel: [ 63.228033] wlp5s0: associate with
c0:25:06:f5:7f:06 (try 1/3)
Sep 25 14:07:40 debtop wpa_supplicant[850]: wlp5s0: Associated with
c0:25:06:f5:7f:06
Sep 25 14:07:40 debtop wpa_supplicant[850]: wlp5s0:
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 25 14:07:40 debtop kernel: [ 63.233156] wlp5s0: RX AssocResp from
c0:25:06:f5:7f:06 (capab=0x1431 status=0 aid=6)
Sep 25 14:07:40 debtop kernel: [ 63.233829] wlp5s0: associated
Sep 25 14:07:40 debtop wpa_supplicant[850]: wlp5s0: WPA: Key negotiation
completed with c0:25:06:f5:7f:06 [PTK=CCMP GTK=CCMP]
Sep 25 14:07:40 debtop wpa_supplicant[850]: wlp5s0: CTRL-EVENT-CONNECTED
- Connection to c0:25:06:f5:7f:06 completed [id=0 id_str=]
Sep 25 14:07:40 debtop kernel: [ 63.274816] IPv6:
ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready
Sep 25 14:07:40 debtop kernel: [ 63.282018] wlp5s0: Limiting TX power
to 20 (20 - 0) dBm as advertised by c0:25:06:f5:7f:06
Sep 25 14:07:41 debtop systemd[1]: NetworkManager-dispatcher.service:
Succeeded.
So sieht /var/log/syslog im Fehlerfall aus (von wlp5s0 ist gar nicht die
Rede):
Sep 24 08:41:04 debtop systemd[1]: Started NVIDIA Persistence Daemon.
Sep 24 08:41:06 debtop ModemManager[772]: <info> Couldn't check support
for device
'/sys/devices/pci0000:00/0000:00:01.3/0000:01:00.2/0000:02:07.0/0000:08:00.0':
not supported by any plugin
Sep 24 08:41:06 debtop dhclient[758]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 7
Sep 24 08:41:06 debtop sh[726]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 7
Sep 24 08:41:07 debtop systemd[1]: systemd-rfkill.service: Succeeded.
Sep 24 08:41:13 debtop dhclient[758]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 11
Sep 24 08:41:13 debtop sh[726]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 11
Sep 24 08:41:14 debtop systemd[1]: NetworkManager-dispatcher.service:
Succeeded.
Sep 24 08:41:24 debtop dhclient[758]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 8
Sep 24 08:41:24 debtop sh[726]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 8
Sep 24 08:41:32 debtop dhclient[758]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 13
Sep 24 08:41:32 debtop sh[726]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 13
Sep 24 08:41:34 debtop systemd[1]: systemd-hostnamed.service: Succeeded.
Sep 24 08:41:45 debtop dhclient[758]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 19
Sep 24 08:41:45 debtop sh[726]: DHCPDISCOVER on enp8s0 to
255.255.255.255 port 67 interval 19
Sep 24 08:42:04 debtop dhclient[758]: No DHCPOFFERS received.
Sep 24 08:42:04 debtop sh[726]: No DHCPOFFERS received.
Sep 24 08:42:04 debtop sh[726]: No working leases in persistent database
- sleeping.
Sep 24 08:42:04 debtop dhclient[758]: No working leases in persistent
database - sleeping.
Sep 24 08:42:04 debtop sh[726]: enp8s0=enp8s0
Sep 24 08:42:04 debtop systemd[1]: networking.service: Main process
exited, code=exited, status=1/FAILURE
Als ich versucht habe manuell Dinge zu richten beschreibt /var/log
/syslog die Dinge so:
Sep 24 09:11:16 debtop wpa_supplicant[3642]: Could not read interface
wlp5s0 flags: No such device
Sep 24 09:11:16 debtop wpa_supplicant[3642]: nl80211: Driver does not
support authentication/association or connect commands
Sep 24 09:11:16 debtop wpa_supplicant[3642]: nl80211: deinit
ifname=wlp5s0 disabled_11b_rates=0
Sep 24 09:11:16 debtop wpa_supplicant[3642]: Could not read interface
wlp5s0 flags: No such device
Sep 24 09:11:16 debtop wpa_supplicant[3642]: rfkill: Cannot get wiphy
information
Sep 24 09:11:16 debtop wpa_supplicant[3642]: Could not read interface
wlp5s0 flags: No such device
Sep 24 09:11:16 debtop wpa_supplicant[3642]: WEXT: Could not set
interface 'wlp5s0' UP
Sep 24 09:11:16 debtop wpa_supplicant[3642]: wlp5s0: Failed to
initialize driver interface
Sep 24 09:11:29 debtop wpa_supplicant[3661]: Successfully initialized
wpa_supplicant
Sep 24 09:11:29 debtop wpa_supplicant[3661]: Could not read interface
wlp5s0 flags: No such device
Sep 24 09:11:29 debtop wpa_supplicant[3661]: nl80211: Driver does not
support authentication/association or connect commands
Sep 24 09:11:29 debtop wpa_supplicant[3661]: nl80211: deinit
ifname=wlp5s0 disabled_11b_rates=0
Sep 24 09:11:29 debtop wpa_supplicant[3661]: Could not read interface
wlp5s0 flags: No such device
Sep 24 09:11:29 debtop wpa_supplicant[3661]: rfkill: Cannot get wiphy
information
Sep 24 09:11:29 debtop wpa_supplicant[3661]: Could not read interface
wlp5s0 flags: No such device
Sep 24 09:11:29 debtop wpa_supplicant[3661]: WEXT: Could not set
interface 'wlp5s0' UP
Sep 24 09:11:29 debtop wpa_supplicant[3661]: wlp5s0: Failed to
initialize driver interface
Ich werde die Dinge beobachten und mir die guten und schlechten Logs mal
bei Seite legen, um sie ggf. wieder zur Hand zu haben.
Danke für die Ideen.
Viele Grüße
Kai
Reply to: