| View previous topic :: View next topic |
| Author |
Message |
jamesshuang Tux's lil' helper


Joined: 08 Aug 2002 Posts: 120
|
Posted: Mon Jul 25, 2005 3:08 am Post subject: |
|
|
Ok, so I tried the new ebuilds, and it doesn't help. Here's a completely log again:
| Code: |
Jul 24 22:51:24 alexa NetworkManager: <information> starting...
Jul 24 22:51:24 alexa NetworkManager: <information> eth0: Driver support level for 'ipw2200' is fully-supported
Jul 24 22:51:24 alexa NetworkManager: <WARNING> (): data good :-)
Jul 24 22:51:24 alexa NetworkManager: <information> nm_device_new(): waiting for device's worker thread to start
Jul 24 22:51:24 alexa NetworkManager: <information> nm_device_new(): device's worker thread started, continuing.
Jul 24 22:51:24 alexa NetworkManager: <information> Now managing wireless device 'eth0'.
Jul 24 22:51:24 alexa NetworkManager: <information> Deactivating device eth0.
Jul 24 22:51:26 alexa NetworkManager: <information> eth1: Driver support level for 'b44' is fully-supported
Jul 24 22:51:26 alexa NetworkManager: <information> nm_device_new(): waiting for device's worker thread to start
Jul 24 22:51:27 alexa NetworkManager: <information> nm_device_new(): device's worker thread started, continuing.
Jul 24 22:51:27 alexa NetworkManager: <information> Now managing wired device 'eth1'.
Jul 24 22:51:27 alexa NetworkManager: <information> Deactivating device eth1.
Jul 24 22:51:27 alexa rc-scripts: WARNING: "net.lo" has already been started.
Jul 24 22:51:38 alexa NetworkManager: <information> Updating allowed wireless network lists.
Jul 24 22:51:38 alexa NetworkManager: <information> SWITCH: no current connection, found better connection 'eth0'.
Jul 24 22:51:38 alexa dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jul 24 22:51:38 alexa NetworkManager: <information> Will activate connection 'eth0/linksys'.
Jul 24 22:51:38 alexa NetworkManager: <information> Device eth0 activation scheduled...
Jul 24 22:51:38 alexa NetworkManager: <information> Activation (eth0) started...
Jul 24 22:51:38 alexa NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) scheduled...
Jul 24 22:51:38 alexa NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) started...
Jul 24 22:51:38 alexa NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) scheduled...
Jul 24 22:51:38 alexa NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) complete.
Jul 24 22:51:38 alexa NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) starting...
Jul 24 22:51:38 alexa NetworkManager: <information> Old device 'eth0' activating, won't change.
Jul 24 22:51:38 alexa NetworkManager: <information> Activation (eth0/wireless) Stage 1 (Device Configure) will connect to access point 'linksys'.
Jul 24 22:51:38 alexa NetworkManager: <information> Activation (eth0/wireless): access point 'linksys' is unencrypted, no key needed.
Jul 24 22:51:40 alexa NetworkManager: <information> Activation (eth0/wireless): using essid 'linksys', with no authentication.
Jul 24 22:51:41 alexa NetworkManager: <information> Activation (eth0/wireless) Stage 2 (Device Configure) successful. Connected to access point 'linksys'.
Jul 24 22:51:41 alexa NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) scheduled.
Jul 24 22:51:41 alexa NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) complete.
Jul 24 22:51:41 alexa NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) started...
Jul 24 22:51:42 alexa NetworkManager: <information> Activation (eth0) Beginning DHCP transaction.
Jul 24 22:51:42 alexa NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) complete.
Jul 24 22:51:42 alexa dhcdbd: Unrequested down ?:3
Jul 24 22:51:42 alexa dhclient: Internet Systems Consortium DHCP Client V3.0.2
Jul 24 22:51:42 alexa dhclient: Copyright 2004 Internet Systems Consortium.
Jul 24 22:51:42 alexa dhclient: All rights reserved.
Jul 24 22:51:42 alexa dhclient: For info, please visit http://www.isc.org/products/DHCP
Jul 24 22:51:42 alexa dhclient: Usage: dhclient [-1dqr] [-nw] [-p <port>] [-s server]
Jul 24 22:51:42 alexa dhclient: [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val]
Jul 24 22:51:42 alexa dhclient: [-sf script-file] [interface]
Jul 24 22:51:42 alexa dhclient:
Jul 24 22:51:42 alexa dhclient: If you did not get this software from ftp.isc.org, please
Jul 24 22:51:42 alexa dhclient: get the latest from ftp.isc.org and install that before
Jul 24 22:51:42 alexa dhclient: requesting help.
Jul 24 22:51:42 alexa dhclient:
Jul 24 22:51:42 alexa dhclient: If you did get this software from ftp.isc.org and have not
Jul 24 22:51:42 alexa dhclient: yet read the README, please read it before requesting help.
Jul 24 22:51:42 alexa dhclient: If you intend to request help from the dhcp-server@isc.org
Jul 24 22:51:42 alexa dhclient: mailing list, please read the section on the README about
Jul 24 22:51:42 alexa dhclient: submitting bug reports and requests for help.
Jul 24 22:51:42 alexa dhclient:
Jul 24 22:51:42 alexa dhclient: Please do not under any circumstances send requests for
Jul 24 22:51:42 alexa dhclient: help directly to the authors of this software - please
Jul 24 22:51:42 alexa dhclient: send them to the appropriate mailing list as described in
Jul 24 22:51:42 alexa dhclient: the README file.
Jul 24 22:51:42 alexa dhclient:
Jul 24 22:51:42 alexa dhclient: exiting.
Jul 24 22:51:42 alexa NetworkManager: <information> DHCP daemon state now 12 for interface eth0
Jul 24 22:51:42 alexa NetworkManager: <information> DHCP daemon state now 14 for interface eth0
Jul 24 22:52:07 alexa NetworkManager: <information> Device 'eth0' DHCP transaction took too long (>25s), stopping it.
Jul 24 22:52:07 alexa NetworkManager: <information> Activation (eth0) Stage 4 (IP Configure Timeout) scheduled...
Jul 24 22:52:07 alexa NetworkManager: <information> Activation (eth0) Stage 4 (IP Configure Timeout) started...
Jul 24 22:52:07 alexa NetworkManager: <information> No DHCP reply received. Automatically obtaining IP via Zeroconf.
Jul 24 22:52:07 alexa NetworkManager: <information> autoip: Sending probe #0 for IP address 169.254.228.27.
Jul 24 22:52:07 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 24 22:52:09 alexa NetworkManager: <information> autoip: Sending probe #1 for IP address 169.254.228.27.
Jul 24 22:52:09 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 24 22:52:11 alexa NetworkManager: <information> autoip: Sending probe #2 for IP address 169.254.228.27.
Jul 24 22:52:11 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 24 22:52:14 alexa NetworkManager: <information> autoip: Sending announce #0 for IP address 169.254.228.27.
Jul 24 22:52:14 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 24 22:52:17 alexa NetworkManager: <information> autoip: Sending announce #1 for IP address 169.254.228.27.
Jul 24 22:52:17 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 24 22:52:20 alexa NetworkManager: <information> autoip: Sending announce #2 for IP address 169.254.228.27.
Jul 24 22:52:20 alexa NetworkManager: <information> autoip: Waiting for reply...
Jul 24 22:52:23 alexa NetworkManager: <information> Activation (eth0) Stage 5 (IP Configure Commit) scheduled...
Jul 24 22:52:23 alexa NetworkManager: <information> Activation (eth0) Stage 4 (IP Configure Timeout) complete.
Jul 24 22:52:23 alexa NetworkManager: <information> Activation (eth0) Stage 5 (IP Configure Commit) started...
Jul 24 22:52:23 alexa NetworkManager: <information> Your IP address = 169.254.228.27
Jul 24 22:52:24 alexa NetworkManager: <WARNING> (): nm_spawn_process('/etc/init.d/mDNSResponder stop'): could not spawn process. (Failed to execute child process "/etc/init.d/mDNSResponder" (No such file or directory))
Jul 24 22:52:24 alexa NetworkManager: <WARNING> (): nm_spawn_process('/etc/init.d/mDNSResponder zap'): could not spawn process. (Failed to execute child process "/etc/init.d/mDNSResponder" (No such file or directory))
Jul 24 22:52:24 alexa NetworkManager: <WARNING> (): nm_spawn_process('/etc/init.d/mDNSResponder start'): could not spawn process. (Failed to execute child process "/etc/init.d/mDNSResponder" (No such file or directory))
Jul 24 22:52:24 alexa NetworkManager: <information> Activation (eth0) Finish handler scheduled.
Jul 24 22:52:24 alexa NetworkManager: <information> Activation (eth0) Stage 5 (IP Configure Commit) complete.
Jul 24 22:52:24 alexa NetworkManager: <information> Activation (eth0) successful, device activated.
|
It seems that dhclient is not getting the correct arguments, which would explain the usage guide in the logs. Also, oddly enough, when I su - into root, export | grep DBUS doesn't give me anything. Any clue why that would be? |
|
| Back to top |
|
 |
