does not automatically start the wired connection due to missing link beat

[jerrylamos]

Feisty Fawn Herd 3 downloaded 20070201

Network manager icon on top line says "no network connection" as I make this entry.
The evidence is the CDLive got out on the LAN, got the gateway address, and the DSL nameserver address, then after that feisty network manager decided there was no connection.

From terminal session, ifconfig printout did not return an inet address, and in fact Firefox couldn't access the intenet.

Then I did "sudo dhclient" (from Official Ubuntu manual p. 211), now ifconfig returns an inet address, and Firefox got ubuntu.com so I could make this report. The network manager icon still says "no connction" which is obviously not true.

I tried removing network manager with Synaptic but the icon is still there and still says "no connection".
Edit/Delete Message

[Emilio Pozuelo Monfort (pochu)]

Changed package

[Chris Burgan (cburgan)]

Thanks for the report,

nm-applet requires 1 of 2 situations for it to pick up and control a device. Either it is:

a) Not listed in at all in /etc/network/interfaces
b) Listed, but set to dhcp and auto

Otherwise you need to set it up differently, am I to understand from your second comment that you are no longer on herd 3? If so are you on herd 4 and no longer experiencing this? Let me know please.

[jerrylamos (jerrylamos)]

The Network Manager "No network connection" has persisted thru most every daily update of Herd 4. This is 20070301 which may be Herd 5.

Network Manager still says "No network connection" as I enter this message so the Network Manager is obviously wrong.

If Ubuntu wants to have a wide acceptance on the desktop, then the CD Live should, as much as possible, "Just work". With this hardware configuration Dapper and Edgy both come up with the network working. Feisty does not. I have to do a sudo dhclient to get the connection working again. /etc/var/syslog shows Network Manager disabling the network which was already running at that time since the system has already activated DHCP and found the remote nameserver.

Feisty has Network manager which decides to disable the obviously working network card. I don't know what the network developers want for the future of Ubuntu. It would seem to me that they would want more and more configurations to work, not less and less. Yes, I can do a workaround, but an average new user expects it to "just work" like Dapper and Edgy did.

What is the reason Network Manager on CD Live has to disable an already functioning network card?

Thank you, Jerry Amos

[jerrylamos (jerrylamos)]

Kubuntu CD Live herd 5 Konqueror can't access internet as booted up.

Network manager disables eth0 after eth0 has already found gateway and remote DNS, so the internet is already working fine when network manager disables the card.

Network manger claims the Realtek RTL 8029(AS) card does not support "carrier detect"?. This card works fine on Dapper, Edgy, Xubuntu Herd 5 (no network manager), PCLiunuxOS, Freespire, Knoppix, ...

Clicking on Network Manager and clicking on Wired Network activates it and then Konqueror accesses the internet. Why didn't it "just work" for the "ordinary desktop user" (see Official Ubuntu Book)?

Cheers, Jerry

[Martin Pitt (pitti)]

This works well for me and other people, so as you already mentioned the reason might be that your hardware setup does not have a link beat ('carrier detect'). We need to find a solution for that.

Just to check this theory, can you please do the following:

  - pull out the ethernet cable
  - plug it back in
  - copy&paste the output of "dmesg |grep link" here

Thank you!

[Martin Pitt (pitti)]

This affects several people and we should find a solution for Gutsy.

[jerrylamos (jerrylamos)]

Here's the output of dmesg | grep link after unplugging, waiting, and re-plugging:

[ 25.644058] audit: initializing netlink socket (disabled)

Then I clicked on the Network Manager, it connected, and I'm writing this note. I did another dmesg | grep link and it still says the same thing.

I tried removing the Network Manager package from the latest Feisty however that's worse. Network Manager is still active on boot even though the package is removed(!), still disables eth0, and now there's no icon to re-activate and I have to use the "Applications, Accessories, terminal, sudo dhclient, enter password" method. So I installed Feisty all over again. Removing a package and re-installing frequently does not get me back to where I started.

