Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8755 posts in this topic

Recommended Posts

justin
justin
Posted
Posted
2 hours ago, seyd46 said:

As a computer scientist we are progressives.

 

A scientist should have no problem reading documents right, take a look at Docs/Configuration.pdf, you'll find something new that may hold back your opinion in this post

 

2 hours ago, seyd46 said:

especially since the installation is far from easy

 

The installation is easier than anything else if you read and understand the document.As for clover, there is basically no document, a graphic installer does not always mean easy. it is too hard to get the meaning of parameters in clover config.plist.

 

3 hours ago, seyd46 said:

with limited hardware support at least at the current time

 

i don't think so, the hardware supports depends on kexts, efi most of which clover uses are developed by the same members of opencore, e.g. whatevergreen, applealc, virtualsmc, apfsdriveloader.efi, aptiomemoryfix.efi.  i don't find there is differences between clover and opencore on hardware support. 

 

// PS: I was a clover user, still i am, but love opencore for it's simple structure and clean documents. no offense, just to clarify my feelings. 

 

 

  • Like 1
Erroruser
Erroruser
Posted
Posted
On 6/27/2019 at 2:49 PM, justin said:

@dgsga thank you a lot for the tip, i have successfully compiled the VariableRuntimeDxe.efi againt the OpenCorePkg/UDK. Sleep, reboot, shutdown all work on my Asrock B360M-HDV motherboard, here is what i did:


  


git clone https://github.com/acidanthera/audk UDK
cd UDK
source edksetup.sh
make -C BaseTools
build -a X64 -b RELEASE -t XCODE5 -p MdeModulePkg/MdeModulePkg.dsc -m MdeModulePkg/Universal/Variable/RuntimeDxe/VariableRuntimeDxe.inf --pcd=PcdEmuVariableNvModeEnable=1
cp Build/MdeModule/RELEASE_XCODE5/X64/VariableRuntimeDxe.efi ~/Desktop/

 

this does not work, nvram still doesnt work with the z390 asus board

justin
justin
Posted
Posted (edited)
5 minutes ago, errorexists said:

this does not work, nvram still doesnt work with the z390 asus board

 

Aha, then it's strange, im on B360M, this efi worked perfectly. without it, i don't get wroking shutdown, reboot or sleep/wake. 

 

by the way i use opencore v0.03, config.plist/LegacyEnable=NO

Edited by justin
Erroruser
Erroruser
Posted
Posted
1 minute ago, justin said:

 

Aha, then it's strange, im on B360M, this efi worked perfectly. without it, i don't get wroking shutdown, reboot or sleep/wake. 

i keep getting the f1 post an no issues with clover an if i run nvram -p i get no out put using OpenCore

image.png.58ba2b8e45889f43a79e33e3a648aa0f.png

Erroruser
Erroruser
Posted
Posted
57 minutes ago, justin said:

 

would you mind uploading your config.plist? (remove SN info)

i dont think it would help as i have had pavo an others from the discord channel look at it an all say its good as i have read the docs an differences an applied all the correct info an opened a bug report an been closed byhttps://github.com/acidanthera/bugtracker/issues/397#issuecomment-504645693
 

 

MacPato
MacPato
Posted
Posted
2 hours ago, Download-Fritz said:

@seyd46 Sorry, but criticism is hard to consider when there is no substance. What "hardware support" and "features" are lacking?

Possibly Z390 support for some that still have issues, (NVRAM Issues) But as i see by many posts on here the focus seems to be around booting windows, which leads me as to why people want to boot windows.

Surely making Opencore compatible with PC hardware to boot macOS would be more of a priority. and FYI constructive criticism is good and it's feedback.  

mhaeuser
mhaeuser
Posted
Posted

@MacFriedIntel Criticism is valueable so long as it is comprehensive enough to implement in the real world, yes.

As for Z390, it feels like there is a lot of confusion about the issue. It is not a plain "incompatibility" that needs "support added" for, from our current view it is either a design flaw in macOS (probably breaking the UEFI specification) or a severe bug in AMI's Aptio firmware. Basically, we tell UEFI to write a variable and it never comes back from it. This is not easy to debug and even if the issue was found, the solution might not be trivial.

  • Like 5
  • Thanks 1
MacPato
MacPato
Posted
Posted (edited)
16 hours ago, Download-Fritz said:

@MacFriedIntel Criticism is valueable so long as it is comprehensive enough to implement in the real world, yes.

