OpenFirmware 3.5 and Netboot

Erlon Cruz sombrafam at gmail.com
Tue Jun 15 06:02:17 EST 2010


Hi Paul, thats is the output from the console. In terms of traffic, the
client request the boot file and loads it twice (I dont know why, and it
happens sometimes when loading a kernel image too). Theres no resquest of
any other file.

=================================================


TFTP BOOT ---------------------------------------------------

Server IP.....................192.168.1.1

Client IP.....................192.168.1.140

Gateway IP....................192.168.1.1

Subnet Mask...................255.255.255.0

( 1  ) Filename.................ppc/yaboot-debug

TFTP Retries..................5

Block Size....................512

FINAL PACKET COUNT = 889

FINAL FILE SIZE = 454942  BYTES



Elapsed time since release of system processors: 10325 mins 58 secs



Adding OF methods...

    prom_init - OF interface initialized.

    yaboot_start - Malloc buffer allocated at 00300000 (1048576 bytes)

    yaboot_start - reloc_offset :  0         (should be 0)

    yaboot_start - test_bss     :  0         (should be 0)

    yaboot_start - test_data    :  0         (should be 0)

    yaboot_start - &test_data   :  00233ff4

    yaboot_start - &test_bss    :  00233ff0

    yaboot_start - linked at    :  0x00200000

    yaboot_start - Running on _machine = 4

    yaboot_main - /chosen/bootargs =

    yaboot_main - /chosen/bootpath = /lhea at 23c00600/ethernet at 23e00f00
:speed=aut2
    netdev_path_to_filename - path = /lhea at 23c00600/ethernet at 23e00f00
:speed=aut2
    netdev_path_to_filename - null filename

    netdev_path_to_dev - path = /lhea at 23c00600/ethernet at 23e00f00
:speed=auto,dup2
    yaboot_main - After parse_device_path: dev=/lhea at 23c00600
/ethernet at 23e00f00=
    yaboot_main - After path kludgeup: dev=/lhea at 23c00600/ethernet at 23e00f00:,
pf
Try to netboot

    prom_get_netinfo - using /chosen/bootp-response

    open_file - dev_path = /lhea at 23c00600/ethernet at 23e00f00:

file_name = /etc/01-00-21-5e-b5-9a-0f

partition = -1

    open_file - device is a network device

--> of_net_open

    of_net_open - dev=/lhea at 23c00600/ethernet at 23e00f00:, part=0x00000000
(-1), f
    of_net_open - Opening: "/lhea at 23c00600/ethernet at 23e00f00
:,\etc\01-00-21-5e-"






    of_net_open - file->of_device = 01b47000

    prom_claim_chunk - claimed 16777216 at 0x2100000 (0x1000000)

    of_net_open - TFP...




TFTP BOOT ---------------------------------------------------

Server IP.....................192.168.1.1

Client IP.....................192.168.1.140

Gateway IP....................192.168.1.1

Subnet Mask...................255.255.255.0

( 1  ) Filename.................ppc/yaboot-debug

TFTP Retries..................5

Block Size....................512

FINAL PACKET COUNT = 889

FINAL FILE SIZE = 454942  BYTES

    of_net_open - result: 454942

<-- of_net_open - FILE_ERR_OK

Config file read, 32768 bytes

--> of_close

    of_close - <@01b47000>

    of_close - of_close called

<-- of_close - 0

Resetting image table

ItemA device = <NULL>

ItemB device = <NULL>



ItemA partition = <NULL>

ItemB partition = <NULL>



ItemA default = <NULL>

ItemB default = <NULL>



ItemA timeout = <NULL>

ItemB timeout = <NULL>



ItemA password = <NULL>

ItemB password = <NULL>



ItemA restricted = <NULL>

ItemB restricted = <NULL>



ItemA message = <NULL>

ItemB message = <NULL>



ItemA root = <NULL>

ItemB root = <NULL>



ItemA ramdisk = <NULL>

ItemB ramdisk = <NULL>



ItemA read-only = <NULL>

ItemB read-only = <NULL>



ItemA read-write = <NULL>

ItemB read-write = <NULL>



ItemA append = <NULL>

ItemB append = <NULL>



ItemA initrd = <NULL>

ItemB initrd = <NULL>



ItemA initrd-prompt = <NULL>

ItemB initrd-prompt = <NULL>



ItemA initrd-size = <NULL>

ItemB initrd-size = <NULL>



ItemA pause-after = <NULL>

ItemB pause-after = <NULL>



ItemA pause-message = <NULL>

ItemB pause-message = <NULL>



ItemA init-code = <NULL>

ItemB init-code = <NULL>



ItemA init-message = <NULL>

ItemB init-message = <NULL>




ItemA fgcolor = <NULL>

ItemB fgcolor = <NULL>



ItemA bgcolor = <NULL>

ItemB bgcolor = <NULL>



ItemA ptypewarning = <NULL>

ItemB ptypewarning = <NULL>



Can't set item ELF to value <NULL>
    prom_get_netinfo - using /chosen/bootp-response

    load_config_file - Config file successfully parsed, 32768 bytes

Welcome to yaboot version 1.3.14

Enter "help" to get some basic usage information

boot:

can't get <device_type> for device:

    get_params - after parse_device_path: dev= part=-1 file=/vmlinux

Please wait, loading kernel...

    open_file - dev_path =

file_name = /vmlinux

partition = -1

can't get <device_type> for device:

:-1,/vmlinux: Unable to open file, Invalid device

boot:


=================================================



--------------------------------------------------------------------------------------------------------------

On Sun, Jun 13, 2010 at 12:21 PM, Paul Nasrat <pnasrat at gmail.com> wrote:

> On 10 June 2010 19:20, Erlon Cruz <sombrafam at gmail.com> wrote:
> > Hi all,
> > Some time ago I send some messages in this list about how to netboot
> > diskless clients on Power Plataform. After some work I was able to boot
> the
> > diskless clients. The Open firmware version was SF240-382. Now, using the
> > same yaboot file on EL350-049, yaboot just dont work. Does anyone had
> this
> > same problem or can shad some light on how can a fix it??
>
> So it'd be helpful if you give the make and model of the h/w - looking
> up the Firmware version that seems to be an IBM Power6 machine of some
> sort without a HMC.
>
> Can you capture the console output of a boot with a yaboot built with
> DEBUG=1
>
> What is boot-device set to and what do you see on the network in terms
> of bootp/tftp traffic?
>
> Paul
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/yaboot-users/attachments/20100614/56a7a961/attachment.htm>


More information about the Yaboot-users mailing list