NSLU2-Linux
view · edit · print · history

HowTo.ResetSysConf History

Hide minor edits - Show changes to markup

September 13, 2008, at 09:00 AM by anonymous -- corrected typo
Changed lines 3-4 from:

Note that you must flash the Linksys 2.3R63 vendor firmware immediately afterwards and the re-enter your network settings for correct operation.

to:

Note that you must flash the Linksys 2.3R63 vendor firmware immediately afterwards and then re-enter your network settings for correct operation.

June 08, 2008, at 02:11 AM by ElementZero -- Fixing Typo\'s
Changed lines 21-22 from:

If you reset the box, the SerComm utility might not work as the it can't detect the IP. Instead of using the EraseAll utility though (a.k.a. dangerous), just follow the steps to Telnet insto the box again and then just type "upgrade" and hit enter. Then the sercomm utility should be able to connect to the drive again. - ElementZero?

to:

If you reset the box, the SerComm utility might not work as the it can't detect the IP. Instead of using the EraseAll utility though (a.k.a. dangerous), just follow the steps to Telnet into the box again and then just type "upgrade" and hit enter. Then the sercomm utility should be able to connect to the drive again. - ElementZero?

June 08, 2008, at 02:10 AM by ElementZero -- Added note on how to get back to sercomm instead of using EraseAll
Changed lines 21-22 from:
to:

If you reset the box, the SerComm utility might not work as the it can't detect the IP. Instead of using the EraseAll utility though (a.k.a. dangerous), just follow the steps to Telnet insto the box again and then just type "upgrade" and hit enter. Then the sercomm utility should be able to connect to the drive again. - ElementZero?

May 13, 2008, at 11:33 AM by BenMcDui --
Changed lines 20-21 from:

Note at this point, Sercomm did not work for me - it did not catch the sllug. I had to use EraseAll by Linksys but then I was OK. BenMcDui 20080513.

to:

Note at this point, Sercomm did not work for me - it did not catch the Slug. I had to use EraseAll by Linksys but then I was OK. BenMcDui 20080513.

May 13, 2008, at 11:32 AM by BenMcDui -- Added a Note
Added lines 20-21:

Note at this point, Sercomm did not work for me - it did not catch the sllug. I had to use EraseAll by Linksys but then I was OK. BenMcDui 20080513.

March 29, 2008, at 01:45 PM by Sander van Geest -- Added optimisation and clarification of procedure
Changed lines 18-23 from:

Now you are ready to flash it with Linksys 2.3R63 vendor firmware using either Sercomm's Win32 tool or UpSlug2

After the flashing is complete, the NSLU2 will reboot and the Linksys firmware will recreate the SysConf area. Remember that all the settings will be lost and the IP address will now reset to 192.168.1.77.

Once you have accessed the vendor firmware on 192.168.1.77, it's probably a good idea to reset the settings to default by clicking "Restore Default Config" at the bottom of the Administraion -> System page. Enter all your network settings (make sure you remember to enter the gateway and DNS addresses), then you can go ahead and UseTheResetButtonToEnterUpgradeMode to flash new firmware.

to:

Now you are ready to flash it with Linksys 2.3R63 vendor or uNSLUng 6.10 beta firmware using either Sercomm's Win32 tool or UpSlug2

After the flashing is complete, the NSLU2 will reboot and the firmware will recreate the SysConf area. Remember that all the settings will be lost and the IP address will now reset to 192.168.1.77.

Once you have accessed the firmware on 192.168.1.77, it's probably a good idea to reset the settings to default by clicking "Restore Default Config" at the bottom of the Administration -> System page. Wait untill the NSLU2 has rebooted. Enter all your network settings (make sure you remember to enter the gateway and DNS addresses), then you can go ahead and UseTheResetButtonToEnterUpgradeMode to flash any other firmware.

July 16, 2007, at 10:00 PM by pedxing --
Added lines 23-24:

If you would like to modify the sysconf information, refer to ChangeConfigBin.

July 12, 2007, at 05:23 PM by pedxing -- One more thing
Changed line 22 from:

