NetworkManager can't find interface on resume from suspend

[IFRFlyer]

Often, after resuming from suspend, NetworkManager no longer recognizes any network interfaces. It logs the following messages when this happens:

Jan 23 04:51:13 localhost NetworkManager: <information>^IWaking up from sleep.
Jan 23 04:51:13 localhost NetworkManager: <WARNING>^I nm_add_initial_devices (): could not find existing networking devices:
The maximum number of pending replies per connection has been reached

[Kees Cook (kees)]

Thanks for your report. Based on the path you list, it doesn't sound like you were running the Ubuntu network-manager. Can you confirm the problems with the stock network-manager?

[IFRFlyer (nick-selby)]

Hi, Kees,
Actually I thought that I was - I don't remember having to install anything
special, but this has been six months. Can you point me at some info so I
can try the stock NM?

Thanks very much,
Nick

On 12/12/06, Kees Cook <email address hidden> wrote:
>
> Thanks for your report. Based on the path you list, it doesn't sound
> like you were running the Ubuntu network-manager. Can you confirm the
> problems with the stock network-manager?
>
> ** Changed in: Ubuntu
> Sourcepackagename: None => network-manager
> Status: Unconfirmed => Needs Info
>
> --
> NetworkManager can't find interface on resume from Suspend after update 19
> may
> https://launchpad.net/bugs/45696
>

[Matt Zimmerman (mdz)]

This happens to me all the time with the stock NetworkManager in edgy and feisty. The cause seems to be:

Jan 23 04:51:13 localhost NetworkManager: <WARNING>^I nm_add_initial_devices (): could not find existing networking devices:
The maximum number of pending replies per connection has been reached

[haaland (haaland)]

I had this happen yesterday. After killing all NetworkManager-related processes (NetworkManager, NetworkManagerDispatcher and nm-applet), and restarted them, things were back to normal. Using "/etc/init.d/netapplet restart", "/etc/init.d/networking restart" or simply killing and restarting "nm-applet" had no effect at all.

Note that it does not always happen, most of the time everything works as normal.

[Scott Garman (sgarman)]

I encounter this intermittently (but frequently) on Edgy as well. I'm running Edgy on a Sony VAIO S260 which uses the ipw2200 driver for wireless support. Using network-manager 0.6.3-2ubuntu6. It has happened both after resume from suspend to RAM as well as resume from hibernate.

[Matt Zimmerman (mdz)]

Restarting NetworkManager fixes this consistently for me, so I don't think it's a kernel issue. So far, the cause is not yet known.

[Soren Hansen (soren)]

Which wifi cards are you all using?

[Richard Hult (richard-imendio)]

I have a "Intel Corporation PRO/Wireless 2915ABG Network Connection (rev 05)" according to lspci.

[Soren Hansen (soren)]

Ok, just to make sure: Is anyone experiencing this with something other than ipw2200 cards on Edgy?
I.e. either:
1) Edgy system with a wifi card that doesn't use ipw2200
or
2) Feisty system with any wifi card

[Matt Zimmerman (mdz)]

On Tue, Feb 27, 2007 at 12:16:35PM -0000, Soren Hansen wrote:
> Ok, just to make sure: Is anyone experiencing this with something other than ipw2200 cards on Edgy?
> I.e. either:
> 1) Edgy system with a wifi card that doesn't use ipw2200
> or
> 2) Feisty system with any wifi card

I've experienced it on Feisty with an ipw2200, though I haven't been
successful at reproducing it when I try.

--
 - mdz

[Carsten Schnober (c-schnober)]

In my laptop system with one wifi card (ipw2200) and one ethernet card (both built in), I think the problem is caused by changing interface names: After system boot, the network devices are named eth2 and eth3, eth0 and eth1 don't exist. Network Manager works.
After a suspend, the devices are called eth0 and eth1, so Network Manager doesn't find them anymore. I can still configure the renamed devices using ifconfig and iwconfig.
Restarting Network Manager doesn't have any effect.
The packages network-manager and network-manager-gnome don't contain init scripts at all, btw. Therefore I can restart Network Manager only by killing and restarting the processes manually.
The problem may be related to Udev, I suppose.

