Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,809 posts in this topic

Recommended Posts

Jobe5150
Jobe5150
Posted
Posted (edited)

Hi all!

 

I was wondering if anyone can help me out with 2 issues:

 

I'm using a Dell 3521 i5-3317u Ivy 

 

I have open core installed and working so far, but I'm breaking down my issues and cleaning things up.

 

My keyboard and trackpad don't work, and if I do get them to work my trackpad buttons do not work.

 

Here is my config. Thanks for looking at my post!

config.plist

 

Edit: Sorry, have Catalina installed.

Edited by Jobe5150
Link to comment
Share on other sites
ameenjuz
ameenjuz
Posted
Posted
2 hours ago, Andres ZeroCross said:


Use this,, your system will be sleep well..

 

DSDT.aml

sleep worked fine 

how Can i fix this place 

when I add If_OSI patch in  _CRS METHOD OF TPD0  always Maciasl shows me a error

just I experience whenever if my DSDT lost then I patch from start.  just I m testing on clean DSDT

1732977565_ScreenShot2019-10-23at10_06_50PM.thumb.jpg.5e84c3bbe18a3c319cfbdecd70e058c7.jpg

 

 

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

sleep worked fine 

how Can i fix this place 

when I add If_OSI patch in  _CRS METHOD OF TPD0  always Maciasl shows me a error

just I experience whenever if my DSDT lost then I patch from start.  just I m testing on clean DSDT

1732977565_ScreenShot2019-10-23at10_06_50PM.thumb.jpg.5e84c3bbe18a3c319cfbdecd70e058c7.jpg

 

 


It's Out Of Topic, this thread just for OpenCore

Link to comment
Share on other sites
Leoyzen
Leoyzen
Posted
Posted

Opencore will not boot when using kvm and qemu topology(smp) and newer model rather than Penryn.

 

I digging in the code found that:

1. when cpu model is Penryn, then occpu will not lookup msr 0x35 but cpuid to get correct cpu topology

2. when cpu model is not Penryn, occpu will lookup msr 0x35 to get correct info, but QEMU/KVM do not have a msr node 0x35, it will show "1 cores 1threads" which make the xnu cpu panic.

 

I think it would be better check cpu model Penryn or "Hypervisor Present Bit:Bit 31 of ECX of CPUID leaf 0x1" (which is the feature "hypervisor" QEMU passthrough, from here), then get the topology from cpuid instead of msr 0x35.

 

The code snippet related: 

// or maybe we should also check "hypervisor" cpuid
if (Cpu->MaxId >= CPUID_CACHE_PARAMS && Cpu->Model <= CPU_MODEL_PENRYN) {
    AsmCpuidEx (CPUID_CACHE_PARAMS, 0, &CpuidCacheEax.Uint32, &CpuidCacheEbx.Uint32, NULL, NULL);
    if (CpuidCacheEax.Bits.CacheType != CPUID_CACHE_PARAMS_CACHE_TYPE_NULL) {
      CoreCount = (UINT16)GetPowerOfTwo32 (CpuidCacheEax.Bits.MaximumAddressableIdsForProcessorCores + 1);
      if (CoreCount < CpuidCacheEax.Bits.MaximumAddressableIdsForProcessorCores + 1) {
        CoreCount *= 2;
      }
      Cpu->CoreCount   = CoreCount;
      //
      // We should not be blindly relying on Cpu->Features & CPUID_FEATURE_HTT.
      // On Penryn CPUs it is set even without Hyper Threading.
      //
      if (Cpu->ThreadCount < Cpu->CoreCount) {
        Cpu->ThreadCount = Cpu->CoreCount;
      }
    }
  } else if (Cpu->Model == CPU_MODEL_WESTMERE) {
    Msr = AsmReadMsr64 (MSR_CORE_THREAD_COUNT);
    Cpu->CoreCount   = (UINT16)BitFieldRead64 (Msr, 16, 19);
    Cpu->ThreadCount = (UINT16)BitFieldRead64 (Msr, 0,  15);
  } else {
    Msr = AsmReadMsr64 (MSR_CORE_THREAD_COUNT);
    Cpu->CoreCount   = (UINT16)BitFieldRead64 (Msr, 16, 31);
    Cpu->ThreadCount = (UINT16)BitFieldRead64 (Msr, 0,  15);
  }

