You are not logged in.
Hi.
I have a problem since months. When I open my laptop from standby mode, sometimes I can't find the wifi connection. I'm using "netctl-auto" to manage it. When it fails, journalctl contains this:
Dec 12 09:42:04 gerty dhcpcd[123932]: wlp0s12f0: removing interface
Dec 12 09:42:07 gerty dhcpcd[128804]: dhcpcd-9.3.2 starting
Dec 12 09:42:07 gerty dhcpcd[128807]: DUID 00:04:08:d3:a7:75:17:1d:2c:47:a7:f6:94:e0:f0:2b:24:ed
Dec 12 09:42:07 gerty dhcpcd[128807]: wlp0s12f0: connected to Access Point: Livebox-EE56
Dec 12 09:42:07 gerty dhcpcd[128807]: wlp0s12f0: IAID 74:5b:b7:24
Dec 12 09:42:08 gerty dhcpcd[128807]: wlp0s12f0: rebinding lease of 192.168.1.36
Dec 12 09:42:08 gerty dhcpcd[128807]: wlp0s12f0: probing address 192.168.1.36/24
Dec 12 09:42:13 gerty dhcpcd[128807]: wlp0s12f0: leased 192.168.1.36 for 86400 seconds
Dec 12 09:42:13 gerty dhcpcd[128807]: wlp0s12f0: adding route to 192.168.1.0/24
Dec 12 09:42:13 gerty dhcpcd[128807]: wlp0s12f0: adding default route via 192.168.1.1
Dec 13 09:49:47 gerty dhcpcd[171943]: sending signal TERM to pid 128806
Dec 13 09:49:47 gerty dhcpcd[171943]: waiting for pid 128806 to exit
Dec 13 09:49:47 gerty dhcpcd[128807]: received SIGTERM, stopping
Dec 13 09:49:47 gerty dhcpcd[128807]: wlp0s12f0: removing interface
Dec 13 09:49:50 gerty dhcpcd[172003]: dhcpcd-9.3.2 starting
Dec 13 09:49:50 gerty dhcpcd[172006]: DUID 00:04:08:d3:a7:75:17:1d:2c:47:a7:f6:94:e0:f0:2b:24:ed
Dec 13 09:49:50 gerty dhcpcd[172006]: wlp0s12f0: if_init: Cannot allocate memory
Dec 13 09:49:50 gerty dhcpcd[172006]: wlp0s12f0: interface not found
Dec 13 09:50:40 gerty dhcpcd[172124]: dhcpcd-9.3.2 starting
Dec 13 09:50:40 gerty dhcpcd[172127]: DUID 00:04:08:d3:a7:75:17:1d:2c:47:a7:f6:94:e0:f0:2b:24:ed
Dec 13 09:50:40 gerty dhcpcd[172127]: wlp0s12f0: connected to Access Point: Livebox-EE56
Dec 13 09:50:40 gerty dhcpcd[172127]: wlp0s12f0: IAID 74:5b:b7:24
Dec 13 09:50:41 gerty dhcpcd[172127]: wlp0s12f0: rebinding lease of 192.168.1.36
Dec 13 09:50:41 gerty dhcpcd[172127]: wlp0s12f0: probing address 192.168.1.36/24
Dec 13 09:50:46 gerty dhcpcd[172127]: wlp0s12f0: leased 192.168.1.36 for 86400 seconds
Dec 13 09:50:46 gerty dhcpcd[172127]: wlp0s12f0: adding route to 192.168.1.0/24
Dec 13 09:50:46 gerty dhcpcd[172127]: wlp0s12f0: adding default route via 192.168.1.1Reported error:
Dec 13 09:49:50 gerty dhcpcd[172006]: wlp0s12f0: if_init: Cannot allocate memory
Dec 13 09:49:50 gerty dhcpcd[172006]: wlp0s12f0: interface not foundI try to "sudo systemctl restart netctl-auto@wlp0s12f0.service" but most of the time it does not fix it. I have to restart computer.
The "dhcpcd" service is not enabled. My "/etc/dhcpcd.conf" file is as follow (default one I guess):
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel
# Inform the DHCP server of our hostname for DDNS.
#hostname
# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
duid
# Persist interface configuration when dhcpcd exits.
persistent
# vendorclassid is set to blank to avoid sending the default of
# dhcpcd-<version>:<os>:<machine>:<platform>
vendorclassid
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search
option classless_static_routes
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu
# Request a hostname from the network
option host_name
# Most distributions have NTP support.
#option ntp_servers
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate SLAAC address using the Hardware Address of the interface
#slaac hwaddr
# OR generate Stable Private IPv6 Addresses based from the DUID
slaac private
noipv4llDo you know what might be causing this problem and how to fix it please?
Last edited by Delgan (2020-12-13 20:30:46)
Offline
What is your wireless hardware and driver? Does reloading the kernel module make the interface work again?
And please use code tags for the journal entries rather than quote tags, it greatly aids readability.
Jin, Jîyan, Azadî
Offline
Thanks for your help @Head_on_a_Stick. I removed the quote tag from the initial message.
Here is the output of "iw dev":
phy#0
Interface wlp0s12f0
ifindex 3
wdev 0x1
addr fc:77:74:5b:b7:24
ssid Livebox-EE56
type managed
channel 48 (5240 MHz), width: 40 MHz, center1: 5230 MHz
txpower 22.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0Output of "lspci -vv -s 00:0c.0":
00:0c.0 Network controller: Intel Corporation Device 31dc (rev 03)
Subsystem: Intel Corporation Device 0034
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-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 44
Region 0: Memory at a1110000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
Kernel modules: iwlwifiI tried reloading "iwlwifi" throufh "modprobe" and indeed, it made the interface work again! At least, it's more convenient than rebooting.
Offline
You can add a script under /lib/systemd/system-sleep/ to reload the module automatically after waking, see systemd-sleep(8) for the implementation details.
Jin, Jîyan, Azadî
Offline