[Brian Pitts (bpitts)]

I experience the same behavior and log messages on a Powerbook G4 running edgy. This has a Broadcom wifi card. I run the following script when it happens.

brian@powerbook:~/bin$ cat restartnm
#!/bin/sh
pkill NetworkManagerDispatcher
sudo pkill NetworkManager
sudo NetworkManager
NetworkManagerDispatcher

[Paul Sladen (sladen)]

My report at bug #93535 is similar, though with the message:

  NetworkManager: <WARNING>^I nm_device_802_11_wireless_get_mode (): error getting card mode on eth1: No such device

[Wesley Stessens (wesley)]

I have the same problem. I am running Feisty. My wireless chipset is atheros (ath_pci)

Here is a part of my syslog:

Mar 22 17:01:54 eza NetworkManager: <debug info>^I[1174579314.308979] nm_hal_dev
ice_removed (): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_dev
ice_46d_c03e_noserial_if0').
Mar 22 17:01:54 eza NetworkManager: <debug info>^I[1174579314.326209] nm_hal_dev
ice_removed (): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_dev
ice_46d_c03e_noserial').
Mar 22 17:01:54 eza NetworkManager: <debug info>^I[1174579314.654429] nm_hal_dev
ice_removed (): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_dev
ice_46d_c03e_noserial_if0_logicaldev_input').
Mar 22 17:01:54 eza NetworkManager: <information>^IWaking up from sleep.
Mar 22 17:01:54 eza NetworkManager: <WARNING>^I nm_add_initial_devices (): could
 not find existing networking devices: The maximum number of pending replies per
 connection has been reached

Note that my wireless connection works even though network-manager doesn't handle it after resume

Also, the dbus restart trick works for me too.

[Jonathan Hunt (jjh)]

Hi,

Just to let you know I'm running Feisty (herd 5) on a Dell D610. Using a wired network I get similar problems (the network often fails to get a IP address from DHCP after resume if the lease has expired).

Restarting the computer causes it to successfully get a IP address.

Also, it is not a problem with kernel modules. When NetworkManager fails to get an address, I can disable it, go to command line and
$ sudo su
$dhclient3 eth0
and my computer will be on the network no worries.

Let me know if you want more info about my system.

[Eugenia Loli-Queru (eloli)]

Some more info here:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/99267

[Eugenia Loli-Queru (eloli)]

Oops, sorry, I linked to the wrong bug above. Here is the right bug report:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/93576

Please try to fix this bug, it happens on 2 of my 3 laptops with Feisty. It is easily reproducible here after you sleep/wake-up a laptop about 5-6 times in a row. IMO, this bug should be upgraded to "high" because it seems a lot of people have it.

[Marco (mfj)]

I have same bug with my laptop Fujitsu-Siemens Amilo V3205 Pro.
At the resume also don't work touchpad (problem that I have reported: bug #102400)

[Paulus (donmatteo)]

I have the same problem as Jonathan Hunt above (which may or may not be related to the original report). Waking up from hibernation, network-manager fails to get a DHCP address. This is a simple wired ethernet (via-rhine), and already reported as bug 102716.

[Richard Guo (rfguo)]

I have the same problem on feisty running ipw2200. This never happened to me on edgy. After I resume from a suspend to ram, knetworkmanager does not detect any devices. Quitting and restarting does not work. Quitting, resuspending, and resuming does work.

[Ohb01 (ohb01)]

I have the same problem with a fully updated Ubuntu Feisty on a Desktop (DELL Dimension 4700). I'm trying to use Hibernate or Suspend as they save energy (compared to leaving the computer on) and time (compared to a full shut-down/restart). Not being able to use the network half the time after Resume from Hibernate/Suspend is a serious usability issue for me.

