GNOME Bugzilla – Bug 542916
Network-manager shows wired interface as disconnected when started (under VirtualPC and Hyper-V)
Last modified: 2008-07-15 21:07:41 UTC
Please describe the problem:
When I boot Debian under Microsoft VirtualPC 2007 or WindowsServer Hyper-V, the network is "disconnected".
The network interface is has PCI id =1011:0009
"Digital Equipment Corporation DECchip 21140 [FasterNet]"
The Linux kernel module to handle it is "tulip".
Steps to reproduce:
1. Boot Debian (stable or Testing) under VirtualPC 2007 or Hyper-V
2a. Open a session in a console, type "ifconfig" : The interface isn't configured
2b. Open a session under gnome : the NM applet says the link is down.
(click on the icon, the "Wired Networking" isn't ticked in !).
3a. Type "ifup eth0" : the interface get configured.
3b. Click on the NM applet, tick-in "Wired Networking" : the interface get configured.
We notice that the interface is down.
The interface should be up and configured.
Does this happen every time?
Under Debian stable (kernel 2.6.18 + NM 0.6.4) and Debian Testing (kernel 2.6.25 + NM 0.6.6)
I also made the following test :
1. boot into debian, and remove the files /etc/rc2.d/*network-manager*
2. reboot again and login the console as root.
3. Run ifconfig : notice eth0 is up and running
4. Run the command : "NetworkManager --no-daemon"
### sample output : start ###
NetworkManager: <info> starting...
NetworkManager: <info> eth0: Driver 'tulip' does not support carrier detection. You must switch to it manually.
NetworkManager: <info> nm_device_init(): waiting for device's worker thread to
NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
NetworkManager: <info> Deactivating device eth0.
### sample output : end ###
5. Run ifconfig again. Notice that the interface isn't configured anymore.
Created attachment 114521 [details]
Created attachment 114522 [details]
NetworkManager is not aware of the state of devices that are not configured by NetworkManager. Thus typing 'ifup eth0' has no effect becuase you have not told NetworkManager to bring the device up (by picking it from the list).
The real problem here is that the device does not support carrier detection via ethtool or mii-tool. If the driver supported carrier detection, NetworkManager would bring it up automatically.
NetworkManager: <info> eth0: Driver 'tulip' does not support carrier
detection. You must switch to it manually.
That should be fixed in the driver.
Couldn't NetworkManager try to bring up those devices on boot ? Especially when the computer has no other network interface.
I don't know If this problem can be solved on this application side only, but it would be great if we could find a solution so Windows admins don't get mad when they try Linux ;)
I've opened a similar bug again linux's tulip driver :
Your help would be appreciated.