steevdave Developer

Joined: 25 Oct 2004 Posts: 73 Location: Tulsa, OK
|
Posted: Mon Jul 25, 2005 6:56 am Post subject: |
|
|
Gnome-volume-manager problem - I have been banging my head about this for 4 days, before finally figuring out, the problem is with the configure script. You can either write a patch, or attempt to use the one in my overlay for 1.3.3_pre2005 whatever and apply it against gnome-volume-manager 1.3.2 - 1.2.2 does not work well with the latest dbus/hal. You will need to recompile any programs that depend on dbus or hal whenever you recompile them - IF you are upgrading. If it is a recompile, 9 times out of 10 you won't have to.
I have updated my dhcp ebuild in the overlay, it *should* work with the network manager. I have also added bind and bind-tools to my overlay, as there is a dbus patch for them, HOWEVER, NetworkManager doesn't take advantage of the dbus support of named yet.
Please try my new dhcp ebuild, it has a few patches added to it, and I was able to connect with NetworkManager last night at the coffee shop via my crappy Netgear MA101 usb wifi card, so it DOES work. Or at least, it did once.
gnome-volume-manager, well, the jury is still out on it. |
|
| Back to top |
|
 |
jamesshuang Tux's lil' helper


Joined: 08 Aug 2002 Posts: 120
|
Posted: Mon Jul 25, 2005 6:13 pm Post subject: |
|
|
Thank you very much for the help steev! It seems that NetworkManager is working properly right now... Plugging in the connection (wired) at work makes it autodetect, and fetch the IP properly. DNS works properly as well. All is going well... Now all I have to do is try it at home with the wireless. I will let you know if that works properly!
I tried the gentopia ebuild for gnome-volume-manager and it seems to work! however, I'm having trouble emerging pmount, which seems to be necessary for gnome-volume-manager to work. Apparently, nscd is blocking the correct creations of new users, which is one of the operations in emerge pmount. What is nscd for anyways? In any case, when I kill nscd, the emerge works. Gnome volume manager works fine until a certain point though- when I plug in my USB key, it fails to mount with this message:
| Code: |
manager.c/1181: New Device: /org/freedesktop/Hal/devices/usb_device_781_5150_20041101511b20027127
manager.c/1181: New Device: /org/freedesktop/Hal/devices/usb_device_781_5150_20041101511b20027127_if0
manager.c/1181: New Device: /org/freedesktop/Hal/devices/usb_device_781_5150_20041101511b20027127_if0_scsi_host
manager.c/1181: New Device: /org/freedesktop/Hal/devices/usb_device_781_5150_20041101511b20027127_if0_scsi_host_scsi_device_lun0
manager.c/1181: New Device: /org/freedesktop/Hal/devices/storage_model_Cruzer_Mini
manager.c/1187: not a mountable volume: /org/freedesktop/Hal/devices/storage_model_Cruzer_Mini
manager.c/1217: Changed: /dev/sda
manager.c/1181: New Device: /org/freedesktop/Hal/devices/volume_uuid_3B69_1AFD
manager.c/1217: Changed: /dev/sda1
Error: UDI '/dev/sda1' does not exist
|
Any ideas on how to fix this? |
|
| Back to top |
|
 |