The oc log LEFT: using QEMU and Penryn with topology/smp set . RIGHT: using QEMU topology and IvyBridge,:

image.thumb.png.5593f67ca9b86a6b15e6b2d97592d7cd.png

Link to comment
Share on other sites
dgsga
dgsga
Posted
  • Author
Posted (edited)

Does anyone know if it is possible to set the macOS partition as the default boot selection in the boot picker on Z390 boards with borked firmware. On my rig the picker always defaults to the first listed volume. I have LegacyEnable set to YES and have nvram.plist loading correctly. Any help here would be much appreciated. Thanks.

Edited by dgsga
Link to comment
Share on other sites
Erroruser
Erroruser
Posted
Posted
1 minute ago, dgsga said:

Does anyone know if it is possible to set the macOS partition as the default boot selection in the boot picker on Z390 boards with {censored} nvram implementation. On my rig the picker always defaults to the first listed volume. I have LegacyEnable set to YES and have nvram.plist loading correctly. Any help here would be much appreciated. Thanks.

system preferences startup select drive

Link to comment
Share on other sites
Leoyzen
Leoyzen
Posted
Posted

I have something weird, the inject kext (USBPorts.kext, FakePCIID.kext, FakePCIID_Intel_GBx.kext) not load at all, but according to the opencore debug log, the kext loads succuessfully.

This blocks me switch from clover.

opencore log 

02:310 00:005 OCB: Matching <> args on type 1 0
02:315 00:004 OCC: Configuring behaviour 2
02:320 00:004 OCC: Setting cc mode 1 -> 1
02:326 00:006 OCABC: Only 246/256 slide values are usable!
02:331 00:004 OCABC: Valid slides - 10-255
02:337 00:006 OCC: Setting cc mode 1 -> 0
02:351 00:013 Trying XNU hook on System\Library\PrelinkedKernels\prelinkedkernel
02:362 00:011 Kext reservation size 8572928
02:816 00:453 Result of XNU hook on System\Library\PrelinkedKernels\prelinkedkernel is Success
02:832 00:016 OC: Read kernel version 19.0.0 (190000)
02:838 00:005 OCAK: algrey - cpu_topology_sort -disable _x86_validate_topology replace count - 1
02:843 00:004 OC: Kernel patcher result 0 for kernel (algrey - cpu_topology_sort -disable _x86_validate_topology) - Success
02:868 00:024 OCAK: PanicKextDump replace count - 1
02:872 00:004 OCAK: Patch success kext dump
02:920 00:047 OC: Prelink injection Lilu.kext () - Success
02:938 00:017 OC: Prelink injection VirtualSMC.kext () - Success
02:956 00:018 OC: Prelink injection WhateverGreen.kext (Video card) - Success
02:970 00:014 OC: Prelink injection FakePCIID.kext () - Success
02:986 00:016 OC: Prelink injection AppleALC.kext (Sound) - Success
02:991 00:004 OC: Prelink injection MCEReporterDisabler.kext () - Success
02:996 00:004 OC: Prelink injection FakePCIID_Intel_GbX.kext () - Success
03:008 00:011 OC: Prelink injection NullCPUPowerManagement.kext () - Success
03:012 00:004 OC: Prelink injection AGPMInjector.kext () - Success
03:026 00:013 OC: Prelink injection SMCSuperIO.kext () - Success
03:039 00:013 OC: Prelink injection SMCProcessor.kext () - Success
03:044 00:004 OC: Prelink injection USBPorts.kext () - Success
03:069 00:025 OC: Prelink injection SmallTreeIntel8259x.kext () - Success
03:099 00:030 Prelinked status - Success
03:120 00:020 OC: OcAppleGenericInputTimerQuirkExit status - Success
04:156 01:036 OC: OcAppleGenericInputKeycodeExit status - Success

kextstat says there is no fakepciid.kext loaded:

image.thumb.png.6c4b8e102bbdb53e739e658777bfa7ce.png

I checked multiple times that the config is set correctlly.

image.thumb.png.0bc8254b8bc043e11a4c45f913333910.png

 

 

