Hi!I was running OpenSUSE 13.2 32 bit and have just upgraded to Tumbleweed 32 bit on my laptop.Wifi was running perfectly on 13.2 with no disconnects but periodically disconnects on Tumbleweed getting disabled and showing a question mark on the wifi icon.I have to turn wifi off and on again to resume connection.
Kindly assist in resolving this.
This could well be a wifi power management issue.
Just in case the following helpful to you…
https://forums.opensuse.org/showthread.php/527757-Regular-intermittent-loss-of-communication-over-WiFi?p=2842471#post2842471
Also, please provide your wireless hardware details…
/usr/sbin/hwinfo --wlan
Here are my hardware details.Note that wifi was operating perfectly on OpenSUSE 13.2 but disconnects on Tumbleweed so I dont think its a hardware issue
/usr/sbin/hwinfo --wlan
18: PCI 200.0: 0282 WLAN controller
[Created at pci.378]
Unique ID: S6TQ.LijBSGb8FsA
Parent ID: z8Q3.Cj2ByQjL_A7
SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:02:00.0
SysFS BusID: 0000:02:00.0
Hardware Class: network
Device Name: “Intel(R) Centrino(R) Advanced-N 6300 AGN”
Model: “Realtek RTL8191SEvA Wireless LAN Controller”
Vendor: pci 0x10ec “Realtek Semiconductor Co., Ltd.”
Device: pci 0x8171 “RTL8191SEvA Wireless LAN Controller”
SubVendor: pci 0x103c “Hewlett-Packard Company”
SubDevice: pci 0x1467
Revision: 0x10
Driver: “rtl8192se”
Driver Modules: “rtl8192se”
Device File: wlo1
Features: WLAN
I/O Ports: 0x3000-0x30ff (rw)
Memory Range: 0xd3500000-0xd3503fff (rw,non-prefetchable)
IRQ: 16 (no events)
HW Address: 70:f1:a1:8d:54:ea
Permanent HW Address: 70:f1:a1:8d:54:ea
Link detected: yes
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias: “pci:v000010ECd00008171sv0000103Csd00001467bc02sc80i00”
Driver Info #0:
Driver Status: rtl8192se is active
Driver Activation Cmd: “modprobe rtl8192se”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #14 (PCI bridge)
After reading the link that you posted above,I have confirmed that tlp was already installed on my Tumbleweed.I have also executed the 2 commands below
WIFI_PWR_ON_AC=off
WIFI_PWR_ON_BAT=off
They’re not commands that get executed - they’re configuration options that get added /etc/default/tlp
Note also that the guide I linked to previously mentioned that changes to the settings take effect after a reboot, a change of the power source, or directly by restarting tlp.
/usr/sbin/iwconfig
sudo journalctl -fu NetworkManager
When the connection drops you should be able to capture the relevant event in the output. This might help with debugging.
[logging]
level=DEBUG
Note that any changes to this configuration will take effect at next boot or restart of NetworkManager…
sudo systemctl restart NetworkManager
I have run the command below and confirmed power management is off
/usr/sbin/iwconfig
I have added the debug entry below in my /etc/NetworkManager/NetworkManager.conf file.I assume there will be a debug logfile produced.In which directory path can I find this file?I was hoping to get the file /var/log/NetworkManager but didnt find it.Can I also check the file /var/log/wpa_supplicant?
[logging]
level=DEBUG
The logging is done by the systemd-journald service these days. You use the journalctl command to view the journal logging. I’ve already shown you how to watch the NetworkManager logging live, but other options are available and there are various ways to filter for the required output.
Some useful references…
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.journalctl.html
https://wiki.archlinux.org/index.php/Systemd#Journalhttps://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs
Kindly find the output of sudo journalctl -fu NetworkManager when the wifi connection diconnected
Nov 25 08:26:51 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587611.4830] device[0xec2380] (wlo1): wifi-scan: scanning-state: scanning
Nov 25 08:26:55 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587615.0853] device[0xec2380] (wlo1): wifi-scan: scan-done callback: successful
Nov 25 08:26:55 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587615.0862] device[0xec2380] (wlo1): remove_pending_action (0): 'wifi-scan'
Nov 25 08:26:55 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587615.0929] device[0xec2380] (wlo1): wifi-scan: scanning-state: idle
Nov 25 08:28:51 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587731.4728] device[0xec2380] (wlo1): wifi-scan: scanning requested
Nov 25 08:28:51 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587731.4729] device[0xec2380] (wlo1): wifi-scan: no SSIDs to probe scan
Nov 25 08:28:51 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587731.4731] device[0xec2380] (wlo1): add_pending_action (1): 'wifi-scan'
Nov 25 08:28:51 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587731.4732] device[0xec2380] (wlo1): wifi-scan: scheduled in 120 seconds (interval now 120 seconds)
Nov 25 08:28:51 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587731.4801] device[0xec2380] (wlo1): wifi-scan: scanning-state: scanning
Nov 25 08:28:55 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587735.0473] device[0xec2380] (wlo1): wifi-scan: scan-done callback: successful
Nov 25 08:28:55 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587735.0473] device[0xec2380] (wlo1): remove_pending_action (0): 'wifi-scan'
Nov 25 08:28:55 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587735.0681] device[0xec2380] (wlo1): wifi-scan: scanning-state: idle
Nov 25 08:29:19 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587759.4760] connectivity: (wlo1) sending request to 'http://conncheck.opensuse.org'
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <info> [1511587789.4724] connectivity: (wlo1) timed out
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4725] device[0xec2380] (wlo1): state changed from FULL to LIMITED
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4725] manager: connectivity checking indicates LIMITED
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4726] dispatcher: (7) dispatching action 'connectivity-change'
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4731] device[0xec2380] (wlo1): ip4-config: update (commit=1, routes-full-sync=0, new-config=0xeb9dc8)
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4732] platform: address: adding or updating IPv4 address: 192.168.0.14/24 lft 1797sec pref 1797sec lifetime 3632-0[1797,1797] dev 3 src unknown
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4734] platform: signal: address 4 changed: 192.168.0.14/24 lft 1797sec pref 1797sec lifetime 3632-3632[1797,1797] dev 3 src kernel
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4734] default-route: resync: schedule on idle
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4735] device[0xec2380] (wlo1): queued IP4 config change
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4735] platform-linux: do-add-ip4-address[3: 192.168.0.14/24]: success
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4736] route-mgr4: 3: sync 1 IPv4 routes
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4736] platform: route: adding or updating IPv4 route: 192.168.0.0/24 via 0.0.0.0 dev 3 metric 600 mss 0 rt-src kernel pref-src 192.168.0.14
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4737] platform-linux: do-add-ip4-route[3: 192.168.0.0/24 600]: success
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4738] default-route: entry[0/dev:0xec2380:wlo1:+has:+sync]: record:update 0.0.0.0/0 via 192.168.0.1 dev 3 metric 20600 mss 0 rt-src user (600)
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4738] default-route: resync: cancelled (2994)
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4739] default-route: entry[0/dev:0xec2380:wlo1:+has:+sync]: sync:update 0.0.0.0/0 via 192.168.0.1 dev 3 metric 20600 mss 0 rt-src user (600 -> 20600)
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4739] platform: route: adding or updating IPv4 route: 0.0.0.0/0 via 192.168.0.1 dev 3 metric 20600 mss 0 rt-src user
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4740] platform: signal: route 4 added: 0.0.0.0/0 via 192.168.0.1 dev 3 metric 20600 mss 0 rt-src rt-static scope global
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4741] platform-linux: do-add-ip4-route[3: 0.0.0.0/0 20600]: success
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4741] platform: route: deleting IPv4 route 0.0.0.0/0, metric=600, ifindex 3 dev wlo1
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4742] platform: signal: route 4 removed: 0.0.0.0/0 via 192.168.0.1 dev 3 metric 600 mss 0 rt-src rt-static scope global
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4743] platform-linux: do-delete-ip4-route[3: 0.0.0.0/0 600]: success
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4743] device[0xec2380] (wlo1): ip4-config: default route changed
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4744] dns-mgr: (device_ip4_config_changed): queueing DNS updates (1)
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4744] dns-mgr: (device_ip4_config_changed): DNS configuration did not change
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4744] dns-mgr: (device_ip4_config_changed): no DNS changes to commit (0)
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4869] device[0xec2380] (wlo1): ip4-config: update (commit=0, routes-full-sync=0, new-config=0xeb99d8)
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4869] default-route: entry[0/dev:0xec2380:wlo1:+has:-sync]: record:update 0.0.0.0/0 via 192.168.0.1 dev 3 metric 20600 mss 0 rt-src rt-static scope global (20600)
Nov 25 08:29:51 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587791.2099] dispatcher: (7) 99tlp-rdw-nm succeeded
Nov 25 08:29:51 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587791.2099] dispatcher: (7) autofs succeeded
Nov 25 08:29:51 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587791.2100] dispatcher: (7) nfs succeeded
Nov 25 08:29:51 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587791.2100] dispatcher: (7) ntp succeeded
This caught my attention…
Nov 25 08:29:19 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587759.4760] connectivity: (wlo1) sending request to 'http://conncheck.opensuse.org'
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <info> [1511587789.4724] connectivity: (wlo1) timed out
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4725] device[0xec2380] (wlo1): state changed from FULL to LIMITED
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4725] manager: connectivity checking indicates LIMITED
Nov 25 08:29:49 TUMBLEWEED.site NetworkManager[1251]: <debug> [1511587789.4726] dispatcher: (7) dispatching action 'connectivity-change'
However, I don’t know the underlying cause, and the wifi connection itself does not appear to drop, at least for the logging period that you have captured and shared here. Some more analysis is necessary.
Is this connection to a single private access point? Or a public/shared wifi network with multiple APs?
What does the signal level (and other AP properties look like)?
sudo /usr/sbin/iw dev wlo1 scan
We can also examine the kernel output live and capture the relevant output for when the connection state changes…
dmesg --follow