jamesshuang Tux's lil' helper


Joined: 08 Aug 2002 Posts: 120
|
Posted: Mon Jul 25, 2005 10:15 pm Post subject: |
|
|
Ok, so I finally got home and tried it with wireless. The connection and fetching works! BUT- I have to kill nscd for firefox to register anything at all... Any way to make nscd not run? because it seems to be causing more trouble than it's helping with...
Gnome-volume-manager still fails, not sure why... but I'll keep prodding it... |
|
| Back to top |
|
 |
steevdave Developer

Joined: 25 Oct 2004 Posts: 73 Location: Tulsa, OK
|
Posted: Mon Jul 25, 2005 10:33 pm Post subject: |
|
|
| About the NSCD thing, yes it would be possible, I am still trying to get my patches applied upstream, because its a pain to apply 3 patches because they haven't applied them yet for whatever reason. I just sent a new one upstream again. I know of the problem with gnome-volume-manager as well, what is happening is that pmount-hal is getting passed the %d option instead of %h - I will be updating my overlay again here in a minute, which should fix that, I also removed the 1.3.3_pre ebuild for now, so the 1.3.2-r1 in my overlay *should* work, I am thinking of downgrading my hal to 0.5.2 until I can figure out what is going on with hal > 0.5.2 |
|
| Back to top |
|
 |
