Firmware compatible to Wireless Space?

[coelhonet]

Ok, I'm finishing saving my data someplace else and I'll start it as soon as copy is completed (50% done).

Thanks a lot!

[Ian_sl]

Any luck with this. I am hoping to run squeezebox server.
Thanks much,
Ian s

[fvdw]

Any luck with this. I am hoping to run squeezebox server.
Thanks much,
Ian s

there is no reply from the other user, so you could try yourself see this topic. viewtopic.php?f=4&t=890&start=20#p15665

If this standalone kernel runs then we can proceed to install the firmware. if it doesn't run we need to modify the kernel

[coelhonet]

Hi there!

Sorry for taking longer to answer. Just had problems to backup some files (in fact, I lost them by now, since I couldn't find a way to get them out there on xfs).

So, I started this thing. Following procedures on viewtopic.php?f=7&t=1271:
1. Powered down my LaCie Wireless Space
2. Set IP address for my LaCie Wireless Space
3. At menu, selected Action > Stand alone kernel, load and start
4. When asked, I selected image UIMAGE-395-NWSP2CL-179-standalone
5. Turned on my device
6. TFTP and UBoot worked like a charm
7. Telnet opened after a while, but connection was not stablished

So, I'm stuck on this step. I tried to ping IP Address my device uses (DHCP server on my network provides a fixed IP Address based on MAC address to LaCie Wireless Space), but no luck.

What I could do next?

Thanks!

[coelhonet]

Hey!

So, I just tried to set my LAN IP (I was using Wireless connection before) to 192.168.1.251 and connected my notebook directly via network cable to one Wireless Space free local LAN port. I got link, but not able to ping 192.168.1.252. After that, tried also 192.168.0.251, but same results when trying to connect 192.168.0.252.

I'll let device turned on, by the way, it's not connect to a no break.

Thanks!

[coelhonet]

Ok, so I have done few more tests that could describe better things and maybe you can find a way to help me.

First thing, I read a lot on forum and I learned with that. So, FVDW-SL-Console cannot harm my unit if I don't ask to deploy a new firmware or change disk layout, it runs on RAM only. With that, I understood I can turn off and bring back device as before at stage I'm.

So, what I did:
1. Turn LaCie Wireless Space back on
2. Change its IP address to 192.168.1.252
3. Turned it off
4. Unplugged LaCie Wireless Space from my network
5. Change my notebook LAN IP address to 192.168.1.251
6. Connected a network cable from my notebook to one of LAN ports at LaCie Wireless Space
7. Disabled all other interfaces on my notebook (Wireless, Virtual, etc)
8. Turned LaCie Wireless Space back on and was able to access web interface on 192.168.1.251
9. Turned it back off
10. Started FVDW-SL-Console on my notebook
12. At menu, selected Action > Stand alone kernel, load and start
13. When asked, I selected image UIMAGE-395-NWSP2CL-179-standalone
14. Turned on my device
15. TFTP and UBoot worked like a charm
16. Telnet opened after a while, but connection was not stablished

I tried to connect network cable to every network port on Wireless Space but no ICMP reply got from a ping command to 192.168.1.252 from 192.168.1.251.

What I can think of, is that console is assigning an IP to a network device that is not present. Network Space has only on network port, while Wireless Space has 4 cabled network (1 for WAN and 3 for LAN) and also 1 wireless network. Is it something that makes sense?

Thanks!

[fvdw]

thanks for testing :thumbup
I think then the kernel setup file for the wireless space has a problem, as a result the kernel seem not to load.

It will be difficult to find out hwat is causing without having console output. I could try to make a minimal kernel to see if that loads and then add more features one by one.

If you are able to get the serial port connected we can see were the boot process fails

[coelhonet]

Hey!

Thanks for work you are doing and trying to make a broader coverage of what you developed.

So, I'd be glad to setup a console cable there, but could you help me out on where to find how to make one (pins and connections). I can get all needed to make it and put in place for testing.

If you need to check what is on current board, I can take some pictures and upload here.

Thanks again!

[coelhonet]

Back once again!

So, I opened my Wireless Space case and I can see J2 there (removed harddisk and pull off fan holder). Unfortunatelly I don't know where is pin 1 (printed board doesn't have this info), but connections look similar to ones I saw here (http://lacie.nas-central.org/wiki/Seria ... rk_space_2)). So, I think if I purchase correct USB to Serial converter I can have a serial console access.

By the way I read that there's a way to connect via Network Console (http://lacie-nas.org/doku.php?id=uboot). Will that help us someway or I should move straight to Serial Console?

Thanks!

[fvdw]

The net console will only work if the kernel loads as it is activasted inside the kernel, if the kernel fails to load before it is activate then you won't get output.

The serial console will not have this problem