**** BEGIN LOGGING AT Tue Dec 28 02:59:56 2010 **** BEGIN LOGGING AT Tue Dec 28 04:44:34 2010 **** ENDING LOGGING AT Tue Dec 28 17:22:34 2010 **** BEGIN LOGGING AT Tue Dec 28 17:22:49 2010 Dec 28 18:22:04 goodday Dec 28 18:23:36 could andone help me in getting the latest kernel running, I already managed to install a new U-boot (via http://oinkzwurgl.org/guruplug_uboot ) and managed to get a new kernel from ( http://www.plugcomputer.org/plugwiki/index.php/Setting_GuruPlug_to_be_a_stable_WiFi_Client ) Dec 28 18:25:07 but I am not sure about which root environment variable I should use, I currently have something like: ´setenv bootargs console=ttyS0,115200n8 root=dev/sdb1 rootdelay=5 ro´ -> which results in a ¨cannot open root device¨ error Dec 28 18:28:29 you mean /dev/sdb1 Dec 28 18:28:43 also use rootwait Dec 28 18:29:15 @kerio: I guess the root device should be the NAND-device or something? Dec 28 18:29:24 what's the root? Dec 28 18:30:11 actually I want only to update the guruplug server with a new kernel for stable wifi, but reading all wiki´s I still don´t know what I am doing... Dec 28 18:31:25 I setup a tftp-server on my laptop where I put the uImage which is on the plugcomputer stable wifi wiki page and which I can then load into the guruplug-device by typing ´tftp 0x640000 uImage´ in the U-boot console Dec 28 18:32:04 then I set the environment variables like serverip and ipaddr and finally the bootargs Dec 28 18:33:05 seems to boot the kernel quite nice, but in the end it cannot find the root-FS and that´s where I am stuck, perhaps there is a better way to accomplish what is on the http://www.plugcomputer.org/plugwiki/index.php/Setting_GuruPlug_to_be_a_stable_WiFi_Client page Dec 28 18:33:50 *where* is the root Dec 28 18:33:55 your installed system Dec 28 18:33:56 where is it Dec 28 18:34:18 just on the internal memory, I guess Dec 28 18:34:26 the NAND-memory of the Guruplug Dec 28 18:36:14 it's some /dev/mmcblk* device Dec 28 18:36:56 when the kernel wants to mount the root fs, it gives some alternative partitions like mtdblock0, mtdblock1, mtdblock2 Dec 28 18:42:09 which all fail if I try to replace like: setenv bootargs console=ttyS0,115200n8 root=dev/mtdblock0 Dec 28 18:43:37 I´ve also seen alternatives like setenv x_bootargs_root 'ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs' Dec 28 19:10:02 @kerio: found already something: setenv bootargs console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs seems to boot Dec 28 19:10:14 oh, you're using ubifs Dec 28 19:10:41 it´s all default factory settings Dec 28 20:59:42 thanks for the feedback for now Dec 28 20:59:42 bye **** ENDING LOGGING AT Wed Dec 29 02:59:57 2010