Hi there, on both the current 20140820 snapshot and the previous one, both for Gnome and KDE, NetworkManager isn’t working, at least not for WiFI. My WiFI card is successfully detected and powered on, but I had to manually start the NetworkManager service. Even then, the Gnome and KDE interfaces to NetworkManager can’t seem to communicate with NetworkManager or establish a connection.
It is working fine for me with KDE – well, almost fine.
Maybe your system was setup to use “wicked” (the replacement for the older “ifup”). I suggest you go into Yast network settings, and see if you can switch it to NetworkManager.
As for the “almost fine” - I’m noticing on an installed system that when I boot the WiFi connection gets an IPv4 address and an IPv6 link-local address, but no IPv6 global address. If I disconnect, then reconnect, it gets the proper IPv6 addresses. I suspect a timing problem. The connection is defined to be a system connection (shared with other users). If I boot the live KDE media (on a USB, and with the same network settings), it does come up with the proper IPv6 addresses. But booting is slower from the live USB, which might be enough to take care of any timing problem.
Strange, I did check Yast network settings and I tried to switch it to NetworkManager. I also tried manually restarting NetworkManager with systemctl, but it doesn’t seem to make any difference. The KDE applet always says NetworkManager is not running.
yfi
installed factory on 24-Aug-2014 and also had difficulty getting NetworkManager working,
very similar to your case
if after booting the sound was correctly setup, NetworkManager also worked,
so assumed it was a timing problem with module loading,
it worked on only about every 6th reboot
setup wicked via yast and the network was rock solid, but ipv6 had to be enabled to access the internet via the modem
on three other installs NetworkManager is working
ok with,
Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too (32bit install)
Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver: r8169 (64bit install)
Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 (64bit install)
problem with,
Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller driver: r8169 (64bit install)
cheers
Here’s the bug report:
https://bugzilla.novell.com/show_bug.cgi?id=893650
Observation
Addendum to http://forums.opensuse.org/showthread.php/500494-Factory-20140820-NetworkManager-not-working?p=2661414#post2661414,
the first message after mount of root if wicked is enabled is
[DEPEND] Dependency failed for Network Manager Wait Online.
after booting with wicked enabled, NetworkManager works when selected via
-yast --Network Settings
then all is normal for switching the network on / off for the session
NetworkManager fails again on the next reboot
wicked has to be re-selected via -yast --Network Settings to enable network services again
again NetworkManager can only be re-enabled after a reboot with wicked enabled
Reproducible: Always
fwiw
recovery from no network connection via NetworkManager,
after updating from 13.1 to Factory, wicked working
from user 1, via -Yast --Network Setting, selected NetworkManager Services,
noticed in the Icon Tray NetworkManager, the only Icon showing was Flight Mode
and no Active connections available
and no network connection possible
chose logout and logged in as user 2 and found NetworkManager worked fine,
in the Icon Tray NetworkManager, only Icon
showing was Flight Mode and 2 Active Wired Connections were showing with the same name,
so deleted both and rebooted
on reboot into user 1, (no [DEPEND] message appeared during boot)
via -Yast --Network Setting, selected NetworkManager Services
and all worked fine
the Icon Tray NetworkManager now showed the Wireless icon,
so disconnected the wired connection and enabled Wireless, and Active connections
showed foreign interfaces and after about 10 seconds the wireless usb dongle
connection was shown to the router, after selection all work fine (no intervention necessary,
security setting from prior install still in memory)
re-checked with user 2 and network connections looked identical and were fine
something got crossed? but what?
hth someone
fwiw
after updating to openSUSE 20140901 (Harlequin) yesterday,
again lost NetworkManager function
zypper dup stated nothing to do
tried to switch to wicked but informed package iw missing
after installation neither wicked nor NetworkManager gave a reliable wireless connection
again deleted all connections in NetworkManager and also deleted all files in directory
/etc/NetworkManager/system-connections/
cold boot to find old connection to router still found by NetworkManager,
assumed from files in /var/
verified/corrected entries and again cold booted
NetworkManager connection good and reporting Signal Strength: 59%
ymmv
On Wed, 03 Sep 2014 21:06:01 GMT
keellambert <keellambert@no-mx.forums.opensuse.org> wrote:
> after updating to openSUSE 20140901 (Harlequin) yesterday,
> again lost NetworkManager function
> zypper dup stated nothing to do
>
> tried to switch to wicked but informed package iw missing
Odd that I have had no trouble with NM. One difference is that I use
YaST for updating instead of zypper. Another is that the message
regarding “iw” package only happens when I try to configure wireless
during setup; apparently it’s a known error though I haven’t confirmed
with bugzilla.
–
Graham P Davis, Bracknell, Berks.
openSUSE 13.1 (64-bit); KDE 4.14.0; AMD Phenom II X2 550 Processor;
Kernel: 3.11.10; Video: nVidia GeForce 210 (using nVidia driver);
Sound: ATI SBx00 Azalia (Intel HDA)
hi Cloddy,
thanks for the feedback
updates so far have all been via Yast,
Zypper dup has only been used for verification
wireless problems have only occured on one PC,
another PC and two laptops updated without any need of intervention
wrt iw, it was installed just to eliminate another possible line of testing,
as NerworkManager and wicked had worked before the update it did not seem
logical it should be needed now
the suspicion is a cold boot is needed if network parameters are changed
else the old parameters are still used from temperary files in /var/, which is
user dependent
cheers