Once you have accessed the vendor firmware on 192.168.1.77, and entered all your network settings (make sure you remember to enter the gateway and DNS addresses), then you can go ahead and UseTheResetButtonToEnterUpgradeMode to flash new firmware.

to:

Once you have accessed the vendor firmware on 192.168.1.77, it's probably a good idea to reset the settings to default by clicking "Restore Default Config" at the bottom of the Administraion -> System page. Enter all your network settings (make sure you remember to enter the gateway and DNS addresses), then you can go ahead and UseTheResetButtonToEnterUpgradeMode to flash new firmware.

June 05, 2007, at 08:27 AM by rwhitby --
Changed lines 18-19 from:

Now you are ready to flash it with Linksys 2.3R63 vendor firmware using either Sercomm's Win32 tool or UpSlug2

to:

Now you are ready to flash it with Linksys 2.3R63 vendor firmware using either Sercomm's Win32 tool or UpSlug2

June 05, 2007, at 08:25 AM by rwhitby --
Changed line 22 from:

Once you have accessed the vendor firmware on 192.168.1.77, and entered all your network settings (make sure you remember to enter the gateway and DNS addresses), then you can go ahead and use the UseTheResetButtonToEnterUpgradeMode method to flash new firmware.

to:

Once you have accessed the vendor firmware on 192.168.1.77, and entered all your network settings (make sure you remember to enter the gateway and DNS addresses), then you can go ahead and UseTheResetButtonToEnterUpgradeMode to flash new firmware.

June 05, 2007, at 08:24 AM by rwhitby --
Changed lines 11-12 from:

Once you have done that, type upgrade to put the NSLU2 into upgrade mode, and then flash it with Linksys 2.3R63 vendor firmware using either Sercomm's Win32 tool or UpSlug2.

to:

Once you have done that, type upgrade to put the NSLU2 into upgrade mode.

Added lines 18-19:

Now you are ready to flash it with Linksys 2.3R63 vendor firmware using either Sercomm's Win32 tool or UpSlug2

June 05, 2007, at 08:23 AM by rwhitby --
Changed lines 11-12 from:

Once you have done that, type upgrade to put the NSLU2 into upgrade mode, and then flash it with Linksys 2.3R63 vendor firmware using either Sercomm's Win32 tool or UpSlug2?.

to:

Once you have done that, type upgrade to put the NSLU2 into upgrade mode, and then flash it with Linksys 2.3R63 vendor firmware using either Sercomm's Win32 tool or UpSlug2.

June 05, 2007, at 08:23 AM by rwhitby --
Changed lines 11-12 from:

Once you have done that, type upgrade to put the NSLU2 into upgrade mode, and then flash it with Linksys 2.3R63 vendor firmware using either [SercommFirmwareUpdater|Sercomm's Win32 tool] or UpSlug2?.

to:

Once you have done that, type upgrade to put the NSLU2 into upgrade mode, and then flash it with Linksys 2.3R63 vendor firmware using either Sercomm's Win32 tool or UpSlug2?.

June 05, 2007, at 08:22 AM by rwhitby --
Changed lines 11-12 from:

Once you have done that, type upgrade to put the NSLU2 into upgrade mode, and then flash it with Linksys 2.3R63 vendor firmware.

to:

Once you have done that, type upgrade to put the NSLU2 into upgrade mode, and then flash it with Linksys 2.3R63 vendor firmware using either [SercommFirmwareUpdater|Sercomm's Win32 tool] or UpSlug2?.

Changed lines 16-17 from:

RedBoot> upgrade @@

to:

RedBoot> upgrade @@

June 05, 2007, at 08:21 AM by rwhitby -- Took out all the incorrect information, and put in a recipe that is guaranteed to always work.
Added lines 3-4:

Note that you must flash the Linksys 2.3R63 vendor firmware immediately afterwards and the re-enter your network settings for correct operation.

Changed lines 11-12 from:

Reboot and the NSLU2 will recreate the SysConf area. Remember that all the settings will be lost and the IP address will now reset to 192.168.1.77.

to:

Once you have done that, type upgrade to put the NSLU2 into upgrade mode, and then flash it with Linksys 2.3R63 vendor firmware.

Changed lines 16-101 from:

RedBoot> reset @@

NOTE: ResetSysConf should be done WITHOUT any disk attached at boot.

Additional Information:

I tried to flash a brand new NSLU2 with the original firmware to 3.18beta and get the problem: "Fail to get samba information". I tried to recreate the SysConf area 15 times, but it didn' work. After a lot of researching I found a german help description: http://www.nslu2-info.de/showthread.php?t=71&page=2&pp=10&highlight=samba

Translation:

  1. Start NSLU2 in the RedBoot mode (see above)
  2. Give the NSLU2 RedBoot command upgrade - This puts the NSLU2 into "upgrade mode"
  3. Update the firmware with the SerComm Upgrade Utility to desired firmware. This method does not work with firmware 2.3R29 , use 2.3R25 instead. See [1]
  4. Give the NSLU2 RedBoot command reset

(Comment by Jon B: in my experience this step is incorrect - the slug will restart immediately after the sercomm upgrade is complete and therefore you will not enter this reset command. While the upgrade is in progress, get ready to intercept this restart to go into redboot mode again..)

  1. Start NSLU2 in the RedBoot mode (again)
  2. Give the NSLU2 RedBoot command fis erase -f 0x50040000 -l 0x20000
  3. Give the NSLU2 RedBoot command reset

(24-03-2005 DNR) Just to add to above

I had to do it this way as well (using [http://www.nslu2-linux.org/wiki/Main/SercommFirmwareUpdater]) as just going into redboot and doing

fis erase -f 0x50040000 -l 0x20000

didn't work. For the record I followed the same proceedure as above but used 2.3R29 and it worked.

(27-03-2005 TDJ) This can also be completed from the web interface. Reflash the linksys firmware go to Administration / system and click the reset to default configuration.

(07-05-2005 DL) I too got it to work using 2.3R29. One thing I would add is to make sure you don't let the slug boot up properly after the upgrade but before you have done the sysconf reset. The box will reboot itself immediately after the upgrade with SerComm - make sure to catch it and get it into redboot, do the sysconf reset, then reboot again. If you let it boot all the way through between the upgrade and the sysconf reset, you may face 'failed to get samba info' message again like me.

(2005-06-05 Hans Persson) I also got this to work using 2.3R29. When I tried the "upgrade" command in RedBoot, my slug hung. I tried a couple of times with the same result. I went on anyway, skipping that step, and everything worked as it should.

(2006-04-23 JH) Same problem with the V2.3R63, I too got it to work with the 2.3R29. However, I did it in reverse sequence.

a. Redboot and delete the configuration file.

b. Reboot into upgrade mode using the paperclip method http://www.nslu2-linux.org/wiki/HowTo/UseTheResetButtonToEnterUpgradeMode.

c. Flash with 2.3R29

d. Reboot - allowing the new 2.3R29 to create the config file.

This way avoided any timing issues getting the redboot prompt and creating a new bad config file from the old flash.

June 2006 - comment by Jon B:

My slug (which was running Unslung 6.8beta, v2.3R63) developed the annoying "Error: fail to get samba information" error message ( see FailSambaInformation) within the linksys web interface. I had tried re-flashing this firmware again using the web interface but another error message then appeared (something like 'bad file name') after flashing, and the the problem remained.

Even using Redboot to do fis erase -f 0x50040000 -l 0x20000 as above didn't fix the problem, however the translated german method also shown above DID fix the problem.

I would however note that the slug does restart itself automatically as soon as the Sercomm utility has finished installing (unlike the instructions suggest) so you do need to be ready to get back into redboot again (as commented by DL above). I have highlighted these important sections above in bold.

---

Dec 2006 - comment by Andrew F:

I've had this same problem (Failed to get samba info). I followed the above plan (Redboot, erase config, upgrade from redboot, reboot) and it worked fine. FYI I used the VBS script from a Windows box to get to redboot - worked fine

---

Jan 2007 - comment by Lars L:

I had the same problem. Now i avoided all timing issues by doing the following:

  1. Enter redboot
  2. Delete configuration file
  3. Enter upgrade mode by typing "upgrade"
  4. Flash new firmware (i.e. directly to unslung)

Horray, the slug works like a charm!

Feb 2007 comment by Geir: "Fail to get samba info" when operating the nslu2 web interface. Tried the procedure above, upgrading, resetting, both with version 2.3R63, and latest Unslung-6.8. Also tried reverse sequence of resetting, upgrading. So now I am out looking for 2.3R29, or even 2.3R25, but where can I find previous original linksys firmware releases? Btw, I am using upslug for upgrade, would Sercomm be a better choice?

Older NSLU2 firmware can be found at the Linksys FTP site: ftp://ftp.linksys.com/pub/network/

to:

RedBoot> upgrade @@
After the flashing is complete, the NSLU2 will reboot and the Linksys firmware will recreate the SysConf area. Remember that all the settings will be lost and the IP address will now reset to 192.168.1.77.

Once you have accessed the vendor firmware on 192.168.1.77, and entered all your network settings (make sure you remember to enter the gateway and DNS addresses), then you can go ahead and use the UseTheResetButtonToEnterUpgradeMode method to flash new firmware.

March 05, 2007, at 10:09 PM by Spyrus -- Added link to old Linksys firmware
Changed lines 97-99 from:

So now I am out looking for 2.3R29, or even 2.3R25, but where can I find previous original linksys firmware releases? Btw, I am using upslug for upgrade, would Sercomm be a better choice?

to:

So now I am out looking for 2.3R29, or even 2.3R25, but where can I find previous original linksys firmware releases? Btw, I am using upslug for upgrade, would Sercomm be a better choice?

Older NSLU2 firmware can be found at the Linksys FTP site: ftp://ftp.linksys.com/pub/network/

February 03, 2007, at 10:53 AM by Geir --
Changed lines 39-40 from:

I had to do it this way as well (using [SerCom?>http://www.nslu2-linux.org/wiki/Main/SercommFirmwareUpdater]) as just going into redboot and doing

to:

I had to do it this way as well (using [http://www.nslu2-linux.org/wiki/Main/SercommFirmwareUpdater]) as just going into redboot and doing

February 03, 2007, at 10:52 AM by Geir --
Changed lines 39-40 from:

I had to do it this way as well (using SerCom?) as just going into redboot and doing

to:

I had to do it this way as well (using [SerCom?>http://www.nslu2-linux.org/wiki/Main/SercommFirmwareUpdater]) as just going into redboot and doing

February 03, 2007, at 10:39 AM by Geir --
Changed line 97 from:

So now I am out looking for 2.3R29, or even 2.3R25, but where can I find previous original linksys firmware releases?

to:

So now I am out looking for 2.3R29, or even 2.3R25, but where can I find previous original linksys firmware releases? Btw, I am using upslug for upgrade, would Sercomm be a better choice?

February 03, 2007, at 10:38 AM by Geir --
Changed line 97 from:

So now I am out looking for 2.3R29, or even 2.3R25

to:

So now I am out looking for 2.3R29, or even 2.3R25, but where can I find previous original linksys firmware releases?

February 03, 2007, at 10:33 AM by Geir --
Changed lines 96-97 from:

"Fail to get samba info" when operating the nslu2 web interface. Tried the procedure above, upgrading, resetting, both with version 2.3R63, and latest Unslung-6.8. Also tried reverse sequence of resetting, upgrading

to:

"Fail to get samba info" when operating the nslu2 web interface. Tried the procedure above, upgrading, resetting, both with version 2.3R63, and latest Unslung-6.8. Also tried reverse sequence of resetting, upgrading. So now I am out looking for 2.3R29, or even 2.3R25

February 03, 2007, at 10:26 AM by Geir --
Changed lines 89-92 from:
  1. a) Enter redboot
  2. b) Delete configuration file
  3. c) Enter upgrade mode by typing "upgrade"
  4. d) Flash new firmware (i.e. directly to unslung)
to:
  1. Enter redboot
  2. Delete configuration file
  3. Enter upgrade mode by typing "upgrade"
  4. Flash new firmware (i.e. directly to unslung)
Changed lines 95-97 from:

Feb 2007 comment by Geir W:

"Fail to get samba info" when operating the nslu2 web interface. Tried the procedure above, upgrading, resetting, both with version 2.3R63, and latest Unslung-6.8. Also tried resetting, upgrading

to:

Feb 2007 comment by Geir:

"Fail to get samba info" when operating the nslu2 web interface. Tried the procedure above, upgrading, resetting, both with version 2.3R63, and latest Unslung-6.8. Also tried reverse sequence of resetting, upgrading

February 03, 2007, at 10:23 AM by Geir W -- Fail to get samba info
Changed lines 64-67 from:

c. Flash with 2.3R9

d. Reboot - allowing the new 2.3R9 to create the config file.

to:

c. Flash with 2.3R29

d. Reboot - allowing the new 2.3R29 to create the config file.

Changed lines 89-93 from:

a) Enter redboot b) Delete configuration file c) Enter upgrade mode by typing "upgrade" d) Flash new firmware (i.e. directly to unslung) Horray, the slug works like a charm!

to:
  1. a) Enter redboot
  2. b) Delete configuration file
  3. c) Enter upgrade mode by typing "upgrade"
  4. d) Flash new firmware (i.e. directly to unslung)