I'm sorry to say that I'd never had this problem with Windows XP Pro or XP Media Center Edition. I also don't remember this problem with Ubuntu Edgy. The network was just re-detected immediately. Feisty risks being perceived as not environmentally-friendly if it cannot handle Hibernate/Suspend properly.

With Feisty, it sometimes helps to use System > Administration > Network > Configure, and change the Wired Connection > Properties from DHCP to Local Zeroconf, and then back to DHCP again. But other times, it does not help.

I have the following WIRED Ethernet card: Intel Corporation, Device: 82562ET/EZ/GT/GZ - PRO/100 VE (LOM). Network device: eth0
Hardware address: 00:13:20:0e:ce:fb. I use DHCP networking via my wired router.

Background: Suspend or Hibernate only work when I use the open-source ati video driver, not the closed-source one that the Update Manager recommended after upgrading to Feisty. I'm not sure if it's related, but I'm mentioning this just in case.

Thanks in advance for your prompt attention to this matter.

[Paulus (donmatteo)]

When you have this problem, try:

sudo /etc/dbus-1/event.d/22dhcdbd restart

Does this fix things for you?

Paulus

[Oliver Gerlich (ogerlich)]

In my case, it was sufficient to left-click on network-manager icon and select Cable Network again... it then re-requested an IP and succeeded (see Bug #105251). Does this help in your case as well?

[Jojo (kuzniarpawel)]

In my case I had to:
1) ifconfig eth0 down
2) dhclient eth0

Without turning of eth0 first running dhclient resulted in successful ip renew from dhcp-server but network was not working.

Turning off/on network in Network Manager wasn't helpful.

[Jai Singh (i922sparkcir)]

I will check next time is occurs.

-Jai

On Sat, 2007-04-28 at 08:05 +0000, Paulus Esterhazy wrote:
> When you have this problem, try:
>
> sudo /etc/dbus-1/event.d/22dhcdbd restart
>
> Does this fix things for you?
>
> Paulus
>

[tomaszr (tomasz-rosinski)]

In my notebook too. Acer Travel Mate 2423 with Atheros card.
After suspend/resume not work dhcp correctly and NetworkManager all time search the network.

[Brian Pitts (bpitts)]

The same error condition (no network devices found) sometimes occurs for me on a Dell Inspiron 600M after I disable and reenable NetworkManager by right-clicking nm-applet.

The network hardware is
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet (rev 02)
02:03.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)

[Jai Singh (i922sparkcir)]

> When you have this problem, try:
>
> sudo /etc/dbus-1/event.d/22dhcdbd restart
>
> Does this fix things for you?

This does solve the problem, and is far better than just restarting
dbus. Thank You,

- Jai

[Paulus (donmatteo)]

> This does solve the problem, and is far better than just restarting
> dbus. Thank You,

