In a nutshell run lsmod and look at all the modules that your USB drive is using. You'll notice that the interrelated modules are listed making things a bit easier for you.
Then use mkinitrd and it's preload and fstab option to tell mkinitrd which modules to load into the boot image, and how they are mounted. Doing this gets everything loaded into ram during the boot and before any other services are started or called. -JMS |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]] On Behalf Of |[EMAIL PROTECTED] |Sent: Saturday, October 20, 2001 11:34 PM |To: Jose M. Sanchez |Cc: [EMAIL PROTECTED] |Subject: RE: [expert] external usb hard drive problems | | |Hi, | |I read the man page and looked around a bit on the net, but am |not sure what I should do; should I use the --preload switch, |and if so, then for which modules? | |Thanks, |David Charles | |On Sat, 20 Oct 2001, Jose M. Sanchez wrote: | |> |> | |> |I wish *SOMEBODY* would include a USB kernel as an install option! |> |USB keyboard and mouse work a lot better if they are available all |> |through the boot process. Also in regard to your first |question, it |> |seems that the USB has gotten a whole lot less |"unpluggable" in 2.4. |> |Hint: this is a step |> |backwards! |> | |> |mg |> | |> |> Including it in the kernel is not needed and/or superfluous... |> |> You can utilize mkinitrd to create a boot image (used |automatically by |> the boot loader) that incorporates any modules that you need present |> and loaded during the first stage of the boot. Booting from a SCSI |> device requires this. |> |> There is no reason that you can use this to add in the USB drivers |> either. You could go as far as booting Linux from a USB hard drive |> (ugh!!). |> |> |> -JMS |> | | |
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
