[Bug 45356] Re: Wrong network interface order after resume from suspend to ram resulting in no network connectivity

2007-02-27 Thread Peter Whittaker
I should have marked this as needs info (or left it there) last time, when I added the request for more information. At any rate, since the requested information is not available and the bug has sat without updates for 6 weeks, I am marking as rejected based on lack of response. ** Changed in:

[Bug 45356] Re: Wrong network interface order after resume from suspend to ram resulting in no network connectivity

2007-01-19 Thread Peter Whittaker
I'm marking this as confirmed based on several people recording the same problem. Folks, to move forward on this, can you each please attach the output of the following commands? uname -a sudo lspci -vv sudo lspci -vvn sudo dmidecode Please be sure to use sudo, as these require root

[Bug 45356] Re: Wrong network interface order after resume from suspend to ram resulting in no network connectivity

2006-11-07 Thread greubeuld
I have the same issue as Chris Jones. Email me if more info is needed. -- Wrong network interface order after resume from suspend to ram resulting in no network connectivity https://launchpad.net/bugs/45356 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 45356] Re: Wrong network interface order after resume from suspend to ram resulting in no network connectivity

2006-10-14 Thread towsonu2003
** Changed in: Ubuntu Sourcepackagename: None = acpi-support -- Wrong network interface order after resume from suspend to ram resulting in no network connectivity https://launchpad.net/bugs/45356 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 45356] Re: Wrong network interface order after resume from suspend to ram resulting in no network connectivity

2006-07-11 Thread Chris Jones
I just installed on an X40 and I appear to be seeing a similar problem, but I'm not sure if it's identical. The network devices come back up with the right names, but they don't seem to trigger udev/hal events, so networkmanager doesn't see them again and thinks it has no network devices to work