<kristianpaul> hahah, finally i'm ready something knwow :)
<kristianpaul> damn ack flag signal..
<kristianpaul> lets see what happen when writing :)
<kristianpaul> hello aw !!
<kristianpaul> yeah, i can write as well
<aw> kristianpaul, hi hi u got somethings new? hehe ;-)
<kristianpaul> soon,i hope
<kristianpaul> just dealing with two clocks domains in the milkymsit soc
<kristianpaul> and seems i calm down the beast ;)
<aw> good though although i don'et know what story you are building now. ;-)  in the other irc, i need to see backlog, u know. ;-)
<kristianpaul> sure, go ahead, just saying hi :)
<aw> yes, calm down..me need to be. :-)
<kristianpaul> damn, speak too fast, writing is not working at all
<kristianpaul> he, no i'm right, just inverted some parameters..
<kristianpaul> oh well, lets implement that channel then
<qi-bot> [commit] Werner Almesberger: mm1rc3/fix?.fig: various reset fixes Sebastien proposed (master) http://qi-hw.com/p/wernermisc/ed4101f
<qi-bot> [commit] Werner Almesberger: mm1rc3/fix2.sch: Qucs simulation of fix2 (master) http://qi-hw.com/p/wernermisc/a374dab
<qi-bot> [commit] Werner Almesberger: mm1rc3rst/fix2.sch: use fixed V range for result; don't open data display (master) http://qi-hw.com/p/wernermisc/c0395dc
<ignatius_> Hi... after compiling the kernel.. I get this message: "Kernel panic - not syncing VFS: Unable to mount root fs on unknown-block (0,0"  Here is my kernel .config: http://www.armory.com/~ignatius/config.htm -- if anyone could help me out, i'd really appreciate it. Thanks..
<mth> how does the kernel get the device to be used for the rootfs?
<mth> there is no kernel command line defined there
<mth> is it passed via u-boot?
<mth> how are you booting your kernel?
<ignatius_> Hmm. Good point... although, in the past it (the kernel cmdline) didn't really matter. I got the same error message.
<ignatius_> In the mean time, I guess i'll try it again. Thanks.
<mth> maybe you don't need it, but then the rootfs device must come from somewhere else, for example u-boot
<ignatius_> I'm using the OpenWRT u-boot binary.
<ignatius_> It (a previous kernel) worked fine, with what seemed to be that same basic .config
<mth> the "unknown-block" suggests that something is wrong there, either there is no device defined or a device of an unsupported type
<ignatius_> I don't understand what i'm doing wrong.
<mth> and you're building the same type of image?
<ignatius_> Yeah. Same kernel. Same everything.
<mth> u-boot kernel arguments only work with "uImage", not "zImage", iirc
<ignatius_> Same tool chain.
<ignatius_> Yes. I'm using the "linux/arch/mips/boot/uImage" file.
<ignatius_> In the process of getting the cmdline from the working kernel.
<mth> do you still have to old config? if so, it might be useful to run a diff
<ignatius_> Yeah. I tried "make oldconfig" but the tool chain didn't like that.
<ignatius_> Unless it's "make target/linux/oldconfig" ??
<mth> "make oldconfig" doesn't build with the old config, it upgrades a config from an older kernel version to the current version
<mth> you have "ARCH=mips" defined?
<mth> forgetting that even once can really mess up your kernel config
<ignatius_> Ah. I see.
<ignatius_> Nah. Since i've been using the same kernel version, there is no previous .config file that I could use.
<ignatius_> Well, since i'm able to select the Nanonote in "make kernel_menuconfig" I assume that it is using the ARCH=mips statement.
<ignatius_> Here is the kernel cmdline: "mem=32M console=tty0 console=ttyS0,57600n8 ubi.mtd=2 rootfstype=ubifs root=ubi0:rootfs rw rootwait"
<mth> ah, OpenWRT might set ARCH for you
<mth> I usually build kernels in isolation (for the Dingoo, not the NanoNote, but the hardware is similar)
<ignatius_> Ah. Nod.
<ignatius_> I just recently got a Dingoo. It's really cool.
<mth> if you like to mess with kernels, have a look at OpenDingux, it's basically the NanoNote kernel ported to the Dingoo
<mth> with a few extras that are not fully mature yet (cpufreq, double buffering)
<ignatius_> Cool.
<ignatius_> Compiling the kernel..
<ignatius_> (For the NanoNote)
<ignatius_> Just like I thought. I got the same error message ("Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)"
<mth> is (0,0) the major/minor number?
<mth> in that case it does look like the rootfs device is undefined
<ignatius_> I'm not sure, actually.
<ignatius_> Ah. Hmm.
<GitHub103> [milkymist] kristianpaul pushed 1 new commit to gps-sdr-testing: http://bit.ly/nKC3ib
<GitHub103> [milkymist/gps-sdr-testing] generic wishbone CC bridge template,migration from avalon WIP - Cristian Paul Peñaranda Rojas
<ignatius_> How would I define it?
<mth> I guess the "root=ubi0:rootfs" part of the command line should take care of that
<ignatius_> Hmm. I wonder why it isn't registering.
<ignatius_> JFFS is defined.. ReiserFS is.. Ext2/3/4 is..
<mth> JFFS? is it possible that will claim the NAND making it unavailable for UBI?
<ignatius_> Hmm. Maybe.
<ignatius_> I'll give it a try.
<mth> is there anything printed before the fatal message?
<mth> for example whether any NAND partitions are found
<ignatius_> "UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19"
<ignatius_> "VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)"
<ignatius_> Please append a currect "root=" boot option; here are the available partitions:"
<ignatius_> Then it lists mtdblock0 thorugh mtdblock3
<mth> what is error 19?
<ignatius_> I have no idea.
<mth> you can check in errno.h or one of its includes (errno-base.h, probably)
<mth> in the include/ dir in the kernel source
<ignatius_> #define ENODEV          19      /* No such device */
<ignatius_> Well, undefined JFFS support.. still won't boot.
<mth> ok, so "ubi0" does not exists
<ignatius_> Nod.
<mth> does it say anything about UBI or NAND earlier in the log?
<ignatius_> I'm not sure. I can't scroll back in the buffer.
<ignatius_> But, I checked the .config file.. the only "UBI" (besides basic debugging) item that isn't defined is the "XATTR" one.
<mth> could you run a diff between this config and a known working one?
<mth> anyway, I'm going afk, I'll check back here later