From: himbA <goavr@email.si>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] kernel bootparams
Date: Thu, 12 Feb 2004 00:14:07 +0100 [thread overview]
Message-ID: <402AB73F.5010803@email.si> (raw)
Hello
I have a board, pxa based, and it has u-boot burnt, but i don't have the
source from which it was compiled from, so i don't have any config
setting (got the board as-is).
for now booting is made from flash, loading both kernel and ramdisk. i
want to try nfs based booting and first strange thing i notice when
kernel gets booted is that kernel parameters are always the same, no
matter to what i set 'bootargs' var in u-boot. it always displays
....
Kernel command line: root=/dev/ram0 console=ttyS0,115200 mem=64M
....
and hangs at
....
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com
Kernel panic: VFS: Unable to mount root fs on 01:00
although passed bootargs says:
bootargs=root=/dev/nfs rw nfsroot=10.10.10.1:/tftpboot/10.10.10.1
ip=10.10.10.2:10.10.10.1::255.255.255.0:xcep:: console=ttyS0,115200 mem=64M
I also tried changing CONFIG_CMDLINE setting in .config of the kernel to
same value as bootargs but still notihng changed.
If CONFIG_BOOTARGS var in u-boot is specified during compile time, does
it interfere with bootargs passed at boot time ?
i will copile u-boot from CVS tomorrow (need to create new board
defines), just need to clear some stuff now...
regards, himba
next reply other threads:[~2004-02-11 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 23:14 himbA [this message]
2004-02-11 23:27 ` [U-Boot-Users] kernel bootparams Wolfgang Denk
2004-02-12 11:47 ` himbA
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=402AB73F.5010803@email.si \
--to=goavr@email.si \
--cc=u-boot@lists.denx.de \
/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.