**** BEGIN LOGGING AT Sun Jan 27 02:59:57 2008 Jan 27 04:53:54 03bzhou * r7660 10optware/trunk/ (3 files in 2 dirs): slimserver: fixed -I/opt/include on slugos, promoted Jan 27 07:24:00 03bzhou * r7661 10optware/trunk/ (make/apache.mk sources/apache/httpd-conf-in.patch): apache: 2.2.6 -> 2.2.8 Jan 27 11:04:38 03rwhitby * r1006 10kernel/trunk/patches/apex/ (fatslug-sdram-init.patch series): Added fatslug detection by default Jan 27 11:37:08 03rwhitby * r1007 10kernel/trunk/patches/2.6.25/ (4 files): Updated rtc patches from my git repo ready for upstream Jan 27 11:59:50 hi, is *.nslu2-linux.org undergoing some maintainance? it seems to be dead :( Jan 27 12:01:51 03rwhitby * r1008 10kernel/trunk/patches/2.6.25/ (10 files): Submitted four more patches upstream Jan 27 12:03:33 treitmayr: looking at it Jan 27 12:03:45 the server is up (it's the svn repo too, and that's working fine) Jan 27 12:04:40 hmm, for me www is slow, svn even slower/not responding Jan 27 12:06:30 i have a question: Does the ethernet driver in kernel 2.6.23.14 still have a problem with nfs ("nfsd: non-standard errno: -14") or did I miscompile? Jan 27 12:07:20 its happening for me on SlugOS/LE (homemade EABI version) Jan 27 12:07:31 treitmayr: I haven't tried NFS on that version myself. Jan 27 12:09:21 treitmayr: www should be back to normal now Jan 27 12:10:16 great, thanks Jan 27 17:15:50 Hmm, is it normal that untarring gentooslug uses more than 2G ? Jan 27 17:39:56 03rwhitby * r1009 10kernel/trunk/patches/2.6.25/ixp4xx-4771-ethernet-support.patch: Updated with comments from l-a-k. Jan 27 19:28:58 hey Jan 27 19:29:54 what's the proper procedure to upgrade my existing nslu2 load to the latest kernel? I tried just installing a module but it installed the .23 and I'm still at .21 so might as well.l. Jan 27 19:30:28 I just started a fresh build but I wanted to try it while I wait.. Jan 27 19:30:50 ipkg doesn't seem to mind me having multiple version of the kernel! Jan 27 19:33:06 ipkg == kernel agnostic Jan 27 19:33:53 notice that! I now have a .23 kernel and all old .21 modules... messy Jan 27 19:34:39 no easy way to upgrade accross the board? Otherwise I'll just wait for the build... Jan 27 19:34:43 wait for the build Jan 27 19:34:47 are you using 4.8? Jan 27 19:34:50 Is the latest slugosbe head defaulting to .23 anyways? What about EABI? Jan 27 19:34:51 or 4.4? Jan 27 19:35:02 EABI is only on Anstrom Jan 27 19:35:05 Angstrom Jan 27 19:35:20 4.7beta from dec. Jan 27 19:35:38 ok. What's the build target? angstrom? Jan 27 19:35:39 ah, 4.8 iirc is a 2.6.23.12 Jan 27 19:35:52 for EABI its Angstrom. Jan 27 19:36:15 I will be playing with gpsd and my robot code uses a lot of vector math so I think it's worth a try.. Jan 27 19:36:29 * VoodooZ aborts his slugosbe build... Jan 27 19:36:35 the FP is a lot better in EABI Jan 27 19:36:41 yep. Jan 27 19:36:58 any side-effect to angstrom? Jan 27 19:37:17 As in ethernet driver support or? Jan 27 19:37:58 I'm starting to ramp up on all this as I haven't touched the robotics stuff in 1-2 years... I'm psyched again... Jan 27 19:38:04 currently NO Optware package in Angstrom. Jan 27 19:38:22 not an issue for me. good. Jan 27 19:38:43 there's a lot of anstrom targets... I guess angstrom-image is all I need... Jan 27 19:38:58 there's a be and le build too.. choices... Jan 27 19:40:20 are you using libusb? Jan 27 19:40:29 ooops. yes... Jan 27 19:40:32 why? Jan 27 19:40:50 its broken in BE for some things. Jan 27 19:41:00 darn.. Jan 27 19:41:11 (maybe they have a later version in Angstrom) Jan 27 19:41:27 I would test BE first Jan 27 19:41:33 Ok. not a big deal.. I'll try it.. Jan 27 19:41:35 thanks. Jan 27 19:41:35 if it doesnt' work then switch to BE. Jan 27 19:41:44 S/BE/LE Jan 27 19:44:15 Angstrom right now does not work with BE, AFAIK Jan 27 19:44:29 due to EABI Jan 27 19:44:48 just try LE Jan 27 19:45:08 [BTW, I got SlugOS/LE compiled with EABI] Jan 27 19:45:28 I need to ping Lennert and ask him where my EABI BE toolchain is! :P Jan 27 19:49:34 rwhitby: I've discovered part of what's going on with the makefile. I think there's a circular dependency. gcc-4.1 depends on libc6 libc6 depends on libgcc1 and libgcc1 depends on gcc-4.1. Jan 27 19:53:40 Q: SlugOS unstable uses APEX, how can I upgrade the kernel "the APEX way"? "ipkg upgrade" did not change the kernel. Jan 27 19:56:49 would I have to use apex-env? Jan 27 19:57:11 treitmayr: you need to flash the new kernel into the onboard flash Jan 27 19:57:42 (along with the new initrd/initramfs) Jan 27 19:59:04 http://www.nslu2-linux.org/wiki/SlugOS/Upgrade Jan 27 19:59:16 I think I heard of an easier/better method Jan 27 19:59:26 but it will take me a few minutes to find it Jan 27 19:59:27 that's what I also thought Jan 27 20:42:16 Ok, at this time, it is beyond my time commitment to get the arm-cross build environment up. The current problem is that in the debian pool, the highest version of libgcc1-4.1 is 1-21, while the highest version of gcc-4.1 is 2-18. This makes libgcc1 incompatible with gcc-4.1. I'm going to have to ty a different distro. Jan 27 21:03:17 treitmayr: I'd be curious to see how you did that.... Were you the one who posted the speexenc benchmark on egroups? Jan 27 21:15:01 03bzhou * r7662 10optware/trunk/make/libmemcache.mk: libmemcache: removed -pipe option if toolchain is anything like cs04q3armel Jan 28 00:41:23 well, it looks like I've finally gotten a debian base system onto my NSLU2 through the slugos/le debootstrap method. Jan 28 00:41:41 Now I just need a kernel that recognizes all my RAM. Jan 28 00:56:27 03bzhou * r7663 10optware/trunk/make/less.mk: less: 416 -> 418 Jan 28 00:58:15 03bzhou * r7664 10optware/trunk/make/ (optware-bootstrap.mk wget.mk): wget: 1.10.2 -> 1.11 Jan 28 01:09:02 Any slugos/le users here? Jan 28 01:09:18 yes Jan 28 01:10:26 Can you tell me what it means when I have the status LED doing double-blinks? Jan 28 01:10:37 (I don't have a serial mod in place) Jan 28 01:16:11 Perhaps I wasn't clear enough. The status LED is steady green with two orange blinks every second. It closely resembles a heartbeat. Jan 28 01:17:10 mine isn't doing that so I can't tell you. Jan 28 01:17:52 Ok. Do you know where I can find a resource listing the LED codes on a slugos/le install? Jan 28 01:18:11 the only place would be the wiki. Jan 28 01:18:36 It started doing this after I attempted to reboot into my debian system following my debootstrap Jan 28 01:19:21 check the debonras website then..sound like a debian thing. Jan 28 01:19:36 It hasn't grabbed an ip, which makes me think the boot failed. Jan 28 02:22:31 is it normal that building angstromle-image builds all that extra crap... like non-system related stuff... **** ENDING LOGGING AT Mon Jan 28 02:59:57 2008