[coreboot] Coreboot on Tyan S2892

Anose, Bijoy K (N-Aerotek) bijoy.k.anose at lmco.com
Wed Nov 19 17:40:54 CET 2008


> From: Ward Vandewege [mailto:ward at gnu.org] 
> Sent: Thursday, November 13, 2008 6:56 PM
> To: Anose, Bijoy K (N-Aerotek)
> Cc: Myles Watson; Marc Jones; Coreboot
> Subject: Re: [coreboot] Coreboot on Tyan S2892
> 
> On Thu, Nov 13, 2008 at 07:04:49PM -0500, Anose, Bijoy K 
> (N-Aerotek) wrote:
> > > So far it's just me seeing that, on one specific board 
> (s2891). So 
> > > don't worry about that too much just yet.
> > 
> > True, I'll cross that bridge when I get there.
> > 
> > First I'll need to be able to boot, period.  So far, what 
> I've done is
> > this:
> > 
> > 1.  Subversion checkout of latest buildrom 2.  make menuconfig, 
> > specifying Tyan S2892, 32-bit LAB 3.  make
> > 
> > Do I need to do further configuration (Config.lb etc)?  I 
> thought that 
> > the menuconfig took care of everything.  Maybe that was wishful 
> > thinking..
> 
> It's not. The only other thing you need to do is *pre*pend 
> the vga image to the generated image, which will generate an 
> image that is exactly 1024KB large, and which you can flash, 
> and which *should* just boot your system.
> 

I finally got coreboot+LAB to boot my target kernel/initrd on the SATA
disks (many thanks to Ward)!

However, once the init script in the initrd attempts to assembly the
software
RAID, it fails because it can't see the SATA disks.  The same disk boots
fine
when I boot with the legacy BIOS installed.

My guess is that coreboot is originally doing some low level block reads
from
the disk to load the kernel/initrd but when the final kernel attempts to
do a
SATA read from the disk, the controller has not been fully/properly
initialized,
and it fails.

I assume that whatever modifications that Myles made to successfully
boot from
SATA devices with coreboot+LAB on S2892 have trickled down to buildrom..

Are there other tweaks I need to make, Myles?

-Bijoy




More information about the coreboot mailing list