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
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
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!
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: New = Invalid
--
NetworkManager can't find
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
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
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
** Changed in: network-manager (Ubuntu)
Assignee: Tollef Fog Heen
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
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
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 member of Ubuntu
Bugs, which is a
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
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
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
On Fri, Sep 28, 2007 at 07:52:19AM -, 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
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
have already included in your bug report.)
Best Regards,
System 76
- Original Message -
From: Alexander Sack [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 24, 2007 5:04:16 AM (GMT-0700) America/Denver
Subject: [Bug 45696] Re: NetworkManager can't find interface on resume
Yes, I had mentioned that about six months ago - sorry if I didn't do it
here!!
On 8/21/07, andy baxter [EMAIL PROTECTED] wrote:
Jonathan Amir wrote:
Same problem for me. Running on Thinkpad R60e, with Intel Corporation
PRO/Wireless 3945ABG. Feisty Kubuntu (with KNetworkManager, not nm-
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
Same problem for me. Running on Thinkpad R60e, with Intel Corporation
PRO/Wireless 3945ABG. Feisty Kubuntu (with KNetworkManager, not nm-
applet).
--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
You received this bug notification because you
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.
--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
You received
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)
** Attachment added: Terminal commands in relation
http://launchpadlibrarian.net/8453081/network-log
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
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
Carl,
Thanks. I will give this a try.
Adam
On 6/6/07, Carl Richell [EMAIL PROTECTED] 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
.
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
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
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
On Wed, May 23, 2007 at 05:18:54PM -, 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
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?
--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
You received this bug notification because you are
I'm really sorry, I postet to the wrong thread, please ignore/delete it.
--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
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.
--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
Same problem with THINKPAD X40. So far only on wired network.
sudo /etc/dbus-1/event.d/22dhcdbd restart
gets it going again
--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
You received this bug notification because you are a member of Ubuntu
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)
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
--
NetworkManager can't find interface on resume from suspend
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.
--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
You received
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.
--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
You received this bug notification
When you have this problem, try:
sudo /etc/dbus-1/event.d/22dhcdbd restart
Does this fix things for you?
Paulus
--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
You received this bug notification because you are a member of Ubuntu
Bugs, which
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?
--
NetworkManager can't find interface on resume from suspend
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.
--
NetworkManager can't find interface on resume
I will check next time is occurs.
-Jai
On Sat, 2007-04-28 at 08:05 +, Paulus Esterhazy wrote:
When you have this problem, try:
sudo /etc/dbus-1/event.d/22dhcdbd restart
Does this fix things for you?
Paulus
--
NetworkManager can't find interface on resume from suspend
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
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.
--
NetworkManager can't find interface
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.
--
NetworkManager can't find
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)
--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
You received this bug notification because you
Some more info here:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/99267
--
NetworkManager can't find interface on resume from suspend
https://bugs.launchpad.net/bugs/45696
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
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
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
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
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
--
NetworkManager can't find interface on resume from suspend
https://launchpad.net/bugs/45696
--
ubuntu-bugs mailing
** Changed in: network-manager (Ubuntu)
Target: 7.04-beta = ubuntu-7.04
--
NetworkManager can't find interface on resume from suspend
https://launchpad.net/bugs/45696
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Tollef Fog Heen
Target: None = 7.04-beta
--
NetworkManager can't find interface on resume from suspend
https://launchpad.net/bugs/45696
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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.
[EMAIL PROTECTED]:~/bin$ cat restartnm
#!/bin/sh
pkill NetworkManagerDispatcher
sudo pkill NetworkManager
sudo NetworkManager
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
Which wifi cards are you all using?
--
NetworkManager can't find interface on resume from suspend
https://launchpad.net/bugs/45696
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have a Intel Corporation PRO/Wireless 2915ABG Network Connection (rev
05) according to lspci.
--
NetworkManager can't find interface on resume from suspend
https://launchpad.net/bugs/45696
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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
--
NetworkManager can't find interface on resume from suspend
On Tue, Feb 27, 2007 at 12:16:35PM -, 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
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.
--
NetworkManager can't find interface on resume from suspend
https://launchpad.net/bugs/45696
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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.
--
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
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
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 PROTECTED] wrote:
Thanks for your report. Based on the
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
--
62 matches
Mail list logo
