On time set via gnome-panel, "/sbin/hwclock returned 256"

[NY00123]

Whenever ever I try to change the time in Ubuntu Hardy 8.04 (GNOME), it seems to be set properly, but I also get the following error:
Big font: "Failed to set the system time"
Small font: "/sbin/hwclock returned 256"

I haven't checked if it's set properly after a reboot, though.

1) right-click on calendar applet in toolbar
2) select "Adjust date & time"
3) click "Set system time"
==> error message (screenshot attached):
"Failed to set the system time" (bold big font)
"/sbin/hwclock returned 256" (small normal font)

Also confirmed on Ubuntu 8.10.

[Pascal De Vuyst (pascal-devuyst)]

Did you change the time using the clock applet on the panel or from a command line?
Is this reproduceable after a reboot?

[NY00123 (ny00)]

Right now it seems like it doesn't happen, after trying to change by a whole hour (like in the last time); I've always tried to change using the clock applet on the panel, in that case.

[Pascal De Vuyst (pascal-devuyst)]

Is this still an issue?
If not please close this bug report by clicking on the current status, under the Status column, and change the Status to "Invalid". Thanks!

[NY00123 (ny00)]

Doesn't seem to occur (I've just tried to decrease the hour by 1 and then increase back).
The bug status has been changed to "Invalid".

[Luca Carrogu (motoplux)]

I'm on updated intrepid kernel 2.6.27-6-generic and I get the error initially described.

[Walter Heck (walterheck)]

I have the same problem after upgrading to the latest beta of Intrepid. Trying to update the time through the clock applet produces the error mentioned before. It remains so after a reboot.

Linux walterheck-laptop 2.6.27-7-generic #1 SMP Tue Oct 14 18:40:44 UTC 2008 i686 GNU/Linux

my syslog says:
walterheck@walterheck-laptop:~$ grep ntpd /var/log/syslog
Oct 17 07:46:16 walterheck-laptop ntpd[5518]: ntpd exiting on signal 15
Oct 17 07:46:17 walterheck-laptop ntpdate[7809]: can't find host clock.tricity.wsu.edu
Oct 17 10:55:04 walterheck-laptop ntpdate[7809]: step time server 193.67.79.202 offset 11326.571568 sec
Oct 17 10:55:04 walterheck-laptop ntpd[7849]: ntpd 4.2.4p4@1.1520-o Wed Aug 20 17:03:52 UTC 2008 (1)
Oct 17 10:55:04 walterheck-laptop ntpd[7850]: precision = 2.000 usec
Oct 17 10:55:04 walterheck-laptop ntpd[7850]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Oct 17 10:55:04 walterheck-laptop ntpd[7850]: Listening on interface #1 lo, 127.0.0.1#123 Enabled
Oct 17 10:55:04 walterheck-laptop ntpd[7850]: Listening on interface #2 wlan0, 192.168.1.101#123 Enabled
Oct 17 10:55:04 walterheck-laptop ntpd[7850]: kernel time sync status 0040
Oct 17 10:55:04 walterheck-laptop ntpd[7850]: frequency initialized -49.214 PPM from /var/lib/ntp/ntp.drift
Oct 17 10:55:04 walterheck-laptop ntpd[7850]: getaddrinfo: "::1" invalid host address, ignored
Oct 17 10:55:07 walterheck-laptop ntpd_initres[7853]: couldn't resolve `clock.tricity.wsu.edu', giving up on it
Oct 17 10:58:18 walterheck-laptop ntpd[7850]: synchronized to 213.222.193.35, stratum 1
Oct 17 10:58:18 walterheck-laptop ntpd[7850]: kernel time sync status change 0001
Oct 17 11:19:50 walterheck-laptop ntpd[7850]: synchronized to 193.67.79.202, stratum 1
Oct 17 12:22:20 walterheck-laptop ntpd[7850]: synchronized to 213.222.193.35, stratum 1
Oct 17 12:31:41 walterheck-laptop ntpd[7850]: synchronized to 193.67.79.202, stratum 1
Oct 17 14:23:39 walterheck-laptop ntpd[7850]: synchronized to 213.222.193.35, stratum 1
Oct 17 14:32:18 walterheck-laptop ntpd[7850]: synchronized to 193.67.79.202, stratum 1
Oct 17 15:59:25 walterheck-laptop ntpd[7850]: synchronized to 213.222.193.35, stratum 1
Oct 17 16:06:01 walterheck-laptop ntpd[7850]: synchronized to 193.67.79.202, stratum 1
Oct 17 17:28:17 walterheck-laptop ntpd[7850]: synchronized to 213.222.193.35, stratum 1
Oct 17 17:32:03 walterheck-laptop ntpd[7850]: synchronized to 193.67.79.202, stratum 1
Oct 17 07:46:06 walterheck-laptop ntpd[5517]: ntpd 4.2.4p4@1.1520-o Wed Aug 20 17:03:52 UTC 2008 (1)
Oct 17 07:46:06 walterheck-laptop ntpd[5518]: precision = 2.000 usec
Oct 17 07:46:06 walterheck-laptop ntpd[5518]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Oct 17 07:46:06 walterheck-laptop ntpd[5518]: Listening on interface #1 lo, 127.0.0.1#123 Enabled
Oct 17 07:46:06 walterheck-laptop ntpd[5518]: kernel time sync status 0040
Oct 17 07:46:06 walterheck-laptop ntpd[5518]: frequency initialized -2.440 PPM from /var/lib/ntp/ntp.drift
Oct 17 07:46:06 walterheck-laptop ntpd[5518]: getaddrinfo: "::1" invalid host address, ignored
Oct 17 07:46:08 walterheck-laptop ntpd_initres[5533]: couldn't resolve `ntp.ubuntu.com', giving up on ...

