time setting

I noticed that if my Guruplug is not connected to power for a couple of days it looses its time setting. I just got it 3 weeks ago. Is this a setting I need to adjust? Surely the battery is not dead already.

Richard

Guruplug does not have a RTC. It gets the time from ntp.

Quote

Surely the battery is not dead already.

You're running a Guruplug off a battery? Hey, that's a cool idea!

Try using the AC power adapter and plugging it into the 'net. That should solve the problem.

J/K :) sorry, just had to do it. LOL

^ This link says it has a RTC with battery backup -- http://www.globalscaletechnologies.com/t-guruplugdetails.aspx

I have opened it and it does have a small cell on the board. I guess Globalscale is selling them with dead batteries. Is there any way to tell when it was manufactured?

Quote

RTC w/Battery

Not easy to find on the page.

I guess I get to be the idiot on this one! ;) Sorry. . .

I'm seriously shocked that any *Plug has a RTC. I didn't even remember Kirkwood had a RTC input. Can you use a cheap DMM to check the voltage on the batt? It could be the RTC chip went bad.

Can the batt be desoldered and replaced?

Replacing is easy. I just need to get one and open it up again. If anyone has a bit of knowledge with these I would like to add a sata connector and could use advise. I have pictures of both board but no schematics.

gnexus Wrote:
-------------------------------------------------------
> I'm seriously shocked that any *Plug has a RTC. I
> didn't even remember Kirkwood had a RTC input.

The GoFlex Home has RTC, too :-)

Quote

The GoFlex Home has RTC, too :-)

Seriously?

Does that mean my GoFlex Net's also have an RTC I don't even know about?

That would be very nice indeed if it did!

dmesg |grep rtc
[   16.108994] rtc-mv rtc-mv: internal RTC not ticking
[   16.150154] /build/buildd-linux-2.6_3.2.19-1-armel-NviH8z/linux-2.6-3.2.19/debian/build/source_armel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

I don't see one . . .

Is it just GoFlex Home?

Wait a minute whats this: "linux-2.6_3.2.19-1-armel"

I'm on 3.2.0-2-kirkwood...maybe this kernel is not built w/ RTC support? But there are no 2.6 modules anywhere on the system. So where is that coming from?

my GoFlex Home reports:

dmesg |grep rtc
[ 15.973799] rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
[ 16.010293] rtc-mv rtc-mv: setting system clock to 2012-06-11 21:51:34 UTC (1339451494)


dockstar says no though:

dmesg |grep rtc
[ 11.146183] rtc-mv rtc-mv: internal RTC not ticking
[ 11.181620] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)



Edited 1 time(s). Last edit at 06/30/2012 07:36AM by optim.

Quote

dockstar says no though:

dmesg |grep rtc
[ 11.146183] rtc-mv rtc-mv: internal RTC not ticking
[ 11.181620] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

dockstar has no rtc. That's common knowledge. Interesting that GoFlex Home has one. More than likely that means the Net model also does. I will have to try to diagnose the issue at some point. But I'm really curious to know where the "linux-2.6-3.2.19" message on mine is coming from. But I'm too busy with my A10 now to mess with it. My GoFlex uses NTP anyway of course, and it rarely if ever gets rebooted...

gnexus Wrote:
-------------------------------------------------------
>

Quote

dockstar says no though:
>
> dmesg |grep rtc
> [ 11.146183] rtc-mv rtc-mv: internal RTC not
> ticking
> [ 11.181620] drivers/rtc/hctosys.c: unable to open
> rtc device (rtc0)

>
> dockstar has no rtc. That's common knowledge.
> Interesting that GoFlex Home has one. More than
> likely that means the Net model also does. I will
> have to try to diagnose the issue at some point.
> But I'm really curious to know where the
> "linux-2.6-3.2.19" message on mine is coming from.
> But I'm too busy with my A10 now to mess with it.
> My GoFlex uses NTP anyway of course, and it rarely
> if ever gets rebooted...

I don't think the GoFlex Net has RTC, only the GoFlex Home.

About the message "linux-2.6-3.2-19", could it be that because when you built your kernel, the 2.6.3.2-19 drivers were still on your system and got picked up somehow?

Quote

About the message "linux-2.6-3.2-19", could it be that because when you built your kernel, the 2.6.3.2-19 drivers were still on your system and got picked up somehow?

probably... . still it's a bit strange.