X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C85EB2.7CEE645A@onstor-exch02.onstor.net>; Thu, 24 Jan 2008 10:56:47 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C85EB2.7CEE645A"
References: <BB375AF679D4A34E9CA8DFA650E2B04E056C9306@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0779799B@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Boot issues with g9r204 and g10r204
Date: Thu, 24 Jan 2008 10:56:34 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E042F0053@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Boot issues with g9r204 and g10r204
Thread-Index: AchePu0VU5GqpLYoQGy82T7Iq36SLgAAM02vAByuugc=
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Ken Renshaw" <ken.renshaw@onstor.com>,
	"Vikas Saini" <vikas.saini@onstor.com>
Cc: "Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C85EB2.7CEE645A
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Yes.


-----Original Message-----
From: Ken Renshaw
Sent: Wed 1/23/2008 8:15 PM
To: Larry Scheer; Vikas Saini
Cc: Andy Sharp
Subject: RE: Boot issues with g9r204 and g10r204
=20
Thanks for plodding through it guys.=20

So I need to locally modify cougar-config for the time being for my =
builds, correct?=20

-Ken


-----Original Message-----
From: Larry Scheer
Sent: Wed 1/23/2008 8:09 PM
To: Vikas Saini; Ken Renshaw
Cc: Andy Sharp
Subject: Boot issues with g9r204 and g10r204
=20
Ken, Vikas,
   Got the issue sorted out. The reason my system (g4r5) booted with the =
default (Ken's build) kernel configuration was because that system had a =
compact flash loaded with a release. When it booted it mounted the =
compact flash and is using the SSC daemons and Linux from the flash and =
not the NFS root.

Andy looked at this issue and determined this is a PROM bug. The PROM is =
not constructing the correct command line after boot. We should be able =
to build the kernel with the default boot command line (as it is =
currently checked into Perforce) and the PROM should create the correct =
boot arguments in the case of a network boot.=20

Andy has notified Rick Lund of the situation. We won't be changing the =
kernel source in perforce. So for the time being the work-around is to =
modify linux/kernel/linux-mips-2.6/cougar-config in your local workspace =
until the PROM is fixed.

Larry



------_=_NextPart_001_01C85EB2.7CEE645A
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.7653.38">
<TITLE>RE: Boot issues with g9r204 and g10r204</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Yes.<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Ken Renshaw<BR>
Sent: Wed 1/23/2008 8:15 PM<BR>
To: Larry Scheer; Vikas Saini<BR>
Cc: Andy Sharp<BR>
Subject: RE: Boot issues with g9r204 and g10r204<BR>
<BR>
Thanks for plodding through it guys.<BR>
<BR>
So I need to locally modify cougar-config for the time being for my =
builds, correct?<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Larry Scheer<BR>
Sent: Wed 1/23/2008 8:09 PM<BR>
To: Vikas Saini; Ken Renshaw<BR>
Cc: Andy Sharp<BR>
Subject: Boot issues with g9r204 and g10r204<BR>
<BR>
Ken, Vikas,<BR>
&nbsp;&nbsp; Got the issue sorted out. The reason my system (g4r5) =
booted with the default (Ken's build) kernel configuration was because =
that system had a compact flash loaded with a release. When it booted it =
mounted the compact flash and is using the SSC daemons and Linux from =
the flash and not the NFS root.<BR>
<BR>
Andy looked at this issue and determined this is a PROM bug. The PROM is =
not constructing the correct command line after boot. We should be able =
to build the kernel with the default boot command line (as it is =
currently checked into Perforce) and the PROM should create the correct =
boot arguments in the case of a network boot.<BR>
<BR>
Andy has notified Rick Lund of the situation. We won't be changing the =
kernel source in perforce. So for the time being the work-around is to =
modify linux/kernel/linux-mips-2.6/cougar-config in your local workspace =
until the PROM is fixed.<BR>
<BR>
Larry<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C85EB2.7CEE645A--
