Jump to content
8755 posts in this topic

Recommended Posts

It is for real Mac, but maybe someone can help me. MBP4.1, updated to the last beta, applied OCLP and no more admin user. My user become standard. I have tried to restore"--last-sealed-snapshot", to delete .AppleSetupDone, but no avail. Hints?

1 hour ago, Stefanalmare said:

It is for real Mac, but maybe someone can help me. MBP4.1, updated to the last beta, applied OCLP and no more admin user. My user become standard. I have tried to restore"--last-sealed-snapshot", to delete .AppleSetupDone, but no avail. Hints?

 

For those who might face this issue:

This works:

"I booted the Mac (6.1 MacPro) from an external hard drive. (Thank God I had a backup system ready)
Then I went into the terminal as an admin and edited the sudoers file on the internal hard drive:
sudo nano /etc/sudoers
And entered my user under the root entry:
root ALL=(ALL) ALL
(My user name) ALL=(ALL) ALL
After that, I saved the sudoers file and started my system normally from the internal hard drive.
Then I went into the terminal and executed this command:
sudo dscl . -append /Groups/admin GroupMembership (My user name)
There they were again, my admin rights in the right place."

https://www.reddit.com/r/OpenCoreLegacyPatcher/comments/1bdx538/no_mac_admin_account_after_installing_sonoma_with/

 

  • Like 2

Is somebody in here with a Skylake desktop system with iGPU?

 

I would like to try develop a new iGPU spoof via an SSDT and OSIEnhancer kext for running macOS 13+ on these systems with Intel HD 530. So I need a volunteer to test if the spoof works.

Edited by cankiulascmnfye
1 hour ago, cankiulascmnfye said:

Is somebody in here with a Skylake desktop system with iGPU?

 

I would like to try develop a new iGPU spoof via an SSDT and OSIEnhancer kext for running macOS 13+ on these systems with Intel HD 530. So I need a volunteer to test if the sppof works.

Yes i am using it ....SSDT-GFX0.aml Please check the attached SSDT 

  • Like 1
18 minutes ago, cankiulascmnfye said:

 

Awesome. Thanks.

 

So, I guess users need OSIEnhancer Kext, SSDT-Darwin and SSDT-GFXO to make it work?

yes absolutly 

  • Like 1
  • Thanks 1
10 hours ago, datafeedexpert said:

yes absolutly 

 

Do properties injected via SSDT have precedence over the ones injected via config plist?

 

In other words: can I leave the default properties in the config for older macOS versions and if a higher kernel is detected the igpu spoof is ijected via the SSDT OSIEnhancer combo?

 

Can you test, if this still works for you? it only injects the AAPL,ig-platform-id and the device-id.

 

I switched the method to use kernel versions instead of macOS versions, in order to future proof it a bit better, since we don't know the name of the next macOS version yet.

 

SSDT-GFX0.dsl

Edited by cankiulascmnfye
  • Like 1
On 1/13/2025 at 6:37 PM, cankiulascmnfye said:

In other words: can I leave the default properties in the config for older macOS versions and if a higher kernel is detected the igpu spoof is ijected via the SSDT OSIEnhancer combo?

i dont think its works because of the ACPI patch is compulsory for OSIEnhancer  
 

On 1/13/2025 at 6:37 PM, cankiulascmnfye said:

Do properties injected via SSDT have precedence over the ones injected via config plist?

No as per my understandig you cannot use both the ways at mixed mode injection of properties with config.plist | SSDT, While using OSIEnhancer it's better to use SSDT for properties injection 

 

On 1/13/2025 at 6:37 PM, cankiulascmnfye said:

Can you test, if this still works for you? it only injects the AAPL,ig-platform-id and the device-id.

i test it result is negetive while using only AAPL,ig-platform-id and the device-id

 

On 1/13/2025 at 6:37 PM, cankiulascmnfye said:

I switched the method to use kernel versions instead of macOS versions, in order to future proof it a bit better, since we don't know the name of the next macOS version yet.

yes using kernel versions method works perfact, but with my version sets of WEG properties. injection of only AAPL,ig-platform-id and the device-id not works on both methods.

Screenshot 2025-01-16 at 10.54.59 PM.png

Not working-Darwin-SSDT-GFX0.aml Not Working-OSname-SSDT-GFX0.aml Working Kernel-Method-SSDT-GFX0.aml

  • Like 4

@datafeedexpert Can you test if this table is still working?

 

I've only modified the _if OSI darwin method, so it's more universal:

 

If (_OSI ("Darwin 22") || _OSI ("Darwin 23") || _OSI ("Darwin 24") || _OSI ("Darwin 25"))   

 

Meaning: "apply fb patch if macOS Ventura, or Sonoma, or Sequoie or whatever the next macOS will be, is detected."

 

