[SOLVED] Network Manager not working after battery pullout from ntb

Daybringer · 2019-08-31 10:12:56

Since this is my first question and I am really new to linux, I'm sorry for some inappropriate formatting, usage of terms and stuff like that.

Hello guys so my problem in it's simplicity is that NetworkManager is not working at all. I recall that this has happend after making encrypted Vault on my KDE and ticking the box: Disconnect networks in times of using vault. After some tinkering with the vault I have deleted it, but since then NM is not working. I think that NM might conflict with some dependency from netctl, but since I am using linux just for 1 month I am not able to solve this issue by myself.

IMPORTANT NOTE: I am using wifi-menu to be connected so it might produce some false info from my side

Now some usable info:
-1. Wi-Fi is working: I can connect with

sudo wifi-menu

to wifi or DHCP to ethernet cable

-Wi-Fi is not soft nor hard blocked

[daybringer@archpad ~]$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

-lspci -k controllers and drivers in my NTB

00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
        Subsystem: Lenovo 82579LM Gigabit Network Connection (Lewisville)
        Kernel driver in use: e1000e
        Kernel modules: e1000e
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34)
        Subsystem: Intel Corporation Centrino Advanced-N 6205 (802.11a/b/g/n)
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

-logs
No logs in faillog neither in lastlog and I can post journal if it would be helpful

-systemctl: NetworkManager.service is enabled and netctl is not in enabled

 [daybringer@archpad journal]$ systemctl list-unit-files --type=service | grep enabled
autovt@.service                            enabled        
dbus-fi.w1.wpa_supplicant1.service         enabled        
dbus-org.freedesktop.nm-dispatcher.service enabled        
display-manager.service                    enabled        
getty@.service                             enabled        
haveged.service                            enabled        
NetworkManager-dispatcher.service          enabled        
NetworkManager-wait-online.service         enabled        
NetworkManager.service                     enabled        
sddm.service                               enabled        
systemd-fsck-root.service                  enabled-runtime
systemd-remount-fs.service                 enabled-runtime
tlp-sleep.service                          enabled        
tlp.service                                enabled        
wpa_supplicant.service                     enabled

- Even after disabling i found some netctl in systemd

[daybringer@archpad ~]$ systemctl list-units |grep "netctl"
netctl@wlp3s0\x2dVanatovi_123.service                                                       loaded active     exited    Networking for netctl profile wlp3s0-Vanatovi_123                                
system-netctl.slice                                                                         loaded active     active    system-netctl.slice

- I can't use nmtui neither I see any wifi in nmcli connection

-If this might help

[daybringer@archpad ~]$ nmcli device show
GENERAL.DEVICE:                         enp0s25
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         54:EE:75:00:27:72
GENERAL.MTU:                            1500
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               off
IP4.GATEWAY:                            --
IP6.GATEWAY:                            --

GENERAL.DEVICE:                         lo
GENERAL.TYPE:                           loopback
GENERAL.HWADDR:                         00:00:00:00:00:00
GENERAL.MTU:                            65536
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
IP4.ADDRESS[1]:                         127.0.0.1/8
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         ::1/128
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = ::1/128, nh = ::, mt = 256

GENERAL.DEVICE:                         wlp3s0
GENERAL.TYPE:                           wifi
GENERAL.HWADDR:                         E0:9D:31:2F:90:44
GENERAL.MTU:                            1500
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
IP4.ADDRESS[1]:                         10.0.0.6/24
IP4.GATEWAY:                            10.0.0.138
IP4.ROUTE[1]:                           dst = 10.0.0.0/24, nh = 0.0.0.0, mt = 303
IP4.ROUTE[2]:                           dst = 0.0.0.0/0, nh = 10.0.0.138, mt = 303
IP6.ADDRESS[1]:                         2001:1ae9:1a7:5300:e29d:31ff:fe2f:9044/64
IP6.ADDRESS[2]:                         fe80::e29d:31ff:fe2f:9044/64
IP6.GATEWAY:                            fe80::1
IP6.ROUTE[1]:                           dst = 2001:1ae9:1a7:5300::/64, nh = ::, mt = 256
IP6.ROUTE[2]:                           dst = fe80::/64, nh = ::, mt = 256
IP6.ROUTE[3]:                           dst = ff00::/8, nh = ::, mt = 256, table=255
IP6.ROUTE[4]:                           dst = ::/0, nh = fe80::1, mt = 1024

In advance thanks for your help, bye.

Last edited by Daybringer (2019-09-02 16:55:48)

V1del · 2019-09-01 20:50:28

Disable wpa_supplicant.service it will be invoked on demand by networkmanager.

If that isn't sufficient post a complete

journalctl -b

after logging into the problematic plasma session (FWIW you might want to check for, and possibly delete/move away, a potential ~/.config/plasmavaultrc

Daybringer · 2019-09-02 14:18:16

In the first place, thank you for your reply. As you advised I have disabled the wpa_supplicant.service and removed the plasmavaultrc but it didn't help. After some thinking i realized that before setting up Vault, I had removed the battery out of my ntb. After some googling I found a tip to remove status file /var/lib/NetworkManager/NetworkManager.state to get NM working.

But I have some questions: should I rename the threads name to the real problem and mark as solved?; or straightaway remove it cause this problem is mentioned in troubleshooting with NM in arch wiki?

Bye

EDIT1: Here is the link to the problem and its entire solution under Network management disabled: https://wiki.archlinux.org/index.php/Ne … leshooting

Last edited by Daybringer (2019-09-02 16:58:52)

V1del · 2019-09-02 14:22:34

Well that sounds weird, however glad to hear, you can definitely rename and mark as [SOLVED] maybe add a reference to the section you've read for your solution.

Arch Linux

#1 2019-08-31 10:12:56

[SOLVED] Network Manager not working after battery pullout from ntb

#2 2019-09-01 20:50:28

Re: [SOLVED] Network Manager not working after battery pullout from ntb

#3 2019-09-02 14:18:16

Re: [SOLVED] Network Manager not working after battery pullout from ntb

#4 2019-09-02 14:22:34

Re: [SOLVED] Network Manager not working after battery pullout from ntb

Board footer