Re: Re: RTC Bug on Indy?

[Edwin Kwan <ekwan@rawbw.com>]

Hi Guido,

	I don't see any difference.  The new log is at the
bottom.

	I have to tell you this was the first time I upgraded
the kernel though.  Here is what I did:

1.  Downloaded
"kernel-image-2_4_19-r5k-ip22_2_4_19-0_020911_7_mips.deb"
2.  "dpkg -i" and continued despite the "depmod" errors
3.  used "dvhtool" to copy "/boot/vmlinux-2.4.19-r5k-ip22" to
    "linux_n" in the "volume header"
4.  Boot into the ROM montior and "boot -f" with the partition
    identifier followed by "/linux_n"

	Thanks!

>
>On Thu, Sep 18, 2003 at 01:58:50AM -0700, Edwin Kwan wrote:
>>       I have installed "woody" on an SGI Indy.  "uname -r"
>> gives 2.4.16.
>Please try 2.4.19 from the archive.
> -- Guido

gundam:~# uname -r
2.4.19-r5k-ip22
gundam:~# hwclock --set --date="09/17/03 23:59:45"
gundam:~# hwclock --show --localtime --debug
hwclock 2.4c/util-linux-2.11n
Using /dev/rtc interface to clock.
Assuming hardware clock is kept in local time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time
from /dev/rtc to change
...got clock tick
Time read from Hardware Clock: 2003/09/17 03:59:51
Hw clock time : 2003/09/17 03:59:51 = 1063796391 seconds since 1969
Wed Sep 17 03:59:51 2003  -0.682695 seconds
gundam:~# hwclock --show --localtime --debug
hwclock 2.4c/util-linux-2.11n
Using /dev/rtc interface to clock.
Assuming hardware clock is kept in local time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time
from /dev/rtc to change
...got clock tick
Time read from Hardware Clock: 2003/09/17 03:59:54
Hw clock time : 2003/09/17 03:59:54 = 1063796394 seconds since 1969
Wed Sep 17 03:59:54 2003  -0.085170 seconds
gundam:~# hwclock --show --localtime --debug
hwclock 2.4c/util-linux-2.11n
Using /dev/rtc interface to clock.
Assuming hardware clock is kept in local time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time
from /dev/rtc to change
...got clock tick
Time read from Hardware Clock: 2003/09/17 03:59:58
Hw clock time : 2003/09/17 03:59:58 = 1063796398 seconds since 1969
Wed Sep 17 03:59:58 2003  -0.884689 seconds
gundam:~# hwclock --show --localtime --debug
hwclock 2.4c/util-linux-2.11n
Using /dev/rtc interface to clock.
Assuming hardware clock is kept in local time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time
from /dev/rtc to change
...got clock tick
Time read from Hardware Clock: 2003/09/18 00:00:01
Hw clock time : 2003/09/18 00:00:01 = 1063868401 seconds since 1969
Thu Sep 18 00:00:01 2003  -0.146659 seconds
gundam:~#