[pre-release] macOS Ventura

[Henties]

1 hour ago, 5T33Z0 said:

 

Whether or not a device is headless depends on the chosen AAPL,ig-platform-id and the framebuffer it's associated with. A framebuffer is considered "empty" if it only contains dummiy connectors. Since ig-platform-id (0x59120000) has connectors, it's technically not an empty framebuffer (that would be 0x59120003). But it doesn't matter since you're only using it to trick macOS Ventura into "believing" you are using a Kaby Lake CPU with Intel HD 630 graphics.

 

0x59120000

 

0x59120003

Thks, it's all coming back now. Did all this many moons ago. A connectionless framebuffer would be the best choice for my Skylake environment.

Now wading through all the ones availablele for a Kaby Lake.

 

Greetings Henties

[Extreme™]

4 hours ago, PoMpIs said:

 

It's not that it removed "powerd"... simply by doing a clean installation of Beta 4 it hasn't shown up anymore... and the computer is working normally, it goes to sleep, and it doesn't wake up by itself like before, nor is there any high CPU usage for no reason 🤷‍♂

 

 

I did not do a clean installation but upgrade from beta 3 to beta 4 and as you have seen in the video I posted a few posts behind I am not running the powerd process yet the problem of CPU stress in idle is still there. But it seems that today everything is going well because strangely I did not have abnormal CPU consumption in idle.

[D3v1L]

no more problem here...after add schedule via terminal, all goes well. "powerd" it's on 0,1/0,2% cpu usage every time. Normally.

 

all ok with my own ssdt and oc 0.8.4 🙂 👍 all perfect.

[Extreme™]

2 hours ago, D3v1L said:

no more problem here...after add schedule via terminal, all goes well. "powerd" it's on 0,1/0,2% cpu usage every time. Normally.

 

all ok with my own ssdt and oc 0.8.4 🙂 👍 all perfect.

How add schedule via terminal? 

[Henties]

@Hervé  @Cyberdevs in the meantime I have waded through and injected each one of the 19 KBL FBs available in Hackintool, into the correct iGPU address space being PciRoot(0x0)/Pci(0x2,0x0)

 

Not one of them allows me to install Ventura beta 4 from a USB installer, the same one that I used to install Ventura beta4 on my GA-Z490 Vision G hacks.

 

It seems that merely injecting is not all that is needed, there must be something else that is required but I am not able

to figure out what that should be.

 

I am using iMac17,1 as the system definition for this GA-Z170-UD3 hack.

 

I have attached a list of all the KBL FBs which I used for testing.

 

Appreciate your further assistance.

 

Greetings Henties

  

KBL Framebuffers tested.rtf

Edited August 1, 2022 by Henties

[miliuco]

2 hours ago, Extreme™ said:

How add schedule via terminal? 

@chris1111 has a script to do this as temporary fix.

https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/?do=findComment&comment=2790325

 

Edited August 1, 2022 by miliuco

[PoMpIs]

Would someone be so kind as to remind me what the command was for the GPU to appear in the activity monitor please

 

 

It's that when I do a clean installation it doesn't come up anymore, and I don't remember... Among so many messages I can't find it 😅..

 

Thank you very much

Edited August 2, 2022 by PoMpIs

[chris1111]

With Ventura 13 you cannot eject the EFI partition without having to cancel another disk

Here a Simple app to Eject EFI on Ventura 13 

Note: you can not Unmount "EFI 1" or "EFI 2" Only EFI is available to unmount.

Update: Eject EFI Ventura 13-V2 can unmount any EFI partition

 

For quick access I put in my Applications then drag to my DOCK

Spoiler

 

Eject EFI Ventura 13-V2 can unmount any EFI partition

 

 

Eject EFI Ventura 13.zip

 

Update Eject EFI Ventura 13-V2 can unmount any EFI partition

Eject EFI Ventura 13-V2.zip

Edited August 4, 2022 by chris1111
Eject EFI Ventura 13-V2 can unmount any EFI partition

[Guest ricoc90]

23 minutes ago, PoMpIs said:

Would someone be so kind as to remind me what the command was for the GPU to appear in the activity monitor please

 

defaults write com.apple.ActivityMonitor ShowGPUTab -bool true

 

[Alex HQuest]

