**** BEGIN LOGGING AT Thu Feb 15 02:59:57 2007 Feb 15 03:00:05 ls -l *.txt Feb 15 03:00:08 oop. Feb 15 03:00:12 can you recognise the FIS directory and the Trailer (which should be the same between both files) ? Feb 15 03:00:34 rwhitby: altboot could replace /linuxrc as well Feb 15 03:00:36 no, that's the problem. the file are not even close to being the same size Feb 15 03:00:49 CoreDump|home: yes, that's the plan Feb 15 03:00:55 -rw-r--r-- 1 root root 34485 Jan 1 00:37 new.txt Feb 15 03:00:55 -rw-r--r-- 1 root root 1763 Jan 1 00:37 orig.txt Feb 15 03:01:15 VoodooZ: that's expected Feb 15 03:01:33 orig.txt has a whole lot of FFs in the middle, wherease new.txt has the microcode Feb 15 03:01:46 Ah! Feb 15 03:02:14 and the ff don't show up in hexdump? Feb 15 03:02:24 hexdump elides duplicate lines Feb 15 03:03:49 I see. Feb 15 03:03:56 Here's the pastebin: http://www.pastebin.ca/356542 Feb 15 03:05:38 time for bed, n8! Feb 15 03:06:02 night Feb 15 03:06:33 it's going to be my turn soon. But I'd love to understand this before though.. Feb 15 03:06:44 VoodooZ: that looks fine. Feb 15 03:07:02 Is that the f/w starting at 0001c000? Feb 15 03:07:12 yes Feb 15 03:07:13 microcode Feb 15 03:07:25 ok. are those minor diffs at the top normal? Feb 15 03:08:06 that's the new skip regions Feb 15 03:08:35 ok. so does that mean I'm safe to flash it? Feb 15 03:08:35 yes Feb 15 03:09:03 ok, would i do cat FIS_file > /dev/mtdblock5 ? Feb 15 03:10:30 I'm just curious why there's a microcode in the FIS dir partition? Shouldn't that be in a another partition? Feb 15 03:10:46 then again, I'm totally new to FIS so... Feb 15 03:11:45 we put it there so as not to waste space. Feb 15 03:11:54 yes you can cat that to /dev/mtdblock5 Feb 15 03:12:13 do you really want to give up another 128Kb of flash space for the microcode? Feb 15 03:12:27 nope. Good point! Feb 15 03:12:28 (when there's 104Kb spare in the FIS directory block) Feb 15 03:13:12 ok. because of the 128k block size? Feb 15 03:13:25 yes Feb 15 03:13:49 ok. understood. at least I learned something out of all this. Feb 15 03:13:55 here goes.... Feb 15 03:14:25 oops. it says: cat: Write Error: Operation not permitted Feb 15 03:15:00 unless i have to use mtd5? Feb 15 03:15:25 aha - FIS directory is write protected Feb 15 03:15:40 ok, you need to go into Apex and write that file into the FIS directory partition Feb 15 03:15:46 ouch. Feb 15 03:16:02 oh well, it's better than an 8meg file i guess. Feb 15 03:16:30 my apex is old and probably doesn't understand FIS right? Feb 15 03:16:58 I have 1.3.13 Feb 15 03:17:14 which I wanted to upgrade but was too chicken to do. :( Feb 15 03:17:37 ok, all I need then is the starting memory address. Feb 15 03:18:34 I'm off to get some lunch - back in about 15 minutes Feb 15 03:19:34 ok. I might see you tommorow then as it's bed time. Feb 15 03:19:38 Thanks for your patience. Feb 15 03:22:23 If I want to update my apex, would the default apex package do or is it configured as a second bootloader? Feb 15 03:40:57 time for bed. night. Feb 15 03:41:28 rwhitby: I'll be reading the logs again tommorow so let me know if you remember the exact address of the FIS dir partition. Feb 15 03:41:48 meanwhile I'll start looking into updating my apex to latest version with FIS driver. Feb 15 03:41:51 thanks Feb 15 03:41:57 VoodooZ: exact address is in the wiki Feb 15 03:42:22 ok. I'll try to find it. Feb 15 03:43:05 http://www.nslu2-linux.org/wiki/Info/LastBlockMemoryMap Feb 15 03:43:07 is there anything in the apex package config that would prevent me from running it from flash? Feb 15 03:43:10 thanks Feb 15 03:43:29 0x507E0000 Feb 15 03:43:36 some stuff on the wiki is outdated so I'm never sure... Feb 15 03:43:47 VoodooZ: I know nothing about Apex as first stage. You are on your *own* there. Feb 15 03:43:53 no problem. Feb 15 03:44:06 do you know who set it up for second stage though? Feb 15 03:44:43 thanks for the link. it's a good read... Feb 15 03:48:25 I set it up for second stage Feb 15 03:49:06 ok. no worries. that's for another day.. Feb 15 03:49:10 thanks and good night. Feb 15 03:49:17 night Feb 15 10:55:43 rwhitby: do you have any thoughts how $USER should select the partition to be booted by altboot? Feb 15 10:56:26 nm, I'll hack up something Feb 15 11:14:33 CoreDump|afk: just by /dev/sda1 type name, configuring it from the cmdline or a menu input Feb 15 11:14:47 (and it takes effect on the next boot) Feb 15 11:15:30 there is no way for $USER to select the boot partition in real time - it's always the value they selected whilst configuring altboot during the previous session before they rebooted. Feb 15 11:18:44 yep Feb 15 11:18:58 I'll hack a menu Feb 15 11:22:08 note that we make sure we mount the partition by UUID, in case the usb hub reorders them randomly, or someone plugs another disk in ahead of the one your booting from in the USB order. Feb 15 11:22:27 (see the slugos-init scripts for how we do the uuid boot selection. Feb 15 11:23:59 ok Feb 15 11:25:38 the user selects by /dev/sda1 partition name, but the behind-the-scenes code turns this into a UUID and uses that in the boot process Feb 15 13:13:51 who replaced redboot with apex here? Feb 15 13:13:59 ACTION  Feb 15 13:14:55 NAiL: you did too? recently? which version? Feb 15 13:15:27 A long time ago Feb 15 13:15:32 very long time ago Feb 15 13:15:53 I have no idea which version actually Feb 15 13:16:40 ok. I did too way back so I now need a newer version (w/ FIS support) but I'm afraid my old defconfig might not cut it anymore. Feb 15 13:17:05 rwhitby: thanks for making the FIS writeable. I'll give that a try... Feb 15 13:26:03 how can I rebuild slugosbe-image with the latest pulls without deleting tmp. ? Feb 15 14:57:01 What's the alias of the apex dude again? Feb 15 22:20:34 hi Feb 15 22:23:01 hey CoreDump|home Feb 15 22:45:08 rwhitby: good. I rebuilt and flashed the latest slugos and was able to cat FIS to mtdblock5 thanks to your change Feb 15 22:47:42 cool Feb 15 22:55:14 cool! It picked up the firmware too! Feb 15 22:56:05 Ive got a fresh copy of apex ready to flas too which supports FIS. Feb 15 22:56:59 sweet - is the configuration for first stage bootloader any different from the current slugos-nslu2-armeb_config in OE ? Feb 15 23:15:48 hi Feb 15 23:17:02 hi saladino Feb 15 23:17:20 hi rwhitby Feb 15 23:58:18 So is now a good time to test the new changes or should I hold off a few more days? Feb 16 00:01:03 slugos 4.3-beta vs. 3.10-beta What are the major differences? Just kerne;/flash work? Feb 16 00:01:18 s/kerne:/kernel Feb 16 00:32:26 joshin: now's a good time - I have no outstanding changes. Feb 16 00:32:51 kapookee: mainly kernel. Feb 16 00:42:58 rwhitby: So I could just do a 'reflash' instead of starting from scratch. Cool! Feb 16 00:43:26 yes - there is an upgrade procedure on the wiki. Feb 16 00:43:57 Got it - thanks! Feb 16 00:44:52 Ok, upgrading master makefile and then going to test a fresh build Feb 16 02:10:45 when will be slugos 4.3 officially released? Feb 16 02:11:12 * NAiL guesses when it's tested and outstanding issues are fixed. Feb 16 02:11:25 :-) Feb 16 02:11:37 ie, "when it's ready" ;) Feb 16 02:11:43 got it Feb 16 02:12:10 so it is in code freeze Feb 16 02:12:33 not really Feb 16 02:13:29 it's in sort-of-feature-freeze Feb 16 02:13:49 k Feb 16 02:14:14 if I want to test ti I need to build my own image, right? Feb 16 02:15:00 yes Feb 16 02:15:05 building it is half the test :-) Feb 16 02:16:50 are we going to keep the optware feeds in sync with the slugos/be release? Feb 16 02:23:15 hmm - good question. Feb 16 02:23:38 I know :-) Feb 16 02:23:58 cuz right now I'm building my own packages for 3.10 Feb 16 02:24:43 for 3.10 is to late to do something, but for 4.3 we should do ... Feb 16 02:25:29 not really, we just create http://ipkg.nslu2-linux.org/feeds/optware/slugosbe/cross/3.10-beta and compile packages for 3.10 into there. Feb 16 02:25:37 Then do the same for 4.x Feb 16 02:25:53 same as we handle the OE package feeds for slugos Feb 16 02:30:44 right now all the optware packages are compiled against 4.3 Feb 16 02:31:07 if we really want them to be 3.10 we will need to recompile with proper settings Feb 16 02:54:43 osas: right - we can leave the current set as unstable, and kick off a stable 3.10 build **** ENDING LOGGING AT Fri Feb 16 02:59:57 2007