On Sun, Jun 19, 2011 at 11:24 AM, Prajosh Premdas <premdas.prajosh@gmail.com> wrote:

Hi

Please find the entire boot sequence here

RomBOOT

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

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)

Could it be the problem with the ethernet. Were you able to ping the LAN when booted without the NFS?
Phy address seems to be wrong(ffff...) and the irq as well.

Dinesh

On Wed, Jun 15, 2011 at 12:10 PM, Raseel Bhagat <raseelbhagat@gmail.com> wrote:

On Tue, Jun 14, 2011 at 7:22 PM, Prajosh Premdas <premdas.prajosh@gmail.com> wrote:

Hi Dave

I 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@gmail.com> wrote:

Hi Prajosh,

On Tue, Jun 14, 2011 at 10:07 AM, Prajosh Premdas
<premdas.prajosh@gmail.com> 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.

If I had to guess (since you didn't include any boot logs, that's
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@kernelnewbies.org
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@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

--
Regards,

Prajosh Premdas

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies