Jump to content

[Pre-Release] macOS Sonoma 14.5

Wayang-NT

By Wayang-NT,
in New Releases and Updates

 Share
114 posts in this topic

Recommended Posts

deeveedee
deeveedee
Posted
Posted (edited)
6 minutes ago, eSaF said:

Right or wrong, I followed the 'Dortania OC Install Guide' and extracted the DSDT in Windows.

 

ACPI patching automation has come a long way - I'll need to review it.  OS updates don't change ACPI (don't change DSDT and SSDTs).

 

EDIT: If you update BIOS and/or change BIOS settings, then you may need to re-extract ACPI and create new patches.  Also true if you add / remove devices.

Edited by deeveedee
MorenoAv
MorenoAv
Posted
Posted (edited)

Yes I'm using OC Mod, and I now don't have conflicts with macOS And Windows, they work well together...

 

I reset the NVRAM, but no I didn't revert the patch or disable the DSDT, but I'm doing it now...

Edited by MorenoAv
deeveedee
deeveedee
Posted
Posted (edited)

@eSaF and @Anto65 I thought I was fairly good at asking questions when providing assistance, but I realize I need to add a question:  "When you say you are using Open Core, do you mean the official Open Core or an unreleased, forked version of Open Core?"

Edited by deeveedee
deeveedee
deeveedee
Posted
Posted (edited)

@eSaF agree that it is a good concept.  I remember briefly following the OC MOD project (never using) and providing a suggestion that OC MOD include a feature which allows easily toggling between multiple versions of config.plist.  But nothing that compelled me to abandon the official version (and now nothing that compels me to abandon the official released version of OC).  My days of regularly building my own OC from a GitHub branch are over.

Edited by deeveedee
MorenoAv
MorenoAv
Posted
Posted

I'm back and with one more re install and now I have WIFI, I remembered that o had an working EFI in my installation usb and now it works again...

Thanks all you for your inputs and help, I'll be back and explain all

 

deeveedee
deeveedee
Posted
Posted

@MorenoAv Congrats.  When you return with your explanation, I'd love to know whether the problem you reported was with Windows or macOS.  I now realize I need to add another question to my repertoire: "You said Wi-Fi is not working on your hackintosh.  Did you mean your hackintosh when running Windows or your hackintosh when running macOS?"  To be honest, that question never occurred to me before.  🤣

MorenoAv
MorenoAv
Posted
Posted (edited)

@eSaF, @deeveedee, @Anto65,

 

First I want to say that I use OC Mod because I used break all my Windows with the OC Official, I don't have a preference in what OC I use, I only want fewer problems with my OS.

For that reason I am able to make EFI That worked following the guide for dortania and with SSDT's pre built I did it on several occasions, before trying the SSDT.aml from @MaLd0n.

After asking @MaLd0n to make me a ssdt.aml I stayed with it, and it works almost all the time.

None the less my problems with Wii were in macOS in Windows the Wifi worked.

I hope to have explained all

Edited by MorenoAv
Anto65
Anto65
Posted
Posted

@MorenoAv I would like you to understand that it is not the official OC that breaks Windows but the DSDT

 

( if this were the case we should all use OC Mod )

 

If you have ways to build the official OC and disable the DSDT as mentioned above you will see that Windows boot without problems

 

( maybe something like this is missing !?
"If (_OSI("Darwin")) ... "
but my skills are not enough for this )

 

As for the Wi-Fi, I honestly didn't quite understand where the problem was...probably as identified by deeveedee's long eye on an old ioskywalk. kext...

 

However, it is important that you solved it

  • Like 2
MorenoAv
MorenoAv
Posted
Posted

Well in my limited understanding of OC I don't know what breaks the windows, but I'll ask, if it is the DSDT that breaks the windows why with OC MOD the same DSDT don't break the windows, because of the no ACPI? 

Me too I don't know why that has happened bit when I have time I'll find it, comparing the others EFi with this one until I find the culprit...

  • Like 1
deeveedee
deeveedee
Posted
Posted (edited)

@MaLd0n Another way that OC can break Windows is with ACPI patches that unconditionally change ACPI. I do the IRQ fixes with SSDTs instead of OC ACPI patches (e.g., I don't use config.plist > ACPI > Patch for IRQ fixes) so that I can condition them on _OSI("Darwin").  Why don't the ACPI patches like "TMR IRQ 0 Fix" affect Windows?  Just asking, because I don't know - not challenging your wisdom.  Thank you.

 

EDIT: Although, after I started disabling HPET, I no longer needed IRQ fixes.

Edited by deeveedee
  • Like 3
deeveedee
deeveedee
Posted
Posted (edited)

@Slice So the only reason that the TMR, RTC and PIC IRQ ACPI patches don't affect Windows is because they are unnecessary?  As I mentioned, I stopped applying IRQ patches after I started disabling HPET (which Apple did, I think starting with Mac Models in 2018).

Edited by deeveedee
  • Like 2
Slice
Slice
Posted
Posted
2 hours ago, deeveedee said:

@Slice So the only reason that the TMR, RTC and PIC IRQ ACPI patches don't affect Windows is because they are unnecessary?  As I mentioned, I stopped applying IRQ patches after I started disabling HPET (which Apple did, I think starting with Mac Models in 2018).

I said nothing about RTC and PIC. They are not obsolete.

  • Thanks 1
deeveedee
deeveedee
Posted
Posted

@Slice - @MaLd0n 's Proposed config.plist includes unconditional ACPI patches that change TMR, RTC and PIC IRQs. My question remains - if not obsolete, why don't these changes affect Windows? I'm asking because I don't know - not because I'm challenging anyone.

  • Like 2
  • Thanks 1
RobertX
RobertX
Posted
Posted (edited)

...just my 2 cents worth...I disabled HPET here in bios and was unable to boot to desktop, {do not enter sign over apple logo)... took a few restarts to correct, had to restart monterey from clover 5145, clear NVRAM, then reboot from clover 5157 to sonoma recovery, used disk utility on ssd, then finally reboot with clover 5157 to sonoma...this with smbios iMac 19,1

Edited by RobertX
  • Like 2
deeveedee
deeveedee
Posted
Posted (edited)
10 hours ago, RobertX said:

...just my 2 cents worth...I disabled HPET here in bios and was unable to boot to desktop,

 

I should have been clearer about "disable HPET."  Apple has been disabling HPET in ACPI since 2018 Mac models (including your iMac19,1).  I have never disabled HPET in BIOS and am not sure of the effects.  If you look at the EFI posted by MaLd0n, you'll see that his SSDT sets HPTE=0.  This causes HPET._STA = 0 for that particular ACPI.  Yours may be different.

Edited by deeveedee
  • Like 1
  • Thanks 2
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...