Attachment is my efi folder, please give some help to make it work fEFI.zipor me.

Link to comment
Share on other sites
justin
justin
Posted
Posted
On 10/25/2019 at 3:08 AM, dgsga said:

Does anyone know if it is possible to set the macOS partition as the default boot selection in the boot picker on Z390 boards with borked firmware. On my rig the picker always defaults to the first listed volume. I have LegacyEnable set to YES and have nvram.plist loading correctly. Any help here would be much appreciated. Thanks.

 

you have to set ShowPicker=NO. 

Link to comment
Share on other sites
vit9696
vit9696
Posted
Posted

@Leoyzen, it is strange, and I would suggest you use kernel logs for tracing the issue. Add some debug code to FakePCIID init/probe/start methods and see what happens. Also check whether there is anything in the kernel log early at start.

 

Side note: you may actually be ok with just injecting vendor-id/device-id through DeviceProperties.

Link to comment
Share on other sites
DaGr8Gatzby
DaGr8Gatzby
Posted
Posted

Hello all. I didn't see anything related to this when I hit search so I hope this helps. I've been AMD Hackintoshing with OpenCore and Vanilla Patches and I was not able to boot Windows out of the box. I solved this by adding an entry here:

  

OpenCore version: 0.5.2
Misc > Entries

 

The sample.plist config has a nice template if you use that. Here it is again for reference:

 

Source: https://raw.githubusercontent.com/acidanthera/OpenCorePkg/cd8a046ce9920e5246a427e347f64ffe1ab63e2d/Docs/SampleFull.plist 

		<array>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Name</key>
				<string>CustomOS</string>
				<key>Comment</key>
				<string>Not signed for security reasons</string>
				<key>Enabled</key>
				<false/>
				<key>Path</key>
				<string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,11-22-33-44-55-66-77-88)/HD(1,GPT,00000000-0000-0000-0000-000000000000,0x800,0x64000)/\EFI\BOOT\BOOTX64.EFI</string>
			</dict>
		</array>

Here is what I have modified: 

<key>Entries</key>
        <array>
            <dict>
                <key>Arguments</key>
                <string></string>
                <key>Name</key>
                <string>Windows 10</string>
                <key>Comment</key>
                <string>Not signed for security reasons</string>
                <key>Enabled</key>
                <true/>
                <key>Path</key>
                <string>IDENTIFIER/\EFI\Microsoft\Boot\bootmgfw.efi</string>
            </dict>
        </array>

Here is what the identifer looks like for my machine: 

<string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,16-7D-50-71-53-38-25-00)/HD(1,GPT,094B0907-C4B8-48B1-8010-8BA5BF105D0E,0x28,0x64000)/\EFI\Microsoft\Boot\bootmgfw.efi</string>

You can use gfxutil to grab this path, but the way I did it was to boot EFI shell and run the following command: 

*BOOT EFI SHELL*

Shell> fs0:
fs0:\> map > maps.txt

I then mounted my ESP partition and was able to copy and paste the info into the plist file:

 

image.thumb.png.a724dbc35353f8f75c502a3d4943fc8f.png

 

I hope this helps somebody. Took me a bit of tries to get it working.

  • Like 1
  • Thanks 2
Link to comment
Share on other sites
Andrey1970
Andrey1970
Posted
Posted
15 hours ago, DaGr8Gatzby said:

Hello all. I didn't see anything related to this when I hit search so I hope this helps. I've been AMD Hackintoshing with OpenCore and Vanilla Patches and I was not able to boot Windows out of the box. I solved this by adding an entry here:

  


OpenCore version: 0.5.2
Misc > Entries

 

The sample.plist config has a nice template if you use that. Here it is again for reference:

 

Source: https://raw.githubusercontent.com/acidanthera/OpenCorePkg/cd8a046ce9920e5246a427e347f64ffe1ab63e2d/Docs/SampleFull.plist 


		<array>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Name</key>
				<string>CustomOS</string>
				<key>Comment</key>
				<string>Not signed for security reasons</string>
				<key>Enabled</key>
				<false/>
				<key>Path</key>
				<string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,11-22-33-44-55-66-77-88)/HD(1,GPT,00000000-0000-0000-0000-000000000000,0x800,0x64000)/\EFI\BOOT\BOOTX64.EFI</string>
			</dict>
		</array>

