wifi with yast ifup ok , networkmanager not

Hi all

Recently installed 13.1 64bit KDE on a new machine , due to long term support .
Because ifup gives slow boot with start job … ± 18 seconds
( i was searching for a solution , but found non )
Finally changed to networkmanager , find my ssid and setup a connection to my router ,
but wpa_supplicant refuse to start .

"

 Failed to open  wpa_supplicant.conf', error: No such file or directory

wpa_gui is empty ( nothing to select )
When i change to ifup , everything appears in wpa_gui .
When i want to save wpa_gui configuration , i show

"The configuration could not be saved.The update_config=1 configuration option
must be used for configuration saving to
be permitted.

Not much to read on the net about my 2 errors

T.I.A.
rudi

wpa_spplicant log

Successfully initialized wpa_supplicantSuccessfully initialized wpa_supplicantSuccessfully initialized wpa_supplicantSuccessfully initialized wpa_supplicantSuccessfully initialized wpa_supplicantdbus: wpas_dbus_bss_signal_prop_changed: Unknown Property value 7dbus: wpas_dbus_bss_signal_prop_changed: Unknown Property value 7dbus: wpas_dbus_bss_signal_prop_changed: Unknown Property value 7Successfully initialized wpa_supplicantdbus: wpas_dbus_bss_signal_prop_changed: Unknown Property value 7Successfully initialized wpa_supplicantSuccessfully initialized wpa_supplicantdbus: wpas_dbus_bss_signal_prop_changed: Unknown Property value 7
 

networkmanager log

