OpenCore General Discussion

[deeveedee]

FYI - to close out what will become an off-topic discussion of USB current limits. I thought I was being smart by using 8" "pigtail" straight-through male/female USB cables to make it easier for me to plug USB devices into my HackMini8,l ports.  See lesson learned here.

[pananning]

Hello,In the EFI partition, there are startup files for Windows and Linux. I used OpenLinuxBoot.efi to boot Linux, so I don't need to use grubx64.efi. In the startup menu, I want OpenCore to automatically detect Windows without detecting grubx64.efi, so I can't block the EFI partition. How can I block grubx64.efi?But please don't delete grubx64.efi, because I need to use it in BIOS.

[markl18]

On 2/14/2022 at 10:55 AM, pananning said:

Hello,In the EFI partition, there are startup files for Windows and Linux. I used OpenLinuxBoot.efi to boot Linux, so I don't need to use grubx64.efi. In the startup menu, I want OpenCore to automatically detect Windows without detecting grubx64.efi, so I can't block the EFI partition. How can I block grubx64.efi?But please don't delete grubx64.efi, because I need to use it in BIOS.

hi on 0.7.9 I get 

38:026 00:080 OCB: Adding bless entry on disk - PciRoot(0x0)/Pci(0x14,0x0)/USB(0xA,0x0)/HD(1,GPT,18697105-A0AF-4EC8-98C6-FD3D5974F6DA,0x28,0x64000)
3Adding fs 44446C98 (E:1|L:1|P:Success) - PciRoot(0x0)/Pci(0x14,0x0)/USB(0xA,0x0)/HD(1,GPT,ADB4411E-D3C2-4B51-84C0-D90BD8F363C8,0x28,0x64000)
41:409 00:040 OCB: Adding fs 44408998 (E:0|L:0|P:Success) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0x0,0x0)/HD(1,GPT,659A1FA0-856B-4457-B6DA-04D4AD24BAD9,0x28,0x64000)
41:449 00:039 OCB: Adding fs 44408718 (E:0|L:0|P:Success) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0x0,0x0)/HD(2,GPT,60489D52-2111-488E-AEA3-DBC9F7C34F53,0x64800,0xEE6F800)
41:488 00:039 OCB: Adding fs 44408498 (E:0|L:0|P:Success) - PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0x0,0x0)/HD(3,GPT,F7A5E10B-2783-44D5-8392-0E47F7594425,0xEED4000,0xED9F000)
41:528 00:039 OCB: Found 4 potentially bootable filesystems
42:010 00:481 OCB: BootOrder/BootNext are not present or unsupported
42:049 00:039 OCB: Adding fs 2007C5F5 for 4 custom entries and nvram reset (aux shown)
42:089 00:039 OCB: Processing blessed list
42:129 00:039 OCB: Adding bless entry on disk - PciRoot(0x0)/Pci(0x14,0x0)/USB(0xA,0x0)/HD(1,GPT,ADB4411E-D3C2-4B51-84C0-D90BD8F363C8,0x28,0x64000)
42:170 00:041 OCBP: Predefined <nil> PciRoot(0x0)/Pci(0x14,0x0)/USB(0xA,0x0)/HD(1,GPT,18697105-A0AF-4EC8-98C6-FD3D5974F6DA,0x28,0x64000)/\EFI\BOOT\BOOTX64.EFI is missing - Invalid Parameter
42:210 00:039 OCBP: Blessed file is missing
42:249 00:039 OCBP: Blessed folder is missing
42:311 00:062 OCBP: Predefined <nil> \System\Library\CoreServices\boot.efi is missing - Not Found
42:352 00:040 OCBP: Predefined <nil> \EFI\Microsoft\Boot\bootmgfw.efi is missing - Not Found
42:395 00:042 OCBP: Predefined <nil> \EFI\BOOT\BOOTX64.EFI was found
42:435 00:039 OCB: Adding entry type (T:1|F:0|G:1) - PciRoot(0x0)/Pci(0x14,0x0)/USB(0xA,0x0)/HD(1,GPT,ADB4411E-D3C2-4B51-84C0-D90BD8F363C8,0x28,0x64000)/\EFI\BOOT\BOOTX64.EFI

