<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16735" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=436261523-19112008><FONT face=Arial
color=#0000ff size=2>Yes, it is busybox-based, and yes, the final kernel is
definitely getting run, as evidenced by 'uname -a' output at the
busybox</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=436261523-19112008><FONT face=Arial
color=#0000ff size=2>prompt. The file '/dev/sda' does exist.. I don't
remember the major/minor numbers, etc.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=436261523-19112008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=436261523-19112008><FONT face=Arial
color=#0000ff size=2>My .config file is attached. I am not modifying the
skeleton/* files.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=436261523-19112008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=436261523-19112008><FONT face=Arial
color=#0000ff size=2>-Bijoy</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Myles Watson [mailto:mylesgw@gmail.com]
<BR><B>Sent:</B> Wednesday, November 19, 2008 3:24 PM<BR><B>To:</B> Anose,
Bijoy K (N-Aerotek)<BR><B>Cc:</B> Ward Vandewege; Coreboot<BR><B>Subject:</B>
Re: [coreboot] Coreboot on Tyan S2892<BR></FONT><BR></DIV>
<DIV></DIV><BR><BR>
<DIV class=gmail_quote>On Wed, Nov 19, 2008 at 2:12 PM, Anose, Bijoy K
(N-Aerotek) <SPAN dir=ltr><<A
href="mailto:bijoy.k.anose@lmco.com">bijoy.k.anose@lmco.com</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>I
enabled the busybox option and used the default value of "5 second pause to
allow access to busybox" but it doesn't</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>pause
anywhere, as far as I can tell. Coreboot starts, LAB starts, LAB
kexecs the kernel/initrd on the SATA disk, and</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>then at
that busybox prompt, I get no output when I issue "fdisk -l
/dev/sda".</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><BR>So your kernel/initrd is busybox-based as well? Is the new
kernel really getting run?<BR><BR>I'd start with ls -l /dev/sda or something
simple like that.<BR> </DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff
size=2></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>Could
you send me a tarball of your
buildrom-devel?</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV>Since it's old I don't think that would be really helpful. Are you
changing the .config files? Are you changing the skeleton/
files?<BR> <BR></DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>
Something must be different in our config. Also your lab.conf
and</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>the
kernel/initrd that is on your SATA disk, if that would
ok.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV>I don't have that machine up right now, so it would take a while. I
think there's a shorter path to the answer than that.<BR> </DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>I built
my own static kexec and xfer'd it to the SATA
drive.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV>Great. <BR></DIV>
<DIV> </DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>Multiple
drives shouldn't make any difference -- if the controller can see one drive,
it can see them all (if it is actually</FONT></SPAN></DIV>
<DIV><SPAN><FONT face=Arial color=#0000ff size=2>working
properly). </FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<DIV><BR>You're right. If they don't all work it's a bug. Maybe
it's been fixed. If you're only using two drives, though, it's probably
not that.<BR> </DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV><SPAN><FONT face=Arial color=#0000ff size=2>My system may have 2 drives
or 8, depending on its function. The one I'm currently
experimenting</FONT></SPAN> <BR></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff
size=2></FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>with has
only 2 installed.</FONT></SPAN></DIV></DIV></BLOCKQUOTE>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff
size=2></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff
size=2>-Bijoy</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN><FONT face=Arial color=#0000ff size=2>(sorry
again for top-posting, Outlook is acting differently over VPN/rdesktop for
some reason)</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,255) 2px solid; MARGIN-RIGHT: 0px">
<DIV lang=en-us dir=ltr align=left>
<HR>
<FONT face=Tahoma size=2><B>From:</B> Myles Watson [mailto:<A
href="mailto:mylesgw@gmail.com" target=_blank>mylesgw@gmail.com</A>]
<BR><B>Sent:</B> Wednesday, November 19, 2008 11:19 AM
<DIV class=Ih2E3d><BR><B>To:</B> Anose, Bijoy K
(N-Aerotek)<BR></DIV><B>Cc:</B> Ward Vandewege; Coreboot
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c><BR><B>Subject:</B> Re: [coreboot] Coreboot on Tyan
S2892<BR></DIV></DIV></FONT><BR></DIV>
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c>
<DIV></DIV><BR><BR>
<DIV class=gmail_quote>On Wed, Nov 19, 2008 at 9:40 AM, Anose, Bijoy K
(N-Aerotek) <SPAN dir=ltr><<A href="mailto:bijoy.k.anose@lmco.com"
target=_blank>bijoy.k.anose@lmco.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>> From: Ward Vandewege [mailto:<A href="mailto:ward@gnu.org"
target=_blank>ward@gnu.org</A>]<BR></DIV>> Sent: Thursday, November
13, 2008 6:56 PM<BR>
<DIV>> To: Anose, Bijoy K (N-Aerotek)<BR>> Cc: Myles Watson; Marc
Jones; Coreboot<BR>> Subject: Re: [coreboot] Coreboot on Tyan
S2892<BR>><BR></DIV>
<DIV>> On Thu, Nov 13, 2008 at 07:04:49PM -0500, Anose, Bijoy
K<BR>> (N-Aerotek) wrote:<BR>> > > So far it's just me
seeing that, on one specific board<BR>> (s2891). So<BR>> > >
don't worry about that too much just yet.<BR>> ><BR>> >
True, I'll cross that bridge when I get there.<BR>> ><BR>> >
First I'll need to be able to boot, period. So far, what<BR>>
I've done is<BR><SPAN><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN>> > this:<BR>> ><BR>>
> 1. Subversion checkout of latest buildrom 2. make
menuconfig,<BR>> > specifying Tyan S2892, 32-bit LAB 3.
make<BR>> ><BR>> > Do I need to do further
configuration (Config.lb etc)? I<BR>> thought that<BR>> >
the menuconfig took care of everything. Maybe that was
wishful<BR>> > thinking..<BR>><BR>> It's not. The only other
thing you need to do is *pre*pend<BR>> the vga image to the generated
image, which will generate an<BR>> image that is exactly 1024KB
large, and which you can flash,<BR>> and which *should* just boot
your system.<BR>><BR><BR></DIV>I finally got coreboot+LAB to boot my
target kernel/initrd on the SATA<BR>disks (many thanks to
Ward)!<BR><BR>However, once the init script in the initrd attempts to
assembly the<BR>software<BR>RAID, it fails because it can't see the SATA
disks.</BLOCKQUOTE>
<DIV>How many do you have? Ward has seen a problem with some disk
controllers not functioning on the ck804. I've never used more than
one.<BR> <BR></DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">My
guess is that coreboot is originally doing some low level block
reads<BR>from<BR>the disk to load the kernel/initrd but when the final
kernel attempts to<BR>do a<BR>SATA read from the disk, the controller
has not been fully/properly<BR>initialized,<BR>and it fails.</BLOCKQUOTE>
<DIV><BR>Have you tried configure the busybox shell to not load
automatically, and looked at the SATA drives from there?<BR><BR></DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">I
assume that whatever modifications that Myles made to
successfully<BR>boot from<BR>SATA devices with coreboot+LAB on S2892
have trickled down to buildrom..</BLOCKQUOTE>
<DIV>I used buildrom. I think the multiple drives may be getting
you, though.
<BR><BR>Thanks,<BR>Myles<BR></DIV></DIV><BR></DIV></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>