yaboot fails to get the [scyg]iaddr fields from netinfo

[Roman Rakus]

On 01/29/2010 06:15 PM, Roman Rakus wrote:
> Hi,
> yaboot fails to get the [scyg]iaddr fields from netinfo even if these 
> fields are passed from arguments list. For example:
> 0 > boot
> network1:bootp,10.0.0.242,yaboot_rhel6d,10.0.0.241,10.0.0.1,5,5,255.255.255.0
>
> but yaboot doesn't use them and they are not in /chosen/. In my 
> booting system there is debug message `prom_get_netinfo - using 
> /chosen/bootpreply-packet'. But in the nonbooting system there is no 
> such message.
>
> The resulting messages are:
> Welcome to yaboot version 1.3.14 (Red Hat 1.3.14-23.el6)
> Enter "help" to get some basic usage information
> boot: linux
> parse_device_path - imagepath = /vmlinuz-2.6.31-33.el6.ppc64; defdevice
> /lhea at 23c00100/ethernet at 23e00100:; defpart -1, deffile /vmlinux
> /vmlinuz-2.6.31-33.el6.ppc64: Unable to parse
> boot:
>    
> So the infected functions are (in the order from deepest to shallowest):
> prom_get_netinfo()
> extract_netinfo_args()
> parse_device_path()
> get_params()
> yaboot_text_ui()
> ...
>
> Is there any way how to debug this?
> Shouldn't be yaboot changed so it uses command line arguments for 
> addresses?
>
> RR
>
>
> _______________________________________________
> Yaboot-devel mailing list
> Yaboot-devel at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/yaboot-devel
>    
Is 
`network1:bootp,10.0.0.242,yaboot_rhel6d,10.0.0.241,10.0.0.1,5,5,255.255.255.0' 
device path allowed or not?

Nevertheless, there should be some nice message displayed that we don't 
have any BOOTREPLY packet.

RR
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/yaboot-devel/attachments/20100205/71f6d978/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: yaboot-1.3.14-nopacket.patch
URL: <http://lists.ozlabs.org/pipermail/yaboot-devel/attachments/20100205/71f6d978/attachment.asc>