I tried a few things. First I did replace the CMOS battery just in case, no go was not the issue. Second I tried MAKEDEV /dev/rtc which created a device file with a MAJOR/MINOR pairing of 10, 135 just as devices.txt specifies, however this did not work and the device was gone after a reboot. The I tried a series of mknod's with varying MAJOR/MINOR pairings i.e. mknod /dev/rtc c 10 135 and mknod /dev/rtc c 10 254 and mknod /dev/rtc c 254 0 none of which worked and the device always disappears after a reboot. Is there some log file I can check to look for errors in creating devices at boot?

byrdca(a)gmail.com wrote: You should not need /dev/rtc for this. Unless they changed it for F9, you should be able to edit /etc/sysconfig/clock and set UTC=false. You may also have to run "hwclock --localtime --hctosys" to make sure thing get set write when you shutdown. (hwclock "remembers" the last use of --localtime or --utc.) Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!

byrdca(a)gmail.com wrote: I would expect support for the CMOS clock to be loaded automatically, and I can't guess why you would need anything else. There might be a boot option, but it certainly doesn't come to mind. Looking at several working systems, I am trying to guess which modules might be related. There is virtually nothing in common between a Q6600 and Celeron system with SIS chipset, so I doubt it's a module. Here are some ideas in order of how likely I think they are: 1 - find out how to tell XP to use UCT on the hardware clock and reset it to UTC. This will also fix problems the next time our bonehead congress proves it doesn't understand time and resets DST. 2 - in GNOME go to system->administration->date&time, and on the "time zone" tab check that you have the TZ set and the hardware clock checked (or not, if you disregard my 1st idea). 3 - use the acpi= boot options, you can look up which ones seem possible as solutions. It could be an ACPI problem, there were a lot of changes in that area with FC9 kernels. Actually with recent kernels, I think they're in FC8 current as well. 4 - disable apic from the boot options line. Last resort, I have no idea why this might help, but I saw it in a posting elsewhere. -- Bill Davidsen <davidsen(a)tmr.com&gt; "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot

byrdca(a)gmail.com wrote: Let me start by saying that XP has an option to run the clock in UTC, and that you would have been happier to run your hardware clock that way. Having the hardware clock reset seems to leads to other learning experiences. It sounds as if your hardware clock is simply not usable by the kernel drivers. However, if you boot and get the system starting at nearly the right time, then it's likely that your hardware is being read. In /var/log/messages, when you boot do the messages have the right time? If so some source of the clock was found. -- Bill Davidsen <davidsen(a)tmr.com&gt; "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot

First it was my hope that there was a solution other than MAKEDEV or mknod as I suspect that there is another issue perhaps with udev or something that would leave me in the same situation after a reboot. Now onto the questions. The /dev/rtc does not exists it is however listed as a character device as you can see in the results from cat /proc/devices (it is 254) cat /proc/devices Character devices: 1 mem 4 /dev/vc/0 4 tty 4 ttyS 5 /dev/tty 5 /dev/console 5 /dev/ptmx 7 vcs 10 misc 13 input 14 sound 21 sg 29 fb 116 alsa 128 ptm 136 pts 180 usb 189 usb_device 195 nvidia 202 cpu/msr 203 cpu/cpuid 248 firewire 249 usb_endpoint 250 hidraw 251 usbmon 252 bsg 253 pcmcia 254 rtc Block devices: 1 ramdisk 8 sd 9 md 11 sr 65 sd 66 sd 67 sd 68 sd 69 sd 70 sd 71 sd 128 sd 129 sd 130 sd 131 sd 132 sd 133 sd 134 sd 135 sd 253 device-mapper 254 mdp Another mystery is that when I run timeconfig it shows that "System uses UTC" is unchecked, though system-config-date shows the option as checked/enabled.