Jump to content

OpenCore General Discussion

dgsga

By dgsga,
in OpenCore

 Share
8,826 posts in this topic

Recommended Posts

crusher
crusher
Posted
Posted (edited)
6 minutes ago, STLVNUB said:

Where is that?

Download last Oc and then open Utilitis folder and u can see ocvalidate.

OpenTerminal Drag and dropi first ocvalidate and then config.plist and u can see where is the problem.

99150187-0fad5d80-2693-11eb-934f-8d49165d3992.png

Edited by crusher
  • Like 3
  • Thanks 1
Link to comment
Share on other sites
STLVNUB
STLVNUB
Posted
Posted
34 minutes ago, crusher said:

Download last Oc and then open Utilitis folder and u can see ocvalidate.

OpenTerminal Drag and dropi first ocvalidate and then config.plist and u can see where is the problem.

99150187-0fad5d80-2693-11eb-934f-8d49165d3992.png

Thanks

Link to comment
Share on other sites
mathew2019
mathew2019
Posted
Posted

Hi @vit969 @vandroiy2012

 

I have received my new AMD 6800XT graphics card and I have replaced my RX5700XT which is working fine with Big Sur but after installing 6800XT I am getting this rolling screen error. any idea what may be the issue? or is it a compatibility issue with Big Sur? any help appreciated

Thank you

 

IMG_6314.JPG

Link to comment
Share on other sites
Andrey1970
Andrey1970
Posted
Posted
21 minutes ago, mathew2019 said:

I have received my new AMD 6800XT graphics card and I have replaced my RX5700XT which is working fine with Big Sur but after installing 6800XT I am getting this rolling screen error. any idea what may be the issue? or is it a compatibility issue with Big Sur? any help appreciated

You hurried, macOS yet doesn't support 6800XT.

  • Haha 1
Link to comment
Share on other sites
mathew2019
mathew2019
Posted
Posted
5 minutes ago, eSaF said:

So as @Andrey1970 said not yet supported - Beast of a card though when it is.

I am not sure, with macOS release 11.0.1 the boot was stuck on apple logo/progress bar and with 11.1 beta macOS booting fine but without hardware acceleration..looking into IOreg it shows few models are compatible...like Dortania has said in his post..

Screenshot 2020-11-20 at 17.00.49.png

  • Thanks 1
Link to comment
Share on other sites
ichrioni
ichrioni
Posted
Posted

Opencore 0.6.3 macOS Big Sur - Audio,Battery & Trackpad Functionality on HP ENVY J053ea Laptop

 

CPU: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (Haswell)

GPU: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller & NVIDIA Corporation GK208M [GeForce GT 740M]

RAM: 16 GB 1600 MHz DDR3

