| 2007-02-02 20:45:08 |
jerrylamos |
bug |
|
|
added bug |
| 2007-02-02 20:57:05 |
Simon Law |
None: status |
Unconfirmed |
Needs Info |
|
| 2007-02-02 20:57:05 |
Simon Law |
None: assignee |
|
sfllaw |
|
| 2007-02-02 20:57:05 |
Simon Law |
None: statusexplanation |
|
Hello.
Could you reproduce this problem again and list your exact reproduction steps? Try not to work around the problem before you capture the following information:
1. A copy of /var/log/syslog, which should have entries from NetworkManager
2. The output of /sbin/ifconfig -a
3. The output of lspci -vvn
Thanks! |
|
| 2007-02-05 20:05:16 |
jerrylamos |
bug |
|
|
added attachment 'log' (/var/syslog from boot "no network connection") |
| 2007-02-05 20:07:19 |
jerrylamos |
bug |
|
|
added attachment 'conf' (output of ifconfig network manager says no connection) |
| 2007-02-05 20:08:47 |
jerrylamos |
bug |
|
|
added attachment 'lsp' (lspci -vvn from no network connection) |
| 2007-02-05 21:25:27 |
Simon Law |
network-manager: status |
Needs Info |
Confirmed |
|
| 2007-02-05 21:25:27 |
Simon Law |
network-manager: importance |
Undecided |
Medium |
|
| 2007-02-05 21:25:27 |
Simon Law |
network-manager: statusexplanation |
Hello.
Could you reproduce this problem again and list your exact reproduction steps? Try not to work around the problem before you capture the following information:
1. A copy of /var/log/syslog, which should have entries from NetworkManager
2. The output of /sbin/ifconfig -a
3. The output of lspci -vvn
Thanks! |
This is a problem with the ne2k-pci driver, for which NetworkManager claims:
Feb 3 21:50:36 ubuntu NetworkManager: <information>^Ieth0: Driver 'ne2k-pci' does not support carrier detection. ^IYou must switch to it manually.
A workaround is to not use NetworkManager and let ifupdown deal with the DHCP. This is done by having:
auto eth0
iface eth0 inet dhcp
lines in /etc/network/interfaces.
|
|
| 2007-02-05 21:25:27 |
Simon Law |
network-manager: assignee |
sfllaw |
|
|
| 2007-02-06 03:29:41 |
jerrylamos |
bug |
|
|
added attachment 'log-wconf-lspc' (/var/log/syslog ifconfig lspci -vvn) |
| 2007-02-08 20:37:27 |
Ben Collins |
linux-source-2.6.20: statusexplanation |
This is a problem with the ne2k-pci driver, for which NetworkManager claims:
Feb 3 21:50:36 ubuntu NetworkManager: <information>^Ieth0: Driver 'ne2k-pci' does not support carrier detection. ^IYou must switch to it manually.
A workaround is to not use NetworkManager and let ifupdown deal with the DHCP. This is done by having:
auto eth0
iface eth0 inet dhcp
lines in /etc/network/interfaces.
|
Ok, then, this is a bug in n-m. |
|
| 2007-03-03 09:14:44 |
Mantas Kriaučiūnas |
bug |
|
|
assigned to network-manager (Baltix) |
| 2007-03-15 22:09:33 |
Mathias Hasselmann |
bug |
|
|
assigned to network-manager (upstream) |
| 2007-03-15 22:20:36 |
Chris Wagner |
title |
feisty fawn no network connection |
[feisty fawn] NetworkManager reports incorrect online status |
|
| 2007-03-16 07:32:50 |
Bug Watch Updater |
network-manager: status |
Unknown |
Unconfirmed |
|
| 2007-03-17 21:19:06 |
jerrylamos |
description |
feisty fawn herd 3 download 1 February 2007
After bootup there was a message about a crash, apparently "add/remove" program?
Going on:
Network manager icon on top line, right side just before speaker volume says:
"No Network Connection"
After booted from Live CD, ifconfig did not return an IP. Ping the gateway didn't work.
Network DNS showed IP's from my gateway and from the DSL nameserver, so during boot CDLive did in fact get out on the internet.
From terminal I issued:
dhcp
which then got an ip address, and ping the gateway worked. Firefox connected to ubuntu hence I'm writing this entry.
Network Manager still says "no connection" which is not correct which is a bug since I'm making this entry through the connection. |
Description edited 3/17/07 by Jerry Amos, originator:
1. Hardware and ethernet card run fine on Dapper and Edgy and other Linux distros and Windows.
2. Feisty has Network manager standard. After bootup, Network manager says: "No Network connection" and indeed Firefox can't find the internet.
3. Issue "sudo dhclient" as per Official Ubuntu Book p.211, eth0 comes up and Firefox runs fine.
Bug #1. However, Network Manager still says "no network connection" even though there is a connection.
4. I didn't understand why there was no connection after bootup, so looking thru the syslog and networking, I see during boot Ubuntu establishes the network connection and finds the gateway and the nameserver out on the internet so eth0 is functioning fine.
Bug #2. Then Network manager decides the Realtek ethernet card (which is already running), "does not support carrier detect" and disables eth0. That's the second bug, Network manager should not disable a perfectly functioning eth0.
If the Ubuntu goal is for the "ordinary computer desktop user" to "just run", then Network manager is in this case impeding the goal. My view as a user, anyway. Jerry |
|
| 2007-04-13 16:40:13 |
Martin Pitt |
network-manager: status |
Confirmed |
Fix Released |
|
| 2007-04-13 16:40:13 |
Martin Pitt |
network-manager: statusexplanation |
Ok, then, this is a bug in n-m. |
This should have been fixed in
network-manager (0.6.4-6ubuntu7) feisty; urgency=low
* 21_manual_means_always_online.diff:
The previous version of this patch (ubuntu5) made a change to nm-applet
that would assume the state was disconnected if the device list was empty.
This didn't work since the device list is always empty on start because
the status is obtained first.
This was guarding against having the connected state with no devices,
which broke later assertions. Change the patch to correct those
assertions instead; a connected state with no active device will now
display the wired icon with a "Manual network configuration" tooltip.
LP: #82335, #105234.
* 05-debian_backend.patch:
Revert change in ubuntu3 that commented out the blacklisting of
devices listed in /etc/network/interfaces with more exotic configuration
than just inet dhcp. This was done by the above patch in ubuntu5, it
seems silly to do it there, better to do it in the original patch.
* 22_manual_config_available_when_connected.patch:
Display the "Manual configuration" menu option when we have no devices,
but are connected; since that means some number of blacklisted devices
exist. Don't display the "No network devices" message in that case.
-- Scott James Remnant <scott@ubuntu.com> Thu, 12 Apr 2007 19:32:01 +0100
Please report back if you still have this problem with this version. |
|
| 2007-09-05 22:06:10 |
Stéphane Graber |
description |
Description edited 3/17/07 by Jerry Amos, originator:
1. Hardware and ethernet card run fine on Dapper and Edgy and other Linux distros and Windows.
2. Feisty has Network manager standard. After bootup, Network manager says: "No Network connection" and indeed Firefox can't find the internet.
3. Issue "sudo dhclient" as per Official Ubuntu Book p.211, eth0 comes up and Firefox runs fine.
Bug #1. However, Network Manager still says "no network connection" even though there is a connection.
4. I didn't understand why there was no connection after bootup, so looking thru the syslog and networking, I see during boot Ubuntu establishes the network connection and finds the gateway and the nameserver out on the internet so eth0 is functioning fine.
Bug #2. Then Network manager decides the Realtek ethernet card (which is already running), "does not support carrier detect" and disables eth0. That's the second bug, Network manager should not disable a perfectly functioning eth0.
If the Ubuntu goal is for the "ordinary computer desktop user" to "just run", then Network manager is in this case impeding the goal. My view as a user, anyway. Jerry |
Description edited 3/17/07 by Jerry Amos, originator:
1. Hardware and ethernet card run fine on Dapper and Edgy and other Linux distros and Windows.
2. Feisty has Network manager standard. After bootup, Network manager says: "No Network connection" and indeed Firefox can't find the internet.
3. Issue "sudo dhclient" as per Official Ubuntu Book p.211, eth0 comes up and Firefox runs fine.
Bug #1. However, Network Manager still says "no network connection" even though there is a connection.
4. I didn't understand why there was no connection after bootup, so looking thru the syslog and networking, I see during boot Ubuntu establishes the network connection and finds the gateway and the nameserver out on the internet so eth0 is functioning fine.
Bug #2. Then Network manager decides the Realtek ethernet card (which is already running), "does not support carrier detect" and disables eth0. That's the second bug, Network manager should not disable a perfectly functioning eth0.
If the Ubuntu goal is for the "ordinary computer desktop user" to "just run", then Network manager is in this case impeding the goal. My view as a user, anyway. Jerry |
|
| 2007-10-17 06:37:49 |
jhansonxi |
bug |
|
|
added attachment 'syslog_CUV-NT.bz2' (syslog) |
| 2007-10-19 01:53:59 |
jerrylamos |
description |
Description edited 3/17/07 by Jerry Amos, originator:
1. Hardware and ethernet card run fine on Dapper and Edgy and other Linux distros and Windows.
2. Feisty has Network manager standard. After bootup, Network manager says: "No Network connection" and indeed Firefox can't find the internet.
3. Issue "sudo dhclient" as per Official Ubuntu Book p.211, eth0 comes up and Firefox runs fine.
Bug #1. However, Network Manager still says "no network connection" even though there is a connection.
4. I didn't understand why there was no connection after bootup, so looking thru the syslog and networking, I see during boot Ubuntu establishes the network connection and finds the gateway and the nameserver out on the internet so eth0 is functioning fine.
Bug #2. Then Network manager decides the Realtek ethernet card (which is already running), "does not support carrier detect" and disables eth0. That's the second bug, Network manager should not disable a perfectly functioning eth0.
If the Ubuntu goal is for the "ordinary computer desktop user" to "just run", then Network manager is in this case impeding the goal. My view as a user, anyway. Jerry |
Description edited 3/17/07 by Jerry Amos, originator:
1. Hardware and ethernet card run fine on Dapper and Edgy and other Linux distros and Windows.
2. Feisty and Gutsy have Network manager standard. After bootup, Network manager says: "No Network connection" and indeed Firefox can't find the internet.
3. Issue "sudo dhclient" as per Official Ubuntu Book p.211, eth0 comes up and Firefox runs fine (Gutsy Ubuntu and Xubuntu, not Kubuntu see explanation 18 Oct 2007 below)
Bug #1. However, Network Manager still says "no network connection" even though there is a connection.
4. I didn't understand why there was no connection after bootup, so looking thru the syslog and networking, I see during boot Ubuntu establishes the network connection and finds the gateway and the nameserver out on the internet so eth0 is functioning fine.
Bug #2. Then Network manager decides the Realtek ethernet card (which is already running), "does not support carrier detect" and disables eth0. That's the second bug, Network manager should not disable a perfectly functioning eth0.
If the Ubuntu goal is for the "ordinary computer desktop user" to "just run", then Network manager is in this case impeding the goal. My view as a user, anyway. Jerry |
|
| 2007-10-19 01:53:59 |
jerrylamos |
title |
[feisty fawn] NetworkManager reports incorrect online status |
[feisty fawn and Gutsy] NetworkManager reports incorrect online status |
|
| 2008-01-25 11:05:38 |
Bug Watch Updater |
network-manager: status |
New |
Incomplete |
|
| 2009-01-15 05:11:08 |
Bug Watch Updater |
network-manager: status |
Incomplete |
Won't Fix |
|
| 2010-09-15 23:22:23 |
Bug Watch Updater |
network-manager: importance |
Unknown |
Medium |
|
