Jump to content

OpenCore General Discussion


dgsga
8,887 posts in this topic

Recommended Posts

@Andres ZeroCross Why are you using named framebuffer? It's nonsense. Radeon cards in hackintosh must use default "automated" RadeonFramebuffer. With help of WhateverGreen. 

I also have RX 580 cards in several my PC's and i don't have any problems with reddish image or two monitor configurations. 

 

Read WhateverGreen FAQ. There are a lot of info why you shouldn't use named framebuffer at all!!!

 

You create problems by yourself mostly:)         

  • Like 1
Link to comment
Share on other sites

5 minutes ago, vandroiy2012 said:

@Andres ZeroCross Why are you using named framebuffer? It's nonsense. Radeon cards in hackintosh must use default "automated" RadeonFramebuffer. With help of WhateverGreen. 

I also have RX 580 cards in several my PC's and i don't have any problems with reddish image or two monitor configurations. 

 

Read WhateverGreen FAQ. There are a lot of info why you shouldn't use named framebuffer at all!!!

 

You create problems by yourself mostly:)         

Yes, you're right. SOmetimes i like to try the "old way" method :)

The problem is about binary / kernel patch in Catalina :)

Because AFAIK, this method still useful for Radeon R7 250/250X to set custom port with certain FB Name.

Edited by Andres ZeroCross
Link to comment
Share on other sites

3 minutes ago, nytr0 said:

7 days of working trying to get XHC working so i can use my mouse,usb ports, or bluetooth in 0.0.4 to no avail. It was working fine in the previous version, now it won't even load the ports in ioreg on my laptop. If the layout of Opencore hasn't changed , this should work, but it hasn't.  

All XHC is working here with lates commit 0.0.4


What's your problem with current 0.0.4 Opencore?

Link to comment
Share on other sites

19 minutes ago, nytr0 said:

7 days of working trying to get XHC working so i can use my mouse,usb ports, or bluetooth in 0.0.4 to no avail. It was working fine in the previous version, now it won't even load the ports in ioreg, yet loads them in hackintools on my laptop. If the layout of Opencore hasn't changed , this should work, why hasn't it? what changed? how can this be fixed?  

 

Reading your posts recently intrigued me to download v0.0.4.

 

Happy to report I experienced no issues with XHC for both of my laptop and desktop (nor issues with BRCM bluetooth).

Link to comment
Share on other sites

10 minutes ago, nytr0 said:

I removed Custom ACPI at the beginning of 0.0.3. XHC just will not work. All my kexts are updated. Here is my config (minus kexts for size).     

theConfig.zip

 

What????  you should joint all this SSDT into single SSDT. It will need time to read each SSDT and check compatible from one to another one SSDT.

Another thing is, i don't see any EC device in your configurations. Are you sure your embedded control device is ECDV?? not EC0?? Because i just see you have renamed EC0 to EC.

I am pretty sure with your current configuration you will get more trouble in windows or other OS when boot with OpenCore Bootloader

image.thumb.png.074cf62c656e4091b9b2ddabc513d72b.png

Edited by Andres ZeroCross
  • Haha 1
Link to comment
Share on other sites

6 minutes ago, nytr0 said:

I removed Custom ACPI at the beginning of 0.0.3. XHC just will not work once i updated to 0.0.4. All my kexts are updated. Here is my config (Dell XPS 9560 laptop).     

theConfig.zip

You've USBMap and USBPower kexts. Arent they doing similar things? You've had XHCI-unsupported enabled but not USBInjectall. Isnt these kexts supposed to work together? No. I had not checked other settings in your plist yet.

Link to comment
Share on other sites

3 minutes ago, onemanOSX said:

You've USBMap and USBPower kexts. Arent they doing similar things? You've had XHCI-unsupported enabled but not USBInjectall. Isnt these kexts supposed to work together? No. I had not checked other settings in your plist yet.

Why did he need XHCIUnsupported.kext?? Are you sure his XHC Device id is not supported by macOS???? AFAIK, most of XHC device id of Kabylake notebook is native supported by macOS. No need XHCIUnsupported.kext. USBInjectAll.kext will work as long as there is XHC, EH01, EH02 not XHC1, EHC1 or EHC2.

Link to comment
Share on other sites

24 minutes ago, nytr0 said:

I removed Custom ACPI at the beginning of 0.0.3. XHC just will not work once i updated to 0.0.4. All my kexts are updated. Here is my config (Dell XPS 9560 laptop).     

theConfig.zip


Can you try this please??? Reboot and upload your IOREG Output

config.plist

  • Like 1
Link to comment
Share on other sites

Just now, nytr0 said:

I had been trying everything involving XHC  to get XHC to work in different configurations -- enabling and disabling kexts thats why you see XHCIUnsupported.kext. Tips i've gotten so far, are to compress my ssdts into one big one and all i need to do is enable Usbinjectall, minimize kexts. OK, now uploading ioreg. 


 I will help,, but try config.plist above. Reboot and upload IOREG Outputt

Link to comment
Share on other sites

15 minutes ago, nytr0 said:

here's the ioreg from that config 

ioreg.ioreg

 

Something wrong with your SMBIOS,, i will check again your config.plist
image.png.b67fa1922b799908d0d39378ebb46b64.png

17 minutes ago, nytr0 said:

here's the ioreg from that config 

ioreg.ioreg


Use this,, make sure you have used latest commit of OpenCore from Github.

Reboot and upload your IOREG again

config.plist

Link to comment
Share on other sites

2 minutes ago, nytr0 said:

automatic or iMac18,1 worked fine in 0.0.3. I recently changed smbios to macbook pro in 0.0.4 because neither worked for xhc in 0.0.4 and macbook pro doesn't work either in loading xhc.


