[U-Boot-Users] kernel bootup for PQ2FADS-ZU

[U-Boot-Users] kernel bootup for PQ2FADS-ZU

[Nethra]

hi,

I am using montavista linux kernel 2.6.10 and after nfs mounting it is
giving fallowing error.
 
=> setenv bootargs root=/dev/nfs nfsroot=192.168.178.110:/mnt
ip=192.168.178.234
:192.168.178.110:192.168.178.6:255.255.255.0:cashel:eth1:off
=> savee
Saving Environment to Flash...
.
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... done
.
Protected 1 sectors
=> printenv
bootdelay=5
baudrate=38400
ethact=FCC2 ETHERNET
serverip=192.168.178.110
ethaddr=00:99:23:44:ad:de
bootcmd=tftpboot 0x1000000 godcome;bootm 0x1000000;
ipaddr=192.168.178.234
stdin=serial
stdout=serial
stderr=serial
bootargs=root=/dev/nfs nfsroot=192.168.178.110:/mnt
ip=192.168.178.234:192.168.1
78.110:192.168.178.6:255.255.255.0:cashel:eth1:off

Environment size: 346/262140 bytes
=> run bootcmd
Using FCC2 ETHERNET device
TFTP from server 192.168.178.110; our IP address is 192.168.178.234
Filename 'godcome'.
Load address: 0x1000000
Loading: #################################################################
         #################################################################
         ########################################################
done
Bytes transferred = 948671 (e79bf hex)
## Booting image at 01000000 ...
   Image Name:   Linux-2.6.10_mvl401-8272ads
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    948607 Bytes = 926.4 kB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
Linux version 2.6.10_mvl401-8272ads (root at em178110) (gcc version 3.4.3
(MontaVis
ta 3.4.3-25.0.70.0501961 2005-12-18)) #2 Tue Jan 23 16:54:50 IST 2007
Motorola PQ2 ADS PowerPC port
Built 1 zonelists
Kernel command line: root=/dev/nfs nfsroot=192.168.178.110:/mnt
ip=192.168.178.2
34:192.168.178.110:192.168.178.6:255.255.255.0:cashel:eth1:off
PID hash table entries: 256 (order: 8, 4096 bytes)
hr_time_init: arch_to_nsec = 83886080, nsec_to_arch = 107374182
Warning: real time clock seems stuck!
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 30152k available (1684k kernel code, 468k data, 100k init, 0k
highmem)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
spawn_desched_task(00000000)
desched cpu_callback 3/00000000
ksoftirqd started up.
desched cpu_callback 2/00000000
desched thread 0 started up.
NET: Registered protocol family 16
Installing knfsd (copyright (C) 1996 okir at monad.swb.de).
Initializing Cryptographic API
Serial: CPM driver $Revision: 0.01 $
ttyCPM0 at MMIO 0xf0011a00 (irq = 40) is a CPM UART
ttyCPM1 at MMIO 0xf0011a60 (irq = 43) is a CPM UART
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
fs_enet.c:v1.0 (Aug 8, 2005)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
eth0: FCC ENET Version 0.3, 00:99:23:c4:ad:de
eth1: FCC ENET Version 0.3, 00:99:23:44:ad:de
eth2: FCC ENET Version 0.3, 00:99:23:64:ad:de
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: Complete:
      device=eth1, addr=192.168.178.234, mask=255.255.255.0,
gw=192.168.178.6,
     host=cashel, domain=, nis-domain=(none),
     bootserver=192.168.178.110, rootserver=192.168.178.110, rootpath=
Looking up port of RPC 100003/2 on 192.168.178.110
Looking up port of RPC 100005/1 on 192.168.178.110
VFS: Mounted root (nfs filesystem) readonly.
Freeing unused kernel memory: 100k init
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to
kernel.
 <0>Rebooting in 180 seconds..

is root file system correct? If not, where is the problem?

waiting for early response...

with regards,

Nethra
-- 
View this message in context: http://www.nabble.com/kernel-bootup-for-PQ2FADS-ZU-tf3134550.html#a8685457
Sent from the Uboot - Users mailing list archive at Nabble.com.

[U-Boot-Users] kernel bootup for PQ2FADS-ZU

[Wolfgang Denk]

In message <8685457.post@talk.nabble.com> you wrote:
> 
> 
> I am using montavista linux kernel 2.6.10 and after nfs mounting it is
> giving fallowing error.
...
> Warning: unable to open an initial console.
...
> is root file system correct? If not, where is the problem?

One of your problems is that you are posting to the wrong list. You
are off topic here.

But yes, your file system is obviously not correct.

Now if this were the ELDK, I would say you had forgotten to  run  the
ELDK_MAKEDEV  script, but since this is MVL you probbly should ask MV
support...

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
: 1.  What is the possibility of this being added in the future?
In the near future, the probability is close to zero. In the  distant
future, I'll be dead, and posterity can do whatever they like... :-)
                                                              - lwall

[U-Boot-Users] kernel bootup for PQ2FADS-ZU

[Charles Krinke]

Dear Nethra:

The fact that you have gotten this far indicates that uboot is doing the
correct thing and the issue is with Linux.

The things to look for when an nfs mount fails at this point are:

1. Can you ping the nfs host with uboot before the bootm.
2. Is the nfs hosts setup correctly, i.e. is nfs running and is
/etc/exports exporting the correct directory.
3. Is the nfs rootfs itself correct. That is, does it have init in the
appropriate place. Does it have the appropriate dev entry points and are
they character devices with good major/minor and not just blank
mountpoints.

Charles

[U-Boot-Users] kernel bootup for PQ2FADS-ZU

[Nethra]

Charles Krinke wrote:
> 
> Dear Nethra:
> 
> The fact that you have gotten this far indicates that uboot is doing the
> correct thing and the issue is with Linux.
> 
> The things to look for when an nfs mount fails at this point are:
> 
> 1. Can you ping the nfs host with uboot before the bootm.
> 
>    yes i can ping host with u-boot before the bootm
> 
> 2. Is the nfs hosts setup correctly, i.e. is nfs running and is
> /etc/exports exporting the correct directory.
> 
>   yes it is running and i have exported the same directory
> 
> 3. Is the nfs rootfs itself correct. That is, does it have init in the
> appropriate place. Does it have the appropriate dev entry points and are
> they character devices with good major/minor and not just blank
> mountpoints.
> 
>    i have created root file system using montavista (devrocket) and
> packages i have selected are busybox and initscripts.This is giving error
> i mentioned earlier.But same kernel is working with other root file
> system.
> 
> can i create ramdisk image using root file system (i have file system but
> not ext2 image file system) which i have?
> 
> 
> regards,
> Nethra
> 
> 
> 
> Charles
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
> 
> 

-- 
View this message in context: http://www.nabble.com/kernel-bootup-for-PQ2FADS-ZU-tf3134550.html#a8742456
Sent from the Uboot - Users mailing list archive at Nabble.com.