|
Post by sp00bking on Mar 29, 2007 23:32:08 GMT 7
|
|
|
Post by dbridges on Mar 30, 2007 5:30:09 GMT 7
I'll never be able to figure out why people unnecessarily take a soldering iron to their expensive electronics 1. What firmware version did you start with? 2. Did you ever have debian installed and working? 3. Have you been playing near the redboot? 4. What are the lights doing? 5. What terminal software on what OS are you using? 6. Isolation test is the key. Crossover if you have it. Switch if you dont. Disconnected from your router if need be. Static ip addresses on everything. If you've managed to corrupt your redboot partition then you've killed your n2100. You should probably be getting something from the serial port even if the redboot isn't functioning which make me think that there is something wrong with with your wiring or soldering. There are two solutions for the serial port because there are two versions of the n2100. One with the serial port riser and one without.
|
|
|
Post by sp00bking on Mar 30, 2007 13:11:57 GMT 7
I'll never be able to figure out why people unnecessarily take a soldering iron to their expensive electronics 1. What firmware version did you start with? 2. Did you ever have debian installed and working? 3. Have you been playing near the redboot? 4. What are the lights doing? 5. What terminal software on what OS are you using? 6. Isolation test is the key. Crossover if you have it. Switch if you dont. Disconnected from your router if need be. Static ip addresses on everything. If you've managed to corrupt your redboot partition then you've killed your n2100. You should probably be getting something from the serial port even if the redboot isn't functioning which make me think that there is something wrong with with your wiring or soldering. There are two solutions for the serial port because there are two versions of the n2100. One with the serial port riser and one without. --- 1.> 2.1.05 2. > NO,the installer was running but when i was ready to partion drives i was stupid and had a power out. 3.> = NO,i havent had any communication yet 4.> = The unit is powering up and the fan spinning up.after some time the fan goes down in speed and theres only light in the power button. 5. > Hyperterminal on Windows 6:> I tried DHCP and it seemed to pickup a ip but telnetting into it didnt work.Static ip and serial port worked neither. I tried measuring between my soldering point but it seems ok. Ill check my wiring now that you have clarified which how that i should make my serial connections.Thanx for making that clear! Maybe i should unsolder the pinheads.It even says so in one guide "DONT solder".I must be retarded!! Why is it sooo bad that i soldered?!?
|
|
|
Post by dbridges on Mar 30, 2007 13:51:13 GMT 7
I wrote that guide I figured it out the hard way It's not that bad that you solder it's just that it's unnecessary and a hot iron or splash of molten solder could do some real damage. And if you get the wiring wrong you have to melt the solder to change it Anyway back to the problem at hand. From what you're saying the redboot should be intact which is good. Have a read of this page www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBootIt's a different device but it highlights some of the potential issues with telnet access to redboot. Basically you have to be real quick!!! If you pursue the serial port side of things be sure that your serial port isn't disabled in your bios or device manager. The serial port method works but you have to get it right and it can be easy to mix it up. Once you're in i may be able to put together a tarball that you can unpack into the /app area on the flash. What state are your disks in? Have you tried the reset button or the connection wizard? Depending on how far you got through the installer you may find that the n2100 is relatively intact and just needs a little help.
|
|
|
Post by sp00bking on Mar 30, 2007 13:57:58 GMT 7
I wrote that guide I figured it out the hard way It's not that bad that you solder it's just that it's unnecessary and a hot iron or splash of molten solder could do some real damage. And if you get the wiring wrong you have to melt the solder to change it Anyway back to the problem at hand. From what you're saying the redboot should be intact which is good. Have a read of this page www.nslu2-linux.org/wiki/HowTo/TelnetIntoRedBootIt's a different device but it highlights some of the potential issues with telnet access to redboot. Basically you have to be real quick!!! If you pursue the serial port side of things be sure that your serial port isn't disabled in your bios or device manager. The serial port method works but you have to get it right and it can be easy to mix it up. Once you're in i may be able to put together a tarball that you can unpack into the /app area on the flash. What state are your disks in? Have you tried the reset button or the connection wizard? Depending on how far you got through the installer you may find that the n2100 is relatively intact and just needs a little help. If i ever get into redboot ill try to flash with a official firmware and then try the debian installer afterwards. Kinda a n00b so i have to read the guides to get a picture.Unpacking tarball stuff is kinda "talking jibberish" to me.HMM Disk is clean and newly formated. Tried the reset button but that changed nothing. I hope its intact but lets see about that. I have soldered the pinheads of and ill follow the guide 101% this time.DUH!
|
|
|
Post by sp00bking on Apr 9, 2007 22:30:34 GMT 7
From what you're saying the redboot should be intact which is good. Have you tried the reset button or the connection wizard? Depending on how far you got through the installer you may find that the n2100 is relatively intact and just needs a little help. Hiya Still there but im outtha luck... Cannot connect to the device via telnet.Kinda doubting if redboot still is there..!? Tried resetting and tried putting the device on a dhcp net but nooo luck. Seriel just doesnt work for me either.Im really doubting that the device is still alive.. 8(
|
|
|
Post by dbridges on Apr 10, 2007 5:09:24 GMT 7
d**n!!! At this stage there's nothing left to try. You may be able to find someone who could re-write the flash but the cost would be high.
|
|
ab56
New Member
Posts: 2
|
Post by ab56 on Apr 15, 2007 16:23:54 GMT 7
1.> 2.1.05 2. > NO,the installer was running but when i was ready to partion drives i was stupid and had a power out. 3.> = NO,i havent had any communication yet 4.> = The unit is powering up and the fan spinning up.after some time the fan goes down in speed and theres only light in the power button. 5. > Hyperterminal on Windows 6:> I tried DHCP and it seemed to pickup a ip but telnetting into it didnt work.Static ip and serial port worked neither. I tried measuring between my soldering point but it seems ok. Ill check my wiring now that you have clarified which how that i should make my serial connections.Thanx for making that clear! Maybe i should unsolder the pinheads.It even says so in one guide "DONT solder".I must be retarded!! Why is it sooo bad that i soldered?!? Your NAS is definitely still alive, no doubt about that. You just need to get acces through the serial port. The problem ist that these recovery ports don't use handshaking and this makes it sometimes very difficult to get a working connection more so at a speed of 115200 bps. So set your hyperterminal to 115200 bps, 8, N, 1, no Handshake, VT52 and try to connect. Start with a freshly booted PC, start Hyperterminal, start the connection in Hyperterminal, switch your N2100 on and as soon as you see some characters in the terminal window press 'CRTL-C' several times. The default timeout to interrupt the boot process is only 1 second which isn't very helpful in this situation. I had to repeat this process many, many times untill it worked and the 'STRG-C' interrupted the boot loader. Then I immediately set with fconfig the timeout to 5 seconds, the local IP and server IP and from this point on I connected always through telnet which works absolutely reliable. As soon as you have access to the boot loader RedBoot you can get per TFTP all necessary images 'load -r [filename] -b [base address]' from a TFTP server, flash them for example per 'fis create ramdisk', 'fis create kernel' and 'fis create user' as necessary and your NAS should work again as expected.
|
|
|
Post by sp00bking on Apr 18, 2007 15:20:08 GMT 7
Your NAS is definitely still alive, no doubt about that. Thank you for the positive spirit.. Why are you sooo sure that its still alive!? Guess ill try a couple of times more...
|
|
ab56
New Member
Posts: 2
|
Post by ab56 on Apr 18, 2007 23:20:41 GMT 7
Your NAS is definitely still alive, no doubt about that. Thank you for the positive spirit.. Why are you sooo sure that its still alive!? Guess ill try a couple of times more... The Busy LED would blink all the time.
|
|