I tried on the same old machine. This time the NIC in it is an old tulip (21140-based Cogent EM-110 or 100), which doesn't support carrier detection either. I used the Hardy i386 beta livecd (nice Heron wallpaper, BTW):
Everything is the same as before. The daemon.log messages from NetworkManager are the same as I copied/pasted in the initial bug report. eth0 is detected, but n-m decided not to run DHCP on it until instructed. It turns out that the network connectivity applet has a left-click menu which (in this case) has a radio button for "Wired Network", and a "manual configuration" option. Selecting "wired network" gives connectivity (since the machine is on an ethernet segment with a DHCP server). So it's really trivial to tell n-m to use the interface _if you know how_. Left clicking on something to bring up a different menu wasn't obvious to me, but what do I know; I usually use fluxbox and mostly run stuff from bash in a gnome-terminal. I probably only right-clicked it before, which just gives an "Enable Networking" on/off, which is already enabled. I would still suggest that at least for the live CD, defaulting to trying to activate the connection would be a good thing. I'd rate this as a wishlist bug. AFAIK, only really old NICs don't support carrier detection. This tulip NIC was old 8 years ago. People with old hardware usually have some computer experience, at least in this part of the world (Canada). Thanks, -- defaults to deactivating NICs that don't support carrier detection https://bugs.launchpad.net/bugs/176003 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