Motherboard/Laptop Make and Model: Laptop HP Envy J053ea (17.2" 1920x1080)

Audio Codec: IDT 92HD91BXX & Intel Haswell HDMI

Ethernet Card: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

Wifi/BT Card: BCM4352 802.11ac Wireless Network Adapter

Touchpad and touch display devices: SynPS/2 Synaptics TouchPad

BIOS revision: Insyde//F.63

Which of the guides on the sidebar you used: Opencore 0.6.3 https://dortania.github.io/OpenCore-Install-Guide/extras/big-sur/#table-of-contents

What's working: WIFI/BT,Continuity & iCloud services.

and what isn't working: Audio,Trackpad,Camera input,Battery indication,Keyboard controls for Brightness.

I've tried all layout id's alcid=xx for my codec as mentioned on

https://github.com/acidanthera/AppleALC/wiki/Supported-codecs.

No sound is shown in output.

 

For Battery patching as per Rehabmans guide, https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/

I've decompiled the DSDT.aml and tried to use Acidanthera: MaciASL for patching using https://github.com/RehabMan/Laptop-DSDT-Patch/blob/master/battery/battery_HP-Envy-17t.txt

The above however generates an error.

 

Prior to using OC 0.6.3 I have been using this laptop for 7 years on OSX using Rehabmans Guide(Mavericks~Mojave) : https://www.tonymacx86.com/threads/guide-hp-envy-haswell-series-j-k-q-n-using-clover-uefi.261724/

 

Intention is to now transition away from Clover to OC provided I'm able to get the same installation and functionality.

 

Any troubleshooting or link sharing will be much appreciated.

DSDT & Config

zym5yzwcnj061.png

  • Like 2
Link to comment
Share on other sites
STLVNUB
STLVNUB
Posted
Posted
3 hours ago, 149113 said:

Still having boot issues. Any suggestions? I had a very stable OC Catalina with all the most recent patches running prior to the attempted upgrade to Big Sur.

IMG_6651.JPG

using OC6.0 here try it BS and Catalina

bifgsur_efi.zip

Link to comment
Share on other sites
PG7
PG7
Posted
Posted
On 11/20/2020 at 5:40 PM, mathew2019 said:

I can confirm that macOS 11.1 beta is loading with 6800XT graphics card but no acceleration...7Mb display 

Screenshot 2020-11-20 at 16.34.33 copy.png

Screenshot 2020-11-20 at 16.35.29.png

 

 

tesa with a FakeID of this "0x73001002 0x730F1002" in BigSur Beta 11.1
these IDs are already in the AMD9000Controlleur.kext of Beta 11.1
also has id 0x73101002 0x73121002 0x73181002 0x73191002 0x731A1002 0x731B1002 0x731F1002 0x73401002 0x73411002 0x73471002 0x73471002 0x734711002 0x73601002
in AMDRadeonX6000Framebuffer.kext which means that working FakeID should normally take

  • Like 3
Link to comment
Share on other sites
149113
149113
Posted
Posted (edited)

Finally got things up and running. Here is what I found & just in case this helps someone else out. As mentioned I had been running dual boot Opencore/Win 10 with 0.6.0 for a while with no issues at all. It was so stable that I have never had a single issue since converting from Clover to OC last winter. From my BIOS I had 3 entries in the boot section:

 

  1. Opencore
  2. Windows Boot Manager
  3. Other UEFI OS

 

I had been running fine on the Opencore selection until this upgrade to Big Sur. I ended up moving the Other UEFI OS to the top, keeping Windows Boot Manager second and eliminating the Opencore boot option entirely. Once I did that things started working. I don't know if Opencore got corrupted in any way but those were the ONLY changes I made to get things going. I have a Gigabyte Aorus Elite with the most recent firmware. Don't know if that is a known issue with that board?

 

The only remaining issue I have now is cracking audio that cuts out often. I have the alcid=1 entry in the boot arguments section. Should I change that to something else? That seemed to work fine for Catalina

Edited by 149113
  • Like 1
Link to comment
Share on other sites
Max.1974
Max.1974
Posted
Posted (edited)
12 hours ago, 149113 said:

Finally got things up and running. Here is what I found & just in case this helps someone else out. As mentioned I had been running dual boot Opencore/Win 10 with 0.6.0 for a while with no issues at all. It was so stable that I have never had a single issue since converting from Clover to OC last winter. From my BIOS I had 3 entries in the boot section:

 

  1. Opencore
  2. Windows Boot Manager
  3. Other UEFI OS

 

I had been running fine on the Opencore selection until this upgrade to Big Sur. I ended up moving the Other UEFI OS to the top, keeping Windows Boot Manager second and eliminating the Opencore boot option entirely. Once I did that things started working. I don't know if Opencore got corrupted in any way but those were the ONLY changes I made to get things going. I have a Gigabyte Aorus Elite with the most recent firmware. Don't know if that is a known issue with that board?

 

The only remaining issue I have now is cracking audio that cuts out often. I have the alcid=1 entry in the boot arguments section. Should I change that to something else? That seemed to work fine for Catalina

 

@149113 thanks for information, are you can explain in details or show your config.plist? Its because i have 2 OC EFI, one is for desktop and boot up Windows 7 normally without issue. But another, for my Lenovo, just up with Clover, i have no idea why, because both plist are the same, just different on drivers and kexts... 

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