[Release] macOS Monterey 12.5.1

[maly70]

4 hours ago, Joshua60 said:

@Slice

 

Because I only have the Framebuffers given in https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md and all have

0 connectors and Stolen memory 1MB. 

 

(0x9BC80003 0x9BC50003 0x9BC40003)

They are the only Framebuffers that work but with 7MB VRAM.

 

It's my guess but I think there is a little confusion between Coffee Lake and Comet Lake Framebuffers.

hi, try 07009B3E and device id as: C89B8868 

Edited August 18, 2022 by maly70

[Joshua60]

@Cyberdevs

 

The system stop at 'detected device Novoton NOT679BD'.

 

So, I think I will update OC.

 

Thanks again for your help.

[Cyberdevs]

6 minutes ago, Joshua60 said:

@Cyberdevs

 

The system stop at 'detected device Novoton NOT679BD'.

So, I think I will update OC.

I already updated the EFI but I might have missed something, compare it to you efi and remove what's unnecessary  

[Anto65]

Full Installer

 

https://swcdn.apple.com/content/downloads/18/44/012-51693-A_2W745BUZP7/xtd63whw506llesta7af6cjvcxlyj8mxvf/InstallAssistant.pkg

[Joshua60]

On 8/18/2022 at 4:05 PM, maly70 said:

hi, try 07009B3E and device id as: C89B8868 

@maly70

 

black screen, thank you anyway

[Slice]

On 8/18/2022 at 5:05 PM, maly70 said:

hi, try 07009B3E and device id as: C89B8868 

This device-id is completely wrong.

[Joshua60]

On 8/18/2022 at 4:44 PM, Cyberdevs said:

I already updated the EFI but I might have missed something, compare it to you efi and remove what's unnecessary  

@Cyberdevs

I have tried 

Framebuffer: 07009B3E. Device id: 983E0000 from your EFI.

 

Blackscreen and 0 connectors. Probably the only values that work are giving 7MB VRAM.

[Cyberdevs]

28 minutes ago, Joshua60 said:

I have tried 

Framebuffer: 07009B3E. Device id: 983E0000 from your EFI.

Blackscreen and 0 connectors. Probably the only values that work are giving 7MB VRAM.

Try with only these settings:

 

PciRoot(0x0)/Pci(0x2,0x0)

AAPL,ig-platform-id: 0300C89B

AAPL,slot-name: Built-In

device_type: Display Controller

model: Intel UHD Graphics 630

[Joshua60]

37 minutes ago, Cyberdevs said:

Try with only these settings:

 

PciRoot(0x0)/Pci(0x2,0x0)

AAPL,ig-platform-id: 0300C89B

AAPL,slot-name: Built-In

device_type: Display Controller

model: Intel UHD Graphics 630

@Cyberdevs

 

the system does not boot. It already happens if I remember right.

[Cyberdevs]

Well that's weird, nothing seems to work on your rig.

[Joshua60]

1 hour ago, Cyberdevs said:

Well that's weird, nothing seems to work on your rig.

As far as I understand you need 'framebuffer-patch-enable <01000000> ' according to the OC Guide.

But nevermind I think there is no solution for that problem.

 

Thank you so much for your support.

 

Edited August 22, 2022 by Joshua60

[Cyberdevs]

You're welcome.

As I understand there are few people that succeeded with the same board, but what I don't understand is why isn't yours working.

Take a look at these posts:

https://github.com/Twixes/Hackintosh-Intel-i7-10700K-Gigabyte-Z490-Vision-D

https://gitee.com/softxing/Hackintosh-Intel-i7-10700k-Gigabyte-Z490-Vision-G

Although they are using Gigabyte boards but they have successfully installed Big Sur and if you want to use their EFI folders you need to make some changes and update OC and kexts.

You can use OC Auxiliary Tool  to update them easily. 

 

For instance if you see the attached config under #PciRoot(0x0)/Pci(0x2,0x0) (# symbol disables the entry by the way so it won't work you need to remove the # before any entry for it to be activated) there are all sort of connector and framebuffer data.

Config.plist

[Anto65]

@Joshua60 If you want to try (2 configurations)  add the Framebuffer in PciRoot (0x0) / Pci (0x2,0x0)

 

 

Comet-Dev-DeviceProperties.zip

[Joshua60]

20 hours ago, Cyberdevs said:

You're welcome.

As I understand there are few people that succeeded with the same board, but what I don't understand is why isn't yours working.

Take a look at these posts:

https://github.com/Twixes/Hackintosh-Intel-i7-10700K-Gigabyte-Z490-Vision-D

https://gitee.com/softxing/Hackintosh-Intel-i7-10700k-Gigabyte-Z490-Vision-G

Although they are using Gigabyte boards but they have successfully installed Big Sur and if you want to use their EFI folders you need to make some changes and update OC and kexts.

You can use OC Auxiliary Tool  to update them easily. 

 