jamesshuang Tux's lil' helper


Joined: 08 Aug 2002 Posts: 120
|
Posted: Mon Jul 25, 2005 11:40 pm Post subject: |
|
|
| Hmm... it seems that the ubuntu patches aren't sitting well with this package... The configure script is looking for libgnomeui-2.0 dbus-glib-1 >= 0.31 hal >= 0.5.0 gtk+-2.0 >= 2.6.0 libgksuui1.0 >= 1.0.0. Definitely not emerging... |
|
| Back to top |
|
 |
steevdave Developer

Joined: 25 Oct 2004 Posts: 73 Location: Tulsa, OK
|
Posted: Tue Jul 26, 2005 2:46 am Post subject: |
|
|
| Which of those don't you have? It might be easier if you message me about what you have via private message in the forums rather than in this thread as its rather Off Topic of NetworkManager - I am still working on it. |
|
| Back to top |
|
 |
j0shwalk3r n00b

Joined: 26 Jul 2005 Posts: 2 Location: Hampton, VA
|
Posted: Tue Jul 26, 2005 3:33 am Post subject: got it working |
|
|
Just wanted to drop a quick note to thank steev and everyone else in this thread. I've been working through the same thing and am now typing this over wifi controlled by NetworkManager.
Hope I can help with any questions, now that I got something working. |
|
| Back to top |
|
 |
rel Tux's lil' helper

