| kristianpaul | hahah, finally i'm ready something knwow :) | 02:44 |
|---|---|---|
| kristianpaul | damn ack flag signal.. | 02:44 |
| kristianpaul | lets see what happen when writing :) | 02:44 |
| kristianpaul | hello aw !! | 02:44 |
| kristianpaul | yeah, i can write as well | 02:45 |
| aw | kristianpaul, hi hi u got somethings new? hehe ;-) | 02:45 |
| kristianpaul | soon,i hope | 02:46 |
| kristianpaul | just dealing with two clocks domains in the milkymsit soc | 02:46 |
| kristianpaul | and seems i calm down the beast ;) | 02:46 |
| 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. ;-) | 02:47 |
| kristianpaul | sure, go ahead, just saying hi :) | 02:48 |
| qi-bot | The build has FAILED, see log here: http://fidelio.qi-hardware.com/~xiangfu/compile-log/openwrt-xburst.full_system-07162011-1957/ | 02:48 |
| aw | yes, calm down..me need to be. :-) | 02:48 |
| kristianpaul | damn, speak too fast, writing is not working at all | 03:01 |
| kristianpaul | he, no i'm right, just inverted some parameters.. | 03:02 |
| kristianpaul | oh well, lets implement that channel then | 03:02 |
| qi-bot | The build has FAILED, see log here: http://fidelio.qi-hardware.com/~xiangfu/compile-log/openwrt-xburst.full_system-07172011-0449/ | 11:40 |
| qi-bot | [commit] Werner Almesberger: mm1rc3/fix?.fig: various reset fixes Sebastien proposed (master) http://qi-hw.com/p/wernermisc/ed4101f | 13:33 |
| qi-bot | [commit] Werner Almesberger: mm1rc3/fix2.sch: Qucs simulation of fix2 (master) http://qi-hw.com/p/wernermisc/a374dab | 13:34 |
| 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 | 13:42 |
| 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.. | 20:08 |
| mth | how does the kernel get the device to be used for the rootfs? | 20:11 |
| mth | there is no kernel command line defined there | 20:12 |
| mth | is it passed via u-boot? | 20:12 |
| mth | how are you booting your kernel? | 20:12 |
| ignatius_ | Hmm. Good point... although, in the past it (the kernel cmdline) didn't really matter. I got the same error message. | 20:13 |
| ignatius_ | In the mean time, I guess i'll try it again. Thanks. | 20:13 |
| mth | maybe you don't need it, but then the rootfs device must come from somewhere else, for example u-boot | 20:15 |
| ignatius_ | I'm using the OpenWRT u-boot binary. | 20:15 |
| ignatius_ | It (a previous kernel) worked fine, with what seemed to be that same basic .config | 20:16 |
| mth | the "unknown-block" suggests that something is wrong there, either there is no device defined or a device of an unsupported type | 20:16 |
| ignatius_ | I don't understand what i'm doing wrong. | 20:16 |
| mth | and you're building the same type of image? | 20:16 |
| ignatius_ | Yeah. Same kernel. Same everything. | 20:16 |
| mth | u-boot kernel arguments only work with "uImage", not "zImage", iirc | 20:16 |
| ignatius_ | Same tool chain. | 20:16 |
| ignatius_ | Yes. I'm using the "linux/arch/mips/boot/uImage" file. | 20:17 |
| ignatius_ | In the process of getting the cmdline from the working kernel. | 20:18 |
| mth | do you still have to old config? if so, it might be useful to run a diff | 20:18 |
| ignatius_ | Yeah. I tried "make oldconfig" but the tool chain didn't like that. | 20:18 |
| ignatius_ | Unless it's "make target/linux/oldconfig" ?? | 20:18 |
| mth | "make oldconfig" doesn't build with the old config, it upgrades a config from an older kernel version to the current version | 20:19 |
| mth | you have "ARCH=mips" defined? | 20:20 |
| mth | forgetting that even once can really mess up your kernel config | 20:20 |
| ignatius_ | Ah. I see. | 20:21 |
| ignatius_ | Nah. Since i've been using the same kernel version, there is no previous .config file that I could use. | 20:21 |
| ignatius_ | Well, since i'm able to select the Nanonote in "make kernel_menuconfig" I assume that it is using the ARCH=mips statement. | 20:22 |
| ignatius_ | Here is the kernel cmdline: "mem=32M console=tty0 console=ttyS0,57600n8 ubi.mtd=2 rootfstype=ubifs root=ubi0:rootfs rw rootwait" | 20:22 |
| mth | ah, OpenWRT might set ARCH for you | 20:24 |
| mth | I usually build kernels in isolation (for the Dingoo, not the NanoNote, but the hardware is similar) | 20:24 |
| ignatius_ | Ah. Nod. | 20:25 |
| ignatius_ | I just recently got a Dingoo. It's really cool. | 20:25 |
| mth | if you like to mess with kernels, have a look at OpenDingux, it's basically the NanoNote kernel ported to the Dingoo | 20:26 |
| mth | with a few extras that are not fully mature yet (cpufreq, double buffering) | 20:26 |
| ignatius_ | Cool. | 20:26 |
| ignatius_ | Compiling the kernel.. | 20:26 |
| ignatius_ | (For the NanoNote) | 20:26 |
| 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)" | 20:29 |
| mth | is (0,0) the major/minor number? | 20:29 |
| mth | in that case it does look like the rootfs device is undefined | 20:30 |
| ignatius_ | I'm not sure, actually. | 20:30 |
| ignatius_ | Ah. Hmm. | 20:30 |
| GitHub103 | [milkymist] kristianpaul pushed 1 new commit to gps-sdr-testing: http://bit.ly/nKC3ib | 20:30 |
| GitHub103 | [milkymist/gps-sdr-testing] generic wishbone CC bridge template,migration from avalon WIP - Cristian Paul Peñaranda Rojas | 20:30 |
| ignatius_ | How would I define it? | 20:31 |
| mth | I guess the "root=ubi0:rootfs" part of the command line should take care of that | 20:31 |
| qi-bot | The build has FAILED, see log here: http://fidelio.qi-hardware.com/~xiangfu/compile-log/openwrt-xburst.full_system-07172011-1341/ | 20:32 |
| ignatius_ | Hmm. I wonder why it isn't registering. | 20:32 |
| ignatius_ | JFFS is defined.. ReiserFS is.. Ext2/3/4 is.. | 20:33 |
| mth | JFFS? is it possible that will claim the NAND making it unavailable for UBI? | 20:34 |
| ignatius_ | Hmm. Maybe. | 20:34 |
| ignatius_ | I'll give it a try. | 20:34 |
| mth | is there anything printed before the fatal message? | 20:35 |
| mth | for example whether any NAND partitions are found | 20:35 |
| ignatius_ | "UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19" | 20:36 |
| ignatius_ | "VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)" | 20:36 |
| ignatius_ | Please append a currect "root=" boot option; here are the available partitions:" | 20:36 |
| ignatius_ | Then it lists mtdblock0 thorugh mtdblock3 | 20:37 |
| mth | what is error 19? | 20:39 |
| ignatius_ | I have no idea. | 20:40 |
| mth | you can check in errno.h or one of its includes (errno-base.h, probably) | 20:40 |
| mth | in the include/ dir in the kernel source | 20:41 |
| ignatius_ | #define ENODEV 19 /* No such device */ | 20:48 |
| ignatius_ | Well, undefined JFFS support.. still won't boot. | 20:49 |
| mth | ok, so "ubi0" does not exists | 20:49 |
| ignatius_ | Nod. | 20:49 |
| mth | does it say anything about UBI or NAND earlier in the log? | 20:49 |
| ignatius_ | I'm not sure. I can't scroll back in the buffer. | 20:51 |
| ignatius_ | But, I checked the .config file.. the only "UBI" (besides basic debugging) item that isn't defined is the "XATTR" one. | 20:51 |
| mth | could you run a diff between this config and a known working one? | 20:56 |
| mth | anyway, I'm going afk, I'll check back here later | 20:56 |
| --- Mon Jul 18 2011 | 00:00 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!