[Walter Heck (walterheck)]

Oh, and I cancelled that stupid command halfway through, so I have no idea if whatever is not working now is connected to this. I was in doubt wether to even respond to this since my system is in a weird state right now. Everything basic seems to be working though, so I thought it could only help.

[xteejx (xteejx-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[NY00123 (ny00)]

To summerize, I haven't seen a problem in a recent trial.
In more details,
I've tried changing the time by adding 1 minute (more or less) in Ubuntu 8.10 with GNOME,
and then reduced by 1 minute. As expected, I had to type the password before the first trial.

[NY00123 (ny00)]

To summarize, I haven't seen a problem in a recent trial.
In more details,
I've tried changing the time by adding 1 minute (more or less) in Ubuntu 8.10 with GNOME,
and then reduced by 1 minute. As expected, I had to type the password before the first trial.

[NY00123 (ny00)]

* Clicking on "Save Changes" twice quickly (as I've fixed a typo) has appeared to make the message be sent twice.
Well, just an explanation for the dual messages.

[Adam Wolbach (adam-wolbach)]

I just came across this thread having experienced the same problem, after noticing my system time zone was set incorrectly. Since it looks like the problem wasn't addressed, let me add my experience. I'm running an up-to-date installation of Intrepid/8.10 in a 32-bit VirtualBox virtual machine, with a 20 GB virtual hard disk and 1 GB ram allocated. The host machine is running an up-to-date 64-bit Intrepid install. In the guest:

awolbach@playground:~$ uname -a
Linux playground 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

Adjusting the time through the clock applet produces the same error other users have experienced, a big red minus sign with "Failed to set the system time" and "/sbin/hwclock returned 256" in a single dialog. After about twenty tries I've noticed that the results are nondeterministic. There are three outcomes: outright failure with the error dialog box, a silent fail without setting the clock, and a bizarre third scenario where the clock is set for about two seconds and then automatically resets to the previous time; I'm guessing the software clock update succeeds here and the hardware update fails, the applet mistakenly kills the dialog, and then shortly after a daemon somewhere overwrites the software clock with the incorrect hardware value.

I updated /etc/localtime with a symbolic link to my time zone, which fixed my actual problem. As for the applet, some sleuthing suggests the real problem is deeper:

awolbach@playground:~$ sudo date -s '12/09/2008 19:09:40'
Tue Dec 9 19:09:40 CST 2008

awolbach@playground:~$ sudo /sbin/hwclock --systohc --debug
hwclock from util-linux-ng 2.14
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.

And indeed /dev/rtc is missing, as well as any /dev/rtc* devices. I have posted this here but it seems possible that VirtualBox could be at fault. However, the existence of the following post about a similar problem with VMWare/Intrepid leads me to believe it is the result of incompatible changes in the Linux kernel:

https://bugs.launchpad.net/ubuntu/intrepid/+source/udev/+bug/252924

and that /dev/rtc doesn't exist because the kernel can no longer find the appropriate legacy CMOS RTC driver for the virtualized clock. Anyone care to address? If someone can convince me VirtualBox needs to update something on their side, I'll repost over there.

[Adam Wolbach (adam-wolbach)]

I think a problem remains here.

[xteejx (xteejx-deactivatedaccount)]

Marking as Confirmed, setting as linux package and assigning to Ubuntu Kernel Team.
This should be enough information to begin working on the problem, so I'm going to let the developers take a look at it from here. Thank you.

[Steven (svanpoeck)]

Hi,

Stumbled upon this thread while looking for a solution for my issue to update the system time from the Gnome toolbar.

Same happens here:
1) right-click on calendar applet in toolbar
2) select "Adjust date & time"
3) click "Set system time"
==> error message (screenshot attached):
"Failed to set the system time" (bold big font)
"/sbin/hwclock returned 256" (small normal font)
tail -f on /var/log/syslog while performing action (3) yields:
Dec 10 21:14:48 steven-laptop kernel: [72880.567182] /dev/vmmon[1635]: HostIF_ReadUptime: detected settimeofday: fixed uptimeBase old 18445515206478279819 new 18445515206480757296 attempts 1

