New NetworkManager fail

GoinEasy9 · #1 18th August 2010, 04:57 AM

A new NetworkManager came in tonight. Even though it's set to auto, and services show it as enabled, it has to be started after each boot.
NetworkManager-0.8.1-4.git20100817.fc14.i686
Messages shows:
Aug 17 23:33:24 fedora14dw32 init[1]: Failed to load configuration for NetworkManager-by-dbus.service: No such file or directory
Aug 17 23:33:24 fedora14dw32 init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument
Aug 17 23:33:24 fedora14dw32 kernel: init[1]: Failed to load configuration for NetworkManager-by-dbus.service: No such file or directory
Aug 17 23:33:24 fedora14dw32 kernel: init[1]: D-Bus activation failed for NetworkManager-by-dbus.service: Invalid argument

I'm wondering if NetworkManager is the offending party.

R3353 · #2 18th August 2010, 05:37 AM

does wicd work? It'd be nice if there were a more established gui alternative bundled into the official releases. I've found wicd works better for everyday home and office use, while nm is better for roaming and connecting to random networks when need be.

#3 18th August 2010, 05:41 AM

Quote:

Originally Posted by R3353

does wicd work? It'd be nice if there were a more established gui alternative bundled into the official releases. I've found wicd works better for everyday home and office use, while nm is better for roaming and connecting to random networks when need be.

you should still be able to use Redhats old network utility an disable NM which is probably more stable than anything else out there

i think its called system-config-network

GoinEasy9 · #4 18th August 2010, 05:55 AM

I'm really not complaining about NetworkManager, in fact, in F13, my laptops can seamlessly go from eth0 to wifi to broadband tethering. The reason I posted is to see if there are any others who are having the same problems with F14 Alpha and the recent update. Why? Because I don't know if the Bugzilla should be filed with NetworkManager, dbus or the dbus.service set up by systemd.

andrewthomas · #5 18th August 2010, 06:50 PM

Code:

# /etc/rc.d/init.d/NetworkManager restart

will restore connectivity

https://bugzilla.redhat.com/show_bug.cgi?id=624773

GoinEasy9 · #6 18th August 2010, 06:56 PM

@andrewthomas
Yes, that's what I've been doing, or service NetworkManager restart, or System-->Administration-->Services and hitting start (the restart icon is grayed out).
Thanks for the bugzilla link.

ovadyah · #7 19th August 2010, 02:15 AM

I tried the "# /etc/rc.d/init.d/NetworkManager restart" and the applet came back but had greyed out "disconnected" and I could not connect to my wireless network. Is there another step I am missing?
thanks.

GoinEasy9 · #8 19th August 2010, 02:39 AM

I've only played with the wired network. You could try "ifup wlan0". I can't test, I only have F14 running on desktops at the moment.

---------- Post added at 09:39 PM CDT ---------- Previous post was at 09:36 PM CDT ----------

Also, make sure the auto connect is checked in NetworkManager

ovadyah · #9 19th August 2010, 02:40 AM

Thanks, if has been so long since I had network issues I had forgotten about that. I am gioing to see if I can find a long patch cable, I use wireless on my desktop to avoid a cable going from one end to the other of my RV.
Thanks again, I shall report in the morning.

dd_wizard · #10 19th August 2010, 02:53 AM

NetworkManager-0.8.1-5.git20100818.fc14.x86_64.rpm in koji works, but it's not even in bodhi yet or I'd give it +1 karma. Do a "yum list installed NetworkManager*" to see which packages you need. I needed NetworkManager-glib and NetworkManager-gnome as well.

dd_wizard

GoinEasy9 · #11 19th August 2010, 04:22 AM

I just saw on the devel list another work around, supposedly. I won't be able to check till tomorrow.
"systemctl enable NetworkManager.service" and "systemctl start NetworkManager.service"

chepioq · #12 19th August 2010, 02:21 PM

I confirm that NetworkManager-0.8.1-5.git20100818.fc14 from koji solve problem...

andrewthomas · #13 19th August 2010, 03:57 PM

Quote:

Originally Posted by GoinEasy9

I just saw on the devel list another work around, supposedly. I won't be able to check till tomorrow.
"systemctl enable NetworkManager.service" and "systemctl start NetworkManager.service"

The workaround does indeed work.

ovadyah · #14 19th August 2010, 04:48 PM

The workaround does put the applet up in the panel, however for me it does nothing to help connect. I can see my wireless network but it will not connect.
I got out the 30 foot cat5 and now have network, may be something with only wireless?

Tonights updates fixed the NM and wireless! Way to go TEAM!
Thanks

GoinEasy9 · #15 20th August 2010, 04:33 AM

After update, I've got reboot and shutdown working again, but, NM isn't starting eth0 automatically. I may have to bring in that newer version from koji.
@ovadyah what version of NM do you have installed?

---------- Post added at 11:33 PM CDT ---------- Previous post was at 10:46 PM CDT ----------

OK, with the NetworkManager packages from koji, I'm now getting automatic network connections.
I installed/updated:
NetworkManager-gnome-0.8.1-5.git20100818.fc14.i686.rpm
NetworkManager-glib-0.8.1-5.git20100818.fc14.i686.rpm
NetworkManager-0.8.1-5.git20100818.fc14.i686.rpm

I've just started testing and everything so far seems to be working, except for my blank AVC Alert when I first log in.