no carrier detection for ethernet

Bug #89295 reported by Gabriel Dragffy
14
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: network-manager-gnome

As per title. Have tried three new Feisty installations over the last couple of weeks. Have a computer connected only via 100mb LAN. Turn on, log in and no internet connection - must manually click on nm-applet and select wired connection. After this it gets the DHCP info and connects, until next reboot. Expected behaviour: automatically attempt configuration and connection via DHCP, especially if wired connection is the only method available. At the moment I'm going to nuke nm-applet and go back to the old-fashioned /etc/network/interfaces file config :)

description: updated
Jammykay (james-kerrz)
Changed in network-manager:
assignee: nobody → james-kerrz
status: Unconfirmed → Fix Committed
Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. With which version of network-manager did you notice this issue? You could check via 'dpkg -l network-manager'. Thanks in advance.

Changed in network-manager:
assignee: james-kerrz → brian-murray
status: Fix Committed → Needs Info
Revision history for this message
Gabriel Dragffy (dragffy-deactivatedaccount) wrote :

It says:

network-manage 0.6.4-6ubuntu2

Which as far as I know is the latest available for Feisty. No updates came through on my aptitude update and aptitude upgrade.

Changed in network-manager:
assignee: brian-murray → nobody
status: Needs Info → Confirmed
Revision history for this message
didier (did447-deactivatedaccount) wrote :

Hi,

Do you have something like:
 NetworkManager: <information>eth0: Driver 'xxx' does not support carrier detection. You must switch to it manually.

In /var/log/syslog?

Revision history for this message
Gabriel Dragffy (dragffy-deactivatedaccount) wrote : Re: [Bug 89295] Re: nm-applet won't automatically connected to a DHCP wired network

I groped and greped my way through syslog an found nothing at all like
that. About the only thing I saw was warnings that ipupdating allowed
wireless networks. It doesn't have wireless, only wired though. Hope
that helps.

Revision history for this message
Jonas Jørgensen (jonasj) wrote : Re: nm-applet won't automatically connected to a DHCP wired network

I see the same problem on one computer (only one wired connection; no wireless). My /var/log/syslog contains "NetworkManager: <information>^Ieth0: Driver 'ne2k-pci' does not support carrier detection. ^IYou must switch to it manually.".

network-manager version is 0.6.4-6ubuntu3.

Revision history for this message
Thierry Lemaire (thierry-lemaire) wrote :

I have the same problem. It works fine before the 2 last update of nm.

Revision history for this message
Martin Pitt (pitti) wrote :

Works for me on feisty du jour. Can you please boot your machine and give me the output of

  dmesg |grep 'eth.*link'

? Thank you!

Changed in network-manager:
status: Confirmed → Needs Info
importance: Undecided → Medium
Revision history for this message
Robert Zelnik (rzelnik) wrote :

I have the same problem in Feisty. network-manager is updated.

dmesg |grep 'eth.*link' has empty output, even after manual reconnecting.

in /etc/network/interfaces the line "auto eth0" dissapeared, as desribed here:

http://ubuntuforums.org/showthread.php?t=408647&highlight=network+manager

Revision history for this message
Martin Pitt (pitti) wrote :

> in /etc/network/interfaces the line "auto eth0" dissapeared

Ah, this would explain it. Non-auto cards are not handled by network-manager, because they are regarded as 'manually configured'.

Changed in network-manager:
status: Needs Info → Rejected
Revision history for this message
Robert Zelnik (rzelnik) wrote :

Actually I edited the /etc/network/interfaces and put the line "auto eth0" back, but it did not help - the network did not start automatically either.

I don't know why this bug was set to rejected. This IS a real bug. I did not delete the "auto eth0" line manually. There's something that automatically delete that line or put it to the end of the file.

Revision history for this message
Martin Pitt (pitti) wrote :

Alright, with the 'auto' line added it should indeed connect automatically.

If the static configuration program screws up the interfaces file, can you please file a bug against gnome-system-tools, together with a recipe how to reproduce it? Thank you!

Changed in network-manager:
status: Rejected → Unconfirmed
Revision history for this message
Robert Zelnik (rzelnik) wrote :

I checked it again. The /etc/network/interfaces file is untouched, but the network still needs to be connected manually. The default mode after startup is "not connected".

Revision history for this message
Martin Pitt (pitti) wrote :

> dmesg |grep 'eth.*link' has empty output, even after manual reconnecting.

So indeed there is no carrier detection for your ethernet card. This might be either a bug in the particular network driver, or simply a problem with the physical wiring (going through some weird routers/switches, etc.)

Changed in linux-source-2.6.20:
status: Unconfirmed → Needs Info
Revision history for this message
Robert Zelnik (rzelnik) wrote :

Ok, but in 6.04 and 6.10 it worked well. This issue occured after upgrade to 7.04 beta.

Revision history for this message
Joe Soroka (launchpad-joesoroka) wrote :
Download full text (13.1 KiB)

I have the same bug running a pristine feisty install straight off the desktop cd. This is on the free-as-in-beer Microsoft VirtualPC 2007, which uses the tulip driver. (You'll have to do a tiny bit of xorg.conf editing to get feisty to install on VPC2K7. When the borked install screen comes up, switch to a text console and change DefaultDepth 24 to DefaultDepth 16, then switch back and ctrl-alt-backspace it)
-----------------------------------------------------------------------------------------
AMIBI0S(C)2001 American Megatrends, Inc.
BI0S Date: 02/22/06 20:54:49 Ver: 08.00.02

Press DEL to run Setup
Checking NVRAM..

512MB 0K
Auto-Detecting Pri Channel (0)...IDE Hard Disk
Auto-Detecting Pri Channel (1)...Not Detected
Auto-Detecting Sec Channel (0)...CDR0M
Auto-Detecting Sec Channel (1)...Not Detected
Pri Channel (0): 1. 1 Virtual HD

Starting up ...
[ 19.281252] isapnp: checksum for device 1 is not valid (0x89)
[ 19.289884] isapnp: checksum for device 2 is not valid (0xbe)
Loading, please wait...
kinit: name_to_dev_t(/dev/disk/by-uuid/00000000-0000-0000-0000-000000000fff) = h
da5(3,5)
kinit: trying to resume from /dev/disk/by-uuid/00000000-0000-0000-0000-000000000
ac1
kinit: No resume image, doing normal boot...

Ubuntu 7.04 feisty tty1

feisty login: root
Password:
Last login: Fri May 4 00:22:21 2007 on tty1
Linux feisty 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
                     ...

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.