Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Thanks a lot. I' ll try this and report. Disabling OC, setting the Bootvolume in native-Mojave and re-enabling should do job?
The guide describes what you need to do step by step, but in case you're curious, here's a supplementary explanation:

The key is RequestBootVarRouting or "boot selection routing": boot through OpenCore as usual, turn off boot selection routing, reboot (your Mac will still boot through OC, but boot selection routing will be off), select Mojave in Startup Disk (because you turned off boot selection routing, the selection will be used by your Mac's firmware not OC), finally reboot again. Your Mac will then boot Mojave natively.
 
Hopefully a quick question getting thrown into this thread. Upon boot, the loading bar (which sometimes doesn't move) and Apple logo disappear, and I get hit with a intense full-screen white flash, then black, then the loading bar & Apple logo reappear before the login prompt. Is that normal?

Video of the issue, here, for anyone curious (happens at 20sec, audio for emphasis):



If this is normal, and there's no way around this, then I'll just make sure to never turn on my system in a dark room. Since, after a few boots last night, my eyes still hurt. If this isn't normal. I hope its not my GPU, it's already given me enough gruff. Maybe there's a possible fix in OpenCore?

2010 MP 5,1; 2x X5690; 10.13.6; 2x 860 EVO SSDs (1 boot, 1 w/ OC EFI); stock MSI "RX 580 8G" Reference; 2x Sonnet 4port USB3.0; 1x ATTO FastFrame NS11; Intake/Exhaust Noctua NF-A12; Followed cdf's tutorial Parts 1-3 (all except Night Shift), OpenCore 0.6.7
 
Last edited:
Updated to 11.2.3 with OC 0.6.7: no issue on my cMP 5,1
Same here using v0.6.7. Couple of butt-clenching moments though where I thought the system froze or crashed.

In a nutshell:
  1. VMM off (virtualization instead)
  2. Updated via OTA
  3. First reboot, OC boot picker showed "Macintosh HD" rather than "MacOS Installer"
  4. Fairly long 1st stage boot screen load times (progress bar froze for what seemed several minutes then rapidly moved up to about 80%)
  5. Reboot. This time boot picker showed my Big Sur SSD hard drive (and Recovery volume version changed to 11.2.3)
  6. 1st stage boot screen immediately at 80% (it appeared to freeze again here, then reboot. Thought it KP'd at this point)
  7. After seleting Big Sur SSD volume again, 1st stage boot screen appeared for another couple of minutes before finally going to login prompt.
1615381915847.png
 
Last edited:
Updated to 11.2.3 with OC 0.6.7: no issue on my cMP 5,1
Same here using v0.6.7. Couple of butt-clenching moments though where I thought the system froze or crashed.

In a nutshell:
  1. VMM off (virtualization instead)
  2. Updated via OTA
  3. First reboot, OC boot picker showed "Macintosh HD" rather than "MacOS Installer"
  4. Fairly long 1st stage boot screen load times (progress bar froze for what seemed several minutes then rapidly moved up to about 80%)
  5. Reboot. This time boot picker showed my Big Sur SSD hard drive (and Recovery volume version changed to 11.2.3)
  6. 1st stage boot screen immediately at 80% (it appeared to freeze again here, then reboot. Thought it KP'd at this point)
  7. After seleting Big Sur SSD volume again, 1st stage boot screen appeared for another couple of minutes before finally going to login prompt.
View attachment 1740946
Same experience here!
 
@amstel78, While it's nothing to worry about, OpenCore is setting your processor speed in the SMBIOS as 3.45 GHz instead of 3.46 GHz. Please check if a reboot or two fixes this. If not, a DEBUG log would be useful to help improve the rounding algorithm.
 
@amstel78, While it's nothing to worry about, OpenCore is setting your processor speed in the SMBIOS as 3.45 GHz instead of 3.46 GHz. Please check if a reboot or two fixes this. If not, a DEBUG log would be useful to help improve the rounding algorithm.
Sure, will keep an eye on it. Thanks!
 
Not seeing 11.2.3 on my MacPro5,1. Using OC 0.6.7 and config.plist from first post - only mod is Board ID spoofing and VMM OFF. Confirmed 0.6.7 is installed in terminal. No hardware acceleration - I have a GTX 680.

Thoughts or things I can check?
 
@amstel78, While it's nothing to worry about, OpenCore is setting your processor speed in the SMBIOS as 3.45 GHz instead of 3.46 GHz. Please check if a reboot or two fixes this. If not, a DEBUG log would be useful to help improve the rounding algorithm.

updating to 0.6.7 changed my clock speed to 3.45ghz also and I was wondering why or if that is a problem?
 
updating to 0.6.7 changed my clock speed to 3.45ghz also and I was wondering why or if that is a problem?
Version 0.6.7 brought support for processor speeds with two decimal points. However, because some 3.46 GHz processors are showing up as 3.45 GHz, it seems that the rounding algorithm needs some refining. A DEBUG log would help for this.
 
Version 0.6.7 brought support for processor speeds with two decimal points. However, because some 3.46 GHz processors are showing up as 3.45 GHz, it seems that the rounding algorithm needs some refining. A DEBUG log would help for this.
00:000 00:000 OC: OpenCore DBG-068-2021-03-08 is loading in Optional mode (0/0)...
00:025 00:025 OC: Boot timestamp - 2021.03.09 03:01:52
00:050 00:025 OCCPU: MP services threads 24 (enabled 24) - Success
00:068 00:018 OCCPU: MP services Pkg 2 Cores 16 Threads 32 - Success
00:088 00:019 OCCPU: Found Intel(R) Xeon(R) CPU X5690 @ 3.47GHz
00:107 00:018 OCCPU: Signature 206C2 Stepping 2 Model 2C Family 6 Type 0 ExtModel 2 ExtFamily 0 uCode 1F
00:125 00:018 OCCPU: EIST CFG Lock 0
00:145 00:019 OCCPU: Timer address is 408 from LPC
00:263 00:117 OCCPU: Intel TSC: 3457999990Hz, 3457MHz; FSB: 132999999Hz, 132MHz; MaxBusRatio: 26
00:273 00:010 OCCPU: Detected Apple Processor Type: 05 -> 0501
00:295 00:021 OCCPU: CPUFrequencyFromTSC 3457999990Hz 3457MHz
00:317 00:022 OCCPU: CPUFrequency 3457999990Hz 3457MHz
00:339 00:021 OCCPU: FSBFrequency 132999999Hz 132MHz
00:361 00:021 OCCPU: Pkg 2 Cores 6 Threads 12
I don't think you can get much from the debug log as it always showed the correct value. But I see here:
FSB: 132999999Hz, 132MHz Which is a weird rounding. But actually if it was 26x133 it would be 3458 and now is 26x132=3432
 
  • Like
Reactions: TECK and amstel78
I don't think you can get much from the debug log as it always showed the correct value.
The rounding is based on the CPU frequency that appears there. For the X5690, the rounding was based on a value of 3457999888 Hz, so in your case the speed should appear as 3.46 GHz in About This Mac (with hybridization, of course). Is that what you're seeing?
 
The rounding is based on the CPU frequency that appears there. For the X5690, the rounding was based on a value of 3457999888 Hz, so in your case the speed should appear as 3.46 GHz in About This Mac (with hybridization, of course). Is that what you're seeing?
No, it is 3.45. But as I said even before the recent frequency code change Intel TSC: 3457999990Hz in the debug log was always the same. What I am trying to say is that OC was not using directly that value.
 
No, it is 3.45. But as I said even before the recent frequency code change Intel TSC: 3457999990Hz in the debug log was always the same. What I am trying to say is that OC was not using directly that value.
The fact that it's 3.45 should be reported. The rounding algorithm indeed uses the CPUFrequency value. Here's the code:

 
The fact that it's 3.45 should be reported. The rounding algorithm indeed uses the CPUFrequency value. Here's the code:

well this is clearly wrong:
Code:
if (MhzRemainder >= 50 && MhzRemainder < 90) {
    MhzSpeed = (MhzSpeed) / 10 * 10;
  } else if (MhzRemainder >= 12 && MhzRemainder < 90) {
    MhzSpeed = (MhzSpeed + 5) / 10 * 10;
  } else {
    MhzSpeed = (MhzSpeed + 50) / 100 * 100;
  }
Where is the case where the remainder is >90? Is it MhzSpeed = (MhzSpeed + 50) / 100 * 100? That would be 3500(3.5). This is what we had before. How is it calculating 3.45 then?
Edit:
it looks like it is using case 1 MhzSpeed = (MhzSpeed) / 10 * 10; 3458/10*10=3450=3.45
 
  • Like
Reactions: Dewdman42
well this is clearly wrong:

Where is the case where the remainder is >90? Is it MhzSpeed = (MhzSpeed + 50) / 100 * 100? That would be 3500(3.5). This is what we had before. How is it calculating 3.45 then?
For the X5690, the remainder is 58, so the calculation is actually doing MhzSpeed = (MhzSpeed) / 10 * 10. This gives 3.45. It should actually do MhzSpeed = (MhzSpeed + 5) / 10 * 10. I think the issue is due to accommodating the weird rounding down for 2.66 GHz processors...
 
  • Like
Reactions: Dewdman42
For the X5690, the remainder is 58, so the calculation is actually doing MhzSpeed = (MhzSpeed) / 10 * 10. This gives 3.45. It should actually do MhzSpeed = (MhzSpeed + 5) / 10 * 10. I think the issue is due to accommodating the weird rounding down for 2.66 GHz processors...
So the first case should be removed altogether and it should be:
Code:
if (MhzRemainder >= 12 && MhzRemainder < 90) {
    MhzSpeed = (MhzSpeed+5) / 10 * 10;
    } else {
    MhzSpeed = (MhzSpeed + 50) / 100 * 100;
  }
 
  • Like
Reactions: macnu
Moving on: cMP3,1 20D91, oclp 0.0.14, oc 0.6.8, kepler GT710
using appleALC alcid=13 as per PR #75, no audio devices, no nvidia HDMI audio, firewire works.

generic2.png
 
Im clearly an idiot and don't understand something Im not doing before I go to do everything I have this window and I assume its stopping everything from working correctly
 

Attachments

  • Screen Shot 2021-03-09 at 8.53.54 pm.png
    Screen Shot 2021-03-09 at 8.53.54 pm.png
    170.4 KB · Views: 71
Does someone have X5675? Can you please enable logging and see the frequency and compare it to the one in About this Mac:
 
  • Like
Reactions: amstel78
Last edited:
@amstel78, While it's nothing to worry about, OpenCore is setting your processor speed in the SMBIOS as 3.45 GHz instead of 3.46 GHz. Please check if a reboot or two fixes this. If not, a DEBUG log would be useful to help improve the rounding algorithm.
I know @startergo already filed a bug report, but just to answer your question: no, a reboot (or multiple) has no bearing on algorithm output.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.