Very Computer

by **mcarl..** » Fri, 08 Sep 2000 01:34:26

I started building some modules today, which caused me to notice a boot
problem with timezones.

My hardware clock is local time. /etc/timezone contains "US/Central"
(no quotes). /etc/default/rcS contains "UTC=no" (no quotes).

Once the system is booted, the time is correct.

The problem is that in rcS.d, S20modutils runs before S40hwclock.sh. It
is S40hwclock.sh that sets the time correctly, but S20modutils run
depmod, which regenerates /lib/modules/2.2.13/modules.dep with the
wrong time (5 hours too early). The files time is not my local time
(GMT-5),
nor is it GMT. It is being set to GMT-10. It is as if the HW clock was
GMT, and 5 hours are subtracted from it for local time.

This problem then causes modprobe to complain about /etc/modules.conf
being newer than modules.dep, which causes S20modutils to execute
the last if statement (modprobe ... -t boot \*) when it shouldn't
causing more error messages.

If I edit S20 and add "touch /testtime" I get the same thing. I need
the HW clock as local since the system is dual boot with Win98.

libc6 2.1.3-10, Debian potato.

Any suggestions?
Thanks
-Michael

Sent via Deja.com http://www.deja.com/
Before you buy.

by **composerofch..** » Fri, 08 Sep 2000 01:45:19

once i had the same think then i made a resetup said "do not change
my hrdware time "

> I started building some modules today, which caused me to notice a
boot
> problem with timezones.

> My hardware clock is local time. /etc/timezone contains "US/Central"
> (no quotes). /etc/default/rcS contains "UTC=no" (no quotes).

> Once the system is booted, the time is correct.

> The problem is that in rcS.d, S20modutils runs before S40hwclock.sh.
It
> is S40hwclock.sh that sets the time correctly, but S20modutils run
> depmod, which regenerates /lib/modules/2.2.13/modules.dep with the
> wrong time (5 hours too early). The files time is not my local time
> (GMT-5),
> nor is it GMT. It is being set to GMT-10. It is as if the HW clock
was
> GMT, and 5 hours are subtracted from it for local time.

> This problem then causes modprobe to complain about /etc/modules.conf
> being newer than modules.dep, which causes S20modutils to execute
> the last if statement (modprobe ... -t boot \*) when it shouldn't
> causing more error messages.

> If I edit S20 and add "touch /testtime" I get the same thing. I need
> the HW clock as local since the system is dual boot with Win98.

> libc6 2.1.3-10, Debian potato.

> Any suggestions?
> Thanks
> -Michael

> Sent via Deja.com http://www.deja.com/
> Before you buy.

Sent via Deja.com http://www.deja.com/
Before you buy.

by **Villy Kru** » Fri, 08 Sep 2000 17:00:29

On Wed, 06 Sep 2000 16:34:26 GMT,

Quote:>I started building some modules today, which caused me to notice a boot
>problem with timezones.

> My hardware clock is local time. /etc/timezone contains "US/Central"
>(no quotes). /etc/default/rcS contains "UTC=no" (no quotes).

> Once the system is booted, the time is correct.

> The problem is that in rcS.d, S20modutils runs before S40hwclock.sh. It
>is S40hwclock.sh that sets the time correctly, but S20modutils run
> depmod, which regenerates /lib/modules/2.2.13/modules.dep with the
>wrong time (5 hours too early). The files time is not my local time
>(GMT-5),
> nor is it GMT. It is being set to GMT-10. It is as if the HW clock was
>GMT, and 5 hours are subtracted from it for local time.

What happens if you push up hwclock.sh to, say, S10hwclock.sh ?

Villy

Very Computer

timezone problem during boot

timezone problem during boot

timezone problem during boot

timezone problem during boot