I dont understand why cant the bloody system except the bless file and not regect it I have removed anything to do with security. 

EFI.zip opencore-2022-02-15-170759.txt

Edited February 15, 2022 by markl18

[eSaF]

I am sorry if this query has been answered before and also if the query comes across as idiotic. As an avid tester of Nightly Releases of OC I am confused by two factors, acidanthera/OpenCorePkg (All workflows), sometimes the Commit will have a red 'x' beside it with the comment 'This workflow run failed'. To my feeble understanding does this mean the package is unusable? Yet on https://dortania.github.io/ - it appears as Release, so what is it. Is it usable or not? Hope someone can put my feeble mind at ease with the answer.

Edited February 15, 2022 by eSaF

[Stefanalmare]

On 2/11/2022 at 12:52 PM, jsl2000 said:

Please try this one provided by MaLd0n.

EFI.Opencore.Desktop.LGA775.zip 4.52 MB · 9 downloads

Thank you! I have the system up and running: Asus P5Q, core 2 extreme qx9650, 8GB DDR2, HD 7750. Only issue is wake from sleep. I have the sensation that SATA is not waking up and the computer stall with no disk led activity and black screen. Anybody had this issue with ICH10?

[jsl2000]

14 hours ago, Stefanalmare said:

Thank you! I have the system up and running: Asus P5Q, core 2 extreme qx9650, 8GB DDR2, HD 7750. Only issue is wake from sleep. I have the sensation that SATA is not waking up and the computer stall with no disk led activity and black screen. Anybody had this issue with ICH10?

In my ASUS P5Q PRO hackintosh wake up from S3 sleep broken since High Sierra (10.13.x) or higher MacOS (10.14/10.15/11/12).

Can you wake up from S3 sleep at 10.13.x or higher MacOS  not just at Monterey (12.x) ?

And I don't think it's due to ICH10 which should be related to GPU activate Montitor issue.

For example my B85M-G & Z370 hackintoshs can wake up by ASUS VE276Q monitor, but failed in Z97 & M5A hackintoshs which only wake up by ASUS PB278 monitor.

Edited February 17, 2022 by jsl2000

[mnfesq]

I have a nagging problem that I just can't seem to solve.  Hackintool properly identifies my CPU as an i7-8850U @ 1.80 GHz.

Spoiler

 

Clover properly identifies my CPU as a 1.8 GHz Quad-Core Intel Core i7

Spoiler

 

But for some reason, OpenCore identifies my CPU as a 2 GHz Quad-Core Intel Core i7.

Spoiler

 

What gives and how can I fix this?  I have read up on the CPU Type variable in config.plist and it does not address the frequency of the CPU, only its type.  What controls the identification of the frequency?

[deeveedee]

@mnfesq Hackintool v3.8.4 identifies my CPU as i5-8250U @1.6GHz (correct base frequency).  In About This Mac (Big Sur 11.6.4), the Processor is listed as 1.8 GHz Quad Core i5 (wrong base frequency).  I'm using OC 0.7.8.

 

I wouldn't have noticed the discrepancy until you mentioned yours.  I don't have a fix - just saying you have company.

 

