Bug#557949: awk errors and invalid /etc/default/adjtimex

2010-04-16 Thread Savvas Radevic
Thanks to an insightful comment, I have managed to fix my problem!
It was either spread spectrum or the d.o.t. (overclocking) technology
by MSI. Disabling these settings in BIOS helped me get a way better
setting (some milliseconds difference) -- now ntp and adjtimex work
without warning about +/- 500ppm!

https://bugs.launchpad.net/ubuntu/+source/adjtimex/+bug/553237/comments/11
https://bugs.launchpad.net/ubuntu/+source/adjtimex/+bug/553237/comments/12



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#557949: awk errors and invalid /etc/default/adjtimex

2010-04-07 Thread Savvas Radevic
My problem is back unfortunately, I have no idea what seems to be the
cause of it:

https://bugs.launchpad.net/ubuntu/+source/adjtimex/+bug/553237/comments/6
https://bugs.launchpad.net/ubuntu/+source/adjtimex/+bug/553237/comments/7

My motherboard is MSI P965 Neo2 if it matters:
http://www.msi.com/index.php?func=proddescmaincat_no=1prod_no=1163



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#557949: awk errors and invalid /etc/default/adjtimex

2010-04-06 Thread Savvas Radevic
While I had this problem for a couple of days, I used a patch I made
for Ubuntu 10.04 (lucid, development):
https://bugs.launchpad.net/bugs/553237
However, someone suggested to purge and try installing again, which I
did. It works great now!

$ sudo adjtimexconfig
Comparing clocks (this will take 70 sec)...done.
Adjusting system time by -2.46162 sec/day to agree with CMOS clock...done.


Try purging adjtimex, rebooting the machine and installing the 1.28-1
version again:

aptitude purge adjtimex

rm /etc/default/adjtimex

rm -r /var/cache/apt/archives/adjtimex*

rm -r /var/cache/apt/archives/partial/adjtimex*

reboot

aptitude update

aptitude install adjtimex


P.S. Could it be that ntpd causes problems?



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#557949: awk errors and invalid /etc/default/adjtimex

2010-04-04 Thread Santiago Vila
On Thu, 1 Apr 2010, Savvas Radevic wrote:

 It looks like that Correctly apply +-500 ppm sanity check applied for 
 version 1.28 is causing problems.
 Also, bug #559882 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559882 ) 
 seems to be a duplicate of this one.

Question for James: It is really useful to have those sanity checks at all?

In my case, the very reason I use adjtimex is that my computer has a too big 
clock skew
that may not be fixed just by using ntpd (it's an old powerpc Mac Mini).

As ntpd already refuses to work corretly outside the +-500 ppm margin, I would 
expect
adjtimex not to have any sanity checks at all, or, at least, be a *lot* more 
permissive.

What about +-5000 ppm, for example?

The typical clock skew for a Mac Mini is about 2800 ppm. A sanity check lower 
than that
would force me to do special things to be able to use this package.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#557949: awk errors and invalid /etc/default/adjtimex

2010-04-01 Thread Savvas Radevic
Package: adjtimex
Version: 1.28-1
Severity: grave

I have the same problem on Ubuntu 10.04 (lucid, still under testing).
This error makes this package unusable.

It looks like that Correctly apply +-500 ppm sanity check applied for version 
1.28 is causing problems.
Also, bug #559882 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559882 ) 
seems to be a duplicate of this one.

I have the same problem:

$ sudo aptitude install adjtimex
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Reading extended state information  
Initializing package states... Done
The following NEW packages will be installed:
  adjtimex 
0 packages upgraded, 1 newly installed, 0 to remove and 5 not upgraded.
Need to get 0B/58.2kB of archives. After unpacking 176kB will be used.
Writing extended state information... Done
Preconfiguring packages ...
Selecting previously deselected package adjtimex.
(Reading database ... 167625 files and directories currently installed.)
Unpacking adjtimex (from .../adjtimex_1.28-1_amd64.deb) ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up adjtimex (1.28-1) ...
update-rc.d: warning: adjtimex start runlevel arguments (S) do not match LSB 
Default-Start values (2 3 4 5)
update-rc.d: warning: adjtimex stop runlevel arguments (none) do not match LSB 
Default-Stop values (0 1 6)
Regulating system clock...done.
Comparing clocks (this will take 70 sec)...done.
awk: BEGIN{print ((to-1)*100 + override)./65536.)*.0864}
awk:^ syntax error
awk: BEGIN{print ((to-1)*100 + override)./65536.)*.0864}
awk:  ^ unterminated regexp
awk: cmd. line:1: BEGIN{print ((to-1)*100 + override)./65536.)*.0864}
awk: cmd. line:1:^ 
unexpected newline or end of string
Adjusting system time by  sec/day to agree with CMOS clock...done.

Reading package lists... Done 
Building dependency tree   
Reading state information... Done
Reading extended state information  
Initializing package states... Done
Writing extended state information... Done

$ sudo adjtimex --adjust
  --- current ---   -- suggested --
cmos time system-cmos  error_ppm   tick  freqtick  freq
1270121506-124.142183
1270121516-123.95716018502.3  1 0
1270121526-123.77223818492.2  1 09815511312
1270121536-123.57137520086.3  1 09799897037
1270121546-123.38645718491.8  1 09815537875

ERROR: required correction is greater than plus/minus 500 parts 
per million, quitting (use --force-adjust to override).

$ sudo adjtimex --adjust --force-adjust
  --- current ---   -- suggested --
cmos time system-cmos  error_ppm   tick  freqtick  freq
1270121703-120.372324
1270121713-120.18728418504.0  1 0
1270121723-119.98643820084.6  1 09799   1009537
1270121733-119.80150018493.8  1 09815406625
1270121743-119.59656020494.0  1 09795392687

WARNING: required correction is greater than plus/minus 500 parts 
per million, but adjusting anyway per your request.
1270121753-119.627563-3100.3   97953926879826412337
1270121763-119.639954-1239.1   97953926879807   2955737
1270121773-119.652301-1234.7   97953926879807   274

WARNING: required correction is greater than plus/minus 500 parts 
per million, but adjusting anyway per your request.


I tried using --force-adjust in adjtimexconfig, but it did not help.


-- System Information:
Debian Release: squeeze/sid
  APT prefers lucid-updates
  APT policy: (500, 'lucid-updates'), (500, 'lucid-security'), (500, 'lucid')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-18-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages adjtimex depends on:
ii  debconf [debconf-2.0]1.5.28ubuntu2   Debian configuration management sy
ii  libc62.11.1-0ubuntu5 Embedded GNU C Library: Shared lib

adjtimex recommends no packages.

Versions of packages adjtimex suggests:
ii  ntpdate  1:4.2.4p8+dfsg-1ubuntu1 client for setting system time fro

-- debconf information:
  adjtimex/compare_rtc: true
  adjtimex/run_daemon: true



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org