**** BEGIN LOGGING AT Sat May 12 02:59:56 2007
May 12 09:55:13 <oddbjoh> hi, is there anyone that could tell me if the psu of the nlsu2 is positive or negative center?
May 12 09:55:31 <oddbjoh> ...I seem to have misplaced my psu
May 12 10:02:59 <quack100> let me see if I can check without powering it off!
May 12 10:03:20 <oddbjoh> quack100: thx, I believe it is positive center
May 12 10:03:30 <oddbjoh> the wiki says so, but nice to get it confirmed
May 12 10:06:08 <quack100> PSU says positive centre, 5.0V DC 2.0A
May 12 10:06:23 <oddbjoh> quack100: thx a lot
May 12 10:07:04 <quack100> there are 2 model numbers on the psu
May 12 10:07:27 <quack100> one says AD 5/2A
May 12 10:09:06 <quack100> other says M1-10S05 (that's emm one dash one zero esss zero five)
May 12 10:09:22 <oddbjoh> oki
May 12 10:09:29 * oddbjoh wanders off to get a new psu
May 12 10:09:52 <quack100> no prob - glad to be able to help
May 12 13:01:37 <kestrel> morning, flashed my new nslu2 and all i get is a yellow ready/status, green ethernet and no light on hd2(120gdrive attached). 
May 12 13:01:46 <kestrel> no ping no ssh
May 12 13:02:01 <kestrel> ideas or suggestion?
May 12 13:02:06 <oddbjoh> kestrel: flashed again?
May 12 13:02:32 <kestrel> no, how do I do that if i cna't connect?
May 12 13:03:06 <oddbjoh> http://www.cyrius.com/debian/nslu2/install.html <-- look at the part on upslug
May 12 13:04:40 * kestrel flashing again - thanks oddbjoh
May 12 13:04:54 <oddbjoh> kestrel: np, good luck
May 12 13:21:30 <kestrel> reflash worked - waiting patiently for reboot - holding breath
May 12 13:22:00 <oddbjoh> well, if it reflashes it cannot be totally dead ;-)
May 12 13:25:41 <barnseenio> good luck!
May 12 13:47:45 <__mindless__> hi
May 12 13:48:37 <__mindless__> i have a question: where in redboot source code are the flash partitions defined? I downloaded its source code btu couldn't find it
May 12 13:51:10 <jrb_> prob in the EEPROM
May 12 13:51:30 <__mindless__> yes, well i saw the partitions defined on sysconf region in flash
May 12 13:51:39 <__mindless__> but someone had to write them there 
May 12 13:52:32 <__mindless__> i thought it was redboot but can't find where in source code does that thing
May 12 13:54:36 <jrb_> bootloader shouldn't have anything todo with partition layout?
May 12 13:55:25 <__mindless__> agree, but kernel's configured to search for redboot partition (in FIS region) and then create MTD devices according to this partition layout
May 12 13:56:13 <__mindless__> i can't find who did create my partition layout, if it was debian installer, redboot, apex....
May 12 13:58:08 <jrb_> prob the installer image
May 12 13:58:30 <jrb_> flashing the EEPROM would just write bytes after bytes to the storage medium
May 12 13:59:02 <jrb_> if such a data pattern (as defined by the installer) resulted in a partition layout when interpreted by the installer, that yr source
May 12 13:59:39 <__mindless__> so do you think that debian installer was the one who created my partition layout?
May 12 13:59:53 <jrb_> on your flash then yer
May 12 14:00:30 <jrb_> the installer installs APEX's to chainload a larger kernel (redboot has a kernel image size limit)
May 12 14:00:47 <__mindless__> yes
May 12 14:01:11 <__mindless__> redboot runs apex and then apex load the kernel image which can be larger than 1MB and then boots it from ram
May 12 14:01:12 <mwester> For the flash, the partition layout is defined by the procedure that constructs the flash image that you initially download to the SLUG when you reflash same.
May 12 14:01:46 <mwester> There are no partition tables in the Redboot implementation on the SLUG -- it's all in the image itself
May 12 14:01:49 <__mindless__> oh i see.. so the initial firmware i loaded into flash (nslu2.bin or something like this) defined the layout?
May 12 14:01:53 <mwester> Yes.
May 12 14:02:41 <__mindless__> then i should see somewhere in redboot source code where the partition layout is defiend to be written in FIS region.. shouldn't i?
May 12 14:03:08 <mwester> The debian image does not replace the NSLU2's redboot.
May 12 14:03:12 <__mindless__> sorry, in the nslu2 firmware source code
May 12 14:03:20 <mwester> THe NSLU2's redboot doesn't do FIS stuff at all.
May 12 14:03:33 <__mindless__> aha
May 12 14:04:05 <mwester> I don't know where in the source you would find the equiv. of the FIS -- something sets it up to "fake it", and everything from there on in sees a normal FIS layout.
May 12 14:04:47 <mwester> These questions are probably better addressed on one of the Debian/ARM channels on IRC, the developers who know this stuff usually don't monitor this channel!
May 12 14:04:54 <__mindless__> so if i understood you, the image i flashed first, contained the partition layout (which was prepared to use a second stage loader btw)
May 12 14:05:07 <mwester> Sort of...
May 12 14:05:22 <__mindless__> oh i wasn't actually sure if this was a debian related answer
May 12 14:05:34 <mwester> The image contains what appears to the NSLU2 redboot to be a 1MB kernel and "everything else".
May 12 14:05:44 <mwester> When redboot boots,
May 12 14:05:46 <__mindless__> ok thanks for help i'm now having a look at the image
May 12 14:05:52 <mwester> what it actually starts is APEX.
May 12 14:05:56 <__mindless__> i see
May 12 14:06:31 <__mindless__> but the partition layout is prepared for a 2nd stage loader because it's got the followign partitions: "RedBoot" "Loader" (this one's where APEX is written) "Kernel" ...
May 12 14:06:32 <mwester> APEX knows how to read the kernel, crossing the 1MB boundary (there's a marker in the flash image at that location that needs to be skipped over)
May 12 14:06:57 <__mindless__> so it seems that the nslu2 image is prepared for apex
May 12 14:07:04 <mwester> It boots the kernel, and I think (*just think, don't know for sure*) that the kernel NSLU2 code knows how to figure out the FIS.
May 12 14:07:28 <mwester> Yes, apex is built by the debian build process, and added to the firmware image.
May 12 14:07:30 <__mindless__> yes, the kernel knows how to read the FIS to create MTD partitions
May 12 14:07:50 <mwester> Right - on the NSLU2 I think the kernel also builds the "fake" FIS.
May 12 14:07:59 <mwester> Since it didn't get one from the bootloader.
May 12 14:08:57 <__mindless__> mm that's the point, and that's why i looked into kernel sources to see if the fis is built 'onthefly'
May 12 14:09:01 <__mindless__> but couldn't find it
May 12 14:11:40 <__mindless__> mwester you're right, i'm watching di-nslu2.bin with an hexeditor and there it is the partition layout
May 12 14:11:57 <__mindless__> so definitively the debian isntaller is the one creating it
May 12 14:25:19 <kestrel> oddbjoh: same result - ping reports no route to host - ready/status light yellow ethernet green 
May 12 14:44:43 <oddbjoh> kestrel: same happens when using original linksys firmware?
May 12 14:50:18 <kestrel> oddbjoh: no - used web interface to flash first time -was able to set it up and format harddrive - gave it ip - worked great
May 12 14:50:52 <oddbjoh> kestrel: and what are you flashing with now?
May 12 14:51:18 <kestrel> sudo upslug2 --device ra0 -i di-nslu2.bin
May 12 14:51:34 <oddbjoh> kestrel: ah, which debian image are you using?
May 12 14:52:21 <oddbjoh> the one with the proprietary drivercode or the one without?
May 12 14:53:00 <kestrel>  "an unofficial image which consists of the official Debian image plus the proprietary IXP4xx microcode."
May 12 14:53:17 <kestrel> From the http://www.cyrius.com/debian/nslu2/install.html
May 12 14:53:24 <oddbjoh> hmmm, strange, well, I am also new to this, so I am not sure what the problem might be, sry bout that
May 12 14:53:58 <Naib> kestrel, the upslug2 command you posted only valid (like that) for ralink wireless cards ;)
May 12 14:54:17 <Naib> if the default device is eth0 the --device part can be dropped
May 12 14:54:21 <kestrel> true - the flash works fine
May 12 14:54:36 <kestrel> I have a ralink card
May 12 14:54:53 <Naib> not saying it won't ;) (I got a ralink card and do the same), just incase someone middlemouses that command and gets some errors
May 12 14:55:51 <kestrel> Is there a way to flash back to factory default and have a real redo?
May 12 14:56:26 <oddbjoh> kestrel: yes, use the upslug2-tool with the original linksys firmware
May 12 14:56:32 <Naib> just flash the original image
May 12 14:57:32 <kestrel> thanks - where do I find the "original image" - was I supposed to save it - oh no!
May 12 14:57:42 <oddbjoh> www.linksys.com ;-)
May 12 14:58:00 <kestrel> duh on my part>
May 12 14:58:10 <kestrel> thanks
May 12 15:30:38 <oddbjoh> kestrel: btw, I just started the installer and it does use dhcp
May 12 15:31:04 <oddbjoh> kestrel: so if you assumed .77 you might want to look around for another ip in the dhcp range as well
May 12 15:32:09 <kestrel> oddbjoh: must be problem with nic - original firmware works great - remembered static ip setting - there may be the problem - resetting to dhcp
May 12 15:32:48 <oddbjoh> kestrel: what I said, it used dhcp here even though I had static ip set
May 12 15:33:37 <kestrel> i looked at dhcp leases and there were none
May 12 15:59:06 <kestrel> oddbjoh: progress only with your help thanks
May 12 15:59:15 <kestrel> firmware upgrade fine
May 12 15:59:19 <kestrel> ping ok
May 12 15:59:35 <kestrel> ssh key problem now
May 12 15:59:46 <Naib> kestrel, what prob with ssh key?
May 12 16:01:24 <oddbjoh> kestrel: wipe the old key
May 12 16:01:35 <oddbjoh> ?
May 12 16:03:03 <kestrel> NSLU2 tells me what the fingerprint is but says "RSA host key for 192.168.0.7 has changed and you have requested strict checking."
May 12 16:03:38 <oddbjoh> kestrel: look in your .ssh/known_hosts file
May 12 16:03:57 <oddbjoh> ...and find the one for that ip
May 12 16:10:05 <kestrel> confused - nothing human readable in  .ssh/known_hosts
May 12 16:11:25 <oddbjoh> kestrel: well, I wiped the last line since I knew that the nlsu var added last
May 12 16:12:04 <oddbjoh> kestrel: if you do not remember when you added the .7 on your network I would google for known_hosts ;-)
May 12 16:17:21 <kestrel> i noticed 'Offending key in /home/will/.ssh/known_hosts:6' and removed line 6 and it worked! HAW HOO!
May 12 16:18:11 <kestrel> oddbjoh: finally now off to the install thanks for your encourgement - first i have honey do's to do
May 12 16:22:57 * kestrel wanders off for awhile...
May 12 21:00:37 <tymm> hi, why i can't connect the nslu after flashing it with the debian firmware from slug-firmware.net ?
May 12 21:03:19 <Reedy_Boy> How long have you waited?
May 12 21:03:31 <Reedy_Boy> Is it on a static IP/Are you connecting to the correct IP?
May 12 21:03:37 <Reedy_Boy> How are you trying to connect to it?
May 12 21:10:06 <tymm> Reedy_Boy: till it beeped, i think i connect to the right one (192.168.1.77), via ssh
May 12 21:10:25 <Reedy_Boy> Was it on .77 before you flashed it?
May 12 21:10:59 <tymm> whats .77? i turned it in the upgrade modus
May 12 21:11:47 <Reedy_Boy> Im meaning, was it on the .77 ip before the upgrade
May 12 21:12:07 <pierrelux> Reedy_Boy: you can use nmap to find its IP
May 12 21:12:30 <Reedy_Boy> Thanks, but its not me looking for its ip
May 12 21:12:31 <Reedy_Boy> :)
May 12 21:12:36 <tymm> pierrelux: with nmap it doesnt find the nslu
May 12 21:13:15 <tymm> Reedy_Boy: i don't know, i bought it from a friend which also used it with debian
May 12 21:13:20 <pierrelux> how come ?
May 12 21:13:30 <Reedy_Boy> How did you reflash it?
May 12 21:14:31 <tymm> Reedy_Boy: with unslug
May 12 21:14:41 <Reedy_Boy> upslug you mean?
May 12 21:14:55 <tymm> yes :)
May 12 21:15:11 <tymm> upslug2 with gentoo
May 12 21:15:17 <Reedy_Boy> Does it respond to a ping?
May 12 21:15:24 <tymm> no
May 12 21:15:40 <Reedy_Boy> hmmm so it sounds like its not at that IP
May 12 21:16:02 <Reedy_Boy> Have you got a router or something that assigns DHCP addresses? If so, have you looked if its taken a DHCP address
May 12 21:17:23 <tymm> yes, i tried it with my router, but it didnt get an ip through dhcp
May 12 21:20:39 <tymm> pierrelux: how can i find the slug through nmap?
May 12 21:30:20 <oddbjoh> tymm: do a ipconfig renew on your laptop (or ifconfig) and look at the ip's around that range
May 12 21:31:11 <oddbjoh> ...that did it for me
May 12 21:35:11 <tymm> oddbjoh: sry i dont understand (bad english), what do you mean with "and look at the ip's around that range" ?
May 12 21:36:05 <oddbjoh> if you renew your ip and get 192.168.1.23 try .21, .22, .24 and so forth
May 12 21:36:45 <tymm> okay
May 12 21:42:57 <pierrelux> tymm: you just go with nmap 192.168.101.0/24 if your local network is 192.168.101.0
May 12 21:43:29 <tymm> okay i just found it! my friend told my which ip he used and now i find it
May 13 00:24:41 * kestrel quietly sneeks back.
May 13 00:51:31 <osas> http://www.nslu2-linux.org seems to be down
**** ENDING LOGGING AT Sun May 13 02:59:59 2007