[coreboot] LNXI eVelocity 2 BIOS reburn

Stefan Reinauer stepan at coresystems.de
Fri Sep 4 16:01:47 CEST 2009

Sebastian Lara wrote:
> Hi,
> 2009/9/3 Stefan Reinauer <stepan at coresystems.de>:
>> Sebastian Lara wrote:
>>> Hi,
>>> I'm trying to revive a Linux Netwox eVelocity 2 Cluster with
>>> LinuxBIOS- and Etherboot 5.2 on compute nodes. After some
>>> trouble, I have access to a shell after node system installation over
>>> network. My problem now is that I can't get localboot to work.
>> What's the error?
> Boot from (N)etwork (D)isk or (Q)uit? D
> Probing pci disk...
> [IDE]LBA48 mode
> disk-1 78150744k cap: 2f00
> Searching for image...
> ................................<abort>
> Probing pci disk...
> [IDE]
> Probing isa disk...
> <sleep>
> Etherboot searches for an ELF header in the first 8K. I don't really
> know how can I do this. I had tried to use a ELF image of the kernel
> installed in the node but it doesn't work.

I think you need to run "mkelfimage" on a Linux kernel in order to get
it booted and dump that directly on the first partition

>>> I need to know if I can re-burn the BIOS with a newer version of
>>> coreboot or something else, so I can use PXE and use GRUB for booting
>>> from local.
>> What mainboard type is that? Can you post a boot log from serial console?
> It's there some way to know the mainboard type without open a node
> case? Get permission to do that may take some time.
if you can run "nvramtool" from a current coreboot tree on that node, it
can dump the fields

> Here is the boot log:

> Found ELF candiate at offset 0
> Loading Etherboot version: 5.2.4js1
> Dropping non PT_LOAD segment
> New segment addr 0x20000 size 0x41e65 offset 0xc0 filesize 0x993a
> (cleaned up) New segment addr 0x20000 size 0x41e65 offset 0xc0 filesize 0x993a
> Loading Segment: addr: 0x000000007ffc4000 memsz: 0x0000000000010000
> filesz: 0x000000000000993a
> Clearing Segment: addr: 0x000000007ffcd93a memsz: 0x00000000000066c6
> Loading Segment: addr: 0x0000000000030000 memsz: 0x0000000000031e65
> filesz: 0x0000000000000000
> Clearing Segment: addr: 0x0000000000030000 memsz: 0x0000000000031e65
> Jumping to boot code at 0x20000
> ROM segment 0x0000 length 0x0000 reloc 0x00020000
> CPU 2486 Mhz
> Etherboot 5.2.4js1 (GPL) http://etherboot.org ELF64 ELF with TFTP SLAM
> LACP for [EEPRO100][E1000][3C90X][TG3][IDE]
> Relocating _text from: [00029930,00063080) to [7fec68b0,7ff00000)
> �Probing pci nic... (D)isk or (Q)uit?
> [tg3-5702X]Ethernet addr: 00:50:45:5C:34:1A
> Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)] (PCI:66MHz:32-bit)
> Link is up at 100 Mbps, full duplex.
> Searching for server (DHCP)...
> ...Me:, Server:, Gateway
> Loading ...(ELF)... ................

Does booting over the network work?

More information about the coreboot mailing list