2016-04-01T16:48:36.507772+02:00 server NetworkManager[5359]: <info> (wlp4s0): using nl80211 for WiFi device control
2016-04-01T16:48:36.508009+02:00 server NetworkManager[5359]: <info> (wlp4s0): driver supports Access Point (AP) mode
2016-04-01T16:48:36.508199+02:00 server NetworkManager[5359]: <info> (wlp4s0): new 802.11 WiFi device (driver: 'rt2800pci' ifindex: 4)
2016-04-01T16:48:36.508433+02:00 server NetworkManager[5359]: <info> (wlp4s0): exported as /org/freedesktop/NetworkManager/Devices/2
2016-04-01T16:48:36.508603+02:00 server NetworkManager[5359]: <info> (wlp4s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
2016-04-01T16:48:36.508727+02:00 server NetworkManager[5359]: <info> (wlp4s0): bringing up device.
2016-04-01T16:48:36.542618+02:00 server NetworkManager[5359]: <info> (wlp4s0): preparing device.
2016-04-01T16:48:36.542756+02:00 server NetworkManager[5359]: <info> (wlp4s0): deactivating device (reason 'managed') [2]
2016-04-01T16:48:36.543126+02:00 server NetworkManager[5359]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
2016-04-01T16:48:36.543338+02:00 server NetworkManager[5359]: <warn> /sys/devices/virtual/net/vmnet1: couldn't determine device driver; ignoring...
2016-04-01T16:48:36.543509+02:00 server NetworkManager[5359]: <warn> /sys/devices/virtual/net/vmnet8: couldn't determine device driver; ignoring...
2016-04-01T16:48:36.543872+02:00 server NetworkManager[5359]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
2016-04-01T16:48:36.544037+02:00 server NetworkManager[5359]: <warn> /sys/devices/virtual/net/vmnet1: couldn't determine device driver; ignoring...
2016-04-01T16:48:36.544166+02:00 server NetworkManager[5359]: <warn> /sys/devices/virtual/net/vmnet8: couldn't determine device driver; ignoring...
2016-04-01T16:48:36.546567+02:00 server NetworkManager[5359]: <warn> Couldn't get managed objects: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
2016-04-01T16:48:36.547601+02:00 server NetworkManager[5359]: <info> ModemManager available in the bus
2016-04-01T16:48:36.552500+02:00 server NetworkManager[5359]: <info> (wlp4s0) supports 4 scan SSIDs
2016-04-01T16:48:36.552735+02:00 server NetworkManager[5359]: <info> (wlp4s0): supplicant interface state: starting -> ready
2016-04-01T16:48:36.552942+02:00 server NetworkManager[5359]: <info> (wlp4s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
2016-04-01T16:48:36.553120+02:00 server NetworkManager[5359]: <warn> Trying to remove a non-existant call id. 
2016-04-01T16:48:36.553739+02:00 server NetworkManager[5359]: <info> (wlp4s0): supplicant interface state: ready -> disconnected
2016-04-01T16:48:36.553961+02:00 server NetworkManager[5359]: <info> (wlp4s0) supports 4 scan SSIDs
2016-04-01T16:48:37.664735+02:00 server NetworkManager[5359]: <info> (wlp4s0): supplicant interface state: disconnected -> inactive
2016-04-01T16:53:10.104485+02:00 server NetworkManager[5359]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
2016-04-01T16:53:10.135090+02:00 server NetworkManager[5359]: <warn> /sys/devices/virtual/net/vmnet1: couldn't determine device driver; ignoring...
2016-04-01T16:53:10.141293+02:00 server NetworkManager[5359]: <warn> /sys/devices/virtual/net/vmnet8: couldn't determine device driver; ignoring...
2016-04-01T16:53:11.327218+02:00 server NetworkManager[5359]: <info> caught signal 15, shutting down normally.
2016-04-01T16:53:11.327417+02:00 server NetworkManager[5359]: <info> (enp2s0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
2016-04-01T16:53:11.328188+02:00 server NetworkManager[5359]: <info> (enp2s0): cleaning up...
2016-04-01T16:53:11.328343+02:00 server NetworkManager[5359]: <info> (enp2s0): taking down device.
2016-04-01T16:53:11.332011+02:00 server NetworkManager[5359]: <info> (enp3s0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]

And the Installation is virtual?

Virtualbox, Vmware, KVM/Quemu etc?

No , not virtual . SSD Samsung

VirtualBox and Vmware_player installed .

I could not fix networkmanager and/or wpa , so , i went back to yast ifup .
Tried some re-installs with a few reboot and boot_time is now acceptable

systemd-analyze blame | head

5.849s network.service         
5.264s network@wlp4s0.service          
1.811s vmware.service          
1.544s plymouth-start.service           
296ms vboxdrv.service           
252ms SuSEfirewall2.service           
251ms postfix.service           
245ms dev-sda5.device           
160ms apparmor.service           
114ms SuSEfirewall2_init.service

Thread can be closed , thanks .

@bismarel
First, you should know that 13.1 LTS expires end of summer, so if your objective is to install an openSUSE version that will be supported a long time before needing to upgrade, you should choose LEAP over 13.1.

Your wpa_supplicant.conf error is odd, and should be something to investigate (if you don’t decide to change to LEAP immediately).
It should be installed and usable by default on all systems whether actually using wireless or not.

This is where your wpa_supplicant.conf files <should> be, found by using the search utility “locate”

# locate wpa_supplicant.conf/etc/dbus-1/system.d/wpa_supplicant.conf
/etc/wpa_supplicant/wpa_supplicant.conf
/usr/share/doc/packages/wpa_supplicant/wpa_supplicant.conf
/usr/share/man/man5/wpa_supplicant.conf.5.gz

TSU

13.1 , because it’s the next Evergreen .

# locate wpa_supplicant.conf
/etc/dbus-1/system.d/wpa_supplicant.conf
/etc/wpa_supplicant/wpa_supplicant.conf
/etc/wpa_supplicant/wpa_supplicant.conf.rpmsave
/etc/wpa_supplicant/wpa_supplicant.conf~
/usr/share/doc/packages/wpa_supplicant/wpa_supplicant.conf 
/usr/share/man/man5/wpa_supplicant.conf.5.gz
/usr/src/linux-3.12.53-40/Documentation/networking/mac80211_hwsim/wpa_supplicant.conf

it’s not that i don’t have a connection ,
it just intrigues me why wpa w’ont start with networkmanager .
while ifup was slowing down boot with a “start job is running for LSB”

thanks for your time
rudi

13.1 isn’t actually the “next” Evergreen, it’s the “soon to expire” Evergreen.
LEAP is the current “other” designated Evergreen which was recently launched and has a long time to run (as of today).

I’m not sure what your wpa_supplicant.conf issues are, but unless you’re connecting to an open hotspot (no password), it’s almost certain that even running Wicked will have to use wpa_supplicant functionality… For years now, it’s been the standard underlying functionality for connecting to WPA with no substitute.

IMO the main problem you’ll run into using Wicked for your wireless is that Wicked doesn’t remember multiple network connections, the moment you might connect to a different WiFi network, your previous connection’s settings will be lost and have to be re-created all over again when you return.

TSU

13.1 isn't actually the "next" Evergreen, it's the "soon to expire" Evergreen.
LEAP is the current "other" designated Evergreen which was recently launched and has a long time to run (as of today).

Aw , I guess i’m missing a few years of info on distro updates , lol
I was enjoying 13.1 so much on my old desktop and remember i had postponed the 13.2 upgrade .
Now i’'ll jump start my LEAP !

thanks .