Re: [gentoo-user] after emerge -Du world date can't keep time
On Sun, 2005-09-11 at 20:41 -0700, maxim wexler wrote: Also, the BIOS clk is correct. How do you know that? what does hwclock tell you? -mw hum, run rc-status boot is clock started? check out /etc/conf.d/clock yup __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Nick Rout [EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] after emerge -Du world date can't keep time
--- Willie Wong [EMAIL PROTECTED] wrote: On Sun, Sep 11, 2005 at 08:41:31PM -0700, maxim wexler wrote: --- Willie Wong [EMAIL PROTECTED] wrote: On Sun, Sep 11, 2005 at 11:59:58AM -0700, maxim wexler wrote: Hello everybody, After emerge --deep --update world I compiled and installed the new kernel, 2.6.12-gentoo-r10, then I noticed that no matter when I boot the system, date always starts marking time at 6:00 AM, although it gets the date and zone right. No matter what time string I give to date(as root), after a re-boot it alway replies with 6AM plus whatever time has elapsed since the original boot. FWIW rtc support is compiled as a module and is *not* currently loaded. Also, the BIOS clk is correct. -mw hum, run rc-status boot is clock started? yup Let me check my understanding of the problem: 1) If you cold boot, the time starts at 6AM of the right day. A closer look: It appears 6AM was a one-off. Last night before shutdown I set the correct time. This morning at 9:17AM date gave 3:17 w/ correct day, date, time zone. So it looks like it's picking an hour at random but gets everything else correct. 2) If you reboot, the time counts from 6AM + the elapsed time of all previous reboots up until the last cold boot. whatever time has elapsed since first cold boot is added *correctly* to the incorrect original time every time I reboot. For instance, the clock on the wall says 12:40PM. I've just rebooted for the second time and date gives 6:40 which is what it *would* be if the original time, 3:17 had been correct, since approx two and a half hrs have elapsed. 3) Behaviours 1 and 2 doesn't change if you set the time yourself. i.e., on the next boot/reboot the same thing will happen. Does that summary seem correct? Yes. Whatever time string I give to date after rebooting, the clock resets to the original, wrong time after another reboot. BTW this applies to xclock as well. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] after emerge -Du world date can't keep time
--- Willie Wong [EMAIL PROTECTED] wrote: On Sun, Sep 11, 2005 at 08:41:31PM -0700, maxim wexler wrote: On Sun, Sep 11, 2005 at 11:59:58AM -0700, maxim wexler wrote: Hello everybody, After emerge --deep --update world I compiled and installed the new kernel, 2.6.12-gentoo-r10, then I noticed that no matter when I boot the system, date always starts marking time at 6:00 AM, although it gets the date and zone right. No matter what time string I give to date(as root), after a re-boot it alway replies with 6AM plus whatever time has elapsed since the original boot. FWIW rtc support is compiled as a module and is *not* currently loaded. Also, the BIOS clk is correct. -mw hum, run rc-status boot is clock started? yup what about the output from hwclock? run it as root, does it give the same time/date as date? the same. In fact when I update the time w/ date -s hwclock continues to give the incorrect one. Until a reboot when both will give the incorrect original time plus whatever time has elapsed since the first boot of the day. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] after emerge -Du world date can't keep time
On Mon, Sep 12, 2005 at 12:03:27PM -0700, maxim wexler wrote: what about the output from hwclock? run it as root, does it give the same time/date as date? the same. In fact when I update the time w/ date -s hwclock continues to give the incorrect one. Until a reboot when both will give the incorrect original time plus whatever time has elapsed since the first boot of the day. hum... fishy! On Mon, Sep 12, 2005 at 12:20:55PM -0700, maxim wexler wrote: check out /etc/conf.d/clock # /etc/conf.d/clock # Set CLOCK to UTC if your system clock is set to UTC (also known as # Greenwich Mean Time). If your clock is set to the local time, then # set CLOCK to local. CLOCK=UTC ^ | Problem #1. # If you wish to pass any other arguments to hwclock during bootup, # you may do so here. CLOCK_OPTS= # If you want to set the Hardware Clock to the current System Time # during shutdown, then say yes here. CLOCK_SYSTOHC=no ^ --- | | THIS is your problem #2. Date only manipulates the kernel clock. If you don't sync it with your hardware clock, how do you expect the computer to remember the change? During a power cycle, the kernel is not running, you know q= Also, I'd wager that your clock is consistently off by the same number of hours after each boot. Why? If the BIOS clock is correctly set to the time in your time-zone, you need to set CLOCK=local (see problem #1 above). Right now even though the BIOS clock is correct, the software thinks that the time it is keeping is Greenwich Mean Time, so it adds/subtracts the suitable number of hours according to your timezone. W -- This is obviously not how one does science, but in retrospect you get the right answer. ~DeathMech, S. Sondhi. P-town PHY 205 Sortir en Pantoufles: up 32 days, 1:07 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] after emerge -Du world date can't keep time
--- Willie Wong [EMAIL PROTECTED] wrote: On Mon, Sep 12, 2005 at 12:03:27PM -0700, maxim wexler wrote: what about the output from hwclock? run it as root, does it give the same time/date as date? the same. In fact when I update the time w/ date -s hwclock continues to give the incorrect one. Until a reboot when both will give the incorrect original time plus whatever time has elapsed since the first boot of the day. hum... fishy! On Mon, Sep 12, 2005 at 12:20:55PM -0700, maxim wexler wrote: check out /etc/conf.d/clock # /etc/conf.d/clock # Set CLOCK to UTC if your system clock is set to UTC (also known as # Greenwich Mean Time). If your clock is set to the local time, then # set CLOCK to local. CLOCK=UTC ^ | Problem #1. # If you wish to pass any other arguments to hwclock during bootup, # you may do so here. CLOCK_OPTS= # If you want to set the Hardware Clock to the current System Time # during shutdown, then say yes here. CLOCK_SYSTOHC=no ^ --- | | THIS is your problem #2. Thanks W, that works! Date only manipulates the kernel clock. If you don't sync it with your hardware clock, how do you expect the computer to remember the change? Dunno, but on another box(2.6.12-gentoo-r6) with the same settings date gives the correct, local time. During a power cycle, the kernel is not running, you know q= ? Also, I'd wager that your clock is consistently off by the same number of hours after each boot. Why? If the BIOS clock is correctly set to the time in your time-zone, you need to set CLOCK=local (see problem #1 above). Right now even though the BIOS clock is correct, the software thinks that the time it is keeping is Greenwich Mean Time, so it adds/subtracts the suitable number of hours according to your timezone. W -- This is obviously not how one does science, but in retrospect you get the right answer. ~DeathMech, S. Sondhi. P-town PHY 205 Sortir en Pantoufles: up 32 days, 1:07 -- gentoo-user@gentoo.org mailing list __ Yahoo! for Good Donate to the Hurricane Katrina relief effort. http://store.yahoo.com/redcross-donate3/ -- gentoo-user@gentoo.org mailing list
[gentoo-user] after emerge -Du world date can't keep time
Hello everybody, After emerge --deep --update world I compiled and installed the new kernel, 2.6.12-gentoo-r10, then I noticed that no matter when I boot the system, date always starts marking time at 6:00 AM, although it gets the date and zone right. No matter what time string I give to date(as root), after a re-boot it alway replies with 6AM plus whatever time has elapsed since the original boot. FWIW rtc support is compiled as a module and is *not* currently loaded. Also, the BIOS clk is correct. -mw __ Yahoo! for Good Watch the Hurricane Katrina Shelter From The Storm concert http://advision.webevents.yahoo.com/shelter -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] after emerge -Du world date can't keep time
On Sun, Sep 11, 2005 at 11:59:58AM -0700, maxim wexler wrote: Hello everybody, After emerge --deep --update world I compiled and installed the new kernel, 2.6.12-gentoo-r10, then I noticed that no matter when I boot the system, date always starts marking time at 6:00 AM, although it gets the date and zone right. No matter what time string I give to date(as root), after a re-boot it alway replies with 6AM plus whatever time has elapsed since the original boot. FWIW rtc support is compiled as a module and is *not* currently loaded. Also, the BIOS clk is correct. -mw hum, run rc-status boot is clock started? W -- Fucking shit, man, this is ridiculous. Ben...this is what Princeton is like: (mimes delivering a beating with a large, blunt object.) Wham, wham, wham. (mimes shaking hand.) Here's your degree. Except the 'Whams' take four years. Urgh... ~DeathMech, Some Student. P-town PHY 205 Sortir en Pantoufles: up 31 days, 2:12 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] after emerge -Du world date can't keep time
--- Willie Wong [EMAIL PROTECTED] wrote: On Sun, Sep 11, 2005 at 11:59:58AM -0700, maxim wexler wrote: Hello everybody, After emerge --deep --update world I compiled and installed the new kernel, 2.6.12-gentoo-r10, then I noticed that no matter when I boot the system, date always starts marking time at 6:00 AM, although it gets the date and zone right. No matter what time string I give to date(as root), after a re-boot it alway replies with 6AM plus whatever time has elapsed since the original boot. FWIW rtc support is compiled as a module and is *not* currently loaded. Also, the BIOS clk is correct. -mw hum, run rc-status boot is clock started? yup __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] after emerge -Du world date can't keep time
On Sun, Sep 11, 2005 at 08:41:31PM -0700, maxim wexler wrote: On Sun, Sep 11, 2005 at 11:59:58AM -0700, maxim wexler wrote: Hello everybody, After emerge --deep --update world I compiled and installed the new kernel, 2.6.12-gentoo-r10, then I noticed that no matter when I boot the system, date always starts marking time at 6:00 AM, although it gets the date and zone right. No matter what time string I give to date(as root), after a re-boot it alway replies with 6AM plus whatever time has elapsed since the original boot. FWIW rtc support is compiled as a module and is *not* currently loaded. Also, the BIOS clk is correct. -mw hum, run rc-status boot is clock started? yup what about the output from hwclock? run it as root, does it give the same time/date as date? W -- Tell me a story. I like stories. I read them a lot. I'm just a little girl, you know. I don't ever plan to grow up either. You hear? Never grow up! You lose too much... I had a parakeet once, named Violet. She was the only one left... We had four. Peter Pan and Lily went to live with some friends, so there were two. And then Pip died. I loved Pip... he might have been my favorite. So we buried him in the backyard, and then there was Violet. Then there was Harpo. He wanted to eat Violet. So she went to live in my third grade classroom... and stayed there to the end of her days. I went to visit Violet after I left the third grade occasionally, but then, well, I guess Harpo took her place, when he stopped biting so much and started being nice. Tell me a story. I like stories. ~S Sortir en Pantoufles: up 31 days, 7:59 -- gentoo-user@gentoo.org mailing list
