Contribute
Register

Guide to Installing Mountain Lion on HP Probook

DimeVagg said:
As you can notice, there are different IP-addresses of apple time server. Maybe you should specify it manually
Click to expand...

Actually, there are instances where the same server was used several times in a row. But the drift still varies, sometimes by significant amounts.
 
That's your log:
[2.241]
24 Feb 17:46:24 ntpdate[12568]: adjust time server 17.253.2.241 offset -0.035188 sec
Tue Feb 24 17:46:24 PST 2015
25 Feb 03:47:27 ntpdate[12811]: adjust time server 17.253.2.241 offset -0.036890 sec
Wed Feb 25 03:47:27 PST 2015
[2.243]
24 Feb 14:46:06 ntpdate[11866]: adjust time server 17.253.2.243 offset -0.043325 sec
Tue Feb 24 14:46:06 PST 2015
[8.243]
24 Feb 12:45:54 ntpdate[11656]: adjust time server 17.253.8.243 offset -0.073517 sec
Tue Feb 24 12:45:54 PST 2015
[12.241]
24 Feb 16:46:18 ntpdate[12342]: adjust time server 17.253.12.241 offset -0.031860 sec
Tue Feb 24 16:46:18 PST 2015
24 Feb 22:46:56 ntpdate[12711]: adjust time server 17.253.12.241 offset -0.026620 sec
Tue Feb 24 22:46:56 PST 2015
25 Feb 00:47:09 ntpdate[12749]: adjust time server 17.253.12.241 offset -0.026443 sec
Wed Feb 25 00:47:09 PST 2015
[16.243]
24 Feb 11:45:41 ntpdate[11284]: adjust time server 17.253.16.243 offset 0.021102 sec
setUsingNetworkTime: Off
24 Feb 11:45:48 ntpdate[11286]: adjust time server 17.253.16.243 offset 0.008662 sec
Tue Feb 24 11:45:48 PST 2015
24 Feb 13:46:00 ntpdate[11848]: adjust time server 17.253.16.243 offset -0.007885 sec
Tue Feb 24 13:46:00 PST 2015
24 Feb 15:46:10 ntpdate[12300]: adjust time server 17.253.16.243 offset -0.028111 sec
Tue Feb 24 15:46:10 PST 2015
24 Feb 20:46:42 ntpdate[12685]: adjust time server 17.253.16.243 offset -0.031657 sec
Tue Feb 24 20:46:42 PST 2015
25 Feb 02:47:23 ntpdate[12777]: adjust time server 17.253.16.243 offset -0.025689 sec
Wed Feb 25 02:47:23 PST 2015
25 Feb 04:47:32 ntpdate[12828]: adjust time server 17.253.16.243 offset -0.033140 sec
Wed Feb 25 04:47:32 PST 2015
25 Feb 05:47:37 ntpdate[12843]: adjust time server 17.253.16.243 offset -0.034776 sec
Wed Feb 25 05:47:37 PST 2015
[22.243]
24 Feb 18:46:31 ntpdate[12657]: adjust time server 17.253.22.243 offset -0.031542 sec
Tue Feb 24 18:46:31 PST 2015
24 Feb 19:46:35 ntpdate[12669]: adjust time server 17.253.22.243 offset -0.033077 sec
Tue Feb 24 19:46:35 PST 2015
24 Feb 21:46:50 ntpdate[12698]: adjust time server 17.253.22.243 offset -0.035040 sec
Tue Feb 24 21:46:50 PST 2015
24 Feb 23:47:02 ntpdate[12726]: adjust time server 17.253.22.243 offset -0.039879 sec
Tue Feb 24 23:47:02 PST 2015
25 Feb 01:47:15 ntpdate[12764]: adjust time server 17.253.22.243 offset -0.041831 sec
Wed Feb 25 01:47:15 PST 2015

The only curious thing is the red line. And all of the rest shows that offset slightly increases. But it is too insignificant and it means, that your bus speed value is correct. I had much significant offsets with BusSpeed, that Clover detected automaticaly. And I suppose it affected audio syncronization in Logic.
 
My point was that the amount of drift is not very consistent, even from the same server.

In my view this section was more interesting...

Code: 
[16.243]
24 Feb 11:45:41 ntpdate[11284]: adjust time server 17.253.16.243 offset 0.021102 sec
setUsingNetworkTime: Off
24 Feb 11:45:48 ntpdate[11286]: adjust time server 17.253.16.243 offset 0.008662 sec
Tue Feb 24 11:45:48 PST 2015
24 Feb 13:46:00 ntpdate[11848]: adjust time server 17.253.16.243 offset -0.007885 sec
Tue Feb 24 13:46:00 PST 2015
24 Feb 15:46:10 ntpdate[12300]: adjust time server 17.253.16.243 offset -0.028111 sec
Tue Feb 24 15:46:10 PST 2015
24 Feb 20:46:42 ntpdate[12685]: adjust time server 17.253.16.243 offset -0.031657 sec
Tue Feb 24 20:46:42 PST 2015

Min=-0.007885
Max=-0.031657

They are different by a factor of ~4.015 (0.031657/0.007885).

I think it means that the method is an inaccurate way of measuring or some sort of average between differences should be employed. Because individual drifts measurements in one hour of time can be significantly different.
 
So you tell me how to detect this value in accurate way. I've found the reason of audio cracking and solution. May be there is any other way to do it. Should I remove my manual value, then switch UEFI to legacy mode and check this value in log-file of Clover ? I've read that Clover detects an inaccurate value when it boots UEFI native
 
I had Mountain Lion running on a Probook 4730s. Unfortunately the CPU had to be replaced and was upgraded from i3 to i7. I now get a kernel panic when booting with P-State error 18. Is there a possibility to make it boot again?
 

Attachments

  • 20150314_150755_resized.jpg
    20150314_150755_resized.jpg
    813.5 KB · Views: 86
dikkiedirk said:
I had Mountain Lion running on a Probook 4730s. Unfortunately the CPU had to be replaced and was upgraded from i3 to i7. I now get a kernel panic when booting with P-State error 18. Is there a possibility to make it boot again?
Click to expand...

Boot using USB. Create new SSDT and re-patch DSDT.
 
dikkiedirk said:
Just "-f"? Or do I need more bootflags?
Click to expand...

-f will ignore kernel cache, which is likely your problem. Other than that, I have no ability to predict the future.
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top