Red Hat Bugzilla – Bug 451401
/dev/rtc | /dev/rtc0 not created at boot time.
Last modified: 2009-07-14 13:58:33 EDT
Description of problem:
/dev/rtc (and/or) /dev/rtc0 are not created at boot time. hwclock and
system-config-date are unable to synch/communicate with hardware clock.
NOTE: Dual boot system with Win XP Pro
Version-Release number of selected component (if applicable):
Boot and attempt to set clock
Steps to Reproduce:
2. run system-config-date, when done error stating "failed to synchronize
hardware clock. This may be because there is no hardware clock accessible e.g.
when running in a virtualized environment."
3. run hwclock --debug --show and receive following output
hwclock --debug --show
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.
After install noticed clock was wrong. Saw that "System uses UTC" was checked
even though I unchecked it at boot time so I attempted to clear the checkbox and
save but was met with reported error, did an ls -l and saw no /dev/rtc* device
cat /proc/devices returns output below
Also noticed a somewhat different bug dealing with /dev/rtc that may or may not
be relevant https://bugzilla.redhat.com/show_bug.cgi?id=290731
I can send along my udev rules and or anything else that is needed just let me know.
I also note that MAKEDEV was attempted and a device file with a MAJOR/MINOR pair
of 10, 135 was created though it seems from discussion on mailing lists and
forums that most people have /dev/rtc as a symlink to /dev/rtc0 with a
MAJOR/MInor pair of 254, 0.
still a problem?
It was a problem for the duration of my Fedora 9 usage. Unfortunately at the moment I've installed another distro for test/dev purposes on the set of hardware that showed this issue. Once I'm done I'll be putting Fedora back, if no one has joined it may just be an issue with my hardware, I've noticed that restarts occasionally result in a Kernel panic no matter the distro I boot, so I'm beginning to suspect hardware issues of some sort, though my rtc is back under my current setup.
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.