Jai, then your problem (though not necessarily everyone else's) is a
dupliacate of bug #88327.

[philly (phburks)]

I was having this same problem with Edgy where after 2 or 3 suspend/resume cycles Network Manager would not recognize my network interfaces (using a notebook with built-in intel wireless). I was also using Beagle for my desktop search. I don't know why, but when I killed the beagled process my problems with Network Manager disappeared. Every suspend/resume cycle worked flawlessly, with Network Manager reconnecting on every single resume. Not wanting to lose my desktop search, I removed Beagle and replaced it with Tracker, which also integrates with the Deskbar Applet. I had no more problems with Network Manager not resuming after that.

For whatever that is worth, there it is. I can't explain why it worked, but it did.

[Matt Zimmerman (mdz)]

On Fri, May 04, 2007 at 11:48:51AM -0000, philly wrote:
> I was having this same problem with Edgy where after 2 or 3
> suspend/resume cycles Network Manager would not recognize my network
> interfaces (using a notebook with built-in intel wireless). I was also
> using Beagle for my desktop search. I don't know why, but when I killed
> the beagled process my problems with Network Manager disappeared.

This is probably coincidental; plenty of folks are having similar problems
with Network Manager without using Beagle.

--
 - mdz

[David A. Benitez (dbenitez)]

I have a Dell Latitude C610 using a Linksys Wireless card (using the ndiswrapper driver). The card would automatically reconnect successfully in Edgy; in Feisty it will occasionally _not_ reconnect after resuming from a suspend to RAM session when closing the lid.

Information about my Wireless Card:
03:00.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

Are there any other tests that I should run to figure out if I have this problem or an altogether different problem?

[Kuropka (d2)]

Similar problem here on my Samsung Q20: Wired network interfaces always does not work after waking up from suspend to RAM, Wireless network interfaces sometimes also stop working after wake up.

[vkoch (volga-kotsch)]

Same problem with THINKPAD X40. So far only on wired network.
sudo /etc/dbus-1/event.d/22dhcdbd restart
gets it going again

[TS (thomas-schwarzl)]

Same USB problem with Thinkpad T30 on Feisty Beta and Ubuntu Studio but networking works fine for me.
How can the USB problem be fixed please?

[TS (thomas-schwarzl)]

I'm really sorry, I postet to the wrong thread, please ignore/delete it.

[David A. Benitez (dbenitez)]

What is the status of this bug for those who are currently working on it?

Can we do anything to help (i.e., run some tests, send log files, etc.)? If so, please describe in detail what tests we should run to expedite this.

I'm sorry if I sound impatient but I kinda miss my wireless. I am making due with wired. :-P

[Matt Zimmerman (mdz)]

On Wed, May 23, 2007 at 06:26:39AM -0000, David A. Benitez wrote:
> What is the status of this bug for those who are currently working on
> it?

I think it is a duplicate of bug 40125, so it would be helpful if you could
try the workaround posted there.

--
 - mdz

[Ohb01 (ohb01)]

Thanks, but I'm a bit confused: the discussion of bug 40125 seems to include different workarounds. Also, some of the comments propose further variations. A direct link (permalink?) to the workaround(s) that you mean, plus specific implementation comments, would be great. Thanks in advance for your help.

[Matt Zimmerman (mdz)]

On Wed, May 23, 2007 at 05:18:54PM -0000, Ohbother01 wrote:
> Thanks, but I'm a bit confused: the discussion of bug 40125 seems to
> include different workarounds. Also, some of the comments propose
> further variations. A direct link (permalink?) to the workaround(s) that
> you mean, plus specific implementation comments, would be great. Thanks
> in advance for your help.

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/40125/comments/74

--
 - mdz

[David A. Benitez (dbenitez)]

Please see the attached link to read my description for the attempted fix.

https://bugs.launchpad.net/ubuntu/feisty/+source/network-manager/+bug/40125/comments/88

Please contact me if you require me to run additional tests or attachments of any needed files.

[vkoch (volga-kotsch)]

I made the recommended changes to /etc/dbus-1/system.d/Networkmanager.conf
After that I did
/etc/dbus-1/event.d/25NetworkManager restart
/etc/dbus-1/event.d/26NetworkManagerDispatch restart

Still problem after several suspends with my Thinkpad x40 on wired network.
Just discovered that there is also a file /etc/dbus-1/system.d/knetworkmanager.conf
which looks pretty much like Networkmanager.conf. Since I am on kubuntu, maybe this is the relevant file to patch as well. I will try to add the same line to this file and see if it helps
Will report back

[Carl Richell (carlrichell)]

Doesn't make a lot of sense but this has fixed the problem on my notebook - IPW 3945

sudo nano /etc/acpi/resume.d/60-asus-wireless-led.sh

switch the 0 and 1 so the file reads:

#!/bin/sh
. /usr/share/acpi-support/state-funcs
if isAnyWirelessPoweredOn ; then
    setLEDAsusWireless 0
else
    setLEDAsusWireless 1
fi

maybe the source of the problem is in /usr/share/acpi-support/state-funcs

[Adam York (aaylnx)]

Carl,

Thanks. I will give this a try.

Adam

On 6/6/07, Carl Richell <email address hidden> wrote:
>
> Doesn't make a lot of sense but this has fixed the problem on my
> notebook - IPW 3945
>
> sudo nano /etc/acpi/resume.d/60-asus-wireless-led.sh
>
> switch the 0 and 1 so the file reads:
>
> #!/bin/sh
> . /usr/share/acpi-support/state-funcs
> if isAnyWirelessPoweredOn ; then
> setLEDAsusWireless 0
> else
> setLEDAsusWireless 1
> fi
>
> maybe the source of the problem is in /usr/share/acpi-support/state-
> funcs
>
> --
> NetworkManager can't find interface on resume from suspend
> https://bugs.launchpad.net/bugs/45696
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

[Adam York (aaylnx)]

Carl,

I've confirmed that this change fixes the wireless resume problem for both
hibernate and suspend on my Gazelle Pro. Yeah!!!!

I'd say that this is something to be rolled into the next version of the
System76 driver. I don't know if the other laptops need it, but it
certainly appears that the Gazelle Pro does.

Adam

On 6/7/07, Adam York <email address hidden> wrote:
>
> Carl,
>
> Thanks. I will give this a try.
>
> Adam
>
> On 6/6/07, Carl Richell <email address hidden> wrote:
> >
> > Doesn't make a lot of sense but this has fixed the problem on my
> > notebook - IPW 3945
> >
> > sudo nano /etc/acpi/resume.d/60-asus-wireless-led.sh
> >
> > switch the 0 and 1 so the file reads:
> >
> > #!/bin/sh
> > . /usr/share/acpi-support/state-funcs
> > if isAnyWirelessPoweredOn ; then
> > setLEDAsusWireless 0
> > else
> > setLEDAsusWireless 1
> > fi
> >
> > maybe the source of the problem is in /usr/share/acpi-support/state-
> > funcs
> >
> > --
> > NetworkManager can't find interface on resume from suspend
> > https://bugs.launchpad.net/bugs/45696
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
>
>

[vkoch (volga-kotsch)]

As announced previously added extra line also to
/etc/dbus-1/system.d/knetworkmanager.conf
since I am on Kubuntu.
Problem persists with wired network

[Thomas de Graaff (thomasdegraaff)]

My computer with Xubuntu feisty had a problem with getting an ip-adress after waking from hibernation. I´ve solved this problem by changing /etc/default/acpi-support

Editing this file, look for the line below, where to add [networking] after that no problems anymore:

# Add services to this list to stop them before suspend and restart them in
# the resume process.
STOP_SERVICES="networking"

Hope this will work for you to,
Thomas.

[David A. Benitez (dbenitez)]

I have added the specified line as the above post on the required file but I still cannot get my Linksys card with the Broadcom chipset to work.

I am currently using my local library's open wireless network to try to access it; however, it could not access it.

Has anyone else verified that his fixed works for them???

[Ohb01 (ohb01)]

I've tried the fix suggested by Matt Zimmerman on 2007-05-23 (see https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/45696/comments/40 ), but unfortunately, it does not seem to help, at least not completely. I'm still getting the occasional lack of networking after resuming from Hibernate. (A bit less frequently, perhaps?.. It's a bit hard top tell because the original problem had been intermittent as well. Sorry about not keeping better statistics.).

Moreover, when resuming from Suspend (not Hibernate), my computer just hangs sometimes, with a blinking white cursor at the top left of a black screen. Restarting with Ctrl-Alt-Del only gets me as far as the GNOME "Loading Desktop" splash screen before there is another freeze-up. Everything finally clears up after I restart X by doing Ctrl-Alt-Backspace. (The networking also seems to start working at that point.)

Note: restarting X does not seem to help restore networking after resuming from Hibernate. It does sometimes help to use System > Administration > Network > Configure, and change the Wired Connection > Properties from DHCP to Local Zeroconf, and then back to DHCP again. This seems to work more consistently now than before I had tried the fix.

To recap, I am using Ubuntu Feisty (fully updated) on a Desktop (DELL Dimension 4700). I have the following WIRED Ethernet card: Intel Corporation, Device: 82562ET/EZ/GT/GZ - PRO/100 VE (LOM). Network device: eth0. Hardware address: 00:13:20:0e:ce:fb. I use DHCP networking via my wired router. (Suspend or Hibernate only work when I use the open-source ati video driver, not the closed-source one that the Update Manager had recommended after upgrading to Feisty. I'm not sure if it's related, but I'm mentioning this just in case.)

Many thanks to everyone who is working on this issue. I really appreciate your efforts, and I'm sure that a solution will be found.

[Serge (contact-inpagina)]

Same problem for me.

Solutions proposed here didn't help me. :(
Network interface eth0 become invariably eth1 after resume and network is down until restart of the system.
(Asus M2NPV-VM)

[andy baxter (andy-earthsong)]

Just to let people know I have the same problem. I'm using feisty on a dell inspiron 2650.

sudo -i
ifdown eth0 && ifup eth0

fixes it, once I've disabled the network manager applet.

[Jonathan Amir (jonathan-amir)]

Same problem for me. Running on Thinkpad R60e, with "Intel Corporation PRO/Wireless 3945ABG". Feisty Kubuntu (with KNetworkManager, not nm-applet).

[andy baxter (andy-earthsong)]

Jonathan Amir wrote:
> Same problem for me. Running on Thinkpad R60e, with "Intel Corporation
> PRO/Wireless 3945ABG". Feisty Kubuntu (with KNetworkManager, not nm-
> applet).
>
>
I just found out that it seems to work better if you remember to disable
networking before you do the suspend. I.e. right click on the applet and
deselect 'enable networking'. It automatically reconnects when you wake
up the system.

andy.

[IFRFlyer (nick-selby)]

Yes, I had mentioned that about six months ago - sorry if I didn't do it
here!!

On 8/21/07, andy baxter <email address hidden> wrote:
>
> Jonathan Amir wrote:
> > Same problem for me. Running on Thinkpad R60e, with "Intel Corporation
> > PRO/Wireless 3945ABG". Feisty Kubuntu (with KNetworkManager, not nm-
> > applet).
> >
> >
> I just found out that it seems to work better if you remember to disable
> networking before you do the suspend. I.e. right click on the applet and
> deselect 'enable networking'. It automatically reconnects when you wake
> up the system.
>
> andy.
>
> --
> NetworkManager can't find interface on resume from suspend
> https://bugs.launchpad.net/bugs/45696
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Alexander Sack (asac)]

