hwclock reports “Cannot access the Hardware Clock via any known method”
Bug #126893 reported by
Anders Kaseorg
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| util-linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: util-linux
I’m running gutsy amd64 on a Lenovo 3000 N100 laptop, and it won’t sync the hardware clock:
$ sudo /etc/init.
* 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.
$ sudo hwclock --show --debug
hwclock from util-linux-2.12r
hwclock: Open of /dev/rtc failed, errno=16: Device or resource busy.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.
Revision history for this message
| Anders Kaseorg (andersk) wrote | #1 |
| Changed in util-linux: | |
| status: | New → Invalid |
To post a comment you must log in.
The problem was that timidity was stopping at K99timidity after K25hwclock.sh, and holding the rtc device open so hwclock couldn’t access it. After purging and reinstalling timidity, timidity now stops at K01timidity, so I’m not sure how that happened. Anyway, closing this.