HTH,
Steven

[Steven (svanpoeck)]

Hi again,

Sorry forgot to attach my machine info:
cat /etc/issue: Ubuntu 8.10
uname -a: Linux steven-laptop 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux

If you need any more information, please let me know which and how I can obtain it.

BR,
Steven

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[LPO (leonardo-p-oliveira)]

Hi Steven and All.
Same happens to me. I was hoping that upgrading to ubuntu 9.04 the problem would disappear, but not yet.
My details:
cat /etc/issue: Ubuntu 9.04
uname -a: Linux xxxxxxxx-laptop 2.6.28-6-386 #20-Ubuntu Fri Apr 17 08:32:39 UTC 2009 i686 GNU/Linux

If you need more information please let me know.
Best.
LPO

[xteejx (xteejx-deactivatedaccount)]

LPO: Why and how are you using the 28-6 kernel? I believe the current kernel for Jaunty is 28-12, can you please ensure you install ALL available updates, reboot, and let us know if this is still an issue? Thanks.

[Michael Rooney (mrooney)]

Setting to Medium as it seems to affect a bunch of people performing a common action.

[LPO (leonardo-p-oliveira)]

Teej: I'm running a very basic installation since I'm a newbie on this. Yesterday the machine was reported as "up-to-date" using the update manager, and today it still is. I don't know how to force the upgrade from kernel 28-6 to 28-12, but if you give some orientation I can try.
Thanks.

[Steven (svanpoeck)]

@Teej: current Jaunty kernel on my up-to-date system (updated less than one hour ago) is:
Linux ilius507 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

[xteejx (xteejx-deactivatedaccount)]

LPO: If you are using Jaunty 9.04 as stated then your kernel version will be 28-11 anyway, or 28-12 if you have enabled the proposed updates, can you ensure this is the version you are running, update Ubuntu, and run Computer Janitor to clean out any old useless kernels. Thanks.

[Steven (svanpoeck)]

@Michael Rooney:
cat /etc/issue: Ubuntu 9.04
uname -a: Linux ilius507 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

On Ubuntu 9.04 I no longer have an error message, but when clicking "Set system time" the dialog box simply disappears. Perhaps this is the normal behaviour ? If it is, I'd prefer having a message stating that the system clock was successfully updated instead.

When performing this operation, tail -f /var/log/syslog yields:
May 14 08:59:22 ilius507 kernel: [48981.021157] /dev/vmmon[5402]: HostIF_ReadUptime: detected settimeofday: fixed uptimeBase old 18445501838311214264 new 18445501838313488022 attempts 1

I suppose this means the operation was successful ? Again, as a user I'd like to be informed of the outcome of my action: did it succeed or fail and if it failed, have an error message.

Thanks,
Steven

[xteejx (xteejx-deactivatedaccount)]

OK, can you provide us with the following:

1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

Thanks.

[LPO (leonardo-p-oliveira)]

@Teej: I've run the Computer Janitor some days ago, so no other useless kernels were installed when I reported this error. In Update Manager/Settings/Software Sources/Updates/Ubuntu Updates the Pre-release updated (jaunty-proposed) is selected (as well as jaunty-security and jaunty-updates) the only not selected is Unsupported updates (jaunty-backports). I've run an update and computer janitor again and after that my uname -a still was:
Linux xxxxxx-laptop 2.6.28-6-386 #20-Ubuntu Fri Apr 17 08:32:39 UTC 2009 i686 GNU/Linux
After a fresh restart the uname -a still was as above. See attached dmesg.log and lspci-vvnn.log.
The error still happens.
Many thanks for your help.

[xteejx (xteejx-deactivatedaccount)]

Thanks for the logs. Are you using the main Ubuntu mirror for your updates, perhaps the updates haven't dropped down to the local mirrors, although this is doubtful...

[LPO (leonardo-p-oliveira)]

