Re: LinuxSSI x86_64 bit

Thanks for getting back to me Scott,

I have now just re-started again on the install and have gotten back to step number 10, but had a question.

I added the "e1000" for the network on eth1 to the /etc/mkinitrd/modules file and am just about to run the mkinitrd like you mentioned in you last email, but had a question.

In doing ls on the current /boot I noticed we have not put in a ssi image from the documentation, but that your email suggested that I do that

> mkinitrd -o /boot/initrd.img-2.6.14-ssi-686-smp 2.6.14-ssi-686-smp

for the 64-bit AMD image that will be installed in step number 17 on the document where it asks me to use the one:

linux-image-2.6.12-ssi-amd64

So if I do not have an image for this in the /boot then how can I run mkinitrd for it?

Thanks and have a great day,
Lonnie Cumberland, Prof.
Physicist

National Institute of Standards and Technology
Ionizing Radiation Division (846)
Radiation Physics Group (245), Room C106
ADDRESS:
                 100 Bureau Drive, Stop 8462
                Gaithersburg, MD 20899-8462
 
EMAIL: [email protected]
http://physics.nist.gov/Divisions/Div846/div846.html



-----Original Message-----
From: Scott Walters [mailto:[email protected]] 
Sent: Monday, June 28, 2010 12:49 PM
To: Cumberland, Lonnie
Cc: [email protected]
Subject: Re: [SSI-users] LinuxSSI x86_64 bit

Oh yeah, you're on the x86-64 version.  The identifier for you will be
slightly different.  Do uname -a and pick out the third token.
(Obviously that heuristic will be wrong if you're building an initrd
for a different kernel than you're running but that shouldn't come
up... the apt upgrade process for OpenSSI's kernel should handle that
for you).

-scott

On 6/28/10, Scott Walters <[email protected]> wrote:
> Hi Lonnie,
>
> Ahh, I forgot that that does take arguments or I would have gave examples.
>
> mkinitrd -o /boot/initrd.img-2.6.14-ssi-686-smp 2.6.14-ssi-686-smp
>
> That's a Linux-ism.  The kernel, care of make menuconfig or otherwise,
> has an identifier that includes the version, target CPU, 'smp' or
> similar things, and so on.  The kernel looks for its modules inside
> the initrd image (init ramdisk image, I think that means) and in
> /lib/modules in a directory named after this identifier.  This keeps
> kernels from trying to load modules from other kernel versions that
> just aren't compat.  Since you may be using one kernel to generate an
> initrd for a different kernel, it requires you to specify.  In the
> case of the 1st argument, that has to match what's specified for the
> initrd in the bootloader, since the name of the initrd file is
> specified to the kernel at boot time.
>
> And yeah, this is all a bit silly, normally.  It's essential for
> netbooting as in the case of OpenSSI, but on systems such as plain old
> Fedora, it's possible to do away with the initrd entirely in most
> cases.  People love to throw additional stages at the Linux
> bootloading process.
>
> Anyway, I have that command with arguments in a little .sh script in
> root's home directory with 'ssi-ksync' immediately following it.
>
> Cheers,
> -scott
>
> On 6/28/10, Cumberland, Lonnie <[email protected]> wrote:
>> Greetings All,
>>
>> Well, another attempt on getting the OpenSSI installed on my AMD 64-bit
>> main
>> node and have been following the
>>
>> http://openssi.org/cgi-bin/view?page=openssi.html
>>
>> exactly as it specifies, but cannot seem to get past step number 18 where
>> I
>> reboot the machine.
>>
>> Not sure what is going on with the system, but think that it has to do
>> with
>> the step 10 and mkinitrd where I add in my network card information
>> "e1000"
>> although I am not sure.
>>
>> Any help would be greatly appreciated since I am at a loss at this point.
>>
>> Thanks and have a great day,
>> Lonnie Cumberland, Prof.
>> Physicist
>>
>> National Institute of Standards and Technology
>> Ionizing Radiation Division (846)
>> Radiation Physics Group (245), Room C106
>> ADDRESS:
>>                  100 Bureau Drive, Stop 8462
>>                 Gaithersburg, MD 20899-8462
>>
>> EMAIL: [email protected]
>> http://physics.nist.gov/Divisions/Div846/div846.html
>>
>>
>>
>

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first