sambo Posted July 11, 2004 Report Share Posted July 11, 2004 Am having a 'problem' with starting up Mandrake 10.0 (OE). When "checking for new hardware" it says "FAILED". What does this mean? Also, when it says "Bringing up interface for eth0" it takes about a minute before it finishes doing so. What does this mean (I have a feeling it is modem related)? Is there any way to speed this up? Thanks folks. Quote Link to comment Share on other sites More sharing options...
arctic Posted July 11, 2004 Report Share Posted July 11, 2004 (edited) bringing up the eth0 also takes up some time on my box (eth0 + adsl-flatrate). this is quite normal. but it doesn't mean that your box doesn't work. it is simply that linux tries to bring up eth0 at startup, while most redmond-products start up eth0 after your dektop shows up. the time "lost" is the same. concerning the "checking-failed" thing: go to mcc and have a look at your hardware, if there is any item that doesn't show up, although it should. i think that it yould indicate to e.g. some hotplugging device not being configured. Edited July 11, 2004 by arctic Quote Link to comment Share on other sites More sharing options...
xbob Posted July 13, 2004 Report Share Posted July 13, 2004 bringing up the eth0 also takes up some time on my box (eth0 + adsl-flatrate). this is quite normal. but it doesn't mean that your box doesn't work. it is simply that linux tries to bring up eth0 at startup, while most redmond-products start up eth0 after your dektop shows up. the time "lost" is the same. concerning the "checking-failed" thing: go to mcc and have a look at your hardware, if there is any item that doesn't show up, although it should. i think that it yould indicate to e.g. some hotplugging device not being configured. <{POST_SNAPBACK}> I got the FAILED hardware message on my first install of Mdk10. I don't have a floppy drive, have it disabled in BIOS, etc... no problems. Did a BIOS flash, which by defualt loads "optimzed defaults" which re-enables the floppy controller. So Linux would boot, find a new hardware entry in BIOS, not find the drive and FAIL. I had some other issues I created with excessive sessions of "what does this do" so I did a clean install and fixed it that way, but I would go with arctic, do some digging and you might find a failing hot plug device. Quote Link to comment Share on other sites More sharing options...
sambo Posted July 14, 2004 Author Report Share Posted July 14, 2004 I'm also getting this: Determining IP configuration for eth0: Failed What does this mean? How do I fix it? Quote Link to comment Share on other sites More sharing options...
Ixthusdan Posted July 14, 2004 Report Share Posted July 14, 2004 If you are using dhcp, then it means it can't find the dhcp server. If your ip is fixed, then Mandy can't find the fixed ip. In mandy 9.2, I always got a failed eth0 during boot, yet my network was fine after logging in to kde. I use dhcp. So I lazily never worried about it! :lol: Better yet, what is your network configuration? (modem) Quote Link to comment Share on other sites More sharing options...
SwiftDeath Posted July 16, 2004 Report Share Posted July 16, 2004 Yeah, My grandaddy used to say if it ain't broke, don't fix it. Their are ways to speed things up like tweaking your firefox, or chaning your ip version and stuff. BTW 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.