Hi Ben

The script mkbootdisk.pl seems does not work as it supposed to. I end up 
getting the following message

[EMAIL PROTECTED] tmp]# ./mkbootdisk.pl --kernel /boot/vmlinuz $kernelVersion 
--new-flavor redhat --verbose --modules-dir /lib/modules/$kernelVersion --fs 
ext2
WARNING: mkbootpackage is currently considered an experimental tool.
         "Your Mileage May Vary"
Use of uninitialized value in concatenation (.) or string at ./mkbootdisk.pl 
line 116.
>>> Kernel release:
>>> Using modules from:         /lib/modules/
>>> Using architecture:         i386
>>> Base temporary dir:         /tmp/si7672
>>> gunzip /tmp/si7672/old_initrd.gz
>>> Old initrd mount point:     /tmp/si7672/old_initrd_dir
>>> mount /tmp/si7672/old_initrd /tmp/si7672/old_initrd_dir -o loop
>>> New initrd temporary dir:   /tmp/si7672/staging_dir
>>> rsync -aHS --exclude=lost+found/ --numeric-ids /tmp/si7672/old_initrd_dir/ 
/tmp/si7672/staging_dir/
>>> umount /tmp/si7672/old_initrd_dir
>>> Removing old modules from:  /tmp/si7672/staging_dir/my_modules
Couldn't open /tmp/si7672/staging_dir/my_modules /INSMOD_COMMANDS for reading. 
at ./mkbootdisk.pl line 425.
[EMAIL PROTECTED] tmp]#

I do not have deep knowledge of Perl to fix the problem. It looks like for 
some reasons the script inserts additional space between "/my_modules" and 
"/INSMOD_COMMANDS". Is there any quick fix for this problem ?

Pavel.