chances are high that this is fixed in latest gutsy network-manager (0.6.5-0ubuntu14) ... please test the wpasupplicant mentioned in http://ubuntuforums.org/showthread.php?t=556488 as well.

Thanks,

 - Alexander

[Thomas Aaron (tom-system76)]

Hi, Alexander.

When filing bugs, please include The model of your machine and instructions for re-creating the problem. Please also include the Ubuntu version you are using and whether you use Ubuntu, Kubuntu, Xubuntu, etc...

(This response is a template. Please disregard aspects of it that you have already included in your bug report.)

Best Regards,
System 76

----- Original Message -----
From: "Alexander Sack" <email address hidden>
To: <email address hidden>
Sent: Monday, September 24, 2007 5:04:16 AM (GMT-0700) America/Denver
Subject: [Bug 45696] Re: NetworkManager can't find interface on resume from suspend

chances are high that this is fixed in latest gutsy network-manager
(0.6.5-0ubuntu14) ... please test the wpasupplicant mentioned in
http://ubuntuforums.org/showthread.php?t=556488 as well.

Thanks,

 - Alexander

--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
You received this bug notification because you are a direct subscriber
of a duplicate bug.

[Olivier Cortès (olive)]

Hi. Here on latest Gusty the problem persists. Resuming from suspend to ram, NM-applet says "no network adapter detected". Manually restarting NM don't totally work :

