I done searches for "clock" and found similar threads, but no real fix that is working for me. My clock resets when I boot into linux. It does not happen in windows or bios even on cold boots. The battery is replaced and good** the old battery was by all measures dead (0.6v), but still seemed to have enough power for the clock, since windows tested fine with it.
I have tryed setting it to local time, UTC.. etc... My timezone is GMT (london). "sudo /sbin/hwclock --systohc" Although I have windows, I do not use it except the few times to test this, so no conflict.
when I was entering a sed command, with a back-reference to the scnd set of parenthesis. 2 reset X, or so I though ... I did some experimenting, and lo and behold, I could reproduce the behaviour even on the xdm login screen, when I typed in my sed expression as the name. Not every time, not accurately, but maybe 3 out of 10 times I can reset X by pressing 2 on the numeric row in a quick succession with other keys, and the I at first thought was required to trigger the behavior is not necessary at all. Nothing in the X-log, nothing in ~/.xsession-errors.
I'm annoyed, and as X is quite sizable and spawns a truckload of processes I'm highly reluctant to try and reproduce the behaviour under the control of strace (mind you, since it seems to be "speed" related it maybe wouldn't even occur under strace ;}). I'm running Slack64 13.0 on a Thinkpad R500 with an Intel GMA 4500MHD graphics chipset, can't think of anything else that might be special with this hardware in regards to X.
I added an ext4dev filesystem to my hard drive as /dev/sda3 and mounted at /share with the goal of putting all of my multimedia files on it and sharing it through NFS. I followed this guide: [url]
Of course, this was from lenny (hence the -dev). The partition was fine, and I mounted it numerous times. I also performed a dist-upgrade to squeeze. I shutdown that computer with the usual 'shutdown -h now' and disconnected the AC power cord from it, because I wasn't planning on using that machine for awhile. As far as I could determine, everything was fine before I unplugged it.
Every time that computer is powered off, the clock resets to 1999 because the battery is bad. So I am used to getting the "last mount time is in the future" error.
Three weeks after halting, I powered the computer back on. It was unplugged until this point. I got an error message when it attempted to mount /dev/sda3
I then removed its line from /etc/fstab, rebooted. and tried to check it, but I just keep getting the same error-- even with the '-b 8193' option.
The machine is still using the 2.6.26 kernel from lenny. I am building a new one right now (2.6.30), hoping that the problem is caused by the ext4dev/ext4 module. Otherwise I don't know what to do.
I have this problem for a while but didn't notice it until lately(i did reboot the machine for few months). Now that i reboot it frequently i notice that the clock is always not what is supposed to be. I'm in Toronto, Canada so it should be GMT -5:00. Sometimes it shows GMT-6, sometimes -10, now is GMT -11. Anyone would know why i have this issue? I'm running Suse11.1 on a 64 bit. My laptop which runs on 32 bit is working fine.(well probably different versions for kernel and kde.(whatever was in th repository to be updated i updated)
2.6.27.39-0.2-default Version 4.3.4 (KDE 4.3.4) "release 2"
if I have to reset my system for any reason or even logging out my pavucontrol resets to my built in audio instead of sticking to my HDMI like I want it to.I can manually configure a file I will, I just need to know where to start.I will provide hardware info when asked for it, just need a feeler here.I am running Debian Jessie KDE 64bit
I have recently installed ubuntu as my main operating system, everything has been working great except every time I re-boot the resolution resets back to a default. How can I get it to default to 1440x900?
I'm on 10.10 Everytime I start my iMac, the volume in alsamixer is reset to zero. It takes 8 seconds to fix, but I'd rather not have to do this every time I boot up. Anyone know how to fix this?
I have my clock set to use "Public Time Server (pool.ntp.org)" but it's actually off by 10 minutes (and I think it's getting off by more and more each day).I had previously had it set manually, but it was getting off by more and more every day, so I thought using automatic time set would fix the issue.
When installing I perhaps mistakingly told Fedora it should use the BIOS clock and now it shows the wrong time, 1 hour ahead of my time-zone GMT+0. If I try and go to the preferences and set the time the 'Advanced Options' one of which I need are grayed out, I need the 'Use local time source' option to be unchecked. Could somebody tell me a workaround or the command-line commands to tell it not to do this anymore?
Trying to adjust my clock settings!I am running KDE 4.4.3 on Squeeze, on an 64bit laptop.(I used the AMD64 net install version)How can I fix the time settings so it shows 5:00pm instead of 17:00:00So far I have not been able to find a cure
When I boot into Debian (lenny) my clock is always 4 hours slow. Whether I set it manually, or set it to get it's time from the network, the next time I boot into debian, it's back to being 4 hours slow.
I have dual boot on my comp. Windows XP and Fedora 11 Now in both systems time zone is set to Belgrade ( which is my time zone), but when I setup clock in fedora to be, let's say 16.15h, then when I swich to windows it says time is 14.15h. When I setup in windows on 16.15h, and I swich to fedora, it says time is 18.15h. So I can't get accurate time on both systems in no way.
By default, Fedora 11 sets my clock to military time. For example it says 16:22. I would like it to show civilian time (or at least know how to do it) I logged into the clock settings and had to put in the root password, but couldn't find where you do this. If you scroll on the time for hours, it just goes from 0 to 23 and back, not to AM and PM like some others.
Try as I might I cannot seem to get the system clock to display local time. It looks like it's stuck on GMT. In the System>Administration>Time and Date I have my local time zone set correctly and also set to update automatically with an appropriate time server selected. It still displays my local time +5 hours (I'm central time, USA).
I restored my .kde directory after changing some stuff unrelated to my clock and now all plasma clocks are exactly 5 hours faster than my system time (the correct time).I've set the time zone for Date&Time in System Settings properly and that's working well and I've ALSO gone into the time zone settings for the plasma widgets and switched between UTC and Local manually but that doesn't do anything.
I'm running windows 7 and the F12 Beta (although the same issue existed in my f11 distro) on an asus g71 bb. When ever I boot into windows my time is correct. If I boot into to F12 my time is wrong. Usually by 4 hours. If I change it in Linux when I boot into windows I end up switching the time on my windows partition. I tried searching the forum (rather casual I'll admit) and couldn't find any solutions.
I'd like to have two gnome clock applets, one with the regular default time and date in the upper right hand corner (the default) and another set to epoch time. However, I can't figure out how to set the second gnome clock applet to display the epoch time. I'm running FC12.
Dual boot system. Boot Linux Fedora 13 and the hardware clock is set to GMT. Boot Windows 7, time is wrong, as it expects the hardware clock to be set to the local time. reset the hardware clock each time I reboot in to the other O/S.
In Kubuntu 10.10, the clock is set to military time. I shouldn't have to do the math just to look at the clock. There is no setting anywhere to change it to normal time.
I am running Ubuntu 10.04.2 and I've got a problem with the Clock 2.30.2 applet not updating the time.
The only way I can get this to work is after logging on, removing the applet from the panel & the adding it back again. Not really a satisfactory "fix".
I recently noticed that the time displayed in the Gnome Clock applet is exactly (or nearly so) one second behind NTP time.I have a NTP server on my small network to which I sync my other PCs. Some of the applications I run are critical of time and need sub second accuracy - I am also a bit of Time Nut as well.My NTP server is OK. My PCs can sync to my NTP server OK. My applications which require precise time get the right time from NTP - BUT - the time displayed in the GNOME Clock applet is always behind one second!I have spent much time searching for others with similar problems and their solutions but so far nothing - hence my asking here, why do I see this behaviour and what can I do about it
I have cron jobs running and the timing is critical, because I'm running Nessus scans on production servers. If I hit them at the wrong time, I'm toast. But when I check the cron log, I see that it is an hour off. Here is the output for the command "clock": Wed 31 Mar 2010 03:01:26 PM CDT -0.257677 seconds
And this is the tail of the cron log: Mar 31 16:00:01 nes-001 CROND[8790]: (root) CMD (/Nessus/Targets/NessusScriptDataCenterScan.test) Mar 31 16:01:02 nes-001 CROND[8822]: (root) CMD (run-parts /etc/cron.hourly) Mar 31 16:01:02 nes-001 run-parts(/etc/cron.hourly)[8822]: starting 0anacron Mar 31 16:01:02 nes-001 anacron[8832]: Anacron started on 2010-03-31 Mar 31 16:01:02 nes-001 anacron[8832]: Normal exit (0 jobs run) Mar 31 16:01:02 nes-001 run-parts(/etc/cron.hourly)[8834]: finished 0anacron
Cron thinks it is 4:00 p.m., but it's really 3:00 p.m. How do I tell Cron what time it is? (Stopping and restarting the crond service did not change it.)
I'm having a problem with the time on one of my servers jumping forward into the future. We run serveral CentOS 5.4 servers running Xen, some up to date and some a little older. The one in question is running 2.6.18-164.el5xen, with xen-libs-3.0.3-94.el5_4.2 and xen-3.0.3-94.el5_4.2. On this server are several Xen virtual machines, also running CentOS 5.4 with kernel 2.6.18-164.el5xen. One in particular has problems with the clock keeping proper time.
We use NTP (ntpd) to sync time to a central server in the company. Our NTP set-up works fine, and we have problems on only a couple of servers out of many. The problem I see is that one one particular Xen virtual machine, the clock will suddenly jump forward into the future, usually by several minutes but once by more than an hour. This has obvious implications for software running on the machine. Software such as Oracle grid control agent will restart itself under the (incorrect) assumption that it has been hung for several minutes with no activity. Oracle database will cope gracefully, but applications that refer to the clock will be confused.
We detect these time jumps because we have Nagios checking the clock on each host against the centralised time server (Nagios's check_ntp plugin). Nagios will suddenly report a clock offset that is miles into the future. Following the time jump, ntpd on the host in question will re-sync the time. Ntpd keeps the time steady, ticking just a few milliseconds per second until real time catches up with the server. i.e. Nagios will report the time as being 10 minutes ahead, then a minute later the host will be 9 minutes ahead, and then a further minute later the host will be 8 minutes ahead of real time. The clock on the host stays running very slow until it eventually is correct.
