[Voyage-linux] Testing pre-0.8.0 - hwclock

[Teco Boot]

Op 16 sep 2011, om 17:55 heeft themrorange at gmail.com het volgende geschreven:

> Yep, it fixed the problem on 0.7.5 Alix2d3 
> I don't have the error anymore during shutdown
> 
> Unfortunatelly hwclock, it still fails.
> 
> # hwclock --debug
> hwclock from util-linux-ng 2.17.2
> hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
> No usable clock interface found.
> Cannot access the Hardware Clock via any known method.

With --directisa it works fine.

root at AHR-175-166:~# hwclock --directisa --debug
hwclock from util-linux-ng 2.17.2
Using direct I/O instructions to ISA clock.
Last drift adjustment done at 0 seconds after 1969
Last calibration done at 0 seconds after 1969
Hardware clock is on unknown time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2011/09/16 16:53:55
Hw clock time : 2011/09/16 16:53:55 = 1316192035 seconds since 1969
Fri Sep 16 16:53:55 2011  -0.961696 seconds
root at AHR-175-166:~# 


> Teco, at witch line did you add this snippet in the init-scripts:
> 
> # Include hwclock defaults if available
> if [ -f /etc/default/hwclock ] ; then
>   . /etc/default/hwclock
> fi

I replace the HWCLOCKPARS="" line (and the 2 comment lines, as described below).
IMHO config should be in config files, not in scripts.

Teco


> 
> On 16 Sep 2011, at 15:41, Teco Boot wrote:
> 
>> 
>> Op 16 sep 2011, om 16:34 heeft themrorange at gmail.com het volgende geschreven:
>> 
>>> Hi,
>>> 
>>> Seems to me that voyage 0.7.5 has the same problem.
>> Yes. 0.7.0 also. I remember 0.6.x (Lenny) was better.
>> 
>> I check all my 0.7.0 bypasses and check if solution is in 0.8.0
>> I stepped over 0.7.5. 
>> 
>> Teco
>> 
>>> I'll try your patch on my Alix 2d3 and I'll let you know
>>> 
>>> Davide
>>> 
>>> 
>>> On 16 Sep 2011, at 13:43, Teco Boot wrote:
>>> 
>>>> Hi Punky,
>>>> 
>>>> I started testing 0.8.0. Development: VMware, target Alix6.
>>>> I'll post my findings.
>>>> 
>>>> hwclock
>>>> =======
>>>> During shutdown, there is an error:
>>>> Saving the system clock.
>>>> Cannot access the Hardware Clock via any known method.
>>>> I adjusted /etc/init.d/hwclock.sh - hwclockfirst.sh for saving & resoring clock during (soft)reboot:
>>>> HWCLOCKPARS="--directisa -u --noadjfile"
>>>> Ref:
>>>> http://www.pcengines.info/forums/?page=post&id=27136143-ABFC-4447-87DE-2B942342FE71&fid=40251191-FF24-48A8-BB0E-995B04812ADE
>>>> 
>>>> 
>>>> It would be nice to add the parm in a /etc/default/hwclock file, with content:
>>>> # Defaults for hwclock.sh and hwclockfirst.sh initscripts
>>>> 
>>>> # Set this to any options you might need to give to hwclock, such
>>>> # as machine hardware clock type for Alphas.
>>>> HWCLOCKPARS="--directisa -u --noadjfile"
>>>> 
>>>> 
>>>> And update the initscripts with:
>>>> # Include hwclock defaults if available
>>>> if [ -f /etc/default/hwclock ] ; then
>>>> . /etc/default/hwclock
>>>> fi
>>>> 
>>>> 
>>>> Thanks, Teco
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Voyage-linux mailing list
>>>> Voyage-linux at list.voyage.hk
>>>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>> 
>>> 
>>> _______________________________________________
>>> Voyage-linux mailing list
>>> Voyage-linux at list.voyage.hk
>>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>> 
>