You might try enabling the following in the kernel config: Device Drivers -> Memory Technology Device (MTD) support --> RAM/ROM/Flash chip drivers ---> Support for RAM chips in bus mapping --> Mapping drivers for chip access ---> Generic uClinux RAM/ROM filesystem support ----> uClinux RAM/ROM filesystem is located at ebss
On Mon, Jun 16, 2008 at 7:50 PM, David McCullough < [EMAIL PROTECTED]> wrote: > > Jivin rwarner lays it down ... > > Hi, > > > > Ok searching the archives i've found a lot of scattered answers. Using > > scatter and gather algo did not result in joy. ;) > > > > I have the necessary correction(s) to the appropriate makefile in the > > vendors directory, such that mtd(0,1,2) and mtdblock(0,1,2) are created > > in the romfs. In addition i've verified that in memory at the location > > of the romfs (0x204cffd0) i have the string -rom1fs-. > > -rw-r--r-- 1 root root 0 Jun 11 12:34 @mtdblock2,b,31,4 > > -rw-r--r-- 1 root root 0 Jun 11 12:34 @mtdblock1,b,31,2 > > -rw-r--r-- 1 root root 0 Jun 11 12:34 @mtdblock0,b,31,0 > > -rw-r--r-- 1 root root 0 Jun 11 12:34 @mtd2,c,90,4 > > -rw-r--r-- 1 root root 0 Jun 11 12:34 @mtd1,c,90,2 > > -rw-r--r-- 1 root root 0 Jun 11 12:34 @mtd0,c,90,0 > > > > However, when the final icing (and i don't mean throwing the puck down > > the ice) is put on the cake i'm eating no joy. > > > > Now for the output from tty console (just the last part) ... > > [42949379.530000] Calling initcall 0x20414f14: init_mtd+0x0/0x44() > > [42949379.560000] Calling initcall 0x20414f58: init_mtdchar+0x0/0x14c() > > [42949379.580000] Calling initcall 0x204150a4: init_mtdblock+0x0/0x1c() > > [42949379.610000] Calling initcall 0x204150c0: map_rom_init+0x0/0x20() > > [42949379.630000] Calling initcall 0x204150e0: > uclinux_mtd_init+0x0/0x158() > > [42949379.660000] uclinux[mtd]: RAM probe address=0x204cffd0 size=0x8e000 > > [42949379.670000] Creating 1 MTD partitions on "%s": > > [42949379.680000] 0x%8x-0x%x : "<NUEL>" > > [42949379.700000] uclinux[mtd]: set ROMfs to be root filesystem > > [42949379.710000] Calling initcall 0x20415318: serport_init+0x0/0x34() > > [42949379.730000] Calling initcall 0x2041546c: hwmon_init+0x0/0x48() > > [42949379.750000] Calling initcall 0x2040ed0c: > arm_mrc_hook_init+0x0/0x20() > > [42949379.770000] Calling initcall 0x20410c7c: > > clocksource_done_booting+0x0/0x24 > > () > > [42949379.800000] Calling initcall 0x204140c0: random32_reseed+0x0/0x34() > > [42949379.820000] Calling initcall 0x204141c8: seqgen_init+0x0/0x1c() > > [42949379.920000] VFS: Cannot open root device "mtdblock0" or > > unkno6n-bloÀk(%u,0 > > ) > > [42949379.930000] Please append a correct "root=" boot option > > [42949379.940000] Kernel panic - not syncing: VFS: Unable to mount root > > fs on un > > kno6n-bloÀk(%u,0) > > [42949379.950000] > > Firstly, at this point, your filesystem has not been accessed, so it > doesn't matter what dev nodes you have, they don't matter. > > The kernel is failing to find your root fs. What is your kernel command > line ? > > And as someone else said, work out that console corruption/not printing > thing, that would be a good start ;-) > > Cheers, > Davidm > > -- > David McCullough, [EMAIL PROTECTED], Ph:+61 > 734352815 > Secure Computing - SnapGear http://www.uCdot.org > http://www.snapgear.com > _______________________________________________ > uClinux-dev mailing list > [email protected] > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev > This message was resent by [email protected] > To unsubscribe see: > http://mailman.uclinux.org/mailman/options/uclinux-dev > -- chris -at- microcozm -dot- net === Si Hoc Legere Scis Nimium Eruditionis Habes
_______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
