On Sat, 16 Oct 2004, Benoit des Ligneris wrote:
> Hello Paul, > > Kernel_picker is usefull once your nodes are installed. If they are not, > then it is not useful. Interesting - I was under the impression that the [--networkboot [Y/n]] option controlled whether the kernel I was adding to the system image was also used for network boot/initial install. And using that option *did* affect the network boot kernel - the file in /tftpboot changed, and I got this new error where there was none before when using the --networkboot option. > From what I understand, you can not install properly your node because > the kernel/initrd used by System Installer does not have the proper > module (e1000) or because your adapter is not properly detected ? Initially the problem was that System Installer didn't have the proper module. Now I've tried to modify the kernel used by system installer with kernel_picker and the --networkboot option and the client won't boot at all, let alone install. > If yes, please have a look here : > http://www.revolutionlinux.com/downloads/OSCAR/Supermicro-P4SC8=P4SCi-en/ > > Some information is mandrake specific but the procedure is generic. > > To help the module detection, please modify Table.pm on the master node > and on the image root. > > To generate a new kernel and initrd for SIS, please use the > mkbootdisk.pl script. I will try this out on Monday and let you know. It sounds like it will work for me the same as it did for you, although I might need to manage my own ifcfg-eth0. Paul ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
