You are not logged in.
This problem has been going on for quite awhile. I spent a few minutes awhile ago searching for a possible solution, but couldn't locate anything that seemed worthwhile.
When waking up from suspend, Network Manager attempts to re-authenticate with my router. I click the Connect (?) button, but the existing password is not accepted. I then have to reboot to use WiFi again under my BL-Unstable instance. For a while, I was able to get around this by reconnecting via the Connect to Hidden Wi-Fi Network option in Network Manager, but that no longer works for some reason.
Last edited by KrunchTime (2017-03-24 06:55:47)
Offline
Have you tried restarting NetworkManager.service?
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
Does this bring your connection back up:
# systemctl restart network-manager.service
EDIT: Ninja'd...
Last edited by Head_on_a_Stick (2017-03-22 22:27:20)
Offline
@damo: No, I have not tried restarting the service. That may work, but then that begs the question, why should I have to?
@Stick: I'm currently in my Hydrogen instance. I'll boot back into my Unstable instance and give your suggestion a try.
Edit: OK, I've suspended twice and Network Manager has reconnected both times without issue. It will happen again, so I'll try restarting Network Manager when it does and report back.
Last edited by KrunchTime (2017-03-22 23:23:18)
Offline
When this happens, what does your ifconfig -a look like? Is your network stack operational at all? can you ping your own interfaces?
When you lose connection, maybe check to see what the output of
nmcli general status
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
^Never tried ifconfig -a. Never tried, nor do I know how, to ping my own interfaces. However, thanks for chiming in.
Last edited by KrunchTime (2017-03-22 23:46:13)
Offline
^Never tried ifconfig -a. Never tried, nor do I know how, to ping my own interfaces. However, thanks for chiming in.
Umm okay.. well try the command:
ip address
having to restart the net manager service shouldn't be needed obviously. perhaps a dhcp lease issue?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
having to restart the net manager service shouldn't be needed obviously. perhaps a dhcp lease issue?
I'm not so sure about that. I've read about suspend issues, such as Wi-Fi, under Linux and Network Manager is disconnected when I suspend my desktop or my laptop. When I resume, Network Manager attempts to reconnect, but sometimes unsuccessfully. When unsuccessful, I get a prompt to enter the authentication password.
Well, the issue happened again a few minutes ago. Restarting Network Manager worked using the command HoaS provided. Following is the info Horizon_Brave asked me to check (prior to restarting Network Manager):
Results of nmcli general status:
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
disconnected none enabled enabled enabled enabled
Results of ifconfig -a:
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether [redacted] txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 54670 bytes 24465570 (23.3 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 54670 bytes 24465570 (23.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp3s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether [redacted] txqueuelen 1000 (Ethernet)
RX packets 83119 bytes 95251499 (90.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 4995
TX packets 64274 bytes 7753836 (7.3 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 19
Thank you to damo, HoaS, and Horizon_Brave.
Offline
Can we see the output of this:
systemd-inhibit
We could try a script in /usr/lib/systemd/system-sleep/ to run that `restart` command but systemd-suspend.service(8) says that this is a hack and that the Inhibitor interface should be used instead.
TBH, this is all over my head a little bit so I may have to investigate some more...
Offline
Btw what wireless card/manufacturer do you have here? and what kernel?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
Can we see the output of this:
systemd-inhibit
Who: NetworkManager (UID 0/root, PID 659/NetworkManager)
What: sleep
Why: NetworkManager needs to turn off networks
Mode: delay
Who: ModemManager (UID 0/root, PID 664/ModemManager)
What: sleep
Why: ModemManager needs to reset devices
Mode: delay
2 inhibitors listed.
Btw what wireless card/manufacturer do you have here? and what kernel?
Wireless card: Broadcom Limited BCM4352 802.11ac Wireless Network Adapter
Kernel: 4.9.13-1 (linux-image-xxx pkg version)
Last edited by KrunchTime (2017-03-28 23:48:39)
Offline
Wireless card: Broadcom Limited BCM4352 802.11ac Wireless Network Adapter
Are you using the proprietary driver with that?
If so, try the open version instead, it will probably work better in respect of suspend behaviour.
This command will show the driver in use:
lspci -k | grep -A2 BCM4352
Offline
^ I don't know if I'm using the proprietary driver or the open driver. I do know that I had to install the package broadcom-sta-dkms to get wireless to work. Output of the command you suggested:
03:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03)
Subsystem: AzureWave Device 2123
Kernel driver in use: wl
Offline
Kernel driver in use: wl
That's the non-free driver and they tend to not integrate with the system as well as the open drivers.
You could try the non-proprietary version, that may fix your problem but outright performance may suffer.
The real problem here is the hardware choice — Broadcom's support for the F(L)OSS community is atrocious and their products should be avoided, IMO.
Offline
I think I'll stick with the non-free driver. This is the first real issue I've had since I bought the computer.
Yeah, I've read about Broadcom issues, but again, this is the first real issue I've had.
Offline