Good info -- thank you!
Have any thoughts on how to trace an init process that apparently goes off into
the weeds? My 2.6 on my 7400 boots great and finds the initrd that I pass in
using bootloader_static <...> --initrd= (I assume the initrd file is put in an
absolute location in RAM by bootloader.o from within the 2.4 kernel as a passed
file parameter)...
Anyways, the process croaks when it hits what I believe is the actual
/sbin/init step, but I am somewhat at a loss at a quick way to debug that.
Any ideas welcome?
-dave
--- In Jason Stahls <> wrote:
>
> wrote:
> > I am attempting much the same thing.
> >
> > Your problem below is most likely this: Your kernel can not find your root
> > filesystem. In the case of my 7400 the base kernel does not have the SD
> > kernel module compiled in so it can't look for it by default on the SD/CF
> > (hda1 is the default location to look)
> >
>
> The TS-7200 is a little different animal from the rest, being the only
> one with a CF card slot onboard. The CF slot only needs ATA support in
> the kernel, not the SD modules. It also uses redboot unlike the 7400.
> I haven't tried to use 2.6 on one yet since I haven't had access to a TS
> board in a few years, but with 2.4 getting it to boot from the CF with a
> kernel in flash, or from NFS, or kernel and rootfs off CF was quite easy.
>
> --
> Jason Stahls
>
------------------------------------
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/
|