Comment 6 for bug 293484

I don't know how to get the right information, could you please tell me what
information I can provide and how can I get it(what command should I execute) to
help solve this problem?
It is ok If you need all the output of dmesg and lsmod. (about 578 + 48 lines)
Following is the information I can get.

Fedora 9 On HP DL380G4 (use new rtc driver and don't work)
# ls -al /dev/rtc*
ls: cannot access /dev/rtc*: No such file or directory

# dmesg | grep -i rtc
<nothing>

#lsmod | grep -i rtc
<nothing>

# clock --systohc --debug
hwclock from util-linux-ng 2.13.1
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.

Fedora 9 On IBM BladeCenter HS21 (use new rtc driver and working)
# ls -al /dev/rtc*
lrwxrwxrwx 1 root root 4 2008-06-16 22:07 /dev/rtc -> rtc0
crw-r--r-- 1 root root 254, 0 2008-06-16 22:07 /dev/rtc0

# dmesg | grep -i rtc
ACPI: RTC can wake from S4
rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one year

#lsmod | grep -i rtc
<nothing>

Fedora 8 On HP DL380G4 (Use old char -> rtc and working)
# ls -alt /dev/rtc*
crw-r--r-- 1 root root 10, 135 2008-06-10 20:32 /dev/rtc

# dmesg | grep -i rtc
<nothing>

#lsmod | grep -i rtc
<nothing>