Can I just chime in and mention that my NetworkManager doesn't survive
resume as well? The /etc/init.d/network-manager restart fixes it.
(Not that I expect much support for ndiswrapper.... B-)
Here's a not-very-useful report from daemon.log. (Debian testing,
network-manager 0.6.6-1, ndiswrapper-source 1.52-1, g-p-m 2.22.1-1, hal
0.5.11-2, acpi 1.1-1.)
Jul 1 05:06:39 daptop NetworkManager: <info> Waking up from sleep.
Jul 1 05:06:39 daptop NetworkManager: <info> Deactivating device wlan0.
Jul 1 05:06:39 daptop NetworkManager: <WARN>
nm_device_802_11_wireless_set_essid(): error setting ESSID to '' for
device wlan0: Invalid argument
Jul 1 05:06:39 daptop NetworkManager: <WARN> nm_signal_handler():
Caught signal 11. Generating backtrace...
Jul 1 05:06:39 daptop NetworkManager: ******************* START
**********************************
Jul 1 05:06:39 daptop NetworkManager: (no debugging symbols found)
Jul 1 05:06:39 daptop NetworkManager: Using host libthread_db library
"/lib/i686/cmov/libthread_db.so.1".
Jul 1 05:06:39 daptop NetworkManager: (no debugging symbols found)
Jul 1 05:06:40 daptop last message repeated 12 times
Jul 1 05:06:40 daptop NetworkManager: [Thread debugging using
libthread_db enabled]
Jul 1 05:06:40 daptop NetworkManager: [New Thread 0xb7b32720 (LWP 3985)]
Jul 1 05:06:40 daptop NetworkManager: [New Thread 0xb6b2fb90 (LWP 4423)]
Jul 1 05:06:40 daptop NetworkManager: [New Thread 0xb7330b90 (LWP 4040)]
Jul 1 05:06:40 daptop NetworkManager: [New Thread 0xb7b31b90 (LWP 4024)]
Jul 1 05:06:40 daptop NetworkManager: (no debugging symbols found)
Jul 1 05:06:40 daptop last message repeated 7 times
Jul 1 05:06:40 daptop NetworkManager: 0xffffe410 in __kernel_vsyscall ()
Jul 1 05:06:40 daptop NetworkManager: ******************* END
**********************************
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
