<div dir="ltr"><div>Well, after some poking around I finally solved the problem....<br></div><div><br></div><div>1. The onboard nic was not dead, just a little confused.</div><div>2. The problem was in /etc/fstab in this line</div>
<div>//<a href="http://192.168.25.105/orca">192.168.25.105/orca</a> /home/share cifs file_mode=0644,dir_mode=0755,uid=1000,gid=1000,rw 0 0</div><div>I found these errors in the logs - </div><div>CIFS VFS: cifs_mount failed w/return code = -6</div>
<div><br></div><div>When I commented out the line above in /etc/fstab, everything started working again. </div><div><br></div><div>The network mount was for a NAS that turned out not to work very well, so I removed it from the network and must have forgotten to comment out that line in /etc/fstab.</div>
<div><br></div><div>I hate it when things like that come back to haunt you years later.....</div><div><br></div><div>Mark</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jan 27, 2013 at 6:18 PM, Mark Phillips <span dir="ltr"><<a href="mailto:mark@phillipsmarketing.biz" target="_blank">mark@phillipsmarketing.biz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Boot messages when booting into single user mode<br></div><div><br></div><div>Configuring network interfaces...</div>
<div>r8169 0000:01:09.0: eth1:link down</div><div>r8169 0000:01:09.0: eth1:link down</div>
<div>ADDRCONF(NETDEV_UP): eth1: link is not ready</div><div>r8169 0000:01:09.0: eth1:link ready</div><div>ADDRCONF(NETDEV_UP): eth1: link becomes ready</div><div><br></div><div>and then it hangs.</div><div><br></div><div>
Thanks for any suggestions.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Mark</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sun, Jan 27, 2013 at 5:07 PM, Mark Phillips <span dir="ltr"><<a href="mailto:mark@phillipsmarketing.biz" target="_blank">mark@phillipsmarketing.biz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>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.</div>
<div><br></div><div>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 <a href="http://google.com" target="_blank">google.com</a> and ssh to the box.</div>
<div><br></div><div>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.</div>
<div><br></div><div>So now the new nic is enabled, but the system still hangs at trying to configure the network. </div><div><br></div><div>Anyone have any ideas?</div><div><br></div><div>Thanks,</div><div><br></div><div>
Mark</div><div><br></div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jan 27, 2013 at 12:04 PM, Matt Graham <span dir="ltr"><<a href="mailto:danceswithcrows@usa.net" target="_blank">danceswithcrows@usa.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">From: Mark Phillips <<a href="mailto:mark@phillipsmarketing.biz" target="_blank">mark@phillipsmarketing.biz</a>><br>
<div>> There was an ATI Rage 128 video card in the system, and the the newer<br>
> Debians do not have the radeon drivers.<br>
<br>
</div>That shouldn't have caused any problems. Rage 128 cards use the r128 X<br>
module, not the radeon one. Why is Debian not including the radeon modules?<br>
That just seems weird and counterproductive, since so many machines out there<br>
have video cards driven by that module. And if it's headless, it should<br>
probably be starting up without X, in a VGA text console or vesafb, so that<br>
the video card is completely irrelevant.<br>
<div><br>
> However, the system hangs when trying to start network services.<br>
</div>> [10.184481] e1000: eth0 NIC Link is UP 1000 Mbps Full Duplex, Flow<br>
> Control: RX/TX<br>
> [10.187930] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready<br>
<div>><br>
> Then nothing is printed out and the system does not respond.<br>
</div><div>> The card is the internal NIC - I don't have any extra cards in the<br>
> machine.<br>
<br>
</div>Take a random PCI NIC you have lying around. Put that NIC in the machine. Go<br>
into the machine's BIOS Setup and disable the internal NIC. If you do that,<br>
and the thing boots normally, then the machine's internal NIC is hosed. BTDT.<br>
NIC failure *can* happen, it's just sort of rare since there aren't any<br>
moving parts.<br>
<br>
Or the new kernel has some sort of weird bug with its e1000 module. Distro<br>
kernels seem to have more weird bugs than vanilla kernels, for some reason.<br>
You could test this by booting with the rescue system's option for "no<br>
network", then if it comes up, and you modprobe e1000 and it immediately locks<br>
up, that may be the problem.<br>
<span><font color="#888888"><br>
--<br>
Matt G / Dances With Crows<br>
The Crow202 Blog: <a href="http://crow202.org/wordpress/" target="_blank">http://crow202.org/wordpress/</a><br>
There is no Darkness in Eternity/But only Light too dim for us to see<br>
</font></span><div><div><br>
---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>