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