Simon Geard wrote:
> On Thu, 2008-09-04 at 07:29 -0700, Dan Nicholson wrote:
>
>> [snip]
>>
> As for NM itself, I don't need any patches to use current SVN - it's
> become generic enough that it works fine to build with
> --with-distro=redhat and a custom bootscript to start it on LFS.
>
> Stuff like 3G broadband and VPN might require extra packages, but the
> basic dependencies according to my scripts are hal, wpa_supplicant, ppp,
> libgcrypt, libnl, and dhcp. The Gnome applet additionally requires
> gnome-keyring, libnotify, libglade, and NSS.
>
Sorry to bring this up after so long, but can you shed some more light
on how your setup is ? I've been struggeling trying to get
NetworkManager up and running for the better part of this evening, and I
can't get it to do what i *think* is right. No matter what I try, i
end up with the following :
[EMAIL PROTECTED] : /usr/sbin/NetworkManager --no-daemon
NetworkManager: <info> starting...
NetworkManager: <info> eth0: Device is fully-supported using driver
'e1000'.
NetworkManager: <info> nm_device_init(): waiting for device's worker
thread to start
NetworkManager: <info> nm_device_init(): device's worker thread
started, continuing.
NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
NetworkManager: <info> Deactivating device eth0.
NetworkManager: <WARN> nm_spawn_process():
nm_spawn_process('/etc/init.d/net.lo start'): could not spawn process.
(Failed to execute child process "/etc/init.d/net.lo" (No such file or
directory))
NetworkManager: <info> Will activate wired connection 'eth0' because it
now has a link.
NetworkManager: <info> SWITCH: no current connection, found better
connection 'eth0'.
NetworkManager: <info> Will activate connection 'eth0'.
NetworkManager: <info> Device eth0 activation scheduled...
NetworkManager: <info> Activation (eth0) started...
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare)
scheduled...
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare)
started...
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device
Configure) scheduled...
NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare)
complete.
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device
Configure) starting...
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device
Configure) successful.
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure
Start) scheduled.
NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device
Configure) complete.
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure
Start) started...
NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure
Start) complete.
NetworkManager: <info> DHCP daemon state is now 12 (successfully
started) for interface eth0
NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for
interface eth0
NetworkManager: <info> Device 'eth0' DHCP transaction took too long
(>45s), stopping it.
NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure
Timeout) scheduled...
NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure
Timeout) started...
NetworkManager: <info> No DHCP reply received. Automatically obtaining
IP via Zeroconf.
NetworkManager: <info> autoip: Sending probe #0 for IP address
169.254.147.141.
NetworkManager: <info> autoip: Waiting for reply...
NetworkManager: <info> autoip: Sending probe #1 for IP address
169.254.147.141.
NetworkManager: <info> autoip: Waiting for reply...
NetworkManager: <info> autoip: Got some data to check for reply packet.
NetworkManager: <WARN> get_autoip(): autoip: (eth0) recv arp type=2048,
op=16384,
NetworkManager: <WARN> get_autoip(): source = 184.110.192.168
2D:06:51:46:CC:98,
NetworkManager: <WARN> get_autoip(): target = 68.175.236.2
0C:69:00:15:DF:09
NetworkManager: <info> autoip: Sending probe #2 for IP address
169.254.147.141.
NetworkManager: <info> autoip: Waiting for reply...
NetworkManager: <info> autoip: Sending announce #0 for IP address
169.254.147.141.
NetworkManager: <info> autoip: Waiting for reply...
NetworkManager: <info> autoip: Sending announce #1 for IP address
169.254.147.141.
NetworkManager: <info> autoip: Waiting for reply...
NetworkManager: <info> autoip: Sending announce #2 for IP address
169.254.147.141.
NetworkManager: <info> autoip: Waiting for reply...
NetworkManager: <info> autoip: Got some data to check for reply packet.
NetworkManager: <WARN> get_autoip(): autoip: (eth0) recv arp type=2048,
op=16384,
NetworkManager: <WARN> get_autoip(): source = 184.110.169.254
2D:06:77:E9:CC:98,
NetworkManager: <WARN> get_autoip(): target = 68.175.236.2
93:8D:00:15:DF:09
NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure
Commit) scheduled...
NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure
Timeout) complete.
NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure
Commit) started...
NetworkManager: <WARN> nm_spawn_process():
nm_spawn_process('/usr/bin/killall -q nscd'): could not spawn process.
(Failed to execute child process "/usr/bin/killall" (No such file or
directory))
NetworkManager: <WARN> nm_spawn_process():
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))
NetworkManager: <WARN> nm_spawn_process():
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))
NetworkManager: <WARN> nm_spawn_process():
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))
NetworkManager: <info> Activation (eth0) Finish handler scheduled.
NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure
Commit) complete.
NetworkManager: <info> Activation (eth0) successful, device activated.
NetworkManager: <WARN> nm_signal_handler(): Caught signal 2, shutting
down normally.
NetworkManager: <info> Caught terminiation signal
NetworkManager: <debug> [1228256665.170226] nm_print_open_socks(): Open
Sockets List:
NetworkManager: <debug> [1228256665.170319] nm_print_open_socks(): Open
Sockets List Done.
NetworkManager: <info> Deactivating device eth0.
root [ ~/sources/NetworkManager-0.7.0 ]# ip addr
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 10
link/ether 00:1b:38:83:1f:7e brd ff:ff:ff:ff:ff:ff
inet 169.254.147.141/16 brd 169.254.255.255 scope global eth0
If start dhclient it is able to get an "sane" address assigned to eth0.
The versions i have is :
- NetworkManager-6.5.0/network-manager-applet-6.5.0
- libnl-1.0-pre6
- dhclient from dhcp-3.0.6 with both patches
- wpa_supplicant v0.5.8
- HAL package version: 0.5.9.1
*Any* help in getting me to understand what's going on is much apreciated ;-)
regs,
peram
> Simon.
>
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
