hi there,
i'm a big fan of this forum and got a few devices allready running successfully bodhi's great debian stuff - thank you for all your work :-)
my latest project is a broken (hdd - crashed) lacie networkspace 2 lite devices. i flashed the mainline u-boot (from lacie-side) and got
it running with a new drive and bodhi's latest rootfs and kernel 4.4.0
my only problem is, that the hardwareclock is on 2018 .. when i try to set it up automatically with:
ntpdate de.pool.ntp.org
i got the error: Can't adjust the time of day: Invalid argument
tried to set it up manualy worked: date -s 2016-02-12
debian replied with: Fr 12. Feb 00:00:00 CET 2016
when i entered 2 seconds later: date
debian replied: Fr 31. Aug 01:54:27 CEST 2018
i played around with hwclock but without any luck. can some of you guys tell me what the heck is going on with it ???
thank you in advanced.
greetz, sLOID.
i'm a big fan of this forum and got a few devices allready running successfully bodhi's great debian stuff - thank you for all your work :-)
my latest project is a broken (hdd - crashed) lacie networkspace 2 lite devices. i flashed the mainline u-boot (from lacie-side) and got
it running with a new drive and bodhi's latest rootfs and kernel 4.4.0
my only problem is, that the hardwareclock is on 2018 .. when i try to set it up automatically with:
ntpdate de.pool.ntp.org
i got the error: Can't adjust the time of day: Invalid argument
tried to set it up manualy worked: date -s 2016-02-12
debian replied with: Fr 12. Feb 00:00:00 CET 2016
when i entered 2 seconds later: date
debian replied: Fr 31. Aug 01:54:27 CEST 2018
i played around with hwclock but without any luck. can some of you guys tell me what the heck is going on with it ???
thank you in advanced.
greetz, sLOID.