Hi Olivier: On Thu, Apr 7, 2011 at 2:04 AM, Olivier LAHAYE <olivier.lah...@cea.fr> wrote:
> Do you think this problem is solved in latest svn update? I doubt it, but you could try. >> > The problem is that after deploying the image without any trouble, the >> > node fails to reboot (kernel panic, no disk found). >> > The cause is that the node initrd.img lacks the ahci.ko module (and >> > uselesly includes cciss.ko). Did you actually extract the SystemConfigurator generated initrd and confirm that it does not include the ahci module? Some times it's included but just not called/referenced. If your headnode has the same hardware as the client nodes, try copying /etc/modprobe.conf from the headnode to the image, re-image and reboot, and see if it works. If the hardware is not identical, then boot the client in a rescue CD, get a copy of the modprobe.conf from /tmp and then copy that to your image. UYOK is probably your best bet though -- why are you hesitant to use it? It provides the *best* compatibility between SystemImager kernel/initrd and deployed OS kernel/initrd. The gap between the bundled SystemImager kernel and kernels in current Linux distributions should be quite huge now... P.S. Would be good if you could test my RPMs and integrate that with OSCAR and see if youcome up with any issues. Cheers, Bernard ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