Horray, the slug works like a charm!

Feb 2007 comment by Geir W:

"Fail to get samba info" when operating the nslu2 web interface. Tried the procedure above, upgrading, resetting, both with version 2.3R63, and latest Unslung-6.8. Also tried resetting, upgrading

January 17, 2007, at 04:56 PM by Lars Lydersen --
Changed lines 82-93 from:

I've had this same problem (Failed to get samba info). I followed the above plan (Redboot, erase config, upgrade from redboot, reboot) and it worked fine. FYI I used the VBS script from a Windows box to get to redboot - worked fine

to:

I've had this same problem (Failed to get samba info). I followed the above plan (Redboot, erase config, upgrade from redboot, reboot) and it worked fine. FYI I used the VBS script from a Windows box to get to redboot - worked fine

---

Jan 2007 - comment by Lars L:

I had the same problem. Now i avoided all timing issues by doing the following: a) Enter redboot b) Delete configuration file c) Enter upgrade mode by typing "upgrade" d) Flash new firmware (i.e. directly to unslung) Horray, the slug works like a charm!

December 27, 2006, at 10:20 PM by AndrewF -- Added my experience of removing \"Failed to get Samba info\"
Added lines 78-82:

---

Dec 2006 - comment by Andrew F:

I've had this same problem (Failed to get samba info). I followed the above plan (Redboot, erase config, upgrade from redboot, reboot) and it worked fine. FYI I used the VBS script from a Windows box to get to redboot - worked fine