Here is what I have modified: 


<key>Entries</key>
        <array>
            <dict>
                <key>Arguments</key>
                <string></string>
                <key>Name</key>
                <string>Windows 10</string>
                <key>Comment</key>
                <string>Not signed for security reasons</string>
                <key>Enabled</key>
                <true/>
                <key>Path</key>
                <string>IDENTIFIER/\EFI\Microsoft\Boot\bootmgfw.efi</string>
            </dict>
        </array>

Here is what the identifer looks like for my machine: 


<string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,16-7D-50-71-53-38-25-00)/HD(1,GPT,094B0907-C4B8-48B1-8010-8BA5BF105D0E,0x28,0x64000)/\EFI\Microsoft\Boot\bootmgfw.efi</string>

You can use gfxutil to grab this path, but the way I did it was to boot EFI shell and run the following command: 


*BOOT EFI SHELL*

Shell> fs0:
fs0:\> map > maps.txt

I then mounted my ESP partition and was able to copy and paste the info into the plist file:

 

image.thumb.png.a724dbc35353f8f75c502a3d4943fc8f.png

 

I hope this helps somebody. Took me a bit of tries to get it working.

 

It becomes simply with BlessOverride.

  • Like 4
Link to comment
Share on other sites
moozuki
moozuki
Posted
Posted
On 10/21/2019 at 7:31 PM, moozuki said:

1. Holdover from Clover, sorry

2. My hardware NVRAM works just fine

3. SSDT-PLUG.aml was adjusted for my board

4. no way in BIOS

5. All my drives are SATA.

 

Had to make USB installer and re-install Catalina to get it to boot again, not the best solution.

It seems everytime I update kexts or OC , it gets the unable to load kernel cache error.

 

Solved the problem! Had a bad copy of VirtualSMC.

Link to comment
Share on other sites
DaGr8Gatzby
DaGr8Gatzby
Posted
Posted
2 hours ago, Andrey1970 said:

 

It becomes simply with BlessOverride.

 

This did not work for me. I just tested it. I'm booting Windows and Catalina off of the same drive and I already tried setting HideSelf to False. The only way I was able to get boot working is with this entry, which is why I posted it.

 

Good suggestion though!

Link to comment
Share on other sites
Andrey1970
Andrey1970
Posted
Posted
12 minutes ago, DaGr8Gatzby said:

 

This did not work for me. I just tested it. I'm booting Windows and Catalina off of the same drive and I already tried setting HideSelf to False. The only way I was able to get boot working is with this entry, which is why I posted it.

 

Good suggestion though!

 

ScanPolicy 

(bit 10) — OC_SCAN_ALLOW_FS_ESP, allows scanning of EFI System Partition file system.
  • Like 2
Link to comment
Share on other sites
n.d.k
n.d.k
Posted
Posted
33 minutes ago, Andrey1970 said:

 

ScanPolicy 

(bit 10) — OC_SCAN_ALLOW_FS_ESP, allows scanning of EFI System Partition file system.

Custom Entries are the way to get your particular boot entry to show up, changing ScanPolicy to allow Scanning ESP is not a good idea, there's are potentially my drives and multiple EFI partitions from a system, it will pollute the boot menu with multiple additional unwanted entries.

  • Like 1
Link to comment
Share on other sites
Andrey1970
Andrey1970
Posted
Posted
39 minutes ago, n.d.k said:

Custom Entries are the way to get your particular boot entry to show up, changing ScanPolicy to allow Scanning ESP is not a good idea, there's are potentially my drives and multiple EFI partitions from a system, it will pollute the boot menu with multiple additional unwanted entries.

 

If you have booter files on others ESP, means they to you are necessary. Otherwise why they there.)

Link to comment
Share on other sites
obus
obus
Posted
Posted
3 hours ago, DaGr8Gatzby said:

 

This did not work for me. I just tested it. I'm booting Windows and Catalina off of the same drive and I already tried setting HideSelf to False. The only way I was able to get boot working is with this entry, which is why I posted it.

 

Good suggestion though!

Try this: ScanPolicy 722179 HideSelf -> NO.

Works for me.

 

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