Network disconnected after "suspend" (Intel 3945ABG), reboot only way to get it back on

[Pascal Desroches]

Happens about 50 % of the time when resuming from "suspend" (or "hibernate" but I don't use this). Unable to restart wireless, the only option is to reboot. Resuming from "suspend" might work perfectly 3 times in a row, only then to get the next 4 with network disconnected...

Other users have had similar problems, but that was regarding power management (the problem didn't occur when plugged in, only when on battery). My problem occurs when plugged in.

I used "Aport" (or something) but I did this after a suspend session, so I wasn't connected to the internet and therefore I was unable to send it. I also tried to copy the huge amount of information it gave but that didn't seem to be possible. However, I did create the 4 documents listed on this page. I'll try to find a way to attach them to this text.

Same problem with 10.04. As far as I can remember, it also occurred with 9.10. Also, I've tried the last 2 or 3 versions of Xubuntu and Linux Mint, and the latest version of Fedora, and the same happens. It happens with 32- and 64-bit versions.

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Xubuntu better. If you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Pascal Desroches (pascal-desroches)]

I might need some help with that... "upstream" and "kernel" means nothing to me. However I did read everything on that page (your link) and I chose to download what I could find on the link in this sentence: "Most likely that you want to download and test against the most current version.". Once downloaded, I let Ubuntu software centre install it. Then I rebooted. What should I do now, except clicking on the yellow pencil icon (which I will do as soon as I understand whether I have done things correctly.)?

Thank you!

[Pascal Desroches (pascal-desroches)]

I have put my computer to "suspend" a few times and the same problem reappeared.

Is there something I can do to check whether "linux-headers-2.6.37-999_2.6.37-999.201101140908_all.deb" is in fact correctly installed?

[Charlie Kravetz (cjkgeek)]

thank you for testing this kernel. You can check if it installed by opening a terminal and typing
uname -a

It should respond with the Linux "some_name" 2.6.37-
numbers showing that the kernel was changed. The numbers for Karmic are 2.6.31- and the numbers for Lucid 10.04 are 2.6.32- .

[Pascal Desroches (pascal-desroches)]

Thanks. It didn't work the first time, I was still on an old kernel. I downloaded 3 files from this page ( http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2011-01-13-natty/ ) and then it worked. I'll do the testing now and I'll report back.

[Pascal Desroches (pascal-desroches)]

I still have the exact same problem.

[Charlie Kravetz (cjkgeek)]

Thank you for following up on this. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[Charlie Kravetz (cjkgeek)]

Fedora task is marked invalid. It is only used when tracking the same issue reported as a bug to Fedora.

[Pascal Desroches (pascal-desroches)]

Thanks to everyone who participates in making Ubuntu better (especially those who might solve my problem ;) !

[Pascal Desroches (pascal-desroches)]

Additional information: As mentioned in the first post, this problem occurs 50 % of the time (probably a bit more than 50 %).

I have recently made a change which affects the problem. Ever since I removed the password protection (a few days ago) after resuming from suspend, I have had the connection starting up about 75 % of the time!

So to make things clear: if I have to enter my password after suspend, the network is likely to be disconnected. If I don't have to enter my password, the network connection is likely to appear and work.

(I've been wanting to remove the password thing after resume for so long, but couldn't remember how to. Now I'm really glad I found it!)

[Pascal Desroches (pascal-desroches)]

I still have this problem =(

[Wolfgang Kufner (wolfgangkufner)]

Care to try with the current newest kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.39-rc5-oneiric/ to see whether it is fixed there?

[ENigma885 (enigma-pentagram)]

_____________________________________________

****A WORKAROUND (tried under Ubuntu 11.10)
_____________________________________________
1- Open a terminal window and
gksudo gedit /etc/pm/config.d/unload_modules
(even if the file is not there it will be created)

2- in this document add
SUSPEND_MODULES="Your_Network_Driver" [with the qoutes] (to get ur network driver's name follow the next step)

3- Open a terminal and
sudo lshw
- Under "network" section then under "configuration" the driver will be written as "driver=SOMETHING"
(you can use the search menu in the terminal to search for network)
- Example:-
*-network
                description: Ethernet interface
                product: RTL8111/8168B PCI Express Gigabit Ethernet controller
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:09:00.0
                logical name: eth0
                version: 02
                serial: 00:23:8b:62:11:7c
                size: 100Mbit/s
                capacity: 1Gbit/s
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
                configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=N/A ip=192.168.1.62 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s

**##So, what will be written in the document opened in the first step is
SUSPEND_MODULES="r8169"

then save the file.

- After saving the file resuming after a suspend will reconnect your network automatically.

( Source: Organized from http://ubuntuforums.org/showthread.php?t=1164115)

[Pascal Desroches (pascal-desroches)]

Unfortunately this did not fix the problem for me!

I'm currently using Elementary Jupiter (based on Ubuntu 10.10 if I'm correct) though, I don't know if that would change anything...

[Marc Quinton (mquinton)]

may be dupplicate of : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1021904 and solved by new kernel : 3.5 (quantal).

[penalvch (penalvch)]

Pascal Desroches, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]