Boot messages when booting into single user mode Configuring network interfaces... r8169 0000:01:09.0: eth1:link down r8169 0000:01:09.0: eth1:link down ADDRCONF(NETDEV_UP): eth1: link is not ready r8169 0000:01:09.0: eth1:link ready ADDRCONF(NETDEV_UP): eth1: link becomes ready and then it hangs. Thanks for any suggestions. Mark On Sun, Jan 27, 2013 at 5:07 PM, Mark Phillips wrote: > 1. I installed a new nic, an asus NX1101, and went into the bios and > disabled the on board network interface controller. The system booted, but > the network was not working. > > 2. I then edited the /etc/network/interfaces file and changed eth0 to eth1 > for the new nic. I then ran ifup eth1, and the network came up. I could > ping google.com and ssh to the box. > > 3. I rebooted the machine, and the boot process again stopped at > Configuring the network. I rebooted again to check if the bios had been > changed, and the bios still says that the on board network interface > controller is disabled. > > So now the new nic is enabled, but the system still hangs at trying to > configure the network. > > Anyone have any ideas? > > Thanks, > > Mark > > > > On Sun, Jan 27, 2013 at 12:04 PM, Matt Graham wrote: > >> From: Mark Phillips >> > There was an ATI Rage 128 video card in the system, and the the newer >> > Debians do not have the radeon drivers. >> >> That shouldn't have caused any problems. Rage 128 cards use the r128 X >> module, not the radeon one. Why is Debian not including the radeon >> modules? >> That just seems weird and counterproductive, since so many machines out >> there >> have video cards driven by that module. And if it's headless, it should >> probably be starting up without X, in a VGA text console or vesafb, so >> that >> the video card is completely irrelevant. >> >> > However, the system hangs when trying to start network services. >> > [10.184481] e1000: eth0 NIC Link is UP 1000 Mbps Full Duplex, Flow >> > Control: RX/TX >> > [10.187930] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready >> > >> > Then nothing is printed out and the system does not respond. >> > The card is the internal NIC - I don't have any extra cards in the >> > machine. >> >> Take a random PCI NIC you have lying around. Put that NIC in the >> machine. Go >> into the machine's BIOS Setup and disable the internal NIC. If you do >> that, >> and the thing boots normally, then the machine's internal NIC is hosed. >> BTDT. >> NIC failure *can* happen, it's just sort of rare since there aren't any >> moving parts. >> >> Or the new kernel has some sort of weird bug with its e1000 module. >> Distro >> kernels seem to have more weird bugs than vanilla kernels, for some >> reason. >> You could test this by booting with the rescue system's option for "no >> network", then if it comes up, and you modprobe e1000 and it immediately >> locks >> up, that may be the problem. >> >> -- >> Matt G / Dances With Crows >> The Crow202 Blog: http://crow202.org/wordpress/ >> There is no Darkness in Eternity/But only Light too dim for us to see >> >> --------------------------------------------------- >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org >> To subscribe, unsubscribe, or to change your mail settings: >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss >> > >