--- In "mout551" <> wrote:
>
> --- In andrewt <andrewt@> wrote:
> >
> > On Thu, Mar 27, 2008 at 03:06:34PM -0000, mout551 wrote:
> > > Warning: unable to open an initial console.
> > > Failed to execute /sbin/init. Attempting defaults...
> >
> > It looks like you need to do this (cut&paste from
> > our build script):
> >
> > cd $FILESYSTEM/dev
> > test -e console || sudo mknod console c 5 1
> > test -e ttyAM0 || sudo mknod ttyAM0 c 204 16
> > test -e null || sudo mknod null c 1 3
> >
> > and you want to check that init is present.
> >
> > Andrew
> >
>
>
> Hi Andrew and Charlie,
>
> I am using the kernel 2.6.21 and my rootfs is with udev, the same than
> Charlie suggest me and with the cross compiler for ARM EABI.
EABI kernel now? The rootfs listed above is not EABI, IIRC. EABI
kernels can run older OABI executables (like init), but *only if that
option is configured in the kernel*.
>
> I am a beginner, so maybe i make some mistakes.
>
> But i re-installed my rootfs, i changed the file
> $filesystem/etc/network/interfaces to have a static IP, i modified the
> file $filesystem/etc/fstab by adding the last line. Now i have :
>
> proc /proc proc defaults 0 0
> none /dev/pts devpts gid=5,mode=620 0 0
> sysfs /sys sysfs default 0 0
> 192.168.1.5:/var/exports/nfsroot26 / nfs exec,dev,suid 1 1
>
> I wrote this in the $filesytem/dev directory without mistake responses
>
> test -e console || sudo mknod console c 5 1
> test -e ttyAM0 || sudo mknod ttyAM0 c 204 16
> test -e null || sudo mknod null c 1 3
Andrews advice should be spot-on here. Do the nodes actually get
made? Also see a recent post:
http://tech.groups.yahoo.com/group/ts-7000/message/10784
>
>
> But i have again the same errors :
>
> .
> .
> VFS: Mounted root (nfs filesystem).
> Freeing init memory: 100K
> Warning: unable to open an initial console.
> Kernel panic - not syncing: No init found. Try passing init= option
> to kernel.
>
>
> Maybe there are again some modifications to do in the rootfs or maybe
> my kernel is not enought configurated ?
Yes, it's possible. Compare your .config to the one that is used to
build the TS kernels
You seem to be doing many things at once. Maybe you should step back,
and take smaller steps:
* Use TS pre-built kernel (non-EABI), with matching TS rootfs, boot
with nfsroot.
* Then try re-building the TS kernel with your toolchain, boot new
kernel with nfsroot.
* When that works, try building an EABI kernel, and use an EABI
rootfs. Links to several EABI rootfs's have been posted in this
group; you don't have to use the ones from TS.
Regards, ........ Charlie
>
>
> Regards
> Mout
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|