Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 179780
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo's Team for Core System packages <base-system@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Renato Caldas <seventhguardian@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 179780 depends on: Show dependency tree
Bug 179780 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2007-05-25 18:52 0000 
From what I've read RTC_CLASS is the new rtc framework for the kernel, and will
eventually supersede the other rtc driver framework. So now /dev/rtc is
replaced by /dev/rtc<n> where <n> is the rtc index. In my system I have a
/dev/rtc0.

Unfortunately hwclock from sys-apps/util-linux-2.12r-r7 is unable to work under
this new environment:

  $ hwclock
  Cannot access the Hardware Clock via any known method.
  Use the --debug option to see the details of our search for an access method.

So the "/etc/init.d/clock" baselayout script doesn't work and reports this
error every time it is ran (that is, at every boot). Strangely (or not) the
system clock is correctly updated. So I'm not sure if this is a core-system or
baselayout bug.

PS: I'm currently trying out baselayout-2.0.0_alpha3, so I'm trying to solve
the boot errors one by one..

------- Comment #1 From Renato Caldas 2007-05-25 21:38:54 0000 ------- 
As a side note, the system works perfectly with /etc/init.d/clock removed from
the runlevels. So maybe it is not needed under new kernels (?) or maybe the
docs should be updated (?)

Should I submit a new bug report and/or patches to the docs? Or is this plain
stupid?

------- Comment #2 From SpanKY 2007-05-26 02:21:50 0000 ------- 
this has been fixed upstream in util-linux already ... not sure it's worth
backporting the changes though

------- Comment #3 From SpanKY 2007-09-03 15:20:35 0000 ------- 
2.13 is in portage now and it should work fine

------- Comment #4 From Chris Mayo 2007-11-05 20:16:25 0000 ------- 
Not fixed in 2.13 for me or others. Even specifying the device:

hwclock --systohc --rtc=/dev/rtc0
hwclock: open() of /dev/rtc failed, errno=2: No such file or directory.

Needed to apply the patch from:
http://git.kernel.org/?p=utils/util-linux-ng/util-linux-ng.git;a=commitdiff_plain;h=5d1f6bae3b298809ecd63b3e55f6ab30caaa4dbf

------- Comment #5 From Renato Caldas 2007-11-06 20:33:15 0000 ------- 
I'm reopening this then(In reply to comment #4)
> Not fixed in 2.13 for me or others. (...)

I'm reopening it then.

------- Comment #6 From SpanKY 2007-12-14 03:17:51 0000 ------- 
fixed in util-linux-2.13-r3

http://sources.gentoo.org/sys-apps/util-linux/files/util-linux-2.13-hwclock-rtc.patch?rev=1.1
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug