[Solved] Wifi module stopped working after reboot

Getting your soundcard to work, using Debian on non-i386 hardware, etc

[Solved] Wifi module stopped working after reboot

Postby gopiandcode » 2020-06-29 14:42

I'm running on a Lenevo Carbon X1 using Debian 4.19. Everything was running fine, but then suddenly after rebooting (not after any particular update), my wifi is no longer working:

Output of
Code: Select all
ip addr

Code: Select all
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
(no wlxxxx interfaces)

Unlike the other similar issues I have found online - this should not be an issue with the iwlwifi firmware, as I have already installed it before.

Output of
Code: Select all
uname -a

Code: Select all
Linux GOPTOP-SJGR4BSG 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux


Checking the output of dmesg (see attachment), no logs for iwl are found - so it seems like the firmware is not being loaded on boot. However, once the system has booted, I can run
Code: Select all
modprobe iwlwifi
to load the module with no errors, and after that running
Code: Select all
lsmod | grep iwl
returns:
Code: Select all
iwlwifi               249856  0
cfg80211              774144  1 iwlwifi

However, even after loading the module and restarting network-manager, I still can't use wifi.

Running
Code: Select all
lspci | grep Network -iA 18
returns:
Code: Select all
00:14.3 Network controller: Intel Corporation Wireless-AC 9560 [Jefferson Peak] (rev 10)
   Subsystem: Intel Corporation Wireless-AC 9560 [Jefferson Peak]
   Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
   Interrupt: pin A routed to IRQ 255
   Region 0: Memory at 404b10c000 (64-bit, non-prefetchable) [disabled] [size=16K]
   Capabilities: [c8] Power Management version 3
      Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
      Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
   Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
      Address: 0000000000000000  Data: 0000
   Capabilities: [40] Express (v2) Root Complex Integrated Endpoint, MSI 00
      DevCap:   MaxPayload 128 bytes, PhantFunc 0
         ExtTag- RBE-
      DevCtl:   Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
         RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+
         MaxPayload 128 bytes, MaxReadReq 128 bytes
      DevSta:   CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
      DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR+, OBFF Via WAKE#
      DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis-, LTR+, OBFF Disabled
   Capabilities: [80] MSI-X: Enable- Count=16 Masked-
      Vector table: BAR=0 offset=00002000
      PBA: BAR=0 offset=00003000
   Capabilities: [100 v0] #00
   Capabilities: [14c v1] Latency Tolerance Reporting
      Max snoop latency: 0ns
      Max no snoop latency: 0ns
   Capabilities: [164 v1] Vendor Specific Information: ID=0010 Rev=0 Len=014 <?>

So it seems the wireless card hardware is detected - although It lists the memory as being disabled for some reason.

