irclog2html for #nslu2-linux on 20040925

00:01.41ka6soxrwhitby-away: I'm noticing a lot of times I have to reload a page several times before it will display. getting a lot of 404 errors.
00:01.56ka6soxdifferent machines: different browsers.
00:02.24[g2]-awayrwhitby-away, when I build the -vfatdisk2 it works with the big vfat disk on port2
00:02.40[g2]-away# df
00:02.40[g2]-awayFilesystem           1k-blocks      Used Available Use% Mounted on
00:02.40[g2]-awayrootfs                    9911      8928       881  91% /
00:02.40[g2]-away/dev/root.old             9911      8928       881  91% /
00:02.40[g2]-away/dev/sdb1            119995104        32 119995072   0% /share/flash/data
00:52.05ka6soxokay stupid question #1 for the day: I've unslung my slug but it doesn't respond to the root pw for uNSLUng? doe this mean it failed?
00:53.19[g2]-awayka6sox, was the disk unslung before ?
00:53.26ka6soxno
00:53.32ka6soxit is a stock one.
00:53.54ka6soxformtted by the slug 10 minutes ago with R25
00:54.05[g2]did you run unsling
00:54.26ka6soxoh...no...I didn't see that in the readme.
00:54.53[g2]enable telnet via the web intf
00:54.57[g2]telnet in and unsling
00:55.05[g2]reboto
00:55.08[g2]or reboot
00:55.15ka6soxthat is the problem . telnet is enabled and the root pw is not working.
00:55.22ka6soxokay rebooting now.
00:56.21[g2]ka6sox, you should have been able to get in
00:56.26[g2]which password did you us
00:56.29[g2]e
00:56.34ka6soxuNSLUng
00:57.21[g2]What does the top admin web page say in the upper right when you web to the box ?
00:57.37ka6soxoh..it failed...
00:57.42ka6soxstill R25
00:57.50ka6soxhmmm weird.
00:57.57[g2]Firmware Version:  V2.3R25-uNSLUng-1.11-beta
00:58.10ka6soxV2.3R25
00:58.18ka6soxit failed then.
00:58.26[g2]looks like it
00:58.34[g2]the flash didn't
00:58.41ka6soxokay brb
00:59.24ka6soxI made a fatal misteak...I left the HD plugged in...
00:59.28ka6soxmy bad.
01:00.18[g2]ka6sox, that shouldn't matter but it goes faster if you don't have one plugged in
01:00.44ka6soxokay trying again.
01:01.43ka6soxthanks...been a stressful day...bricked my G4 too...with a Debian YaBoot problem :P
01:02.27TierstenHey
01:02.32[g2]suck
01:02.52Tierstenka6sox: I believe the proper term is "boat anchor".  A brick the size of a G4 would have to be for one big house!
01:02.54Tiersten;)
01:03.10[g2]lol
01:03.17ka6soxyes!
01:03.43ka6soxno version of Knoppix for PPC yet.
01:04.02[g2]there's gentoo for the ppc
01:04.25TierstenI'd be surprised if there wasn't a Gentoo for most platforms.  It's not like they have to make binaries :)
01:04.53ka6soxokay..one beep and then alternative red/green flashing.
01:05.48[g2]Tiersten, on the contrary my friend, where do the livecd's come from? And there's the GRP install which is mostly a binary install
01:06.16ka6soxhave I bricked it..its been flashing for over 2 minutes
01:06.21ka6soxafter the beep
01:06.54Tiersten[g2]: Ah well.  Live cds don't count ;)  And GRP didn't always exist ;)
01:07.10TierstenAny other points you may wish to make also don't count ;)
01:07.17ka6soxouch!
01:07.32TierstenAnything appear on the serial port?
01:07.40[g2]Tiersten, it's a good thing you're working on something I need/want :)
01:07.53ka6soxhaven't modded this one yet...
01:08.05TierstenYou want my chocolate chip cookie recipe?  Well okay...
01:08.05ka6soxlooks like I will be doing that tonight.
01:08.19TierstenYou could do the redboot telnet thing
01:08.33ka6soxlooks like I will be doing that!
01:10.56hculvergot a failed oe build with rwhitby's local.conf and a bk pull from just before the build.
01:11.02hculverinstall: cannot stat `/export/project/openembedded/build/tmp/work/busybox-1.00-rc3-r6/udhcp-serrver': No such file or directory
01:11.24hculverNOTE: Task failed:
01:11.24hculverERROR: package busybox-1.00-rc3-r6: task do_package failed
01:11.24hculverERROR: TaskFailed event exception, aborting
01:11.24hculverERROR: package busybox: build failed
01:11.24hculverERROR: Build of bootstrap-image failed
01:11.52Tierstenhculver: Did you work out what was wrong with your wiggler setup?
01:12.03hculversorry didn't mean to make it sound like I was blaming someone.
01:12.27hculverNo haven't gotten back to the jtag stuff yet.  Working on 2 different nslu kernel builds.
01:14.33[g2]hculver, what were you oemake'ing
01:15.14hculverunslung
01:16.14[g2]which unslung
01:17.12hculverOK, I'm still coming up to speed (after a few weeks off).  Whatever a bk pull and the local.conf that rwhitby posted to nslu-changessets gives me.
01:17.41hculverI'm guessing unslung 2.x
01:20.12[g2]hculver, I mean what did you type on the oemake command
01:20.34[g2]oemake unslung ?
01:21.06hculveroh, sorry.   oemake bootstrap-image, not correct?
01:21.31[g2]well, I think that was correct
01:22.12hculverDISTRO="unslung" TARGET_OS="linux"
01:22.39[g2]for the 2.x stuff I did a oemake nslu2-unslung-kernel-vfatdisk2 and nslu2-unslung-ramdisk
01:22.58hculverOK, still an oe n00b
01:23.15[g2]I think there's a nslu2-unslung-kernel-ext3... and a plain kernel
01:23.32[g2]hculver, join the crowd
01:24.07hculvera full belly and 2 glasses of shiraz don't help much. :)
01:24.27[g2]:)
01:25.08hculverI think I'll do another bk pull.  Its been several hours.
01:25.32[g2]there's probably no need
01:26.11hculveryou're right.
01:28.26[g2]I'm about to try unslinging from the oe build ramdisk
01:28.44hculver[g2]: gl
01:29.20[g2]well there's an unsling command there :)
01:29.26ka6soxokay this is weird.
01:29.40ka6soxI can get the web interface to work.
01:29.45ka6soxand it reports unslung
01:30.08ka6soxBUT telnet won't let me in with the uNSLUng password.
01:31.42[g2]ka6sox, which sw are you running ?
01:32.32ka6soxokay this is weird...it said unslung a minute ago..and now it says V2.3R25
01:32.53[g2]it only says that on the top page
01:32.58[g2]the unslung....
01:33.14ka6soxokay the top page says unslung
01:33.29ka6sox1.1-beta
01:33.30[g2]that's normal not wierd
01:33.36ka6soxokay.
01:34.02ka6soxso either I'm sending the wrong information or something else is happening.
01:34.40ka6soxlogin incorrect.
01:35.16ka6soxlemme get the serial port setup here on this one and I'll check to see what is coming out.
01:36.22*** join/#nslu2-linux rwhitby-away (~rwhitby@CPE-144-136-196-72.sa.bigpond.net.au)
01:36.39rwhitby-awayhculver: did you bk -r co -q ?
01:36.48rwhitby-awayafter each bk pull ?
01:37.19rwhitby-awayhculver: use unslung-image, not bootstrap-image
01:38.21hculverrwhitby, yes.
01:39.13hculverOK, I;ve done an oemake nslu2-unslung-kernel, should I stop that?
01:39.28rwhitby-awayno that's fine
01:39.41rwhitby-awayjust do an unslung-image afterwards
01:39.51hculverok
01:40.34rwhitby-away[if you just want the kernels then you don't need to do unslung-image, but it looks from your error that busybox might be broken, so you'll want to stay away from bootstrap-image until it's fixed]
01:42.00[g2]rwhitby-away, the vfat2 disk worked on port2 when made with -vfatdisk2, I've unslung from the nslu2-unslung-ramdisk, but there were two sed errors.
01:42.09[g2]The pw seemed fine
01:42.19rwhitby-awayand if something is fixed in openembedded.bkbits.net but hasn't been pulled into nslu2-linux.bkbits.net, then you can always bk parent temporarilily to openembedded to pick up the latest changesets from there.  BitKeeper is smart enough to know you've already got those next time you bk parent back to nslu2-linux and bk pull.
01:42.41rwhitby-away[g2]: the sed in unsling is expected, as we haven't spliced in the support utils yet.
01:42.53[g2]and I've got the path I dislike
01:43.10rwhitby-awaygood news on the vfatdisk2 (it's called vfatdisk2, not vfat2disk, cause it only causes vfat on the disk2 port)
01:43.14[g2]rwhitby-away, the pw for root in /passwd was correct though
01:43.36rwhitby-awayyeah - if you unsling a virgin disk, then you don't need the seds
01:44.11[g2]ah..
01:44.28[g2]it runs to check, but the sed wouldn't have executed
01:44.39rwhitby-awayyep
01:44.56[g2]Ok, then I'm unslung on 2.x with the vfatdisk2 kernel
01:45.09rwhitby-awayjust pulling latest from openembedded into nslu2-linux now
01:45.14[g2]well... I just haven't flashed it
01:45.35rwhitby-away[g2]: cool - you won't have an ipkg script there, so no point in flashing until we splice the stuff in
01:46.19[g2]np.. oe is working nicely when you know what to build! :)
01:46.59rwhitby-awayyep, we're getting close - as soon as we do the splice then a whole world of packages will open up
01:48.08[g2]rwhitby-away, was there a final decision on /opt versus normal install on an unslung disk ?
01:48.55rwhitby-awaynot yet.  Kergoth said that we should be able to do /opt in OE easily, and packages which don't act accordingly are considered to have a bug
01:51.28rwhitby-awaywhat's your opinion on that, [g2]?
01:52.19[g2]rwhitby-away, well, we've started down the slipery slope.
01:52.34[g2]I this case I don't think that's a bad thing
01:52.41rwhitby-awaywhich slope?
01:52.55rwhitby-awaynormal or /opt?
01:53.12[g2]diversion from unslung
01:53.41[g2]originally, unslung was "stock kernel and libs" with diversion scripts
01:53.50rwhitby-awayyep
01:54.07rwhitby-awayand unslung firmware will remain as that
01:54.54hculveroooooo   2.4.22-xfs-nslu2.patch.  I may need to apply that to the stock snapgear 3.1.1 and compile the nfs module again (don't have to manually apply the 2.4.21 xfs patches).
01:55.42rwhitby-away[g2]: [we're only flashing in those packages which are required to run unsling and ipkg and last-resort recovery]
01:55.44[g2]ok. so nslu2-unslung is will include a package manager
01:56.54rwhitby-awayyep, that's what we're splicing in
01:57.12rwhitby-awayyou mean "unslung-image", right?
01:57.33rwhitby-away[which includes nslu2-unslung-kernels and nslu2-unslung-ramdisk]
01:58.10rwhitby-awayI'm setting it up so someone can do a slugplus-image and include other packages in the ramdisk for systems without external storage.
01:58.11[g2]well it gets blurry to me that splicing in nfs support, etc... violates the "stock kernel". Clearly I think end-users want functionality and only mildly care about backwards compatibility
01:59.10rwhitby-awayyou mean nfs support in kernel (for loading rootfs from nfs) or nfs-server support for users (which can easily be done with a package)
02:00.09rwhitby-awayhculver:  bootstrap-image works now (if you were looking for a busybox compile for some reason) - they must have fixed it overnight
02:00.35rwhitby-away[g2]: end-users of unslung will complain bitterly if stock functionality does not work for some reason
02:00.57hculverno, just that my 2nd oemake bootstrap-image failed on busybox.
02:01.12hculverjust getting my feet wet.
02:01.21rwhitby-away[g2]: [unless they intentionally add a package which is clearly marked as overriding stock functionality]
02:01.46rwhitby-awayhculver: looks like it was just a temporary oe problem in the parent repo - seems to be fixed now
02:01.48[g2]rwhitby-away, ok.
02:02.09rwhitby-awayslugplus or openslug is a different matter altogether
02:02.32hculver[g2]: btw, you were right, my original oemake was OK. I still had my zImage in my /tftpboot directory and did an exec instead of an go and it booted ok.
02:03.14[g2]hculver, great. that's good to know
02:03.19rwhitby-awayyeah, go doesn't seem to work with oe made images - you need to run exec 0x01d00000
02:04.03hculver(of course thats after I rm -rf build/tmp'd). :)
02:05.20hculverI know its a bit off topic, but I like that my snapgear 3.1.1 w/Intel patches boots.
02:06.26hculverActually the openslug 2.6 kernel booted with a completely unrelated ramdisk.
02:06.54hculver(lots of unresolved references, but a # is a #).
02:07.11[g2]hculver, congrats on the snapgear 3.1.1
02:08.05hculverIf I can get that xfs patch applied, I think the nfs kernel module will compile and then nfs v3 and > 2G should work (I know unfs is already working).
02:09.09rwhitby-awaybbiab
02:10.29hculvermy oemake nslu2-unslung-kernel just finished.
02:12.28[g2]when rwhitby-away comes back he can explain the exact differences between the 3 nslu2-unslung kernels the -vfatdisk2 allows large msdos/vfat disks on port 2
02:13.03[g2]there's an ext3 something amd the normal kernel
02:15.43hculvernslu2-unslung-kernel looks pretty good.
02:16.23hculverdoing an oemake unslung-image now.
02:21.55hculveryou know, #tivo is not a very happy place to be.  I've been lurking there for days, and anyone other than a rather small clique is ignored.
02:22.34*** join/#nslu2-linux __chris__ (~chris@pcp09944349pcs.hyatsv01.md.comcast.net)
02:23.20TierstenYup
02:24.06rwhitby-away[g2]: the differences are captured in the patch files in nslu2-unslung-kernel-2.4.22 directory
02:25.06rwhitby-awayext3flash mounts all disks as ext3 (even flash disks).  vfatdisk2 mounts anything on the disk2 port as vfat (even hard disks).  the normal one is normal unslung behaviour (1Gb limit between vfat flash and ext3 hard disk)
02:26.00rwhitby-awayhculver: yeah, we have a number of lurkers here, and I'm always on the lookout for them to make themselves know if they wish :-)
02:26.21rwhitby-away[or just stay lurking if they wish too :-)]
02:28.39rwhitby-away... make themselves known (typo) ....
02:29.25hculveryeah, well I used to be god's gift to programming, now I'm happy with every fragment of help I get.
02:35.25hculver"The very young do not always do as they are told" - Stargate SG-1
02:36.02rwhitby-awayok - I'm off for a picnic lunch
02:36.06rwhitby-away~weather YPAD
02:36.24[g2]rwhitby-away, enjoy!  turn off the -treo
02:36.25hculverbon-apetite
02:36.40[g2]I'm off to sleep early