[U-Boot-Users] kernel bootparams
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
In message 402AB73F.5010803@email.si you wrote:
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).
Then request the source from the guys who gave/sold you the board. U-Boot is under GPL and they MUST give you the full source code, including all modifications they might have made, _ffor_free_.
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
Probably the kernel uses it's own bootstrap loader which includes a hard-wired command line.
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 ?
No, this is just the default value which can be overwritten by the standard setenv command.
i will copile u-boot from CVS tomorrow (need to create new board defines), just need to clear some stuff now...
Complain at the guys who gave you the board!!
Best regards,
Wolfgang Denk
i apoligize since i sent first reply to Wolfgang Denk only, my mail client tricked me :)
Wolfgang Denk wrote:
In message 402AB73F.5010803@email.si you wrote:
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).
Then request the source from the guys who gave/sold you the board. U-Boot is under GPL and they MUST give you the full source code, including all modifications they might have made, _ffor_free_.
got it today, the forgot to include on the cd they gave me.
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
Probably the kernel uses it's own bootstrap loader which includes a hard-wired command line.
and how could i tell if such bootstrap loader exists ? as far as i know there is nothing present on flash except u-boot and u-boot env.
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 ?
No, this is just the default value which can be overwritten by the standard setenv command.
ok, that means kernel line supplied to the kernel is hardwired, i guess, somewhere else.
i will copile u-boot from CVS tomorrow (need to create new board defines), just need to clear some stuff now...
Complain at the guys who gave you the board!!
i did, and i got it - but they have 1.0.0 sources ported and said they tried porting cvs version, but had some problems. are there major changes from 1.0.0 and current cvs (1.0.2)? it is only a patch revision according to numbering in README as I recall, so how different could it be.
Best regards,
Wolfgang Denk
thank, you
regards, himba
participants (2)
-
himbA -
Wolfgang Denk