Joined: 20 Apr 2002 Posts: 137
|
Posted: Sat Aug 13, 2005 8:25 pm Post subject: |
|
|
Can't get it to work. Using steev's version.
| Code: |
NetworkManager: <information> starting...
NetworkManager: <information> eth0: Driver support level for 'tg3' is fully-supported
NetworkManager: <information> Activated the DHCP daemon /sbin/dhcdbd with PID 25847.
NetworkManager: <information> Error from dhcdbd on 'reason' request because: name 'org.freedesktop.DBus.Error.ServiceUnknown', message 'The name com.gentoo.dhcp was not provided by any .service files'.
NetworkManager: <information> Will activate wired connection 'eth0' because it now has a link.
NetworkManager: <information> Device eth0 activation scheduled...
NetworkManager: <information> nm_device_new(): waiting for device's worker thread to start
NetworkManager: <information> nm_device_new(): device's worker thread started, continuing.
NetworkManager: <information> Now managing wired device 'eth0'.
NetworkManager: <information> Deactivating device eth0.
Warning: Driver for device wlan0 recommend version 18 of Wireless Extension,
but has been compiled with version 17, therefore some driver features
may not be available...
NetworkManager: <information> wlan0: Driver support level for 'ndiswrapper' is fully-supported
NetworkManager: <WARNING> (): data good :-)
NetworkManager: <information> nm_device_new(): waiting for device's worker thread to start
NetworkManager: <information> nm_device_new(): device's worker thread started, continuing.
NetworkManager: <information> Now managing wireless device 'wlan0'.
NetworkManager: <information> Deactivating device wlan0.
NetworkManager: <information> Activation (eth0) started...
NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) scheduled...
NetworkManager: <information> Old device 'eth0' activating, won't change.
NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) started...
NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) scheduled...
NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) complete.
NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) starting...
NetworkManager: <information> Activation (eth0/wired) Stage 2 (Device Configure) successful.
NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) scheduled.
NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) complete.
NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) started...
NetworkManager: <information> Activated the DHCP daemon /sbin/dhcdbd with PID 25926.
NetworkManager: <information> Old device 'eth0' activating, won't change.
NetworkManager: <information> Activation (eth0) Beginning DHCP transaction.
NetworkManager: <information> Couldn't send DHCP 'up' message because: name 'org.freedesktop.DBus.Error.ServiceUnknown', message 'The name com.gentoo.dhcp was not provided by any .service files'.
NetworkManager: <information> Activation (eth0) failure scheduled...
NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) complete.
NetworkManager: <information> Activation (eth0) failed.
NetworkManager: <information> Deactivating device eth0.
NetworkManager: <information> SWITCH: no current connection, found better connection 'eth0'.
NetworkManager: <information> Activated the DHCP daemon /sbin/dhcdbd with PID 25931.
NetworkManager: <information> Error from dhcdbd on 'reason' request because: name 'org.freedesktop.DBus.Error.ServiceUnknown', message 'The name com.gentoo.dhcp was not provided by any .service files'.
NetworkManager: <information> Will activate connection 'eth0'.
NetworkManager: <information> Device eth0 activation scheduled...
NetworkManager: <information> Activation (eth0) started...
NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) scheduled...
NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) started...
NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) scheduled...
NetworkManager: <information> Activation (eth0) Stage 1 (Device Prepare) complete.
NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) starting...
NetworkManager: <information> Activation (eth0/wired) Stage 2 (Device Configure) successful.
NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) scheduled.
NetworkManager: <information> Activation (eth0) Stage 2 (Device Configure) complete.
NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) started...
NetworkManager: <information> Activated the DHCP daemon /sbin/dhcdbd with PID 25934.
NetworkManager: <information> Activation (eth0) Beginning DHCP transaction.
NetworkManager: <information> Couldn't send DHCP 'up' message because: name 'org.freedesktop.DBus.Error.ServiceUnknown', message 'The name com.gentoo.dhcp was not provided by any .service files'.
NetworkManager: <information> Activation (eth0) failed.
NetworkManager: <information> Deactivating device eth0.
NetworkManager: <information> SWITCH: no current connection, found better connection 'eth0'.
NetworkManager: <information> Activation (eth0) failure scheduled...
NetworkManager: <information> Activation (eth0) Stage 3 (IP Configure Start) complete.
NetworkManager: <information> Activated the DHCP daemon /sbin/dhcdbd with PID 25939.
NetworkManager: <information> Error from dhcdbd on 'reason' request because: name 'org.freedesktop.DBus.Error.ServiceUnknown', message 'The name com.gentoo.dhcp was not provided by any .service files'.
|
Also, how should I start the applet. Should I add it from the gnome-applets dialog? It's not there..
hal v. 0.54
dbus v. 0.36
networkmanager v. 0.4.1_pre20050806
greets |
|
| Back to top |
|
 |
BigBaaadBob Guru


Joined: 19 Apr 2003 Posts: 342 Location: Swampscott, MA USA
|
Posted: Mon Sep 12, 2005 6:48 pm Post subject: |
|
|
| Is there a working ebuild for this now? Does it require extreme unmasking of dependencies? |
|
| Back to top |
|
 |
