fvdw-sl-console for ms windows install without removing HDD

[fvdw]

try if you can connect with the webinterface or with putty (ssh client)
Of course you need to know the ip assigned to the nas by your router

If the the blue led was flickering for some minutes this indicates the disk is active and loads the firmware, if it did not flicker and stayed steady blue well then it failed

[favroom]

give command

Code: Select all

bootm

this will start the kernel which will try to load the firmware from sda7

Kernel started...
What's next:)

There's no http respons on the ip address of the NWSP2 and the Marvell prompt seems to have stalled...

[fvdw]

yes the marvel prompt is stalled

the ip of the nas will not be the same as used in the fvdw-sl-console, it will be an ip assigned dynamic by your dhcp server (router)

ps do you use a wireless connection between PC and router ?

[fvdw]

how did you figure out the ip address to be used for http access to the nwsp2 ?

[fvdw]

please respond a little quicker it is getting late :-D I want to go to my bed

[favroom]

yes the marvel prompt is stalled

the ip of the nas will not be the same as used in the fvdw-sl-console, it will be an ip assigned dynamic by your dhcp server (router)

ps do you use a wireless connection between PC and router ?

I was first using the same address as I used running the fvdw-sl-console...

OK, I might have a dhcp problem... I had to manually config network settings on the NSWP1 too.
The modem/ router does not report any new devices on the dhcp pool...

And yes, I am using a wireless connection between my laptop and the router.

[favroom]

please respond a little quicker it is getting late :-D I want to go to my bed

Maybe one last try. Manually config network settings... Is that possible?

[fvdw]

And yes, I am using a wireless connection between my laptop and the router.

That is probably the reason for the fact that you loose response of at Marvell prompt.
I notice a T when it uploaded the kernel. That means it had a timeout

Probably similar problems happens when installing the firmware using the installer. The wireless is not so reliable.
I suggest you repeat it using a wired connection.

If you use the installer again first delete the partition table

About your question, manully setting up network settings, that needs adaptation of the nas database, cannot be done from u-boot console
But with the standalone kernel we could manage that. But that will not be tonight, I go to bed, sorry
But tomorrow I will have some time

[favroom]

And yes, I am using a wireless connection between my laptop and the router.

That is probably the reason for the fact that you loose response of at Marvell prompt.
I notice a T when it uploaded the kernel. That means it had a timeout

Probably similar problems happens when installing the firmware using the installer. The wireless is not so reliable.
I suggest you repeat it using a wired connection.

If you use the installer again first delete the partition table

About your question, manully setting up network settings, that needs adaptation of the nas database, cannot be done from u-boot console
But with the standalone kernel we could manage that. But that will not be tonight, I go to bed, sorry
But tomorrow I will have some time

Thanks! And good night.

[fvdw]

The modem/ router does not report any new devices on the dhcp pool...

why not ? (is it full...)