**** BEGIN LOGGING AT Sat Oct 31 02:59:57 2009
Oct 31 03:00:13 <mwester-laptop> Use the standard linksys way to reset the device to the default settings using the reset button - if that fails, then follow the instructions on the nslu2-linux wiki to use the reset button to enter upgrade mode, and reflash the linksys firmware.
Oct 31 03:06:16 <RWings19> ok, will try that
Oct 31 03:06:22 <RWings19> was hoping this POS would work right out of the box
Oct 31 03:07:39 <mwester-laptop> Heh.   A word of advice on used flashable devices -- never, never use them until you reset them and reflash the firmware.
Oct 31 03:08:22 <mwester-laptop> You'll never know what somebody may have done to the device, either by foolishness or maliciousness.
Oct 31 03:10:57 <RWings19> checking now - existing firmware was 23r63
Oct 31 03:11:00 <RWings19> reflashing with same
Oct 31 03:11:23 <RWings19> interesting that the upgrade utility would not even see the device until it was in upgrade mode
Oct 31 03:12:14 <mwester-laptop> Probably just means it wasn't running with the original firmware.  Most replacement firmware retains that 23r63 signature.
Oct 31 03:12:38 <RWings19> right... but doesn't explain why I couldn't see it on 192.168.1.77
Oct 31 03:12:45 <mwester-laptop> Frankly, I wouldn't use the original firmware - nor would anyone on this channel (which is the whole point of this channel, of course.
Oct 31 03:12:53 <mwester-laptop> The reason you didn't see it is
Oct 31 03:13:02 <RWings19> right - I am just trying to make sure the device works before I work on adding unslung
Oct 31 03:13:03 <mwester-laptop> that it wasn't listening on that address.
Oct 31 03:13:21 <RWings19> yeah but my router was not reporting the device's MAC address at all
Oct 31 03:13:30 <mwester-laptop> WHy would it?
Oct 31 03:13:39 <mwester-laptop> If the device was set with a static IP
Oct 31 03:13:50 <mwester-laptop> there's no reason for the router to care to log the MAC.
Oct 31 03:13:55 <RWings19> still - shouldn't the router tell me which devices are connected?
Oct 31 03:14:01 <mwester-laptop> Nope.
Oct 31 03:14:08 <RWings19> it told me my two laptops were connected and reported their MACs
Oct 31 03:14:16 <mwester-laptop> Most routers only report DHCP'd devices.
Oct 31 03:14:21 <mwester-laptop> They don't snoop the wire.
Oct 31 03:14:29 <RWings19> even with DDWRT?
Oct 31 03:14:58 <mwester-laptop> You *can* do it with ddwrt, but by default it doesn't put the ports in promiscuous mode -- way too much cpu required on a busy network.
Oct 31 03:15:07 <mwester-laptop> And to log all teh macs - that crazy.
Oct 31 03:15:39 <RWings19> ok, device has rebooted
Oct 31 03:15:46 <RWings19> single beep, two green lights
Oct 31 03:16:08 <RWings19> STILL no connection on .77
Oct 31 03:16:14 <mwester-laptop> Don't forget to do the reset -- reflashing the firmware doesn't reset it.
Oct 31 03:16:33 <mwester-laptop> it keeps things like the network settings in a part of the firmware that's untouched when you reflash.
Oct 31 03:16:42 <RWings19> help me out - is that the two-second reset button push?
Oct 31 03:16:55 <mwester-laptop> Dunno - you'll have to check linksys' website.
Oct 31 03:17:01 <mwester-laptop> It's running Linksys firmware now.
Oct 31 03:17:29 <RWings19> ugh
Oct 31 03:17:46 <RWings19> and I can't install unslung without an attached flash drive right?
Oct 31 03:18:02 <mwester-laptop> You can install it, but its relatively pointless.
Oct 31 03:18:14 <RWings19> i just want the damn slug to work
Oct 31 03:18:32 <mwester-laptop> So do I, but for me that means it must run SlugOS.
Oct 31 03:18:48 <mwester-laptop> For others, it just has to run LInksys' firmware.
Oct 31 03:19:18 <mwester-laptop> So I guess it depends on what you need it to do -- maybe it will work without external storage for your application.
Oct 31 03:19:39 <RWings19> my application will eventually be an attached 320GB drive
Oct 31 03:19:47 <RWings19> but I wanted to make sure I could set a static IP, etc.
Oct 31 03:20:04 <RWings19> so right now I just have the slug connected to the router, and that's it (nothing attached to the slug)
Oct 31 03:20:22 <mwester-laptop> Then were I you, I would flash the native Linksys firmware, reset the device following the Linksys docs, and use it the way Linksys wants me to use it.
Oct 31 03:20:46 <mwester-laptop> Since Unslung is just Linksys' firmware opened up, it won't work if the Linksys firmware won't work.
Oct 31 03:20:52 <RWings19> trying... still can't connect on .77
Oct 31 03:20:59 <mwester-laptop> Well, reset it already.
Oct 31 03:21:36 <mwester-laptop> And make sure that your network is on the 192.168.1.xxx subnet, of course.
Oct 31 03:22:00 <RWings19> yes, it is
Oct 31 03:22:17 <RWings19> have reset multiple times... nothing
Oct 31 03:22:21 <mwester-laptop> Or install the Linksys host software, which IIRC has some sort of utility to find the device and change its IP...
Oct 31 03:22:41 <RWings19> tried that - it found nothing
Oct 31 03:23:35 <mwester-laptop> Well, keep working on it - just make sure you are following the reset instructions you found on Linksys' site to the letter - that should do it.
Oct 31 03:24:25 <mwester-laptop> The only other possible solution is the last resort - that's resetting the sysconfig, which is not an easy process to do (but it's documented on the wiki, but not recommended unless it really really really is the last resort).
Oct 31 03:24:56 <RWings19> well that's where I'm headed...
Oct 31 03:24:59 <RWings19> reset did NOTHING
Oct 31 03:25:02 <mwester-laptop> So soon?
Oct 31 03:25:11 <RWings19> setup wizard can't even see the device on the network
Oct 31 03:25:25 <mwester-laptop> Either I'm in a time warp, or you haven't really tried very hard -- just being honest here.
Oct 31 03:25:26 <RWings19> the SerComm only saw it when it was in upgrade mode.
Oct 31 03:25:36 <mwester-laptop> RIght - so it's working fine.
Oct 31 03:25:44 <RWings19> what else do I need to try?  I've reflashed and reset - and still nothing.
Oct 31 03:25:45 <mwester-laptop> Therefore, it's just not on your network.
Oct 31 03:26:04 <RWings19> how is it not on the network if it's plugged in to the same router as this computer I'm using?
Oct 31 03:26:40 <mwester-laptop> There's a difference between the physical network and the subnet.
Oct 31 03:27:26 <mwester-laptop> When you configured the router, you gave it an IP address range it was allowed to use (or if you didn't, it's using its default).
Oct 31 03:27:35 <RWings19> correct
Oct 31 03:27:43 <mwester-laptop> If the default NSLU2 address is not in that range, then it will never be seen.
Oct 31 03:27:50 <RWings19> interesting
Oct 31 03:27:53 <RWings19> maybe that's it
Oct 31 03:28:00 <RWings19> i think i started at 100 and went up
Oct 31 03:28:20 <mwester-laptop> No, thats the dhcp range.
Oct 31 03:29:30 <RWings19> any idea where to fnd that setting in the DDWRT firmware?
Oct 31 03:29:35 <RWings19> (looking right now myself)
Oct 31 03:29:45 <mwester-laptop> yeah.
Oct 31 03:29:46 <mwester-laptop> google.
Oct 31 03:29:49 <mwester-laptop> :p
Oct 31 03:31:13 <RWings19> ugh
Oct 31 03:32:05 <RWings19> can't seem to find it
Oct 31 03:34:34 <mwester-laptop> I think you need to spend a bit of time to dig into IP addresses, netmasks, and subnets -- that background will help you find the settings on your router so that you can see if its configured correctly, and fix it if not.
Oct 31 03:35:13 <mwester-laptop> I think wikipedia has better descriptions of how that all works that I can type up! :D
Oct 31 03:35:28 <mwester-laptop> er, than I can type up.
Oct 31 03:35:46 <RWings19_> were you typing something to me?  i missed it - got disconnected
Oct 31 03:36:11 <mwester-laptop> I think you need to spend a bit of time to dig into IP addresses, netmasks, and subnets -- that background will help you find the settings on your router so that you can see if its configured correctly, and fix it if not.
Oct 31 03:36:25 <mwester-laptop> I think wikipedia has better descriptions of how that all works than I can type up! :D
Oct 31 03:36:40 <RWings19_> well... all my other machines connect on 192.168.1.x
Oct 31 03:36:46 <RWings19_> even when directly connected
Oct 31 03:37:00 <mwester-laptop> Then it's probably ok.
Oct 31 03:37:09 <mwester-laptop> You're just not getting it reset then.
Oct 31 03:37:12 <RWings19_> but the dhcp setup I have starts at 110, and I have a couple of devices that get static IPs
Oct 31 03:39:09 <mwester-laptop> anyway, gotta run - good luck.  If you could flash it with the host utility, then clearly the hardware is all working, it's just a matter of getting it listening on the network.  And don't forget to check your host system to make sure it doesn't have a firewall configuration issue, or suchlike (try another system).
Oct 31 03:39:12 <mwester-laptop> later.
Oct 31 03:42:28 <RWings19_> would it matter if my WAN settings have a different subnet?
Oct 31 03:48:03 <RWings19__> anyone else have any ideas here?
Oct 31 04:05:32 <RWings19> still not working, anyone else feel like they could help?
Oct 31 04:39:07 <RWings19> need some help if anyone is awake
**** ENDING LOGGING AT Sat Oct 31 11:39:06 2009

**** BEGIN LOGGING AT Sat Oct 31 11:39:30 2009
Oct 31 15:08:22 <messerting> I've copied my pendrive to a new bigger pendrive. I've used the same layout for the partitions. When I boot the new pendrive, it seems it is not used.
Oct 31 15:08:34 <messerting> Can I simply try "turnup memstick -i /dev/sda1"?
Oct 31 15:09:03 <messerting> Or will that possibly make it hard to go back to the old pendrive if it fails?
Oct 31 15:50:48 <mwester-laptop> messerting: SlugOS mounts by UUID, and your new partitions have new UUIDs.  Just do the turnup memstick /dev/sda1 (without the -i) to keep everything as-is and reset the UUID.
Oct 31 16:26:47 <messerting> mwester-laptop: thanks!
Oct 31 16:27:05 <messerting> I just tried, but turnup says I'm missing one of four things
Oct 31 16:27:23 <messerting>   1) A directory /mnt.  2) A command line interpreter program in /bin/sh.  3) The program chroot in /sbin or /usr/sbin.  4) The program init in /sbin, /etc or /bin.
Oct 31 16:27:41 <messerting> But, as far as I can see, I've got all of those
Oct 31 16:28:04 <messerting> Now I've tried "mount /dev/sda1 /mnt/buf"
Oct 31 16:28:51 <messerting> I've got:
Oct 31 16:28:52 <messerting> drwxr-xr-x    5 root     root         4096 Oct 12 20:32 /mnt/buf/mnt/
Oct 31 16:29:22 <messerting> lrwxrwxrwx    1 root     root            7 Apr 16  2009 /mnt/buf/bin/sh -> busybox
Oct 31 16:29:53 <messerting> lrwxrwxrwx    1 root     root           16 Apr 16  2009 /mnt/buf/usr/sbin/chroot -> chroot.coreutils
Oct 31 16:30:01 <messerting> (and the destination of those links)
Oct 31 16:30:25 <messerting> lrwxrwxrwx    1 root     root           19 Apr 16  2009 /mnt/buf/sbin/init -> /sbin/init.sysvinit
Oct 31 16:30:44 <messerting> But - hm, maybe I need to set the partition bootable in fdisk...
Oct 31 16:30:50 <messerting> will try that
Oct 31 16:37:43 <messerting> hm, bootable flag didn't help, turnup is still complaining
Oct 31 17:57:52 <mwester-laptop> Send an email to the nslu2-linux mailing list outlining the problem, and then manually fix things up.  Boot up to flash, then edit the /linuxrc file, and replace the UUID that's there with the UUID for the new sda1 partition.
Oct 31 21:30:59 <schme> Hello. I'm trying to get my scanner to work here with saned and whatsorts. sane-find-scanner tells me it's not there. Yet testlibusb spots it just fine.
Oct 31 21:31:12 <schme> Anyone got any pointers on where to look?
Oct 31 21:33:54 <schme> scanner is supported, and works fine on my desktop computer
Oct 31 23:11:38 <mwester-laptop> schme: I can't help you, AFAIK.  But you might improve your luck if you mention what hardware and firmware you are using, the version of the firmware, and what package feeds you got the sane packages from.
Oct 31 23:17:47 <schme> mwester-laptop: Hi. Not sure about hardware.. Is a NSLU2 (obviously), and using slugos5.   feeds  http://ipkg.nslu2-linux.org/feeds/slugosbe/cross/5.3-beta/ 
Oct 31 23:18:15 <schme> turns out libusb from there is horribly broken. installing one from http://ipkg.nslu2-linux.org/feeds/optware/slugos5be/cross/unstable/ solved it
Oct 31 23:18:27 <mwester-laptop> Yes, libusb is broken on 5.3
Oct 31 23:18:29 <schme> not even lsusb worked with libusb from that there opkg install
Oct 31 23:18:39 <schme> aha
Oct 31 23:18:52 <schme> well it's all working now after an ipkg install :)
Oct 31 23:19:05 <mwester-laptop> I sent an email out about the fixed version in the unstable feeds.  Good to know it runs on 5.3 (I only tested on 5.4-alpha).
Oct 31 23:19:37 <schme> trying to configure me jabberd now.. a bit not wanting to work :)
Oct 31 23:19:40 <schme> but oh well. ya it works.
Oct 31 23:19:42 <schme> \o/
Oct 31 23:19:50 <schme> (libusb that is)
Nov 01 01:07:20 <Woolly> hey guys
Nov 01 01:12:24 <Woolly> I just finished the debian installer on my slug, but when it rebooted, there was no ethernet connectivity. The LED on my USB stick is on, as is the third light down on the device itself. Could this be a missing intel ethernet driver?
Nov 01 01:12:43 <Woolly> and does anyone have any advice on fixing this issue?
Nov 01 01:39:25 <Woolly> anyone?
Nov 01 01:39:59 <mwester-laptop> The debian folks don't seem to hang out here.
Nov 01 01:40:06 <mwester-laptop> You might try the debian-arm channel
Nov 01 01:40:13 <mwester-laptop> (listed in the wiki)
Nov 01 01:40:15 <Woolly> mwester-laptop: thanks :) I'll give that a try
**** ENDING LOGGING AT Sun Nov 01 02:59:56 2009