We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: linux-source-2.6.1
Any news on this ?
** Changed in: linux-source-2.6.15 (Ubuntu)
Importance: Undecided => High
--
network lost on suspend on Asus M2N
https://bugs.launchpad.net/bugs/49984
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
Thank you for your bug report. Do you still have this issue with the
latest release of Ubuntu ?
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Unconfirmed => Needs Info
--
network lost on suspend on Asus M2N
https://bugs.launchpad.net/bugs/49984
You received this bug notification bec
..forget to say: a night WITHOUT Suspend!
** Attachment added: "lspci -vv"
http://librarian.launchpad.net/3084563/lspci-vv.txt
--
network lost on suspend on Asus M2N
https://launchpad.net/bugs/49984
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
That certainly seem suspicious, but the fact is if manually configuring
it works, then the kernel has performed everything that NetworkManager
would normally ask it to do.
So I'm a little reluctant to say this is a kernel bug. Possibly
NetworkManager is at fault.
Please attach the output of "lspc
yes, I can. If I boot with -23, it still works automatically - that's
why I guess it's the kernel.
--
network lost on suspend on Asus M2N
https://launchpad.net/bugs/49984
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Question is, can you manually configure these devices? If so, then I
would blame it on something else besides the kernel.
--
network lost on suspend on Asus M2N
https://launchpad.net/bugs/49984
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubu
ok, some more details, I found:
I'm using network-manager here, so the devices do not get automatically
configured in /etc/network/interfaces, but the NetworkManager-Scripts
seam to do ifconfig eth0 up and ifconfig eth1 up (nothing more!) after
booting. This get's restored with 2.6.15-23, but not