Finally, in
Code: Select all
journalctl -xe
, there are some messages from the network-manager but I'm not sure if they're related:
Code: Select all
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.7625] monitoring ifupdown state file '/run/network/ifstate'.
Jun 29 15:35:27 GOPTOP-SJGR4BSG polkitd[900]: started daemon version 0.105 using authority implementation `local' version `0.105'
Jun 29 15:35:27 GOPTOP-SJGR4BSG dbus-daemon[855]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.7' (uid=0 pid=867 comm="/usr/sbin/NetworkManager --no-daemon ")
Jun 29 15:35:27 GOPTOP-SJGR4BSG dbus-daemon[855]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jun 29 15:35:27 GOPTOP-SJGR4BSG systemd[1]: Started Authorization Manager.
-- Subject: A start job for unit polkit.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit polkit.service has finished successfully.
--
--
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.9917] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.9917] ifupdown:       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.9918] ifupdown:       interface-parser: parsing file /etc/network/interfaces.d/setup
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.9919] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces.d/setup
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.9919] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.9924] ifupdown: guessed connection type (eth0) = 802-3-ethernet
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.9925] ifupdown: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.9930] ifupdown: management mode: unmanaged
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.9931] settings: Loaded settings plugin: SettingsPluginIfupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-settings-plugin-ifupdown.so")
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.9931] settings: Loaded settings plugin: NMSKeyfilePlugin (internal)
Jun 29 15:35:27 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441327.9953] keyfile: new connection /etc/NetworkManager/system-connections/Nokia 8110 4G.nmconnection (d33a237b-5be5-49d5-98af-43982d664148,"Nokia 8110 4G")
Jun 29 15:35:27 GOPTOP-SJGR4BSG kernel: alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
Jun 29 15:35:27 GOPTOP-SJGR4BSG kernel: media: Linux media interface: v0.10
Jun 29 15:35:27 GOPTOP-SJGR4BSG kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
--
Jun 29 15:35:28 GOPTOP-SJGR4BSG NetworkManager[867]: <warn>  [1593441328.2487] Error: failed to open /run/network/ifstate
Jun 29 15:35:28 GOPTOP-SJGR4BSG nm-dispatcher[929]: req:2 'connectivity-change': new request (2 scripts)
Jun 29 15:35:28 GOPTOP-SJGR4BSG nm-dispatcher[929]: req:2 'connectivity-change': start running ordered scripts...
Jun 29 15:35:28 GOPTOP-SJGR4BSG systemd[1]: Starting Bluetooth service...
-- Subject: A start job for unit bluetooth.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit bluetooth.service has begun execution.
--
-- The job identifier is 571.
--
Jun 29 15:35:29 GOPTOP-SJGR4BSG systemd[1]: Starting Raise network interfaces...
-- Subject: A start job for unit networking.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit networking.service has begun execution.
--
-- The job identifier is 88.
Jun 29 15:35:29 GOPTOP-SJGR4BSG NetworkManager[867]: <info>  [1593441329.3188] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 29 15:35:29 GOPTOP-SJGR4BSG dhclient[1057]: Internet Systems Consortium DHCP Client 4.4.1
Jun 29 15:35:29 GOPTOP-SJGR4BSG ifup[983]: Internet Systems Consortium DHCP Client 4.4.1
Jun 29 15:35:29 GOPTOP-SJGR4BSG ifup[983]: Copyright 2004-2018 Internet Systems Consortium.
Jun 29 15:35:29 GOPTOP-SJGR4BSG ifup[983]: All rights reserved.
Jun 29 15:35:29 GOPTOP-SJGR4BSG ifup[983]: For info, please visit https://www.isc.org/software/dhcp/
Jun 29 15:35:29 GOPTOP-SJGR4BSG dhclient[1057]: Copyright 2004-2018 Internet Systems Consortium.
Jun 29 15:35:29 GOPTOP-SJGR4BSG dhclient[1057]: All rights reserved.
--
Jun 29 15:35:29 GOPTOP-SJGR4BSG systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit networking.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Jun 29 15:35:29 GOPTOP-SJGR4BSG systemd[1]: networking.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit networking.service has entered the 'failed' state with result 'exit-code'.
Jun 29 15:35:29 GOPTOP-SJGR4BSG systemd[1]: Failed to start Raise network interfaces.
-- Subject: A start job for unit networking.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit networking.service has finished with a failure.
--
-- The job identifier is 88 and the job result is failed.
Jun 29 15:35:29 GOPTOP-SJGR4BSG systemd[1]: Reached target Network.
-- Subject: A start job for unit network.target has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit network.target has finished successfully.
--
-- The job identifier is 90.


I'm really not sure why it stopped working all of a sudden? Could someone help? Thank you.
Last edited by gopiandcode on 2020-06-29 16:08, edited 2 times in total.
gopiandcode
 
Posts: 2
Joined: 2020-06-29 14:10

Re: Wifi module stopped working after reboot

Postby LE_746F6D617A7A69 » 2020-06-29 15:30

Most of laptops are equipped with WiFi "killswitch" - on Lenovo it's Fn+F8 or just F8, depending on the BIOS configuration.
Have You tried to enable the WiFi using those keys?
Bill Gates: "(...) In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating system."
The_full_story and Nothing_have_changed
LE_746F6D617A7A69
 
Posts: 168
Joined: 2020-05-03 14:16

Re: Wifi module stopped working after reboot

Postby gopiandcode » 2020-06-29 16:07

This is quite embarrassing - it seems like that was in fact the issue, as after I pressed it during boot, my wifi now works. (That or maybe it was due to some kind of overheating disabling the wireless card? I left the laptop off for a while and now it is significantly cooler, so maybe that was a factor).

Oddly, after I've logged in, pressing Fn-F8 toggles the wireless at software level (the hardware is still enabled), so maybe my DM or WM is rebinding it.

Thanks - you really saved me.
I'll update the title.
gopiandcode
 
Posts: 2
Joined: 2020-06-29 14:10


Return to Hardware

Who is online

Users browsing this forum: No registered users and 8 guests

fashionable