EDIT: We both have KabyLake-R CPUs (and I'm assuming you spoofed your device-id as 0x5916).

 

EDIT2: A quick scan of OC source seems to indicate that OC's CPU frequency detection is in Library/OcCpuLib/OcCpuLib.c.

 

EDIT3: @mnfesq I noticed that the CPU string in my HP Envy BIOS screen is identical to the CPU string reported by Hackintool.

Spoiler

 

If I had to guess, I'd say that Hackintool is pulling the CPU string from a register, while OC is creating its own CPU description with a calculated frequency.

 

EDIT4: @mnfesq I issued the following command in terminal and see why OC may be reporting 1.8GHz instead of 1.6GHz (on my rig):

sysctl hw.cpufrequency

Spoiler

 

Maybe OC is correct and everything else is wrong?

Edited February 23, 2022 by deeveedee

[MorenoAv]

Hi guys,

Tonight I updated my OpenCore to 0.7.9 and I have this text in picker : OC: Setting NVRAM 4D1FDA02-38C7-4A6A-9C06-4BCCABB30102:boot-path = PciRoot(0x0)/Pci(0x1B,0x4)/Pci(0x0,0x0)/NVMe(0x1,D1-FB-SB-46-4A-44-1B-00)/HD(1,GPT,EC61B213-1AC1-4941-9027-986BE34A48B5,0x28,0x64000)/EFI\OC\OpenCore.efi - Invalid Parameter.

I had this text with openCore 0.7.8, and this only happened after a re install of macOS Monterey, before the re install all was as it should, now although ocvalidate says that are no problems with my config.plist the text appears.

Also one more thing after changing scan policy for 0 my windows don't show in piker.

How do i solve this?

thank you

config.plist.zip

Edited February 21, 2022 by MorenoAv

[droples]

5 hours ago, MorenoAv said:

Hi guys,

Tonight I updated my OpenCore to 0.7.9 and I have this text in picker : OC: Setting NVRAM 4D1FDA02-38C7-4A6A-9C06-4BCCABB30102:boot-path = PciRoot(0x0)/Pci(0x1B,0x4)/Pci(0x0,0x0)/NVMe(0x1,D1-FB-SB-46-4A-44-1B-00)/HD(1,GPT,EC61B213-1AC1-4941-9027-986BE34A48B5,0x28,0x64000)/EFI\OC\OpenCore.efi - Invalid Parameter.

I had this text with openCore 0.7.8, and this only happened after a re install of macOS Monterey, before the re install all was as it should, now although ocvalidate says that are no problems with my config.plist the text appears.

Also one more thing after changing scan policy for 0 my windows don't show in piker.

How do i solve this?

thank you

config.plist.zip 4.29 kB · 3 downloads

 

[eSaF]

@MorenoAv -You have too many choices in PickerVariant in the config.plist, you must pick only one (like my attached) also I'd say your config.plist needs to clean up a bit, entries with the hashtag symbol needs deleting as it means lines with that symbol at the front are not needed therefore not loading.

Spoiler

 

[Anto65]

I think that's not even the problem ... I recreated the same configuration 🤔  ... the machine boots ( showing the GUI ) the same without errors like:
OC: Setting NVRAM 4D1FDA02 -........ Invalid Parameter ( @MorenoAv Maybe you have to reset the nvram? Post the entire EFI if you can , Gracias )

 

[MorenoAv]

Hi guys,

In the first place thank you all for your continuous help with my various issues and my endless noobisse...

Right know I'm not at home, when I arrive home I'll upload my entire EFI, what is curious is the fact that this same config.plist and the same configuration only gave me problems after reinstalling macOS Monterey. Before the re-installation I was using OpenCore 0.7.9 and I never had any such problems.

 

[MorenoAv]

Sorry guys, I haven't uploaded my EFI because when I arrived at home I decided to re-install macOS Monterey again to see if I was able to solve the related problems, and after resetting the NVRAM the annoying text disappeared...

Thanks again...

 

 

[ghost8282]

On 2/15/2022 at 1:49 PM, eSaF said:

sometimes the Commit will have a red 'x' beside it with the comment 'This workflow run failed'. To my feeble understanding does this mean the package is unusable?

Hi, most of the times it's usable, if you click on the little red icon, then on Details , you can see why the workflow fails.

Sometimes there are 404 errors, meaning that external resources are temporary not available, or it can fail to build on some compiler(s), but that doesn't mean that the package is non usable. If it fails because of compilation issue then it's another thing.

So summarizing, the red x only means that there was an error during the workflow, check why it failed (there could be billions of causes!) and you can see yourself if the package is ok or not.

 

For example:

 

Click on the red x:

 

You see that the package builds on all compilers, but fails on CI / Analyze Coverity.

Click on Details:

 

The workflow failed because coverity url returned error 500 (generic internal server error).

However the package is perfectly usable.

Edited February 24, 2022 by ghost8282

[mnfesq]

On 2/21/2022 at 2:03 PM, deeveedee said:

@mnfesq Hackintool v3.8.4 identifies my CPU as i5-8250U @1.6GHz (correct base frequency).  In About This Mac (Big Sur 11.6.4), the Processor is listed as 1.8 GHz Quad Core i5 (wrong base frequency).  I'm using OC 0.7.8.

 

I wouldn't have noticed the discrepancy until you mentioned yours.  I don't have a fix - just saying you have company.

 

EDIT: We both have KabyLake-R CPUs (and I'm assuming you spoofed your device-id as 0x5916).

 

EDIT2: A quick scan of OC source seems to indicate that OC's CPU frequency detection is in Library/OcCpuLib/OcCpuLib.c.

 

EDIT3: @mnfesq I noticed that the CPU string in my HP Envy BIOS screen is identical to the CPU string reported by Hackintool.

  Hide contents

 

If I had to guess, I'd say that Hackintool is pulling the CPU string from a register, while OC is creating its own CPU description with a calculated frequency.

 

EDIT4: @mnfesq I issued the following command in terminal and see why OC may be reporting 1.8GHz instead of 1.6GHz (on my rig):

sysctl hw.cpufrequency

  Hide contents

 

Maybe OC is correct and everything else is wrong?

 

I get the same result using 

sysctl hw.cpufrequency

 

Here's what my Clover bootlog looks like for CPU:

Spoiler

0:105  0:000  Running on: 'HP ENVY Laptop 17-ae1xx' with board '83AD'
0:105  0:000  === [ GetCPUProperties ] ========================
0:105  0:000  CPU Vendor = 756E6547 Model=806EA
0:105  0:000   The CPU supported SSE4.1
0:105  0:000   The CPU supported RDRAND
0:105  0:000  BrandString = Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
0:105  0:000   The CPU supported turbo
0:105  0:000   Energy PerfBias is  visible:
0:105  0:000  MSR 0x35               40008
0:105  0:000   TSC/CCC Information Leaf:
0:105  0:000    numerator     : 166
0:105  0:000    denominator   : 2
0:105  0:000   Calibrated ARTFrequency: 23993292
0:105  0:000   Rounded ARTFrequency: 24000000
0:105  0:000  MSR 0xE2 before patch 1E008008
0:105  0:000  MSR 0xE2 is locked, PM patches will be turned on
0:105  0:000  MSR 0xCE              0004043D_F1011400
0:105  0:000  corrected FLEX_RATIO = 0
0:105  0:000  MSR 0x1B0             00000000
0:105  0:000  FSBFrequency = 85 MHz, DMI FSBFrequency = 100 MHz, Corrected FSBFrequency = 100 MHz
0:105  0:000  MaxDiv/MinDiv: 20.0/4
0:105  0:000  Turbo: 37/37/40/40
0:105  0:000  Features: 0x77FAFBBFBFEBFBFF
0:105  0:000  Threads: 8
0:105  0:000  Cores: 4
0:105  0:000  FSB: 100 MHz
0:105  0:000  CPU: 1700 MHz
0:105  0:000  TSC: 1700 MHz
0:105  0:000  PIS: 100 MHz
0:105  0:000  ExternalClock: 25 MHz

 

As you can see, the FSB is adjusted from 85 MHz to 100 MHz.  That happens as a result of a setting in Clover that allows me to configure the CPU:

 

Spoiler

 

But you are correct that OC attempts to calculate the FSB while Clover uses the reported value.  I'm not sure why OC chooses the calculation method or if it results in better performance or more accurate sensor readings.  Thanks for your investigation!

Edited February 24, 2022 by mnfesq

[Guest 5T33Z0]

I've noticed that in the last 2 weeks a lot of errors are occurring under the "Actions" Tab of the OpenCorePkg Repo. Also, the last bOC uild available on the Dortania Repo is also about 10 days old. I wonder what's going on. 

[eSaF]

1 hour ago, 5T33Z0 said:

Also, the last bOC uild available on the Dortania Repo is also about 10 days old. I wonder what's going on. 

Yes quite noticeable, I have a theory about it but it is unmentionable plus I could be entirely wrong which is not surprising to be honest as I am often wrong with my assumptions but forgivable because I often use the get out of jail card - 'Senility' - You'll be surprise how great that works. 

[Matgen84]

2 hours ago, 5T33Z0 said:

Also, the last bOC uild available on the Dortania Repo is also about 10 days old. I wonder what's going on. 

 

Hi @5T33Z0 I just watched: all Opencorepkg commits are build as usual on the Dortania repo. Only the one from February 24 is not in the repo. There were no commits between Feb 16 and Feb 23, so no build. 😊

[Guest 5T33Z0]

18 minutes ago, Matgen84 said:

 

Hi @5T33Z0 I just watched: all Opencorepkg commits are build as usual on the Dortania repo. Only the one from February 24 is not in the repo. There were no commits between Feb 16 and Feb 23, so no build. 😊

 

That's not true. The last OC commit on the Dortanio Repo is ae04256 which is about 10 days old

[eSaF]

6 minutes ago, 5T33Z0 said:

That's not true. The last OC commit on the Dortanio Repo is ae04256 which is about 10 days old

Correct.

[chris1111]

Correct is  Acidanthera not Dortania

Why you guys not creating your build from Xcode inside macOS Monterey, its work verry good

[Guest 5T33Z0]

@chris1111 Because not everybody is a programmer and has XTools installed and wants to waste processing power, time and energy to compile OpenCore,…I guess.

[ghost8282]

2 hours ago, Matgen84 said:

Hi @5T33Z0 I just watched: all Opencorepkg commits are build as usual on the Dortania repo. Only the one from February 24 is not in the repo. There were no commits between Feb 16 and Feb 23, so no build. 😊

 

2 hours ago, 5T33Z0 said:

That's not true. The last OC commit on the Dortanio Repo is ae04256 which is about 10 days old

 

That's true what Matgen84 said, I don't really know why you are saying it's not true...

 

There were no commits between 16 and 23 Feb.

Dortania lacks only the latest commit (who knows why?Ask them), which however adds nothing to the package.

 

46 minutes ago, 5T33Z0 said:

Because not everybody is a programmer

 

There's no need to be a programmer (I'm not...) when the only thing you have to do is to have xcode installed, download the source and run one single command ./build_oc.tool from the terminal.

 

Who doesn't want to compile himself can wait for releases, can wait for dortania, can wait for somebody else to publish compiled packages, otherwise if one wants to be independent and on the cutting edge, then...install the tools, use some processing power and compile yourself.

 

5 hours ago, 5T33Z0 said:

I've noticed that in the last 2 weeks a lot of errors are occurring under the "Actions" Tab of the OpenCorePkg Repo.

 

What fails is coverity in the latest automatic checks:
 

make: error: sh -c '/Applications/Xcode_12.4.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode_12.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find make 2> /dev/null' failed with exit code 34304: (null) (errno=No such file or directory)
xcode-select: Failed to locate 'make', requesting installation of command line developer tools.

Being an ignorant, maybe something related to the setup on github, because it cannot find any command line developer tools.

All the latest builds compile perfectly fine.

Edited February 25, 2022 by ghost8282

[chris1111]

54 minutes ago, 5T33Z0 said:

@chris1111 Because not everybody is a programmer and has XTools installed and wants to waste processing power, time and energy to compile OpenCore,…I guess.

I think you undervalue yourself, you are very good at Hackintosh and you don't need to be a programmer for that

When you Installe Xcode and Command Line Tools from Apple Developper need Sign to developper

your not need to reinstall all stuf after macOS Update, you only to reopen Xcode then install componant

Its one Shot deal 

Edited February 25, 2022 by chris1111