mike wrote: > > Praedor Tempus wrote: > > > In this case, and until a real fix could be found, it would be better to have > > the function of the module as it SHOULD be working (but isn't) than to do it > > the "proper" Mandrake way. The proper way seems to be failing in this case > > for some reason. > > > > Until figuring out why this is the case, there is no need to go without the > > module and its functionality nor is it necessary to manually install the > > module every time you bootup. It is a workable temp fix until the real > > problem can be determined. > > How can the real problem be determined ? > > What steps can I take? > > Or would it be better just to recompile the module into the kernel? > > Mike
If the correct entries are in the /etc/modules.conf and /etc/modules then you may want to preload the scsi device via initrd. mkinitrd creates filesystem images which are suitable for use as Linux initial ramdisk (initrd) images. Such images are often used for preloading the block device modules (such as IDE, SCSI or RAID) which are needed to access the root filesystem. mkinitrd automatically loads IDE modules, all scsi_hostadapter entries and all modules in a probeall scsi_hostadapter .. line in /etc/modules.conf, and raid modules if the system's root partition is on raid, which makes it simple to build and use kernels using modular device drivers. Any module options specified in /etc/modules.conf are passed to the modules as they are loaded by the initial ramdisk. Ref: man mkinitrd Larry -- Sword'sEdge VoiceMail/Fax: (858) 860-6406 x1587
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
