Observed in Hardy 8.04.2. Fairly generic workstation motherboard.
--
Could hwclock.sh fall back to using --directisa
https://bugs.launchpad.net/bugs/39959
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Oh, and second the suggestion that hwclock should fall back to direct
ISA by default if /dev/rtc fails.
--
Could hwclock.sh fall back to using --directisa
https://bugs.launchpad.net/bugs/39959
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Addressed differently in linux.
** Changed in: util-linux (Ubuntu)
Status: Confirmed = Won't Fix
--
Could hwclock.sh fall back to using --directisa
https://bugs.launchpad.net/bugs/39959
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Could you explain this a bit more --verbose, Daniel?
--
Could hwclock.sh fall back to using --directisa
https://bugs.launchpad.net/bugs/39959
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
See my comments in [url=https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/21295/]bug 21295[/url].
Now works for me after Hardy upgrade (Dell Optiplex 745). Appears that
Ubuntu doesn't use the rtc modules (rtc or genrtc) any more in my case,
since lsmod | grep rtc returns nothing.
--
Confirmed by various people (including me) in bug 198558 and bug 21295.
** Changed in: util-linux (Ubuntu)
Status: New = Confirmed
--
Could hwclock.sh fall back to using --directisa
https://bugs.launchpad.net/bugs/39959
You received this bug notification because you are a member of
Similar problem with 64 bit Ubuntu 7.10 Gutsy:
~$ sudo /etc/init.d/hwclock.sh restart
* Saving the system clock
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Clock is lagging about an hour a day.
--
Could
