**** BEGIN LOGGING AT Sat Feb 11 10:59:56 2006 Feb 11 12:00:40 hi Feb 11 12:01:33 how can i gat a ramdisk to my sluggy? i tryed "upslug2 --target=bla --ramdisk=initrd.img.gz" but he just prints out the output as without any arguments: the slugs wich are in upgrademode Feb 11 12:46:17 <[cc]smart> rammy: how do you mean how to get a ramdisk ? ramdisk would be default. Feb 11 12:56:01 errr Feb 11 12:56:39 [cc]smart: i have a ramdisk Feb 11 12:56:47 but dunno, how to get it on my slug Feb 11 12:56:59 because upslug2 doesnt work here Feb 11 12:57:18 actually im in reboot and try to get it from http Feb 11 12:57:21 but dunno where to store it Feb 11 12:57:54 http://www.nslu2-linux.org/wiki/Info/BootFlash <- here they say, that the ramdisk should start at 0x50160000 Feb 11 12:58:27 here, they copy the ramdisk to: 0x1000000 http://www.nslu2-linux.org/wiki/HowTo/UseMinicomScriptsToLoadTestBuilds Feb 11 12:58:33 whats true now? Feb 11 13:00:12 and when i boot linux, it says: Feb 11 13:00:17 0x00040000-0x00060000 : "SysConf" Feb 11 13:00:17 0x00060000-0x00160000 : "Kernel" Feb 11 13:00:17 0x00160000-0x00180000 : "Ramdisk" Feb 11 13:00:32 but: FLASH: 0x50000000 - 0x50800000, 64 blocks of 0x00020000 bytes each. Feb 11 13:01:12 how can the "ramdisk" be at 0x00160000 when the flash starts at 0x50000000? Feb 11 13:35:43 rammy2: see the "move" command in the redboot source Feb 11 13:36:23 redboot copies the kernel and initrd from flash to ram, and then execs the kernel from ram, which reads the initrd from ram too Feb 11 13:37:07 and those partition offsets you are seeing the kernel print are just that - offsets, not physical addresses. Feb 11 13:38:10 aaahh0x1000000 Feb 11 13:38:19 thanks :) Feb 11 13:38:35 so this is the adress, where i have to put the initrd? Feb 11 13:39:01 there's a wiki page on testing images in ram Feb 11 13:39:51 (BTW, it's now your duty to update the wiki with the information above, where you would have expected to see it. Rule #3) Feb 11 13:41:01 ramdisk is at 0x01000000 and kernel is at 0x01d00000 Feb 11 13:41:38 thanks! ill update it :) Feb 11 13:41:48 err.. my ramdisk is too big Feb 11 13:42:14 yep, that's the second reason why we use jffs2 instead of ramdisk Feb 11 13:43:33 jffs has a better compression than gzip -9? Feb 11 13:44:20 no, jffs2 doesn't get copied into ram, and can therefore be up to about 6MB in size Feb 11 13:44:36 6mb.. Feb 11 13:44:39 i need perl Feb 11 13:44:43 :) Feb 11 13:45:17 my rootfs is 15mb big. created a 17mb large ext2 partition for that. gzipped, its 3,7mb big Feb 11 13:45:41 i thought, a 17mb big ramdisk would get into a ram of 32mb Feb 11 13:45:48 how big is it in jffs2? Feb 11 13:47:55 havent tryied it till now. i thought, jffs2 schouldnt have such a good compression as gzip Feb 11 13:48:48 have you tried ucslugc? Feb 11 13:50:45 nah, ive built uclibc+busybox for my own Feb 11 13:51:05 ok, good luck then. Feb 11 13:51:24 the problem is not the libc and the tools Feb 11 13:51:29 perl is the beast :) Feb 11 13:51:39 tried miniperl? Feb 11 13:52:09 ehh dunno, i compiled it under gentoo with useflag "minimal". i think, that should be miniperl Feb 11 13:52:50 sorry, I meant microperl Feb 11 13:53:24 see Makefile.micro in the perl build directory Feb 11 13:53:30 but do you know, if upslug2 --target=bla --ramdisk=should work? or is "--ramdisk" just build in as a placeholder for the future? Feb 11 13:53:33 We build it in Optware Feb 11 13:54:32 --target=bla --kernel=xy works.. but --ramdisk just prints out, as i wouldnt have typed any params: the list with slugs in upgrademode Feb 11 13:55:45 thats why im actually in redboot and tryied to figure out, where to store that initrd.gz.. :( Feb 11 13:57:34 I have never personally used upslug or upslug Feb 11 13:57:38 or upslug2 Feb 11 13:59:33 you ever loaded the files from tftp/http out of redboot? Feb 11 14:00:08 kk, ill try it too :) Feb 11 14:01:15 I wrote that page i referred to above Feb 11 14:03:26 http://www.nslu2-linux.org/wiki/HowTo/TestAnImageInRamUsingRedBoot Feb 11 14:04:38 hey :) thank you! Feb 11 16:29:21 rwhitby: that is correct for making a jffs2 image of my rootfs? "mkfs.jffs2 -d /tmp/rootfs -o bla.img" Feb 11 16:29:40 because thats my cmdline: CONFIG_CMDLINE="root=/dev/mtdblock4 rootfstype=jffs2 console=ttyS0,115200,8n noirqdebug init=/linuxrc ... Feb 11 16:30:15 and he everytime tells me, that there is no "linuxrc". but obviously, there is a linuxrc in /tmp/rootfs/ Feb 11 17:25:41 damn.. it was the wrong device.. Feb 11 17:25:58 the ramdisk is not /dev/mtdblock4 but /dev/mtdblock3 Feb 11 17:26:09 but now, the filesystem is wrong Feb 11 17:26:26 jffs2: Too few erase blocks (1) Feb 11 17:26:26 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3) Feb 11 17:26:45 any ideas, how i should create the jffs image of my rootfs? Feb 11 22:21:30 hi all Feb 11 22:21:46 Where is the end-user-channel again? Feb 11 22:31:59 Madkiss, #nslu2-general it is Feb 11 22:49:56 thanks **** ENDING LOGGING AT Sun Feb 12 10:59:58 2006