The reason was that the RTC was not running on the nwsp1 and as result the hwclock command didn't work.
This does not cause a real problem, especially if you have set the clock to adjust automatic via internet. if you set it manual the time will be set but an error message will be displayed as the firmware tries to adjust the hardware clocks as well.
However on the spd8020 the RTC and hwclock is working with the current kernel. The reason is that there must be a small difference between the hardware on the main board of the nwsp1 and spd8020 with respect to the RTC, the nwsp1 uses a different chip then the spd8020. Only the driver for the spd8020 RTC chip is loaded in the current kernel, as result the RTC on the nwsp1 doesn't work.
I adapted the kernel scripts in a way that as well the RTC chip of the spd8020 and nwsp1 is supported. I tested it on the spd8020 and it is working ok, but I need a volunteer to try this kernel on the nwsp1 to see if this new kernel gets the RTC and hwclock command working on the nwsp1.
To install it unpack the sip file and place the kernel in a share on the nwsp1 and use putty to write it to sda6 partition using the dd command, after it reboot the NAS.
If you have put the kernel in the "fvdw" share the command to use in putty is:
- Code: Select all
dd if=/share/1000/fvdw/uImage-26331-4 of=/dev/sda6
of course it can be installed form any directory where you have put it.
I am interested in the output that the dmesg command will give after installation. This to see if the driver is loaded properly and a test if the hwclock command is working.
To test if the hwclock command is working give in putty the command
- Code: Select all
hwclock -r
If you get a response something like this
- Code: Select all
/$ hwclock -r
Thu Aug 25 20:38:12 2011 0.000000 seconds
then RTC is working.
edit 5-sept-2011--test kernel removed, doesn't seem to cure the problem on the nwsp1
Do NOT use this kernel on other devices than the Lacie networkspace version 1.
It will make your device non functional !