June 14, 2006, at 02:31 PM by Jon B --
Changed lines 26-28 from:
  1. Start NSLU2 in the RedBoot mode (see above)
  2. Give the NSLU2 RedBoot command upgrade - This puts the NSLU2 into "upgrade mode"
  3. Update the firmware with the SerComm Upgrade Utility to desired firmware. This method does not work with firmware 2.3R29 , use 2.3R25 instead. See [1]
to:
  1. Start NSLU2 in the RedBoot mode (see above)
  2. Give the NSLU2 RedBoot command upgrade - This puts the NSLU2 into "upgrade mode"
  3. Update the firmware with the SerComm Upgrade Utility to desired firmware. This method does not work with firmware 2.3R29 , use 2.3R25 instead. See [1]
Changed lines 30-34 from:
  1. Start NSLU2 in the RedBoot mode (again)
  2. Give the NSLU2 RedBoot command fis erase -f 0x50040000 -l 0x20000
  3. Give the NSLU2 RedBoot command reset
to:

(Comment by Jon B: in my experience this step is incorrect - the slug will restart immediately after the sercomm upgrade is complete and therefore you will not enter this reset command. While the upgrade is in progress, get ready to intercept this restart to go into redboot mode again..)

  1. Start NSLU2 in the RedBoot mode (again)
  2. Give the NSLU2 RedBoot command fis erase -f 0x50040000 -l 0x20000
  3. Give the NSLU2 RedBoot command reset