As for Z390, it feels like there is a lot of confusion about the issue. It is not a plain "incompatibility" that needs "support added" for, from our current view it is either a design flaw in macOS (probably breaking the UEFI specification) or a severe bug in AMI's Aptio firmware. Basically, we tell UEFI to write a variable and it never comes back from it. This is not easy to debug and even if the issue was found, the solution might not be trivial.

 

I appreciate the response, if this seems to be an APTIO issue, then wouldn't clover have the same issue, as Clover boots the Z390 mostly without complications these symptoms only seem to occur with Gigabyte and some Select ASUS Boards, All i ask is that some care and consideration is taken towards this and is noted and looked at in some depth, because future chipsets may end up based around the same Aptio Structure as the Z390 this could be an ongoing issue for OpenCore in general unless some time is spent looking for a possible solution. But a welcomed response and i thank you. 

Edited by MacFriedIntel
MacPato
MacPato
Posted
Posted

I have noticed with @PMheart recent commit a structure change with renaming Tools to Utilities, will this be reflected in the Documentation as the macbuild.tool builds as per screenshot, but the structure in the documentation is still saying Tools?

 

Screenshot 2019-07-01 at 22.26.28.png

justin
justin
Posted
Posted
9 minutes ago, MacFriedIntel said:

but the structure in the documentation is still saying Tools?

 

Tools in the structure in the documentation is for config.plist/Misc/Tools, which contains third party efi tools, like UEFI SHELL.efi, CLEAN NVRAM.efi, which will show up in the opencore boot menu if configured in the config.plis.  Utilities is for scripts (e.g. sign OC) . they were both called Tools, it was confusing before this change/commit.

  • Like 1
MacPato
MacPato
Posted
Posted
1 minute ago, justin said:

 

Tools in the structure in the documentation is for config.plist/Misc/Tools, which contains third party efi tools, like UEFI SHELL.efi, CLEAN NVRAM.efi, which will show up in the opencore boot menu if configured in the config.plis.  Utilities is for scripts (e.g. sign OC) . they were both called Tools, it was confusing before this change/commit.

Okay this makes sense, thanks

  • Like 1
Slice
Slice
Posted
Posted
35 minutes ago, Download-Fritz said:

@MacFriedIntel There is no such difference between Clover and OpenCore, there is only a difference between using and not using the EmuVariable driver (OC needs edk2's applying to all OSes, Clover has its own, which does not work with OC)

Clover uses EDK2 driver 

  MdeModulePkg/Universal/Variable/EmuRuntimeDxe/EmuVariableRuntimeDxe.inf

Clover.dsc line 253

Pavo
Pavo
Posted
Posted
1 hour ago, nytr0 said:

Okay, having trouble getting bluetooth working on Catalina dp2 with Opencore. brcmpatchram2.kext is not loading and giving the message Invalid Parameter before boot. Is there a newer version that someone has that I can use that works with Catalina dp2? I have BCM4352

How is your entries made in config? This is what is should look like as a injector kext.

5x6m8kW.png

  • Like 1
xtddd
xtddd
Posted
Posted
On 6/14/2019 at 11:41 PM, fabiosun said:

@obus

without any CPU renames in config..I use this 


DefinitionBlock ("", "SSDT", 2, "CpuRef", "CpuSsdt", 0x00003000)
{
    External (_SB_.SCK0.CP00, DeviceObj)

    Scope (\_SB.SCK0.CP00)
    {
        Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
        {
            Debug = "Writing plugin-type to Registry!"
            If ((Arg2 == Zero))
            {
                Return (Buffer (One)
                {
                     0x03                                             // .
                })
            }

            Return (Package (0x02)
            {
                "plugin-type", 
                One
            })
        }
    }
}

thanks to macos86.it for help to solve it ;)

 

 i also will try it. thanks

hardcorehenry
hardcorehenry
Posted
Posted

I have two massages in OClog that bothers me. The first one:

 

OC: Missing GOP on ConsoleOutHandle, will install - Unsupported

 

Is this connected with the fact I have CSM enabled, no UEFI graphic card?(can’t flash UEFI_GOP rom on my ancient ati Radeon 4850) or I missing something. The second:

 

OCSMB: SmbiosLookupHost failed to lookup SMBIOSv3 - Not Found

 

I can’t find answers in configuration.pdf. Could someone give me hints or links, so I could solve it? Attaching my current config.plist

  • Like 1
 Share
Go to topic listing
×
×
  • Create New...