@Cyberdevs don't ask me why, but erasing the entire disk fixed whatever was crapping my install. No changes to the few days old OC, Lilu and friends, nor the config.plist. Now to get Windows 10 reinstalled again (shared NVMe)...

 

Edited August 2, 2022 by Alex HQuest

[D3v1L]

8 hours ago, Extreme™ said:

How add schedule via terminal? 

 

 

 

 

 

[datafeedexpert]

On 7/27/2022 at 7:40 PM, Rocky12 said:

@datafeedexpert i'm not the expert if u asking about connector patching

config.plist-macOS Monterey.zip 5.98 kB · 17 downloads

@Rocky12Here is your IGPU properties screen shot , Have to check both display connecter ? HDMI works good but DP no display using your IGPU Properties and boot args you used in this config.plist { igfxfcms=1 -igfxdvmt igfxonln=1 } My Optiplex 7050 MT Have 3 Connector (HDMI - DP - VGA) ( i5-6500T )

[Guest 5T33Z0]

@PoMpIs defaults write com.apple.ActivityMonitor ShowGPUTab -bool true

 

Oh, ricoc was faster.

Edited August 2, 2022 by 5T33Z0

[Rocky12]

@datafeedexpert i don't have  Monterey on this machine any more and really no idea about connector patching i have ventura installed without any connector  patch only platform id

 

[Henties]

I have still not been successful in setting up a GA-Z170X-UD3 hack, presently configured with iMac17,1 SMBOS, as per the attached EFI folder, to a SMBIOS of iMac18,1 with a working iGPU framebuffer. 

 

The objective is to upgrade macOS Monterey to Ventura 13 beta 4 and still end up with a working framebuffer. 

 

I can actually get rid of the "Skylake No Entry" message after I have changed the SMBIOS from iMac17,1 to iMac18,1 in the config.plist section PlatformInfo-->Generic-->SystemProductName iMac18,1 

 

This change to my config.plist actually ensures that Ventura 13 beta 4 can actually be installed with a USB-stick installer, however without a working framebuffer.

 

I have tested all 19 Kaby Lake frame buffers available through the latest version of Hackintool. The attachment "KBL Framebuffers tested" refers.

 

The 19 tests actually involved plugging-in each framebuffer pair of the columns "AAPL,ig-platform-id" and "device-id" of the attached file, into the respective placeholders of the EFI config.plist file under:

 

DeviceProperties-->Add-->PciRoot(0x0)/Pci(0x2,0x0) and then followed by system restart.

 

None of the FB test combinations resulted in a functional framebuffer.

 

It could well be that I am approaching this from a totally wrong angle and would appreciate for anybody to help me along in finally achieving the desired result.

 

The attached EFI folder has been working for my Skylake system for many months/years without any problems whatsoever, including 

"Wake for network access",  "Enable Power Nap" and "Sleep"

 

The dGPU used is a AMD 580XT and under Skylake the iGPU is configured via a headless framebuffer.

 

Greetings Henties

 

 

EFI.zip KBL Framebuffers tested.rtf

Edited August 2, 2022 by Henties

[PoMpIs]

10 hours ago, ricoc90 said:

 

defaults write com.apple.ActivityMonitor ShowGPUTab -bool true

 

 

2 hours ago, 5T33Z0 said:

@PoMpIs defaults write com.apple.ActivityMonitor ShowGPUTab -bool true

 

Oh, ricoc was faster.

 

thanks a lot 

 

[D3v1L]

if any1 wanna try...this is my efi...

 

Aorus Pro z390 bios f12

RX6600XT

MacPro7,1

 

just add your/new smbios data and try...

in ssdt there are : MCHC smbus fix, USB-EC fake, USBX power and PMC for nvram.....

 

cpufriend is set to "false"...if you have cpu like mine (i5 9600K), you can set cpufriend and cpu data to true...otherwise, make your cpudata kext...

 

No WEG, no devirtualisemmio, no mmio whitelist, IRQ 0/8 patch...

 

everything is ok (for update and/or clean install of Ventura...)

 

