<br><br><div class="gmail_quote">On Thu, Dec 4, 2008 at 3:25 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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">That seemed to be the case, but it is not exactly
correct. The LAB kernel (and kernels I've built) consistently are only
seeing</font></span></div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">part of the drives. The two drives in my setup each
have 1 partition that is outside any swraid, and several partitions that
are</font></span></div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">in a raid1 between the two drives.</font></span></div>
</div></blockquote><div><br>I wish I knew more about swraid. Hopefully someone else on the list will know more.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">Each time I boot and kexec my target kernel from LAB,
creation of the swraid is failing. It complains that it can't find
/dev/sda2</font></span></div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">(part of the swraid). However, I can manually mount
/dev/sda1 without issues.</font></span></div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">The whole boot process (including the swraid assembly, etc)
has always been successful when booting with legacy BIOS.</font></span></div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">To be clear, we do not use the onboard RAID controller at
all.</font></span></div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial"></font></span> </div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">It appears to me that coreboot is maybe not fully/correctly
initializing the SATA controller as the BIOS is.</font></span></div>
</div></blockquote><div>This is very possible. Are there any illuminating error messages when the drive fails to mount? Have you compared a very verbose lspci of the SATA controller? lspci -vvxxx<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">Also, I'm curious what other cards, if any, you had in your
machine when you were able to boot successfully? Eventually,
I</font></span></div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">need to be able to boot with some multi-port serial cards
and a multi-port NIC (a Broadcom card that Stepan and others
have</font></span></div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">seen issues with). Right now, with coreboot I get no
VGA or serial console output whatsoever when those are
present</font></span><span><font size="2" color="#0000ff" face="Arial">, so I've</font></span></div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">been doing all my experimenting with those cards
removed.</font></span></div>
</div></blockquote><div><br>I've never used any cards in the machine. Just a HyperTransport module.<br><br>Thanks,<br>Myles<br><br><br><br><br>
<blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div dir="ltr" align="left" lang="en-us">
<hr>
<font size="2" face="Tahoma"><div class="Ih2E3d"><b>From:</b> Myles Watson [mailto:<a href="mailto:mylesgw@gmail.com" target="_blank">mylesgw@gmail.com</a>]
<br></div><b>Sent:</b> Thursday, November 20, 2008 11:47 AM<div><div class="Wj3C7c"><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></div></div></font><br></div><div><div class="Wj3C7c">
<br><br>
<div class="gmail_quote">On Thu, Nov 20, 2008 at 10:24 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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">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><font size="2" color="#0000ff" face="Arial">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></span> </div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">My
.config file is attached. I am not modifying the skeleton/*
files.</font></span></div>
<div><span></span> <br></div>
<div dir="ltr" align="left"><span></span></div></div></blockquote>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">-Bijoy</font></span></div></div></blockquote>
<div><br>All right. The only differences I see
are that you are building on a 32-bit machine and you're building a 32-bit LAB
image.<br>CONFIG_TARGET_64BIT<br>CONFIG_CHOOSE_64BIT<br><br>Since your kernel
gets loaded, I don't see why either of those should matter. It seems
like there's a difference between the way your LAB kernel and your regular
kernel are handling the SATA drive. Since the LAB kernel finds and reads
it, but yours doesn't...<br><br>I hope that
helps.<br><br>Thanks,<br>Myles<br><br><br><br><br><br></div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br>
<blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div dir="ltr" align="left" lang="en-us">
<hr>
<font size="2" face="Tahoma">
<div><b>From:</b> Myles Watson [mailto:<a href="mailto:mylesgw@gmail.com" target="_blank">mylesgw@gmail.com</a>]
<br></div><b>Sent:</b> Wednesday, November 19, 2008 3:24 PM
<div><br><b>To:</b> Anose, Bijoy K (N-Aerotek)<br></div>
<div>
<div><b>Cc:</b> Ward Vandewege; Coreboot<br><b>Subject:</b>
Re: [coreboot] Coreboot on Tyan S2892<br></div></div></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" target="_blank">bijoy.k.anose@lmco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">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 size="2" color="#0000ff" face="Arial">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 size="2" color="#0000ff" face="Arial">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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span></span></div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial"> Something must be different in our config. Also your
lab.conf and</font></span></div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">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 size="2" color="#0000ff" face="Arial">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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div><span><font size="2" color="#0000ff" face="Arial">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></span></div></div></blockquote>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">with
has only 2 installed.</font></span></div></div></blockquote>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><span></span></div>
<div dir="ltr" align="left"><span></span> </div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">-Bijoy</font></span></div>
<div dir="ltr" align="left"><span></span> </div>
<div dir="ltr" align="left"><span><font size="2" color="#0000ff" face="Arial">(sorry again for top-posting, Outlook is acting differently over
VPN/rdesktop for some reason)</font></span></div><br>
<blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div dir="ltr" align="left" lang="en-us">
<hr>
<font size="2" face="Tahoma"><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><br><b>To:</b> Anose, Bijoy K
(N-Aerotek)<br></div><b>Cc:</b> Ward Vandewege; Coreboot
<div>
<div><br><b>Subject:</b> Re: [coreboot] Coreboot on
Tyan S2892<br></div></div></font><br></div>
<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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<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 size="2" color="#0000ff" face="Arial"> </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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">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></div></div></blockquote></div></blockquote></div><br></div></div></blockquote></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
</blockquote></div><br>