Jump to content
1709 posts in this topic

Recommended Posts

Hello @jsl2000 , 

 

has your config.plist  the cpu-patch what I can also use for OpenCore or is the cpu-patch different?

I have the same ASUS Mobo, but with AMD FX 4300.

 

Regards, Franziska1993

Edited by Franziska1993
18 minutes ago, Franziska1993 said:

Hello jsl2000, 

 

has your config.plist  the cpu-patch what I can also use for OpenCore or is the cpu-patch different?

I have the same ASUS Mobo, but with AMD FX 4300.

 

Regards, Franziska1993

Vanilla kernel patch for OpenCore is different from that of Clover.

Because I can enable ProvideCurrentCpuInfo quirk in Clover 5151 you may apply to your FX 4300 except change core No. from 6 to 4 in respective patches (totally 4 I think).

After I got how to convert RadeonDeInit from Clover to OpenCore I'll post my config.plist for OC 0.9.4 ASAP.

  • Like 1

Thank you all that helped me, I solved the issue with another usb drive, that one usually was used with windows, and this time with macOS it refused to create the ESP, but this problem was solved...

But the one that I can solve is the boot without usb installer, I'll upload my EFI folder for your help...

Thank you 

EFI.zip

13 hours ago, cankiulascmnfye said:

@jsl2000 Looks like there's no such thing as RadeonDeinit in OpenCore. But maybe this could be achieved with an ACPI or Kernel patch in OC as well

Can you or anyone who can provide more detailed info to fix this issue ?

2 hours ago, MorenoAv said:

Thank you all that helped me, I solved the issue with another usb drive, that one usually was used with windows, and this time with macOS it refused to create the ESP, but this problem was solved...

But the one that I can solve is the boot without usb installer, I'll upload my EFI folder for your help...

Thank you 

EFI.zip 16.96 MB · 4 downloads

 

Hi Moreno, apparently you used OCAT, but I'm not sure. I also see that it uses DSDT with some alerts (warnings) and if you manage to boot with your EFI, which is already something remarkable, because Opencore today has hardly accepted it, unless the DSDT is "perfect" and corrected, I see that the ESP problem is perhaps linked to a previous Windows installation. Unfortunately if so, the previous installation of Windows transforms the EFI partition into ESP. I suggest you use the GParted tool with Rufus to use as a partitioner. I suggest that you copy your EFI with it and paste it in the ESP. But better if you format all disk without partition and redo the process, starting from macOs first. Then Windows. Good luck.

 

You can try use SSDTTime to extract essentials SSDTs. After that, you can change for your DSDT. 

  • Like 1
  • Thanks 1
8 hours ago, MorenoAv said:

Thank you all that helped me, I solved the issue with another usb drive, that one usually was used with windows, and this time with macOS it refused to create the ESP, but this problem was solved...

But the one that I can solve is the boot without usb installer, I'll upload my EFI folder for your help...

Thank you 

EFI.zip 16.96 MB · 8 downloads

 

Hi @MorenoAv

There is some structure errors :

  • config.plist:  Kext order: Lilu must be first, followed by VirtualSMC, put AirportBrcmFixup to False (for Sonoma)
  • Structure: two kexts at EFI/, they must be in EFI/Kexts even if you don't use them.

Do you try to copy/paste your working USB EFI folder to your EFI Hard disk, reset NVRAM !

  • Like 3
  • Thanks 1
1 hour ago, MorenoAv said:

Thanks to @Max.1974, @Matgen84, @eSaF, for your help

Don't forget that Lilu MUST BE BEFORE its plugins, if a kext is not a Lilu plugin, it doesn't depend of Lilu and can be placed before Lilu or anywhere. IntelMausi is not Lilu plugin, so it can go before Lilu. But it's universally accepted that it's better that Lilu goes in the first place, VirtualSMC it's Lilu plugin and is a mandatory kext and better if is loaded in early stage.

  • Like 4
In my 13600k it starts perfectly from the flash drive, but when it should load the graphical environment the screen stays black. It doesn't like my 6800xt 

I have a RX 6800 XT in my AMD rig and I don’t believe I did anything special for it to work with Sonoma or anything prior. I do know I am not using Whatevergreen.