Whoever coded Network Manager decided that my adapter didn't have carrier detect and can't work so NM disables it during boot. In my case that's a wrong decision. I even installed Edgy, installed Network Manager, and got the same problem. Without Network Manager any number of Linux distro's work fine no manual actions required.

Examples of the anklebiter situations I get: Boot up, right away Update says there are packages to install, lists them, I click install, Ubuntu asks for password, and then Install can't accesses the package files! Then I notice the little red mark on the Network Manager, I click to activate the network, do System, Admin, Update Manager, and then install goes through.

Let me know if I can try anything. Thanks for looking at this bug. Cheers, Jerry

[Skou (skou)]

As this bug have been confirmed by several people I'm changing the status to Confirmed. See bug #97278.
If Info is needed please ask for it!

[Martin Pitt (pitti)]

This was discussed on the developer summit:

 * network-manager is designed to be a tool for dynamic network roaming. It is not supposed to work around hardware or driver bugs. If the driver is the problem, such bugs should be filed against the kernel with details about the hardware. If the hardware is broken, there's nothing we can do about it, except for publishing a list of known-good hardware. That's why I close this bug for n-m.

However, for most people who are affected by this bug, the root cause is actually bug 90267, since our installer still puts ethernet devices into /etc/network/interfaces, so that they are initialized during boot. Thus this should be the priority to fix.

[jerrylamos (jerrylamos)]

Your Ubuntu, your call. My hardware does not have bugs. The driver does not have bugs. They work nice and fast on Edgy and Dapper and Knoppix ...

During boot, Network Manager "disables" eth0 wired connection with some complaint about "carrier detect" whatever the Network Manager programmer used to decide that.

I then have to manually reconnect eth0 by selecting Network Manager icon and manually select Wired Connection, and it works perfectly. Since Network Manager can enable the connection, it does not make sense for Network Manager to disable the connection during boot.

[folkoy (pluron)]

agreed that if the bug is not in that application you should track the problem.

Just to correct some of your comment; The hardware which is not working with Feisty has been working PERFECTLY with Debian, Suse, Fedora, Ubuntu Dapper for the longest time. There really is a bug in Feisty somewhere in the networking and that bug was not there in previous release. The bug is also present in the Debian testing release "Lenny".

Would be nice to have some suggestion of which subsystem could be the problem. Not sure bug 90267, describe the problem I reported.

[Martin Pitt (pitti)]

Right, I did not deny that there was a problem. I just stated that bug 90267 is the root cause of that evil, and that we will fix that one instead of doing dodgy workarounds for this one.

[folkoy (pluron)]

The problem is fixed for me in Gutsy Tribe 5. My wired ethernet interface is up when I log in the GUI.

[shanen (Shannon Jacobs) (shanen)]

I think I'm seeing the same problem in the released Feisty. I just did a fresh install from the CD on a fairly new Sharp machine. Whenever it first boots it fails to connect to the network, and I have to disable the enable the network once or twice before it will connect. Once it has the connection it seems to work fine.

