Fedora :: Clock Gives Wrong Times When Reboot
Aug 24, 2009So every time I reboot into Fedora11 the clock is wrong.Any idea what might be causing it to keep resetting and what I can do to correct the issue?
View 6 RepliesSo every time I reboot into Fedora11 the clock is wrong.Any idea what might be causing it to keep resetting and what I can do to correct the issue?
View 6 RepliesI'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.
View 10 Replies View RelatedDual 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.
View 5 Replies View RelatedI have a strange problem with my Ubuntu Natty virtual machine running under VirtualBox on OSX.One day last week, my clock on the top bar in Gnome stopped displaying the correct time (I'm not running Unity). I'm on GMT, so right now it should be 9:31, but it's showing 3:31, so I think it's something to do with TimeZones. If I go into the date and time applet, the time is initially wrong but after a second sets itself to the correct GMT Time. The timezone is correclty set as London and it makes no difference if I unlock and set it again or select manual or automatic from internet time.
From a bash prompt, the "date" command shows: "Tue Sep 20 03:33:35 CDT 2011".If I run "sudo dpkg-reconfigure tzdata" I am correctly set as London. Upon exiting the commnand I'm shown the correct London time, but then typing "date" again shows the CDT time again.The clock is correct in OSX. This has been working fine for a month or two - I think it stopped working after an update last week. Any ideas?
Everytime I reboot Ubuntu,the clock is behind by two hours and needs to be manually set. Is there a way to fix this?
View 6 Replies View RelatedPretty much what the title says. Everytime I reboot Ubuntu,the clock is behind by two hours and needs to be manually set.
View 9 Replies View RelatedI've set-up dual boot on my laptop. Ubuntu installed first, then Windows 7 so it uses Grub2 to control the booting on start-up. I've noticed that my system clock goes out by an hour on both OS's, I change the clock to correct time & on reboot the time is usually (not always straight away) an hour behind. Has anyone else had this problem & know how to fix it?
View 4 Replies View RelatedBeen using Sound Recorder and set it to save as:CD Quality, MP3(.mp3 type)but it saves it as, 40 kbps and shows the time as 9 minutes 33 seconds when the correct time is really 2 minutes 39 seconds!Is there some plugin that will correct this to show the standard (128, 160, 192, 320) Bitrates and show accurate song times?
View 3 Replies View RelatedI had been manually starting my wireless network with "sudo iwconfig wlan0 essid "my wireless router id". The network would start and work flawlessly for weeks at a time. I can't ask my wife to find the essid in the terminal and then start wireless manually when I'm not here. She hates and fears the terminal. So I downloaded gnome network manager for a point and click interface on gnome panel.The network would start fine but shut down after anywhere from one to six hours. It would then refuse to restart manually or otherwise. I completely uninstalled network manager and tried wicd instead. The same basic problem is happening. The network will restart if I reboot the computer. My system:
Desktop computer acting as proxy server for the internet. Internet connection is by a dial up modem. This computer uses a wireless pci card connected to a dedicated hub. This is for file sharing via nfs. The OS is ubuntu 9.10. My wife's computer sharing the internet using a proxy to my computer. File sharing via nfs and a wireless card. Also running ubuntu 9.10. This same basic system worked flawlessly under Ubuntu Hardy.My desktop was updated recently with new hardware which created the need to move to Ubuntu Karmic. Some hardware was too new for hardy to deal with.
I have recently come across a Debian installation page for powerpc: viewtopic.php?t=20481. It got me motivated to fix the Debian I have on my iBook G4. I have a Debian Lenny installed on my iBook G4 -- but I have been having some sort of problem (mostly likely due to hardware) which causes the system to crash. After the latest crash, the clock on iBook has been readjusted. For this reason, I cannot reboot Debian completely.
Every time I turn on the computer it begins the booting process but before I get to my desktop I encounter numerous error messages concerning my clock. After either OK'ing or canceling these error messages, I get to my desktop but the system by then is either frozen or else not working at all. Worse, I can't even turn off the computer since the upper right corner of the desktop is completely blank and I have no menu to turn off or reboot the system.
It took this computer to a local Apple store and they ran many different hardware diagnostic tests on it. They concluded there's "technically" nothing wrong with the computer. But they said although the system has successfully passed all hardware tests, there may still remain some complicated but slight hardware glitch/es which the hardware diagnostics could not pick up.
Every time I reboot my computer the system time always comes up exactly 10 hours behind where it should be. So if I reboot it at 16:00 it comes up as 06:00.
This has only been happening since I got back from a trip to Australia, where I naturally changed the computer's timezone to match the local one. I'm now back in Central European Time which is 10 hours behind Australia's. This is on opensuse 11.3.
I've used the YAST date and time tool to set the timezone correctly, and /etc/localtime is set correctly:
Code:
:~> sha1sum /etc/localtime
b065fae6bda0f0642ca6a52b665768e34a99d213 /etc/localtime
:~> sha1sum /usr/share/zoneinfo/Europe/Berlin
b065fae6bda0f0642ca6a52b665768e34a99d213 /usr/share/zoneinfo/Europe/Berlin
[Code].....
Every time I reboot my computer the system time always comes up exactly 10 hours behind where it should be. So if I reboot it at 16:00 it comes up as 06:00.
This has only been happening since I got back from a trip to Australia, where I naturally changed the computer's timezone to match the local one. I'm now back in Central European Time which is 10 hours behind Australia's. This is on opensuse 11.3.
I've used the YAST date and time tool to set the timezone correctly, and /etc/localtime is set correctly:
Code:
:~> sha1sum /etc/localtime
b065fae6bda0f0642ca6a52b665768e34a99d213 /etc/localtime
:~> sha1sum /usr/share/zoneinfo/Europe/Berlin
b065fae6bda0f0642ca6a52b665768e34a99d213 /usr/share/zoneinfo/Europe/Berlin
[Code]....
A couple of days ago I asked why my pc changes the wireless card name.It switches between AR9285 ( right) and AR5008 ( wrong). Well, it is not the case. When system identified with AR9285,it loads ath9k and I can connect to the router. When system identifies my card as AR5008, no kernel module is present at all ( lspci -k). The wrong card name occurs only when system rebooted. If I gracefully shut down the system, it always comes up with a right name for the card( AR9285). So, how to force the system identify my card right no matter if I reboot or shut down?
View 1 Replies View RelatedI've been running arch linux, with my clock set to UTC with no problem. Recently I installed slackware on a different partition. During the setup I chose to set my clock to 'local time' instead of UTC by accident. Now in slackware my clock shows the wrong time. Also in arch it shows the same wrong time.
I booted back into slackware and ran pkgtool to enter the setup again, and changed my time to UTC. But this makes no difference. My clock is still wrong in both slackware and arch. Do I need to reboot after changing my clock settings in slackware before it takes effect? how the clock or the setup works.
System time was drifting ahead increasingly for several days time in the end. This is what I did with the clock about 6 hours "in the future":
Quote:
sntp -P no -r pool.ntp.org
hwclock --systohc
i.e. I got the (more or less) exact time from the time server and set the hardware / BIOS timer with this value.I renamed "/etc/adjtime" to beginn with a clean slate. During reboot (shut down phase) I noticed a message saying something like: "hwclock set to system time". I checked in the BIOS and there was a new time about one hour early(!). The boot phase then reset the time again, this time several hours forward (usually two to six hours). This is an iterating process, with a net gain of several hours per boot. It is not always whole hours -- like in a time zone error but it involves also minutes. System is set to UTC as affirmed by the "date" command. What could be the cause of this behaviour of the clock / timer?
My systemd-udev-settle.service is failing for some reason.
systemctl status systemd-udev-settle.service -a output
Code: Select all● systemd-udev-settle.service - udev Wait for Complete Device Initialization
Loaded: loaded (/lib/systemd/system/systemd-udev-settle.service; static)
[ode]...
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I'm using a very simple conky script to diplay the date and time on my desktop. I've noticed that he conky clock is a few seconds early compared to the time displayed in the right hand side of the top panel (Natty). I guess both displays are based on the same "internal" time, so I'm left wondering how this could happen, and how to sync back the clocks.
It seems that Conky is in sync with the system date, while the panel clock is 2 seconds late (on my system). Checked with while true; do date; sleep 0.1; done
Just curious as to if it is possible to have the clock in the center of the task bar centered clock in Ubuntu 11.04?
View 1 Replies View RelatedDoes anyone know of an interface to a quartz clock that can be used for a TOD clock?? I want to interface it to an Arduino board. Can be GPIO or USB.
View 1 Replies View RelatedI had cloned a centos 5.6 installation from virtualbox virtual machine to physical box. Everything work fine. However, the time showing in os using date command differs from bios time by roughly 4 hours. I am running ntp services which sync the time with another centos server on the network. It appears that some services are using virtual clock and some use physical clock. How do I get rid of virtual clock and only use physical clock?
View 1 Replies View Relatedlast -a shows server rebooted, how to identify the source or cause of reboot? thx reboot system boot Wed Feb 16 08:52 (02:0 2.6.21.7-2.fc8xen
View 2 Replies View RelatedI have bumped into a rather bizarre problem on a redhat system at work:I have mapped 10 LUNS to a server.The server has 2 HBAs, but the luns were mapped only to 1 HBA,and only one HBA is connected with a fibre cable.Every lun has only 1 path,the storage array management software (hitachi storage)confirms this.However, instead of 10 luns, I am seeing 40 luns!
- this is the output of the command ll /dev/sd*:
ll /dev/sd*
brw-r----- 1 root disk 8, 0 Mar 17 15:11 /dev/sda
[code]....
i set my clock with this command-/usr/sbin/ntpdate -v ntp-1.mcs.anl.gov ntp-2.mcs.anl.gov
but my clock changes to incorrect time when i restart my system,how can i make it stable?
what's happened. I now have to log-in 7 times (at least) before I can finally get in to fedora 11. It only started happening at the week-end after a patch was installed. what's going on?
View 5 Replies View RelatedWhen 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?
View 2 Replies View RelatedEverytime i switch between XP and Fedora, my system clock changes with +/- 2 hours.... So I have to adjust my system time everytime.
View 2 Replies View RelatedI've never had this happen to me before on any Linux boxes and I'm totally stumped: at random times, seemingly not at all to do with the applications open or number of windows...X crashes. This happened once every 2 weeks or so a couple of months ago...now it seems to happen 2-3 times every 24 hours.
I do not remember installing nvidia drivers. But I may have. How can I check this?
And more importantly, what things can I do to get to the bottom of why this keeps happening? It's just X crashing -- the system is not bricked. I can ssh in from another machine. But X is locked up so tightly even the mouse doesn't move.
I have had lots of problems with dual boot. Hardly never making success with first boot. I have to try 3,4,5 even 6 times until reach the X. Some kernels make it better (hardly never succesful boot with first try). This 2.6.34.7-56.fc13.i686.PAE seems to be one of the worst.
Boot hangs on starting atd. Xorg.conf:
I have to use nvidia proprietary driver. With nv the screen will freezy quite soon.
Graphic card: Nvidia 9500 GT
I've been running a fedora server for over a year now, and has seen some very strange issue, that really make it uncomfortable to use, and that I cannot manage to solve easily.
The problem is as follow : sometimes (every 20-30 minutes or so : this time is quite random), the server completely hangs.
I'm using it mainly remotely, through ssh and nfs. What I see when it "hangs" is the following:
-no ping response
-nfs stalled
-ssh sessions hangs (for example, if I run a "top" command", it just isn't updated anymore
-disk activity led stays completely off (in normal activity, it is almost always blinking, even due to "internal" server activities, so network disconnection doesn't explain that either)
The most strange thing is that, to resume it, I basically have 3 options : wait (sometimes few tens of seconds, usually between 2 and 4 minutes!), just hit a key on the keyboard!, or do something like un/plugging any king of usb peripheral (which makes me think of some interruption mechanism that is stalled).
When it "wakes up", I see my "top" session over ssh suddenly being quickly updated hundreds of times (for all it has not received during the "pause"), ping says that the packets have actually all been received (with long times, for example, packet 1 : 80xxxms, packet 2 : 79xxxms, packet 3 : 78xxxms..... packet 79 : 1xxxms, packet 80 : 0.xxxms), the disk is quite overloaded for a few seconds, and everything is back at normal!
Furthermore, I think this i related, but my clock drifts for few hours per day (3 holding minutes every 20-30 minutes makes me think there is some relation!)
I tried to set up ntpd to compensate it, but sometimes the suspensions are just too long, and I ended up with
Code:
Nov 27 01:22:36 server ntpd[699]: 0.0.0.0 0617 07 panic_stop +1203 s; set clock manually within 1000 s
and ntpd dies...
You'll ask me to have a look at the log, which I did by
Code:
But when the suspension happens, there is absolutely nothing new in all those files!
Version information :
Code:
I said in the title "F13-F14", because I already had the problem with F13, but after some time it disappeared (I may have changed some configuration, I have to admit...). I still have a backup of the "/etc" tree of that "working" F13.
The hardware for F13[working] and F14[not_working] is the same : Phenom II X4 on an ASUS M3N78 PRO, data on raid 10, system on separated SATA disk, 8Gb RAM, some qemu vms running (between 4 and 6).
I use Fedora 11 and xfce from official repo. Xfce started to behave unstable two weeks ago. Unstable I mean, when I log in icons on desktop blinks few times, applets don't appear and the result of ps -A command is:
Code:
I've have found the same error with workaround on Ubuntu bug tracker: [url]