Bug#533895: linux-image-2.6.26-2-r4k-ip22: Unable to Access Hardware Clock

2009-06-24 Thread Edwin Kwan
wrote: * Edwin Kwan ek...@stanfordalumni.org [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

Bug#533895: linux-image-2.6.26-2-r4k-ip22: Unable to Access Hardware Clock

2009-06-24 Thread Edwin Kwan
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 ek...@stanfordalumni.org [2009-06-24 02:48]: No, I don't have udev. This is an old SGI Indy

Bug#533895: linux-image-2.6.26-2-r4k-ip22: Unable to Access Hardware Clock

2009-06-21 Thread Edwin Kwan
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),