(In reply to comment #19)
> Are you sure this hasn't worked? hwclock runs twice during the boot process,
> once before modules are loaded, and one after. The second one should work.
Its obviously a timing issue. Removing the first call stops the error message
and the second call works fine.
(In reply to comment #19)
> Are you sure this hasn't worked? hwclock runs twice during the boot process,
> once before modules are loaded, and one after. The second one should work.
Its obviously a timing issue. Removing the first call stops the error message
and the second call works fine.