wpa_supplicant at login issue

blackbirdsr71 · 02-05-2021, 06:13 AM

Hi to all,

I could not find on the internet a suitable information that helps me to solve the problem that i am explaining next.
First of all i use artixlinux-runit and dwm as window manager. Every time i start my laptop and after i'm prompted to login i see the following:

Code:

artix login: Successfully initialized wpa_supplicant
nl80211: send_and_recv->nl_recvmsgs failed: -33
nl80211: send_and_recv->nl_recvmsgs failed: -33
wlp2s0: SME: Trying to authenticate with...
.
.
.
bgscan simple: Failed to enable signal strenght monitoring

After that, when it connects i am able to login after hiting enter as usual

Code:

artix login:

I am using networkmanager.
The laptop boots because networkmanager conects to my wifi, but if not it spawns

Code:

artix login: Successfully initialized wpa_supplicant
nl80211: send_and_recv->nl_recvmsgs failed: -33
nl80211: send_and_recv->nl_recvmsgs failed: -33
nl80211: send_and_recv->nl_recvmsgs failed: -33
nl80211: send_and_recv->nl_recvmsgs failed: -33
nl80211: send_and_recv->nl_recvmsgs failed: -33
nl80211: send_and_recv->nl_recvmsgs failed: -33
.
.
.

indefinitly.
This a real problem because suppose that i am travelling i would not be able to login due to networkmanager being unable to connect to a new wifi network.

Can someone help me with this issue, in order to login properly and that the networkmanager starts after i log in?

Thanks!

Emerson · 02-05-2021, 11:21 AM

OK, I'm stabbing totally in dark and can only tell from my Gentoo experience. In Gentoo we can have similar trouble when wpa_supplicant is started by init system and then NetworkManager is started and attempts to start wpa_supplicant in its own, causing a conflict. So my advice is to double-check your init scripts, perhaps wpa_supplicant is started from there and it shouldn't.

blackbirdsr71 · 02-13-2021, 04:02 PM

Quote:

Originally Posted by Emerson

... So my advice is to double-check your init scripts, perhaps wpa_supplicant is started from there and it shouldn't.

Thanks for your kind answer, Emerson, i am not so experienced in order to double check init scripts, i am afraid to make a big mistake, is any guide to do that?

Brains · 02-13-2021, 09:02 PM

Quote:

Originally Posted by blackbirdsr71

Every time i start my laptop and after i'm prompted to login i see the following:

The behaviour you describe is more consistent with bringing up the laptop out of Suspend or Hibernation rather than booting it up after it was properly shutdown. If this is the case, might be a good idea to review power management settings regarding the handling of wireless networks in these modes.

u666sa · 02-14-2021, 03:08 AM

Quote:

Originally Posted by blackbirdsr71

Can someone help me with this issue, in order to login properly and that the networkmanager starts after i log in?

Do you have iwd installed? If so -

systemctl stop iwd.service
systemctl disable iwd.service
sudo pacman -R iwd (or whatever you use there to uninstall)

Then reboot see if it works.

Suck suggestion because I just had problems with NetworkManager and iwd on Arch -- network simply would not connect, only removing iwd solved my issues.

blackbirdsr71 · 02-19-2021, 07:38 AM

Quote:

Originally Posted by Brains

The behaviour you describe is more consistent with bringing up the laptop out of Suspend or Hibernation rather than booting it up after it was properly shutdown. If this is the case, might be a good idea to review power management settings regarding the handling of wireless networks in these modes.

Thanks for your answer. Indeed this happens since the beginings of time i installed Artix. Installing iwd solved partally the issue but not the hanging i describe above. I will check your suggestion.

blackbirdsr71 · 02-19-2021, 07:43 AM

Quote:

Originally Posted by u666sa

Do you have iwd installed? If so -

systemctl stop iwd.service
systemctl disable iwd.service
sudo pacman -R iwd (or whatever you use there to uninstall)

Then reboot see if it works.

Suck suggestion because I just had problems with NetworkManager and iwd on Arch -- network simply would not connect, only removing iwd solved my issues.

Thanks for the answer u666sa, indeed iwd helped to avoid the fact that if there is no known network i could not login at all. The thing is that it is very anoying that login stops untill i hit enter and then i may login properly.

Brains · 02-19-2021, 05:52 PM

Something I mentioned in another thread recently, can't find it so might of been another forum. I noticed when you click the X in the upper right of the GUI to close it, it don't actually close it gets minimized to the tray. Qbittorent used to do that to me where it's always running in the background eating up my bandwidth seeding because it's never closed and always resumes after reboot.
If you right click the little antenna in the top left of the wpa-sup GUI and select close it will again be minimized to the tray.
If you select File/close or quit I forget, now it will actually be closed and not minimized to tray.
If you right click on it's icon in the tray which looks like the wireless icon and select quit, it will close. When properly closed it don't come up after reboot.

calliealbert · 03-03-2021, 02:06 AM

Can you run wpa-passphrase "essid" "password" > ~/wpa_new.conf and see if that works with wpa_supplicant.