Ubuntu Suspend w/ Ethernet Cable Plugged in
- From: Mario Limonciello <mario mailing gmail com>
- To: NetworkManager-list gnome org
- Cc:
- Subject: Ubuntu Suspend w/ Ethernet Cable Plugged in
- Date: Sun, 13 Nov 2005 12:39:23 -0600
Hello All,
I'm using Ubuntu Dapper (although I know this was occurring in Breezy as
well) w/ a deb of NetworkManager 0.5.1. A friend of mine who isn't so
linux savy is having the same problems in Breezy with the version of
Network Manager that ships with it.
NetworkManager works fine for me for the most part while the computer is
up and running to switch between networks, but after a suspend things go
wacky.
When you suspend a machine in ubuntu, it by default pulls out all kernel
modules for network devices and usb devices to prevent errors.
My thinkpad is using the e1000 kernel module for ethernet and madwifi
for wireless. So, both of these modules are pulled and reinserted after
a suspend.
My problem is that if I leave the cat5 plugged in during a suspend,
after the resume it seems that NM goes through this process:
1) Ubuntu reinserts the wireless module before the wired module, so
RIGHT after the resume it will try to associate with a wireless network.
2) As soon as the wired module is reinserted, it stops associating with
a wireless network (as i'd hope).
3) Now one of two reproducible things different things seem to happen
every time here.
A) There was enough time for it to associate with a wireless
network. So it records the nameservers in my /etc/resolv.conf. It
reassociates with the wired network fine, but the nameservers are wrong
and not updated.
B) It gets the address that I should be getting immediately after
the module is reinserted, and actually the network works momentarily.
Soon thereafter it stops to work and going to connection information
shows that I received an address in the 169.254 range.
If I pull the ethernet cable and plug it back in, things are back to
normal again in either case. The second case seems to happen more
often, but I have reproduced the first case several times.
My question here is where to assign blame to, is it Ubuntu ACPI scripts,
the fact that I probably haven't properly disabled the debian style
networking options for Ubuntu, or a bug in Network Manager?
Thanks
Mario Limonciello
mario mailing gmail com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]