Please find the entire boot sequence here
RomBOOT
U-Boot 1.3.4 (Mar 9 2010 - 19:35:35)
DRAM: 64 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: macb0
macb0: Starting autonegotiation...
macb0: Autonegotiation complete
macb0: link up, 100Mbps full-duplex (lpa: 0xc5e1)
Hit any key to stop autoboot: 0
U-Boot>
U-Boot> set bootcmd 'tftp 0x22200000 uImage; bootm 0x22200000'
U-Boot> set bootargs 'root=/dev/nfs nfsroot=10.0.0.1:/nfs ip=10.220.4.200::10.220.4.35:::eth0:off console=ttyS0,115200'
U-Boot> print
ethaddr=3a:1f:34:08:54:54
bootdelay=3
baudrate=115200
ethact=macb0
ipaddr=10.0.0.2
serverip=10.0.0.1
stdin=serial
stdout=serial
stderr=serial
bootcmd=tftp 0x22200000 uImage; bootm 0x22200000
bootargs=root=/dev/nfs nfsroot=10.0.0.1:/nfs ip=10.220.4.200::10.220.4.35:::eth0:off console=ttyS0,115200
Environment size: 297/131067 bytes
U-Boot> boot
macb0: link up, 100Mbps full-duplex (lpa: 0xc5e1)
Using macb0 device
TFTP from server 10.0.0.1; our IP address is 10.0.0.2
Filename 'uImage'.
Load address: 0x22200000
Loading: #################################################################
#####################################################
done
Bytes transferred = 1720076 (1a3f0c hex)
## Booting kernel from Legacy Image at 22200000 ...
Image Name: Linux-2.6.37
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1720012 Bytes = 1.6 MB
Load Address: 20008000
Entry Point: 20008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (prajosh@prajosh) (gcc version 4.3.5 (Buildroot 2011.02) ) #2 Sun Jun 19 15:27:13 IST 2011
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Atmel AT91SAM9G20-EK
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 396 MHz, master 132 MHz, main 18.432 MHz
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: root=/dev/nfs nfsroot=10.0.0.1:/nfs ip=10.220.4.200::10.220.4.35:::eth0:off console=ttyS0,115200
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61416k/61416k available, 4120k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xc4800000 - 0xfee00000 ( 934 MB)
lowmem : 0xc0000000 - 0xc4000000 ( 64 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0028000 ( 128 kB)
.text : 0xc0028000 - 0xc032e0f8 (3097 kB)
.data : 0xc0330000 - 0xc0350fe0 ( 132 kB)
NR_IRQS:192
AT91: 96 gpio irqs in 3 banks
Console: colour dummy device 80x30
console [ttyS0] enabled
Calibrating delay loop... 197.83 BogoMIPS (lpj=989184)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
AT91: Power Management
AT91: Starting after user reset
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource pit
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 119
io scheduler noop registered (default)
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung )
Scanning device for bad blocks
Bad eraseblock 532 at 0x000004280000
Bad eraseblock 1572 at 0x00000c480000
Creating 3 MTD partitions on "atmel_nand":
0x000000000000-0x000000400000 : "Bootstrap"
0x000000400000-0x000004000000 : "Partition 1"
0x000004000000-0x000010000000 : "Partition 2"
atmel_spi atmel_spi.0: Atmel SPI Controller at 0xfffc8000 (irq 12)
atmel_spi atmel_spi.1: Atmel SPI Controller at 0xfffcc000 (irq 13)
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (3a:1f:34:08:54:54)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, irq=-1)
usbmon: debugfs is not available
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
udc: at91_udc version 3 May 2006
mice: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
rtc-at91sam9 at91_rtt.0: rtc0: SET TIME!
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock
IP-Config: Guessing netmask 255.0.0.0
IP-Config: Complete:
device=eth0, addr=10.220.4.200, mask=255.0.0.0, gw=10.220.4.35,
host=10.220.4.200, domain=, nis-domain=(none),
bootserver=255.255.255.255, rootserver=10.0.0.1, rootpath=
eth0: link up (100/Full)
VFS: Mounted root (nfs filesystem) on device 0:12.
Freeing init memory: 128K
Starting network...
ip: RTNETLINK answers: File exists
Starting dropbear sshd: generating rsa key... generating dsa key... OK
I have put down the entire sequence. I have also shown the u-boot parameters.
Could anybody please tell me why the board stops after the command. I have the same file system flashed on my NAND flash and if i show that path for the boot operation every thing works fine. (i.e. i load the kernel on tftp and boot from that.)
Regards
Prajosh Premdas
On Wed, Jun 15, 2011 at 12:10 PM, Raseel Bhagat <raseelbhagat@xxxxxxxxx> wrote:
On Tue, Jun 14, 2011 at 7:22 PM, Prajosh Premdas <premdas.prajosh@xxxxxxxxx> wrote:
_______________________________________________Hi DaveI tried booting with the root file system in my flash and uImage i copy using TFTP everything is fine.--On Tue, Jun 14, 2011 at 10:49 PM, Dave Hylands <dhylands@xxxxxxxxx> wrote:
Hi Prajosh,
If I had to guess (since you didn't include any boot logs, that's
On Tue, Jun 14, 2011 at 10:07 AM, Prajosh Premdas
<premdas.prajosh@xxxxxxxxx> wrote:
> Hi
> I am stuck with a problem. inittab is not executing after my Linux box boots
> up.
> The problem in detail. I have a linux box, i load the Linux image uImage
> using TFTP and my root file system is configured in NFS. After the security
> key is generated, my box just waits there infinity. Its not starting a new
> terminal.
> The new terminal has been specified in the inittab as
> ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL
> Can anybody help me out with this problem?
> Since i am not able to set password i cannot do a secure shell access too.
pretty much all I can do), I'd say that your NFS mount of the root
file system isn't working.
You can always try and see if you can even boot into a shell manually,
by adding init=/bin/sh to the kernel command line.
Have you tried booting without using NFS, and verifying that you can
mount the NFS volume?
--
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com
Regards,
Prajosh Premdas
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi Prajosh,
Could you post what exact error are you getting.
I had a very similar problem recently when trying to boot the kernel using tftp and then mounting the Rootfs over NFS.
The issue I faced was that the Rootfs' /dev directory was not correctly populated and was missing the /dev/console device.
I was getting an error on the lines of "Unable to start init console" and I too spent time mucking about in my inittab.
Thanks,
Raseel
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
Regards,
Prajosh Premdas
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
