We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
On Tue, Jan 08, 2008 at 10:03:08PM -, Raphael Kraus wrote:
> This bug has appeared again for my AMD64 hardware in Gutsy (unsure of
> Feisty)
Has appeared again, or was never fixed?
If it was not fixed when this one was, then it's probably a different bug,
and you should file it separately rat
This bug has appeared again for my AMD64 hardware in Gutsy (unsure of
Feisty)
** Changed in: util-linux (Ubuntu)
Status: Fix Released => Incomplete
--
AMD64: Cannot access the Hardware Clock via any known method.
https://bugs.launchpad.net/bugs/8414
You received this bug notification beca
Sorry, this bug isn't fixed for me. :( :( :(
I'm hoping this will reopen the bug?
# hwclock --hctosys --utc --debug
hwclock from util-linux-ng 2.13
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
