Lacie 2Big Network vs1

[Jocko]

HI matzi,

Do you change your router settings so that your LAN IP are 192.168.1.0/24 or 192.168.0.0/24 ?

You must do it and check that your dhcp server allows ip up to 252

[matzi]

What do you mean by the /24 ?
I have set the computer manually to 192.168.0.250 and connected the nas directly. Doesn't that do the same?

See last post on page 2 and there the senders IP.

[Jocko]

It's a short write of
192.168.1.0/24 = 192.168.1.0-192.168.1.255 IP range of your LAN (gateway: 192.168.1.1; mask:255.255.255.0)
192.168.0.0/24 = 192.168.0.0-192.168.0.255 ''...

[matzi]

OK meanwhile I tried the other router settings. No success.
Maybe we ask uelpenich for his exact experience?

[Jocko]

To check if there is an issue only with the kernel, you can try to get the u-boot console (see u-boot help page).

if you get the u-boot console then there is no issue with your LAN and in the other case it's a LAN setting issue

[fvdw]

of course we can but I am 100% sure that this kernel works on a 2big1
this was the output of Uelpenich after booting #22 standalone kernel and connecting with telnet (notice the #22) in the first line of dmesg output

Code: Select all

root@(none):/ # dmesg
Linux version 2.6.39.4 (root@fvdwsl-5big2.local) (gcc version 4.5.4 (GCC) ) #22 PREEMPT Tue Oct 8 21:38:40 GMT+1 2013
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
CPU: VIVT data cache, VIVT instruction cache
Machine: LaCie 2Big Network
<snip>

There is a possibility left and that is that your 2big1 isn't a 2big1 but a different type of lacie
In that case this kernel will load but not run

We can test if it runs by loading it what netconsole enable in an u-boot console window of the fvdw-sl console
How ?
Swicth off the nas, start fvdw-sl console, start tftp server and open u-boot console window (in fvdw-sl console)
Now start the nas and get the marvell>> prompt in the u-boot window

Now set first the environmental variables in this u-boot window

Code: Select all

setenv ipaddr ${ipaddr}; setenv serverip ${serverip};
setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7


(there is way oto paste in the u-boot window (right click on top of u-boot window and select form drop down window the required action)
After this is set boot the kernel using tftp

Code: Select all

 tftpboot 0x800000 UIMAGE-26394-NWSP2CL-2BIG1-22-standalone


it should now upload the kernel
Boot it

Code: Select all

bootm

It should now mentions that it boots the kernel, some info, then starting the kernel and after that console output should follow.
similar to the output shown above. if that is the case then the kernel and telnet server will be running something must be wrong in your lan. if the console output doesn't appear then probably the kernel is not running probably because your device is not a 2big1....

[matzi]

Router is back to 192.168.178.1 and DHCP. In fvdw-SL console I entered the IP given by DHCP (Field "IP Adress for NAS").
I have full u-boot console access, e.g. enter "help" and see the command list.

[matzi]

see the u-boot console:

Capture_3.jpg

and it goes on with T T T

[matzi]

See the webinterface. Does it give any hint?

[Jocko]

So it seems that there is an issue with your LAN. Do you use a wireless connection? and try to disable your firewall

Note : I don't think it's the same issue with the web-interface