--- In "j.chitte" <> wrote:
>
> --- In "j.chitte" <j.chitte@> wrote:
> >
> > --- In "Razvan Ionut
> > Stoian" <razvan_ionut_stoian@> wrote:
> > >
> > > --- In "Razvan Ionut Stoian"
> > > <razvan_ionut_stoian@> wrote:
> > > >
> > > > --- In "j.chitte" <j.chitte@> wrote:
> > > > >
> > > > > --- In "Razvan Ionut
> > > > > Stoian" <razvan_ionut_stoian@> wrote:
> > > > > >
> > > > > > --- In Jim Jackson <jj@> wrote:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Thu, 29 May 2008, Razvan Ionut Stoian wrote:
> > > > > > >
> > > > > > > > --- In Triffid Hunter
> > > > > <triffid_hunter@>
> > > > > > wrote:
> > > > > > > >>
> > > > > > > >> On Wed, 28 May 2008, Razvan Ionut Stoian wrote:
> > > > > > > >>
> > > > > > > >>> For some reason the system freezes after vmlinux
> starts
> > > > > > > >>> to decompress. This is what I got:
> > > > > > > >>>
> > > > > > > >>> Uncompressing
> > > > > > > >>>
> > > > >
> > Linux.............................................................
> > > > > > > >>>
> > > > > > > >
> > > > > >
> > > > >
> > > >
> >
>
........................................................................
> > > > > > > >>>
> > > > > > > >>> What am I doing wrong?
> > > > > > > >>
> > > > > > > >> Mine do that if my toolchain is broken
> > > > > > > >>
> > > > > > > >
> > > > > > > > This is odd. I used the toolchain provided by TS.
> > > > > > > > Any good alternatives?
> > > > > > >
> > > > > > > You can check if you toolchain is ok, by compiling the
> > supplied
> > > > > 2.4
> > > > > > kernel
> > > > > > > source, with the default configuration. If the 2.4 kernel
> > fails
> > > > > to boot
> > > > > > > then it may be your toolchain. If 2.4 works, then you
> have
> > a 2.6
> > > > > issue.
> > > > > > >
> > > > > > Hi.
> > > > > >
> > > > > > I managed to boot the 2.6 kernel. Apparently, the initial
> > image was
> > > > > > just too big. Now it boots, but my SBC freezes due to a
> > kernel
> > > > > panic:
> > > > > > ----------------------------------------------------
> > > > > > Kernel panic - not syncing: Attempted to kill init!
> > > > > > ----------------------------------------------------
> > > > > >
> > > > > > Any ideas?
> > > > > >
> > > > > > thank you,
> > > > > > R
> > > > > >
> > > > >
> > > > > That's probably the point at which it switches from initrd to
> > the
> > > > > disk fs. Check you rootfs is compatible with your kernel and
> > > > > accessible.
> > > > >
> > > > > Can yo boot to it over nfs using your new kernel?
> > > > >
> > > > I do not have an NFS server, but it seems that it boots alright.
> > > > So the question is how do I make the kernel recognize the root
> > device
> > > > hda1?
> > > > I parsed the lines in the .config file, but I could not find
> > anything
> > > > helpful.
> > > >
> > > > R
> > > >
> > >
> > > I used the debian_sarge_udev filesystem and copied vmlinux to /
> boot.
> > > Still nothing...
> > >
> > > Now I get this message:
> > > ================================================================
> > > VFS: Cannot open root device "hda1" or unknown-block(0,0)
> > > Please append a correct "root=" boot option
> > > Kernel panic - not syncing: VFS: UNable to mount root fs on
> > > unknown-block(0,0)
> > > ================================================================
> > >
> > > I included the ext2/ext3/cramfs modules in the kernel so the
> > > partitions could be recognized.
> > > What am I missing here?
> > >
> > > Razvan
> > >
> >
> >
> > > VFS: Cannot open root device "hda1" or unknown-block(0,0)
> > hda1 is not a device ;) /dev/hda1 ?
> >
> > check what you are feeding to redboot.
> >
> > > Please append a correct "root=" boot option
> > sounds like a good idea to try too.
> >
>
> TS manual states:
>
>
> The root file system used by the Linux OS can be any of the following:
> ✔ JFFS/YAFFS file system image in the on-board Flash (if using
> RedBoot, it should
> include the option root=/dev/mtdblock1 to instruct the kernel to boot
> here)
> ✔ EXT2 file system image in the Compact Flash card (if using
> RedBoot, it should include
> the option root=/dev/hda)
> ✔ NFS root, via Ethernet port (if using RedBoot, it should
include
> the option root=/dev/nfs
> nfsroot=<IP>:<DIRECTORY> ip=dhcp)
>
> HTH
>
This is the problem. These errors show up even if I give the correct
command line in RedBoot.
RedBoot> load -r -b 0x00218000 -m disk hda1:/boot/vmlinux
RedBoot> exec -c "console=ttyAM0,115200 ip=dhcp root=/dev/hda1"
with my CF card formated as ext2.
R
------------------------------------
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/
|