@Teej: Yes, on Software Sources/Ubuntu Software/Downloadable from the Intert/Download from/ is selected "Main Server". Also all other check boxes are marked.
Since I could not identify the address for "Main Server" I chose morrors.us.kernel.org/ubuntu just to see if it cause any difference. But no update was offered. My uname -a is still the same.

[xteejx (xteejx-deactivatedaccount)]

Can you run
apport-collect 207902
and let it pull in all the extra info for each hardware configuration, this should then be enough to pass it onto the correct teams. Thanks.

[LPO (leonardo-p-oliveira)]

@Teej: apport-collect does not work, probably due to proxy or ftp blocking in my company. Nevertheless I found a list of requested information from jtholmes in other bug report that I hope contains most data:
kernel version: 2.6.28-6-386 #20-Ubuntu Fri Apr 17 08:32:39 UTC 2009 i686 GNU/Linux
Graphics Chip Mfgr: Intel Corporation
Graphics Chip Model: Mobile 915GM/PM/GMS/910GML Express Processor
File System Type for /:EXT3-fs
Is this problem on a Laptop: Yes
Laptop mfgr: Hewlett-Packard
Laptop model: Compaq nx6120
Is this problem on a Desktop: No.
using wireless: No.
using wired: Yes
ethernet card driver: tg3
bios mfgr: Hewlett-Packard
using Compiz: Yes (1:0.8.2-0ubuntu8.1)
using Kde: No
using Gnome (metacity): Yes (1:2.25.144-0ubuntu2.1)
If you need any other specific information please guide me on how to collect it. Thanks.

[xteejx (xteejx-deactivatedaccount)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to let them handle it from here. Thanks for taking the time to make Ubuntu better!

[Luca Carrogu (motoplux)]

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=it_IT.UTF-8
Uname: Linux 2.6.29.3-mp58 i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lp lpadmin mythtv netdev plugdev powerdev pulse sambashare scanner src tape tilp video

[Barrett Dillow (bdillow)]

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en
Uname: Linux 2.6.28-6-386 i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

[Bernard François (bernardfrancois-gmail)]

I'm experiencing exactly the same bug since I upgraded from 8.04 to 9.04. It's quite annoying that I can't modify the system time, before this bug was introduced I didn't realise how often I look at the clock :-)

I'm using the 2.6.28-6-386 kernel. A newer kernel was not proposed by the update manager. I assume there is no *-386 version of the 2.6.28-11 kernel in the repositories.

Luckily there is a work-around available to change the time: The time can be changed by going to "system > administration > time and date".

This worked for me, and at least one other person, see http://ubuntuforums.org/showthread.php?t=1091229

[Bernard François (bernardfrancois-gmail)]

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=C
Uname: Linux 2.6.28-6-386 i686
UserGroups: adm admin audio cdrom dialout dip fax floppy plugdev scanner tape

[xteejx (xteejx-deactivatedaccount)]

I am using 28-11 on a fresh i386 install of Jaunty, and 28-11 on an upgrade from Intrepid. Strange that you are not using this.

[Bernard François (bernardfrancois-gmail)]

I'm just using the kernel the update-manager installed for me.

What's your output of uname -r? Are you using the *-386 version of the
kernel? For some reason, I don't have a *28-11-386 kernel in my /boot
directory, only a *28-11-generic one.

On Sat, May 23, 2009 at 12:40 AM, Teej <email address hidden> wrote:
> I am using 28-11 on a fresh i386 install of Jaunty, and 28-11 on an
> upgrade from Intrepid. Strange that you are not using this.
>
> --
> On time set via gnome-panel, "/sbin/hwclock returned 256"
> https://bugs.launchpad.net/bugs/207902
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Bernard François (bernardfrancois-gmail)]

Note that I initially installed ubuntu as 7.04, and that I gradually upgraded over time to 9.04. I'm not willing to re-install ubuntu, as this is quite an involving process on my fakeraid configuration (the ubuntu installer doesn't recognize this raid).

Just in case this would have anything to do with it; here is a description of the method I used to install ubuntu:
https://help.ubuntu.com/community/FakeRaidHowto

Teej, sorry for disclosing your email address in public. It happened by replying to the mail I received with your reaction to my initial comment. Gmail added the quotes without me realising it...

[xteejx (xteejx-deactivatedaccount)]

28-11-generic is the correct version for the kernel in Jaunty, unless you are using the proposed repo, then it will be 28-12-generic. Note kerrnel naming in Ubuntu no longer has i386 or amd64. :)

[LPO (leonardo-p-oliveira)]

