Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,888 posts in this topic

Recommended Posts

matgeo
matgeo
Posted
Posted
3 minutes ago, Andres ZeroCross said:


Then it mean, you don't have EC device in your DSDT. 

I have a ECDV device. I rename ECDV to EC at config/plist but doesn't seems to work on OC (works with Clover).

On High Sierra everything is fine with OC on the same config.

Link to comment
Share on other sites
Andres ZeroCross
Andres ZeroCross
Posted
Posted
2 minutes ago, matgeo said:

I have a ECDV device. I rename ECDV to EC at config/plist but doesn't seems to work on OC (works with Clover).

On High Sierra everything is fine with OC on the same config.


Your config.plist only change ECDV to EC in DSDT table,, there is no guarantee there is no ECDV in other OEM SSDT

2 minutes ago, iTTT said:

hello,

 

may i know how to enable VT-d ? thanks.

Just go to BIOS and enable your VT-D,, it's simple like that

Link to comment
Share on other sites
iTTT
iTTT
Posted
Posted
4 minutes ago, Andres ZeroCross said:


Your config.plist only change ECDV to EC in DSDT table,, there is no guarantee there is no ECDV in other OEM SSDT

Just go to BIOS and enable your VT-D,, it's simple like that

 

BIOS already enabled.

 

how about setting for DisableIoMapper ? Yes or No ?

 

thanks.

Link to comment
Share on other sites
iTTT
iTTT
Posted
Posted
2 minutes ago, Andres ZeroCross said:

Ofcourse NO,, Block DMAR table = No, and don't use dart=0

 

...umm.... ok, then i set DisableIoMapper=No.

 

but i also use boot-args= dart=0,  no problem for sleep and wake.

 

should i delete dart =0 or change it to others value?

Link to comment
Share on other sites
Andres ZeroCross
Andres ZeroCross
Posted
Posted
Just now, iTTT said:

 

...umm.... ok, then i set DisableIoMapper=No.

 

but i also use boot-args= dart=0,  no problem for sleep and wake.

 

should i delete dart =0 or change it to others value?

dart=0 DisableIoMapper and drop DMAR is same function to prevent VT-D

Link to comment
Share on other sites
vandroiy2012
vandroiy2012
Posted
Posted
22 minutes ago, matgeo said:

OK.

Succesfully booted into Catalina after added a fake EC device with SSDT-ECUSBX.aml.

But now I have a EC and a ECDV device?

Would that be a problem?

SSDT-ECUSBX.aml

Screenshot 2019-08-14 at 12.06.09 pm.pdf

 

So disable it. There is a sample in OpenCore repo. https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/SSDT-EC-USBX.dsl#L34

  

    External (_SB_.PCI0.LPCB.ECDV, DeviceObj)

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

587696155_ScreenShot2019-08-14at12_28_36PM.thumb.png.3654f3713c5282cd578915b0445bd884.png

 

  • Like 1
Link to comment
Share on other sites
Andres ZeroCross
Andres ZeroCross
Posted
Posted
29 minutes ago, matgeo said:

OK.

Succesfully booted into Catalina after added a fake EC device with SSDT-ECUSBX.aml.

But now I have a EC and a ECDV device?

Would that be a problem?

SSDT-ECUSBX.aml

Screenshot 2019-08-14 at 12.06.09 pm.pdf

Disable ECDV can be problematic, some device still need ECDV. keep both is no problem after all. Just disable ECDV if get problem with it.

image.png

Link to comment
Share on other sites
Andrw0380
Andrw0380
Posted
Posted (edited)
2 hours ago, matgeo said:

OK.

Succesfully booted into Catalina after added a fake EC device with SSDT-ECUSBX.aml.

But now I have a EC and a ECDV device?

Would that be a problem?

SSDT-ECUSBX.aml

Screenshot 2019-08-14 at 12.06.09 pm.pdf

Here is mine after renaming ECDV to EC. Per looking over this thread, it says if this is a laptop, we have to keep the EC device after renaming since battery stats are tied to it. My laptop doesn't even allow me to disable ECDV as a test as if I do, my laptop will freeze during boot so just have to keep it there. Question I have though is I used Hackintool to customize my USB devices, in the past the tool wouldn't generate a SSDT-EC.aml, but now it does and it doesn't give me a SSDT-USBx.aml file. Is the USBx power properties no longer needed in 10.15 or in that case, do I just use the SSDT-ECUSBx.aml, without the EC portion? I do have a AppleBusPowerController in IOResources, but not on the EC device like 10.14 did when used with USBx.

IOReg.jpg

Edited by Andrw0380
Link to comment
Share on other sites
matgeo
matgeo
Posted
Posted
12 minutes ago, Andrw0380 said:

Here is mine after renaming ECDV to EC. Per looking over this thread, it says if this is a laptop, we have to keep the EC device after renaming since battery stats are tied to it. My laptop doesn't even allow me to disable ECDV as a test as if I do, my laptop will freeze during boot so just have to keep it there. Question I have though is I used Hackintool to customized my USB devices, in the past the tool wouldn't generate a SSDT-EC.aml, but now it does and it doesn't give me a SSDT-USBx.aml. Is the USBx power properties no longer needed in 10.15? I do have a AppleBusPowerController in IOResources, but not on the EC device like 10.14 did when used with USBx.

IOReg.jpg

How did you manage to do the renaming?

Would you mind uploading you oc folder?

Link to comment
Share on other sites
justin
justin
Posted
Posted
On 8/14/2019 at 6:17 AM, obus said:

 

For those how are noob:s like me and don't want to put embarresing questions about things that seems obvious for most of the people on this forum.  

Credits for this guide goes to cattyhouse on GitHub and translation from Chinese to English goes to Google translate:thumbsup_anim:

 

 

OpenCore installs various versions of macOS from Recovery's DMG
advantage

No need to download macOS installation files from the App Store
There is no requirement for the operating platform, as long as you can run the php command, so you can operate on Linux/Windows/macOS or even on a Linux server.
The download volume is very small, Recovery is only 400~500M
Support for the installation of various versions of macOS, solving the problem that is difficult to obtain in the old version of macOS
Disadvantage

Need to know how to configure OpenCore, you must configure it in advance. In fact, it is not a disadvantage, because even if you use the method of making a boot disk, you still need to configure OpenCore to start the computer.
After entering the installation interface, you need to connect to the network. The subsequent installation process needs to get the required files from Apple's server, usually running your bandwidth, so it is not a disadvantage.
step

Configure EFI for OpenCore

Download Recovery DMG

Get php script

Get the reference file for downloading the command of DMG

Take the Linux/macOS platform below, download the Mojave DMG as an example, go to the folder where the retain_recovery.php is located, and run the reference recovery_urls.txt:

Php obtain_recovery.php 00000000000KXPG00 Mac-7BA5B2DFE22DDD8C

Will download 2 files, RecoveryImage.dmg and RecoveryImage.chunklist

Prepare a USB flash drive with a capacity of 1GB or more and format it into Fat32 format.

Copy OpenEore's EFI to the root directory of the USB flash drive

Create a folder name in the root directory of the USB drive: com.apple.recovery.boot

Copy RecoveryImage.dmg and RecoveryImage.chunklist to com.apple.recovery.boot

Name the startup file

Create a new hidden file under the folder com.apple.recovery.boot .contentDetails
Content can be written casually, such as Mojave Boot From Recovery, the name will appear on the OpenCore boot menu.
The file structure on the final USB drive looks like this:

EFI
    ├── BOOT
    ├── OC
Com.apple.recovery.boot
    ├── RecoveryImage.chunklist
    └── RecoveryImage.dmg
    └── .contentDetails
Start the computer with a USB flash drive and select Mojave Boot From Recovery. Then you will enter the normal installation interface.

 

 

cattyhouse is me. 

  • Like 2
Link to comment
Share on other sites
maddie
maddie
Posted
Posted (edited)
On 8/14/2019 at 8:32 AM, NorthAmTrans said:

Used Debug and Target 67 (bit mask was fun to learn in the doc and with some google) and got my first boot log. Rad. Not sure that's the best value for that but it's what I landed on and seems to have given me a very descriptive log.

 

I see there's a ton of searching going on for my APFS volume. Should I be setting this so boot loader only sees my one APFS drive to avoid needless search and fail? 

 

Also this seems funny to me. Normal?

 

@maddie

Tagging you because you've been super helpful. I just moved OC off my flash drive. Very happy. 


18:770 00:057 OC: OcLoadNvramSupport...
18:827 00:057 OC: Invalid nvram data
18:882 00:055 OC: Deleting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:UIScale - Not Found
18:939 00:056 OC: Setting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:UIScale - Success

 

 

 

 

opencore-2019-08-13-222528.txt

 

Totally missed this. I think those warnings should be fine as long as you have working NVRAM. I think it's just being verbose telling you that the NVRAM->Add/Block sections in your config.plist are being parsed.

 

As for the APFS volume scanning, it's fine, don't worry about it.

Edited by maddie
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...