plugout.net

Hello, my first post.

I don't have access to a Windows box.

After building clunc and a lot of trial and error, it is finally working (turns out that it will only listen on the gateway interface, "-d" and "-m" switches notwithstanding).

Anyway, before taking the plunge and installing fvdw firmware, I would like to experiment with the external or standalone kenels included with the Windows SL installer.

(I have a tftp server ready.) What would be the UBoot command line arguments to load either one of them?

Thank you.

[SOLVED]

It was actually easier than I thought.

For anyone who may be interested, this worked for me (YMMV):

Make sure that the "UIMAGE-395-NWSP2CL-179-standalone" image is in your "/tftpboot' directory.

Once clunc brings up the u-boot prompt, load the standalone image:

[code]Marvell>> tftpboot 800000 UIMAGE-395-NWSP2CL-179-standalone[/code]

After the image loads, boot the CloudBox:

[code]Marvell>> bootm 0x800000[/code]

After it boots, you can telnet to the leased address (or 192.168.0/1.252) as root with "giveit2me" as the password.

Now that I've gotten this far, have to figure out how to install the firmware. Read a couple of scripts that may do the trick -- but that would be for a different thread.

Hi Auroro

the commands are almost ok, I use these

Code: Select all

Marvell>> tftpboot 0x800000 UIMAGE-395-NWSP2CL-179-standalone

and then

Code: Select all

Marvell>> bootm

when the standalone kernel is loaded and you have access via telnet you can use tftp to upload the firmware installer script as present in the fvw-sl console package (fvdw-sl-installer.sh)
I assume you have it the tftp directory used by the pc running the tftp server
In the telnet client on the nas running the standalone kernel use this command to upload the fvdw-sl-installer script

Code: Select all

tftp -r fvdw-sl-installer.sh -l fvdw-sl-installer -g ip-pc

(replace ip-pc by actual ip address of the the pc running the tftp server)

make it executable

Code: Select all

chmod 755 fvdw-sl-installer

start the installer

Code: Select all

/fvdw-sl-installer ip-pc

(replace ip-pc by actual ip address of the the pc running the tftp server)
Answer the questions in the dialog boxes, do not make a back up of lacie firmware, pretend that you have a nwsp2
Of course the firmware must be present in your tftp folder on the pc running the tftp server in a subfolder with name nwsp2/ (just like in fvdw-sl console)
When the firmware installer is finished with issues you can reboot your cloudbox and the firmware should come up. After that use the web interface of the fvdw-sl firmware to install latest firmware upgrade package for cloudbox.

Good day and thank you, Fvdw.

I was able to install it with some difficulty (would probably not recommend it to a Linux newbie).

The script worked but the "atftpd" server did not cooperate fully, especially when it came to downloading the image file because of its large size. Every time it tried to get it and couldn't, the script aborted with an unknown error message and would have to be restarted from the beginning.

After the third or fourth time it happened, I checked the syslog on the server and found messages from "atftpd" complaining about "BLKSIZE too big." Increasing the octet size on the tftp client with the "-b" option did not help. Compressing the image file on the server, decompressing it on the NAS, and finishing the installation manually did.

The NAS is now working fine with the fvdw-sl 15.3 firmware. It's like night and day when compared to the native LaCie firmware.

The installation script is a gem because it is thorough yet simple and, I'm sure, gets the job done most of the time. Although I understand it is not supposed to be an interactive script, it would be nice if, when invoked manually, it could restart from where it left off rather than from the beginning. It would also be nice if it would install the latest version of the firmware instead of an older version requiring an update right afterwards.

I have some questions and comments about the operation and features of the NAS with the new firmware. However, I'll save them for a different thread later on today (if I have time) or some other time during the week.

Hi Auroro

glad to hear you got it working. :thumbup

The problem you mention with tftp server is probably because you a version that is not able to handle bigger files.
This problem also occurs when using the tftp client in u-boot. So this is a server setting or capability issue.