**** BEGIN LOGGING AT Wed Apr 06 23:59:56 2005
Apr 07 00:14:54 <siddy-away> update: the build of my 32bit-cpu works perfect. so it seems to be my athlon64's fault.
Apr 07 00:15:50 <VoodooZ_Work> yep. as expected.
Apr 07 00:16:24 <VoodooZ_Work> now if we could only narrow it down more. binutils, cross compiler, etc...
Apr 07 00:17:59 <siddy-away> well, I'll start with some cross-compilation-comparisions, perhaps it'll give me a hint.
Apr 07 00:18:40 <VoodooZ_Work> let me know.
Apr 07 00:18:41 <[g2]> I'd like to know what's busted, maybe you could loan me your AMD64 system and I could do some testing :)
Apr 07 00:18:56 <siddy-away> lol, good one!
Apr 07 00:19:02 <VoodooZ_Work> hehe
Apr 07 00:19:18 <VoodooZ_Work> I've got a quad opteron sitting here if you want it. ;)
Apr 07 00:19:34 <VoodooZ_Work> (I'm not sure the real owner would be too happy though) :)
Apr 07 00:19:57 <[g2]> actually, this is why I'd love to have some standard setups to verify output and we could gain some insight into these issues
Apr 07 00:20:16 <[g2]> this *isn't* supposed to be so cutting-edge
Apr 07 00:31:48 <siddy-away> the cross-compilers produce absolutely identical hello-world-programs. so, I'm stuck before I really started...
Apr 07 00:31:52 <siddy-away> :\
Apr 07 00:33:50 <VoodooZ_Work> damn
Apr 07 01:03:08 <siddy-away> *sigh* the two rootfs differ a bit in size, but chrooting into the one built by amd64 works like a charm, so why the f*** doesn't this thing boot?!
Apr 07 05:01:36 <siddy-away> omg, my slug is finally back online. please remind me that I won't reflash that thing ever again... ;)
Apr 07 05:02:04 <[cc]smart> think about the updates you'll miss .)
Apr 07 05:02:45 * siddy-away will stick to userspace-updates in the future.
Apr 07 05:03:15 <siddy-away> hm... too bad I forgot all my kernel-patches in my current image.
**** ENDING LOGGING AT Thu Apr 07 10:11:18 2005

**** BEGIN LOGGING AT Thu Apr 07 10:14:04 2005
Apr 07 10:27:28 <Denifia> Howdy.
Apr 07 10:28:10 <Denifia> Does anyone here know of a Networking or specific Linksys chat channel?
Apr 07 14:21:58 <jstueve> anyone here?
Apr 07 14:22:08 <ka6sox-laptop> back on the other channel
Apr 07 14:22:53 <jstueve> thx
Apr 07 22:31:43 <siddy-work> oh yeah, I just successfully booted an amd64-built openslug image! so, it really works!
Apr 07 22:31:48 * siddy-work parties
Apr 07 22:37:19 <[g2]> siddy-work, congrats!  what was the blocking issue ?
Apr 07 22:38:18 <siddy-work> I had to throw away lots of useless modules to make the slightly larger amd64-builds fit into the rootfs.
Apr 07 22:39:10 <siddy-work> it would have made life a whole lot easier if slugimage had refused to construct those broken images... ;)
Apr 07 22:40:10 <[g2]> ahh... so the rootfs was just plain to big eh ?
Apr 07 22:40:25 <[g2]> that would be a good check in slugimage
Apr 07 22:40:37 <[g2]> or you mean slugtool right ?
Apr 07 22:40:44 <siddy-work> yes, slugtool
Apr 07 22:40:52 <[g2]> the perl script
Apr 07 22:41:10 <siddy-work> the thing that constructs the image, whatever it's name might be. ;)
Apr 07 22:41:45 <[g2]> iirc it's slugtool.pl which is the successor to slugimage
Apr 07 22:58:08 <siddy-work> hm... there's no slugtool in my build-tree, so I guess we're using slugimage (which is there)
Apr 07 23:16:42 <peteru-home> What were the USB issues seen in openslug?
Apr 07 23:16:51 <peteru-home> Was it the following?
Apr 07 23:17:04 <peteru-home> scheduling while atomic: puppy/0x10000001/249
Apr 07 23:28:52 <[g2]> peteru-home, don't think that was an issue
Apr 07 23:55:01 <peteru-home> bummer, in that case I have a new one :(
**** ENDING LOGGING AT Thu Apr 07 23:59:56 2005