kernel rootfs

Kristoffer Ericson kristoffer.ericson at gmail.com
Fri Dec 4 14:22:02 EST 2009


On Sat, 05 Dec 2009 01:47:05 +0800
Xiangfu Liu <xiangfu at qi-hardware.com> wrote:

> Kristoffer Ericson wrote:
> > On Fri, 04 Dec 2009 11:35:30 +0800
> > Xiangfu Liu <xiangfu at qi-hardware.com> wrote:
> > 
> >> Hi Kristoffer
> >>
> >> Kristoffer Ericson wrote:
> >>> Greetings,
> >>>
> >>> I ran into some issues running my custom made kernel. Is the bootloader assuming that there will be an
> >>> ramdisk? The rootfs that is flashed onto the NAND is that ramdisk/ordinary?
> >> no. bootloader don't assuming the ramdisk. then rootfs in NAND is UBIFS.
> > 
> > Oki. But the correct boot parameter should be? root=? And is this hardcoded
> > into kernel at compile time or does qemu pass it?
> Hi
> 
> u-boot will pass the kernel command line to kernel. 
> correct the command line is :
>   mem=32M console=ttyS0,57600n8 ubi.mtd=2 rootfstype=ubifs root=ubi0:rootfs rw rootwait

Ah oki, thx.

> > 
> >>> And if so, what device should it turn up as?
> >>>
> >>> The error Im getting is that after extracting kernel it says returned to monitor or something similiar.
> >> when kernel boot. there should nothing in screen until the OPENWRT show up. 
> >> so if it returned to screen. the kernel not run. 
> >>
> > 
> > Yes, but Im using a vanilla kernel patched with the openwrt patches. I havent installed
> > the bootsplash.
> > 
> >> you can check the serial output for more info.
> > 
> > Yeah, I guess I will need it after all.
> > 
> >>
> >> -- 
> >> Xiangfu Liu
> >> Email: xiangfu at qi-hardware dot com
> >> Web: http://www.qi-hardware.com
> >>
> >> _______________________________________________
> >> Qi Developer Mailing List
> >> Mail to list (members only): developer at lists.qi-hardware.com
> >> Subscribe or Unsubscribe: http://lists.qi-hardware.com/cgi-bin/mailman/listinfo/developer
> > 
> > 
> 
> 
> -- 
> Xiangfu Liu
> Email: xiangfu at qi-hardware dot com
> Web: http://www.qi-hardware.com


-- 
Kristoffer Ericson <kristoffer.ericson at gmail.com>




More information about the discussion mailing list


interactive