OK, well, that appears to be both right and partly wrong.On Wed, 28 May 2003 08:06:38 -0700 eric huff <[EMAIL PROTECTED]> wrote:
Are you sure it's spending a long time checking for new hardware or theThis is a good point: Which is it?
step that follows (and just hasn't displayed the text of that step,
yet)?
I would think that since the message is "Checking..." it is printing the message first, then doing the job.
That's how i program messages...
But, notice it never says, finished checking..... The "checking" message is displayed when the checking begins. When "checking" is done, the message doesn't change, but the next phase begins. So, if the next phase is waiting, trying to mount something like an empty card reader, the checking message is displayed and appears to hang, but what actually is happening, is Linux is waiting for the scsi emulated card reader to either activate or time out. Since the reader is empty, it waits until the time out.
I would imagine if the original poster checks the messages, that is what is next displayed on the screen (failed to mount....). Most people don't think of it, because, they agree the reader is empty and assume the delay is from the checking. I can duplicate this delay simply by pluging in a usb reader without a card. If you really want to verify it, turn off harddrake and reboot with the empty card reader still attached. There won't be a "checking" message, but the system will still pause, followed by the "failed to mount..." message.
There are a couple of options available. One, you can just live with it. Two, you can leave a card in the reader. Three, have the reader unplugged when rebooting. A fourth option may be to turn off auto mounting in the /etc/fstab for the reader. That may work, but I don't want to reboot my computer at this time just to find out.
Anyway, that has been my experience with a stock and almost stock Mandrake kernel when booting with an empty card reader. It appears to hang right after the checking message is displayed if there is an empty card reader attached. YMMV
Joeb
First off, putting a card in the reader does not cure it.
I strongly suggest it is likely to be the presence of the PQI card reader that it is detecting and tying to do something with.
Yes, if I go to MCC - sevices and remove the cross to run harddrake at boot time that "cures" the problem, in as much as there is no longer any "check for new hardware " delay. But I'm not sure I ought to be doing this. To my mind this is like having a motor car that has a broken exhaust pipe and saying the solution is to scrap the car.
As a matter of reference only the next message after checking for new hardware is setting network parameters.
I'm fully confident the hardware detection is what it was doing and is the problem, and it is almost certainly going to be the PQI card reader that is causing the check new hardware stage of the boot to want to do something more about it. I'm guessing , that where as in M9.0 the check new hardware facility didn't find the reader at all, this new M9.1 does find the reader and wants to configure it, as Joeb says, after a while it is being timed out . In a way I'm glad it's finding the device. I want my reader configured and fully working and for sure detection is necessary to that process.
If I turn harddrake boottime detection permanently off what will be the disadvantages ?
John
--
John Richard Smith
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
