hwclock

brady · n00b Joined: 11 Jun 2002 Posts: 23

/sbin/hwclock is not working on my ibook. it just sits there (taking not resources).

i have tried nvram as a module and static
i have tried gentoo's ppc sources, and benh's
i have proc and devfs support

still cant figure this one out. i also cant figure out which package to re-emerge to re-emerge hwclock.

thanks in advance.

-brady

owen · n00b Joined: 29 Jun 2002 Posts: 5

Very interesting....It works for me

Anyways, what version are you using? Is the time/date correctly set on a reboot?

hwclock is apart of sys-apps/util-linux and you can find which which ebuild "owns" a file by using qpkg available in the gentool kit (emerge gentoolkit).

karasu · Posted: Mon Jul 01, 2002 12:59 am Post subject: Also having this problem -

After having a number of other problems getting gentoo running on my Lombard G3 powerbook, I've also encountered this issue.

Originally I was encountering file system corrupting errors when I tried to run /usr/portage/scripts/bootstrap.sh while building my system. I discovered that problem was related to the 2.4.19-r3 kernel being used by the ramdisk on the install ISO.

Remerging util-linux didn't seem to fix the problem. There don't seem to be any helpful messages in the main log either.

I discovered that I was missing my timezone /etc/localtime link but creating this file didn't remedy the situation.

brady · n00b Joined: 11 Jun 2002 Posts: 23

i re-emerged util-linux (contains hwclock). that didnt fix the problem.

but i took at look at my dmesg, and hwclock is now causing this message:

IN from bad port 71 at c00a4800
IN from bad port 71 at c00a47a4
IN from bad port 71 at c00a4800
IN from bad port 71 at c00a52a8
IN from bad port 71 at c00a5308
IN from bad port 71 at c00a47a4
IN from bad port 71 at c00a4800

actually, a whole bunch of messages like that.

any ideas?

-brady

karasu · Posted: Mon Jul 01, 2002 9:07 pm Post subject:

After having downloaded the latest ISO image, done a complete build from both that, and tried using Gerk's stage2 and stage3 tarballs, I've been unable to get hwclock to work.

I was perusing the kernel documentation on the rtc { Documentation/rtc.txt } and found a program embedded in it which was ment to test and demonstrate using the rtc.

It creates those same [kernel] IN from bad port 71 at xxxxxxx messages, so its a kernel issue it would seem. What version of kernel are you using? I've got benh's 2.4.19-rc1-ben0 currently. Going to experiment with other versions.

Gerk · Retired Dev Joined: 07 May 2002 Posts: 435

I'm not positive of this, but try turning off rtc in kernel config before you fight with more stuff

Gerk

karasu · Posted: Tue Jul 02, 2002 3:03 am Post subject:

Absolutely correct. That fixed it

brady · n00b Joined: 11 Jun 2002 Posts: 23

strange. but i _want_ rtc support.

other than that, could you please explain to me why this fixes the issue?

-brady

Gerk · Retired Dev Joined: 07 May 2002 Posts: 435

Very simple solution, it's not supported on ppc! Why it shows up in the config options I have no idea. The functionality should all be in the ppc kernel AFAIK tho without having to add that option.

brady · n00b Joined: 11 Jun 2002 Posts: 23

ok, im not sure as to what you mean:

Gerk · Retired Dev Joined: 07 May 2002 Posts: 435

hwclock works, rtc doesn't AFAIK. Other than that you'll have to do som research on the net, sorry

brady · n00b Joined: 11 Jun 2002 Posts: 23

ive used rtc before though, in mplayer, for video/audio syncing.

well, at least i /think/ i have. the following is the output from mplayer when i do and do not have:

dvd://1

but when i have proper permissions, it just says "using rtc for timing"

thoughts?

-brady

Gerk · Retired Dev Joined: 07 May 2002 Posts: 435

it's possible that the rtc funcionality is built into ppc kernel in some other guise, like I said, the best bet is to do some research on this (I'm not a kernel hacker by any means).

Try to find a mirror of the (now gone bye bye) linux-ppc dev lists.

karasu · Posted: Thu Jul 04, 2002 7:57 pm Post subject:

I'm curious about this because as far as my previous recollections go, I always used to enable support for RTC in my kernels back in the YDL days.

I suspect that the component that breaks this is the Enhanced RTC Support options thats right under Support for /dev/nvram in the Character devices section, not the Support for /dev/rtc thats under General setup.

Currently compiling the module now and will test in a little.

From everything I've read since this issue came up, you don't support for RTC anyways unless you explicitly know why you need support for it. Basically it just provides a character device interface to the rtc which could be useful for things like time sensitive sampling issues for scientific purposes, or other issues where timing is important and its not reliable to use the system clock. As for mplayer, if the /dev/rtc file didn't exist, it would use the system clock.

Oh BTW - Support for /dev/rtc works, Enhanced RTC does not work, so feel free to enable /dev/rtc, just don't enable the Enhanced option underneath /dev/nvram.