Bernard Li wrote: > Hi all: > > I have seen this issue crop up frequently on the oscar-users mailing-list: > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg06583.html > > Basically, the user deployed the image fine to the clients, however > when the clients boot up they kernel panic. > > The usual response to these issues is "copy a working version of > modprobe.conf to the image". > > My only guess to why this works, is somehow the storage module is > built into the SystemImager kernel and is therefore not added to the > client's /etc/modprobe.conf by SystemConfigurator, therefore we need > to copy over a version from a known working system. > > The version of SystemImager which comes with OSCAR 5.0 (latest > release) is 3.7.5 which I believe is before pci-automod is added -- > perhaps this is related? >
Good question. With pci-automod the file hardware.lst (used by systemconfigurator) is generated by pci-automod itself. This means that you don't need that your hw module must be present in any database (like discover-data), but all the required info are in the kernel. But if you have the hw driver statically built into the kernel, probably the module info are not available by the sysfs interface... this would confirm that, as usual, the good approach to have a better compatibility is to use UYOK. OTOH if you want performance you can choose the default BOEL kernel... -Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
