[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Cannot access the Hardware Clock via any known method

Jarod Wilson wrote:
On Wednesday 30 January 2008 09:40:20 am Nicolas Mailhot wrote:
Le Mer 30 janvier 2008 15:05, Rex Dieter a écrit :
yep, spot and I chatted about this @ FUDCon, his guess was that
hwclock was
running too early, possibly before udev had a chance to
create /dev/rtc.  ??
I think I don't have this message with my home-built mm kernels, so
it's probably a mistake in rawhide's kernel config (IIRC there are two
rtc stacks in the kernel now and you get this message if you build the
wrong one, or both)

The new cmos rtc driver was getting built as a module, rather than staticly into the kernel. Chuck checked in fixes yesterday, so some forthcoming rawhide kernel should be all good.

<BZZZZ> wrong, the new driver has a different major/minor number, so having the new driver not build as a module is part of the solution, but not the complete solution, see: https://bugzilla.redhat.com/show_bug.cgi?id=290731

For the full story about the major/minor no issue.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]