Re: No dhclient started for wireless card



On 4/22/07, Lea Wiemann <LeWiemann gmail com> wrote:
Patrick Bogen wrote:

> I meant a successful association with NetworkManager.

NetworkManager causes my card to associate indeed (according to
iwconfig), but it does not leave a trace in the logs.  I'm attaching the
lines NetworkManager wrote to /var/log/syslog.

Hm...  What can I do to debug this?

Best,

   Lea

Apr 22 15:47:50 fly NetworkManager: <information>^Istarting...
Apr 22 15:47:50 fly NetworkManager: <information>^Ieth0: Device is fully-supported using driver 'tg3'.
Apr 22 15:47:50 fly NetworkManager: <information>^Inm_device_init(): waiting for device's worker thread to start
Apr 22 15:47:50 fly NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Apr 22 15:47:50 fly NetworkManager: <information>^INow managing wired Ethernet (802.3) device 'eth0'.
Apr 22 15:47:50 fly NetworkManager: <information>^IDeactivating device eth0.
Apr 22 15:47:50 fly NetworkManager: <information>^Ieth2: Device is fully-supported using driver 'ipw2200'.
Apr 22 15:47:50 fly NetworkManager: <information>^Inm_device_init(): waiting for device's worker thread to start
Apr 22 15:47:50 fly NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Apr 22 15:47:50 fly NetworkManager: <information>^INow managing wireless (802.11) device 'eth2'.
Apr 22 15:47:50 fly NetworkManager: <information>^IDeactivating device eth2.
Apr 22 15:48:34 fly NetworkManager: <WARNING>^I nm_signal_handler (): Caught signal 15, shutting down normally.
Apr 22 15:48:34 fly NetworkManager: <information>^ICaught terminiation signal
Apr 22 15:48:34 fly NetworkManager: <debug info>^I[1177271314.518053] nm_print_open_socks (): Open Sockets List:
Apr 22 15:48:34 fly NetworkManager: <debug info>^I[1177271314.518128] nm_print_open_socks (): Open Sockets List Done.
Apr 22 15:48:34 fly NetworkManager: <information>^IDeactivating device eth0.
Apr 22 15:48:34 fly NetworkManager: <information>^IDeactivating device eth2.


How are you controlling Network Manager without the GUI?  VIA Dbus?  I
don't think NM can be used from a console without calling it through
dbus.   Additionally the logs you post show that you are starting NM
but then it stops right away so it never can associate.  Why are you
trying to run NM without one of the GUI's?



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]