lacie 5 big network v.1 please support for fvdw

[totorweb]

thank you :woohoo

i will try with the trial version and mdadm !

I'll post here the results.

[totorweb]

I have tried to load the UIMAGE-26394-5BIG1-9-STANDALONE-TRIAL using the u-boot.
ip is 192.168.0.252 (my pc/tftpserver is 192.168.0.12)

Code: Select all

setenv ipaddr ${ipaddr}
setenv serverip ${serverip}
tftpboot 0x800000 UIMAGE-26394-5BIG1-9-STANDALONE-TRIAL
setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/
bootm  0x800000


the kernel boots

Code: Select all

tftpboot 0x800000 UIMAGE-26394-5BIG1-9-STANDALONE-TRIAL
Using egiga0 device
TFTP from server 192.168.0.12; our IP address is 192.168.0.252
Filename 'UIMAGE-26394-5BIG1-9-STANDALONE-TRIAL'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########################
done
Bytes transferred = 3128220 (2fbb9c hex)

the cmd windows stay with the message

Code: Select all

Marvell>> bootm  0x800000
bootm  0x800000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.39.4
   Created:      2013-08-29  19:24:18 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3128156 Bytes =  3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK

i'am unable to ping 192.168.0.252 or telnet 192.168.0.252:23.

Did i do something wrong ?

[fvdw]

no so to see not, :scratch

So far tatae only reported that the normal kernel was running, could be that this standalone nr 9 still has an issue, I will compile today a standalone from the last kernel we tried.

[taetae]

then that I remember were we to version 14 and we had to make sure to switch to 15 where you said there was a possibility of multidisk, correct?

[taetae]

totorweb the problem is the loading??

[fvdw]

yes I think that nr 9 was still not good enough
anyhow attached a new version based on kernl 20 that is running on tatae system

Unpack the zip arcive and put it in the tftp folder of the fvdw-sl console
To load you can use the fvdw-sl console action "load standalone kernel" answer yes on the question if you have a nwsp2, 5big2...
I added a string in the standalone kernel name that will let the console believe that it is a kernel for the supported devices.

@tatae maybe you can test this one as well

[taetae]

Ok then expect to hear from you about what and how to test so we go on in the project :-)

ah ok I feel 21 and I tell you

[fvdw]

ok thks remember 21 is a standalone kernel ! not for writing to sda6 ! only use it with fvdw-sl console

[totorweb]

hi,

the problem is the same using the standalone 21 and the "standalone kernel, load and start" option.

Here is a print screen of the cmd "auto1" just before it close to lauch the telnet window.

no telnet, no ping even after few minutes.

Yes taetae, the kernel seems to begin to boot, but no response from network, maybe it hangs during the boot sequence.

taetae have you the possibility to test this standalone kernel ?

thx

[fvdw]

mmm.. there should come a message that it is ok and starting kernel, I don't see that in your output

this the typical response you should see, its the standalone kernel for a 2big1.

example-2big1.JPG

we could try if that runs but it will not be of much help as it will not be able to connect o your disk as the setup of the 5big1 is very much different, it uses a pci interface while the 2big1 is not.

There must be something in the standalone kernel that prevent booting

You could try to see if it boots if there is no disk inside