Feisty network-manager 0.6.4-6ubuntu3 update killed NIC

Following a reboot symptoms still occur.
However,
sudo /etc/init.d/networking restart
seems to clear the problem.

I do have the same problem with the nforce 4 ethernet and a realtek one i used for testing too. The marvell one seems to be working tho. i posted all the details here:

http://ubuntuforums.org/showthread.php?p=2302180#post2302180

Sorry, but this could not be the solution. Imagine the situation (myself) posted here: http://www.ubuntuforums.org/showthread.php?t=384688 and
http://www.ubuntuforums.org/showthread.php?t=385093 for a temporarily resolution

A solution would be that the network manager take a look at /etc/network/interfaces at boot time. If there is a static configuration given it should be used for all given NIC's by network manager. If not it should try to connect to a dhcp network. At least should the user be able to change or configure the network through the panel icon. This means, please merge the normal network tool into network manager.
And this must be done for more than one NIC at the same time.
For example: At my university I used a wired NIC with static configuration for the local network and sometimes at the same time the wireless card for surfing the net with a dhcp configuration given by the computer centre.
The same is true for my office at home. See links above

The situation reached at this time is more confusing than usable. Sorry.

Frank

But you are making a great job, thanks for this operating system

I can confirm that Feisty's NetworkManager indeed misbehaves when there is more than one network card present. I have two cards, one connected to public internet, one is for my home network. Only one card works at the time, I can even use NetworkManager to choose, which one.

As others have noted, temporary workaround is to execute "sudo /etc/inid.d/networking restart" after each boot. It is pain in the... you know, where.

Since I'm the 3rd person who hits this bug, changing status to Confirmed.

I am having this problem was well. My eth0 is non-functional until I do an ifdown and ifup on the eth0 interface. My eth1 device (gigabit nic) works as expected. I see reference to a solution which I cannot seem to find. If it involves uninstalling my desktop I am not interested. Is there away to disable the network manager?

eth0 Link encap:Ethernet HWaddr 00:17:31:C0:E2:19
          inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::217:31ff:fec0:e219/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:1913 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1692 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2040749 (1.9 MiB) TX bytes:240946 (235.2 KiB)
          Interrupt:20 Base address:0xe000

eth1 Link encap:Ethernet HWaddr 00:40:F4:ED:76:5E
          inet addr:192.168.11.1 Bcast:192.168.11.255 Mask:255.255.255.0
          inet6 addr: fe80::240:f4ff:feed:765e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:40 errors:0 dropped:0 overruns:0 frame:0
          TX packets:109 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7648 (7.4 KiB) TX bytes:13095 (12.7 KiB)
          Interrupt:16 Base address:0xa000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:68 errors:0 dropped:0 overruns:0 frame:0
          TX packets:68 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5132 (5.0 KiB) TX bytes:5132 (5.0 KiB)

Networking seemed to be working with the 2.6.20.12 series of updates (NIC=Winbond Electronics Corp W89C940 per my original). However, the recent update to 2.6.20.13 seems to have broken it again.

Booted back into 2.6.20.12 and it's (networking) now broken in that kernel version as well.

Having to perform a /etc/init.d/networking restart following each boot is getting *very* tiresome. Can this please be moved to a high priority?

Related (or perhaps the same bug) seems to be:
https://launchpad.net/ubuntu/+source/network-manager/+bug/82927
[feisty fawn] NetworkManager reports incorrect online status

Removed and reloaded network-manager (hence ubuntu-desktop). I now find that following a hard reboot, the network manager shows no network connection. However, if I click the NM icon and click 'Wired Network' the NM finds the card & network works properly.

There are no wireless devices on this machine & IP is set for a static address. /etc/network/interfaces is set as:

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.4.101
netmask 255.255.255.0
gateway 192.168.4.1

Seems that NM should default to /etc/network/interfaces settings.

On 03/28/2007 11:11 AM, NoOp wrote:

>
> Seems that NM should default to /etc/network/interfaces settings.
>

I'm not sure which of the updates today did the trick, but I am now able
to uninstall network-manager and network-manager-gnome without either
uninstalling ubuntu-desktop. Static wired networking (without NM) is now
working again - thanks!