**** BEGIN LOGGING AT Sun Jun 11 02:59:57 2006 Jun 11 03:33:29 hey all Jun 11 03:33:38 does anyone iknow if the debian how to Jun 11 03:33:45 supposiely works with the latest openslug beta? Jun 11 03:36:47 hmm? Jun 11 04:07:47 EnterUserName: the Bootstrap procedure works with DebianSlug firmware Jun 11 04:11:15 rwhitby: I'm kinda confused.. Im following the OpenDebianSlug instructions Jun 11 04:11:20 are those outdated? Jun 11 04:11:30 it seems to just be in a never for ending loop with the leds Jun 11 04:11:36 and i cant seem to access it Jun 11 04:12:56 EnterUserName: if you want to use Debian, you should use the DebianSlug firmware now (little endian), not the OpenSlug firmware (big endian) Jun 11 04:13:11 http://www.nslu2-linux.org/wiki/DebianSlug/Bootstrap Jun 11 04:14:16 ok thank u.. i'll continue :) Jun 11 04:25:21 umm Jun 11 04:28:02 hmm sarge or sid:) Jun 11 05:05:14 I use sarge. Jun 11 05:05:41 Both work fine as far as I know Jun 11 05:07:14 oh ok.. Hmm if i ever get time maybe i'll make my own web interface Jun 11 05:11:00 this little device is pretty kewl. :) Jun 11 07:19:29 rwhitby: does the build system by any chance have a dir /opt/montavista/pro/devkit/arm/xscale_be/target Jun 11 07:20:23 false alarm Jun 11 07:20:30 it is a different dir Jun 11 07:20:54 need to know what this is: ${STAGING_DIR}/${HOST_SYS} Jun 11 07:22:26 the diff between my asterisk build and the nudi one is that chan_alsa does not get build on my system. this is triggered by the line: Jun 11 07:22:27 ifneq ($(wildcard $(CROSS_COMPILE_TARGET)/include/alsa/asoundlib.h),) Jun 11 07:22:27 CHANNEL_LIBS+=chan_alsa.so Jun 11 07:22:27 endif Jun 11 07:22:50 and the bb file says: export CROSS_COMPILE_TARGET="${STAGING_DIR}/${HOST_SYS} Jun 11 07:23:27 idea, hang on Jun 11 07:25:43 i'm having trouble recompiling openslug 3.10-beta. is this the right place to ask for help? Jun 11 07:26:13 maybe, depends also on your problem. shoot Jun 11 07:26:43 padBytes error: data (1064308) is longer than total_len (1048576) at /home/hamish/projects/openslug/slugos-3.10-beta/openslug-nslu2.tmp/staging/x86_64-linux/bin/slugimage line 58. Jun 11 07:27:03 during the compile of slugos-image-1.0-r28 Jun 11 07:27:16 ouch, that means your kernel is too large Jun 11 07:27:31 what is your host hw? Jun 11 07:27:39 amd64, dual core ? Jun 11 07:27:49 amd64 single core Jun 11 07:28:30 i attempted to build in an i386 chroot in case building on 64-bit wasn't supported. but gcc had an internal error earlier in the process Jun 11 07:28:42 ah ok, I was not sure whether single or dual core was relevant Jun 11 07:29:00 might try building on a real x86 machine Jun 11 07:29:14 for some unknown reason the gcc cross compiler on amd64 generates larger code than it does on intel hw. Jun 11 07:29:48 ok, so if I can get it building on x86 (either chroot or another machine) it should work? Jun 11 07:30:12 which is odd as the code size shoudl not depend on the host platform, but apparently some decisions are taken differently because your host has a different processor Jun 11 07:30:45 hamishm: yes. I build on a 3 Ghz dual pentium (930), and I build on a single 3 Ghz pention as well Jun 11 07:31:40 my build in an i386 chroot died in gcc-cross-initial, with a segfault. :( Jun 11 07:31:47 ~seen rwhitby Jun 11 07:31:54 rwhitby is currently on #oe (10h 3m 27s) #nslu2-linux (10h 3m 27s) #openslug (10h 3m 27s). Has said a total of 9 messages. Is idling for 2h 26m 14s, last said: 'Both work fine as far as I know'. Jun 11 07:32:59 rwhitby: I expect the nudi build to fail and mine to succeed because nudi apparently already build alsa (because it is earlier in the list if you do a full build) and my system (or Corneliu's) does not Jun 11 07:38:51 verified this, did a bb alsa-lib followed by a bb asterisk and it indeed fails. Jun 11 09:41:45 what is the subversion URL to checkout the 3.10beta release? Jun 11 09:42:05 3.6 at berlios? or 3.10 at nslu2-linux? Jun 11 10:03:48 pepijn: why not dowonload the sources directly (without checkout), eg from here: http://sources.nslu2-linux.org/releases/ Jun 11 10:04:28 or indirectly: http://www.slug-firmware.net/s-dls.php Jun 11 10:04:55 if you want the 3.10 version there is no need to get them from svn or cvs Jun 11 10:05:00 eFfeM: i use extra kernel modules and need to build those Jun 11 10:05:14 do not want to build from MasterMakefile (HEAD) Jun 11 10:05:23 but want the 'stable' release Jun 11 10:05:28 yes, just grab the sources from any nslu2-linux and modify defconfig Jun 11 10:05:37 then rebuild Jun 11 10:05:46 (gone again, have to manage the BBQ :-) ) Jun 11 10:05:57 but getting the sources from the release was too obvious ;) Jun 11 10:11:26 btw afterthought: if you need additional modules which are not there just let us know. Adding a few m's to defconfig does not cause additional footprint so this is something that can be done easily Jun 11 10:12:12 that's why there are so many modules nowadays. I had a few things added because I had the hw that needed this Jun 11 10:12:17 back to bbq again Jun 11 10:12:38 where can the extra modules be downloaded from? Jun 11 10:12:43 in ipkg format is ok Jun 11 10:12:52 (for debianslug) Jun 11 10:13:16 would save me some compile time ;) Jun 11 10:22:32 i mean: i use extra (as in, not from flash image) modules for debianslug and the defconfig does compile them Jun 11 10:22:52 but they are not installed through the image, nor are they available through apt Jun 11 10:23:06 so if i can just download them from the ipkg feed, it should be ok Jun 11 11:30:25 never mind, found http://ipkg.nslu2-linux.org/feeds/debianslug Jun 11 11:38:43 ok, actually if your ipkg.conf or whatever is ok you can just do ipkg install and it will happily install them Jun 11 11:43:31 yeah, but debian has no 'native' ipkg package Jun 11 11:43:48 but i guess i could always install ipkg from the feed (using dpkg) and start using it ;) Jun 11 11:43:58 (for the ipkg packages, that is) Jun 11 11:44:22 ah, ok i think you can indeed install it (played with debian in the past but decided I found contributing to oe easier Jun 11 11:44:24 nice thing about ipkg is that ipkg install also works Jun 11 11:44:27 and more fun of course Jun 11 11:44:33 ah didn't know that Jun 11 11:44:46 i do that with openwrt Jun 11 11:48:49 haven't really played with openwrt, actually I have a wrt54g on my desk but it is an r5 one, need to swap it with another one Jun 11 12:19:54 the idea is to turnup back to flash, install any kernel modules you need, turnup back to the debian disk, then copy the kernel modules from /initrd to the disk. Jun 11 12:20:16 Or you can dpkg install a .ipkg file manually (you might need to force it due to missing dependencies). Jun 11 12:21:21 http://svn.nslu2-linux.org/svnroot/slugos/releases/slugos-3.10-beta/ is the svn URL (read-only unless you're authorised to modify the stable branch) Jun 11 12:22:00 rwhitby: re: ipkg, i used dpkg to install extra modules on the debian root, no need to have them on the flash root Jun 11 12:22:21 works fine, but nw want to upgrade to 3.10beta, so needed updated ipkgs Jun 11 12:22:26 that i have worked out now Jun 11 12:22:38 when it comes to the URL, i'll give that a try Jun 11 12:22:44 only need read access ;) Jun 11 12:23:09 but with the debianslug ipkg repository i do not need to do any compiling myself Jun 11 12:24:07 BTW, the DebianSlug image has the ipkg feed location (you should use feeds/slugos-lag/3.10-beta) Jun 11 12:25:00 ah, right, forgot to look at /initrd/etc/ipkg.conf :-P Jun 11 12:25:05 be aware that the unstable feed is going to become incompatible very quickly with the 3.10 release, cause we're going to gcc 4.1 on the monotone head (so kernel modules built with gcc 4.1 won't work with any released binaries) Jun 11 12:25:18 of course Jun 11 12:25:44 that was why i originally wanted to compile everything myself from the stable branch Jun 11 12:25:53 yep Jun 11 12:26:30 is http://ipkg.nslu2-linux.org/feeds/debianslug a symlink to http://ipkg.nslu2-linux.org/feeds/slugos-lag ? Jun 11 12:26:58 probably, but only for legacy purposes - it's not guaranteed to stay Jun 11 12:27:06 k Jun 11 12:27:22 the only feeds guaranteed to stay are those that were referenced by released binary images Jun 11 12:27:53 other alpha feed locations (of which feeds/debianslug is one) eventually disappear Jun 11 12:28:29 will the term 'DebianSlug' be phased out as well? Jun 11 12:28:37 it is casuing loads of confusion Jun 11 12:28:48 s/casuing/causing/ Jun 11 12:28:49 pepijn meant: it is causing loads of confusion Jun 11 12:29:22 well, the distro is called SlugOS, and it has big-endian and little-endian versions. Jun 11 12:29:45 i know, discussed that with NAiL at one point Jun 11 12:29:45 The little-endian version happens to be useful for debootstrapping to Debian, and therefore became known as DebianSlug. Jun 11 12:30:48 So SlugOS/LE will probably always stay around (cause it is also used by the GentooSlug guys), but the kernel should eventually be very close between SlugOS/LE and Debian/NSLU2. Jun 11 12:31:32 yes, not thinking about that, just about terminology in repositories and in the wiki Jun 11 12:31:37 (i.e. the patchset should be identical from a userland point of view, but perhaps the defconfig might be different due to Debian policy or something outside of nslu2-linux control) Jun 11 12:32:17 you'll notice that the new SVN repository is called slugos, and the SlugOS 3.10 release README points to SlugOS/*** in the wiki. Jun 11 12:32:32 yep, i noticed Jun 11 12:32:55 * pepijn thinks that is a good thing Jun 11 12:33:34 the OpenSlug name is just as "wrong" as the DebianSlug name, cause both variants of SlugOS are built from OpenEmbedded, and both variants can be used to debootstrap a Debian rootfs. Jun 11 12:33:43 agreed Jun 11 12:33:53 but it's hard to change historical reasons Jun 11 12:34:19 but one can try ;) that was basically what i asked Jun 11 12:34:40 yes, you'll notice that I use the SlugOS term as much as possible. Jun 11 12:35:14 i noticed in your response to l0c4lh0st Jun 11 18:48:43 hi just got my second slug up and running but the openslug-native seems to have dissapeared.... would the slugos ones do...? Jun 11 19:38:20 openslug is the depracted name for slugos-bag Jun 11 19:38:35 s/depracted/deprecated/ Jun 11 19:38:36 pepijn meant: openslug is the deprecated name for slugos-bag Jun 11 20:00:05 i've a BIG problem: i was happly using my 2.7 openslug until 2 hours ago, but now after a ./upslug2 -i openslug-3.10-beta.bin i can't ping the nslu, nor on the old ip, nor on 192.168.1.77 or with dhcp... Jun 11 20:00:44 and the strange thing is that now while boothing the led seems to blink amber-red-off instead of amber-off-amber-off etc etc Jun 11 20:01:24 but after some seconds the led is fixed green...but no way to find the slug on the net Jun 11 20:19:08 hia ll Jun 11 20:19:16 Where do i find some instructions on how to use a custom kernel for debianslug Jun 11 20:19:25 is it similiar to the openslug customization instructions? Jun 11 20:46:24 hi all Jun 11 20:46:38 im trying to develop lvm way to get to work with debianfirmware Jun 11 20:46:43 however i would like to customize my own kernel Jun 11 20:46:55 can't seem to find instructions on it Jun 11 20:49:13 EnterUserName, do you use the master makefile? Jun 11 20:54:28 I probably will do that. Sorry I should give it a try first. and look at the slugos source. Jun 11 20:56:17 but i'm using debianslug and im not too sure cuz i uses little endian Jun 11 20:56:20 i need some info before starting.. Jun 11 20:56:22 the .config used for the slugos-kernel kompilation is @ ~slug/openembedded/packages/linux/ixp4xx-kernel/2.6.16/defconfig (when using the Master Makefile) Jun 11 20:56:33 s/kom/com/ Jun 11 20:56:33 EvilDevil meant: the .config used for the slugos-kernel compilation is @ ~slug/openembedded/packages/linux/ixp4xx-kernel/2.6.16/defconfig (when using the Master Makefile) Jun 11 20:57:11 thank you let me copy that Jun 11 20:57:18 EvilDevil: Will that work with DebianSlug? Jun 11 20:57:50 yes, DebianSlug is one of the SlugOs variants (slugos-lag) Jun 11 20:58:47 ok thank you.. i'll come back with some questions later. I see there were some problems using X64|_SUSe 9.3 Jun 11 20:58:52 are those problems still there with 10.1? Jun 11 20:59:01 for the cross compiling system? Jun 11 21:01:30 no clue. but this problems seems to persist on the 64bit platform. the resulting flashimages (or kernels *??*) are too big to flash Jun 11 21:01:41 hmm Jun 11 21:01:51 ok maybe i'll use my older athlon system then when i get hoem Jun 11 21:02:08 its a Athlon Xp 1.6 slower system but if its easier.. and i'll install ubuntu on it Jun 11 21:02:15 to go along with the instructions thanx :) Jun 11 21:02:43 thank you for the help Jun 11 21:03:55 you could install a 32bit linux on the x64 too (10-15 gb should be enough) **** ENDING LOGGING AT Mon Jun 12 02:59:56 2006