Bug#475959: marked as done (hpet=force vs /dev/rtc)

ontact [EMAIL PROTECTED] immediately.) -- 475959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475959 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.24-1-686 Version: 2.6.24-5 Severity: important If I boot with hpet=force I

Bug#475959: hpet=force vs /dev/rtc

Hi, CONFIG_HPET_EMULATE_RTC=y is set in Package: linux-image-2.6.25-1-686 and hwlock works fine (as expected)! Thanks Dr. Markus Waldeck -- Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games! http://games.entertainment.gmx.net/de/entertainment/games/free -- To UNSU

Bug#475959: +

For what it's worth, I have a new(ish) machine that is running the stock kernel 2.6.24 in testing and cannot manage its clock without the --directisa workaround (complains about /dev/rtc problems). -- Regards, Sheridan Hutchinson [EMAIL PROTECTED] signature.asc Description: OpenPGP digital sig

Bug#475959: /dev/rtc access not working without hpet=force boot parameter, too

Hi, I have the problem in both 2.6.22-3-686 and 2.6.24-1-686 (2.6.24-5), too. I cannot access /dev/rtc without --directisa in hwclock and not on boot. It seems that this also prevents ntp from setting my clock: ntpd[4654]: adjusting local clock by -3598.738730s ntpd[4654]: adjtime failed: Invalid

Bug#475959: hpet=force vs /dev/rtc

Package: linux-image-2.6.24-1-686 Version: 2.6.24-5 Severity: important If I boot with hpet=force I avoid approximately 35 wakeups per second. Unfortunately I noticed two unnecessary delays during the boot process. These are caused by the fact that hwclock is not able to read the time from /dev/r