On Wed, Oct 24, 2001 at 06:19:09AM +0200, Robert Bar wrote:
> At 13:16 Uhr -0400 23.10.2001, Daniel Jacobowitz wrote:
> > (...)
> > John, what kernel/machine do you have hwclock causing a hang? I'm not
> > sure off the top of my head what the status is in 2.2, but 2.4 has a
> > "proper" /dev/rtc driver. We should be using hwclock. Clock is an
> > awful ADB-bit-bashing hack that needs to die.
>
> may be we're talking about different problems ('cause of English is
> only my very second language ...):
>
> i'm running debian 2.4.8/testing on an upgraded 7500/G3/400 and have
> to press "F13" at boottime:
>
> System time was (...)
> Setting the System Clock using the Hardware Clock as reference...
> Real Time Clock Driver v1.10d
> (point of lack, skipping via "F13")
> Real Time set. System local Time is now (...) CET
> (... and continuing boot-procedure)
>
>
> ... since updating a week ago (or so ...).debian 2.4 kernel images had both CONFIG_RTC and CONFIG_PPC_RTC enabled as modules, and modutils `helpfully' (in the MacOS sense) loads the wrong one every time. i think drow finally fixed that in the latest 2.4 kernel-image packages, but you generally have to manually upgrade kernel packages (its probably only fixed in 2.4.10 or 2.4.12, whichever is packaged). -- Ethan Benson http://www.alaska.net/~erbenson/
pgpzfuCKYFZHR.pgp
Description: PGP signature
