Hi again.
Problem solved! Just over-installed Q4OS.
purged dhcpcd5 package and all seems OK! Network manager shows available WiFi networks, connects to them fine & connections seem to live thru reboots!
Good job, thanks
]]>Have fun!
]]>Right-Click on tray icon shows Networking & Wi-Fi everything enabled (checked).
Left-Click on tray icon shows Wi-Fi Networks "device not ready"
--------------------
I created a fresh q4os sd (from q4os-2.6-rpi.r4 on website) just to make sure I didn't have any of my fumbling network tweaks in the way. Currently running on rpi 3 (builtin wifi). Happy to test or provide diagnostics on this config if you need it
Thank you
]]>I really appreciate your help. I appologize not to be more useful.
Thank you very much
]]>GUI TDE NetworkManager just seems disconnected from WiFi world. Similar symptoms to tonanis report ... no list of ssid to connect to. I can manually set up a connection, but still unable to manually connect to saved networks via NetworkManager
I've fiddled and have WiFi working on my machines but have not managed to get NetworkManager to function
I'm somewhat of a hack, but here are things I've tried (right or wrong ...)
- Setting up wifi using raspi-config (user pi from console). It works, but did not reconnect wifi after a reboot
- Modified /etc/NetworkManager/NetworkManager.conf - changed managed=false to managed=true. Still no luck
- Finally edited /etc/network/interfaces in an attempt to bring network interfaces up after a boot. NetworkManager still doesn't work, but Wifi reconnects after boots. This works for me. Added the following lines:
# Attempt to bring network interfaces up after boot
auto lo
iface lo inet loopback
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
auto wlan0
allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
Hope it helps. Happy to send diagnostics or additional info if needed
]]>We have checked the "qreport.tar.gz" file sent via e-mail, the initialization of wireless device looks good. The issue could be connected to some user permissions restriction. Please try to login as the first user "pi", try to make a wireless connection and report back the result.
]]>