**** BEGIN LOGGING AT Fri Apr 01 00:46:28 2005 Apr 01 05:08:08 03rwhitby * 10unslung/Makefile: Added readline to wl500g packages. Apr 01 05:08:53 last chance to get the 4.8-alpha binary from nslu.sf.net/downloads before I remove it .... Apr 01 05:09:42 stay Apr 01 05:12:06 go ;-) Apr 01 05:13:56 make sure you add yourself to the database. Please don't discuss the alpha binary on the list - it is an IRC treat only. Apr 01 05:14:01 how do i trigger an updated package to be uploaded? Apr 01 05:14:16 send a /msg to lp30 Apr 01 05:14:17 k Apr 01 05:14:20 jp30 Apr 01 05:23:30 03rwhitby * 10unslung/Makefile: Added expat and libjpeg to wl500g packages. Apr 01 05:26:00 03rwhitby * 10unslung/make/libjpeg.mk: Updated for control file generation. Apr 01 05:27:29 03rwhitby * 10unslung/make/expat.mk: Updated for control file generation. Apr 01 05:31:02 03rwhitby * 10unslung/sources/ (expat/control libjpeg/control): Removed generated control files Apr 01 06:38:25 03jeanfabrice * 10unslung/sources/nylon/nylon.patch: Apr 01 06:49:09 03jeanfabrice * 10unslung/sources/nylon/nylon.patch: suppress configure patch, change conf file location Apr 01 06:50:33 03jeanfabrice * 10unslung/make/nylon.mk: suppress configure patch, change conf file location, update control generation var Apr 01 06:52:51 03jeanfabrice * 10unslung/make/nylon.mk: Apr 01 06:58:25 03jp30 * 10unslung/Makefile: promote minicom, sqlite, nylon Apr 01 07:05:28 Should I update top Makefile when updating modules to control generation ? Apr 01 07:07:18 03jeanfabrice * 10unslung/make/zlib.mk: Update to control generation Apr 01 07:10:41 03jeanfabrice * 10unslung/sources/zlib/control: Update to control generation Apr 01 07:15:00 03jeanfabrice * 10unslung/sources/nylon/nylon.conf-dist: Apr 01 07:18:32 jeanfabrice-away: yes, please update the top-level wl500g_packages variable when you update packages. Apr 01 07:20:25 for zlib, it was already there using the sed method. I see you've updated it to the generation method. Excellent - thx. Apr 01 07:20:58 BTW, if you change anything in the package, remember to increment the IPK_VERSION so that it get's rebuilt and people get the new version when they type "ipk upgrade" Apr 01 07:21:27 03rwhitby * 10unslung/make/nylon.mk: Bumped the IPK version. Apr 01 07:22:15 rod: ok Apr 01 07:22:48 jeanfabrice: for zlib.mk, you forgot to include the parts which actually make the control file. Apr 01 07:22:57 oups... Apr 01 07:23:02 let me correct it Apr 01 07:23:39 The section which says "This rule creates a control file ..." and then replace the sed with a call to that target. Apr 01 07:24:21 There are three places in the .mk file which need to be changed to convert to control file generation. Only then can you remove the control file from the repository. Apr 01 07:28:19 BTW, you probably don't need the nylon.patch, as it should be handled by passing --prefix=/opt to the configure script Apr 01 07:29:34 03jeanfabrice * 10unslung/make/zlib.mk: Apr 01 07:30:13 yep yep... all that is not very easy at beginning ;) but very interesting ! Apr 01 07:31:01 we all learn as we go .... Apr 01 07:31:35 I've confirmed that you can remove nylon.patch from the .mk file and the sources dir Apr 01 07:31:53 ok, will check it Apr 01 07:33:36 I think you also forgot to check in nylon.conf in the sources/nylon dir Apr 01 07:34:19 "cvs update" will tell you if you have any modified or added files which you have not checked in yet. Apr 01 07:34:32 Humm this is strange . I though it was done Apr 01 07:34:40 it is good to have a clean output from cvs update before you are finished on a package Apr 01 07:35:20 did you "cvs add" the new file before "cvs commit" ? Apr 01 07:36:53 03jeanfabrice * 10unslung/sources/nylon/ (nylon.conf nylon.patch): Apr 01 07:37:24 03jeanfabrice * 10unslung/make/nylon.mk: Apr 01 07:38:50 I'm using a windows cvs client as I would like to quickly test how difficult cvs managment is without having also the difficulty to learn command line Apr 01 07:39:31 Maybe it's not the better client. Apr 01 07:39:51 You use command-line cvs or win32 client ? Apr 01 07:40:12 linux command line in CoLinux on a windows laptop Apr 01 07:40:24 feed is now updated with new nylon Apr 01 07:40:46 is everything I broke repaired now ? ;) Apr 01 07:40:56 fell tired... 1:45am there Apr 01 07:41:01 you can try "ipkg update" and "ipkg upgrade" to see if it installs the new version automatically Apr 01 07:41:26 have to had the feed to my ipkg conf Apr 01 07:41:38 03rwhitby * 10unslung/make/zlib.mk: Bumped the IPK version. Apr 01 07:42:44 03rwhitby * 10unslung/make/zlib.mk: Updated the ipk target to remove old versions (as per template). Apr 01 07:43:26 the second wasn't your fault - I just need to do that on really old packages that don't have that line. Apr 01 07:45:01 back later - saturday morning kid's sport ... Apr 01 07:45:49 rwhitby-away, you rang? Apr 01 08:33:21 ~spell accumilated Apr 01 08:33:23 possible spellings for accumilated: accumulated accumulates accumulate cumulated acclimated Apr 01 10:22:43 ka6sox-office: no ping Apr 01 10:30:27 ~spell accountant Apr 01 10:30:29 'accountant' may be spelled correctly Apr 01 10:30:40 "may" ? Apr 01 11:04:12 ~spell colour Apr 01 11:04:16 possible spellings for colour: color co lour co-lour col our col-our Colo cooler coolie collar cool Cloe Cole cloy clue Collie Collier clout collie collier colors COL Clo Col col Cooley Clair Colly coaler lour Apr 01 11:04:48 ~spell antidisestablishmentarianism Apr 01 11:04:50 'antidisestablishmentarianism' may be spelled correctly Apr 01 11:05:03 ~botsnack Apr 01 11:05:04 rwhitby-away: thanks Apr 01 11:05:44 rwhitby-away: LOL that's my favorite word to test spell checkers too Apr 01 11:05:55 it didn't used to be able to do it Apr 01 11:06:19 too bad silly bot doesn't know about UK spellings **** ENDING LOGGING AT Fri Apr 01 13:09:27 2005 **** BEGIN LOGGING AT Fri Apr 01 13:12:09 2005 **** ENDING LOGGING AT Fri Apr 01 13:19:30 2005 **** BEGIN LOGGING AT Fri Apr 01 13:22:04 2005 Apr 01 13:35:10 03bzhou * 10unslung/ (Makefile make/abook.mk): abook ready for cross testing Apr 01 13:47:20 glc, dyoung: tried unslung 4.8-alpha? Apr 01 13:47:39 Not yet. But I built it. ;-) Apr 01 13:47:51 you should be able to copy rootfs to an external disk and preserve the packages and ipk database on that disk now Apr 01 13:48:22 Cool, maybe I'll go straight for ProdSlug2 Apr 01 13:52:09 Last time I tried to bk pull I was asked for a password. Apr 01 13:52:29 Permission denied, please try again. Apr 01 13:52:29 nslu2-linux@nslu2-linux.bkbits.net's password: Apr 01 13:52:50 your key is in there Apr 01 13:53:01 That was several weeks ago, and since I was playing with openslug, I just gave up. Apr 01 13:53:22 Your key on bkbits starts with this: 1024 35 13671345169883290846.......... Apr 01 13:53:33 rsa1 Apr 01 13:56:22 ok, what other devices do we need in /dev for unslung 4.x ? Apr 01 13:59:43 what devices go with CONFIG_USB_PRINTER and CONFIG_USB_SCANNER and CONFIG_USB_OV511 ? Apr 01 14:04:30 any1 noticed http://www.scratchbox.org/ ? Apr 01 14:04:47 dyoung: will 4 webcam devices be enough for you? Apr 01 14:05:06 eno: yep Apr 01 14:05:48 seems to solve a lot of the porting problems Apr 01 14:06:19 have you verified it supports armeb? Apr 01 14:06:36 no, just came across the site Apr 01 14:06:58 last time I looked (which was 0.9.5 or earlier I think), it didn't. Apr 01 14:07:36 i c Apr 01 14:07:54 but it's worth checking again Apr 01 14:21:09 dyoung: I also added /dev/md[0-3] for raid modules. Apr 01 14:25:38 rwhitby-away: ping Apr 01 14:26:17 pong Apr 01 14:26:46 what changes are needed for README on Unslung4.x? Apr 01 14:28:06 It needs to be changed such that the default is that the rootfs is loaded from the external disk, not the jffs2. And a description of the unsling arguments is needed. Apr 01 14:29:36 okay... Apr 01 14:29:52 let me get with BryonT when he gets back Apr 01 14:29:57 and I'll update it Apr 01 14:30:06 (as in next time i see him) Apr 01 14:30:11 we have been keeping in touch Apr 01 14:33:13 we also need to mention the kernel modules Apr 01 14:33:22 are we merging Unslung-Able with Unslung-Standard? Apr 01 14:33:22 and should we fix the Wiki? Apr 01 14:33:50 yes, no more -standard or -able Apr 01 14:34:06 only as "history" Apr 01 14:34:50 yep Apr 01 14:36:00 Hi ruDelph! What firmware are you running? Apr 01 14:36:16 4 webcams and 4 md's shouyld be plenty. Apr 01 14:36:24 Should be put a sr[n] in there too? Apr 01 14:36:36 what's /dev/sr? Apr 01 14:36:46 cdrom Apr 01 14:37:00 or maybe we dont need it, as thats the scsi-ide device name Apr 01 14:37:11 is there a cdrom howto? Apr 01 14:37:18 Hi, rwhitby. I haven't nslu yet :( Now i only thinking about it :) Apr 01 14:37:18 (I got all the others from the howtos) Apr 01 14:37:44 dyoung: I'm also adding the 32K NFS blocksize patch too ... Apr 01 14:38:20 I think there was something on the yahoo group, but no wiki entry as far as I know. Apr 01 14:39:07 http://groups.yahoo.com/group/nslu2-linux/message/4954 Apr 01 14:39:56 so that suggests the use of the sr device. Apr 01 14:39:58 So /dev/scd[0-4] Apr 01 14:40:06 http://groups.yahoo.com/group/nslu2-linux/message/4955 Apr 01 14:40:55 hmm, same same I guess. I might be using old names. either way sr and scd appear to be 11,n Apr 01 14:41:16 okay cool. Apr 01 14:41:18 I put in scd, cause that's what Inge said :-) Apr 01 14:41:46 my desktop distro uses the sr name. Apr 01 14:41:48 scd is what I use Apr 01 14:42:57 Under debian, looks like sr0 is a symlink to scd0 Apr 01 14:43:06 Also put the tmp-permissions.path in the .bb file - don't know how that got removed. Maybe I never added it to the .bb before .... Apr 01 14:43:14 ah...I just never used it as sr0 Apr 01 14:43:49 well, when someone finds a packages that requires the sr0 name we'll fix it. Apr 01 14:47:01 03rwhitby * 10unslung/sources/svn/control: Added openssl and zlib dependencies. Apr 01 14:47:37 ooh...good Subversion Apr 01 14:47:38 03rwhitby * 10unslung/make/svn.mk: Bumped the ipk version. Apr 01 15:02:50 okay...there don't seem to be any slugbugs related to Unslung-firmware in the significant or critical section Apr 01 15:05:42 03rwhitby 07 * r1.3120.1.1 10openembedded/ (5 files in 5 dirs): Unslung 4.9-alpha - various bugs fixed, and devices added. This is the one before the release candidate, so please test it. Apr 01 15:06:19 Let's shoot for a 4.10-beta ... Apr 01 15:08:28 If anyone else has anything else which they want added to 4.x, then now is the time to speak up ... Apr 01 15:08:50 Cause we are now officially in feature freeze as far as I am concerned. Apr 01 15:09:42 Release Manager has Spook Apr 01 15:31:16 03rwhitby 07 * r1.3131 10openembedded/packages/nslu2-binary-only/unslung-rootfs_2.3r25.bb: Bumped the PR. Apr 01 15:31:37 03rwhitby 07 * r1.3130 10openembedded/packages/nslu2-binary-only/unslung-rootfs_2.3r25.bb: Fixed the name of the Unslung tmp-permissions patch. Apr 01 15:31:48 that should build now :-) Apr 01 15:50:26 unslung-4.9-alpha.bin is now on nslu.sf.net/downloads Apr 01 15:51:07 it's the one before the release candidate (which will be 4.10-beta if no problems are found) Apr 01 15:52:39 Mine built, but I'll try the download Apr 01 15:55:30 might as well try the built one. the download to test will be the next one Apr 01 15:55:52 (and it will be packaged with the updated README) Apr 01 15:57:23 ka6sox: is the latest README update on the wiki page? Apr 01 16:23:29 good morning Apr 01 16:37:24 g'day Apr 01 18:02:35 Hi guys, I just flashed my nslu2 with a fresh build of openslug I just created. I noticed that the Ready/status link stays amber, anyone know what could be wrong please? Of course the device isnt reachable from the netowrk. Thanx in advance. Apr 01 18:03:52 Nothing. Apr 01 18:04:01 oh wait Apr 01 18:04:04 sorry, misread tat. Apr 01 18:04:50 :) Apr 01 18:05:20 amber is its still in redboot i think. Apr 01 18:05:26 nettie_: have you ever successfully flashed an openslug you have built yourself? Apr 01 18:05:55 rwhitby that's my first build but I'm pretty used I have a few wrt's too Apr 01 18:06:25 I thought the nick was familiar Apr 01 18:06:32 when did you build it? Apr 01 18:06:55 dyoung even if it's still in redboot it's not answering to the redboot default ip Apr 01 18:06:59 last night Apr 01 18:07:15 like 8 hrs ago Apr 01 18:07:50 dyoung: didn't we document those led sequences somewhere? Apr 01 18:08:20 Probably, but i've forgotten. Apr 01 18:08:29 I dont suppose you have serial.... Apr 01 18:08:51 correct I dont ehehhango Apr 01 18:08:53 hangon Apr 01 18:08:55 think I got it Apr 01 18:09:09 http://www.nslu2-linux.org/wiki/HowTo/UseTheResetButtonToEnterUpgradeMode Apr 01 18:09:31 naja Apr 01 18:10:10 can you telnet into redboot? Apr 01 18:10:22 I think I can surely do the arp trick Apr 01 18:10:26 lemme try how Apr 01 18:11:17 im in Apr 01 18:12:12 maybe I configure redboot networking and try to flash again? Apr 01 18:12:46 rwhitby, did telnet into redboot let you see some of the boot sequence? Apr 01 18:13:18 uhmm I think I can exec an image from here Apr 01 18:13:35 dyoung: I have never telnetted into redboot personally Apr 01 18:13:41 eheh Apr 01 18:13:54 nettie_: you've got a redboot prompt? Apr 01 18:13:58 sure Apr 01 18:13:58 I think I did it only once to check it out. Apr 01 18:14:10 do you have a tftp or http server on your lan? Apr 01 18:14:14 sure Apr 01 18:14:30 http ready with openslug image Apr 01 18:14:35 httpd Apr 01 18:14:40 http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash Apr 01 18:15:35 I use that method exclusively for all my flashing (via serial access to redboot) Apr 01 18:16:03 make sure you count the zeros twice .... Apr 01 18:16:22 ok Apr 01 18:16:28 thanx im gonna try rigthaway Apr 01 18:19:04 I'm using that same procedure right now to test the latest unslung alpha. Apr 01 18:19:33 If you're going to be building your own openslug images, I can recommend adding a serial port. Apr 01 18:19:36 yeah the RAM loader is pretty neat Apr 01 18:20:07 yeah it's something I have in mind, I?m waiting to get the max232's from my local store here Apr 01 18:20:18 maybe today is the good day ;) Apr 01 18:20:32 you're getting the 3.3v version, right? Apr 01 18:20:38 yup Apr 01 18:20:48 yeah, 3232 will yield better results. Apr 01 18:21:08 (unless you have some extra LVC244's lying around Apr 01 18:21:09 * dyoung hides Apr 01 18:21:15 ~ubessa Apr 01 18:21:16 ubessa is, like, a Unorthrodox But Effective Super Serial Adapter. It refers to a UBE board using a MAX232 coupled to a 74LVC244 because somebody was too lazy to get a MAX3232. Apr 01 18:21:27 I know there's a DS which is cool too I think it's uhmm DS275 or something like that but I cant find it here handy Apr 01 18:21:46 eeheh Apr 01 18:21:57 http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash Apr 01 18:23:03 oops, meant to paste http://nslu2-linux.thestuffguy.com/gallery/UBESSA Apr 01 18:23:31 ok, now I get a bounce of ---------------------- Apr 01 18:24:07 yep, you get lots of those Apr 01 18:24:17 as the file is loading Apr 01 18:24:29 tons like a few lines right? Apr 01 18:24:35 like 8/10 lines Apr 01 18:24:44 yep, maybe even 15 Apr 01 18:24:48 uhmm Apr 01 18:24:57 yeah depends on term setting eeh Apr 01 18:25:00 anyway Apr 01 18:25:06 36 for me :-) Apr 01 18:25:36 ok lets scan the subnet for a reacahble bo Apr 01 18:25:38 box Apr 01 18:26:05 naja Apr 01 18:26:21 and the led is still amber :( Apr 01 18:26:33 I think I'll just try with a prebuilt image Apr 01 18:26:51 to see if I built from borked sources then Apr 01 18:30:31 guys how big are your openslug images? Apr 01 18:34:57 -rw-r--r-- 1 oho root 8388608 2005-03-30 18:46 openslug-nslu2-20050330144341.flashdisk.img Apr 01 18:36:12 8388608 Apr 2 03:18 openslug-nslu2-20050401231448.flashdisk.img Apr 01 18:36:15 same here Apr 01 18:36:30 exactly the same Apr 01 18:36:46 odoc you rember the default ip address? Apr 01 18:37:28 maybe I have collisiosn Apr 01 18:38:47 mhh Apr 01 18:38:53 hard to remember ... Apr 01 18:38:56 192.168.1.77 Apr 01 18:39:02 thanx Apr 01 18:41:20 dyoung how long does it takes to boot? Apr 01 18:42:01 it takes a bit on the first boot. Apr 01 18:42:12 did you read the turnup page yet Apr 01 18:42:13 ? Apr 01 18:42:25 turnup ? Apr 01 18:42:28 nope Apr 01 18:42:39 things get kind of confused if you dont have some things pre-setup Apr 01 18:42:48 ~nslu2-turnip Apr 01 18:43:00 ~nslu2-vegetable Apr 01 18:43:11 what the hell was it Apr 01 18:43:17 ~openslug-vegetable Apr 01 18:43:22 ~nslu-turnup Apr 01 18:43:25 ~nslu2-turnup Apr 01 18:43:46 ~lart jbot Apr 01 18:43:47 * jbot urinates on jbot Apr 01 18:45:41 http://www.nslu2-linux.org/wiki/OpenSlug/OpenSlugTurnUp Apr 01 18:46:01 ~openslug-veggie Apr 01 18:46:03 http://www.nslu2-linux.org/wiki/OpenSlug/OpenSlugTurnUp Apr 01 18:46:06 aha that was it Apr 01 18:46:09 thx Apr 01 18:46:41 You might want to read this too: http://nslu2-linux.thestuffguy.com/gallery/UBESSA Apr 01 18:46:42 does it beep at all? Apr 01 18:47:00 dang, can't paste anything right tonight: http://www.nslu2-linux.org/wiki/OpenSlug/BetaRelease Apr 01 18:47:01 rwhitby, having some paste issues this evening are we? Apr 01 18:47:11 indeed! Apr 01 18:47:37 let's hope it wasn't happening when I was putting together the Unslung build .... Apr 01 18:49:45 unslung-4.9 booted btw. Apr 01 18:49:53 I unslunged to hdd-data. Apr 01 18:50:05 but then i got distracted, so dunno if that worked right or not yet. Apr 01 18:50:35 I just had an error running unsling Apr 01 18:51:33 The first beta release of OpenSlug designed to be run from an external hard driver or flash stick. Apr 01 18:51:38 is this still actual? Apr 01 18:52:20 yes, but that's only intended for newbies to read. You can run from jffs2 if you want Apr 01 18:52:39 yeah Apr 01 18:52:40 eheh Apr 01 18:52:54 the intention is that newbies run rootfs from an external disk so that when they stuff something up they can just unplug the disk to recover. Apr 01 18:53:10 yeah I get this .. good planm Apr 01 18:53:12 plan Apr 01 18:53:40 did you guy have found the led sequence doc please? Apr 01 18:53:46 nope Apr 01 18:54:10 I did unsling hdd-data and claimed to work, but it doesnt do it on reboot. Apr 01 18:54:14 after a normal openslug boot the ready/status shoul dbe green right? Apr 01 18:54:21 this is on prodslug2, so no serial Apr 01 18:54:39 I dunno, lemme reboot my openslug slug and I'll let you know. Apr 01 18:54:41 just moment. Apr 01 18:54:46 dyoung: something is wrong with ipkg - looks like upstream has changed or something Apr 01 18:55:05 mine iss green Apr 01 18:55:45 I'm pulling the alpha binary. Something is weird. Apr 01 18:55:54 and red during boot Apr 01 18:56:26 does it beep? Apr 01 18:57:21 uhmm Apr 01 18:57:24 no Apr 01 18:57:31 it desnt beep Apr 01 18:57:48 with the standard firmware it beeps when it finish Apr 01 18:57:54 the boot procedure Apr 01 18:58:01 oaky the boot sq is yellow redboot, beep, red, theh green when up Apr 01 18:58:04 openslug is differnt Apr 01 18:58:20 it beeps when the n2io driver loads, which is early in kernel load. Apr 01 18:58:29 rwhitby, I dotn even have ipkg Apr 01 18:58:33 I have a ipkg-cl Apr 01 18:58:34 only Apr 01 19:00:06 yeah, something is going wrong in do_rootfs Apr 01 19:04:09 the postinst stuff is not being run in the rootfs for some reason Apr 01 19:06:22 that's what's supposed to do the alternatives stuff, and usually it creates stuff in /usr/lib/ipkg, and unsling is relying on that, and that's causing the error in unsling Apr 01 19:10:14 This looks suss: Apr 01 19:10:17 Updated list of available packages in /home/unslung/tmp/rootfs//home/unslung/tmp/staging/i686-linux/lib/ipkg/lists/oe Apr 01 19:10:58 yep, bug in ipkg Apr 01 19:11:17 putting the info in the wrong place when given an offline root Apr 01 19:13:15 Ugh. Apr 01 19:13:32 paths.patch has disappeared between 0.99.144 and 0.99.147 Apr 01 19:13:39 (that's where I fixed this last time) Apr 01 19:23:43 yep, building ipkg-native: -DLIBDIR=\"/home/unslung/tmp/staging/i686-linux/lib\" Apr 01 19:23:48 should be /usr/lib Apr 01 19:23:59 noway.. Apr 01 19:24:07 I also tried loading the standard firmware Apr 01 19:24:10 linksys one Apr 01 19:24:17 doesnt work :( Apr 01 19:24:33 you still get a redboot prompt, right? Apr 01 19:25:02 sure Apr 01 19:28:33 ok, I've got pb_ on the case of the ipkg bug in #oe Apr 01 19:29:07 Cool. Apr 01 19:32:50 diagnosed and he agrees. working on the fix Apr 01 19:43:41 we could force it to use 144 for our beta release. Apr 01 19:48:25 think I got it Apr 01 19:48:34 Raw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000 Apr 01 19:48:35 :) Apr 01 19:48:45 the laoding via http wasnt relaible Apr 01 19:48:53 or had some kind of problem Apr 01 20:06:43 noway Apr 01 20:06:50 loads it, saves it to flash but doesnt boot it Apr 01 20:06:52 unbealivalbe Apr 01 20:06:52 eheh Apr 01 20:08:35 did you do a cksum to make sure the transfer was clean? Apr 01 20:14:56 sure Apr 01 20:14:58 it's perfect Apr 01 20:15:06 did on both unix box and nslu Apr 01 20:15:12 it's the same Apr 01 20:15:22 now it's loaded in ram Apr 01 20:16:41 what upgrade mode handleS? Apr 01 20:37:27 pardon? Apr 01 20:38:17 nettie_: http://www.nslu2-linux.org/wiki/HowTo/InstallUnslungFirmware Apr 01 20:38:31 points 2 and 3 are for upgrade mode Apr 01 20:40:24 is that the same for openslug? Apr 01 20:40:37 yep, you're talking to redboot in all cases Apr 01 20:41:23 the point is that wont solve my problem Apr 01 20:41:28 I mean it doesnt boot from ram Apr 01 20:41:37 that's strange too Apr 01 20:41:48 so you load the firmware Apr 01 20:42:02 nettie_: what's in the flash at the moment? stock or openslug? Apr 01 20:42:07 with load -v -r -b 0x01000000 openslug.bin Apr 01 20:42:17 then you type go 0x0100000 Apr 01 20:42:20 uhmm Apr 01 20:42:39 I dont remember Apr 01 20:42:42 I have t ocheck Apr 01 20:42:59 nettie_: that won't work Apr 01 20:43:12 how you start from ram then? Apr 01 20:43:41 nettie_: it's at this point that I ask you to read the HowTo page on the wiki Apr 01 20:43:45 <[g2]> nettie_, check the wiki Apr 01 20:44:01 http://www.nslu2-linux.org/wiki/HowTo/TestAnImageInRamUsingRedBoot Apr 01 20:44:25 ahhh Apr 01 20:44:26 damn Apr 01 20:44:30 I was desperately looking for that Apr 01 20:44:32 thanx Apr 01 20:45:04 <[g2]> nettie_, there's a "Search" option on the wiki that is very helpful Apr 01 20:46:17 thanx ;) Apr 01 20:46:37 the point is that I entered the openslug aread Apr 01 20:46:39 and I got lost there Apr 01 20:46:48 I didnt check the bottom left frame Apr 01 20:46:51 than Apr 01 20:46:52 thanx Apr 01 20:54:16 <[g2]> rwhitby, I've been looking at the oe-devel repo, OpenSlug is broke due to some files not be copied like the init symlink Apr 01 20:54:39 <[g2]> any idea if that's related/unrelated to the ipk changes ? Apr 01 20:55:06 if it's something which is done as an ipkg postinst, then it won't happen at the moment. Apr 01 20:55:49 <[g2]> postinst broke with the latest changes ? Apr 01 20:55:57 postinst at rootfs time Apr 01 20:56:05 or on first boot time Apr 01 20:56:22 postinst on packages installed after first boot is fine Apr 01 20:57:03 <[g2]> well the image is borked, so it's during the creation of the rootfs Apr 01 20:57:31 yep Apr 01 20:57:38 <[g2]> doh! Apr 01 20:58:11 fixing it for both unslung and openslug now ... Apr 01 20:58:23 <[g2]> revering to 144 ? Apr 01 20:58:27 <[g2]> reverting Apr 01 20:58:43 <[g2]> or hammering the path ? Apr 01 20:59:26 reverting to 144 while pb_ implements the solution I proposed (i couldn't get the .bb quoting to play ball) Apr 01 21:06:28 <[g2]> rwhitby, thx Apr 01 21:07:04 flashing it now .... Apr 01 21:08:26 03rwhitby 07 * r1.3131.1.1 10openembedded/conf/distro/ (openslug.conf unslung.conf): Reverted ipkg back to 0.9.144 for both Unslung and OpenSlug. Apr 01 21:12:40 that one works now Apr 01 21:29:37 ok, the unslung-4.9-alpha.bin file on nslu.sf.net/downloads has been updated Apr 01 21:30:07 9f1b34ff349baaf4da4eb7d78dde2800 unslung-4.9-alpha.bin Apr 01 21:35:12 uhmmm Apr 01 21:35:26 I was able to flash the original linsys image Apr 01 21:35:54 now works again but when I try to boot ramdisk and kernel directly from ram it doesnt work Apr 01 21:36:06 nettie_: ipkg-native has been broken for the last couple of days, and that has broken unslung and openslug images built in that time Apr 01 21:36:12 I followed carefully the wikithis time :) Apr 01 21:36:20 if you pull from nslu2-linux now, you will get a good openslug build Apr 01 21:36:21 ah Apr 01 21:36:33 this definitely makes sense ok Apr 01 21:36:34 ok Apr 01 21:36:37 I'll rebuild Apr 01 21:36:43 thanx Apr 01 21:39:58 you should see ipkg revert to 0.99.144 and the rootfs should be rebuilt Apr 01 21:41:39 I'm pretty nre to oe, I'm following the how-tos but I realize this is gonna take 4ever eheh I just updated the source tree and blasted build/tmp ;) Apr 01 21:42:08 you didn't need to blow away tmp Apr 01 21:42:48 we try and be careful with PRs in nslu2-linux, to make things rebuild properly without having to rebuild from scratch Apr 01 21:43:46 I'll read oe docs then in the mentime it's already rebuild, I have a fast machine and the "baking" was cached before so.. Apr 01 21:44:08 I'm sure that when I finish reading oe docs it will be done eheh Apr 01 21:44:51 oe seems very complex compared to other build systems Apr 01 22:05:46 <[g2]> rwhitby, openslug is still broke :( Apr 01 22:06:28 did it build 0.99.144 ? Apr 01 22:06:34 <[g2]> nod. Apr 01 22:06:42 <[g2]> I did an -c clean ipk Apr 01 22:06:58 * rwhitby shrugs Apr 01 22:07:16 what's broke? Apr 01 22:07:41 <[g2]> same thing Apr 01 22:07:44 <[g2]> Preferred root device is jffs2 Apr 01 22:07:44 <[g2]> Cant find valid rootfs on jffs2, using recovery ... Apr 01 22:07:44 <[g2]> Root filesystem cannot be found - dropping into shell ... Apr 01 22:07:54 <[g2]> at least the init symlink is missing Apr 01 22:10:05 <[g2]> and then some other stuff Apr 01 22:10:17 <[g2]> I don't know if it was the device-table changes or something else Apr 01 22:10:38