sudo /etc/dbus-1/event.d/26NetworkManagerDispatcher stop
sudo /etc/dbus-1/event.d/25NetworkManager stop
[hangs ; i must "sudo killall -9 NetworkManager", kill -15 doesn't work]
sudo /etc/dbus-1/event.d/25NetworkManager start
sudo /etc/dbus-1/event.d/26NetworkManagerDispatcher start

then nm-applet shows the network again (wifi AND wired). Note that before doing that, i "sudo dhclient eth0" to bring the wired adapter back up, else ifconfig doesn't even show it (this could be another bug).

My system is a notebook Dell Precision M4300, dmesg attached.

[Matt Zimmerman (mdz)]

On Fri, Sep 28, 2007 at 07:52:19AM -0000, Olivier Cortès wrote:
> Hi. Here on latest Gusty the problem persists. Resuming from suspend to
> ram, NM-applet says "no network adapter detected". Manually restarting
> NM don't totally work :

I haven't seen this problem in ages; yours may be a different one.

--
 - mdz

[Olivier Cortès (olive)]

Hi. I never tested suspend/resume on my dell notebook until yesterday night. I found "no network adapter" message after each resume cycle, even between reboots (i tested 3 times). I'm on Gutsy x86_64. I agree this could be another bug, but restarting eth0 manually and restarting NM resolves the issue, it *seems* to be highly related... Is there any more information I can provide to try to hunt a little more ?

here is the start of my /var/log/syslog (just after resume) :

Sep 28 09:34:22 Kynes syslogd 1.4.1#21ubuntu3: restart.
Sep 28 09:34:41 Kynes NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '$'
Sep 28 09:34:41 Kynes NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Transport endpoint is not connected
Sep 28 09:35:01 Kynes NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '$'
Sep 28 09:35:01 Kynes NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Transport endpoint is not connected
Sep 28 09:35:21 Kynes NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '$'
Sep 28 09:35:21 Kynes NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Transport endpoint is not connected
Sep 28 09:35:41 Kynes NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '$'
Sep 28 09:35:41 Kynes NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Transport endpoint is not connected
Sep 28 09:36:01 Kynes NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '$'
Sep 28 09:36:01 Kynes NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Transport endpoint is not connected
Sep 28 09:36:21 Kynes NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '$'
Sep 28 09:36:21 Kynes NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Transport endpoint is not connected
Sep 28 09:36:41 Kynes NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '$'
Sep 28 09:36:41 Kynes NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Transport endpoint is not connected
Sep 28 09:37:01 Kynes NetworkManager: <WARN> nm_utils_supplicant_request_with_check(): nm_device_802_11_wireless_scan: supplicant error for 'SCAN'. Response: '$'
Sep 28 09:37:01 Kynes NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device wlan0: Transport endpoint is not connected
Sep 28 09:37:21 Kyn...

[Rodrigo Pinheiro (ametade)]

I'm having the same problem with Network Manager at Gutsy as Olivier. I always get the "no network adapter" message at Network Manager applet, even when I restart the laptop. I can only get NM working if I use the commands Olivier explained before:

sudo /etc/dbus-1/event.d/26NetworkManagerDispatcher stop
sudo /etc/dbus-1/event.d/25NetworkManager stop
[hangs ; i must "sudo killall -9 NetworkManager", kill -15 doesn't work]
sudo /etc/dbus-1/event.d/25NetworkManager start

[Kareem Kenawy (thesamo)]

When I resume from suspend2ram, WiFi connectivity is always lost and sometime networkmanager crashes.

I up the interface eth1(my wifi device) from ifconfig And try "iwlist scan" but it claims eth1 does not support scanning.

I have wifi device Intel Corporation PRO/Wireless 3945ABG Network Connection.

I haven't tested wired network yet.

[Alexander Sack (asac)]

So restarting network manager helps? Isn't NetworkManager restarted for you when resuming from suspend?

[Kareem Kenawy (thesamo)]

I don't know how to restart Networkmanager propably, but i tried a
/etc/init.d/networking restart.

I don't think it's restarted. But anyways Andy Baxter sent me a workaround
that actually works. If you disable Networking from nm-applet before
suspend, and re-enable it on resume, all connectivity is resumed.
I do

On 10/1/07, Alexander Sack <email address hidden> wrote:
>
> So restarting network manager helps? Isn't NetworkManager restarted for
> you when resuming from suspend?
>
> --
> NetworkManager can't find interface on resume from suspend
> https://bugs.launchpad.net/bugs/45696
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
-theSamo

[Olivier Cortès (olive)]

Hi,

just to confirm that disabling networking in NM-applet before suspend, and re-enabling it after resume does perfectly the job and completely solves the problem for me (tested 3 times), wired or not. Still annoying to have to do this, and other machines (thinking of my old IBM T40p) worked without this. Isn't there a way (a /etc/power or /etc/acpi script) to do this automatically on suspend/resume ?

[Alexander Sack (asac)]

we have seen improvements in this area. I know that some chipsets still have this issue, so If you still see it, please open a _new_ bug, note your chipset and refer to this bug in your bugreport.

Thanks,

 - Alexander

[Leann Ogasawara (leannogasawara)]

I'm marking this as 'Invalid' against the linux-source-2.6.20 package as this bug really applies to the network-manager package and has been marked 'Fix Released' accordingly. Thanks!

[Ohb01 (ohb01)]

Thanks to everyone for all the info. I'm a bit confused about this issue being marked "Fix Released" though. Alexander Sack wrote (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/45696/comments/65) about seeing some improvements. I'm not clear what these improvements were. Reading the other comments above, it sounds like people keep having to use workarounds, e.g. disabling and re-enabling networking manually. Some people were even having this issue in Gutsy. That doesn't sound like the issue is really "fixed" IMHO.

I still have this problem, too, occasionally, with the same chipset, WIRED Ethernet card: Intel Corporation, Device: 82562ET/EZ/GT/GZ - PRO/100 VE (LOM). Network device: eth0, Hardware address: 00:13:20:0e:ce:fb. I use DHCP networking via my wired router. I still have the same version of Ubuntu (Feisty) as before. Update Manager has so far failed in to upgrade to Gutsy, but that's -- hopefully -- a different issue.

Getting back to network manager, should I open a new bug for the same problem? --Or is Feisty not supported anymore at all now that Gutsy is out, regardless of people who have not been able to upgrade? Thanks in advance for clarifying the process.

[Leann Ogasawara (leannogasawara)]

Hi Ohb01,

As detailed in the activity log:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/45696/+activity

This bug was marked 'Fixed Released' by Alexander back on Oct 4, 2007. As he mentioned, if you are still seeing issues, please open a new bug noting your chipset and reference this bug.

Feisty is still supported, however I'm not sure a fix for this bug would meet the criteria for a stable release update. To find out more information regarding the stable release update process please refer to:

https://wiki.ubuntu.com/StableReleaseUpdates

Since the 7.10 Gutsy Gibbon has been released it would be good to know if this is still an issue in the new release. This can be done with the live environment of the Desktop CD. If you could download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download and report back your results it would be very much appreciated. Thanks!

[fearghalcanning (fearghal-canning)]

I installed Gutsy today on my Dell Inspiron 6400 with the broadcom wireless ethernet. I suspended the session and on resuming the session all interfaces had been lost. This is the first time I have attempted this in Gutsy and I had to use the work around as Olivier. Thanks for the advice Olivier btw.
Details for my card are:
BCM94311MCG wlan mini-PCI
On a full reboot all works ok but not when coming back from suspend.
Guys, we really need some action on this. This is one of the few things that really makes this difficult to 'sell' the average user. I mean I can't see my Dad running some command line code to fix this.
Other than the odd error here and there I am totally sold on this update.
Keep up the good work...