Hi,
I've installed udev 0.125 from unstable on testing and it seems to fix the
issue. The rtc-cmos module is automatically loaded. If udev 0.125 enters
testing, it should not be a problem (for me).
i had the same problem, fixed installing new udev version.
The rtc-cmos is automatically
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-1
Severity: normal
Hi,
When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains
during boot that it can not read the hardware clock using any known
methods.
When I look in /dev, the /dev/rtc* device is not there.
The device
Processing commands for [EMAIL PROTECTED]:
notfixed 476970 2.6.26-1
Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into
kernel, should be compiled as a module.
Bug no longer marked as fixed in version 2.6.26-1.
reopen 476970
Bug#476970: linux-image-2.6.24-1-686:
notfixed 476970 2.6.26-1
reopen 476970
tags 476970 - pending
found 476970 2.6.26-1
severity 493567 important
merge 476970 493567
tags 493567 + confirmed
kthxbye
On Sun, Aug 3, 2008 at 1:00 PM, Rik Theys [EMAIL PROTECTED] wrote:
When booting the 2.6.26 kernel from unstable on Lenny, hwclock
Processing commands for [EMAIL PROTECTED]:
tags 476970 + confirmed
Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into
kernel, should be compiled as a module.
There were no tags set.
Tags added: confirmed
reassign 493567 linux-2.6
Bug#493567:
unmerge 476970
fixed 476970 2.6.26-1
tags 476970 pending
severity 493567 normal
tags 493567 - confirmed
thanks
On Sun, Aug 03, 2008 at 02:26:56PM +0300, Teodor wrote:
notfixed 476970 2.6.26-1
reopen 476970
tags 476970 - pending
found 476970 2.6.26-1
severity 493567 important
merge 476970
Processing commands for [EMAIL PROTECTED]:
unmerge 476970
Bug#476970: linux-image-2.6.24-1-686: Generic RTC support hard compiled into
kernel, should be compiled as a module.
Bug#493567: linux-image-2.6.26-1-amd64: /dev/rtc* not created with 2.6.26,
rtc_cmos module must be manually loaded.
On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote:
When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains
during boot that it can not read the hardware clock using any known
methods.
I see it. The oldstyle rtc is disabled if the new infrastructure is
enabled. To make
On Sun, Aug 3, 2008 at 3:21 PM, Bastian Blank [EMAIL PROTECTED] wrote:
_STOP_ messing with bugs. The original bug was fixed. You are neither a
maintainer of the kernel nor a submitter of any of this bugs.
Ok, I stand corrected since you know better. I apologize for any
trouble created, it
On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote:
On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote:
When booting the 2.6.26 kernel from unstable on Lenny, hwclock complains
during boot that it can not read the hardware clock using any known
methods.
I see it. The
Hi,
On Sunday 03 August 2008 16:08:18 Bastian Blank wrote:
On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote:
On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote:
When booting the 2.6.26 kernel from unstable on Lenny, hwclock
complains during boot that it can not read
On Sunday 03 August 2008 16:08:18 Bastian Blank wrote:
On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote:
On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote:
When booting the 2.6.26 kernel from unstable on Lenny, hwclock
complains during boot that it can not read the
Hi,
On Sunday 03 August 2008 16:08:18 Bastian Blank wrote:
On Sun, Aug 03, 2008 at 02:38:10PM +0200, Bastian Blank wrote:
On Sun, Aug 03, 2008 at 12:00:10PM +0200, Rik Theys wrote:
When booting the 2.6.26 kernel from unstable on Lenny, hwclock
complains during boot that it can not read
13 matches
Mail list logo