For instance if you see the attached config under #PciRoot(0x0)/Pci(0x2,0x0) (# symbol disables the entry by the way so it won't work you need to remove the # before any entry for it to be activated) there are all sort of connector and framebuffer data.

Config.plist 23.61 kB · 2 downloads

@Cyberdevs

 

I took a look at the config you attached. I already try this framebuffer 0300C89B. The system works but with 7MB VRAM.

It works correctly according to the OC guide.

 

I've looked at your first link. It use iMac20,2 system. My system is set to iMac20,1.

Edited August 23, 2022 by Joshua60

[Slice]

2 minutes ago, Joshua60 said:

@Cyberdevs

 

I took a look at the config you attached. I already try this framebuffer 0300C89B. The system works but with 7MB VRAM.

It works correctly according to the OC guide.

You will get 7mb also with framebuffer like 12345678.

[Joshua60]

8 minutes ago, Slice said:

You will get 7mb also with framebuffer like 12345678.

@Slice

 

I absolutely don't want to hurt you. You did a great job during years.

 

[Slice]

I am OK.

[Henry2010]

Smooth update. Just needed to enable TRIM again.😅

[JorgeMax]

Some things I've been analyzing here about the iGPU using a motherboard with the B360 chipset: I used an ASUS TUF B360 PLUS GAMING. In it there was only the option "Pre-Allocated DVMT". I made changes to values and none worked, I always went to a black screen with no signal on the monitor. I went to do some research and saw that the key "DVMT Total Gfx Mem" that I didn't have on my board could be missing. I dumped her bios, took a tool that "opens" the bios and navigated through the sections until I got where these keys were for the integrated video, ASUS removed this key "DVMT Total Gfx Mem". But there was a hidden key for the user to change, which was the "Aperture Size" and it was fixed at 256MB. I got it and gave up activating the iGPU on this motherboard.

A while passed and my video card was a problem, what I did I bought a motherboard from Gigabyte GA-B360M-AORUS-GAMING. In addition to the "Pre-Allocated DVMT", there were also the other two keys that on the ASUS card I did not have.

Testing, leaving "DVMT Pre-Allocated" at 64MB, "DVMT Total Gfx Mem" at "MAX" and "Aperture Size" at 256MB (I also tested the values above 256MB, the same result). There was no video signal after the first boot stage of the system, it was to change the "Aperture Size" to 128MB, then I had the video signal and arrived on desktop (table). But I couldn't get acceleration, it was always at 7MB. I tried all the framebuffers.

Somehow this "Aperture size" is what gets in the way.

[Joshua60]

3 hours ago, antuneddu said:

@Joshua60 If you want to try (2 configurations)  add the Framebuffer in PciRoot (0x0) / Pci (0x2,0x0)

 

 

Comet-Dev-DeviceProperties.zip 2.55 kB · 4 downloads

@antuneddu

 

<0300C89B> works but ...  7MB

 

thank you so much

[Henties]

In the regular release section of "gibMacOS" there are 2 download options for Monterey 12.5.1 (21G83), one dated 17.08.2022 and the other dated 24.08.2022, entered a week later. 

 

My question is:

Are these 2 entries identical, "code wise", or not.

 

Hoping somebody can shed some light on this, what seems to be a rather confusing anomaly, at least to me.

 

A screenshot has been attached to highlight the confusing entries in gibMacOS.

 

Your comments as to what has likely been happening here will be appreciated.

 

Greetings Henties 

 

Edited August 26, 2022 by Henties

[Cyberdevs]

@Henties

I'm not sure what's the difference between those two files but Apple just released a TimeZone Update on all devices couple of days ago and that might be reason for those different files. I might be wrong tho.

[Henties]

Whow @Cyberdevs your response was indeed lightning fast, thank you for that, much appreciated indeed.

 

I am all of a sudden getting "time difference" notifications" originating from the "Private Cloud Services" I set up for myself under Monterey, I have therefore, based on your "hunch", decided to also download the later version of Monterey 12.5.1 (21G83) and see what happens and also compare the 2 releases, differing only in their time stamp, with my favourite file comparison utility. 

 

Should the 2 Monterey versions indeed differ "codewise" then Apple may well be "slipstreaming" updated code, which is not really an ethical act to indulge in by any reputable software pedlar.

 

Greetings Henties 

[Cyberdevs]

@Henties

You're welcome 

I checked the App Store and the installer is from a week ago so they haven't updated the App Store yet which begs the question why there's another installer available in the catalog!

[Henties]

@Cyberdevs I just made a size comparison between the Monterey 12.5.1 (21G83) installer dated 17.08.2022 and Monterey 12.5.1 (21G83) dated 24.08.2022

the latter being 200 kilobytes larger in size with both being available as public download options through gibMacOS.

If this was intentional by Apple then one can only classify this as "slipstreaming" new code, I am now rather perturbed because this kind of practice is just not tolerable. Imagine a huge company, with hundreds of machines, have two macOS opsyses running, completely equal as far as their Version numbers are concerned, but with different code bases, who would be able support such a mess ?  

 

Greetings Henties