Re: 2.6.14-smp kernel headers and sources

"Cumberland, Lonnie" <[email protected]> Wed, 18 Aug 2010 12:57:23 -0400
Newsgroups gmane.linux.cluster.ssic.user
Message-ID <A3FD81D57663BD41BF701B44F5E75CE712D83BA6F0@MBCLUSTER.xchange.nist.gov>
Hello All,

Well, after testing a number of different things, it turns out that the mai=
n node seems to be running great and even the fuse module is working, but t=
hat the other nodes are not coming online. They seem to get the kernel, boo=
t the kernel and then crash out.

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

> -----Original Message-----
> From: Cumberland, Lonnie [mailto:[email protected]]
> Sent: Wednesday, August 18, 2010 10:18 AM
> To: John Hughes; Mulyadi Santosa
> Cc: Openssi users
> Subject: Re: [SSI-users] 2.6.14-smp kernel headers and sources
> =

> Hello All,
> =

> Well, there is good news and bad news.
> =

> The good news is that the compile went well although I did not know how
> to get the "make" commandline switches to SMP and i686 optizimations.
> =

> The bad news is that even though the kernel seems to boot ok on the
> main node, the other nodes do not seems to complete the booting
> properly and crash out after tftp send over the new kernel which I put
> into place via "ssi-ksync".
> =

> There was a document on the OpenSSI website that said to do:
> =

> # make oldconfig  		(by using the .config that was previously
> set up)
> # make dep        		(the compile reported that this was
> unnecessary now)
> # make bzImage    		(this went fine)
> # make modules    		(this went fine)
> # make modules_install    	(this went fine)
> =

> # cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.14_ssi  (this went well)
> =

> # mkinitrd --cfs /boot/initrd-2.6.14_ssi.img  2.6.14__ssi   (PROBLEMS
> HERE: /usr/sbin/mkinitrd: unrecognized option `--cfs')
> =

> Instead, I did:
> =

> # mkinitrd -o /boot/initrd-2.6.14_ssi.img  2.6.14__ssi  (since I did
> this in the install and it went well)
> =

> But still the other nodes do not seem to come online.
> =

> Any ideas on how to fix this?
> =

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

> > -----Original Message-----
> > From: John Hughes [mailto:[email protected]]
> > Sent: Wednesday, August 18, 2010 7:34 AM
> > To: Mulyadi Santosa
> > Cc: Cumberland, Lonnie; Openssi users
> > Subject: Re: [SSI-users] 2.6.14-smp kernel headers and sources
> >
> > Mulyadi Santosa wrote:
> > > On Wed, Aug 18, 2010 at 05:42, Cumberland, Lonnie
> > > <[email protected]> wrote:
> > >
> > >> I'll look to see what version I have tomorrow morning.
> > >>
> > >> Do I have to remove the whole 4.0 version if that is the problem
> and
> > install either 3.4 or 3.5 as you mentioned?
> > >>
> > >
> > > Nope, in Fedora/RHEL, this is usually called gcc-compat or compat-
> gcc
> > > to refer to the "old" gcc. So for example, if Fedora 5 provides gcc
> > > 3.x and 4.x, the 3.x is installed by gcc-compat. Thus, what you
> need
> > > to remove the gcc package (but not the compat one).
> > >
> > On Debian just install the gcc-3.4 package.
> >
> > apt-get install gcc-3.4
> >
> =

> =

> -----------------------------------------------------------------------
> -------
> This SF.net email is sponsored by
> =

> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Ssic-linux-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ssic-linux-users

---------------------------------------------------------------------------=
---
This SF.net email is sponsored by =


Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev =