**** BEGIN LOGGING AT Thu Nov 15 02:59:57 2007 Nov 15 16:20:30 I'm starting a forum for NSLU2 users. Anyone interested in participating can /q me Nov 15 16:37:06 Hello Nov 15 16:37:15 Hi Varazir[NA] Nov 15 16:37:53 I can't install the recover software on my ubuntu system Nov 15 16:39:39 Varazir: Join #ubuntu for support. You can also try the forums (ubuntuforums.org) and/or the mailing lists. Nov 15 16:41:17 on the nslu2 webpage it say "sudo aptitude install upslug2" Nov 15 16:41:54 ubunto can't finde the pkg :( Nov 15 16:43:06 Varazir: Like I said. #ubuntu - Try sudo apt-cache search slug to see what shows up. Nov 15 16:43:07 still go to ubuntu support ? Nov 15 16:43:14 ok Nov 15 16:53:33 thanks Nov 15 18:54:47 Hmm.. the grey network-cabel thats is diliverd whit nslu2... thats a crossover cable right? Nov 15 18:59:06 if i have a router and puts my nslu2 in upgrade mode.. can i upgrade it over my network? Nov 15 19:50:54 digii: No, the grey cable delivered with the NSLU2 is a standard network cable. Nov 15 19:51:22 If you have a router, and put the NSLU2 in upgrade mode, you can upgrade it over the router. That works just fine. Nov 15 19:53:17 digii, FYI, you can still do a debian install from the image... Nov 15 19:53:37 As long as the router doesnt use 192.168.0.1 - or any other device for that matter Nov 15 20:45:26 Reedy_Boy why could it not use 192.168.0.1? Nov 15 20:45:42 As reboot/upgrade mode uses that IP.. Nov 15 20:45:49 u mean becouse bydefault nslu2 is on 192.168.1? Nov 15 20:46:08 192.168.1.77 isnt is that? Nov 15 20:46:11 its 1.77 by default Nov 15 20:46:18 No, thats just the IP for that Nov 15 20:46:39 redboot uses 192.168.0.1, so if something else is using it, the slug cant Nov 15 20:46:55 hmm :S Nov 15 20:47:06 but is i connect it straigt to my comp Nov 15 20:47:26 should the comp and nslu2 fix the ips by theree self? Nov 15 20:47:52 The NSLU2 in upgrade mode will use 192.168.0.1 you'll have to manually set the pc Nov 15 20:48:09 digii, http://www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBoot Nov 15 20:48:15 RedBoot will insist on being 192.168.0.1 for this window, regardless of what you've set the address of the normal Linux portion of your slug to be Nov 15 20:48:36 set the pc to anything on 192.168.0.x exept 192.168.0.1? Nov 15 20:48:42 yeah Nov 15 20:48:48 oh.. Nov 15 20:48:49 .2 is easy enough Nov 15 20:49:10 always thouge it was 192.168.1.77 or something Nov 15 20:49:25 thats the factory default ip Nov 15 20:49:25 becouse it was so by defualt Nov 15 20:49:28 ok Nov 15 20:49:32 i see =) Nov 15 20:49:55 =) Nov 15 20:50:12 But you can use the debian image to install debian again - I did after i worked out there was something with the drive Nov 15 20:50:36 digii: the boot firmware will use IP address 192.168.0.1 *always* -- as soon as the early boot is done, the software running will pick the *real* IP address, which is by default 192.168.1.77. Nov 15 20:51:02 cheers mwester :) Nov 15 20:51:17 So the NSLU2 has *two* IP addresses, and the 192.168.0.1 address cannot be changed, and is used only for a moment or two during the initial boot of the device. Nov 15 20:51:24 cheers Reedy_Boy Nov 15 20:51:36 aah =) Nov 15 20:51:42 thx =) Nov 15 20:51:48 didnt know that :P Nov 15 20:51:59 I remembered this fact when my unslung nslu2 couldnt find my debian one in upgrade mode Nov 15 20:52:02 had to do it via a switch Nov 15 20:52:23 Unfortunately, since you cannot disable nor can you change that 192.168.0.1 address, if you are using that IP range in your network, you may find that the NSLU2 (even with Linksys firmware) is somewhat disruptive... Nov 15 20:52:38 yea, im thinking of doing it via a switch to Nov 15 20:53:13 yea.. but i could always change the gateway adress in my network Nov 15 20:53:14 I just had my pc on the switch with my 2 nslu2's used upslug2 on the unslung one to reflash the other Nov 15 20:53:25 since its uses 0.1 Nov 15 20:54:11 i found it was just easier to use a switch Nov 15 20:54:22 i could change my router to something like 192.168.0.11 and nslu2 using 192.168.0.1 whould appear? right? Nov 15 20:54:22 5 minute job and done Nov 15 20:54:29 aye Nov 15 20:54:36 might have to restart it in upgrade mode again Nov 15 20:54:49 hehe yea :P but then i hafto find one :P and in my mess that would take hours :P Nov 15 20:55:00 lol Nov 15 20:55:09 yea :P but upgrade mode takes like 20 sec ;) Nov 15 20:56:33 yeah Nov 15 20:56:36 omgz 20 secs Nov 15 20:58:36 I had pong (well, my old basic version) running via mono on my debian nslu2 before it decided not to boot Nov 15 21:00:41 are u reaaaaally sure its takes 192.168.0.1 in upgrade mode :D Nov 15 21:01:03 yes... Nov 15 21:01:30 eveen if it was allready flashed whit debian? Nov 15 21:02:26 coz now my gateway is on 192.168.0.2 :S and still cant ping it or anything Nov 15 21:03:14 Are the LEDs blinking to indicate upgrade mode? Nov 15 21:03:54 yea, orange/green Nov 15 21:04:01 suppose the orange means red :p Nov 15 21:05:00 Ok, then just run the upslug2 program (or the windows upgrade tool, if that's what you use) to find it. It does not have enough "brains" at this point to respond in the normal TCP/IP means. Nov 15 21:05:47 u mean upslug2 -i Bin.file? Nov 15 21:05:49 You can't telnet to it, and I don't think it will respond to a ping. It's just listening for ethernet packets that would have the information to upgrade it, I don't even think that the upgrade protocol is TCP/IP. Nov 15 21:06:10 No, just run "upslug2" and it will tell you if it found a device in upgrade mode. Nov 15 21:06:24 nope Nov 15 21:06:29 noone there :o Nov 15 21:06:35 strange.. Nov 15 21:06:45 think i need to find that switch Nov 15 21:34:38 I hade to go ubuntus homepage and DL it from there :) Nov 15 21:39:38 http://packages.ubuntu.com/edgy/otherosfs/upslug2 **** ENDING LOGGING AT Fri Nov 16 02:59:58 2007