sog Guru


Joined: 04 Apr 2004 Posts: 356
|
Posted: Mon Sep 12, 2005 7:04 pm Post subject: |
|
|
AFAIK there is not, and when i unmasked the dbus and hal necessary to get NetworkManager working, it broke Tomboy. if you're worried about dependencies, i'd hold off for just a bit. _________________ ------------------------------------------------
(blog) http://www.redmonk.com/sogrady/ |
|
| Back to top |
|
 |
rel Tux's lil' helper

Joined: 20 Apr 2002 Posts: 137
|
Posted: Wed Sep 14, 2005 8:51 am Post subject: |
|
|
| sog wrote: | | AFAIK there is not, and when i unmasked the dbus and hal necessary to get NetworkManager working, it broke Tomboy. if you're worried about dependencies, i'd hold off for just a bit. |
you should get tomboy working again by re-emerging it. |
|
| Back to top |
|
 |
hgomersall Tux's lil' helper


Joined: 08 Jul 2002 Posts: 135 Location: Cambridge, UK
|
Posted: Thu Sep 15, 2005 2:43 pm Post subject: |
|
|
I now have a working installation of NetworkManager using the ebuild from gentopia. It works like a dream. I can move from home wired to home wireless to internet caf with no trouble.
Initially, the hal and dbus upgrade seemed to break nautilus (gvm seemed to be working fine, but nautilus didn't display the mount), but upgrading to gnome 2.12 has solved everything.
Steadily, everything is coming together. My desktop is pretty much functionally perfect now.
I needed to unmask a few things, but so far it hasn't broken anything. Its certainly worth the possible instability for the awesome functionality.
This is ipw2200 with a Dell Inspiron 8100. |
|
| Back to top |
|
 |
GaMMa l33t


Joined: 23 Aug 2002 Posts: 684 Location: USA
|
Posted: Sat Sep 24, 2005 5:38 pm Post subject: |
|
|
| hgomersall wrote: | I now have a working installation of NetworkManager using the ebuild from gentopia. It works like a dream. I can move from home wired to home wireless to internet caf with no trouble.
Initially, the hal and dbus upgrade seemed to break nautilus (gvm seemed to be working fine, but nautilus didn't display the mount), but upgrading to gnome 2.12 has solved everything.
Steadily, everything is coming together. My desktop is pretty much functionally perfect now.
I needed to unmask a few things, but so far it hasn't broken anything. Its certainly worth the possible instability for the awesome functionality.
This is ipw2200 with a Dell Inspiron 8100. |
What do you do to get NetworkManager running? I execute NetworkManager as root and no icons appear, and nothing seems to happen. _________________ Ubuntu Linux Dapper Drake running Gnome-2.14.1
[Website | Screenshot | Portage Guide] |
|
| Back to top |
|
 |
j0shwalk3r n00b

Joined: 26 Jul 2005 Posts: 2 Location: Hampton, VA
|
Posted: Tue Sep 27, 2005 11:27 pm Post subject: resolv.conf problem |
|
|
| I've got NetworkManager working almost completely. The only remaining problem I still have is that /etc/resolv.conf keeps getting set to 600 permissions. My umask is 022. I've seen this problem elsewhere, but so far haven't seen a solution to it. If anyone can help out, I would greatly appreciate. |
|
| Back to top |
|
 |
GaMMa l33t


Joined: 23 Aug 2002 Posts: 684 Location: USA
|
Posted: Thu Sep 29, 2005 2:16 am Post subject: |
|
|
Do I just run NetworkManager as root and everything should work? Nothing happens when I do.. _________________ Ubuntu Linux Dapper Drake running Gnome-2.14.1
[Website | Screenshot | Portage Guide] |
|
| Back to top |
|
 |
hgomersall Tux's lil' helper


Joined: 08 Jul 2002 Posts: 135 Location: Cambridge, UK
|
Posted: Thu Sep 29, 2005 6:01 pm Post subject: |
|
|
| GaMMa wrote: | | Do I just run NetworkManager as root and everything should work? Nothing happens when I do.. |
You add network manager to your init (rc-update add NetworkManager default) and start it for this session.
You also need to run nm-applet (I added it to my sessions->start up programs). It sticks a little icon in the notification area.
I also had to copy /etc/dhcp/dhclient-script.sample to /sbin/dhclient-script for it to work properly.
Incidently, i have noticed some problems with dropped connection that doesn't recover without a driver reload, but I have put this down to flaky ipw2200 drivers. |
|
| Back to top |
|
 |
GaMMa l33t


Joined: 23 Aug 2002 Posts: 684 Location: USA
|
Posted: Thu Sep 29, 2005 11:39 pm Post subject: |
|
|
Ahh thanks! I've got 2 problems right now. Trying to execute nm-applet as a user I get this error:
** (nm-applet:2560): WARNING **: <WARNING> (): nmwa_dbus_init() could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.5" is not allowed to own the service "org.freedesktop.NetworkManagerInfo" due to security policies in the configuration file'
I can run it as root, but it doesn't seem to use dhcp but manually tries connecting to the network, which makes the connection not work. I tried the dhclient-script thing, but no luck. Any ideas? _________________ Ubuntu Linux Dapper Drake running Gnome-2.14.1
[Website | Screenshot | Portage Guide] |
|
| Back to top |
|
 |
GaMMa l33t


Joined: 23 Aug 2002 Posts: 684 Location: USA
|
Posted: Thu Oct 06, 2005 2:10 am Post subject: |
|
|
Anyone know how to solve my problem? I don't know why dhcp doesn't want to work correctly. Kind of OT: I just got swsusp2 working (with nvidia) which is exciting . _________________ Ubuntu Linux Dapper Drake running Gnome-2.14.1
[Website | Screenshot | Portage Guide] |
|
| Back to top |
|
 |
GaMMa l33t


Joined: 23 Aug 2002 Posts: 684 Location: USA
|
Posted: Thu Oct 20, 2005 9:40 pm Post subject: |
|
|
UPDATE: Got things working for root. As user when trying to run nm-applet I get the error ** (nm-applet:13467): WARNING **: <WARNING> (): nmwa_dbus_init() could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.6" is not allowed to own the service "org.freedesktop.NetworkManagerInfo" due to security policies in the configuration file'
I can modify the /etc/dbus-1/system.d/nm-applet.conf file to get rid of the error messages, but then it says network not found when nm-applet is run as user. Running as root works fine though however after the change. Help? _________________ Ubuntu Linux Dapper Drake running Gnome-2.14.1
[Website | Screenshot | Portage Guide] |
|
| Back to top |
|
 |
omné Guru


Joined: 23 Feb 2003 Posts: 355 Location: Paris / France
|
Posted: Sat Oct 22, 2005 11:12 am Post subject: |
|
|
Maybe can you play with the other files in system.d ?
The dhcdbd.conf and NetworkManager.conf for exemple.
For me only root can run nm-applet too.
My problem is with the WEP key.
Using wifi-radar, I set the key in hexa like this : xx:yy:zz:aa:bb and it works.
But in NetworkManager, nothing works, I tried with and without the ":" in the Hexa or with the 26 character key in passkey but nothing works.
Any idear will be cool.
Omné. |
|
| Back to top |
|
 |
GaMMa l33t


Joined: 23 Aug 2002 Posts: 684 Location: USA
|
Posted: Sat Oct 22, 2005 5:12 pm Post subject: |
|
|
Wahoo got it working! Here's my config/mini howto:
Move /etc/dhcp/dhclient-script.sample to /sbin and chmod +x it.
Add the following in /etc/dbus-1/system.d:
NetworkManager.conf
<policy user="YOUR USERNAME HERE">
<allow send_destination="org.freedesktop.NetworkManager"/>
<allow send_interface="org.freedesktop.NetworkManager"/>
</policy>
nm-applet.conf
<policy user="YOUR USERNAME HERE">
<allow own="org.freedesktop.NetworkManagerInfo"/>
<allow send_destination="org.freedesktop.NetworkManagerInfo"/>
<allow send_interface="org.freedesktop.NetworkManagerInfo"/>
</policy>
There's some kind of issue with dbus or something I believe. The console line should make nm-applet work, but it's not picking up on it. Not sure if it's got something to do with the pam_console USE flag in pam, or what, but I tried adding it there and no luck, so whatever. This way works . _________________ Ubuntu Linux Dapper Drake running Gnome-2.14.1
[Website | Screenshot | Portage Guide] |
|
| Back to top |
|
 |
sog Guru


Joined: 04 Apr 2004 Posts: 356
|
Posted: Fri Feb 24, 2006 7:44 pm Post subject: |
|
|
anybody know why i can't get NetworkManager installed?
compile error is:
| Code: | ../gnome/libnm_glib/.libs/libnm_glib.so: undefined reference to `dbus_bus_get_private'
collect2: ld returned 1 exit status
make[3]: *** [libnm_glib_test] Error 1
make[3]: Leaving directory `/var/tmp/portage/networkmanager-0.5.2_pre20060221/work/NetworkManager-0.5.2/test'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/networkmanager-0.5.2_pre20060221/work/NetworkManager-0.5.2/test'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/networkmanager-0.5.2_pre20060221/work/NetworkManager-0.5.2'
make: *** [all] Error 2
!!! ERROR: net-misc/networkmanager-0.5.2_pre20060221 failed.
!!! Function gnome2_src_compile, Line 48, Exitcode 2
|
any ideas? _________________ ------------------------------------------------
(blog) http://www.redmonk.com/sogrady/ |
|
| Back to top |
|
 |
sog Guru


Joined: 04 Apr 2004 Posts: 356
|
Posted: Mon Feb 27, 2006 5:12 am Post subject: |
|
|
[SOLVED]
ok, so i couldn't get networkmanager-0.5.2_pre20060221 installed because of the error above, but i was able to get 0.51 deployed (with an emerge -a =networkmanager-0.51-r1). i've also modified the NetworkManager.conf & nm-applet.conf files as recommended, added NetworkManager to my default runlevel, and added my user to the newly created dhcp group. i didn't have to move dhclient.script b/c that was already present.
after adding nm-applet to my startup programs, however, i get an error saying that nm-applet cannot find some necessary resources and can't continue. the command line output is below - any ideas?
| Code: | ** (nm-applet:6339): WARNING **: Icon nm-no-connection missing: Icon 'nm-no-connection' not present in theme
(nm-applet:6339): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
|
so problem #1, the icons: this fixed it: gtk-update-icon-cache -f /usr/share/icons/hicolor/
problem #2: NetworkManager would display, but not update networks
remerged dhcp, dhcdbd, and networkmanager packages with dbus use flag, and ensured that i was using the gentopia rather than portage ebuilds
and that pretty much fixed it. works like a champ so far. _________________ ------------------------------------------------
(blog) http://www.redmonk.com/sogrady/ |
|
| Back to top |
|
 |
dashnu l33t

Joined: 21 Jul 2004 Posts: 703 Location: Casco Maine
|
Posted: Tue Mar 07, 2006 5:27 pm Post subject: |
|
|
Few questions. I have this working for my wired card. However when I set up a new wireless connection I do not see WPA-PSK for an option. Am I missing something? Also do I need to keep my net.eth* in my default run level or does NetworkManager handle it all now?
My card is supported. I think I have the latest and greatest ebuilds. I used these ebuilds & patches.
http://gentoo.zugaina.org/gentopia/net-misc.html.en
Any ideas?
TIA
*edit
Also I can not build networkmanager-vpnc probably because I run a ppc chip. But anyways the error.
| Code: | nm-vpnc-service.c:66: error: syntax error before "NMVPNState"
nm-vpnc-service.c:66: warning: no semicolon at end of struct or union
nm-vpnc-service.c:70: error: syntax error before '}' token
nm-vpnc-service.c:70: warning: type defaults to `int' in declaration of `NmVpncData'
|
_________________ write quit bang |
|
| Back to top |
|
 |
|