ts-7000
[Top] [All Lists]

[ts-7000] Re: RTC daughterboard on TS-7200 - how to use?

To:
Subject: [ts-7000] Re: RTC daughterboard on TS-7200 - how to use?
From: "charliem_1216" <>
Date: Wed, 23 Jan 2008 14:31:45 -0000
--- In  Jeff Cunningham <> wrote:
>
> charliem_1216 wrote:
> >
> >  Hi Jeff --
> >
> >  What do the following commands give?
> >
> >  ls -l /dev/rtc* dmesg | grep rtc ln -s /dev/rtc0 /dev/rtc hwclock
> >
> >  Looks like you have /dev/rtc0, but not /dev/rtc. hwclock doesn't know
> >  how to look for anything but /dev/rtc, so we just create a link named
> >  /dev/rtc and point it to the real device /dev/rtc0.
> >
> >  This works for me (hwclock of util-linux-2.12r, but it shouldn't
> >  matter).
> >
> >  Regards, ........ Charlie
> 
> Hi Charlie;
> 
> What I have is /dev/rtc but *not* /dev/rtc0. Here's the results of 3/4 
> of your suggestions:
> 
> :# ls /dev/rtc*
> /dev/rtc
> 
> :# dmesg | grep rtc
> rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc0
> rtc-m48t86 rtc-m48t86: battery ok
> 
> :# hwclock --version
> hwclock from util-linux-2.12r
> 
> :# hwclock
> Cannot access the Hardware Clock via any known method.
> Use the --debug option to see the details of our search for an access 
> method.
> 
> :# hwclock --debug
> hwclock from util-linux-2.12r
> hwclock: Open of /dev/rtc failed, errno=19: No such device.
> No usable clock interface found.
> Cannot access the Hardware Clock via any known method.
> 
> There was no point in trying the soft link, since /dev/rtc is already 
> there.
> 
> --Jeff
>

OK, that's a different problem.  I guess either you have static device
nodes, or startup scripts are creating the device node /dev/rtc (major
10, minor 135), when actually you don't really have the older style
rtc device.  You _do_ get the new rtc0, as indicated by your logs when
you  insert the module, but you _don't_ have the character device for
it in /dev.

[BTW, You can find a detailed explanation of the older PC-centric
(rtc) and the newer (rtc0, rtc1, ...) devices in your kernel tree:
Documentation/rtc.txt.]

So, try these:
* cat /proc/driver/rtc  (check capabilities of new rtc driver)
* cd /dev
* mknod rtc0 c 254 0
* ln -nsf rtc0 rtc
* hwclock

If this works, the longer term solution is (1) to update your udev or
static device nodes to be sure /dev/rtc0 shows up, and (2) upgrade to
a  hwclock that knows to try /dev/rtc0 if /dev/rtc is not available.

Regards, .......... Charlie




 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/ts-7000/join
    (Yahoo! ID required)

<*> To change settings via email:
     
    

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 

<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU