Bernard
I'm now able to successfully do a FC4 autoinstall via pxe to
PDSMi mobo boxes with intel 82573 gigabit ethernet interfaces.
Summary of actions:
Removed old (3.2.0-4) systemimager RPMs from image
server & golden client.
Removed old (2.0.9-1) systemconfigurator RPMs from
imager server & golden client.
Removed old /var/lib/systemimager/ area on image server.
Removed old /etc/systemimager/ area.
Obtained & installed on image server:
perl-XML-Simple-2.14-2.fc4.noarch.rpm
perl-AppConfig-1.52-4.noarch.rpm
systemconfigurator-2.2.2-1.noarch.rpm
systemimager-common-3.7.3-1.noarch.rpm
systemimager-i386boot-standard-3.7.3-1.noarch.rpm
systemimager-server-3.7.3-1.noarch.rpm
Obtained & installed on golden client:
perl-AppConfig-1.52-4.noarch.rpm
systemconfigurator-2.2.2-1.noarch.rpm
systemimager-client-3.7.3-1.noarch.rpm
systemimager-common-3.7.3-1.noarch.rpm
systemimager-i386initrd_template-3.7.3-1.noarch.rpm
On golden client:
si_prepareclient --server SERVER_IP
On imager server:
si_getimage --golden-client GOLDENCLIENT_IP --image IMAGE_NAME
--ip-assignment DHCP
Copied the standard 3.7.3-1 systemimager kernel & initrd.img to /tftpboot
from /usr/share/systemimager/boot/i386/standard/.
Booted client to be autoinstalled, with pxe network boot bios
setting active.
Autoinstall then proceeded without problems, and resulted in the
expected hard-disk bootable clone of the golden client (with its
expected unique IP identity).
Note that the uyok kernel and initrd.img that were produced
by the 3.7.3-1 si_prepareclient (under the golden client's
/etc/systemimager/boot) failed when this kernel attempted
to start up during autoinstall. [Message: "No init found".]
But the standard kernel and initrd.img included with 3.7.3-1
systemimager worked fine, and it apparently included an e1000
ethernet driver that is functional with the i82573 interfaces
on PDSMi mobos.
-bill
> -----Original Message-----
> From: Bernard Li
> Sent: Wed 16/08/2006 15:11
> To: [email protected]
> Subject: RE: [Sisuite-users] SuperMicro PDSMi i82573 support in si =
> kernel
> Hi Bill:
>
> I started using SystemImager with 3.2.3 and I have limited direct =
> experience with SystemImager because I mostly use it in the context of =
> OSCAR, however I do not believe the underlying idea of SystemImager has =
> changed much over the years, the idea is still the same - you setup =
> golden image, you set it up and deploy it. Command names changed (eg. =
> every command is prepended with si_) and there are new features like =
> monitoring where you can visualize your imaging progress, and virtual =
> console where you'll get the client's console message during imaging, =
> and UYOK which allows better support for different hardware.
>
> So I guess short answer is no, you should be able to figure it out - if =
> not, there are documentations in wiki.systemimager.org and we're always =
> here to help you with your problems :-)
>
> Cheers,
>
> Bernard
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] on behalf of Bill =
> McKie
> Sent: Wed 16/08/2006 14:54
> To: [email protected]
> Subject: Re: [Sisuite-users] SuperMicro PDSMi i82573 support in si =
> kernel
> =20
> Hi Bernard
>
> I noted preliminary functional problems with the e1000 driver
> for PDSMi's 82573 nics during initial linux system install
> from the standard FC4 ISO CD distribution. This e1000 was the
> one included with the initial FC4 kernel 2.6.11-1.1369_FC4smp,
> and only 1 of the 2 82573 nics was operating with this kernel.
>
> After downloading the 2.6.17-1.2141_FC4smp kernel update, both
> 82573 nics appeared to function ok. And this continues with the
> latest FC4 kernel 2.6.17-1.2142_FC4smp.
>
> So it appears that the version of e1000 somewhere between
> 2.6.11-1.1369 and 2.6.17-1.2142 FC4 kernels is needed to at
> least begin to use both 82573 nics on a PDSMi box. I.e. I
> cannot say from my bracket of kernels (2.6.11-1 - 2.6.17-1)
> if the e1000 included with 2.6.16.5 will be adequate.
>
> Although I may go ahead with further testing using our small
> testbed of 3 PDSMi boxes, after hearing of Jeff's bad additional
> experiences with the PDSMi's 82573 nics, it is not certain that
> my group will want to proceed with a large cluster built from
> PDSMi boxes.
>
> I'd be glad to test a version of SystemImager that contains
> the lastest e1000 in its standard SI boot kernel on our PDSMi
> boxes. Is your latest SI signficantly different to set up
> and use compared to our current v3.2.0-4?
>
> Thanks,
> -bill=20
>
>
>
> ------_=_NextPart_001_01C6C246.CD02E55F
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
> <HTML>
> <HEAD>
> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
> charset=3Diso-8859-1">
> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
> 6.5.7638.1">
> <TITLE>FW: [Sisuite-users] SuperMicro PDSMi i82573 support in si =
> kernel</TITLE>
> </HEAD>
> <BODY>
> <!-- Converted from text/plain format -->
>
> <P><FONT SIZE=3D2>Re-send...<BR>
> <BR>
> <BR>
> -----Original Message-----<BR>
> From: Bernard Li<BR>
> Sent: Wed 16/08/2006 15:11<BR>
> To: [email protected]<BR>
> Subject: RE: [Sisuite-users] SuperMicro PDSMi i82573 support in si =
> kernel<BR>
> <BR>
> Hi Bill:<BR>
> <BR>
> I started using SystemImager with 3.2.3 and I have limited direct =
> experience with SystemImager because I mostly use it in the context of =
> OSCAR, however I do not believe the underlying idea of SystemImager has =
> changed much over the years, the idea is still the same - you setup =
> golden image, you set it up and deploy it. Command names changed =
> (eg. every command is prepended with si_) and there are new features =
> like monitoring where you can visualize your imaging progress, and =
> virtual console where you'll get the client's console message during =
> imaging, and UYOK which allows better support for different =
> hardware.<BR>
> <BR>
> So I guess short answer is no, you should be able to figure it out - if =
> not, there are documentations in wiki.systemimager.org and we're always =
> here to help you with your problems :-)<BR>
> <BR>
> Cheers,<BR>
> <BR>
> Bernard<BR>
> <BR>
> <BR>
> -----Original Message-----<BR>
> From: [EMAIL PROTECTED] on behalf of Bill =
> McKie<BR>
> Sent: Wed 16/08/2006 14:54<BR>
> To: [email protected]<BR>
> Subject: Re: [Sisuite-users] SuperMicro PDSMi i82573 support in si =
> kernel<BR>
> <BR>
> Hi Bernard<BR>
> <BR>
> I noted preliminary functional problems with the e1000 driver<BR>
> for PDSMi's 82573 nics during initial linux system install<BR>
> from the standard FC4 ISO CD distribution. This e1000 was the<BR>
> one included with the initial FC4 kernel 2.6.11-1.1369_FC4smp,<BR>
> and only 1 of the 2 82573 nics was operating with this kernel.<BR>
> <BR>
> After downloading the 2.6.17-1.2141_FC4smp kernel update, both<BR>
> 82573 nics appeared to function ok. And this continues with =
> the<BR>
> latest FC4 kernel 2.6.17-1.2142_FC4smp.<BR>
> <BR>
> So it appears that the version of e1000 somewhere between<BR>
> 2.6.11-1.1369 and 2.6.17-1.2142 FC4 kernels is needed to at<BR>
> least begin to use both 82573 nics on a PDSMi box. I.e. I<BR>
> cannot say from my bracket of kernels (2.6.11-1 - 2.6.17-1)<BR>
> if the e1000 included with 2.6.16.5 will be adequate.<BR>
> <BR>
> Although I may go ahead with further testing using our small<BR>
> testbed of 3 PDSMi boxes, after hearing of Jeff's bad additional<BR>
> experiences with the PDSMi's 82573 nics, it is not certain that<BR>
> my group will want to proceed with a large cluster built from<BR>
> PDSMi boxes.<BR>
> <BR>
> I'd be glad to test a version of SystemImager that contains<BR>
> the lastest e1000 in its standard SI boot kernel on our PDSMi<BR>
> boxes. Is your latest SI signficantly different to set up<BR>
> and use compared to our current v3.2.0-4?<BR>
> <BR>
> Thanks,<BR>
> -bill<BR>
> <BR>
> <BR>
> </FONT>
> </P>
>
> </BODY>
> </HTML>
> ------_=_NextPart_001_01C6C246.CD02E55F--
>
>
> --===============1135948040==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> --===============1135948040==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> _______________________________________________
> Sisuite-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sisuite-users
>
> --===============1135948040==--
>
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
