--- In Jeff Cunningham <> wrote:
>
> Kevin Cozens wrote:
> >
> > Jeff Cunningham wrote:
> > > :dev# 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.
> > >
> > > I also tried making the device node with 10 135 which is what my
> > > Gentoo desktop is set up with, but it made no difference.
I guess your desktop is still using the PC / ACPI rtc.
> >
> > Did you try rebuilding the kernel with the RTC RAM option enabled to
> > see if it makes any difference?
> >
> > -- Cheers!
> >
> > Kevin.
>
> Hi Kevin,
>
> Yes, I did. No difference. When I try to load the rtc-cmos driver it
says:
>
> :codes# modprobe rtc-cmos
> FATAL: Error inserting rtc_cmos
> (/lib/modules/2.6.23-rc1ide_2/kernel/drivers/rtc/rtc-cmos.ko): No such
> device
>
> I also just tried compiling the test program at the end of rtc.txt in
> the kernel tree. The first thing it tries to do is open /dev/rtc0 and
> fails, even though I've created it with mknod /dev/rtc0 c 10 135 (and
> re-loaded the rtc modules). This seems to be the crux of the
Hi Jeff --
You are using modules, while I always compile RTCs into the kernel. I
see that there are other modules required: rtc-dev (which triggers
udev to create the rtc0 .. rtcN device nodes) and rtc-class at least.
Please see if you have these modules loaded or built in. When
configuring your kernel, look for "/dev/rtcN (character devices)",
which selects 'RTC_INTF_DEV'.
If you are using modprobe to load your chip driver (and have run
'depmod -a'), these other modules should be loaded for you. If you
are using insmod, insmod will happily insert the module even if a
dependency is not satisfied.
problem:
> that node cannot be opened.
>
> What I don't understand yet is what happens when the rtc-m48t86 driver
> is loaded. Dmesg says that the chip is registered "as rtc0" but what
> does that mean? It says that whether or not I've created the /dev/rtc0
> -> /dev/rtc link, so it doesn't seem to look at what's in the dev tree.
> Could this be a udev problem of some kind? Is there some place in the
> udev setup where I need to configure something that is missing?
>
> Regards,
> --Jeff
>
If it's not fixed by rtc-dev and / or rtc-class modules, I'm about out
of ideas. Could be udev related. You could try building everything
RTC related into the kernel. You could see if there are any rtc
changes in a recent (2.6.24-rc8) kernel patch.
RTCs shouldn't be this hard. I will dust off my TS-7250 tonight if
you are still having problems.
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/
|