Jump to content
8755 posts in this topic

Recommended Posts

1 hour ago, tmbt said:

I will post on this thread because you all seem much informed than the average .. What does it take to implement power management for non native NVME disks ? Do you think is "just" a patch to some kexts or something more complex ?

I'm asking around for this feature since when i noticed NVME disk is really more "expensive" for my battery than a normal sata ssd in MacOS but not on Linux or Windows ..

 

Thanks

Mattia

 

 

ThirdPartyDrives quirk only for sata.

It seems that these Memory Allocation problems are quite tricky.

What really surprises me here is the fact that DevirtualiseMmio = true causes early reboot.

What information would help the experts here to give some further advise?

It seems related to OpenCore, since I never ran into similar obstacles in Clover.

Thanks, Mike

@Mike Ranger You may need to dump a log (with DevirtualiseMmio on) and try around with the devirtualised ranges (search of the "OCABC" prefix) added to MmioWhitelist (not devirtualised). There is no real other way, except if you can dump the Kernel Panic with a serial connection.

Hello, I have a z87 board with and have add NVMe with pci-e adapter. 
The nvme-drive did show up initially, but later I added NvmExpressDxe.efi and it showed up. Is NvmExpressDxe.efi the preferred way to enable NVMe in oc? (For unsupported boards..)

2 hours ago, Ritte said:

Hello, I have a z87 board with and have add NVMe with pci-e adapter. 
The nvme-drive did show up initially, but later I added NvmExpressDxe.efi and it showed up. Is NvmExpressDxe.efi the preferred way to enable NVMe in oc? (For unsupported boards..)

 

It is the only way, there's no prefer/not prefer.

2 hours ago, Ritte said:

Hello, I have a z87 board with and have add NVMe with pci-e adapter. 
The nvme-drive did show up initially, but later I added NvmExpressDxe.efi and it showed up. Is NvmExpressDxe.efi the preferred way to enable NVMe in oc? (For unsupported boards..)

https://www.win-raid.com/t871f50-Guide-How-to-get-full-NVMe-support-for-all-Systems-with-an-AMI-UEFI-BIOS.html

6 hours ago, n.d.k said:

 

It is the only way, there's no prefer/not prefer.

 

Thanks! Do you know where I can find the source of the driver? So I don't need to get it from clover.

 

5 hours ago, jinbingmao said:

 

I did know about this, but I'm avoding it since this board will be swapped out sooner or later and will be reused as PLEX-server. Don't want to brick my BIOS otherwise I need a board for the PLEX-server too :)

34 minutes ago, Ritte said:

 

Thanks! Do you know where I can find the source of the driver? So I don't need to get it from clover.

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/Bus/Pci/NvmExpressDxe/NvmExpressDxe.inf || exit 1

# or Debug

build -a X64 -b DEBUG -t XCODE5 -p MdeModulePkg/MdeModulePkg.dsc -m MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressDxe.inf || exit 1

  • Like 2
7 hours ago, meaganmargaret said:

 

Care to share what AHCIPortInjector kext you used (I have the same motherboard)?  Was it the one you posted earlier?

 

Sure!

 

For starters here's what I looked for. In IOReg under SATA (or SAT0 if no name change) you see "name" and mine was "pci8086,a282" so I dug through whatever SATA Unsupported I could find until I found one with IOname matches.

SATA-unsupported.kext.zip

 

22 hours ago, LAbyOne said:

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/Bus/Pci/NvmExpressDxe/NvmExpressDxe.inf || exit 1

# or Debug

build -a X64 -b DEBUG -t XCODE5 -p MdeModulePkg/MdeModulePkg.dsc -m MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressDxe.inf || exit 1


 

Perfect, thanks! 

22 hours ago, LAbyOne said:

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/Bus/Pci/NvmExpressDxe/NvmExpressDxe.inf || exit 1

# or Debug

build -a X64 -b DEBUG -t XCODE5 -p MdeModulePkg/MdeModulePkg.dsc -m MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressDxe.inf || exit 1


 

Perfect, thanks! 

Hi - I've been trying to boot macOS Catalina on a new Lenovo X1 Carbon 7 which has a new Comet Lake i7-10710u. I see in ProcessorInfo.h that we don't have this processor defined yet. I wonder if this could contribute to the boot issue. Hoping this can help the devs add Comet Lake support.

 

After I select to boot the macOS installer, it performs kext injection but hangs here and does not proceed:

78:816 00:112 Prelinked status - Success

 

Attached is my debug log file (with full verbose logging) and here is the CPU info:

Signature A0660 Stepping 0 Model A6 Family 6 Type 0 ExtModel A ExtFamily 0

So i7-10710u Comet Lake is model 0xA6.

opencore-2020-01-04-014053.txt

  • Like 1

Can anyone help me? New to OpenCore.

 

Specs:

Dell 7567

i7 7700HQ

16GB RAM

Intel HD 630 + GTX 1050Ti

 

Followed the OpenCore vanilla guide and tried to boot with minimal setup. I can't see any options to select in OpenCore menu.

EFI.zip

82304809_2700475370032002_1083988331773034496_n.jpg

Edited by Nihhaar
Added specs
13 hours ago, Nihhaar said:

Can anyone help me? New to OpenCore.

 

Specs:

Dell 7567

i7 7700HQ

16GB RAM

Intel HD 630 + GTX 1050Ti

 

Followed the OpenCore vanilla guide and tried to boot with minimal setup. I can't see any options to select in OpenCore menu.

EFI.zip

82304809_2700475370032002_1083988331773034496_n.jpg

try to put on your config scanpolicy=0

 

Edited by Guest

Hi

So i also can now boot into recovery, after a lot of trial and error.

The following problem I have still with booting into recovery.

When I remove the -v boot flag, I get a black screen once boot is completed.

When I boot with -v into recovery, display is fine once boot is completed.

 

The only thing that seems to help is adding "agpmod=pikera"

But then booting into to OSX produces a funny login-screen resolution.

What could be the reason for black screen in recovery?

It happens as soon as a remove verbose mode flag from boot arguments.

 

Edit:

I am not sure if this is OC related or Whatevergreen related, or a combination of the settings I use in OC and using WG.

 

Thanks, Mike

 

Edited by Mike Ranger
24 minutes ago, Nihhaar said:

Thank you, it worked!

 

It seems like opencore team deliberately put wrong defaults so that users will read the configuration?

Default config are not wrong as are not working for all

Their goal I think is help people to learn and thinking :)

 

Edited by Guest
typo
32 minutes ago, Nihhaar said:

It seems like opencore team deliberately put wrong defaults so that users will read the configuration?

If you would *actually* read the PDF instead of just talking about being made, you would know why this is the default.

  • Like 1

I am trying to do a serial kernel debug with an USB serial port adapter connected via cable to a Windows 64 bit pc and using on it terminal app (https://sites.google.com/site/terminalbpp/) and CoolTerm (https://freeware.the-meiers.org/)

My goal is to have some useful data to share to devs/coder with some interst on AMD trx40 new platform

using opencore debug 0.53 and boot arg flag debug=0x11448

I can't see any printed value or useful info in log

Any advice about it?

 

Edited by Guest
10 hours ago, fabiosun said:

I am trying to do a serial kernel debug with an USB serial port adapter connected via cable to a Windows 64 bit pc and using on it terminal app (https://sites.google.com/site/terminalbpp/) and CoolTerm (https://freeware.the-meiers.org/)

My goal is to have some useful data to share to devs/coder with some interst on AMD trx40 new platform

using opencore debug 0.53 and boot arg flag debug=0x11448

I can't see any printed value or useful info in log

Any advice about it?

 

 

But for USB serial port adapter need driver.


I followed this tutorial https://github.com/khronokernel/Opencore-Vanilla-Desktop-Guide/blob/master/AMD/NullCPU-patch.md, after I deleted nullcpupowermanagement.kext, my Ryzen got panic: "Setting P-Limit is unsupported on this system"

EFI.zip

Edited by bondpham

I have another question regarding Quirks that are built into OpenCore

 

Currently for my system to boot, I need at least:

Comment         String  <-> 5960XPatch 10.14 by PMHeart
Disabled        Boolean <-> No
Find            Data<-> 483D0000 0040
InfoPlistPatch  Boolean <-> No
MatchOS         String <-> 10.14.x,10.15.x
Name            String<-> IOPCIFamily
Replace         Data<-> 483D0000 0080

and 

Comment    String  <-> _xcpm_pkg_scope_msrs by JamesK
Disabled   Boolean <-> No
Find       Data<-> 31D2E879 FDFFFF
MatchOS    String <-> 10.15.x
Replace    Data<-> 31D29090 909090

In Clover, both are not needed if the XCPMKernel Flag is selected. Without, the system will not boot.

 

Is this functionality covered in OpenCore as well through a quirk?

Thanks, Mike

 

 

Is it possible to disable XCPM in opencore for Skylake cpu ? I’m asking this because in clover i had FakeCpuId 0x0306a0 and NullCpuPowerManagement.kext so that HWP could work without XCPM. In opencore, I tried to set emulate CpuIdData A0060300 and CpuIdMask FFFFFFFF but boot fails with that settings.

×
×
  • Create New...