Hi Teej, my installation was stuck on 28-6-386, and I was unable to force the update onto 28-11-generic in May.
Today I tried again with 28-15-generic and the update was successful. The good news is that bug 207902 was fixed!!!
The only operation that I performed was in Synaptic, manually requesting the installation of linux-image-2.6.28-15-generic (that for some reason was not automatically installed).
Many thanks for your help!

[bol1 (mb2215)]

Hi,

I just want to say this bug is very much still an issue!.

 I'm running Jaunty on my Acer Aspire L100 and am plagued by this ""/sbin/hwclock returned 256" problem. No one on any of the forums seems to know much about it so have to assume its an infrequent but persistant problem. If you need more detailed information I'll be happy to give it to you, just tell me what to put into Terminal though.
Thanks
Mike

mbdb@M2000:~$ uname -a
Linux M2000 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

[bol1 (mb2215)]

Just to add this is a recent and fresh install of Jaunty

[bol1 (mb2215)]

Just to update. Even though this error msg results whenever I try to set system time it does in fact change the clock. However, its only tempory and as soon as I reboot the change is lost.

I know I should probably be providing more info and will be happy do as soon as someone tells me what what to enter.

Also has this bug actually been fixed? and if so what is that fix?

Mike

[bol1 (mb2215)]

Is this thread still active? Is anyone still reading it? If anyone is please could tell me what the status of this bug is? I'm wondering if its one of these cases thats affects only a handful of people and considered such low priority that it never gets resolved? If anyone knows anything about this please let us know.
Thanks
Mike

[bol1 (mb2215)]

I guess not!

[Bernard François (bernardfrancois-gmail)]

I still have the issue, and I'm following it.

Luckily, the time is set properly using time servers. Manually changing the time isn't possible though.

I'm running kernel 2.6.28-6-386 (there's a kernel update available, but I didn't update it yet as I first want to make a backup of my system).

[deynard (eynard)]

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
Uname: Linux 2.6.28-6-386 i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev sambashare scanner video

[Bernard François (bernardfrancois-gmail)]

Since 2009-08-16 (the date of my previous comment), the time syncronisation doesn't work any more. Unfortunately I missed an appointment because of that (I wasn't aware of it, so I thought the clock time was correct).

When I try to set the system time, I get the error message. When I press the time syncronisation button (with the arrow icon on it), nothing happens.

[toinbis (toinbis-deactivatedaccount)]

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Uname: Linux 2.6.21.7-2.fc8xen i686
UserGroups: fuse

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[emas (emas80spam)]

Hi, this bugs still affects my Lucid, I can't change time from the applet and if I type

emas@ima-zen:~$ hwclock --debug
hwclock from util-linux-ng 2.17.2
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.

[emas (emas80spam)]

I'm really sorry, I've already solved my previous problem, I didn't have checked, in my kernel configuration,

Character devices->Enhanced Real Time clock support

which should create /dev/rtc, so that hwclock could find clock interface.

I'm sorry I didn't check it BEFORE to report the bug.
I will remark the bug as triaged.

[Stefan Leitner (s-o-l)]

hi! i have this problem also on lucid! I'm using Ubuntu 10.04 LTS on my Pegasos II PPC (G3).

So uname -a:
Linux [computername] 2.6.32-22-powerpc #36-Ubuntu Thu Jun 3 23:00:32 UTC 2010 ppc GNU/Linux

My kernel is generated with mkvmlinuz:
sudo mkvmlinuz -o vmlinuz1004 -a chrp -k vmlinux -i initrd.img -z -v

and i have also no /dev/rtc

Any suggestions? :)

[xteejx (xteejx-deactivatedaccount)]

Hi all, sorry this hasn't been updated, but there have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue. Thank you.

[Steven (svanpoeck)]

Works in Ubuntu 10.10 on a Dell Latitude E6510

uname -a -m -r -s
Linux rd-25 2.6.35-23-generic #41-Ubuntu SMP Wed Nov 24 11:55:36 UTC 2010 x86_64 GNU/Linux

Thanks,
Steven

[xteejx (xteejx-deactivatedaccount)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[M. Crewe (m-crewe)]

Might want to open this one back up. Although I am new to Ubuntu.. I just installed it on my PC 2 weeks ago. This is the last of the few "bugs" I have yet to work out. I have XP, Vista and Ubuntu 10.10 all installed to totally separate drives & partitions. Both Windows installs have no problem synching time off the bios but for some reason whenever I boot in Ubuntu my clock is always of -8 or -9 hours.

I finally managed to get a non-default internet time server set up and it will now sync OK.. but I'm on dial-up and it would be really nice if the clock would just stay set.. period.

If there is any additional information I can furnish you please don't hesitate. I'm using Ubuntu 10.10 with all of the latest updates/kernels/etc.