Changed lines 51-52 from:

One thing I would add is to make sure you don't let the slug boot up properly after the upgrade but before you have done the sysconf reset. The box will reboot itself immediately after the upgrade with SerComm - make sure to catch it and get it into redboot, do the sysconf reset, then reboot again. If you let it boot all the way through between the upgrade and the sysconf reset, you may face 'failed to get samba info' message again like me.

to:

One thing I would add is to make sure you don't let the slug boot up properly after the upgrade but before you have done the sysconf reset. The box will reboot itself immediately after the upgrade with SerComm - make sure to catch it and get it into redboot, do the sysconf reset, then reboot again. If you let it boot all the way through between the upgrade and the sysconf reset, you may face 'failed to get samba info' message again like me.

Changed lines 68-77 from:

This way avoided any timing issues getting the redboot prompt and creating a new bad config file from the old flash.

to:

This way avoided any timing issues getting the redboot prompt and creating a new bad config file from the old flash.

June 2006 - comment by Jon B:

My slug (which was running Unslung 6.8beta, v2.3R63) developed the annoying "Error: fail to get samba information" error message ( see FailSambaInformation) within the linksys web interface. I had tried re-flashing this firmware again using the web interface but another error message then appeared (something like 'bad file name') after flashing, and the the problem remained.

Even using Redboot to do fis erase -f 0x50040000 -l 0x20000 as above didn't fix the problem, however the translated german method also shown above DID fix the problem.

I would however note that the slug does restart itself automatically as soon as the Sercomm utility has finished installing (unlike the instructions suggest) so you do need to be ready to get back into redboot again (as commented by DL above). I have highlighted these important sections above in bold.

April 23, 2006, at 09:11 PM by thekitehunter -- Alternative
Changed lines 46-47 from:

This can also be completed from the web interface. Reflash the linksys firmware go to Administraion / system and click the reset to default configuration.

to:

This can also be completed from the web interface. Reflash the linksys firmware go to Administration / system and click the reset to default configuration.

Added lines 54-67:

(2006-04-23 JH) Same problem with the V2.3R63, I too got it to work with the 2.3R29. However, I did it in reverse sequence.

a. Redboot and delete the configuration file.

b. Reboot into upgrade mode using the paperclip method http://www.nslu2-linux.org/wiki/HowTo/UseTheResetButtonToEnterUpgradeMode.

c. Flash with 2.3R9

d. Reboot - allowing the new 2.3R9 to create the config file.

This way avoided any timing issues getting the redboot prompt and creating a new bad config file from the old flash.

June 05, 2005, at 02:48 PM by Hans Persson --
Changed line 53 from:

I also got thiss to work using 2.3R29. When I tried the "upgrade" command in RedBoot, my slug hung. I tried a coupld of times with the same result. I went on anyway, skipping that step, and everything worked as is should.

to:

I also got this to work using 2.3R29. When I tried the "upgrade" command in RedBoot, my slug hung. I tried a couple of times with the same result. I went on anyway, skipping that step, and everything worked as it should.

June 05, 2005, at 02:47 PM by Hans Persson -- Another success report, slightly different
Changed lines 50-53 from:

One thing I would add is to make sure you don't let the slug boot up properly after the upgrade but before you have done the sysconf reset. The box will reboot itself immediately after the upgrade with SerComm - make sure to catch it and get it into redboot, do the sysconf reset, then reboot again. If you let it boot all the way through between the upgrade and the sysconf reset, you may face 'failed to get samba info' message again like me

to:

One thing I would add is to make sure you don't let the slug boot up properly after the upgrade but before you have done the sysconf reset. The box will reboot itself immediately after the upgrade with SerComm - make sure to catch it and get it into redboot, do the sysconf reset, then reboot again. If you let it boot all the way through between the upgrade and the sysconf reset, you may face 'failed to get samba info' message again like me.

