New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sys-net NetworkManager wpa_supplicant #1646

Closed
kestassf opened this Issue Jan 16, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@kestassf

Fresh install of QubesOS 3.1 RC2 doesn't show wifi networks to connect to on network icon (seams to be related to NetworkManager, because iwlist scan works as expected). Wired LAN works ok.
Hardware: Dell Inspiron 17R-5721

On sys-net VM:

# lspci 
00:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 05)
00:01.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)

Starting wpa_supplicant manually (from root) on sys-net fixed the problem for me:

wpa_supplicant -u -B
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 17, 2016

Member

Check journalctl -b -u NetworkManager.service for any errors.

Member

marmarek commented Jan 17, 2016

Check journalctl -b -u NetworkManager.service for any errors.

@kestassf

This comment has been minimized.

Show comment
Hide comment
@kestassf

kestassf Jan 17, 2016

I've attached command's output (I don't see any errors here):
journal.txt
I also checked for for "wpa_supplicant" process, but there is none running (until I start it by hand).

I've attached command's output (I don't see any errors here):
journal.txt
I also checked for for "wpa_supplicant" process, but there is none running (until I start it by hand).

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Apr 6, 2016

Member

I'm assuming this issue has been resolved based on the lack of recent activity. If not, please feel free to re-open it.

Member

andrewdavidwong commented Apr 6, 2016

I'm assuming this issue has been resolved based on the lack of recent activity. If not, please feel free to re-open it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment