Re: [coreboot] Which file should I burn?

[Rick Ant]

Hello,

then I will burn the bios.bin into the flash ROM chip 49LF004, the original BIOS system will be removed ?
and 
disk.img into Compact flash...

Am I right in this point ?

Thanks

--- On Tue, 6/23/09, David Hendricks  wrote:

From: David Hendricks 
Subject: Re: [coreboot] Which file should I burn?
To: "Rick Ant" 
Cc: [e-mail]
Date: Tuesday, June 23, 2009, 7:49 PM

On Tue, Jun 23, 2009 at 7:06 PM, Rick Ant  wrote:

I got this message :
=================
boot: hda:/boot/vmlinuz root=/dev/hda initrd=/boot/initrd console=ttyS0
hda: LBA48 524MB: QEMU HARDDISK
Mounted ext2fs
Found Linux version 2.6.16.5 (root@e-smith) #2 PREEMPT Sat Sep 22 00:14:46 Local time zone must be set--see  bzImage.

Loading kernel... ok
Loading initrd... ok
Jumping to entry point...

==============
Is the coreboot working fine ? or not yet ?
Can I write it to Compact flash for real boot ?
How ? Which file should I burn ? the bios.bin?

Thanks
Yep, Coreboot is working fine and you're squarely in kernel mode at this point. Make sure you have all the requisite serial driver support compiled statically into your kernel (Device Drivers --> Character Devices --> Serial Drivers) so you can see the kernel messages.

Copy your system image to your storage media (compact flash?) as you normally would and try it out with the vendor BIOS first to verify that the system image + kernel work fine on real hardware. If you're comfortable with the QEMU trial results, and you have a sane way of recovering the vendor BIOS, use flashrom to burn the new Coreboot image to the firmware ROM.

Which file should I burn?

[David Hendricks]

Correct, the original BIOS image will be removed / replaced with your new
Coreboot image.

I recommend that you test your system image (disk.img?) separately from your
Coreboot image. There are many, many things that can go wrong in this
process. If you try to apply all of your changes at once, it will be more
difficult to solve any problems that come up.

On Tue, Jun 23, 2009 at 8:38 PM, Rick Ant  wrote:
> Hello,
>
> then I will burn the bios.bin into the flash ROM chip 49LF004, the original
> BIOS system will be removed ?
> and
> disk.img into Compact flash...
>
> Am I right in this point ?
>
> Thanks
>
> --- On *Tue, 6/23/09, David Hendricks * wrote:
>
> From: David Hendricks 
> Subject: Re: [coreboot] Which file should I burn?
> To: "Rick Ant" 
> Cc: [e-mail]
> Date: Tuesday, June 23, 2009, 7:49 PM
>
> On Tue, Jun 23, 2009 at 7:06 PM, Rick Ant <[e-mail]://mc/compose?to=[e-mail]
> > wrote:
> > I got this message :
> >
> > boot: hda:/boot/vmlinuz root=/dev/hda initrd=/boot/initrd console=ttyS0
> > hda: LBA48 524MB: QEMU HARDDISK
> > Mounted ext2fs
> > Found Linux version 2.6.16.5 (root@e-smith) #2 PREEMPT Sat Sep 22
> > 00:14:46 Local time zone must be set--see bzImage.
> > Loading kernel... ok
> > Loading initrd... ok
> > Jumping to entry point...
> >
> > ==============
> > Is the coreboot working fine ? or not yet ?
> > Can I write it to Compact flash for real boot ?
> > How ? Which file should I burn ? the bios.bin?
> >
> > Thanks
>
> Yep, Coreboot is working fine and you're squarely in kernel mode at this
> point. Make sure you have all the requisite serial driver support compiled
> statically into your kernel (Device Drivers --> Character Devices --> Serial
> Drivers) so you can see the kernel messages.
>
> Copy your system image to your storage media (compact flash?) as you
> normally would and try it out with the vendor BIOS first to verify that the
> system image + kernel work fine on real hardware. If you're comfortable with
> the QEMU trial results, and you have a sane way of recovering the vendor
> BIOS, use flashrom to burn the new Coreboot image to the firmware ROM.