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 -- does not automatically start the wired connection due to missing link beat https://bugs.launchpad.net/bugs/83143 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
