Debian :: Hw Clock Drift - Keeps Changing Back To UTC
Feb 24, 2011
The clock keeps changing back to UTC which is not so good. My local timezone is about UTC +7. It appears to be good until I reboot. I can change manually in the bios or enter the following command hwclock --systohc --localtime No matter what it goes back to UTC. I checked the timezone data is correctly recorded and it is...
The command hwclock returns Wed 23 Feb 2011 08:18:05 PM ICT The command date returns Wed Feb 23 20:19:25 ICT 2011 so this shows the system time and the hardware time are the same but they use the 12 and 24 hour clock which is strange since the bios supports only the 24 hour clock. I wonder if the time / date syntax has to be presented in the same way on both the system and the hardware? The time ICT zone appears to be correct.
In the clock display (Kubuntu 10.10 32-bit defaults at the lower right in the task bar) I have been having a problem. When I right click on the clock (is there a name for right-clicking when referring to both right and left handed people?) or sometimes when I just run my mouse over the clock, it changes from CDT to UTC. Doing it again reverses that. I'm speaking about the actual clock on the task bar, not the pop-up panel (tool tip?) that comes up when you roll your mouse over it.
I have both time zones selected so that I can see them in the pop-up info panel when I run the mouse over the clock for a second. But, normally, I just want the CST/CDT displayed always, in the task bar.
I've looked at all the options I could find and haven't found what I missed. It started up recently, so it was probably some setting I changed, but now can't find.
A minor problem, but annoying. Anyone? If the answer is already out there, link me up!
I was running Debian Etch for a while and upgraded to Debian Lenny months ago. After the upgrade I began to notice that I was losing time pretty severely on the desktop clock (On the order of more than 1 second every minute!).I recently noticed an online game lagging exactly every 5 minutes and finally pinpointed it to this timekeeping script I wrote. I would like to fix the time drift issue on this PC properly now but have not found any helpful documentation online yet.
I've recently done a clean install from Karmic to Lucid, everything went well first time, although I noticed that my GPU performance seemed to drop. It wasn't amazing to begin with being an older AGP card (nvidia 6800GT), but it was enough of a drop to make me look for a solution.
I thought maybe the drivers in Lucid were to blame so I recently added the ubuntu-x-swat PPA
[URL]
to get the most up to date drivers.
Performance didn't go up, so I tried the 173 version of the drivers to see if that would help, but I had no luck.
Today I'm pretty sure I downloaded an update from the above PPA and since then every time I change the clock speeds (via the Coolbits option within nvidia-settings) on my card I get a black screen, there is no response from any input device and I have to hold the power button to turn off the PC.
I want to know if there is anyway to check recent packages I've downloaded, and also if anyone could shed some light as to why changing the clock speeds of the card would result in a black screen and no response from the keyboard or mouse.
I'd also like to point out, that I've been changing the clock speeds of the card since I first installed Karmic with no problem. Additionally before I downloaded today's updates, even with the new packages from the above PPA changing the clock speeds worked perfectly. It seems that something I downloaded is to blame.
I just installed kubuntu desktop on my system, now when I boot my system, the kubuntu loading screen comes up (after the grub loading and before the login page). I've tried to change the screen by editing the grub menu list as told in some forum topics but it makes no change. How do I change my splash screen back to that of ubuntu or ant other image.
First of all not sure if this is the correct forum but anyway.Ok well i installed this theme because i liked the look of windows 7 (http://gnome-look.org/content/show.p...content=113264).So i ran the GUIUninstall.sh and it seemed to work but the login screen still has the theme i was wondering how i could change it back to the defualt one.
I'm not sure exactly what happened, but starting a few hours ago, every time i open firefox,the settings have all reverted to the default. I change them back to what i prefer, then when i open it again they are back to the default.
Today I installed Xubuntu desktop on my normal Ubuntu, to see what it's like, and to have the option to run a more minimal desktop when I want.
My only problem is that my login screen loads with the Xubuntu theme. This wouldn't be a problem except it makes it take significantly longer to boot into Ubuntu (Gnome).
How can I change it back so that Gnome is the default, and XFCE only gets loaded if I pick it at login?
what are my options with customizing Gnome at the login screen?
i have changed the network/internet tool on ubuntu 9.04 to wicd which now doesn't work, ethernet or wireless connection how do i change it back to whatever the default is?
I went to YaST>Security and Users>User and Group Management and changed my username. Now I can't do anything (open home directory, start application, login, etc). I tried changing back the username by going to YaST at init 3 and changing back to the previous username.
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
I 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?
When I google screenshots of Linux I often see that people have a clock directly on their desktop. How is this done?
I'm running Xfce on a Wheezy vm, but without xfce4-panel, so having a clock/date right on the wallpaper/desktop would be great..I don't want a clock in a window.
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 had my USB DAC, the aforementioned, working before in Ubuntu, Xubuntu, Fedora, Linux Mint 17.1 and Linux Mint 17.2. I've finally settled on Debian with i3wm as I feel I am now at a stage with Linux where I'm comfortable enough to use it.
It may be something to do with audio output being handled by Pulse, but this was the case in *buntu as well, as I used the Pulse config file to up the maximum bitrate output to take full advantage of the DAC.
On Debian (Stretch), I'm getting this when I select the device in AlsaMixer:
As can see, it is operating in USB 2.0 mode, which is correct.
I initially installed SuSe11.2 with /tmp mounted on separate partition on another physical disk( there are two physical disks). Now I want to attach disk with existing SuSe11.2 to another motherboard so I would like that /tmp becomes part of the root partition. Will deleting /tmp mount point in /etc/fstab create automatically new /tmp from root at next startup, or something else has to be done to achieve, that in future, /tmp resides on root partition instead? In this way it would be much easier to move the disk with SuSe11.2 to another motherboard.
During the installation the installer asked me if my clock was set to UTC. I didn't know what that meant so I said yes. Now whenever I boot into Lenny it messes up the time of day, and since I dual boot with puppy and knoppix on this machine, the time of day is messed up in those systems also. Any idea how to permanently undo the damage in Lenny?
I'm trying to sync my clock. I think I would like to do this by the "ntpd" daemon running. I think it should start up on boot, but it doesn't.
I have the following in my /var/log/syslog: Jul 18 23:44:14 neo ntpd[1780]: ntpd 4.2.6p2@1.2194-o Sun Oct 17 13:45:13 UTC 2010 (1) Jul 18 23:44:14 neo ntpd[1781]: proto: precision = 0.634 usec Jul 18 23:44:14 neo ntpd[1781]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING Jul 18 23:44:14 neo ntpdate[1194]: step time server 72.26.125.125 offset -0.505108 sec
Other posts say if ntpd and ntpdate run too close together, they cause one to think the other is locking a resource. It works to type "ntpdate pool.ntp.org" to manually update the clock. My Debian version is squeeze (6.0.2)
It works to start the ntpd daemon manually: ... sudo /etc/init.d/ntp start ... Starting NTP server: ntpd.
I remember that 10 years ago or so, I used to have on a Debian desktop a clock which displayed the time on a custom level of approximation, e.g. quarter to five for 04:47 or even "morning/late evening/etc". I can't remember if it was a customization of the default clock or a separate program. I didn't have luck searching on the internet. Is it possible to get something similar with Gnome on Jessie?
I had to boot into my Windows 7 install on my laptop for the first time in a few months and I noticed that the Windows clock was 4 hours ahead. Windows sync'd its time with the internet, then I booted back into Debian (Lenny) and my clock was now 4 hours behind. Both OS's are set to the same time zone (EDT). The minutes were correct in both systems. Could the fact that EDT is UTC-0400 be relevant?
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.
I've Lenny with Gnome installed. Under System -> Administration -> Login Window -> Local, I have Industrial Ximian Gnome theme. How to change clock type from 12 to 24 in the Industrial Ximian Gnome window?
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'm not sure if this is the right spot for this pst or not, first on this forum. I just removed Fedora Core 4 from my system and installed Debian Sarge with the 2.6 kernel. I'm a newbie. The install seemed to go fine, after it was done I actually logged in and looked around some. I then restarted to check to make sure that my boot process went ok and I could still get to windows. Worked fine. Then I tried to boot back into Debian. It hung. I rebooted and tried again. Hung again in the same spot.