Can you just try my config.plist above and upload IOREG. It's about CustomSMBIOSGUID, and other lines. Just try and upload IOREG

Link to comment
Share on other sites

4 minutes ago, nytr0 said:


Justin is right,, there are many misconfiguration and unused ACPI Patch in your configuration. Rename ACPI Device is not good at all. It can cause problem to other operating system if you boot with it. But for now, i thought this is enough for your XHC. Try to make simple SSDT for your acpi, avoid renaming device of ACPI. If you need to add new device to ACPI, try to use _STA with If _OSI Darwin. SSDT-EC.dsl in OpenCorePkg/Doc/ACPISample can be your light.

Sorry for bad english

image.thumb.png.4b6366cf3722b6fa3d4d988295266ff8.png

Link to comment
Share on other sites

16 minutes ago, nytr0 said:

The manual was misinterpreted by me also.

 

it's not just the manual, if a aml, kext, efi is being used, you need to know what it does to your computer.

e.g. there is "-lilubetaall -wegbeta" in the boot arg, this indicates that you did not read the documents of Lilu.kext and Whatevergreen.kext. 

e.g. there is AptioInputFix.efi in the UEFI/Drivers/ but without VirtualSMC.efi and AppleUiSupoort.efi, this indicate you did not know what this efi does, and you did not know where it comes from.

e.g. UISCale is set to 10? did you really read through the OpenCore manual many times? 

e.g. You configured 33 SSDT-*.aml and  25 kexts, did you know what they are used for?

 

OpenCore is a very good piece of software, don't ruin it :)

Edited by justin
Link to comment
Share on other sites

6 hours ago, Andres ZeroCross said:


It's look i have give some wrong information before,, so i re-write the conditions of issue.

 

Conditions :
1. I have 2 patch for Orinoco and Salado Framebuffer in config.plist

 

Issue :
1. With or Without enable patch while using Orinoco Framebuffer, i still can get normal screen and dual screen capability in Mojave and Catalina DP 3 (actually because Orinoco have 2 HDMI Connector as default so i will not get reddish image)

2. Without enable Patch (Enable = No) while using Salado Framebuffer, i will get Reddish image and unable dual screen in Mojave and Catalina

3. With Enable Patch (Enable = Yes) while using Salado Framebuffer, i will get normal screen and dual screen capability in Mojave, but not in Catalina. Init Failure in Catalina.

The error means that AMD9500Controller.kext is not present in /System/Library/Prelinkedkernels/prelinkedkernel. We can inspect it for OpenCore issues. To do this we will need you to:

— start your system to UEFI Shell (without OpenCore)

— copy this file through UEFI shell to some other place

— boot OpenCore from UEFI Shell

— boot macOS from OpenCore

— confirm that the issues persists

— upload prelinkedkernel somewhere

 

Link to comment
Share on other sites

23 minutes ago, vit9696 said:

The error means that AMD9500Controller.kext is not present in /System/Library/Prelinkedkernels/prelinkedkernel. We can inspect it for OpenCore issues. To do this we will need you to:

— start your system to UEFI Shell (without OpenCore)

— copy this file through UEFI shell to some other place

— boot OpenCore from UEFI Shell

— boot macOS from OpenCore

— confirm that the issues persists

— upload prelinkedkernel somewhere

 


Is this same like this

1. I enter Clover UEFI Shell,, then i copy Prelinkedkernel to other place
2. I reboot My PC and boot to openCore, 
3. I select macOS caalina
4. Check about the issue
5. Upload prelinkedkernel (point 1)

Link to comment
Share on other sites

41 minutes ago, vit9696 said:

The error means that AMD9500Controller.kext is not present in /System/Library/Prelinkedkernels/prelinkedkernel. We can inspect it for OpenCore issues. To do this we will need you to:

— start your system to UEFI Shell (without OpenCore)

— copy this file through UEFI shell to some other place

— boot OpenCore from UEFI Shell

— boot macOS from OpenCore

— confirm that the issues persists

— upload prelinkedkernel somewhere

 


Before i make test,, please take a look at this picture. Prelinkedkernel show date number 3 July 20119, now is 12 July 2019. Is it ok?? Does prelinkedkernel must be updated?image.thumb.png.4d3b2ca514831c72eeb2e58af3ced8ef.png

Link to comment
Share on other sites

Generally that's fine. It should not change unless /S/L/E kexts change.

 

I reboot My PC and boot to openCore, 

Do not do that. Please boot straight to UEFI Shell (add it as EFI/BOOT/BOOTx64.efi) then load OpenCore. I have a suspect that EFI file system drivers are faulty, so better not to reboot.

Edited by vit9696
Link to comment
Share on other sites

5 minutes ago, vit9696 said:

Generally that's fine. It should not change unless /S/L/E kexts change.

 

I reboot My PC and boot to openCore, 

Do not do that. Please boot straight to UEFI Shell (add it as EFI/BOOT/BOOTx64.efi) then load OpenCore. I have a suspect that EFI file system drivers are faulty, so better not to reboot.


I have add this entry in my BIOS to BOOX64.efi of OpenCore (EFI/BOOT/BOOTX64.efi). 

Ok, i got it, i will send report ASAP

Edited by Andres ZeroCross
  • Like 1
Link to comment
Share on other sites

On 7/11/2019 at 8:43 PM, Andres ZeroCross said:

Nice Logo in OpenCore github.

 

I agree. It's a clean, simple and clever design. Good work.

 

EDIT: The vector in the PDF has some superfluous points which if removed would make the file simpler.

extra_points.thumb.png.719259cfd7b60cc80d638c093cb0d7f9.png

Edited by blackosx
  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...