<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 01/29/2010 06:15 PM, Roman Rakus wrote:
<blockquote cite="mid:4B63179B.5070400@redhat.com" type="cite">
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
Hi,<br>
yaboot fails to get the [scyg]iaddr fields from netinfo even if these
fields are passed from arguments list. For example:<br>
0 > boot<br>
network1:bootp,10.0.0.242,yaboot_rhel6d,10.0.0.241,10.0.0.1,5,5,255.255.255.0<br>
<br>
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.<br>
<br>
The resulting messages are:<br>
<pre class="bz_comment_text" id="comment_text_1">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@23c00100/ethernet@23e00100:; defpart -1, deffile /vmlinux
/vmlinuz-2.6.31-33.el6.ppc64: Unable to parse
boot:
</pre>
So the infected functions are (in the order from deepest to shallowest):<br>
prom_get_netinfo()<br>
extract_netinfo_args()<br>
parse_device_path()<br>
get_params()<br>
yaboot_text_ui()<br>
...<br>
<span class="l"></span><br>
Is there any way how to debug this?<br>
Shouldn't be yaboot changed so it uses command line arguments for
addresses?<br>
<br>
RR<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Yaboot-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Yaboot-devel@lists.ozlabs.org">Yaboot-devel@lists.ozlabs.org</a>
<a class="moz-txt-link-freetext" href="https://lists.ozlabs.org/listinfo/yaboot-devel">https://lists.ozlabs.org/listinfo/yaboot-devel</a>
</pre>
</blockquote>
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?<br>
<br>
Nevertheless, there should be some nice message displayed that we don't
have any BOOTREPLY packet. <br>
<br>
RR<br>
</body>
</html>