**** BEGIN LOGGING AT Mon Jun 02 02:59:56 2008 Jun 02 05:38:57 03bzhou * r8425 10optware/trunk/make/ruby.mk: ruby: 1.8.6-p114 -> 1.8.7 Jun 02 14:28:30 03oleo * r8426 10optware/trunk/platforms/ (packages-mediagate.mk toolchain-mediagate.mk): optware: update toolchain and packages for mediagate platform Jun 03 00:39:21 g'morning Jun 03 00:41:37 I have no problem building from the mtn/bb/etc. builds. My problem is in how to modify existing code and force a recompile? It's not as simple as "rm *.o" and re-make image. I've been stumped regarding the proper method and the wikis seem wrong or obsolete (http://www.nslu2-linux.org/wiki/OpenSlug/CustomisingTheBuild ) Jun 03 00:45:43 There are no standard ways to do so; everyone has their own technique. The problem fundamentally is that OE is a tool that assembles distributions, and developing code happens long before the distribution gets assembled. Jun 03 00:46:11 The answer is to use whatever works for you, and to understand WHY it works, and when it will fail you. Jun 03 00:47:36 What, specifically, are you trying to do? Modify source code? Add a patch? change a config? Jun 03 00:48:57 Hi, mwester. Thanks for your oversight. Indeed, someone had a suggestion for attempt to fix the OOM kernel bug. You probably know about it, when RAM>64MB Jun 03 00:49:54 Ah, kernel development, then. Jun 03 00:50:02 mwester - I believe I can make my own kernel, but I'd rather do a delta of one of the mainstream distributions to eliminate the differences. I.e., slugosbe without the fix, and slugosbe with the fix. Jun 03 00:50:42 Use the master makefile with the svn repo to build a kernel; no need for OE except as a place to get access to the cross-compiler. Jun 03 00:51:14 That's where all SlugOS kernel work is done and tested, patches are created and committed there, and from there are read in by the OE bulid process Jun 03 00:52:09 I don't know if I am as skilled as the veterans in being able to use slugimage to extract the kernel, ramdisk, etc. and re-insert a custom one. Perhaps I'm making it more difficult than necessary? Jun 03 00:53:07 I was only going to use OE to eliminate any deltas between OE-specific issues and kernel. Jun 03 00:53:10 Yes. I personally use kexec to boot the new kernel from somewhere convenient. One can also just flash the kernel alone IIRC. Jun 03 00:54:25 If you insist on use the OE environment, you need to alter the OE process. An overlay or a modified .bb file can do the job, but is best suited if you are adding patches or changing config options. For code tweaking, you need other techniques. Jun 03 00:54:33 They are ugly, but, something like: Jun 03 00:54:47 Build with OE to get a full build with image. Jun 03 00:54:59 mwester: indeed I think you're right - I've seen that somewhere. I suppose it is possible to re-flash just the kernel, ramfs, and modules, right? Jun 03 00:55:34 In the tmp/stamps directory you will find stamps for each package built, at the "task" granularity -- find the one for the kernel, and delete the "linux-.do_compile" stamp. Jun 03 00:56:14 In the tmp/work directory you'll find the kernel source -- edit to suit. Save your work elsewhere because if you screw up, and the "do_fetch" task runs it will overwrite your work. Jun 03 00:57:06 THen when you build again, bitbake will notice the missing "do_compile" step for the kernel, and begin at the compilation stage, and then do all the dependent tasks (including adding modules to the rootfs, and repackaging the jffs2 and kernel intot he .bin file. Jun 03 00:57:33 A real hassle, which is why the kernel master makefile exists, but it does work. Jun 03 00:58:51 I see, so essentially "tricking" the makefile into re-doing it just for the kernel. I should also remove the .o files right? Jun 03 01:00:47 Hmm, in regards to the kernel master makefile, would that be interchangeable with the kernel made for, say, slugosbe or le?\ Jun 03 01:02:37 The reason I ask is that I don't want to assume that a vanilla kernel of a particular version is identical to one built via the OE process. Sometimes there are tweaks, patches, etc. that are branches from the vanilla tree. Jun 03 01:05:00 03rwhitby * r8427 10optware/trunk/sources/ts209-kernel-modules/ (5 files): QNAP published TS109 and TS209 kernel source Jun 03 01:06:13 03rwhitby * r8428 10optware/trunk/sources/ts409-kernel-modules/ (. kernel-2.6.21.1-ts-409.cfg linux-2.6.21.1.patch): QNAP published TS409 kernel source Jun 03 01:15:07 Thanks for your help mwester. I'll try! Jun 03 01:42:27 RobNC: Was it you that was helping ka6sox-laptop figure out why some ram chips weren't working for fattened slugs? Jun 03 01:43:12 perhaps, if you mean a hardware issue Jun 03 01:44:40 Yup. Jun 03 01:44:58 Were you successful? Jun 03 01:45:26 My development slug was one of those with the problem and I'm hoping for its safe return soon. Jun 03 01:48:06 joshin: I haven't heard anything about it. Jun 03 01:48:19 I don't think I have it if that's what you're asking :-( Jun 03 01:49:18 Ok. I'm not sure anymore. Tomorrow will be 5 months since I lent my slug for use as a demo for SCALE Jun 03 01:49:24 Sigh... Jun 03 01:49:27 Yikes... Jun 03 01:49:39 prolly sitting on someone's desk Jun 03 01:50:42 I have no idea. I just know that I'll never lend any hardware to an OSS project again without a deposit. Jun 03 01:51:26 hmm, probably not the project's fault. sorry to hear that. Jun 03 01:51:55 Nope, not the project as a whole. Thanks for the sympathy. :) Jun 03 01:52:58 So it had some kind of soldering issue or board issue? Jun 03 01:56:13 I don't know. It was a perfectly functioning 32MB RAM slug when I sent it to ka6sox (with a deal being made that he'd upgrade it to 64MB). On the last day of the conference he told me that it developed a hardware problem. 6 weeks or so later he swapped out the PHY and was going to upgrade its RAM. Unforturnately he had some life issues that distracted him from it. The last I heard from him was 2.5 weeks ago saying that "your Jun 03 01:56:20 board is in North Carolina being upgraded" Jun 03 01:57:00 So, since I remembered you upping the RAM in your slug and seeing the "NC" in your nick, figured that you might be the one with my slug. Jun 03 01:58:41 03bzhou * r8429 10optware/trunk/make/py-tailor.mk: py-tailor: 0.9.31 -> 0.9.34 Jun 03 01:58:53 Hmm, I can say that the address I gave ka6sox is correct, and I haven't gotten an email or confirmation regarding such. Indeed, I'm from NC as you can probably figure rDNS. Jun 03 01:59:40 So he never sent you a slug? Jun 03 02:00:28 nope, not unless: 1) it was not sent to my address, 2) it was lost in transit, or 3) it was never sent Jun 03 02:01:19 Ok, thanks for the datapoint. Jun 03 02:02:37 It's not too hard to add an additional 32MB. I think I asked him if he can remove the battery, buzzer, and caps for easier access to memory. But for me to do that is approx 5 minutes max. Jun 03 02:04:22 It isn't hard if you have experience with SMD soldering or practice with those tiny pins. I can handle thru-hole soldering just fine but all those tiny pins so close together is terribly intimidating. :) Jun 03 02:04:43 yeah I wouldn't even do it w/o a microscope and SMT tools Jun 03 02:05:10 03bzhou * r8430 10optware/trunk/ (make/icecast.mk sources/icecast/src-auth_url.c.patch): icecast: 2.3.1 -> 2.3.2 Jun 03 02:07:33 Both of which are on my "Yay I just won the lottery" toy list. :) Jun 03 02:07:36 I'd guess it probably takes 1-2 hours, depending on if I get interrupted. :-) Jun 03 02:08:01 heh yeah along with a room you can exhaust the fumes! Jun 03 02:08:34 I have that already. My den/hamshack/project room has good ventilation Jun 03 02:08:46 If you need to get hold of me, I think you can find my email in the nslu2-linux group posts. Jun 03 02:08:57 Ok, thanks. Jun 03 02:10:14 no problem, let me know if you don't hear from ka6sox - you've emailed him? Jun 03 02:11:27 per my records I emailed him my work address May 4th. Jun 03 02:11:32 Yup. I might have to start daily calls to his cell phone. Then hourly ones... :) Jun 03 02:12:10 heh hope it doesn't come to that... Jun 03 02:12:55 Me too. My wife is rather amazed at my patience. Jun 03 02:13:10 I fear she will use it against me soon. :D Jun 03 02:13:26 heh talk about lose/lose scenario Jun 03 02:14:24 Scary Jun 03 02:14:53 yep, I hear ya man... Jun 03 02:15:28 If you want I can email him and ask if he's sent it out Jun 03 02:15:43 Thanks, I'd appreciate it. Jun 03 02:16:33 He may be trying to have a bunch done; he asked me for a total of about 10 I think. I'll have to do it in my spare time of course but I can't do them if I don't have them :-) Jun 03 02:17:34 Odds are that mine is in that group. Jun 03 02:18:05 could it be some other hardware problem? Jun 03 02:18:25 Not that he's told me. Jun 03 02:18:49 No, I think he just told me something to get me off his case for a while and that he hasn't followed up on what he was supposed to do. Jun 03 02:18:55 * joshin is being charitable Jun 03 02:19:16 (Only because he hasn't talked to rwhitby yet) Jun 03 02:20:07 that's good then... Jun 03 02:20:43 I mean wouldn't it be an awkward situation - give someone a bad board and it becomes worse Jun 03 02:22:03 Last I heard, it worked. I'm just ticked (*charitable*) about the poor communication. Jun 03 02:23:06 understandable, I mean 1 month is more than enough time you'd think Jun 03 02:23:37 Yup. Well, thanks for your help. Don't want to keep you up too late. Jun 03 02:23:44 * joshin <- Phoenix AZ Jun 03 02:26:53 oh yeah true I'm EST guy. If I get it and have it and the delay is in my court I'll tell you. Heck, if I know which one it is I can have it sent back to you directly if you want. Jun 03 02:27:29 Thanks. Then I can get back to my Gentoo Slug hacking. Jun 03 02:28:10 * RobNC has to reinstall OS on laptop - yuck - since SP3 messed up something with registry or MBR - either way not recoverable. Thank goodness for backups but yuck I didn't have Ghost installed. Jun 03 02:28:12 And yes, I use distcc to get my bigger machines do the compiling Jun 03 02:28:55 Ugh. I have a virtual machine with Windows Home server for backups/restores of my wife and kid's Windows machines. Jun 03 02:29:07 It isn't bad for that. Jun 03 02:29:39 Great! I was just talking with mwester about that - compiling - need to try if the suggested fix works for >64MB detected via APEX/kernel. Jun 03 02:33:09 ok, good luck joshin and keep in touch if I have your board. Jun 03 02:33:31 * RobNC waves g'nite **** ENDING LOGGING AT Tue Jun 03 02:59:57 2008