**** BEGIN LOGGING AT Fri Dec 07 02:59:57 2007
Dec 07 04:13:21 <DaedalusX> hey all
Dec 07 04:26:19 <CoreDump> hey
Dec 07 04:26:42 <Zero_Chaos> CoreDump: I thought you were in Europe...
Dec 07 04:27:10 <CoreDump> I am
Dec 07 04:27:30 <Zero_Chaos> CoreDump: give up sleep?
Dec 07 04:27:41 <CoreDump> my wake-sleep pattern is "slightly" off ATM
Dec 07 04:27:50 <Zero_Chaos> heh
Dec 07 04:28:01 <Zero_Chaos> Jetlag or random reason?
Dec 07 04:28:28 <CoreDump> random
Dec 07 04:28:52 <Zero_Chaos> CoreDump: does it have breats, or is it no good reason?
Dec 07 04:28:56 <Zero_Chaos> damnit
Dec 07 04:28:59 <Zero_Chaos> breasts*
Dec 07 04:29:10 <CoreDump> heh I widh
Dec 07 04:29:14 <CoreDump> *wish
Dec 07 04:29:44 <Zero_Chaos> CoreDump: well if you really can't sleep, you could look for the bug in updater.sh :-) that should make you tired...
Dec 07 04:29:47 <CoreDump> My sleep cycle is always fucked when I'm on holidays
Dec 07 04:30:06 <CoreDump> Oh, I pretty much gave up on that
Dec 07 04:30:32 <Zero_Chaos> CoreDump: yeah, everyone did...
Dec 07 04:30:43 <CoreDump> I'll try to reproduce the bug with spitz when my bloody build machine finally gets here
Dec 07 04:31:22 <Zero_Chaos> CoreDump: if the bug existed in spitz, then somone else would have found it and fixed it by now...
Dec 07 04:31:35 <CoreDump> no
Dec 07 04:32:01 <CoreDump> as spitz usually installs onto HDD via tar.gz, and not flash via jffs2
Dec 07 04:32:12 <Zero_Chaos> CoreDump: I suppose this is true...
Dec 07 04:32:28 <CoreDump> "flashing" a spitz requires a hacked kernel + updater.sh
Dec 07 04:33:27 <Zero_Chaos> CoreDump: well, if you are going to setup your spitz for flashing, it would be keen to commit the needed things, as I am certain some people would like to do the same.
Dec 07 04:34:09 <CoreDump> updater.sh is useless without the modified kernel
Dec 07 04:34:29 <Zero_Chaos> CoreDump: I know, I'm suggesting that you commit that too (since you are making it anyway)
Dec 07 04:34:35 <CoreDump> and I _really_ doubt Angstrom is gonna upload two different kernels for spitz
Dec 07 04:34:58 <Zero_Chaos> CoreDump: yeah, I suppose that extra 1.2M would really eat up the server space...
Dec 07 04:35:08 <CoreDump> Zero_Chaos: IIRC it boils down to setting some env vars and rebuilding zImage...
Dec 07 04:35:25 <Zero_Chaos> CoreDump: a wiki entry at least? :-)
Dec 07 04:35:48 <CoreDump> I'll think about it
Dec 07 04:36:13 <Zero_Chaos> CoreDump: there was a guy in here just today that wanted to flash his spitz, and if I had one, I know I would want to.  flash has some advantages
Dec 07 04:36:53 <CoreDump> Zero_Chaos: no it hasn't. Flash is dog-slow compared to the HDD
Dec 07 04:36:53 <DaedalusX> well this is bizarre
Dec 07 04:37:14 <CoreDump> due to the slow CPU and the compression in jffs2
Dec 07 04:37:22 <DaedalusX> my asix usb ethernet adapter (it's for the nintendo wii :P) is detected, the modules are loaded, it's given eth0 in ifconfig
Dec 07 04:37:27 <DaedalusX> but it doesn't do crap. :P
Dec 07 04:37:28 <CoreDump> (at least that was the case last time I checked)
Dec 07 04:37:30 <Zero_Chaos> CoreDump: really??? well still, the flash won't die in a magnet ;-)
Dec 07 04:38:06 <Zero_Chaos> DaedalusX: really, mine worked fine just yesterday.  Mind you, mine isn't for a nintendo wii
Dec 07 04:38:26 <DaedalusX> it shouldn't matter. it works fine on my desktop
Dec 07 04:38:39 <DaedalusX> it's a standard asix module
Dec 07 04:38:47 <Zero_Chaos> DaedalusX: yeah, it shouldn't matter, I was just saying.
Dec 07 04:39:17 <Zero_Chaos> DaedalusX: can you please define how it doesn't work? "ifconfig eth0 192.168.0.99 netmask 255.255.255.0" worked fine... I think...
Dec 07 04:39:43 <DaedalusX> I tried that though...
Dec 07 04:39:57 <Zero_Chaos> DaedalusX: what didn't work? wouldn't pass data or?
Dec 07 04:39:59 <DaedalusX> although, come to think of it, my router's outputs are crapping out :P
Dec 07 04:42:24 <DaedalusX> well when I plug it in, the led on the module blinks a few times, then goes out... then occaisionally blinks
Dec 07 04:42:47 <Zero_Chaos> DaedalusX: I have three leds, and they all blink.
Dec 07 04:42:57 <DaedalusX> yeah, but on my desktop the LED stays on.
Dec 07 04:43:27 <Zero_Chaos> interesting...
Dec 07 04:43:52 <DaedalusX> and I can't ping my desktop from it
Dec 07 04:44:01 <DaedalusX> hmmm
Dec 07 04:44:27 <DaedalusX> oh, after a little while it assigns a new interface, eth0:avah (I think that's something to do with avahi, but I have no idea what avahi is :P)
Dec 07 04:44:35 <DaedalusX> which gets some bogus ip address
Dec 07 04:45:31 <DaedalusX> I know it's getting enough power... I've got it on my powered usb hub
Dec 07 04:45:39 <Zero_Chaos> yeah, I don't understand avahi, but that is something else.
Dec 07 04:45:42 <DaedalusX> which has enough juice to run external harddrives
Dec 07 04:45:53 <DaedalusX> and it's also powering my bluetooth adapter just fine
Dec 07 04:46:05 <Zero_Chaos> hmm, dunno to be honest, I simply don't have that issue.
Dec 07 04:46:08 <DaedalusX> yeah
Dec 07 04:46:14 <DaedalusX> maybe it's a udev issue?
Dec 07 04:46:26 <Zero_Chaos> dunno, lemme test mine again real quick
Dec 07 04:46:49 <DaedalusX> when I run dmesg, I see: "eth0: link down"
Dec 07 04:49:50 <Zero_Chaos> DaedalusX: my card is able to pass data.
Dec 07 04:51:46 <DaedalusX> what does your Z say when you run dmesg?
Dec 07 04:52:03 <Zero_Chaos> link down, then it says link up after I ifconfig eth0 up
Dec 07 04:52:48 <DaedalusX> hmmm, mine blinks when I say ifconfig eth0 up
Dec 07 04:52:52 <DaedalusX> but doesn't actually go up
Dec 07 04:53:13 <DaedalusX> and says nothing new in dmesg
Dec 07 04:53:16 <DaedalusX> this is strange
Dec 07 04:53:19 <Zero_Chaos> yeah, mine does. not sure why.  Akita, 2.6.23-rp, powered hub...
Dec 07 04:53:22 <DaedalusX> maybe I'll try reinstalling the drivers
Dec 07 04:53:32 <DaedalusX> akita, 2.6.23-r9
Dec 07 04:53:34 <DaedalusX> powered hub :P
Dec 07 04:53:53 <Zero_Chaos> DaedalusX: Well if you like wifi security you can have my image :-)
Dec 07 04:53:56 <DaedalusX> could you run udevmonitor and unplug the device and plug it back in for me?
Dec 07 04:54:09 <Zero_Chaos> DaedalusX: not until it is done flashing ;-)
Dec 07 04:54:13 <DaedalusX> hah, you mean if I like my battery life disappearing? :P
Dec 07 04:54:22 <DaedalusX> it's amazing how fast my card eats the battery
Dec 07 04:54:26 <DaedalusX> it's like.... aaaaah
Dec 07 04:54:32 <DaedalusX> oh, and the card gets incredibly hot
Dec 07 04:54:44 <DaedalusX> all that for pretty short distance :P
Dec 07 04:54:52 <Zero_Chaos> DaedalusX: well you wouldn't have to use the stuff I have on there, but the image is pointlessly huge if you wouldn't ;-)
Dec 07 04:54:57 <DaedalusX> then again, it's pushing a fairly significant amount of data over it
Dec 07 04:55:06 <CoreDump> could one of you pastebin an ls -l /dev/mtdblock*
Dec 07 04:55:08 <CoreDump> ?
Dec 07 04:55:09 <DaedalusX> yeah well I'm shoving everything on a 4 GB sd card
Dec 07 04:55:17 <DaedalusX> sooooo pointlessly huge is probably not a problem :P
Dec 07 04:55:38 <Zero_Chaos> CoreDump: from normal root or from rescue flash mode?
Dec 07 04:55:51 <DaedalusX> hahahah
Dec 07 04:55:53 <CoreDump> I don't care actually ;)
Dec 07 04:56:10 <Zero_Chaos> DaedalusX: give me a place to drop it, you can test my image, if it works, then it's your fault, if it doesn't work, there is something else wrong...
Dec 07 04:56:34 <DaedalusX> CoreDump, they're all brw-rw----, group disk, 31 kB, and there are four of em
Dec 07 04:56:54 <DaedalusX> Zero_Chaos, I just really wonder why it works differently on my PDA from my desktop
Dec 07 04:57:00 <CoreDump> DaedalusX: I need one complete line please
Dec 07 04:57:07 <Zero_Chaos> DaedalusX: kernel/driver version
Dec 07 04:57:33 <DaedalusX> CoreDump, sorry, I'm not sshing into my zaurus atm, just looking at it. want me to copy over what I see?
Dec 07 04:57:42 <Zero_Chaos> I'll do it in a minute
Dec 07 04:57:56 <DaedalusX> brw-rw----   1 root     disk    31,  0 Dec 8 04:36 /dev/mtdblock0
Dec 07 04:58:08 <Zero_Chaos> or that
Dec 07 04:58:16 <CoreDump> DaedalusX: perfect, thanks
Dec 07 04:58:25 <DaedalusX> and the rest are the same except the 0 before Dec is 1 for /dev/mtdblock1, 2 for blah blah blah you get the picture
Dec 07 04:58:31 <DaedalusX> CoreDump, no problem
Dec 07 04:59:08 <Zero_Chaos> DaedalusX: I get a lot when I plug it in. (from udevmonitor)
Dec 07 04:59:31 <DaedalusX> I don't suppose you could PM it to me
Dec 07 05:00:03 <DaedalusX> what version of udev are you using?
Dec 07 05:00:11 <DaedalusX> you can get it from udevinfo -V
Dec 07 05:01:49 <Zero_Chaos> DaedalusX: I kinda have a hard time with that, what with the fact that I can't plug in my ethernet while connected over ethernet...
Dec 07 05:01:58 <DaedalusX> fair enough
Dec 07 05:02:00 <DaedalusX> don't worry about it
Dec 07 05:02:31 <Zero_Chaos> and I have no udevinfo
Dec 07 05:06:36 <CoreDump> RP: Spitz's kernel is unable to mount its jffs2 partitions, even when all modules are loaded. Any idea why that would be?
Dec 07 05:08:16 <CoreDump> /proc/mtd is also empty
Dec 07 05:20:04 <CoreDump> RP: looks like oebug #3283 explains it
Dec 07 05:29:56 * Zero_Chaos bangs head against wall
Dec 07 05:34:38 <Zero_Chaos> ~lart kernel module deps
Dec 07 06:05:30 <DaedalusX> uuuugh ipkg is sloooooooowwwww
Dec 07 06:05:58 <cofeineSunshine> or not working;/
Dec 07 06:06:32 <DaedalusX> or both.
Dec 07 06:06:45 <DaedalusX> it shouldn't take 15 minutes to install a 7 kB file
Dec 07 06:06:52 <DaedalusX> does it go through alllll of the status files or something?
Dec 07 06:07:08 <cofeineSunshine> dunno
Dec 07 06:07:19 <cofeineSunshine> i wasnt so lucky to get it working;/
Dec 07 06:07:53 <DaedalusX> cofeineSunshine, it's not working, period?
Dec 07 06:08:37 <cofeineSunshine> failed to update lists
Dec 07 06:08:49 <cofeineSunshine> but internet on it was working
Dec 07 06:08:56 <cofeineSunshine> so i didnt bother
Dec 07 06:08:59 <DaedalusX> hmmm
Dec 07 06:09:07 <DaedalusX> sure that ftp isn't blocked?
Dec 07 06:09:48 <cofeineSunshine> ghm
Dec 07 06:10:04 <cofeineSunshine> i feel like bluetooth connection is some kind shitty
Dec 07 06:10:13 <cofeineSunshine> but i'll give another try')
Dec 07 06:10:25 <cofeineSunshine> DaedalusX, and what do you use for music listening?
Dec 07 06:10:30 <cofeineSunshine> on handheld?
Dec 07 06:10:50 <cofeineSunshine> and another think, i've bought 2gb sd card, but i cant to boot from it
Dec 07 06:11:06 <cofeineSunshine> and i have old, 256mb card, it works perfectly
Dec 07 06:11:17 <cofeineSunshine> i even tryed dd from one card to another
Dec 07 06:11:24 <DaedalusX> cofeineSunshine, xmms
Dec 07 06:11:24 <cofeineSunshine> that didn't help;/
Dec 07 06:11:33 <cofeineSunshine> on angstrom?
Dec 07 06:11:34 <cofeineSunshine> nice\
Dec 07 06:11:35 <cofeineSunshine> !
Dec 07 06:11:50 <DaedalusX> 1 GB is technically the maximum capacity of SD cards, specification wise
Dec 07 06:11:58 <cofeineSunshine> oh, i see
Dec 07 06:12:03 <DaedalusX> but my Transcend 4 GB card works great! :)
Dec 07 06:12:08 <DaedalusX> hard to find though
Dec 07 06:12:15 <cofeineSunshine> can you boot from it?
Dec 07 06:12:16 <DaedalusX> but they WILL work
Dec 07 06:12:26 <DaedalusX> I dunno. I haven't tried.
Dec 07 06:12:44 <DaedalusX> I just stick my packages on SD and use ipkg-link to symlink all the stuff onto the flash
Dec 07 06:12:45 <cofeineSunshine> so, you keep your kernel in device memory, intead of sf card?
Dec 07 06:12:51 <DaedalusX> yeah
Dec 07 06:12:57 <cofeineSunshine> i C
Dec 07 06:13:03 <cofeineSunshine> i'll try to do that to
Dec 07 06:13:14 <cofeineSunshine> you using LAB?
Dec 07 06:13:18 <DaedalusX> LAB?
Dec 07 06:13:20 <cofeineSunshine> linux as bootloader
Dec 07 06:13:33 <cofeineSunshine> hum, what device do you have?
Dec 07 06:13:38 <DaedalusX> I dunno. I'm using whatever the akita uses
Dec 07 06:13:42 <DaedalusX> no altboot or anything
Dec 07 06:13:44 <cofeineSunshine> iC
Dec 07 06:13:48 <cofeineSunshine> ok
Dec 07 06:14:48 <cofeineSunshine> mines is ipaq h2200, so i have to change 2nd bootloader with LAB
Dec 07 06:14:53 <DaedalusX> gotcha
Dec 07 06:15:15 <DaedalusX> I dunno how powerful the h2200 is, but if you use MAD for the MP3 decoding, it should probably be fast enough
Dec 07 06:15:18 <DaedalusX> MAD is fixed point
Dec 07 06:15:27 <DaedalusX> so no sloooowwww FPU emulation involved.
Dec 07 06:16:07 <DaedalusX> be back in a minute
Dec 07 06:16:31 <cofeineSunshine> k
Dec 07 06:17:14 * CoreDump wonders why nobody has ported LAB to the zauruses yet. It would solve many problems in one go
Dec 07 08:33:48 <summatusmentis> what're the standard angstrom images called? just console-image and x11-image?
Dec 07 08:33:56 <summatusmentis> or is it angstrom-console-image?
Dec 07 08:52:23 <RP> CoreDump: Someone recently mentioned the flash driver has to be compiled it for the zaurus
Dec 07 08:52:27 * RP needs to fix that
Dec 07 09:39:50 <hrw> morning
Dec 07 09:40:18 <hrw> cofeineSunshine: why LAB? why not use apex/redboot/u-boot?
Dec 07 09:40:28 <hrw> s/cofeineSunshine/CoreDump
Dec 07 09:41:21 <hrw> I do not like idea of LAB on Zaurus
Dec 07 09:44:01 <koen> lab is quite big for a bootloader
Dec 07 09:44:12 <hrw> and its hh.org stuff
Dec 07 10:01:52 <CoreDump> RP: I see, thanks
Dec 07 10:03:24 <CoreDump> it being from hh.org is indeed unfortunate
Dec 07 10:03:24 <hrw> how many devices use it? 
Dec 07 10:03:24 <hrw> few ipaqs?
Dec 07 10:03:24 <CoreDump> yeah
Dec 07 10:03:34 <hrw> so it lack any support or devels
Dec 07 10:03:44 <koen> afaik only h2200 uses LAB
Dec 07 10:03:45 <CoreDump> but its principle of operation is bloody brilliant. It just replaces zImage
Dec 07 10:03:52 <koen> the rest uses some form of bootldr
Dec 07 10:03:58 <CoreDump> or that is what I made of the sucky docs
Dec 07 10:04:24 <koen> and h2200 uses it as second stage loader, so you don't brick it when messing up LAB
Dec 07 10:04:53 <koen> CoreDump: it's kernel + armboot (kexec predecessor)
Dec 07 10:05:17 <koen> it parses 'labrun' files on media is can read (cf, sd, NAND)
Dec 07 10:05:50 <koen> speaking of bootldr, I need to poke SDG to make a new one for angstrom that *does* read /boot/params
Dec 07 10:07:01 <CoreDump> an alternative would be u-boot, but the pdax stuff is kinda pdax specific ( can't boot generic distro or so I read)
Dec 07 10:07:33 <koen> and it still keeps the kernel in a seperate partition
Dec 07 10:07:52 <CoreDump> really? lol
Dec 07 10:08:07 * koen hopes that partition isn't using FTL like the original bootloader did
Dec 07 10:08:24 <CoreDump> what a pointles exercise
Dec 07 10:08:27 <koen> uboot reads jjfs2 really slowly and sash is using all the nand as /
Dec 07 10:17:52 <hrw> I am ok with u-boot on Z and 2MB /boot + / + /home
Dec 07 10:18:13 <hrw> 2MB /boot/ to have kernels in filesystem but have fast booting
Dec 07 10:18:18 <koen> right
Dec 07 10:18:47 <hrw> and 2MB to have space for more things
Dec 07 10:19:04 <koen> we could try to cram in kexec in initramfs that kexecs a kernel from /
Dec 07 10:19:15 <koen> would save up from reflashing the kernel over and over again
Dec 07 10:19:27 <hrw> this is what we consider with lumag
Dec 07 10:19:42 <hrw> problem is that Z kernels are hard to get <500KB
Dec 07 10:20:15 <koen> LAB had patches to fix that
Dec 07 10:20:39 <hrw> but never hit mainline
Dec 07 10:21:49 <hrw> and I do not want to fight hh.org devs to get it mainline
Dec 07 10:23:01 <koen> right
Dec 07 10:43:41 <lumag> hi all!
Dec 07 10:57:32 <ABC|dOC> hi !
Dec 07 12:25:15 <Freak_NL> Hi
Dec 07 12:26:03 <Freak_NL> I am setting up the OE env for Ångström, but it is throwing a warning about the bitbake version
Dec 07 12:26:13 <Freak_NL> it wants 1.8.9?
Dec 07 12:26:54 <koen> yes, and?
Dec 07 12:27:14 <Freak_NL> It doesn't seem to exist at http://developer.berlios.de/project/showfiles.php?group_id=2701&release_id=12930
Dec 07 12:33:24 <Freak_NL> Do I need a SVN version of Bitbake or should I force it to use 1.8.8?
Dec 07 12:43:38 <ffc> Koen: I updated OE, now it says "575e3741db66260805f359854a0513606534de50"
Dec 07 12:43:56 <ffc> I compiled linux-rp with IPv6 and MIPv6 options enabled
Dec 07 12:44:16 <ffc> but something's missing, because mipv6 is not working
Dec 07 12:46:54 <Freak_NL> Was bitbake 1.8.9 removed for some reason? Google finds traces of it being in use, but I can't seem to find it
Dec 07 12:47:10 <CoreDump> svn co it?
Dec 07 12:47:13 <rwhitby> Freak_NL: 1.8.9 means trunk
Dec 07 12:47:29 <Freak_NL> rwhitby: thanks
Dec 07 12:47:56 <rwhitby> For some reason, koen has decided that releases are not required anymore and that OE metadata should just require the unstable bitbake trunk.
Dec 07 12:48:04 <Freak_NL> Might be nice to mention it on http://www.angstrom-distribution.org/building-angstrom
Dec 07 12:48:27 <CoreDump> I guess he just forgot to tag it
Dec 07 12:48:43 <rwhitby> I thought tags were always even numbers
Dec 07 12:48:46 <CoreDump> in any case, you can use a fixed SVNREV if you desire so ;)
Dec 07 12:48:53 <CoreDump> *shrug*
Dec 07 12:49:15 <rwhitby> Looks like pretty haphazard SCM to me.
Dec 07 12:49:45 * koen has nothing to with bitbake svn or bitbake releases
Dec 07 12:49:59 <rwhitby> ah, but you changed sanity
Dec 07 12:50:08 <koen> that's zecke's and RP's territory
Dec 07 12:50:34 <rwhitby> that's funny, I thought I saw your name on the sanity checkin
Dec 07 12:50:41 <rwhitby> maybe I was mistaken
Dec 07 12:51:11 <koen> how does a checkin in OE make me responsible for bitbake svn?
Dec 07 12:51:24 <koen> I don't have commit access to bitbake, check the berlios page
Dec 07 12:51:28 <rwhitby> cause you're requiring a version of bitbake which is not released.
Dec 07 12:51:37 <rwhitby> (as in the formal usage of the word released)
Dec 07 12:52:43 <rwhitby> and you've done it without warning anyone in advance, thereby breaking all builds of people who have followed the previous instructions to only ever use bitbake tagged releaeses.
Dec 07 12:53:04 <rwhitby> I should disapprove it.
Dec 07 12:54:19 <koen> poking the bitbake people to do a 1.8.10 release would be a more helpfull approach
Dec 07 12:54:27 <koen> I've given up asking for bitbake releases
Dec 07 12:54:30 <rwhitby> no, sorry, it doesn't work like that.
Dec 07 12:54:45 <rwhitby> You simply do *not* change sanity until there *is* a bitbake release.
Dec 07 12:55:34 <ant|work392> hi all
Dec 07 12:55:38 <koen> I thought sanity should make sure that it lists the version that is required for the current metadata
Dec 07 12:55:58 <ffc> when I try to run /etc/init.d/mobile-ipv6 start, errors raise
Dec 07 12:56:10 <rwhitby> Software configuration management is not done by blackmail.
Dec 07 12:56:36 <ffc> FATAL: Module mip6_base not found.
Dec 07 12:56:48 <ant|work392> koen: I have some doubts about QA notes from insane.bbclass
Dec 07 12:56:48 <ffc> FATAL: Module mip6_ha not found.
Dec 07 12:57:00 <ffc> ./mobile-ip6: ./mobile-ip6: 1: cannot create /proc/sys/net/ipv6/mobility/min_tnls: Directory nonexistent./mobile-ip6: ./mobile-ip6: 1: cannot create /proc/sys/net/ipv6/mobility/max_tnls: Directory nonexistent
Dec 07 12:57:01 <koen> ffc: are those modules still needed with 2.6.23?
Dec 07 12:57:03 <Freak_NL> "This is a Bitbake from the Unstable/Development 1.9 Branch. This software contains gaping security holes and is dangerous to use!"
Dec 07 12:57:11 <Freak_NL> lovely :)
Dec 07 12:57:36 <ffc> They're the same arrors as when I used 2.6.22
Dec 07 12:57:36 <rwhitby> Freak_NL: seems that's the state of OE configuration management today, courtesy of koen
Dec 07 12:57:43 <ffc> it's strange
Dec 07 12:58:15 <ffc> which version should be compiled for mipv6?
Dec 07 12:58:34 <Freak_NL> "You might want to use the bitbake-1.8 stable branch (if you are not a BitBake developer or tester). I'm going to sleep 5 seconds now to make sure you see that."
Dec 07 12:58:40 <koen> ffc: is that initscript written for the 2.4 patch or for the current mip6 situation?
Dec 07 12:58:56 <ffc> one minute, I'll check it
Dec 07 12:59:02 <ant|work392> koen: everybody seems to ignore the warning "NOTE: preferred version 2.5 of glibc not available"
Dec 07 12:59:44 <Freak_NL> It is building, thanks for the assistance
Dec 07 13:00:35 <rwhitby> Freak_NL: except that as soon as one of the bitbake developers decides (as is their right on the unstable trunk) to check in an incompatible or broken change, your build will break again.
Dec 07 13:01:05 <rwhitby> and that breakage will also be koen's fault, for making sanity depend on an unreleased version.
Dec 07 13:01:37 <koen> rwhitby: no, it will be your fault for telling people to use trunk instead of the bitbake-1.8 stable branch
Dec 07 13:01:52 <CoreDump> RP: could you (or whoever has BB r/w access) please tag 1.8.10?
Dec 07 13:02:10 <Freak_NL> Sanity tells me to use "1.8.9", so who should the novice OE user believe?
Dec 07 13:02:12 <rwhitby> koen: just admit you've done something wrong and get on it
Dec 07 13:02:12 <CoreDump> see? wasn't so bad ;)
Dec 07 13:02:38 <ffc> koen: 2.4
Dec 07 13:02:40 <ffc> :-(
Dec 07 13:03:21 <rwhitby> CoreDump: except that should happen ahead of sanity changing, and there should be an email to the list saying that sanity is going to require a new version of bitbake in X days time.
Dec 07 13:03:33 <ffc> are not there user tools for 2.6 kernel?
Dec 07 13:03:33 <CoreDump> I agree
Dec 07 13:05:48 * XorA returns from lunch and screams
Dec 07 13:06:15 <ffc> koen: I've jkust seen 2.0.2 version
Dec 07 13:06:22 <ffc> Sorry :-)
Dec 07 13:09:32 <ffc> 1.1-v2.4.26 version is set as preferred version for Angstrom anyway
Dec 07 13:09:45 <ffc> shouldn't be changed to 2.0.2?
Dec 07 13:10:02 <ffc> as long as 2.6 kernel is used, I mean
Dec 07 13:10:16 <rwhitby> Freak_NL: use branches/bitbake-1.8, but be prepared for breakage there to, cause we were explicitly told many times over that you should only use tagged releases of bitbake.  Yes, the bitbake folks tell you that the "stable" branch isn't stable, so you should only used tagged releases, yet koen makes sanity require something that is not released (and is an odd-numbered moving target version)
Dec 07 13:11:34 <koen> I checked in a fix from poky that I can't backport to an older bitbake
Dec 07 13:11:55 <koen> I realized that *after* made the checking and bumped sanity to reflect that
Dec 07 13:12:04 <XorA> johncylee: welcome to the jungle, we got fun and games :-)
Dec 07 13:12:50 <koen> I'm not to keen on backing out the package_ipk fix, since it fix a shitload of problems
Dec 07 13:14:14 <rwhitby> correct configuration management is a bitch
Dec 07 13:16:44 <Genesis> yop
Dec 07 13:17:03 <rwhitby> Hmm - bitbake 1.8.8 tagged release to bitbake 1.8 stable branch head is hundreds of lines of changes.  Hope it's been tested well.
Dec 07 13:18:00 <koen> the autobuilder has been using head of the bitbake-1.8 branch for months
Dec 07 13:18:14 <koen> which is why I didn't notice the problem right away
Dec 07 13:19:12 <koen> the "Crap, lockfile is in the 1.8.9 section of ChangeLog" moment
Dec 07 13:20:26 <CoreDump> well, if trunk doesn't cause any breakage, everything is fine.
Dec 07 13:20:53 <CoreDump> but tagging trunk with nearly untested code as "stable" isn't a solution either
Dec 07 13:21:01 <koen> it isn't
Dec 07 13:21:49 <ffc> How can I add support for MIPv6 in kernel headers?
Dec 07 13:21:52 * rwhitby considers whether to change MokoMakefile, so hundreds of developers don't experience the unplanned sanity breakage, or not doing it because the Makefile is useless and they all should be forced to work out which branch and version of bitbake they need to use ...
Dec 07 13:22:50 <rwhitby> johncylee: better not sync the OM monotone repo until this is sorted out
Dec 07 13:24:16 <johncylee> rwhitby: hmmm the build failed since 12/1 so I'm not hurry
Dec 07 13:24:28 <CoreDump> heh
Dec 07 13:26:04 * CoreDump looks out of the window
Dec 07 13:26:16 <CoreDump> It's a bloody storm out there
Dec 07 13:26:27 * rwhitby goes back to putting lots of usb stuff *inside* his router (where the hard disk used to be): http://www.nslu2-linux.org/gallery/FSG3-Hacking/IMGP6151
Dec 07 13:28:28 <CoreDump> rwhitby: nice hack!
Dec 07 13:28:31 <rwhitby> johncylee: I have a mokomakefile change ready which will update everyone to the 1.8 branch, but unless you're intending to sync the OM monotone database, then I'd like to hold onto it and not push it until the bitbake folks do a 1.8.10 tagged release
Dec 07 13:29:20 <rwhitby> CoreDump: just to the left of the disk power connector are the pads for the fifth internal USB interface - that's the one I'm using to connect the internal hub.
Dec 07 13:30:10 <rwhitby> I think it's the first wireless usb router in the world with internal bluetooth access point functionality too.
Dec 07 13:30:19 <CoreDump> =D
Dec 07 13:30:20 <johncylee> rwhitby: got it.  
Dec 07 13:31:50 <ant|work392> * ant thinking to open the ol' Zyxel and stuff the Zaurus inside it...
Dec 07 13:32:50 <hrw> rwhitby: btw - mokomakefile is !#ansgstrom rather ;)
Dec 07 13:33:18 <rwhitby> hrw: nod
Dec 07 13:33:37 <rwhitby> in fact this whole saga should have been in #oe instead of here.
Dec 07 13:37:46 <ffc> is needed to clean anything when adding DISTRO_FEATURES on distro configuration?
Dec 07 13:39:16 <koen> ffc: why do you keep going on about DISTRO_FEATURES?
Dec 07 13:39:40 <koen> it isn't needed for mip6 support
Dec 07 13:41:41 <ffc> yes, you told me the other day
Dec 07 13:41:57 <ffc> but I'm trying to compile mipv6 package
Dec 07 13:42:16 <ffc> and it tells me that kernel headers have no MIPv6 support
Dec 07 13:42:30 <ffc> and I don't know how to add this support
Dec 07 13:43:01 <ffc> now I'm using 2.0.2 mipv6 version
Dec 07 13:46:31 <koen> ffc: what happens if you switch the two -I statements in the mipv6 recipe?
Dec 07 13:50:26 <ffc> you mean CFLAGS, right?
Dec 07 13:50:32 <ffc> I've changed with same result
Dec 07 13:51:43 <hrw> MIPv6 is in which kernel version?
Dec 07 13:53:49 <ffc> I'm using 2.6.23
Dec 07 13:55:52 <ant|work392> bb
Dec 07 13:56:47 <ffc> Well, I've got to leave... I'll ask again on Monday. Thank you!!
Dec 07 14:08:01 <lumag> !seen Spyr1
Dec 07 14:08:03 <cdbot2> Spyr1 (n=ian@i-195-137-94-162.freedom2surf.net) was last seen parting #oe 24 days, 14 hours, 14 minutes ago stating "{}".
Dec 07 16:19:23 <RP> CoreDump: No, as I said in #oe earlier it has some issues I want fixed before I do that. OE should not be requiring 1.8.9
Dec 07 16:51:04 <Jen00> Hi, I would like to use uim.  I compiled it with OE, but I cannot install it.  ipkg complains that the dependency libuim0 is missing.
Dec 07 16:51:32 <Jen00> I cannot find the dependency anywhere or how to compile it.  What can I do?
Dec 07 17:02:12 <ant|work246> !logs
Dec 07 17:02:12 <cdbot2> Channel logs for #angstrom are archived at:
Dec 07 17:02:13 <cdbot2> http://hentges.net/tmp/logs/irc/%23angstrom
Dec 07 17:02:14 <cdbot2> Live-logs are available at
Dec 07 17:02:16 <cdbot2> http://hentges.net/tmp/logs/irc/livelogs/%23angstrom.livelog
Dec 07 17:02:18 <cdbot2> See ?? help-logs for usage instructions
Dec 07 17:14:29 <lumag> bye!
Dec 07 18:11:00 <Genesis> bye
Dec 07 20:22:42 <gmad> Hello!
Dec 07 20:40:34 <Sketch> woo, woo
Dec 07 20:40:45 <Sketch> er, -woo
Dec 07 20:40:59 <Sketch> the akita image works fine on the c3100
Dec 07 20:41:15 <Sketch> so i was able to install without having to reformat/repartition the drive
Dec 07 20:41:21 <Sketch> and it recognizes and mounts the drive just fine
Dec 07 20:41:50 <Sketch> also, the cacko installer.sh worked fine, i just had to rebuild it's tools.tar to include angstrom's kernel  ;)
Dec 07 21:00:27 <gmad> and I am fighting anoter day with lan connection on my Z
Dec 07 21:00:41 <gmad> I can't set internet connection in any way
Dec 07 21:03:11 <hvontres|home> Furre: hey , welcome back :)
Dec 07 21:10:46 <Furre> Hello, o.o
Dec 07 21:21:44 <gmad> hello, anybody is here?
Dec 07 21:24:17 <hvontres|home> gmad: yes?
Dec 07 21:24:25 <summatusmentis> what's up gmad 
Dec 07 21:24:32 <summatusmentis> oh, hvontres|home beat me to it
**** ENDING LOGGING AT Sat Dec 08 02:59:57 2007