**** BEGIN LOGGING AT Tue Mar 25 02:59:56 2008
Mar 25 04:46:09 <massiverobot> hello
Mar 25 04:46:38 <massiverobot> does anyone know if ext3 is a module in the 2.6.23 kernels?
Mar 25 04:46:55 <massiverobot> I can't mount any ext3 partitioned CF cards
Mar 25 04:52:37 <summatusmentis> it's likely a module, but I don't know for sure
Mar 25 04:58:26 <massiverobot> ok, yeah, I tried to insmod it- i'm guessing it didn't get built....
Mar 25 04:58:53 <massiverobot> anyone know how to best turn it on? Probally a bb recipe somewhere....
Mar 25 05:00:30 <massiverobot> ah ok
Mar 25 05:00:51 <massiverobot> I see in my 2.6.23 poodle-config
Mar 25 05:00:51 <massiverobot> CONFIG_EXT3_FS=m
Mar 25 05:01:00 <massiverobot> so it must be in there somewhere
Mar 25 05:07:04 <summatusmentis> or possibly just not installed?
Mar 25 05:11:22 <massiverobot> yeah- I can't find it.
Mar 25 05:11:29 <massiverobot> I did a minimal-console
Mar 25 05:11:44 <summatusmentis> huh
Mar 25 05:12:06 <massiverobot> sorry - console-image
Mar 25 05:12:16 <massiverobot> I guess that isn't building in that module.
Mar 25 05:12:53 <summatusmentis> that's weird
Mar 25 05:13:25 <massiverobot> You have any idea what controls what gets built by these packages?
Mar 25 05:13:42 <massiverobot> i.e. console-image, x11-image, gpe-image
Mar 25 05:14:22 <summatusmentis> it's not really a matter of what gets built, it's just what's included
Mar 25 05:14:34 <summatusmentis> have you checked the feeds for a module?
Mar 25 05:14:58 <massiverobot> mmm, not sure what you mean by that- what feeds?
Mar 25 05:15:05 <summatusmentis> the package repos
Mar 25 05:15:23 <massiverobot> I tried an autobuild console-image and also one that I built locally.
Mar 25 05:15:24 <summatusmentis> using ipkg and all that
Mar 25 05:15:31 <massiverobot> ah no
Mar 25 05:15:44 <summatusmentis> you might try that
Mar 25 05:15:53 <massiverobot> you can install kernel modules via ipkg?
Mar 25 05:16:07 <massiverobot> something like " ipkg install ext3" ???
Mar 25 05:16:26 <summatusmentis> you can install a lot of things w/ ipkg
Mar 25 05:16:39 <summatusmentis> yeah, ipkg install <package name>
Mar 25 05:16:54 <summatusmentis> try ipkg list | grep ext3
Mar 25 05:18:07 <massiverobot> mmm, I see this in my OE monotone local.conf:
Mar 25 05:18:15 <massiverobot> # Add the required image file system types below. Valid are
Mar 25 05:18:15 <massiverobot> # jffs2, tar(.gz|bz2), cpio(.gz), cramfs, ext2(.gz), ext3(.gz)
Mar 25 05:18:15 <massiverobot> # squashfs, squashfs-lzma
Mar 25 05:18:16 <massiverobot> IMAGE_FSTYPES = "jffs2 tar ext3"
Mar 25 05:18:22 <massiverobot> I just added in the ext3
Mar 25 05:18:35 <massiverobot> perhaps that will build it into my image
Mar 25 05:19:52 <massiverobot> but yea, I'll try ipkg.
Mar 25 05:20:04 <massiverobot> THough I haven't really even had it on the network.....
Mar 25 05:22:09 <summatusmentis> no, that won't do it
Mar 25 05:22:30 <massiverobot> mmmm
Mar 25 05:22:33 <summatusmentis> in local.conf, all you did there was tell it that you wanted a loop image formatted to ext3
Mar 25 05:22:49 <massiverobot> well there has to be something that tells bb to install that kernel module...
Mar 25 05:22:52 <massiverobot> ah ok
Mar 25 05:25:48 <hvontres|home> massiverobot: most kernel modules come in through task-base.bb
Mar 25 05:26:51 <massiverobot> Mmmm, ok I think I see the issue- I'm building images for android (still ) and now I see that the android.patch is turning off EXT3 (I think....)
Mar 25 05:27:04 <massiverobot> +# File systems
Mar 25 05:27:04 <massiverobot> +#
Mar 25 05:27:04 <massiverobot> +# CONFIG_EXT2_FS is not set
Mar 25 05:27:04 <massiverobot> +# CONFIG_EXT3_FS is not set
Mar 25 05:27:04 <massiverobot> +# CONFIG_EXT4DEV_FS is not set
Mar 25 05:27:24 <massiverobot> isn't that patching EXT3_FS back to being commented out?
Mar 25 05:32:17 <hvontres|home> massiverobot: yes
Mar 25 05:32:40 <massiverobot> ok, I put it back in and built a new image....
Mar 25 05:36:27 <massiverobot> Arg- anyone here looked at the android.diff from benno or android zaurus?
Mar 25 05:36:59 <massiverobot> Now that I'm looking at it, it seems like it's turning on all the goldfish configs... I thought it was supposed to be turning them off.
Mar 25 05:41:25 <massiverobot> ah well, that didn't do it.
Mar 25 18:07:54 <strikov> hi! when i boot my new kernel with Samsung NAND i get `bad eraseblock error` for each block written using Atmel SAM-BA. It seems that its connected with ECC checking, but i switch it off!
Mar 25 18:43:31 <Miosc> hi all
Mar 25 18:45:09 <Miosc> id like to ask if someone can help with the following situation, when trying to bitbake kernel-handhelds i get the following error message : ../deploy/uclibc/images/"device" can not be found; you have to bitbake it separately
Mar 25 18:45:31 <Miosc> i've been googling for solutions for 2 days, but couldn;t find anything
Mar 25 18:45:40 <Miosc> except the offending commit:
Mar 25 18:45:47 <Miosc> http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg01802.html
Mar 25 18:45:55 <Miosc> i'm not sure what's causing this 
Mar 25 18:54:12 <Miosc> if anyone has suggestions, that i can try out, that'd be great
Mar 25 18:55:49 <Pixelized> miosc: no clue
Mar 25 18:56:04 <Pixelized> Miosc: question for you do you find that uclibc offers a major performance gain?
Mar 25 18:56:23 <Miosc> Pixelized: the weird thing is, it's glibc actually
Mar 25 18:56:37 <Pixelized> Miosc: ??
Mar 25 18:56:37 <Miosc> but for some reason it gets installed in uclibc
Mar 25 18:56:44 <Pixelized> euh
Mar 25 18:57:33 <Miosc> Pixelized: this is the reason i believe:
Mar 25 18:57:34 <Miosc> +KERNEL_INITRAMFS_PATH =  "${TMPDIR}/deploy/uclibc/images/${MACHINE}/initramfs-bootmenu-image-${MACHINE}.cpio.gz"
Mar 25 18:57:52 <Miosc> http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg01768.html
Mar 25 18:58:08 <Miosc> here;s the offending code, not the first link, sorry for that
Mar 25 18:58:55 <Miosc> this is what i did inside angstrom-2008.1.conf:
Mar 25 18:58:56 <Miosc> KERNEL_INITRAMFS_DIR = "${TMPDIR}/deploy/${ANGSTROM_MODE}/images/${MACHINE}/"
Mar 25 18:59:16 <Miosc> replaced uclibc with ${ANGSTROM_MODE}
Mar 25 18:59:21 <Pixelized> according to what i see
Mar 25 19:00:12 <Pixelized> +do_compile_prepend() { +       if [ -n "${KERNEL_INITRAMFS_PATH}" -a "${ANGSTROM_MODE}" == "glibc" ]; then
Mar 25 19:01:53 <Pixelized> that initramfs should be the full path to your cpio.gz image
Mar 25 19:02:33 <Miosc> Pixelized: yeah but it's pointing to /deploy/uclibc/images IIUC
Mar 25 19:02:51 <Pixelized> it should be pointed to where the cpio.gz image is
Mar 25 19:03:27 <Pixelized> Miosc: either copy your cpio.gz image there or locate cpio.gz ( or find / -name cpio.gz) and put that path in there instead
Mar 25 19:03:34 <Pixelized> thats my guess =)
Mar 25 19:04:12 <Miosc> yeah, but i can't find that file either :(
Mar 25 19:04:16 <Miosc> KERNEL_INITRAMFS_PATH = "${KERNEL_INITRAMFS_DIR}/$(readlink ${KERNEL_INITRAMFS_DIR}initramfs-bootmenu-image-${MACHINE}.cpio.gz)"
Mar 25 19:04:27 <Miosc> is what i have inside angstrom-2008.1.conf
Mar 25 19:56:07 <cyrilRomain> 'morning
Mar 26 00:21:30 <hvontres|work> xjqian: hehe.. I still remember "wuarchive.wustl.edu" from my early internet days (~1990) :)
Mar 26 00:22:41 <kolla> :)
Mar 26 00:22:47 <kolla> cdrom.com
Mar 26 00:23:15 <kolla> heh.. I still have to do "cd <backspace>rom.com" :)
**** ENDING LOGGING AT Wed Mar 26 02:59:56 2008