**** BEGIN LOGGING AT Sat Jun 16 02:59:56 2007
Jun 16 06:03:18 <CIA-8> 03bzhou * r6220 10optware/trunk/ (4 files in 4 dirs): nginx: 0.5.25 -> 0.6.0; native -> cross; promoted for non-uclibc
Jun 16 10:28:39 <CIA-8> 03gda * r6221 10optware/trunk/ (2 files in 2 dirs): added loop module
Jun 16 16:01:52 <CIA-8> 03bzhou * r6222 10optware/trunk/make/py-turbojson.mk: py-turbojson: 1.0 -> 1.1
Jun 16 17:52:22 <Dsbeerf> hey someone can tell me for doing a serial jtag what kind of max3233 i need i have choice between 20/pdip 20/soic and 28/soic what the difference which one i need ?
Jun 16 17:57:28 <NAiL> depends on how you want the chip
Jun 16 17:57:40 <NAiL> pdip/soic is the packaging
Jun 16 17:58:06 <Dsbeerf> i just want to be able to add a serial to the slug hehe
Jun 16 17:59:56 <NAiL> the easiest by far is getting a ready-made cable
Jun 16 18:00:21 <NAiL> eg. a cellphone-cable, or one of them sparkfun serial->usb thingys
Jun 16 18:02:45 <Dsbeerf> i have a serial to usb but i need the rest to do the connect
Jun 16 18:04:18 <NAiL> ah
Jun 16 18:21:14 <pierrelux> Dsbeerf: you could open your usb cable and check which chip's inside
Jun 16 18:21:29 <pierrelux> then wire it to the slug
Jun 16 18:22:46 <Dsbeerf> well i think i need a 3.3v convertor cause the usb to serial is 5v no ?
Jun 16 18:24:04 <pierrelux> max233 is made to run on 3.3v
Jun 16 18:26:29 <Dsbeerf> yes but my usb to serial adapter is 5v so that why i need a max233 
Jun 16 18:26:38 <Dsbeerf> so i can not just open the cable and solder the wire
Jun 16 19:34:30 <osmeest> hello
Jun 16 19:35:11 <osmeest> I'm trying to install Debian on my iomega NAS 100d but I can't make it recognize the initrd...
Jun 16 19:35:55 <osmeest> it must be some mistake of mine but I can't see what to do to have it recognized
Jun 16 19:37:11 <osmeest> does someone here know how to do that ?
Jun 16 19:39:49 <kolla> what do you mean "recognize"?
Jun 16 19:41:15 <osmeest> well I built my own apex, installed the kernel from the debian installer
Jun 16 19:41:17 <osmeest> it boots
Jun 16 19:41:50 <osmeest> I also flashed the initrd.gz to the filesystem partition but the kernel does not recognize it
Jun 16 19:42:42 <osmeest> boot ends with: RAMDISK: Compressed image found at block 0                                      
Jun 16 19:42:42 <osmeest> No filesystem could mount root, tried:  jffs2                                   
Jun 16 19:42:42 <osmeest> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2) 
Jun 16 19:45:42 <filas> hi
Jun 16 19:45:49 <filas> everybody
Jun 16 19:46:04 <filas> I have a problem
Jun 16 19:46:27 <filas> I unlocked the slug
Jun 16 19:46:56 <filas> and now the redboot loads 1 time from 5-7
Jun 16 19:47:16 <filas> I can't understand on what it depends on
Jun 16 19:47:32 <filas> when I'm trying to install new firmware
Jun 16 19:47:47 <filas> first of all it installs 8-9 ours, very very slowly
Jun 16 19:48:06 <filas> and it fails the installation on 5% in the verifying stage
Jun 16 19:48:43 <filas> after that, I rebooted the slug and ready/status flashes amber and nothing going on further
Jun 16 19:49:02 <filas> are there eny ways to make the slug work correctly?
Jun 16 19:49:29 <filas> all problems tarted after I overlocked it, I shouldn't do it.. =(
Jun 16 19:49:59 <kolla> osmeest: so how did you create the ramdisk, is it cpio archive or some image file with filesystem?
Jun 16 19:53:49 <osmeest> kolla: as far as I could see (gunzip + file) it's a CPIO archive
Jun 16 19:54:17 <osmeest> and in the boot command by default in apex, it is specified rootfstype=jffs2
Jun 16 19:55:09 <osmeest> it is the initrd.gz that I extracted from di-nslu2.bin with slugimage
Jun 16 19:55:50 <kolla> hm, ok
Jun 16 19:57:28 <kolla> I'm not sure what it is then, just thought it might be a filesystem problem, but cpio should work I guess
Jun 16 20:00:55 <osmeest> kolla: but which rootfstype should it be ?
Jun 16 20:02:26 <filas> #nslu2-general
Jun 16 20:02:45 <filas> ups sorry
Jun 16 20:03:34 <filas> anybody... any ideas?
Jun 16 20:05:25 <osmeest> kolla: tried again without the rootfstype... 
Jun 16 20:05:40 <osmeest> same result but the message is No filesystem could mount root, tried:  cramfs                                                                                                                           
Jun 16 20:29:12 <kolla> hm
Jun 16 20:29:51 <kolla> filas: overclocked it?
Jun 16 20:29:59 <kolla> you mean.. you fixed it
Jun 16 20:30:11 <kolla> or did you really overclock it?
Jun 16 20:34:30 <CIA-8> 03bzhou * r6223 10optware/trunk/platforms/ (packages-gumstix1151.mk toolchain-gumstix1151.mk): gumstix1151: added RPC support to toolchain; promoted lsof portmap player xinetd
Jun 16 20:38:08 <filas> kolla
Jun 16 20:38:25 <filas> I removed the resistor as it was written in the http://www.nslu2-linux.org/wiki/HowTo/OverClockTheSlug.
Jun 16 20:39:13 <kolla> ok, and it is now 266MHz
Jun 16 20:39:17 <kolla> I did the same
Jun 16 20:39:21 <kolla> worked fine
Jun 16 20:39:27 <filas> well, I can't check it
Jun 16 20:39:33 <filas> because I can't start the slug
Jun 16 20:43:27 <filas> now, for example, after 9 hours of firmware uploading (it also fails in the varifying stage on 5)
Jun 16 20:43:37 <filas> now, for example, after 9 hours of firmware uploading (it also fails in the varifying stage on %5), the status led i amber
Jun 16 20:43:54 <filas> a nothing going on
Jun 16 20:48:12 <kolla> 9 hours??
Jun 16 20:48:39 <kolla> how do you flash it?
Jun 16 20:48:48 <kolla> I just telnet to it and flash from redboot
Jun 16 20:48:59 <filas> yes I started today at 11 AM, it finished at 20 PM
Jun 16 20:49:03 <kolla> over tftp or http
Jun 16 20:49:06 <filas> i flash with sercom utility
Jun 16 20:49:20 <kolla> sounds tedious
Jun 16 20:49:30 <kolla> over the serial console?
Jun 16 20:49:58 <filas> over the ethernet cable
Jun 16 20:52:39 <filas> kolla: I can't understand why it so long
Jun 16 20:53:32 <kolla> here it just takes a minute or so
Jun 16 20:54:08 <kolla> using the method described here.. http://www.nslu2-linux.org/wiki/HowTo/ReflashUsingRedbootAndTFTP
Jun 16 20:54:47 <filas> before overclocking it took me 10 minutes
Jun 16 20:57:07 <CIA-8> 03bzhou * r6224 10optware/trunk/Makefile: removed comment for nginx native build
Jun 16 20:57:39 <filas> maybe I removed resistor uncorrectly, but I don't think so, I did it really carefully
Jun 16 20:58:23 <filas> I haven't heard that others have such problems after overclocking
Jun 16 20:59:02 <filas> now I'm gonna try to reflash using your method
Jun 16 21:02:32 <mwester-laptop> filas: did you check that it was not one of the new ones that is already correctly clocked?  Rumor has it that removing what looks like the same resistor on one of those new ones is A Bad Thing.
Jun 16 21:04:46 <filas> mwester-laptop: it wasn't clocked, it showed 133 mhz
Jun 16 21:07:46 <filas> the slug should be in the upgrade mode, to telnet into redboot?
Jun 16 21:08:54 <kolla> no idea, I just turn it on and catch it with arping
Jun 16 21:09:03 <kolla> ctrl-c and I'm in redboot
Jun 16 21:09:33 <kolla> not sure wht "upgrade mode" is really
Jun 16 21:12:24 <mwester-laptop> filas: no
Jun 16 21:12:49 <osmeest> mwester: you probably can tell me... what's the kernel command line used in the debian installer ?
Jun 16 21:12:51 <mwester-laptop> upgrade mode is a mode where the device will accept a firmware download using a specific protocol
Jun 16 21:13:11 <mwester-laptop> that protocol is used by upslug2 on Linux/mac and by the sercomm utility on windows.
Jun 16 21:13:38 <mwester-laptop> telneting into redboot gains access to the bootloader, from there one of the many options available is to enter upgrade mode.
Jun 16 21:14:30 <mwester-laptop> If you use the arping, ctrl-c to enter redboot, typing "upgrade" will enter upgrade mode, but it's usually easier to use the reset button to do it.
Jun 16 21:14:35 <osmeest> mwester: I flashed the initrd.gz in the filesystem partition but now, when APEX boots the kernel, I've an error message "No filesystem could mount root, tried:  cramfs"
Jun 16 21:15:29 <kolla> ok, I only flashed from tftp or http when I was in redboot
Jun 16 21:15:36 <kolla> never used upslug
Jun 16 21:15:46 <mwester-laptop> kolla: try upslug2 (not upslug) or sercomm.
Jun 16 21:16:28 <kolla> nah, I'm comfortable with tftp :)
Jun 16 21:17:17 <mwester-laptop> kolla: your firmware flashing issue sounds like network problems to me -- so maybe your tftp server is not working the way the NSLU2 redboot would like.
Jun 16 21:17:56 <mwester-laptop> osmeest: I don't know what the debian cmdline is, I'm afraid.
Jun 16 21:19:15 <osmeest> or maybe you know how I should have the initrd recognized (what filesystem type it is)
Jun 16 21:19:46 <mwester-laptop> How did you create it?
Jun 16 21:20:14 <osmeest> took the di-nslu2.bin, extracted the files (initrd.gz an vmlinuz*)
Jun 16 21:20:22 <osmeest> vmlinuz is flashed in kernel
Jun 16 21:20:34 <osmeest> added a custom build of apex (for NAS100d)
Jun 16 21:20:58 <osmeest> the initrd is found but its type is not recognized apparently
Jun 16 21:21:54 <mwester-laptop> osmeest: I'd be really surprised if that would work; there are some strange things done to support the NSLU2 (since its redboot doesn't support FIS partitions).
Jun 16 21:22:21 <mwester-laptop> But I don't know -- perhaps someone else here might. :(
Jun 16 21:23:46 <filas> mwester-laptop: can't suggest why does flashing over sercom utlility now, takes me 9 hours?
Jun 16 21:24:07 <osmeest> mwester: I had slugosle working before but I've the impression there are more packages in debian than in optware (ipkg), is it right ?
Jun 16 21:26:33 <eno> osmeest: of course debian has more packages than optware
Jun 16 21:28:29 <osmeest> eno: just makes it more frustrating/challenging to have it working...
Jun 16 21:28:42 <osmeest> maybe should I try deboostrap'ing...
Jun 16 21:30:08 <filas> sorry mwester-laptop: can't assume why does flashing over sercom utlility now, takes me 9 hours?
Jun 16 21:30:10 <filas> =)
Jun 16 21:31:28 <mwester-laptop> filas: if any part of flashing takes more than a few minutes, the problem is almost certainly network-related.
Jun 16 21:32:06 <mwester-laptop> I would check cables and switches, and especially watch for misconfigured 10/100 full/half hubs/switches (the NSLU2 is auto).
Jun 16 21:32:45 <mwester-laptop> Ideally, use standard cables, and a standard 10/100 autosensing hub, with little else on the network.
Jun 16 21:33:11 <mwester-laptop> You cannot flash over a wireless link, or across routers, or subnets.
Jun 16 21:33:33 <eno> osmeest: is it that you have a fatslug that makes installing debian difficult?
Jun 16 21:34:19 <mwester-laptop> Also check what the hw ethernet (MAC) address used by the NSLU2 might be -- that's stored in flash, and there might be obvious problems if it is set to 00:00:00:00:00:00 !
Jun 16 21:45:53 <filas> mwester-laptop: I'm flashing directly laptop-nslu, tested any configuration (auto, 100 full duples, and so on), mac adress is not 00:00:00..
Jun 16 21:46:43 <mwester-laptop> Ok.  Can you telnet into redboot?
Jun 16 21:47:04 <filas> noup..
Jun 16 21:47:10 <filas> =(
Jun 16 21:48:17 <filas> trying, but nothing, can't catch moment
Jun 16 21:53:15 <mwester-laptop> Ok.  If you can, try to use the redboot commands to read data and if possible to send data -- if that works ok, then the network might not be the problem.
Jun 16 21:53:44 <mwester-laptop> Which leaves potential problems with the removal of the resistor as a possible source.
Jun 16 21:54:31 <osmeest> eno: I don't know if that's the source of my problem with the initrd
Jun 16 21:55:00 <filas> mwester-laptop: how can I do that (use the redboot commands to read data)?
Jun 16 21:56:33 <mwester-laptop> I don't recall what the NSLU2 redboot implementation has; try "help" and see if there's a command that dumps out the contents of a block or range of memory or flash, for example.
Jun 16 21:56:53 <mwester-laptop> (NSLU2 redboot is a bit unusual in some ways)
Jun 16 22:50:19 <rwhitby> ~ssen osmeest
Jun 16 22:50:21 <rwhitby> ~seen osmeest
Jun 16 22:50:25 <rwhitby> ~seen filas
Jun 16 22:50:42 <jbot> osmeest <n=olivier@70.7-247-81.adsl-dyn.isp.belgacom.be> was last seen on IRC in channel #nslu2-linux, 56m 10s ago, saying: 'eno: I don't know if that's the source of my problem with the initrd'.
Jun 16 22:50:43 <jbot> filas <i=filas@80.233.248.141> was last seen on IRC in channel #nslu2-linux, 55m 42s ago, saying: 'mwester-laptop: how can I do that (use the redboot commands to read data)?'.
Jun 16 23:13:24 <rwhitby> If anyone else sees osmeest around, tell him that I can help him out with Debian on nas100d.
Jun 16 23:13:37 <rwhitby> (but he needs a serial port first)
Jun 16 23:17:56 <CIA-8> 03bzhou * r6225 10optware/trunk/platforms/toolchain-gumstix1151.mk: gumstix: no builtin math
Jun 16 23:18:27 <CIA-8> 03bzhou * r6226 10optware/trunk/make/player.mk: player: in case NO_BUILTIN_MATH
Jun 16 23:22:24 <CIA-8> 03bzhou * r6227 10optware/trunk/make/player.mk: player: corrected a typo
Jun 17 01:37:01 <Dsbeerf> Hey someone know how to change this /dev/mtdblock0 on / type squashfs (ro) into read-write ?
Jun 17 01:42:45 <rwhitby> Dsbeerf: which firmware?
Jun 17 01:43:32 <Dsbeerf> a customized one
Jun 17 01:43:33 <rwhitby> squashfs is not normally writeable ...
Jun 17 01:43:43 <Dsbeerf> so no way to access it?
Jun 17 01:44:06 <rwhitby> not in a read-write way, unless you use some overlay technique (like mini_fo or unionfs)
Jun 17 01:44:22 <rwhitby> (openwrt on nslu2 uses that technique)
Jun 17 01:44:42 <rwhitby> what's the application that you're using the nslu2 with customized firmware for?
Jun 17 01:45:02 <Dsbeerf> a cpe/router :)
Jun 17 01:45:31 <Dsbeerf> i recompiled it from broadcom to arm
Jun 17 01:46:13 <rwhitby> looked at openwrt?
Jun 17 01:46:30 <Dsbeerf> not yet i will
Jun 17 01:46:44 <rwhitby> kamikaze 7.06 supports nslu2
Jun 17 01:47:28 <Dsbeerf> ok
Jun 17 02:07:47 <CIA-8> 03bzhou * r6228 10optware/trunk/platforms/packages-gumstix1151.mk: gumstix: promoted netatalk, unfs3
Jun 17 02:18:37 <CIA-8> 03osas * r6229 10optware/trunk/make/asterisk14-core-sounds-en-ulaw.mk: asterisk14-core-sounds-en-ulaw: 1.4.6 -> 1.4.7
Jun 17 02:19:04 <CIA-8> 03osas * r6230 10optware/trunk/make/asterisk14-core-sounds-en-gsm.mk: asterisk14-core-sounds-en-gsm: 1.4.6 -> 1.4.7
Jun 17 02:20:07 <CIA-8> 03osas * r6231 10optware/trunk/make/asterisk14-extra-sounds-en-gsm.mk: asterisk14-extra-sounds-en-gsm: 1.4.5 -> 1.4.6
Jun 17 02:20:25 <CIA-8> 03osas * r6232 10optware/trunk/make/asterisk14-extra-sounds-en-ulaw.mk: asterisk14-extra-sounds-en-ulaw: 1.4.5 -> 1.4.6
Jun 17 02:40:01 <CIA-8> 03osas * r6233 10optware/trunk/make/asterisk14.mk: asterisk14: 1.4.4svn-r67398 -> 1.4.5
**** ENDING LOGGING AT Sun Jun 17 02:59:56 2007