**** BEGIN LOGGING AT Wed Feb 28 03:00:01 2007
Feb 28 03:23:24 <jason0_> anyone built a 2.6.18-4 or 2.6.20 image w/ intel driver support?
Feb 28 03:24:49 <theblue> rwhitby, You alive?
Feb 28 03:25:15 <rwhitby> yep
Feb 28 03:25:33 <theblue> I've gotten to the kernel selection for Debian, what should I choose?
Feb 28 03:25:36 <theblue> My options are:
Feb 28 03:25:41 <theblue> linux-image-ixp4xx
Feb 28 03:25:50 <theblue> linux-image-2.6.18-3-ixp4xx
Feb 28 03:25:57 <theblue> linux-image-2.6-ixp4xx
Feb 28 03:26:06 <theblue> Or, rather confusingly, 'none'.
Feb 28 03:26:34 <rwhitby> the third one
Feb 28 03:26:44 <theblue> Ok, and might I ask why?
Feb 28 03:26:58 <rwhitby> cause then it will upgrade to -4 later
Feb 28 03:27:02 <theblue> Makes sense.
Feb 28 03:27:15 <theblue> Now it wants to know what to generate the boot initrd with, yaird or initramfs-tools?
Feb 28 03:27:25 <rwhitby> initramfs-tools
Feb 28 03:27:39 <theblue> I've never been asked that before, what does it mean?
Feb 28 03:28:09 <jason0_> rwhitby: any idea whne 2.6.18-4 is going to be ready for nslu2?
Feb 28 03:28:22 <rwhitby> jason0_: it's already in testing
Feb 28 03:28:31 <rwhitby> s/testing/unstable/ maybe
Feb 28 03:28:44 <jason0_> rwhitby: when you upgrade the kernel do you have to reflash the slug or is it just a simple apt-get
Feb 28 03:28:50 <theblue> I think it's an apt-get.
Feb 28 03:28:59 <rwhitby> apt-get calls flash-kernel which reflashes
Feb 28 03:29:03 <theblue> Oh.
Feb 28 03:29:24 <jason0_> hm.. I'd really like to to get 2.16.18-4 so rtorrent works.
Feb 28 03:29:26 <theblue> Either way.
Feb 28 03:30:09 <rwhitby> jason0_: what do you currently have installed?
Feb 28 03:30:24 <jason0_> 2.6.18-3
Feb 28 03:31:02 <rwhitby> I thought Martin posted an email on how to upgrade from there ...
Feb 28 03:31:29 <jason0_> in nslu2-linux/general on yahoo groups?
Feb 28 03:31:39 <theblue> rwhitby, Did I tell you about how to use RC1 (at least temporarily) and still have it work?
Feb 28 03:31:50 <rwhitby> theblue: yes
Feb 28 03:32:04 <theblue> Ok, I wasn't sure if I said in this channel or somewhere else.
Feb 28 03:32:06 <rwhitby> jason0_: I forget where
Feb 28 03:33:44 <rwhitby> jason0_: have you checked the unstable debian repo?
Feb 28 03:34:20 <jason0_> Yeah I know it's in there, but when I asked about how to upgrade in #debian everyone advised against it. I'm willing to take a gamble.
Feb 28 03:34:56 <theblue> Someone has to be, otherwise there's no development.
Feb 28 03:35:10 * theblue runs off to update the wiki.
Feb 28 03:35:24 <rwhitby> take a backup of your flash with cat /dev/mtdblock* > backup.bin, and then you can always upslug2 it back again if things go horribly wrong.  Same with the disk (take a backup first)
Feb 28 04:28:33 <CIA-6> 03bzhou * r5651 10optware/trunk/ (4 files in 3 dirs): added and promoted launchtool for non-uclibc platforms
Feb 28 04:40:33 <jason0_> rwhitby: do the debian repo's include the onboard ethernet adapter support?
Feb 28 04:42:34 <theblue> jason0_, Nope.
Feb 28 04:42:45 <theblue> YAY!
Feb 28 04:43:06 <theblue> I hereby christen thee 'chadwick'!
Feb 28 04:43:15 * theblue breaks a bottle of champagne on the side of the rack!
Feb 28 04:45:38 <jason0_> So if they don't include the ethernet support, wouldn't people be hozed when they did an apt-get upgrade?
Feb 28 04:46:24 <theblue> No, since the microcode is included in the image.
Feb 28 04:47:00 <jason0_> so the debian repo "images" should include the microcode.
Feb 28 04:47:22 <theblue> I guess.
Feb 28 04:49:09 <rwhitby> there are no "debian repo images"
Feb 28 04:49:15 <rwhitby> only slug-firmware.net images
Feb 28 04:49:35 <rwhitby> the microcode cannot be distributed by Debian, cause it's not DFSG compliant
Feb 28 04:52:12 <jason0_> When I try to build the cross compile env. I get an error: make[1]: *** [configure-arm-linux-gnu-stamp] Error 127. Can't seem to resolve it otherwise I'd build the image myself.
Feb 28 04:57:09 <rwhitby> jason0_: why not just install the RC1 like theblue did, then upgrade the kernel from there?
Feb 28 04:58:11 <jason0_> I did install RC1 a few weeks ago.
Feb 28 04:58:59 <rwhitby> so point your apt/sources.list to an unstable arm repo and upgrade
Feb 28 05:01:46 <jason0_> I must be totally off base about the microcode thing.  I thought if I used the repo then that means no microcode
Feb 28 05:02:35 <jason0_> and therefore no ethernet support
Feb 28 05:03:47 <rwhitby> the microcode is likely on your disk already - it should have been installed with RC1 I believe
Feb 28 05:04:34 <jason0_> So the microcode isn't used internally in the kernel, but delegated to at startup?
Feb 28 05:04:50 <jason0_> I thought the microcode had to be compiled into the kernel, thats why I was confused
Feb 28 05:05:10 <rwhitby> the microcode cannot be compiled into the kernel - that would be a *huge* intel license violation
Feb 28 05:05:34 <jacques> and GPL license violation
Feb 28 05:06:02 <jason0_> Okay, that makes it clear then. When I was reading the BuildImage directions I misunderstood that it had to be built it, hence my confusion. 
Feb 28 05:06:14 <jason0_> *in
Feb 28 05:07:36 <rwhitby> jacques: yeah, but I fear Intel's lawyers more than Richard Stallman :-)
Feb 28 05:13:46 <theblue> Yikes!
Feb 28 05:14:08 <theblue> rwhitby, Were you the one who found the microcode?
Feb 28 05:14:52 <rwhitby> you download the microcode from intel's site when you build an image
Feb 28 05:16:41 <theblue> I see.
Feb 28 05:17:02 <theblue> Thanks once again for the help, chadwick's running beautifully now.
Feb 28 05:23:13 <jason0_> upgrading now. 
Feb 28 05:26:45 <CIA-6> 03bzhou * r5652 10optware/trunk/make/python24.mk: python24: reuse the same host build if we can; a couple of small improvements
Feb 28 05:26:57 <CIA-6> 03bzhou * r5653 10optware/trunk/make/python25.mk: python25: reuse the same host build if we can; a couple of small improvements
Feb 28 05:27:08 <CIA-6> 03bzhou * r5654 10optware/trunk/make/python.mk: python: python-stage includes -stage -host-stage for python24 & python25
Feb 28 05:37:25 <rwhitby> theblue: your slug is in a rack?
Feb 28 05:39:26 <jason0_> rwhitby: reboot worked, running 18-4, thanks for your patience.
Feb 28 05:39:53 <rwhitby> jason0_: glad to hear it.  which wiki pages can you update to make it easier for the next person?
Feb 28 05:40:50 <jason0_> I'll browse nslu2-linux and see where it's appropriate.
Feb 28 05:46:08 <rwhitby> under http://www.nslu2-linux.org/wiki/Debian/HomePage somewhere.
Feb 28 12:48:32 <VoodooZ> rwhitby: How does a cross compiler find the non-system (in this case opencv) libraries? it can't use the host's ldconf.so?
Feb 28 12:48:51 <rwhitby> dunno
Feb 28 12:48:56 <VoodooZ> darn.
Feb 28 12:49:11 <VoodooZ> I guess I'll try to build it outside of OE then.
Feb 28 15:02:39 <CIA-6> 03bzhou * r5655 10optware/trunk/make/ntop.mk: ntop: added pcre to DEPENDS and -stage
Feb 28 15:16:33 <CIA-6> 03nail * r5656 10optware/trunk/sources/buildroot/buildroot.ts101: Update ts101 buildroot config
Feb 28 15:19:50 <CIA-6> 03nail * r5657 10optware/trunk/sources/buildroot/uclibc.ts101: Update ts101 uclibc config
Feb 28 15:21:06 <NAiL> eno: ping?
Feb 28 15:21:23 <NAiL> eno: I can't get it to actually *use* that config file. Not quite sure why.
Feb 28 15:21:54 <CIA-6> 03nail * r5658 10optware/trunk/sources/ts101-kernel-modules/kernel.defconfig: ts101-kernel-modules: Update kernel config
Feb 28 15:35:06 <Blastur> hey!
Feb 28 15:52:59 <NAiL> eno: vxwidgets built if I replaced binutils ;-)
Feb 28 16:13:45 <CIA-6> 03nail * r5659 10optware/trunk/make/buildroot.mk: buildroot: Hack around missing uclibc.config
Feb 28 16:22:15 <eno> NAiL: ts101 toolchain is building here, good you get wxbase working
Feb 28 16:23:37 <eno> will be in a long meeting this whole morning
Feb 28 16:25:04 <NAiL> eno: cool
Feb 28 16:25:11 <NAiL> I'm still building toolchain too
Feb 28 16:28:49 <NAiL> I think most of the failed packages now are either very obscure errors or glib failing
Feb 28 16:41:13 <Blastur> hey NAiL!
Feb 28 16:41:59 <Blastur> thanks for the file yesterday, .. even though, I was unable to get it to function :) It reported a different schema which my monotone did not like.. so i've spent a day migrating the db myself. It actually finished like 1 hour ago 
Feb 28 16:44:09 <NAiL> odd... which version are you running now?
Feb 28 17:06:56 <Blastur> the lastest stuff from Etch, monotone 0.31 (base revision: 1bd1fe1e811dce82bee09b9f0effca3225bd1cee)
Feb 28 17:08:20 <Blastur> also, how much disk space will a full slugosbe build consume? cause my poor p2 450, which im using as a buildserver, only has about 6 gb available
Feb 28 17:13:37 <joshin> Blastur: my sources directory is currently 670MB (could probably be pruned quite a bit) and the actual slugos stuff is at 4.9GB (including all the extra packages I've built)
Feb 28 17:14:52 <Blastur> should be ok then
Feb 28 17:18:26 <Blastur> joshin, i'm planning to build several different images though, like slugosbe and slugosle .. i guess they have a lot in common, will those files overlap, or will I need the double in diskspace?
Feb 28 17:18:46 <Blastur> i mean, it downloads a lot of source, i guess that can be used to compile a toolchain for both 
Feb 28 17:18:54 <joshin> Double the fun, double the disk space
Feb 28 17:18:57 <Blastur> =)
Feb 28 17:19:16 <joshin> At least the source will be shared.  :)
Feb 28 17:20:48 <Blastur> i guess i have to compile it, remove, and re-compile =)
Feb 28 17:22:20 <Blastur> just to be sure i'm not doing a lot of work in vain here, there is no place to download built images for all different targets built from the latest source, right? like, a system which builds images every night from the repository
Feb 28 17:22:47 <Blastur> i'm specifically looking for slugosbe, slugosle 
Feb 28 17:24:39 <joshin> Not that I know of.  At least not yet.
Feb 28 17:25:20 * joshin ponders if he's interested in doing that...
Feb 28 17:26:47 <joshin> I wonder how much net bandwidth that would take...
Feb 28 17:29:40 <Blastur> i think the community would love it,.. there are a lot of people sitting out there, just waiting for stuff on slug-firmware.net to update :) and they don't have the resources/knowledge to build themself
Feb 28 17:30:09 <Blastur> actually, i could supply with a mirror if someone sets up a build-thingie
Feb 28 17:32:06 <NAiL> In that case, you will need a click-through licence
Feb 28 17:32:17 <NAiL> ssince the image contains intel-licenced code
Feb 28 17:32:43 * joshin starts to get a headache
Feb 28 17:32:58 <Blastur> i think most people can live with a click-through licence compared to building an image from scratch
Feb 28 17:33:15 <NAiL> Blastur: btw, seen http://hentges.net/tmp/snapshots/SlugOS/ ?
Feb 28 17:34:03 <NAiL> It only has LE thus far
Feb 28 17:34:10 <NAiL> but it has nightlies
Feb 28 17:34:27 <Blastur> hey, that's exactly what I meant :)
Feb 28 17:35:05 <joshin> I like that solution to the click-through license problem.
Feb 28 17:37:28 <Blastur> who runs that site?
Feb 28 17:38:01 <NAiL> CoreDump
Feb 28 17:41:08 <Blastur> maybe i can convince him to do BE aswell :)
Feb 28 17:43:08 <osas> NAiL: any experience with fetching source code from svn repo via http for oe?
Feb 28 17:43:31 <Blastur> hey, while snooping around at hentges.net, i found this: http://hentges.net/tmp/photos/Akita/Casing/Bild(1).jpg .. anyone know the name of that device? looks sweet!
Feb 28 17:44:05 <Blastur> oh right, it actually says "ZAURUS" with bold letters on the next picture =)
Feb 28 18:01:04 <CIA-6> 03nail * r5660 10optware/trunk/platforms/packages-ts101.mk: add broken packages
Feb 28 18:02:41 <NAiL> osas: no
Feb 28 18:02:54 <osas> ok ...
Feb 28 18:03:35 <osas> I was thinking og getting asterisk 1.4 to work on openslug ... but I got stuck at getting the source :p
Feb 28 19:32:26 <H4rvy> hi any reliable howtos on creating your own jffs2 image out there...?
Feb 28 20:01:38 <CIA-6> 03bzhou * r5661 10optware/trunk/scripts/report-broken.sh: report-broken.sh: still defaults to COMMON_CROSS_PACKAGES, but can use other PKGS_VAR
Feb 28 21:25:26 <Blastur> hey.. is it true that Debian Installer will actually flash the bootloader with APEX during install? is that not _insane_ to do, in case something goes wrong and the user does not have a JTAG cable? Also, does APEX still have the feature of going into "upgrade mode"?
Feb 28 22:42:30 <AdamBaker> Blastur: Debian installs Apex as a secondary bootloader, which is called by the existing redboot.
Feb 28 22:42:53 <Blastur> ah..why?
Feb 28 22:43:20 <Blastur> i mean, why use apex at all?
Feb 28 22:44:33 <NAiL> because redboot has too many limitations
Feb 28 22:44:37 <NAiL> eg. <1mb kernel
Feb 28 22:45:09 <rwhitby> Blastur: debian kernel is larger than 1MB
Feb 28 22:45:27 <rwhitby> that is the only real reason at the moment.
Feb 28 22:45:33 <rwhitby> Blastur: you can use 'INHERIT += "rm_work"' in your local.conf to conserve disk space
Feb 28 22:46:02 <rwhitby> we *never* overwrite the primary bootloader
Feb 28 22:49:17 <Blastur> ah, thats what i thought. Kinda scared me there for a moment, that someone overwritten redboot
Feb 28 22:49:42 <CoreDump|home> hi
Feb 28 22:49:46 <Blastur> hey coredump
Feb 28 22:50:05 <CoreDump|home> heya, I saw you found the LE image ;)
Feb 28 22:50:11 <Blastur> i did :) 
Feb 28 22:50:18 <Blastur> with some help from my friends!
Feb 28 22:50:46 <Blastur> i like the solution, with regularly built images from the repository
Feb 28 22:50:50 <CoreDump|home> ;)
Feb 28 22:51:01 <CoreDump|home> semi regulary actually
Feb 28 22:51:18 <Blastur> well, anything appears regular compared to slug-firmware.net =)
Feb 28 22:51:29 <Blastur> anyway, do you have any plans to extend it to include BE images aswell?
Feb 28 23:00:12 <CoreDump|home> Blastur: I could kick off a BE build, yeah. You'd have to wait for that until tomorrow this time tho
Feb 28 23:00:48 <Blastur> i've started building one myself, been working on it for the past 6 or 7 hours now
Feb 28 23:00:57 <Blastur> but i guess it wont be done until tomorrow
Feb 28 23:00:58 <rwhitby> CoreDump|home: multimachine should work, but not much is shared cause of the endianness.
Feb 28 23:01:28 <NAiL> rwhitby: what exactly is multimachine?
Feb 28 23:01:50 <Blastur> im just saying, pre-built BE and LE (and possibly other) images would be nice :) (from a somewhat updated source) .. built perhaps once a week
Feb 28 23:02:39 <rwhitby> NAiL: bitbake class
Feb 28 23:03:13 <rwhitby> allows you to build multiple MACHINEs in a single tmp dir.
Feb 28 23:03:19 <rwhitby> and shares what can be shared
Feb 28 23:03:29 <NAiL> aha
Feb 28 23:04:45 <CoreDump|home> rwhitby: NAiL it has been my _personal_ experience that multimachine builds can screw up badly from time to time. If you have the HDD space, just compile w/ completely different "tmp" directories for each machine (just my 2 cent)
Feb 28 23:05:12 * CoreDump|home has been doing the latter in the past
Feb 28 23:05:33 <rwhitby> CoreDump|home: yeah, I still keep them separate.  haven't used the multimachine much yet
Feb 28 23:06:10 <CoreDump|home> rwhitby: but we still suffer from the retarded koen deploy patch
Feb 28 23:06:36 <mwester> which is a *real* PITA
Feb 28 23:07:19 <CoreDump|home> mwester: indeed. I intend to atleast fix up meta/package-index to create a working single "Packages" file out of the messed up deploy dir
Feb 28 23:08:18 <mwester> as all my testing is done by adding a feed to my build machine, which as a web server that serves the feeds for my local copies of unslung, optware, slugosle, and slugosbe.  Now I have to cut and paste and use wget to manually fetch the packages.
Feb 28 23:08:53 <CoreDump|home> mwester: yeah. worst .dev change in a _long_ time IMO
Feb 28 23:09:13 <mwester> Well, the most disruptive, anyway.
Feb 28 23:10:01 <CoreDump|home> right
Feb 28 23:10:34 <CoreDump|home> and the complete rejection of even adding a way to revert to the old way
Feb 28 23:13:48 * mwester wonders what happens if he just creates the correct symlinks in the deploy/ipks directory, all pointing to the same real directory...
Feb 28 23:14:23 <Blastur> what is this retarded koen deploy patch? :)
Feb 28 23:14:27 <NAiL> koen submits a patch that breaks symlinks in package dir :-P
Feb 28 23:14:51 <Blastur> who is koen? and does the repository not support rollback?
Feb 28 23:15:00 <CoreDump|home> you no longer can use a compiled OE feed as an actual feed w/o manual fixing
Feb 28 23:25:20 <Blastur> compiled OE feed? do you mean i cannot use the OE MasterMakefile to make an slugosBE image? 
Feb 28 23:26:34 <CoreDump|home> that you can. However, in the past you could point ipkg.conf to the OE-generated deploy dir and use it as a feed for every package compiled w/ OE
Feb 28 23:27:45 <rwhitby> but that didn't work for koen for some reason (whilst it worked for everyone else in the world) and so he decided to break it for everyone else just so it worked for him.
Feb 28 23:30:39 <Blastur> this koen guys seems like a lovely fellah!
Feb 28 23:31:50 <Blastur> guy*
Feb 28 23:35:02 <CoreDump|home> he is...
Feb 28 23:35:36 <mwester> I'm sure he's a decent guy -- some folks here are just peeved about the ramifications of this particular recent change.
Feb 28 23:36:25 <Blastur> does anyone have write-access to this repository?
Feb 28 23:36:26 <CoreDump|home> mwester: his response to my email on the ML showed his usual unfriendly face
Feb 28 23:36:37 <rwhitby> Blastur: we all do
Feb 28 23:37:10 <mwester> Y'know, I complain about it, but I can be easily placated if there was just some easy way to consolidate all the packages once again and ready them for deployment.
Feb 28 23:38:17 <mwester> rwhitby: would it be the wrong solution to add a target to the master makefile to consolidate the packages and prepare the index?
Feb 28 23:38:22 <CoreDump|home> mwester: I didn't look into it yet but I believe package-index could be reworked to do just that
Feb 28 23:38:35 <rwhitby> mwester: better to do it in package-index.bb as CoreDump|home suggests
Feb 28 23:38:39 <mwester> Oops - late to pick up daughter from dance class - bbiab
Feb 28 23:38:56 <rwhitby> if that can't be done, then we would do it in the mmaster makefile.
Feb 28 23:39:47 <CoreDump|home> right
Feb 28 23:49:48 <CoreDump|home> rwhitby: it's not easily fixable due to limitations of ipkg-make-index. One could, however, create a new "combined" directory w/ symlinks from all ARCH'es and generate Packages from it
Feb 28 23:51:27 <rwhitby> tmp/deploy/everything ?
Feb 28 23:52:24 <CoreDump|home> would be misleading as it doesn't contain the images (and hence "everything"). That's what koen would rant anyway
Feb 28 23:53:29 <CoreDump|home> deploy/ipk-feed ?
Mar 01 00:00:49 <rwhitby> sure
Mar 01 00:01:14 <rwhitby> koen will rant that "OE was never, and will never, be a feed" but we can ignore that.
Mar 01 00:01:53 <CoreDump|home> =)
Mar 01 00:04:18 <CoreDump|home> rwhitby: muhaha, so deploy/oe-feed it shall be then
Mar 01 00:04:36 * CoreDump|home is looking forward to the flamefest
Mar 01 00:28:14 <CoreDump|home> omg, the "other" friendly OE guy is back as well
Mar 01 00:46:32 * mwester is looking forward to being able to bitbake and install easily, once again. :)
Mar 01 00:47:48 <CoreDump|home> mwester: I'm almost done
Mar 01 00:48:01 <CoreDump|home> thinking of a matching commit message atm =)
Mar 01 00:49:31 <CoreDump|home> <ljp> qtopia is as open as openmoko is
Mar 01 00:49:33 <CoreDump|home> hehe
Mar 01 01:35:03 <CoreDump|home> mwester: pushed
Mar 01 01:42:18 <rwhitby> CoreDump|home: love the checkin message :-)
Mar 01 01:42:35 <CoreDump|home> rwhitby: heh
Mar 01 01:46:02 <dyoung> hehe
Mar 01 01:49:47 <joshin> Somebody is feeling feisty and it ain't no fawn...
Mar 01 01:53:17 <CoreDump|home> joshin: you don't even want to see my first draft of that message
Mar 01 01:54:09 <joshin> Well I might since I very rarely send even my third draft of something when ticked off.  :)
Mar 01 01:55:01 <CoreDump|home> joshin: http://rafb.net/p/GNilso56.html ;)
Mar 01 01:55:35 <joshin> That's not too bad.  :)  
Mar 01 01:56:00 <CoreDump|home> hehe
Mar 01 01:56:26 * joshin goes to enable it
Mar 01 02:00:34 <joshin> The one OE feature I'd like to see would be to be able to do a "-=" in my local.conf to not build/install packages that I don't use (thinking of szrz and reiserfs stuff that has been in previous slug builds).
Mar 01 02:01:43 <CoreDump|home> joshin: you could always ceate your own "joshin-slugos-image" by inheriting slugos-image and overwriting some package vars
Mar 01 02:02:24 <CoreDump|home> oh joy, bbimage is b0rked
Mar 01 02:02:35 <joshin> That's true.  Of course when I last mentioned it, MickeyL thought it a great idea (but probably a pain in the neck to implement safely).
**** ENDING LOGGING AT Thu Mar 01 02:59:57 2007