(So far this bug seems to be the best match among the various searches I've tried...)

[jhansonxi (jhansonxi)]

I just tested a bunch of network devices for Bug #82927 on Ubuntu Gutsy RC1 and found that the carrier detect problem affects both the ne2k-pci and tulip drivers.

[jerrylamos (jerrylamos)]

If I manually select the Network Manager Icon, and the wired network, the drivers function on the internet just fine.

The obvious conclusion is disabling the connection for a "carrier detect problem" is a Network Manager code decision which is not beneficial for us users. If the drivers work, they work, and since they do, then there's no justification that us users see for the Network Manager code to disable the working connection.

Ubuntu Tribe 5 came right up, connection active, no problem about "carrier detect". Xubuntu has been coming right up, connection active, until Release Candidate when it joined the other non-working as booted versions when it added the Network Manager icon.

Since Ubuntu Tribe 5 works fine, connection active at boot, why did Ubuntu decide to "break" Network Manager boot code again for Release, disabling the connection so I have to manually enable it?

Worst case is Kubuntu 7.10 Release Code. In sequence:
1. Boots up and Network Manager shows "no active connection". Konqueror can't get internet.
2. sudo dhclient establishes connection fine.
3. System, Network shows eth0 connected, DNS, etc. O.K.
3. Network Manager shows "no active connection", Konqueror can't get internet.
4. Add/Remove accesses internet http://... just fine and downloads Firefox O.K.
5. Network Manager still shows "no active connection", Konqueror can't get internet even though Add/Remove had no problem.
6. Start Firefox, browses internet fine. Konqueror still can't.
7. After all this, Network Manager shows "no active connection", which is obviously false.

Would someone explain what use Network Manager is on Kubuntu on this computer?

Thank you, Jerry
7.

Jerry

[Errol (eksatx-ubuntu)]

Is there a reason this bug has been marked invalid? I have been searching the web for an hour or so and I am finding a substantial number of people that are stuck with this problem.

The symptoms seem to be consistent -- networking starts on boot just fine as long as they are not using network-manager.

This seems to be a step backward for many people.

What can be done to re-open this?

[folkoy (pluron)]

This problem has never been fixed in Ubuntu 7.04 but it's fixed in 7.10.
I hope the fix would be backported into the impacted previous release...

[jerrylamos (jerrylamos)]

Wired network is disabled on boot on this system on 7.04, 7.10, and now Hardy Alpha 8.04.

The "Network Manager" disables the perfectly running wired network card:

 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8029(AS) [10ec:8029]
 Subsystem: Realtek Semiconductor Co., Ltd. RTL-8029(AS) [10ec:8029]
 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Interrupt: pin A routed to IRQ 11
 Region 0: I/O ports at e400 [size=32]

From a user viewpoint I haven't seen any developer activity on this function ever since "Network Manager" was put into Feisty, then Gutsy, now Hardy.

Jerry

[Errol (eksatx-ubuntu)]

I can confirm that I also am experiencing these symptoms with Gutsy. Many of the posts I have found elsewhere indicate the same thing.

[ricesteam (popsiclepete)]

I like to confirm this bug exists in 7.10.

I've recently upgraded from 7.04 and discovered this problem. I've been searching for solutions and I found this.

My hardware works. Like the above posters, I have to manually enable my network on each boot-up which is tedious when it was automatically done for me before the upgrade.

Please fix.

[jerrylamos (jerrylamos)]

Hardy Alpha 4, 20080131, same bug. Network Mangler deliberately disables perfectly functioning eth0 requiring a manual select Network Mangler applet, select wired connection. No reason for Network Mangler to disable the connection during boot at all since it works just fine! after manual selection.

Jerry

[jerrylamos (jerrylamos)]

Kudos! Intrepid Ibex Alpha 3 with 20080809 updates finally recognizes wired connection on boot - I get greeted with "wired connection established".

This is uname -a:
Linux linux 2.6.26-5-generic #1 SMP Sun Aug 3 01:25:54 UTC 2008 i686 GNU/Linux

This is a FIRST for network manager on this Realtek
 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
 [10ec:8029]

This is Xubuntu however since Network Mangler first appeared as a mandatory option on Feisty, all three Ubuntu - Xubuntu - Kubuntu have had the problem of Network Mangler deliberately disabling eth0 as in the original bug report, starting with Feisty, then Gutsy, then Hardy, and with Intrepid before yesterday.

From syslog, NetworkMangler first deactivates the device then activates it! From syslog:

Aug 9 15:36:02 linux NetworkManager: <info> (eth0): device state change: 1 ->
2
Aug 9 15:36:02 linux NetworkManager: <info> (eth0): bringing up device.
Aug 9 15:36:02 linux NetworkManager: <info> (eth0): preparing device.
Aug 9 15:36:02 linux NetworkManager: <info> (eth0): deactivating device.
Aug 9 15:36:02 linux NetworkManager: <info> (eth0): device state change: 2 ->
3
Aug 9 15:36:02 linux nm-system-settings: Adding default connection 'Auto eth0'
for /org/freedesktop/Hal/devices/net_00_40_05_55_80_47