(2005-06-05 Hans Persson) I also got thiss to work using 2.3R29. When I tried the "upgrade" command in RedBoot, my slug hung. I tried a coupld of times with the same result. I went on anyway, skipping that step, and everything worked as is should.

May 07, 2005, at 11:08 AM by Dave Licence -- update
Added lines 47-50:

(07-05-2005 DL) I too got it to work using 2.3R29. One thing I would add is to make sure you don't let the slug boot up properly after the upgrade but before you have done the sysconf reset. The box will reboot itself immediately after the upgrade with SerComm - make sure to catch it and get it into redboot, do the sysconf reset, then reboot again. If you let it boot all the way through between the upgrade and the sysconf reset, you may face 'failed to get samba info' message again like me

March 27, 2005, at 06:42 PM by Tim Jordan --
Added lines 45-46:

(27-03-2005 TDJ) This can also be completed from the web interface. Reflash the linksys firmware go to Administraion / system and click the reset to default configuration.

March 24, 2005, at 08:40 PM by Dave Redfern --
Changed lines 35-37 from:

To add to above (24-03-2005 DNR)

to:

(24-03-2005 DNR) Just to add to above

March 24, 2005, at 08:37 PM by Dave Redfern --
Changed line 35 from:

Note 24-03-2005

to:

To add to above (24-03-2005 DNR)

March 24, 2005, at 08:36 PM by Dave Redfern --
Changed lines 35-36 from:

Note 24-03-2005 I had to do it this way as well as just going into redboot and doing

to:

Note 24-03-2005

I had to do it this way as well (using SerCom?) as just going into redboot and doing

Changed lines 40-41 from:

didn't work. For the record I followed the same proceedure as above but used 2.3R29 and it worked.

to:

didn't work. For the record I followed the same proceedure as above but used 2.3R29 and it worked.

March 24, 2005, at 08:34 PM by Dave Redfern --
Changed lines 32-41 from:
  1. Give the NSLU2 RedBoot command reset
to:
  1. Give the NSLU2 RedBoot command reset

Note 24-03-2005 I had to do it this way as well as just going into redboot and doing

fis erase -f 0x50040000 -l 0x20000

didn't work. For the record I followed the same proceedure as above but used 2.3R29 and it worked.

February 26, 2005, at 09:19 AM by chrta --
Changed line 28 from:
  1. Update the firmware with the SerComm Upgrade Utility to desired firmware. See RecoverFromABadFlash
to:
  1. Update the firmware with the SerComm Upgrade Utility to desired firmware. This method does not work with firmware 2.3R29 , use 2.3R25 instead. See RecoverFromABadFlash
February 25, 2005, at 02:01 AM by ByronT --
Changed lines 11-12 from:

@@Example:
RedBoot> fis erase -f 0x50040000 -l 0x20000 \\

to:

Example:
@@RedBoot> fis erase -f 0x50040000 -l 0x20000 \\

Changed lines 22-31 from:

http://www.nslu2-info.de/showthread.php?t=71&page=2&pp=10&highlight=samba

Translation:
1. Start NSLU2 in the RedBoot mode (see above)
2. NSLU2 with the command upgrade switched to the "upgrade mode"
3. Updated the firmware with the tool "upgrade_207_XP.exe" to NSLU2_V23R29.bin (original linksys firmware)
4. reset
5. Start NSLU2 in the RedBoot mode
6. fis erase -f 0x50040000 -l 0x20000
7. reset

to:

http://www.nslu2-info.de/showthread.php?t=71&page=2&pp=10&highlight=samba

Translation:

  1. Start NSLU2 in the RedBoot mode (see above)
  2. Give the NSLU2 RedBoot command upgrade - This puts the NSLU2 into "upgrade mode"
  3. Update the firmware with the SerComm Upgrade Utility to desired firmware. See RecoverFromABadFlash
  4. Give the NSLU2 RedBoot command reset
  5. Start NSLU2 in the RedBoot mode (again)
  6. Give the NSLU2 RedBoot command fis erase -f 0x50040000 -l 0x20000
  7. Give the NSLU2 RedBoot command reset