maybe only need to set your usbmap (i use kext for this 'couse i use other system in my rig)

 

kext update at this time, OC 0.8.4

 

🙂

 

EFI.zip

[Cyberdevs]

@Henties

try this:

EFI.zip

and remind me again what is the model of your CPU?

[Henties]

@Cyberdevs Intel Core i7-6700K

 

Thks  for your EFI will have to try it a bit later though and come back to you with feedback. 

 

Greetings Henties

[Henties]

@Cyberdevs I now tested the modifications you applied to my EFI folder and report as follows:

 

After slight "modifications" to your modifications, your modified EFI folder works quite well with iMac17,1 as the configured SMBIOS - no problems discovered so far - the "pikera...." boot arg now seems to be superfluous, great.

 

Using that EFI, obviously with all the relevant settings applied, does still not allow me to select a framebuffer that is actually working with a SMBIOS setting of iMac18,3 and the KBL framebuffer that you inserted, as well as some of the others that I have retested - particularly the 2 headless fbs. that KBL offers. 

 

I have again attached the EFI folder, this time with most of your modifications included, but without the extensive "obliterations" of relevant, "ostensibly sensitive" identifiction data, only the serial number has been partly obliterated making it easier for us to exchange information required to hopefully arrive at a resolution of this problem I am experiencing.

 

Thank you very much for your, to say the least, extensive input, which is much appreciated, in assisting me in this effort to hopefully finally sort this out eventually.

 

Greetings Henties

 

 

EFI.zip

[Cyberdevs]

@Henties

As far as I've tested the SMBIOSes only the following will work:

iMac18,1 Macmini8,1 and MacPro7,1 I couldn't get the iMac18,3 to work with the iGPU.

[Henties]

@Cyberdevs I follow what you are saying, in my particular environment I should perhaps try another one of the SMBIOSes you have listed, that's actually quite fair, will do so  and report back. At this juncture I need to attend to some other chores I have been neglecting, will revert back as soon as time permits.

 

In the interim it would be interesting if there are others that can, and are willing to make their contribution in helping me in resolving this peculiar problem.

 

For quite a while I have been wondering whether this particular problem will just be history once Ventura 13 beta has been installed, with a framebuffer in Ventura 13 beta 4 being readily available for configuration in the native Ventura environment which the installer created. Just wandering.

 

Greetings Henties

[D3v1L]

19 hours ago, D3v1L said:

if any1 wanna try...this is my efi...

 

Aorus Pro z390 bios f12

RX6600XT

MacPro7,1

 

just add your/new smbios data and try...

in ssdt there are : MCHC smbus fix, USB-EC fake, USBX power and PMC for nvram.....

 

cpufriend is set to "false"...if you have cpu like mine (i5 9600K), you can set cpufriend and cpu data to true...otherwise, make your cpudata kext...

 

No WEG, no devirtualisemmio, no mmio whitelist, IRQ 0/8 patch...

 

everything is ok (for update and/or clean install of Ventura...)

 

maybe only need to set your usbmap (i use kext for this 'couse i use other system in my rig)

 

kext update at this time, OC 0.8.4

 

🙂

 

EFI.zip 9.46 MB · 19 downloads

Wow 'bout 20 download, no one say it works, it not works...cool 🤣

Edited August 3, 2022 by D3v1L

[Derty]

1 hour ago, D3v1L said:

Wow 'bout 20 download, no one say it works, it not works...cool 🤣

 

I think your EFi is not right D3viL 

 

Edited August 3, 2022 by Derty

[Henties]

@Cyberdevs Success.

I took the plunge and installed Ventura beta 4 into an existing APFS HDD partition with ample free space thus creating a volume group of which Ventura 13 Beta (22A5311f) is just one of the members of that particular APFS volume group.

 

Subsequently I used Migration Assistant to migrate all data, settings as well as apps from the Skylake NVMe, all apps are functional except 3 Rogue Amoeba programs and Little Snitch. For the latter the latest nightly build sorted out the problems with Ventura, Amoeba is presently working on Ventura compatible updates for its product range.

Xcode also still needs to be updated with the beta for Ventura, but that can wait.

 

What this all means is that my Skylake hack has received another lease of "modern" life, with the KBL 0x59120000

framebuffer also allowing video processing with hardware acceleration.

 

Will now install Monterey 12.5 Release (21G72) over itself with a SMBIS of iMac18.1, hoping that this will also sort out the

the KBL framebuffer spoofing problem in that particular environment. If successful one single EFI folder can be used to boot any of the 2 macOS versions in operation.

 

Greetings Henties