OpenCore General Discussion

[MacNB]

Feeling confident with OC, I thought I would take next adventure with my even older Hack and try OC Legacy boot.

 

System is a Dell Inspiron LGA 775 P35 Chipset with Xeon E5450 CPU with Legacy BIOS.

Currently successfully booting via Clover r5110. Running very stable for over 10 years !
It boots Windows 10, High-Sierra, Sierra, El-Capitan, Yosemite and even Snow Leopard 

Graphics is an nVidia Tesla GT240 (and that's the reason why I never updated this system OS higher that High Sierra).
Audio, Sleep, Wake, Restart, Shutdown, iMessage, FaceTime, etc all working fine with Clover.

 

I backed & removed all traces of Clover from the Main boot drive (including emulated NVRAM).

I installed OC 0.5.9 Debug released version onto a USB stick using this guide.

OC starts but here I encounter my first problem. The boot file installed by bootinstall.command on the USB root does not "see" any of my SATA drives. BootPicker (Builtin) only shows EFI Shell. 

I had to replace it with one I picked up from @fusion71au's MPS 1530 config-download here and then the BootPicker lists the bootable drives.
(So the boot file issue still needs to be solved as the "official" method does not work - to be solved)

Selecting High Sierra, OC starts the boot and the Kernel Panics on NVDAStartup. Since OC has no Quirks to "InjectNvdia", I had injected Device Properties for the GPU. But these did not work (even though OC log shows "success" for each Add. So I removed them.

I solved the problem by editing the DSDT and adding the GPU device properties under GFX0. And now the OS boots. 

 

Sleep & Wake seem to work. Shutdown works. But Restart fails - screen clears but the system hangs. 

Booting via Clover had no issue with Restart. To be solved.

 

I then installed OC onto the main SSD's ESP. Again I had to replace the boot file since the "official" one does not detect my SATA drives.

 

Next (main) problem is that this old system has no working FW NVRAM.

It was emulated when I was Using Clover.
With OC, I had setup Legacy method from the guide here 

 

This is now my bigger problem as emulated NVRAM does not work - without it, it's impossible to auto boot. 

I had installed Logouthook and then ran it again to generate the nvram.plist which was copied to the root of the ESP.
But OC cannot set the default boot drive.

I tried CTL+ENTER when selecting a macOS drive in the BootPicker (and the OS boots).
Log confirms Default is set but on reboot, it defaults to an EFI drive and NOT the Default.

 

I tried setting the default via System Prefs Startup Disk but that makes no difference.
The nvram.plist file is updated and there's an entry for BootOrder but looks like OC is not reading it or something else wrong.

I read back the defaults for com.apple.loginwindow LogoutHook and it shows:

sudo defaults read com.apple.loginwindow
{
    LogoutHook = "/Users/MacNB/LogoutHook/LogoutHook.command";
}

Summary settings in config are

Booter->Quirks:
• AvoidRuntimeDefrag: YES,
• DisableVariableWrite: NO
• EnableWriteUnprotector: YES
Misc->Security: ExposeSensitiveData: 15
NVRAM->LegacyEnable: YES

 

So, three problems I need to solve (in priority order):
1. Emulated NVRAM
2. Restart hang
3. Legacy boot file from LegacyBoot utility not working.

 

Any help with getting the Emulated NVARM would be appreciated (or the other issues).

Attached last OC log file, nvram.plist and my config.plist
Thanks 

 

 

opencore-2020-06-14-124848.txt

MacNB-config.plist

nvram.plist

[Andrey1970]

1 hour ago, Sherlocks said:

Andrey, is there other driver for elan ps2?

나의 SM-N960N 의 Tapatalk에서 보냄
 

In develop

https://github.com/kprinssu/VoodooPS2/tree/elan-ps2

[sxbkdljb]

Okay just an update, my audio problem is fixed by using SSDTTime to generate a SSDT for HPET. https://github.com/corpnewt/SSDTTime

[Sherlocks]

In develop
https://github.com/kprinssu/VoodooPS2/tree/elan-ps2

thanks a lot

나의 SM-N960N 의 Tapatalk에서 보냄

[markl18]

11 hours ago, eSaF said:

No - you're the one who is not getting it - before a machine boots into an operating system, one is able or should be able to go into the BIOS before it loads any operating system. That is what I was trying to explain to you but it seems all that went right over your head. Right let me start again, when you boot your machine start hitting the delete key as soon as you hear the Post BIOS Beep, by doing so you should be able to go straight into the BIOS before it boots windows. Here is where you can make any necessary changes to the operation of the machine and this is as far as I am prepared to go on the subject. Good luck.

Hi again at boot there’s no ac menu or anything but the stupid circle of dots yes I can get into machine using boot stick but that’s not the point and no nothing happens when I press space bar . If I press f2 if I need to get to bios and boot from usb not ssd

Edited June 15, 2020 by markl18

[gorans]

6 hours ago, eSaF said:

   What are you talking about - Boot sticks, circle of dots and space bar!!!!!!!!!!!!! Listen carefully, read your your Motherboard's manual on how to boot into the BIOS (without the aid of boot sticks and other utter nonsense) until you do, I will not offer any more on the subject. Somehow I think you're rushing into building a Hackintosh without doing any kind of research clearly evident by your lack of not knowing how to boot into a p/c's BIOS.

 

Maybe he needs to disable fast boot first, or boot to BIOS from Windows. Most of the time You can't enter BIOS with default "Fast Startup" enabled in Win10.

[SavageAUS]

i dont think you getting it goes right into windows there is no menu for opencore  or anything am I supposed to replace that efi file inside microsoft/boot/ to bootx64.efi or something to get the op menu to show up

What motherboard do you have? Every motherboard has a “Press X to enter bios” (X is an example but more examples are (escape key, F2, F10, F12 or even del (delete)).

The best method is to look up your motherboard on google for example Gigabyte X570 Aorus Pro WiFi and add the words “bios key” to it.

Once you find which key you need power off your machine, power it back on and mash (press the key lots, don’t hold it down unless your manual says too) the key to enter your bios.

Once in bios, find boot options and select the drive/partition opencore is on. Mine shows up as UEFI OS (insert drive name here).

 

 

Sent from my iPhone using Tapatalk

[mhaeuser]

If you have Windows installed (spinning circles...?), you can just use Advanced Restart to boot into FW UI

[sudoali]

On 6/10/2020 at 11:49 PM, Andrey1970 said:

In OC ACPI patch goes more conditions.
I showed as it to do, look for in this topic.

I ended up using `skip` and `count`. But used trial and error to find the right value for the `skip`. there were different number of `_CRS` in dsl and aml files. in my case the difference was 1.

Edited June 15, 2020 by sudoali

[dolgarrenan]

Hello @vit9696

 

I have been recently setting up the new NUC10i7FHN with latest OC 0.5.9 (which works) everything is working but there is no way to disable device AppleACPIEC via SSDT, the original BIOS contains PNP0C09 under device H_EC, everytime I try to disable it with the following code 

DefinitionBlock ("", "SSDT", 2, "ACDT", "SsdtEC", 0x00001000)
{
    External (_SB_.PCI0.LPCB.H_EC, DeviceObj)

    Scope (\_SB.PCI0.LPCB.H_EC)
    {
        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (_OSI ("Darwin"))
            {
                Return (0)
            }
            Else
            {
                Return (0x0F)
            }
        }
    }
}

It throws a KP at boot, I still haven't had this issue with any other build, so I'm a bit lost... To me it seems that H_EC on original DSDT is not loading, see code:

Scope (_SB.PCI0.LPCB)
    {
        Name (ONEW, Zero)
        Device (H_EC)
        {
            Name (_HID, EisaId ("PNP0C09") /* Embedded Controller Device */)  // _HID: Hardware ID
            Name (_UID, One)  // _UID: Unique ID
            Method (_CRS, 0, Serialized)  // _CRS: Current Resource Settings
            {
                Name (BFFR, ResourceTemplate ()
                {
                    IO (Decode16,
                        0x0062,             // Range Minimum
                        0x0062,             // Range Maximum
                        0x00,               // Alignment
                        0x01,               // Length
                        )
                    IO (Decode16,
                        0x0066,             // Range Minimum
                        0x0066,             // Range Maximum
                        0x00,               // Alignment
                        0x01,               // Length
                        )
                })
                Return (BFFR) /* \_SB_.PCI0.LPCB.H_EC._CRS.BFFR */
            }

            Method (_STA, 0, NotSerialized)  // _STA: Status
            {
                Return (0x0B)
                ^^^GFX0.CLID = 0x03
                Return (Zero)
            }

Here is where I'm a little confused, there is a Return (0x0B) and then a Return (Zero) under STA, system boots as is without trying to disable H_EC but loads Kernel Extension ACPIEC.. Here is a pic of the KP, 

which seems to me like the one I had on my X299X designare till RTC0 SSDT was made, I have tried with it and AWAC too, but nothing happens.. Could you shed some light here? Many thanks in advanced!

[markl18]

ok lets not flame all at once the spining circle is when windows boots in order to enter bios on my machine which is yoga 2 pro hd4400 4510u, I press f2 which can either boot from stick or ssd when I choose ssd it automatically goes into windows with out any oc menus even if mv mgfw.efi to mgfw.efi- and tell oc in misc which file to boot it still some how finds windows boot yes I ca always move that mgwf.efi some where else and boot into oc how does one setup dual boot

[markl18]

6 minutes ago, dolgarrenan said:

Hello @vit9696

 

I have been recently setting up the new NUC10i7FHN with latest OC 0.5.9 (which works) everything is working but there is no way to disable device AppleACPIEC via SSDT, the original BIOS contains PNP0C09 under device H_EC, everytime I try to disable it with the following code 

DefinitionBlock ("", "SSDT", 2, "ACDT", "SsdtEC", 0x00001000)
{
    External (_SB_.PCI0.LPCB.H_EC, DeviceObj)

    Scope (\_SB.PCI0.LPCB.H_EC)
    {
        Method (_STA, 0, NotSerialized)  // _STA: Status
        {
            If (_OSI ("Darwin"))
            {
                Return (0)
            }
            Else
            {
                Return (0x0F)
            }
        }
    }
}

It throws a KP at boot, I still haven't had this issue with any other build, so I'm a bit lost... To me it seems that H_EC on original DSDT is not loading, see code:

Scope (_SB.PCI0.LPCB)
    {
        Name (ONEW, Zero)
        Device (H_EC)
        {
            Name (_HID, EisaId ("PNP0C09") /* Embedded Controller Device */)  // _HID: Hardware ID
            Name (_UID, One)  // _UID: Unique ID
            Method (_CRS, 0, Serialized)  // _CRS: Current Resource Settings
            {
                Name (BFFR, ResourceTemplate ()
                {
                    IO (Decode16,
                        0x0062,             // Range Minimum
                        0x0062,             // Range Maximum
                        0x00,               // Alignment
                        0x01,               // Length
                        )
                    IO (Decode16,
                        0x0066,             // Range Minimum
                        0x0066,             // Range Maximum
                        0x00,               // Alignment
                        0x01,               // Length
                        )
                })
                Return (BFFR) /* \_SB_.PCI0.LPCB.H_EC._CRS.BFFR */
            }

            Method (_STA, 0, NotSerialized)  // _STA: Status
            {
                Return (0x0B)
                ^^^GFX0.CLID = 0x03
                Return (Zero)
            }

Here is where I'm a little confused, there is a Return (0x0B) and then a Return (Zero) under STA, system boots as is without trying to disable H_EC but loads Kernel Extension ACPIEC.. Here is a pic of the KP, which seems to me like the one I had on my X299X designare till RTC0 SSDT was made, I have tried with it and AWAC too, but nothing happens.. Could you shed some light here? Many thanks in advanced!

hi weg I think should have renamed your H_EC to EC or you have to doit but once oc did it you can't have ssd looking for H_EC because it is already renamed so you have rename ssd by hand by replacing H_EC to EC so that that SSDT should do it what ever it supposed to do now I am sure there are more knowledgeable people who will tell you what to do this is just my 2 cents worth  by the way AAPPLE doesn't understand H_EC but only EC hence all of the renaming goes on

[Andrey1970]

1 hour ago, sudoali said:

I ended up using `skip` and `count`. But used trial and error to find the right value for the `skip`. there were different number of `_CRS` in dsl and aml files. in my case the difference was 1.

Don't consider comments // _CRS

 

[Tiem]

34 minutes ago, markl18 said:

ok lets not flame all at once the spining circle is when windows boots in order to enter bios on my machine

Add your build to your signature. Nobody knows what hardware you run or how your system is set up.

The spinning circle is windows loading and already past the BIOS.

 

 

[markl18]

2 hours ago, Tiem said:

Add your build to your signature. Nobody knows what hardware you run or how your system is set up.

The spinning circle is windows loading and already past the BIOS.

 

 

lets start again of course I know how to get into bios and redirect to what ever setting but the question still stands how to set up dual boot before when I had my mgfw.efi renamed to something else and config.plist  misc section didnt exactly knew where that file was oc booted just fine I had no keyboard or mouse usage but windows  menu was there in the  external choser but didnt go anywhere because I didnt change the file name that misc->entries where I specified bootmgfw.efi- to be boot from but still it keeps on booting into windows that tells me that oc is telling it how to do it because bootmgfw.efi is not named properly for windows to boot by itself but rather through opencore. so I am back to squre one now does every one follow what i am saying 

[MacNB]

Anyone have any experience with setting up OC on Legacy BIOS system ?

I just cannot get Emulated NVRAM to work and without it, I cannot boot the correct macOS which I asked about here.

It's an old Dell 530 that's booting great with Clover but not with OC -- I'm trying to see if it's possible.

[markl18]

On 6/15/2020 at 2:17 PM, eSaF said:

Ok - Lets start again, if you're trying to dual boot windows and OS X (each OS on separate disks?) first thing you need to do is to remove the OS X disk out of the machine by either removing that disk by detaching the cable (if an ssd) or taking it out completely. This is to ensure that the windows OS can boot on it's own without any problems, once that is ascertain, now remove the windows disk out of the equation using the fore mentioned method and replace the OS X disk and install Opencore to the EFI Partition of this disk (Here I am assuming you have a working OS X installation). Are you with me thus far? Now reboot the machine, at the boot menu hit the space bar and choose clean/reset NVRAM, the machine will reboot again but you need to go into the bios and choose Opencore as your boot up disk and disable the named disk save and reboot. The machine should now boot up OS X with OpenCore. If the operation was successful, turn the machine off and reattached the disk containing windows, boot the machine again into the Bios and make sure that OpenCore is the first disk in the boot order menu and windows is the second and save. Opencore will now boot both disk at your choosing and leisure problem free if you put some thought into the process. Good luck.

I did everything like you said did nvram reset and then booted with clover into hackintosh put back bootmgfw.efi in boot and reboot in opencore and guess what it rebooted right back into windows I will even try to atach my config.plist shortly

 

Edited June 16, 2020 by markl18

[markl18]

6 minutes ago, eSaF said:

 

Pal you have me so confused with your posts on this subject - why is Clover in the equation? I thought Opencore was your main objective here. To successfully run Opencore on a system that previously had Clover as the boot loader, you have to get rid of every aspect of Clover from the system. Is the windows disk booting ok on it's own? If it is remove it from the system until you can get the OS X booting on it's own as well. The process is so clear cut I am beginning to wonder if this is a case of trolling 

clover is on usb stick my way of getting back just in case I mess up in OpenCore I just go into bios and tell the machine to boot from usb first  that's no other reason

[markl18]

6 minutes ago, eSaF said:

List your machine's specs as well as zip and post your opencore EFI Folder (remove your personal data).

I posted my config file but it won't let me attach the whole efi it is too big I just tried the oc folder is 70 mb compressed

Edited June 15, 2020 by markl18

[makk]

Vit

 

how do I get back in to Catalina to copy files from USB booter?

 

my USB installer keeps hanging.  Dosddude1 Catalina Patcher installer.

I used my Sierra USB installer and get to Terminal but, unable to copy files

to a what seems to be mounted Catalina Volume on /dev/disk1s6.

used /sbin/mount -uw / ; Volumes; Catalina; and a few others. I can edit but what keeps from coping from another Volume?  I copied onto the USB installer the necessary files to copy over.

 

I bungled my HD3000graphics kext somehow adding a VRAMSize statement

and a perl script to increase VRAM to patching.  This however caused a Black Screen.

 

second issue:

 

Open shell. Edited config.plist after saving and exiting restart, the configuration file was unable to be read.  unable to get to Picker screen.

 

What can be done?  I posted in the forum in Post installation.  I not sure if this is OC related entirely.
But, unable to use USB installer for Catalina which is strange because I use it to repatch afterwards.

What would prevent this USB installer from not getting back to the Install screens?

 

Makk

 

[dolgarrenan]

15 hours ago, markl18 said:

hi weg I think should have renamed your H_EC to EC or you have to doit but once oc did it you can't have ssd looking for H_EC because it is already renamed so you have rename ssd by hand by replacing H_EC to EC so that that SSDT should do it what ever it supposed to do now I am sure there are more knowledgeable people who will tell you what to do this is just my 2 cents worth  by the way AAPPLE doesn't understand H_EC but only EC hence all of the renaming goes on

Hi there, unfortunately there are no renames here, It would be easier just to undo what has been done. Renaming devices (in this case) is not an option, macOS doesn't understand what H_EC is, or at least it can't read from it because it does not belong to its code, while renaming might work we are only telling macOS to read a device we have migrated H_EC to EC, thus causing little boot failures and possible issues along the line.

Apple needs a clean plate to eat, if you rename H_EC (rubbish) to EC (clean plate) you are basically moving your s**t to the plate, creating a dummy EC defeats the purpose while renaming, we need to correctly dispose of that rubbish. (easy explanation)

 

Since macOS Mojave there is a need to use an Embedded Controller (EC) to correctly boot, so that's why we create a dummy for the OS to be complacent. If not done properly the kernelExtension AppleACPIEC loads at boot and that's what we are trying to avoid. I'm just summing up whats already in the documentation.

 

Key point, renaming is not the solution.

Edited June 16, 2020 by dolgarrenan
Note added for more information

[SavageAUS]

I posted my config file but it won't let me attach the whole efi it is too big I just tried the oc folder is 70 mb compressed

Remove the items that aren’t needed like the resources folder (largest folder) and try again. Keep removing non essential stuff until you can upload it. If you remove drivers or tools etc folder take a screenshot of it to share. Obviously copy the entire folder to your desktop then remove items.

 

 

Sent from my iPhone using Tapatalk

[hardcorehenry]

2 hours ago, dolgarrenan said:

Hi there, unfortunately there are no renames here, It would be easier just to undo what has been done. Renaming devices (in this case) is not an option, macOS doesn't understand what H_EC is, or at least it can't read from it because it does not belong to its code, while renaming might work we are only telling macOS to read a device we have migrated H_EC to EC, thus causing little boot failures and possible issues along the line.

Apple needs a clean plate to eat, if you rename H_EC (rubbish) to EC (clean plate) you are basically moving your s**t to the plate, creating a dummy EC defeats the purpose while renaming, we need to correctly dispose of that rubbish. (easy explanation)

 

Since macOS Mojave there is a need to use an Embedded Controller (EC) to correctly boot, so that's why we create a dummy for the OS to be complacent. If not done properly the kernelExtension AppleACPIEC loads at boot and that's what we are trying to avoid. I'm just summing up whats already in the documentation.

 

Key point, renaming is not the solution.

It's possible you need to disable original _STA in Device (H_EC) via rename _STA to XSTA and add this modified SSDT-EC-USBX.aml

 

SSDT-EC-USBX.aml

Edited June 16, 2020 by hardcorehenry

[dolgarrenan]

1 hour ago, hardcorehenry said:

It's possible you need to disable original _STA in Device (H_EC) via rename _STA to XSTA and add this modified SSDT-EC-USBX.aml

 

SSDT-EC-USBX.aml

Unfortunately it didn't work, but strange because log now shows a kind of different message, why isn-t the damned embedded controller disabling¿?¿? And why the KP... 

[hardcorehenry]

13 minutes ago, dolgarrenan said:

Unfortunately it didn't work, but strange because log now shows a kind of different message, why isn-t the damned embedded controller disabling¿?¿? And why the KP... 

 

Renaming _STA to XSTA is tricky, you have to rename it only in H_EC device by adding in patch count 1 and skip value(you have to count yourself). Post your untouched DSDT.aml(dumped via OC debug or acpidump.efi or clover(F4)) up to you.