February 24, 2005, at 11:33 PM by wm --
Changed lines 16-31 from:

NOTE: ResetSysConf should be done WITHOUT any disk attached at boot.

to:

NOTE: ResetSysConf should be done WITHOUT any disk attached at boot.

Additional Information:

I tried to flash a brand new NSLU2 with the original firmware to 3.18beta and get the problem: "Fail to get samba information". I tried to recreate the SysConf area 15 times, but it didn' work. After a lot of researching I found a german help description: http://www.nslu2-info.de/showthread.php?t=71&page=2&pp=10&highlight=samba

Translation:
1. Start NSLU2 in the RedBoot mode (see above)
2. NSLU2 with the command upgrade switched to the "upgrade mode"
3. Updated the firmware with the tool "upgrade_207_XP.exe" to NSLU2_V23R29.bin (original linksys firmware)
4. reset
5. Start NSLU2 in the RedBoot mode
6. fis erase -f 0x50040000 -l 0x20000
7. reset

February 19, 2005, at 02:00 AM by ByronT --
Changed line 16 from:

NOTE: ResetSysConf should be done WITHOUT any disk attached.

to:

NOTE: ResetSysConf should be done WITHOUT any disk attached at boot.

February 19, 2005, at 01:59 AM by ByronT --
Added lines 15-16:

NOTE: ResetSysConf should be done WITHOUT any disk attached.

December 31, 2004, at 01:05 PM by tjyang --
Changed lines 9-14 from:

Reboot and the NSLU2 will recreate the SysConf area. Remember that all the settings will be lost and the IP address will now reset to 192.168.1.77.

to:

Reboot and the NSLU2 will recreate the SysConf area. Remember that all the settings will be lost and the IP address will now reset to 192.168.1.77.

Example:
RedBoot> fis erase -f 0x50040000 -l 0x20000
... Erase from 0x50040000-0x50060000: .
RedBoot> reset
\\

October 11, 2004, at 12:28 AM by tman --
Changed line 9 from:

Reboot and the NSLU2 will recreate the SysConf area. Remember that all the settings will be lost and the IP address will now reset to 192.168.1.177.

to:

Reboot and the NSLU2 will recreate the SysConf area. Remember that all the settings will be lost and the IP address will now reset to 192.168.1.77.

October 10, 2004, at 11:45 PM by sonicmctails --
Changed line 9 from:

Reboot and the NSLU2 will recreate the SysConf area. Remember that all the settings will be lost and the IP address will now reset to 192.168.1.77.

to:

Reboot and the NSLU2 will recreate the SysConf area. Remember that all the settings will be lost and the IP address will now reset to 192.168.1.177.

October 10, 2004, at 01:57 AM by tman --
Changed line 1 from:

You can force the NSLU2 to recreate the Sysconf by erasing it from RedBoot.

to:

You can force the NSLU2 to recreate the SysConf area by erasing it from RedBoot.

Changed line 9 from:

Reboot and the NSLU2 will recreate the Sysconf. Remember that the IP address will now reset to 192.168.1.77 and all other settings will be lost.

to:

Reboot and the NSLU2 will recreate the SysConf area. Remember that all the settings will be lost and the IP address will now reset to 192.168.1.77.

October 09, 2004, at 07:30 PM by tman --
Changed line 5 from:

fis erase -f 0x50040000 -l 0x20000

to:

fis erase -f 0x50040000 -l 0x20000

October 09, 2004, at 05:15 PM by tman --
Changed lines 1-9 from:

Describe ResetSysconf? here.

to:

You can force the NSLU2 to recreate the Sysconf by erasing it from RedBoot.

Follow the instructions to TelnetIntoRedBoot and then type the following in:

fis erase -f 0x50040000 -l 0x20000

Make sure you type it in exactly as you may damage other parts if you make a mistake.

Reboot and the NSLU2 will recreate the Sysconf. Remember that the IP address will now reset to 192.168.1.77 and all other settings will be lost.

Page last modified on September 13, 2008, at 09:00 AM