Re: [SOLVED] Re: KDE clock showing 1 hour ahead
> sudo joe /etc/init.d/hwclock.sh > > At first line: HWCLOCKPARS= was blank, so added, with quotes: > "--directisa" > > and saved. > > I then ran sudo hwclock --directisa --systohc > > and then rebooted. thanks all. i was facing the same problem in Gnome, since i am using debian. now it's solved. thanks everybody. -- Arijit Sarkar Kolkata, India Evolution on Debian testing
[SOLVED] Re: KDE clock showing 1 hour ahead (on-going)
Andrew M.A. Cater wrote: On Sun, Jun 10, 2007 at 09:21:56AM +0100, andy wrote: A more general point - you, and I, need to read up on the way that Debian does the init scripts :) Try editing /etc/init.d/hwclock.sh and /etc/init.d/hwclockfirst.sh They are well commented and HWCLOCKPARS is one of the first lines :) (You _might_ be able to do it just by passing the appropriate environment variable - but this early in the boot sequence I wouldn't like to bet on it and it's a one-off edit0 These, in turn, are called from the start up script at /etc/init.d/rcS.d/S11hwclock.sh so you might want to edit that one as well :) Does this help? Andy (Cater) since there are two andys talking to one another here and it gets confusing :) Andy Thanks so much - your suggestion worked: sudo joe /etc/init.d/hwclock.sh At first line: HWCLOCKPARS= was blank, so added, with quotes: "--directisa" and saved. I then ran sudo hwclock --directisa --systohc and then rebooted. This time, on the terminating messages there was no more timing out nor again on the start up and, when logging in, the time was accurate. Well done and many thanks! Andy (Wolfe) -- "If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow"
Re: KDE clock showing 1 hour ahead (on-going)
On Sun, Jun 10, 2007 at 09:21:56AM +0100, andy wrote: > andy wrote: > >andy wrote: > >>Andrew M.A. Cater wrote: > >>>As root > >>> > >>> tzconfig > >>> > >>>Set the time to UTC (probably under 12 - other time zones) > >>> > >>> hwclock --systohc > >>> > >>>Set the BIOS clock to UTC > >>> > >>>In KDE, set the clock to use local time zone and point that at > >>>Europe/London > >>> > >>>Hope this helps, > >>> > >>>Andy > >>> > >>> > >>> > >>> > >>> > >>Thanks Andy > >> > >>I sudo tzconfig and adjusted it specifically to Europe/London then > >>entered sudo hwclock --systohc and after a pause got a message back > >>"select() to /dev/rtc to wait for clock tick timed out" > >>I rebooted the machine, and saw the same message in the closing > >>messages when it reached the point about saving system time. Checked > >>in the BIOS, which is giving the correct time. Loaded KDE and went to > >>configure the clock and it still reports TZ as Guernsey. I ran > >>tzconfig again and this time it reported /Europe/London. > >>Unfortunately, the clock is still 1 hour ahead, despite this. > >> > >Some additional info on this. It would appear that it is a bug in > >Ubuntu Dapper ( linux-source-2.6.15 ): > > > >https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/43661/+viewstatus > > > >"Dapper seems unable to read or set my RTC on an IBM/Lenovo X60 thinkpad. > >The BIOS shows the hardware clock to be several hours different to the > >Linux clock." This is as far as the similarity goes though. > > > >It also looks like Dell laptops have kicked up a series of related > >errors, but my wife's machine is not a Dell. > > > >I'd want to post this as a bug, but I don't get the impression that > >many others are experiencing this fault. If it is related to the RTC, > >I have no idea how to fix that up. > > > >Any clues? > > > Following up on Andy's suggestion, I entered hwclock --directisa > --systohc at the command line as sudo. No error messages were reported > and the command line prompt returned. > > However, I'm not clear on the second part of Andy's suggestion. How do I > pass HWCLOCKPARS="--directisa" to /etc/default/rc5 ? > > Any pointers, please? > > Thanks > > A > A more general point - you, and I, need to read up on the way that Debian does the init scripts :) Try editing /etc/init.d/hwclock.sh and /etc/init.d/hwclockfirst.sh They are well commented and HWCLOCKPARS is one of the first lines :) (You _might_ be able to do it just by passing the appropriate environment variable - but this early in the boot sequence I wouldn't like to bet on it and it's a one-off edit0 These, in turn, are called from the start up script at /etc/init.d/rcS.d/S11hwclock.sh so you might want to edit that one as well :) Does this help? Andy (Cater) since there are two andys talking to one another here and it gets confusing :) > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE clock showing 1 hour ahead (on-going)
andy wrote: andy wrote: Andrew M.A. Cater wrote: As root tzconfig Set the time to UTC (probably under 12 - other time zones) hwclock --systohc Set the BIOS clock to UTC In KDE, set the clock to use local time zone and point that at Europe/London Hope this helps, Andy Thanks Andy I sudo tzconfig and adjusted it specifically to Europe/London then entered sudo hwclock --systohc and after a pause got a message back "select() to /dev/rtc to wait for clock tick timed out" I rebooted the machine, and saw the same message in the closing messages when it reached the point about saving system time. Checked in the BIOS, which is giving the correct time. Loaded KDE and went to configure the clock and it still reports TZ as Guernsey. I ran tzconfig again and this time it reported /Europe/London. Unfortunately, the clock is still 1 hour ahead, despite this. Some additional info on this. It would appear that it is a bug in Ubuntu Dapper ( linux-source-2.6.15 ): https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/43661/+viewstatus "Dapper seems unable to read or set my RTC on an IBM/Lenovo X60 thinkpad. The BIOS shows the hardware clock to be several hours different to the Linux clock." This is as far as the similarity goes though. It also looks like Dell laptops have kicked up a series of related errors, but my wife's machine is not a Dell. I'd want to post this as a bug, but I don't get the impression that many others are experiencing this fault. If it is related to the RTC, I have no idea how to fix that up. Any clues? Following up on Andy's suggestion, I entered hwclock --directisa --systohc at the command line as sudo. No error messages were reported and the command line prompt returned. However, I'm not clear on the second part of Andy's suggestion. How do I pass HWCLOCKPARS="--directisa" to /etc/default/rc5 ? Any pointers, please? Thanks A -- "If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow"
Re: KDE clock showing 1 hour ahead
On Sat, 09 Jun 2007 20:56:03 +0100 andy <[EMAIL PROTECTED]> wrote: > andy wrote: > > Andrew M.A. Cater wrote: > >> As root > >> > >>tzconfig > >> > >> Set the time to UTC (probably under 12 - other time zones) > >> > >>hwclock --systohc > >> > >> Set the BIOS clock to UTC > >> > >> In KDE, set the clock to use local time zone and point that at > >> Europe/London > >> > >> Hope this helps, > >> > >> Andy > >> > >> > >> > >> > >> > > Thanks Andy > > > > I sudo tzconfig and adjusted it specifically to Europe/London then > > entered sudo hwclock --systohc and after a pause got a message back > > "select() to /dev/rtc to wait for clock tick timed out" > > I rebooted the machine, and saw the same message in the closing > > messages when it reached the point about saving system time. Checked > > in the BIOS, which is giving the correct time. Loaded KDE and went to > > configure the clock and it still reports TZ as Guernsey. I ran > > tzconfig again and this time it reported /Europe/London. > > Unfortunately, the clock is still 1 hour ahead, despite this. > > > Some additional info on this. It would appear that it is a bug in Ubuntu > Dapper ( linux-source-2.6.15 ): > > https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/43661/+viewstatus > > "Dapper seems unable to read or set my RTC on an IBM/Lenovo X60 thinkpad. > The BIOS shows the hardware clock to be several hours different to the > Linux clock." This is as far as the similarity goes though. > > It also looks like Dell laptops have kicked up a series of related > errors, but my wife's machine is not a Dell. > > I'd want to post this as a bug, but I don't get the impression that many > others are experiencing this fault. If it is related to the RTC, I have > no idea how to fix that up. There's been a discussion of this issue for several years already in the Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=277298 > > Any clues? > > Cheers > > A Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE clock showing 1 hour ahead
andy wrote: Andrew M.A. Cater wrote: As root tzconfig Set the time to UTC (probably under 12 - other time zones) hwclock --systohc Set the BIOS clock to UTC In KDE, set the clock to use local time zone and point that at Europe/London Hope this helps, Andy Thanks Andy I sudo tzconfig and adjusted it specifically to Europe/London then entered sudo hwclock --systohc and after a pause got a message back "select() to /dev/rtc to wait for clock tick timed out" I rebooted the machine, and saw the same message in the closing messages when it reached the point about saving system time. Checked in the BIOS, which is giving the correct time. Loaded KDE and went to configure the clock and it still reports TZ as Guernsey. I ran tzconfig again and this time it reported /Europe/London. Unfortunately, the clock is still 1 hour ahead, despite this. Some additional info on this. It would appear that it is a bug in Ubuntu Dapper ( linux-source-2.6.15 ): https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/43661/+viewstatus "Dapper seems unable to read or set my RTC on an IBM/Lenovo X60 thinkpad. The BIOS shows the hardware clock to be several hours different to the Linux clock." This is as far as the similarity goes though. It also looks like Dell laptops have kicked up a series of related errors, but my wife's machine is not a Dell. I'd want to post this as a bug, but I don't get the impression that many others are experiencing this fault. If it is related to the RTC, I have no idea how to fix that up. Any clues? Cheers A -- "If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow"
Re: KDE clock showing 1 hour ahead
On Sat, Jun 09, 2007 at 19:24:04 +0100, andy wrote: > Andrew M.A. Cater wrote: [...] >> As root >> >> tzconfig >> >> Set the time to UTC (probably under 12 - other time zones) >> >> hwclock --systohc >> Set the BIOS clock to UTC >> >> In KDE, set the clock to use local time zone and point that at >> Europe/London >> >> Hope this helps, >> >> Andy >> >> >> >> >> > Thanks Andy > > I sudo tzconfig and adjusted it specifically to Europe/London then entered > sudo hwclock --systohc and after a pause got a message back "select() to > /dev/rtc to wait for clock tick timed out" > I rebooted the machine, and saw the same message in the closing messages > when it reached the point about saving system time. Checked in the BIOS, > which is giving the correct time. Loaded KDE and went to configure the > clock and it still reports TZ as Guernsey. I ran tzconfig again and this > time it reported /Europe/London. Unfortunately, the clock is still 1 hour > ahead, despite this. Try hwclock --directisa --systohc instead. If that gets rid of the "select() to /dev/rtc ..." error message then you can add the line HWCLOCKPARS="--directisa" to /etc/default/rcS and the time should stay correct across reboots. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE clock showing 1 hour ahead
Andrew M.A. Cater wrote: On Sat, Jun 09, 2007 at 06:36:59PM +0100, andy wrote: Roberto C. Sánchez wrote: On Sat, Jun 09, 2007 at 06:06:38PM +0100, andy wrote: Greetings Debianistas My wife's machine (Debian Etch, clean install) is consistently showing Europe/Guernsey (BST) in its clock settings and somehow this is always one hour ahead of real time. I have checked the BIOS clock which is set to the regular time and I don't think that it is set to UTC. Also, the time-zone should read Europe/London. I have tried numerous ways of altering this, even killing off gdm so that I can login as root to fix it in Gnome. Then, reboot, and it's back to being 1 hour ahead again. What can I do to fix this, as it is a real PITA to keep having to fix it for her, and let's face it, it shouldn't be necessary to do so. Is the timezone set in her environment? What does /etc/localtime link to? Regards, -Roberto Hi Roberto How do I find out what /etc/localtime links to? It is a binary file. There doesn't appear to be a config file, nor any man pages. Thanks A -- "If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow" As root tzconfig Set the time to UTC (probably under 12 - other time zones) hwclock --systohc Set the BIOS clock to UTC In KDE, set the clock to use local time zone and point that at Europe/London Hope this helps, Andy Thanks Andy I sudo tzconfig and adjusted it specifically to Europe/London then entered sudo hwclock --systohc and after a pause got a message back "select() to /dev/rtc to wait for clock tick timed out" I rebooted the machine, and saw the same message in the closing messages when it reached the point about saving system time. Checked in the BIOS, which is giving the correct time. Loaded KDE and went to configure the clock and it still reports TZ as Guernsey. I ran tzconfig again and this time it reported /Europe/London. Unfortunately, the clock is still 1 hour ahead, despite this. A -- "If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow"
Re: KDE clock showing 1 hour ahead
Roberto C. Sánchez wrote: On Sat, Jun 09, 2007 at 07:04:51PM +0100, andy wrote: ZONE_TMP_FILE=`mktemp` && find /usr/share/zoneinfo/ -type f -print0 |xargs -0 md5sum >>$ZONE_TMP_FILE && grep `md5sum /etc/localtime |cut -f1 -d\ ` $ZONE_TMP_FILE && rm -f $ZONE_TMP_FILE 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/Europe/London Hmm, that is what you thought it was supposed to be set to, correct? Does your clock program have some sort of settings within the application for timezone or daylight savings time? Regards, -Roberto Not that I can discern. In the KDE clock settings (accessible as root) the TZ is always set to Guernsey and identifies itself as BST (British summer time). As noted previously, the BIOS shows the correct time so it would seem that somewhere between the BIOS time setting and the loading of Etch that either the system gains an hour (?), or is switching to UTC (which might push it forward an hour) or has got its notion of BST screwed up. However, on my machine all is fine. Go figure! It does have me stumped! A -- "If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow"
Re: KDE clock showing 1 hour ahead
On Sat, Jun 09, 2007 at 07:04:51PM +0100, andy wrote: > > ZONE_TMP_FILE=`mktemp` && find /usr/share/zoneinfo/ -type f -print0 |xargs > -0 md5sum >>$ZONE_TMP_FILE && grep `md5sum /etc/localtime |cut -f1 -d\ ` > $ZONE_TMP_FILE && rm -f $ZONE_TMP_FILE > > 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/Europe/London Hmm, that is what you thought it was supposed to be set to, correct? Does your clock program have some sort of settings within the application for timezone or daylight savings time? Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: KDE clock showing 1 hour ahead
Roberto C. Sánchez wrote: On Sat, Jun 09, 2007 at 06:36:59PM +0100, andy wrote: Hi Roberto How do I find out what /etc/localtime links to? It is a binary file. There doesn't appear to be a config file, nor any man pages. Interesting. On one system of mine it is a binary file, yet on the other it is a symlink to /usr/share/zoneinfo/US/Eastern. Since you say that /etc/localtime is not a symlink, this little snippet will tell you which zoneinfo files it matches: ZONE_TMP_FILE=`mktemp` && find /usr/share/zoneinfo/ -type f -print0 |xargs -0 md5sum >>$ZONE_TMP_FILE && grep `md5sum /etc/localtime |cut -f1 -d\ ` $ZONE_TMP_FILE && rm -f $ZONE_TMP_FILE Just copy it and paste it at a bash prompt. Post the output here. Regards, -Roberto ONE_TMP_FILE=`mktemp` && find /usr/share/zoneinfo/ -type f -print0 |xargs -0 md5sum >>$ZONE_TMP_FILE && grep `md5sum /etc/localtime |cut -f1 -d\ ` $ZONE_TMP_FILE && rm -f $ZONE_TMP_FILE 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/posix/GB 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/posix/GB-Eire 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/posix/Europe/Belfast 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/posix/Europe/Jersey 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/posix/Europe/Guernsey 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/posix/Europe/London 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/posix/Europe/Isle_of_Man 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/GB 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/GB-Eire 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/Europe/Belfast 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/Europe/Jersey 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/Europe/Guernsey 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/Europe/London 4c9f9c5c5f86bcc5465c08831ef59e75 /usr/share/zoneinfo/Europe/Isle_of_Man -- "If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow"
Re: KDE clock showing 1 hour ahead
On Sat, Jun 09, 2007 at 06:36:59PM +0100, andy wrote: > Roberto C. Sánchez wrote: > >On Sat, Jun 09, 2007 at 06:06:38PM +0100, andy wrote: > > > >>Greetings Debianistas > >> > >>My wife's machine (Debian Etch, clean install) is consistently showing > >>Europe/Guernsey (BST) in its clock settings and somehow this is always > >>one hour ahead of real time. > >>I have checked the BIOS clock which is set to the regular time and I > >>don't think that it is set to UTC. Also, the time-zone should read > >>Europe/London. I have tried numerous ways of altering this, even killing > >>off gdm so that I can login as root to fix it in Gnome. Then, reboot, > >>and it's back to being 1 hour ahead again. > >> > >>What can I do to fix this, as it is a real PITA to keep having to fix it > >>for her, and let's face it, it shouldn't be necessary to do so. > >> > >> > >Is the timezone set in her environment? What does /etc/localtime link > >to? > > > >Regards, > > > >-Roberto > > > > > Hi Roberto > > How do I find out what /etc/localtime links to? It is a binary file. > There doesn't appear to be a config file, nor any man pages. > > Thanks > > A > > -- > > "If they can get you asking the wrong questions, they don't have to worry > about the answers." - Thomas Pynchon, "Gravity's Rainbow" > As root tzconfig Set the time to UTC (probably under 12 - other time zones) hwclock --systohc Set the BIOS clock to UTC In KDE, set the clock to use local time zone and point that at Europe/London Hope this helps, Andy
Re: KDE clock showing 1 hour ahead
On Sat, Jun 09, 2007 at 06:36:59PM +0100, andy wrote: > > > Hi Roberto > > How do I find out what /etc/localtime links to? It is a binary file. > There doesn't appear to be a config file, nor any man pages. > Interesting. On one system of mine it is a binary file, yet on the other it is a symlink to /usr/share/zoneinfo/US/Eastern. Since you say that /etc/localtime is not a symlink, this little snippet will tell you which zoneinfo files it matches: ZONE_TMP_FILE=`mktemp` && find /usr/share/zoneinfo/ -type f -print0 |xargs -0 md5sum >>$ZONE_TMP_FILE && grep `md5sum /etc/localtime |cut -f1 -d\ ` $ZONE_TMP_FILE && rm -f $ZONE_TMP_FILE Just copy it and paste it at a bash prompt. Post the output here. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: KDE clock showing 1 hour ahead
Roberto C. Sánchez wrote: On Sat, Jun 09, 2007 at 06:06:38PM +0100, andy wrote: Greetings Debianistas My wife's machine (Debian Etch, clean install) is consistently showing Europe/Guernsey (BST) in its clock settings and somehow this is always one hour ahead of real time. I have checked the BIOS clock which is set to the regular time and I don't think that it is set to UTC. Also, the time-zone should read Europe/London. I have tried numerous ways of altering this, even killing off gdm so that I can login as root to fix it in Gnome. Then, reboot, and it's back to being 1 hour ahead again. What can I do to fix this, as it is a real PITA to keep having to fix it for her, and let's face it, it shouldn't be necessary to do so. Is the timezone set in her environment? What does /etc/localtime link to? Regards, -Roberto Hi Roberto How do I find out what /etc/localtime links to? It is a binary file. There doesn't appear to be a config file, nor any man pages. Thanks A -- "If they can get you asking the wrong questions, they don't have to worry about the answers." - Thomas Pynchon, "Gravity's Rainbow"
Re: KDE clock showing 1 hour ahead
On Sat, Jun 09, 2007 at 06:06:38PM +0100, andy wrote: > Greetings Debianistas > > My wife's machine (Debian Etch, clean install) is consistently showing > Europe/Guernsey (BST) in its clock settings and somehow this is always > one hour ahead of real time. > I have checked the BIOS clock which is set to the regular time and I > don't think that it is set to UTC. Also, the time-zone should read > Europe/London. I have tried numerous ways of altering this, even killing > off gdm so that I can login as root to fix it in Gnome. Then, reboot, > and it's back to being 1 hour ahead again. > > What can I do to fix this, as it is a real PITA to keep having to fix it > for her, and let's face it, it shouldn't be necessary to do so. > Is the timezone set in her environment? What does /etc/localtime link to? Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