>===== Original Message From Benoit des Ligneris 
<[EMAIL PROTECTED]> =====
>Hello Pavel,
>
>On the web page, the command line used for generating the kernel and
>initrd is explained, namely :
>./mkbootdisk.pl --kernel \
>/boot/vmlinuz-2.4.25-2mdksmp 2.4.25-2mdksmp --new-flavor 2.4.25-2mdksmp\
>--verbose --modules-dir /lib/modules/2.4.25-2mdksmp/ --fs ext2
>
>So my advice would be to :
>1) download the version of mkbootdisk.pl :
>http://www.revolutionlinux.com/downloads/OSCAR/Supermicro-P4SC8=P4SCi-en/mkbo
otdisk.pl
>
>2) Generate the initrd and the kernel for the OS you are using the same
>   command line but adpting it to the vmlinuz and kernel file your are
>   using. If you are using the default redhat kernel please use the
>   following procedure :
>
>export kernelVersion=`uname -r`
>./mkbootdisk.pl --kernel \
>/boot/vmlinuz $kernelVersion --new-flavor redhat\
>--verbose --modules-dir /lib/modules/$kernelVersion --fs ext2
>
>
>3) Copy the files that has been generated in 
/usr/share/systemimager/boot/i386/$kernelVersion
>   into the /tftpboot directory :
>   cp /usr/share/systemimager/boot/i386/$kernelVersion/* /tftpboot
>
>
>4) Re install a node : the specific initrd and kernel that you generated
>   for the specific distribution will be used and you should be able to
>   install the node and then reboot them.
>
>Please let use know of any problems with this procedure or with the
>mkbootdisk.pl program.
>
>Ben
>
>PS : The mkbootdisk.pl program has been created by Bryan Finley but is
>     not yet included in the stable SIS release that is included in
>     OSCAR.
>
>* Pavel A. Petukhov <[EMAIL PROTECTED]> [04-06-03 10:28]:
>> Hi Rich,
>>
>> Yes, I am using standard boot disk flavour and yes I would like to try your
>> link. I did not try to test anything else yet except for this link
>> http://www.revolutionlinux.com/downloads/OSCAR/Supermicro-P4SC8=P4SCi-en/
>>
>> The problem with the link above is that those kernel and initrd.img are for
>> Mandrake. The remedy in this link works fine, the node boots, gets the
>> boot image from TFTP, gets to DHCP server, gets IP, boots, formats the
>> drive but fails to boot from the harddrive afterwards. This is something
>> that I expected since the kernel and initrd.img are for Mandrake. At least
>> I know that the problem CAN be solved. So, now I have a choice either to
>> continue to try with RedHat or to switch to Mandrake. I still have a couple
>> of potential solutions suggested in the link below that I am going to try 
today
>> 
http://sourceforge.net/mailarchive/forum.php?thread_id=4831598&forum_id=1364
>>
>> Pavel.
>>
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, June 03, 2004 3:50 AM
>> To: Pavel A. Petukhov
>> Subject: Re: [Oscar-users] RE: DHCP Client failures after PXE Boot
>>
>>
>> Hi Pavel,
>>
>> Just a quick question here that might help with the installation
>> problem... Are you still using the standard boot disk flavour? If so, I
>> can send a link to a site which provides another flavour which I have
>> used in the past to get the e1000 network cards working.
>>
>> Hope this can help, just let me know if you haven't tried this yet,
>>
>> thanks
>>
>> Rich
>>
>> -------------------------------
>> Richard Bruin
>>
>> PhD Student
>> Department of Earth Sciences
>> University of Cambridge
>> Cambridge
>> UK
>>
>> > We have exactly the same problem as Chad Dupuis. RedHat9.0 does not
>> > recognize IntelGigabit ethernet cards (e1000) in our Supermicro 3.06
>> > Dual Xeon servers unless e1000-5.2.52 driver is installed. We can
>> > install new e1000 driver on the master node and bring up the network
>> > cards but we can not do the same trick with the computational nodes
>> > since OSCAR does not generate an image that has the correct e1000
>> > driver built-in. As in Chad's case, the nodes PXE boot, then they get
>> > the boot image from TFTP server, and then try either to get DHCP
>> > address or to assign static ip and fail because there is simply no
>> > eth0 or eth1 interface. Exactly the same happens if we generate a boot
>> > disk instead of PXE boot.
>> >
>> > Can anybody suggest how to generate a RedHat9.0 boot image with the
>> > correct updated e1000 driver that can be used by OSCAR or how to force
>> > OSCAR to use the correct e1000 driver ?
>> >
>> > Pavel Petukhov
>> > University of Illinois at Chicago
>> >
>> >
>> >
>> > -------------------------------------------------------
>> > This SF.Net email is sponsored by the new InstallShield X.
>> > >From Windows to Linux, servers to mobile, InstallShield X is the one
>> > installation-authoring solution that does it all. Learn more and
>> > evaluate today! http://www.installshield.com/Dev2Dev/0504
>> > _______________________________________________
>> > Oscar-users mailing list
>> > [EMAIL PROTECTED]
>> > https://lists.sourceforge.net/lists/listinfo/oscar-users
>> https://lists.sourceforge.net/lists/listinfo/oscar-users
>>
>>
>> ---------------------------------------------
>> Department of Earth Sciences
>> University of Cambridge
>> Downing Street
>> Cambridge CB2 3EQ
>> Phone: ( +44 ) 1223 333400
>> Fax: ( +44 ) 1223 333450
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by the new InstallShield X.
>> >From Windows to Linux, servers to mobile, InstallShield X is the one
>> installation-authoring solution that does it all. Learn more and
>> evaluate today! http://www.installshield.com/Dev2Dev/0504
>> _______________________________________________
>> Oscar-users mailing list
>> [EMAIL PROTECTED]
>> https://lists.sourceforge.net/lists/listinfo/oscar-users
>
>--
>Benoit des Ligneris Ph. D.
>President de Revolution Linux     http://www.revolutionlinux.com/
>OSCAR Chair                    http://oscar.openclustergroup.org/
>Chef de projet EduLinux                  http://www.edulinux.org/




-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users

Reply via email to