All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: Adrian Bunk <bunk@stusta.de>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.17-rc4-mm1 nfsroot build err, looks related to klibc
Date: Wed, 17 May 2006 10:22:15 -0700	[thread overview]
Message-ID: <446B5BC7.7080105@zytor.com> (raw)
In-Reply-To: <446B5AB0.8050703@gmail.com>

Jim Cromie wrote:
> H. Peter Anvin wrote:
>> Jim Cromie wrote:
>>>>
>>> Ok, it built clean, but broke on boot.
>>>
>>
>> What does the full command line look like?
>>
>>     -hpa
>>
> I presume you mean the kernel boot-line, since last post included the 
> 'Running ipconfig'
> 
> Ive been banging at the kernel with permutations of the following 
> pxelinux stanza.
> 
> LABEL   I 2.6.17-rc4-mm1-sk
>  MENU LABEL    ^i.  2.6.17-rc4-mm1-sk
>  KERNEL        vmlinuz-2.6.17-rc4-mm1-sk
>  APPEND        console=ttyS0,115200n81 root=/dev/nfs 
> nfsroot=/nfshost/truck 
> ip=192.168.42.100:192.168.42.1:192.168.42.1:255.255.255.0:soekris:eth0 
> panic=5
> 
> I think the problem lies with picking up a decent 'rootpath', since that
> part of the output is always empty, for all variations tried so far..
> 

Okay, this is probably a result of specifying the NFS server in the ip= 
option and the nfsroot not having a server.  I will try to debug this 
and straighten it out.

	-hpa

  reply	other threads:[~2006-05-17 17:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16  1:36 2.6.17-rc4-mm1 nfsroot build err, looks related to klibc Jim Cromie
2006-05-16  4:11 ` H. Peter Anvin
2006-05-16 10:18   ` Adrian Bunk
2006-05-16 19:04     ` H. Peter Anvin
2006-05-17  7:12       ` Jim Cromie
2006-05-17 16:14         ` H. Peter Anvin
2006-05-17 17:17           ` Jim Cromie
2006-05-17 17:22             ` H. Peter Anvin [this message]
2006-05-17 18:15               ` Jim Cromie
2006-05-17 23:25               ` Jim Cromie
2006-05-16  5:47 ` Jim Cromie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=446B5BC7.7080105@zytor.com \
    --to=hpa@zytor.com \
    --cc=bunk@stusta.de \
    --cc=jim.cromie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.