idirect os Problem

You may want to consider RMA'ing that unit.

RMA means send it to iDIrect for repair.  

So, you do have the zImage for your software version?

What software version are you using?

Provide me the exact command line strings you are using once you start TFTP on the client (assuming that you have copied the zImage file to the desktop of your client prior to start TFTP).

Thanks

See my PM.

thank you Sir

Hello:
We have the same kind of fail with iDirect X3 Evolution Modem, can someone send us list of commands to solve this problem.
We try with recovery procedure but present some address problems.
Thanks in advance.

My e_mail: cpcharry@hotmail.com

It appears as if you have more than just the Linux image corrupt, I had the same problem recently. You have successfully created a doorstop or you could have it repaired at great expense.

Recovering RootFS.

To copy RootFS from the worker iDirect. For this purpose:

1. To be connected to the worker iDirect through the console and on LAN.

2. To download program WinSPC.

3. To be connected by the program to iDirect, having specified in Host Name – the modem ip-address, User – root, Password – iDirect.

4. File RootFS to save parts on a local disk of the computer.

4.1 In window TelNet in a command line Linux to make a team:
dd if=/dev/mtd2 bs=5M count=1 skip=0 of=/tmp/rImage0
As a result of performance of this command in a folder /tmp of the modem there will be a file with a name rImage0 which will contain the first 5Mb file RootFS. The size of a piece is set in parameter bs. If memory of the modem doesn't suffice, it is possible to save a piece of the smaller size, for example 2Mb, having specified parameter bs=2M.

4.2 Using program WinSPC, copy the saved piece from the folder /tmp of the modem to your computer.

4.3 Repeat actions 4.1 and 4.2, changing parameter skip until all file will be transferred. The parameter skip specifies, how many blocks in the size specified in parameter bs, is passed for copying of the next piece. As change a name of the file containing the next piece.
dd if=/dev/mtd2 bs=5M count=1 skip=1 of=/tmp/rImage1
At the subsequent actions:
… skip=2 of=/tmp/rImage2
…skip=3 of=/tmp/rImage3
…skip=4 of=/tmp/rImage4
…skip=5 of=/tmp/rImage5
…skip=6 of=/tmp/rImage6

4.4 After performance of all actions on a computer disk should be seven files with names rImage0 – rImage7. It also is an image of file RootFS.

To write down RootFS in defective iDirect. For this purpose:

1. To be connected to defective iDirect via the console and TelNet.

2. To stoploading iDirect at a stage of a command line RedBoot, having pressed a blank at the moment of its occurrence.

3. To start the program iSite. To start from it TFTP-server – File-TFTP, in the appeared window to enter the path to the image RootFS with the kept pieces rImage0 – rImage6.

4. In window TelNet in a command line RedBoot to execute commands:
Redboot> fis unlock RootFS
Redboot> fis erase –f 0x50160000 –l 0x1e80000

5. To transfer pieces of file RootFS from a disk of the computer to the modem:

5.1 In a command line RedBoot to execute commands:
Redboot> load –v –r –b 0x1600000 rImage0
Redboot> fis write –b 0x1600000 –f 0x50160000 –l 0x500000

5.2 To repeat actions 5.1, changing the name of file and parameter–f:
Redboot> load –v –r –b 0x1600000 rImage1
Redboot> fis write –b 0x1600000 –f 0x50660000 –l 0x500000
.. rImage2 .. –f 0x50b60000
.. rImage3 .. –f 0x51060000
.. rImage4 .. –f 0x51560000
.. rImage5 .. –f 0x51a60000
.. rImage6 .. –f 0x51f60000

5.3 As a result of performance of these actions in the modem the file RootFS will be written down and the device will renew the work.