[Intrepid] Unable to set System Clock to....

Bug #251334 reported by Alessandro Ghersi
2
Affects Status Importance Assigned to Milestone
util-linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Intrepid 64bit updated today

 When the kernel starts appears:
Unable to set System Clock to (time and date)
cannot access the Hardware Clcok via any known method
Use the --debug option to see the details of our search for an access method.
Unable to set system clock to: (time and date)

Important: this issue is also present in Hardy with kernel 2.6.26 vanilla but is not present with 2.6.24-19- generic and -20-generic

Revision history for this message
Alessandro Ghersi (alessandro-ghersi) wrote :
Revision history for this message
Alessandro Ghersi (alessandro-ghersi) wrote :
Revision history for this message
Luca Carrogu (motoplux) wrote :

I solved modifying
/etc/init.d/hwclockfirst.sh
and
/etc/init.d/hwclock.sh
changing the line
HWCLOCKPARS=
in
HWCLOCKPARS="--directisa"

Revision history for this message
markoa (marko-marko) wrote :

I also had a problem with incorrect system time since a clean install of Intrepid. The hack above seems to have fixed it.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

We fixed this in jaunty with the move to using hwclock --systz which no longer accesses the hardware clock on startup

Changed in util-linux (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.