dcook32p Posted July 10, 2004 Report Share Posted July 10, 2004 When I use verbose mode to see what's going on during boot-up, I see that: Bringing up eth0: [FAILED] but I can still connect to the Internet via my cable modem. However, the "link light" on my modem shows that I'm not connected to the PC. Should I be concerned about this? What do I need to post here to help? Quote Link to comment Share on other sites More sharing options...
streeter Posted July 10, 2004 Report Share Posted July 10, 2004 This seems to be pretty common - if it works, don't worry - leave it alone! Just don't boot in verbose mode if you don't like seeing [FAILED] messages :) Chris Quote Link to comment Share on other sites More sharing options...
theYinYeti Posted July 15, 2004 Report Share Posted July 15, 2004 I looked at the network scripts, and it seems to me, that it is because of a new kind of "plug-and-play" for network interfaces. eth0 is said to be plug-and-play by the motherboard and Mdk10 takes it "seriously". It launches ifplugd on eth0 for autodetecting network start and stop (when you plug or unplug). So auto-start on boot is redondant, I guess. I suppose you could just go to /etc/sysconfig/network-scripts/ and change your eth0 file to say On-boot: no. Yves. Quote Link to comment Share on other sites More sharing options...
dcook32p Posted July 18, 2004 Author Report Share Posted July 18, 2004 So auto-start on boot is redondant, I guess.I suppose you could just go to /etc/sysconfig/network-scripts/ and change your eth0 file to say On-boot: no. <{POST_SNAPBACK}> I changed that line in ifcfg-eth0, but then I lost all network connectivity on the next boot. I had to ifup eth0 to get anything working. I'm using a Netgear FA-311 if it matters. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.