The only issue I have with that system is unless my monitor is on before I switch the pc on no OS can be seen on screen, not even OpenCore picker.


Sent from my iPhone using Tapatalk
Hace 1 hora, SavageAUS dijo:


Tengo un RX 6800 XT en mi equipo AMD y no creo que haya hecho nada especial para que funcionara con Sonoma o cualquier otra cosa antes. Sé que no estoy usando Whatevergreen.

El único problema que tengo con ese sistema es que, a menos que mi monitor esté encendido antes de encender el PC, no se puede ver ningún sistema operativo en la pantalla, ni siquiera el selector OpenCore.


Enviado desde mi iPhone usando Tapatalk

 

When I wrote that message it was the first attempt to install Sonoma, on June 6...

 

That happened to me because the first day if "-lilubetall" was not used when the desktop should load, the screen would go black. It's been a long time we don't need that to function in Sonoma 

"New" old toys on the block....:thumbsup_anim:

 

Intel 9th Gen i5-9600k Coffe Lake, RX 64 Vega GA B360M  OPENCORE 0.9.5 Full 

 

Smooth and fine 

 

Spoiler

image.thumb.png.ca642b35f4f91636e0906157cd9c1043.png

 

EFI-OC 095 - Intel i5-9600k - Coffe Lake 8thGen RX 64 Vega - GA-B360M.zip

Edited by Max.1974
  • Like 5
  • Thanks 1
On 8/19/2023 at 4:26 AM, jsl2000 said:

Vanilla kernel patch for OpenCore is different from that of Clover.

Because I can enable ProvideCurrentCpuInfo quirk in Clover 5151 you may apply to your FX 4300 except change core No. from 6 to 4 in respective patches (totally 4 I think).

After I got how to convert RadeonDeInit from Clover to OpenCore I'll post my config.plist for OC 0.9.4 ASAP.

Whatevergreen does the equivalent of RadeonDeInit - it's just setting an address to zero in the GPU. Whatevergreen actually just returns zero for that function call while Clover sets that register to zero.

 

It is possible to do via SSDT if you don't want Whatevergreen. Believe there was a post on this site, my Google skills are failing me though.

  • Like 4
1 hour ago, iCanaro said:

Thanks.

I have applied this SSDT.aml but it still got blank screen before login desktop of MacOS.

At present only Clover 5151 can boot it successfully at Ventura & Sonoma in my M5A(FX-6300) hackintosh.

Edited by jsl2000
  • Like 1
 
When I wrote that message it was the first attempt to install Sonoma, on June 6...
 
That happened to me because the first day if "-lilubetall" was not used when the desktop should load, the screen would go black. It's been a long time we don't need that to function in Sonoma 

Yeah Tapatalk playing up sorry about that.


Sent from my iPhone using Tapatalk

Hi all,

Today I made a new EFI folder and can boot Sonoma and Ventura with the same EFI, but now I have a problem with an error in OCValidate: 

OCS: Failed to calculate size of array field containing <empty> as type integer, context <4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102>!

Anyone knows how can is solve this problem?

Thanks for your time and patience with me...

I want to give a try to my studio PC - Asus Maximus VIII Gene + i7 6700K + RX6600, currently working just fine with the latest Ventura 13.5.1 and SMBIOS - iMac18,2. What is the best SMBIOS to use for the test ? Anybody succeeded with Sonoma and Skylake ?

2 hours ago, MorenoAv said:

Hi all,

Today I made a new EFI folder and can boot Sonoma and Ventura with the same EFI, but now I have a problem with an error in OCValidate: 

OCS: Failed to calculate size of array field containing <empty> as type integer, context <4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102>!

Anyone knows how can is solve this problem?

Thanks for your time and patience with me...

 

Are you try based with my EFI post above? 

(Moreno, você tentou se basear pela minha EFI genérica alguns posts acima?)

 

I never see this error before, but you can try based on my EFI, it's the same processor like mine. 

(Tente por gentileza se basear na minha EFI, é o mesmo processador que o seu).

  • Thanks 1
Guest
This topic is now closed to further replies.
×
×
  • Create New...