On Wed, Jun 24, 2009 at 02:48:20AM -0700, Edwin Kwan wrote:
> No, I don't have "udev". This is an old SGI Indy workstation, and
> the Debian installation has been upgraded time and again starting
> from Woody. :) I could not plug any new device into it anyway.
> Is there an easy workaround, or
Martin,
I think it is working now. I am keeping both rtc (10, 135), and rtc0
(254, 0), for now just in case I need to go back to an old kernel.
Thanks!
Martin Michlmayr wrote:
Edwin,
* Edwin Kwan [2009-06-24 02:48]:
No, I don't have "udev". This is an old SGI Indy workstation, and the
Edwin,
* Edwin Kwan [2009-06-24 02:48]:
> No, I don't have "udev". This is an old SGI Indy workstation, and the
> Debian installation has been upgraded time and again starting from Woody.
> :) I could not plug any new device into it anyway.
>
> Is there an easy workaround, or do I have to in
Martin,
No, I don't have "udev". This is an old SGI Indy workstation, and the
Debian installation has been upgraded time and again starting from
Woody. :) I could not plug any new device into it anyway.
Is there an easy workaround, or do I have to install "udev"?
Thanks!
Martin Michlmayr
* Edwin Kwan [2009-06-24 01:58]:
> The "/dev/rtc" file does exist, as seen below:
> gundam:~> ls -l /dev/rtc*
> crw-rw 1 root root 10, 135 Mar 15 2002 /dev/rtc
> gundam:~>
Are you not using udev? It seems the device nodes are not correct
because the kernel created rtc0, which you don't have
Hi Martin,
Your test kernel eliminated the error message during kernel boot. But
"hwclock" still fails. :( I have attached 2 files:
rtcnew.log is the excerpt from syslog when your test kernel booted
strace.log is the "strace" output of "hwclock --test --debug" while
using your kernel
The
* Edwin Kwan [2009-06-21 04:27]:
> During boot, I saw this error in syslog:
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> Consequently "hwclock --test --debug" would fail.
Can you please test the following kernel:
http://merkel.debian.org/~tbm/tmp/kernel/linux-image-2.6.26-2-r4k-ip2
Processing commands for cont...@bugs.debian.org:
> owner 533895 !
Bug 533895 [linux-image-2.6.26-2-r4k-ip22] linux-image-2.6.26-2-r4k-ip22:
Unable to Access Hardware Clock
Owner recorded as Martin Michlmayr .
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bu
Package: linux-image-2.6.26-2-r4k-ip22
Version: 2.6.26-15lenny3
Severity: important
During boot, I saw this error in syslog:
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Consequently "hwclock --test --debug" would fail.
After switching back to an older kernel (2.6.18-5-r4k-ip22),
9 matches
Mail list logo
