Jump to content
8755 posts in this topic

Recommended Posts

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.

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.

22 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


Too many USB Kext and USB Seting in your configuration :D

  • Haha 1
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
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

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

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

Just now, nytr0 said:

OMG IT WORKS! but it won't let me upload more than 10MB for the ioreg

Ofcourse it will work,, use IOREG 2.1 for small size. I will make custom SSDT for custom port. so you will get more 1 ssdt again. LoL

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

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
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

 

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)

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

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
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
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
14 hours 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.

Oke maybe this is stupid question.

I have BOOT to OpenCoreShell directly,, then i want to follow this step "— copy this file through UEFI shell to some other place". You mean i need to copy "PrelinkedKernel" right?

But in openCore shell, i only can see EFI partition only. FS0:, FS1:, FS2:, BLK1, BLK2-BLK21. None of them about macOS partition. Several letter just for EFI Partition. I have 3 OS in UEFI so i have 3 EFI Partition.

How can i copy PrelinkedKernel from OpenCoreshell if i can't access the macOS system partition :)

26 minutes ago, vit9696 said:
You can do the following:

load ApfsDriverLoader.efi

map -r

 

I am in shell, and i am in macos partition. But i can't go to System/Library/PrelinkedKernel. No directory to System/Library/PrelinkedKernel or System/Library/Extensions. It's look hidden, catalina use 2 disk in Container. Maybe it's the problem.

 

But if i got to Mojave partition, i can access it with "cd System/Library/PrelinkedKernels" or go to "cd System/Library/Extensions"

 

0f78b9886331a91dc4e223340f616a6a.jpg&key=493c0987b511d1a6c0b113c575842efcf0953df7c314645467fe3de028c1c1d0

 

9688aceb182beb42ba64998af9ce85d3.jpg

 

 

 

Sent from my iPhone using Tapatalk

Edited by Andres ZeroCross

I'd like to upgrade to Mojave and test out the Catalina beta but I have not been able to figure out the right combination of settings to get my onboard Intel UHD Graphics 630 working. Everything I have tried so far has resulted in the UHD framebuffer failing to load or a crash at boot and I have not been able to reach the desktop using the UHD Graphics. Any help getting the UHD Graphics working with OpenCore would be greatly appreciated. I've attached my current OpenCore config.plist which is working for booting High Sierra 10.13.6 using the GTX 1060.

config.plist

4 minutes ago, asstastic said:

I'd like to upgrade to Mojave and test out the Catalina beta but I have not been able to figure out the right combination of settings to get my onboard Intel UHD Graphics 630 working. Everything I have tried so far has resulted in the UHD framebuffer failing to load or a crash at boot and I have not been able to reach the desktop using the UHD Graphics. Any help getting the UHD Graphics working with OpenCore would be greatly appreciated. I've attached my current OpenCore config.plist which is working for booting High Sierra 10.13.6 using the GTX 1060.

config.plist

why you not have an gpu settings

image.png.9895ace24278c5a4ded99e1104f5f928.png

OpenCore_with_text_Small.png please tell me this is a joke logo cause it looks bad like it belongs in an ad for energy or some call center logo 

 

here is a phototshop job done of a real company logo with opencore logo its made for one another

blue-ocean-logo-high-res-e1426699782490.png

Edited by WarDoc
  • Haha 2
  • Sad 1
×
×
  • Create New...