Is the DSM to XDSM rename a must, to make the spoof work? I think your ACPI patch is not configured correctly if it is intended to only rename the _DSM method of the iGPU. In this case you would need to add the PCI path to the igPU "base" entry. The way it's configured now, it renames all occurences of _DSM.

 

SSDT-GFX0.aml

Edited by cankiulascmnfye
  • Like 3
  • Haha 1
13 hours ago, cankiulascmnfye said:

Is the DSM to XDSM rename a must, to make the spoof work? I think your ACPI patch is not configured correctly if it is intended to only rename the _DSM method of the iGPU. In this case you would need to add the PCI path to the igPU "base" entry. The way it's configured now, it renames all occurences of _DSM.

_DSM to XDSM rename is must @b00t0x (https://github.com/b00t0x/OSIEnhancer) mentioned to use it, i inserted base : \_SB.PCI0.IGPU to ACPI-> Patch.

If (_OSI ("Darwin 22") || _OSI ("Darwin 23") || _OSI ("Darwin 24") || _OSI ("Darwin 25"))   
Above darwin method works...

thanks @cankiulascmnfye

  • Like 4

@datafeedexpert and @cankiulascmnfye I didn't know about the "Darwin [kernel version]" _OSI condition with OSIEnhancer - very cool.  I'll have to revisit old hacks to see if I ever needed Darwin-version-specific ACPI patches that couldn't be handled by simple "If (_OSI("Darwin")).  I think this conditional might have been useful had I tried to create a single Open Core EFI that supported High Sierra and Big Sur running on my Dell Latitude E6410.

 

EDIT: It would be helpful if DeviceProperties in OC config.plist could have _OSI conditions.

 

EDIT2: Very cool to see Slice and Rehabman referenced in the credits.

Edited by deeveedee
  • Like 2
On 1/13/2025 at 10:37 AM, cankiulascmnfye said:

Is somebody in here with a Skylake desktop system with iGPU?

 

I would like to try develop a new iGPU spoof via an SSDT and OSIEnhancer kext for running macOS 13+ on these systems with Intel HD 530. So I need a volunteer to test if the spoof works.

Here...

  • Like 1

@ichelash If you'd like to test it, the instructions are on my repo

 

@deeveedee So far, the only use case I found is iGPU spoofing. As of now the only other use case I can imagine would be ioname-spoofing in macOS Sequoia for for Intel WifI cards, so Modern WiFi root patches can be applied to make AirportItlwm kext work

 

 

Edited by cankiulascmnfye
  • Like 1
1 minute ago, cankiulascmnfye said:

@ichelash If you'd like to test it, the instreuctions are on my repo

 

Let me get to it..i had give up on hacks...skylake freezes randomly until you force restart..screen flickers...too much trouble 🤣

  • Like 1
5 minutes ago, ichelash said:

Let me get to it..i had give up on hacks...skylake freezes randomly until you force restart..screen flickers...too much trouble 🤣

 

8 minutes ago, cankiulascmnfye said:

@ichelash If you'd like to test it, the instreuctions are on my repo

 

@deeveedee So far, the only use case I found is iGPU spoofing. As of now the only other use case I can imagen would be ionema-spoofing in macOS Sequoi for for Intel WifI cards, so Modern WiFi root patches can be applied to make AirportItlwm kexts work

 

 

Screenshot2025-01-19at22_50_12.png.c48a995ba8f8d420226064f616b9a3a8.png

Not found

  • Like 1
On 1/20/2025 at 4:33 PM, ichelash said:

I use P530 device-id..and it's HD 530...It does not work with the real device-id

Screenshot2025-01-20at18_32_06.png.137a0299073f66de57a9dfc00e4ef0b0.png

 

Afaik, when using the Intel HD530 on desktops, supposedly device-id 12590000 and AAPL,ig-platform-id 00001259 should be used. And iMac18,3 SMBIOS.

 

I think i am going to put this spoof on hold since I cannot test it myself. The whole idea behind it was to ONLY spoof a different device-id and AAPL,ig-platform-id with an SSDT based on the loaded darwin kernel but not to inject a complete framebuffer patch. Because it may be different for different mainboards.

 

The best result is probably to use the OCLP method to re-install the required Skylake drivers.

17 hours ago, cankiulascmnfye said:

 

Afaik, when using the Intel HD530 on desktops, supposedly device-id 12590000 and AAPL,ig-platform-id 00001259 should be used. And iMac18,3 SMBIOS.

 

I think i am going to put this spoof on hold since I cannot test it myself. The whole idea behind it was to ONLY spoof a different device-id and AAPL,ig-platform-id with an SSDT based on the loaded darwin kernel but not to inject a complete framebuffer patch. Because it may be different for different mainboards.

 

The best result is probably to use the OCLP method to re-install the required Skylake drivers.

When i use device-id 12590000....it doesn't work at all.

  • Like 1
×
×
  • Create New...