Jump to content

[pre-release] macOS Monterey

fantomas

By fantomas,
in New Releases and Updates

 Share
1699 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted
2 hours ago, SavageAUS said:


Did you have to use any trickery?
My laptop with smbios MacBookPro16,1 showed the update, downloaded the update but no matter how many times I tried it would not pass the first reboot, just kept going around and around in a reboot loop, had to use a usb with OC 0.7.4 to get it installed. Now that it’s installed clover boots it just fine. I did not change any settings but I did try adding RestictEvents kext with no luck.

Same deal with my AMD desktop, had to use OC 0.7.4 to finish the update but clover boots it just fine.

With my AMD machine I lost Ethernet again. Wish Apple would make there minds up. Luckily I do have a pci Ethernet card handy if the decide to stop us from using smalltree kext.


Sent from my iPhone using Tapatalk

Check ExtendedFirmwareFeatures. If there is no bit 0x800000000 then it will not pass first reboot.

  • Like 2
  • Thanks 1
Partime
Partime
Posted
Posted
1 hour ago, miliuco said:

If you have 0.7.4, in theory SecureBootModel=Default and SMBIOS set as you prefer must work.

What's your SMBIOS?

Try SecureBootModel=Disabled.

 

Now that everything is updated, its hard to go back an check what's keeping it form updating.

But I did have 0.7.4 and SecureBootModel set to default.  SMBIOS is imacPro1,1

 

I'll try the SBM=Disable next time. 

 

thanks

 

SavageAUS
SavageAUS
Posted
Posted (edited)
1 hour ago, Slice said:
Check ExtendedFirmwareFeatures. If there is no bit 0x800000000 then it will not pass first reboot.


Ah ok. I will check and report next update.

 

Is it ok to use the default value 0x8FE001403 ?

Or should it be 0x800000000?

 

Same for ExtendedFirmwareFeaturesMask is the default value ok to use?


Sent from my iPhone using Tapatalk

Edited by SavageAUS
Dmitriy85
Dmitriy85
Posted
Posted (edited)
30 minutes ago, SavageAUS said:


Ah ok. I will check and report next update.

 

Is it ok to use the default value 0x8FE001403 ?

Or should it be 0x800000000?

 

Same for ExtendedFirmwareFeaturesMask is the default value ok to use?


Sent from my iPhone using Tapatalk 

the values should be under your mac model
for example

 iMacPro1,1

         
FirmwareFeatures: 0xFD8FF53E
FirmwareFeaturesMask: 0xFF9FFF3F
ExtendedFirmwareFeatures: 0x00000008FD8FF53E
ExtendedFirmwareFeaturesMask: 0x00000008FF9FFF3F

 

Edited by Dmitriy85
  • Thanks 1
SavageAUS
SavageAUS
Posted
Posted
I have the latest o.c 75, using imac16,1, secure boot model disabled and these strings blank. Updated no problem.

Yeah with OpenCore, but I’m trying to use clover so perhaps those values are needed. I just need to know which values to use for MacBookPro16,1 and iMacPro1,1.


Sent from my iPhone using Tapatalk
obus
obus
Posted
Posted (edited)

Updated from beta 8 to beta 9 without issues. Updated with full security enabled (file Vault, Vault and ApplesSecureBoot) Everything works like a charm.

Dual booting Windows 10 on the same disk works too after updating. Updated without changing SMBIOS. 😃

 

 

1455951794_Screenshot2021-10-07at15_16_35.thumb.png.3417fdbef3ebcfa9a5f71f214ee1b2eb.png

Edited by obus
  • Like 4
miliuco
miliuco
Posted
Posted
3 hours ago, antuneddu said:

Strange but true apparently it doesn't seem to work with everyone 🤔

I see. Hackintosh world is not simple. As per @vit9696, Default must be valid for every one. And Default picks SMBIOS model so both match. I don’t know why some people has problems with Default. 

Avery B
Avery B
Posted
Posted

After realizing I was on public beta seed (oops), was able to change that and update to B9 like normal.
SMBIOS: MacBookPro15,1
SecureBootModel: Default (J680)
Can also still boot Catalina and older OSes with SBM set to default, which is nice for working on VoodooRMI.
 

Spoiler

image.thumb.png.97538e9bf943481b3c4d3370b54d2a5f.png

 

  • Like 2
Loloflat6
Loloflat6
Posted
Posted (edited)

1416374654_Screenshot2021-10-07at20_07_18.thumb.png.5dc448a9ed16f1581effa1534fd79265.png

 

Updated Beta 8  --------->   Beta 9

 

On my test build Asus X299 Prime A II  CPU i7-7800x - GPU Amd Radeon RX460

 

OC 0.7.4 release with iMacPro 1,1 SMBIOS ( without changing SMBIOS and without RestrictEvents.kext)

 

 

 

 

 

Edited by Loloflat6
  • Like 4
Partime
Partime
Posted
Posted
16 hours ago, miliuco said:

@Partime

I prefer Hackintool method. See here

https://www.insanelymac.com/forum/topic/345140-guide-usb-port-mapping-on-z390-aorus-elite/

 

 

I like Hackintool too.....

 

Anyone, one thing I wanted to check .... I believe we no longer use the USBInjectAll.kext, but do I just remove my existing USBMAP.KEXT before using Hackintool??

greythorne
greythorne
Posted
Posted
On 10/7/2021 at 6:35 PM, miliuco said:

If you have 0.7.4, in theory SecureBootModel=Default and SMBIOS set as you prefer must work.

What's your SMBIOS?

Try SecureBootModel=Disabled.

My SMBIOS is Macmini8,1 & SBM=Disabled.

 

The previous update to beta 7, I changed the SMBIOS to iMac17,1 as suggested here.

Riley Freeman
Riley Freeman
Posted
Posted

Updated the Z68 from b6 to b9. No issues now that I had updated OC to 0.7.4 (previously b7 failed to install).

 

As a test I installed chris1111's Kepler driver patch and that worked fine.

 

However I'm not going to do that with every update so I wiped Monterey and went all the way back to Mavericks, which is the oldest system I can run as a MP6,1.

 

It'll be nice to have a legacy system again as updating the GPU in my X79 means I can't boot my old Snow Leopard install on that.

  • Like 2
Anto65
Anto65
Posted
Posted
39 minutes ago, eSaF said:

The one caveat in rectifying Bluetooth PAN not showing up within Network when a clean install of Monterey is performed and to overcome this by way of upgrading BS, is the Disk remains named as Big Sur at the boot menu but I suppose that is a typical behaviour of a Beta release. :wallbash:

I did not understand if you have solved with the bluet. pan (I think so) but as for the disk name, just Install intel Power Gadget or rename it manually by disabling SIP metod

  • Like 3
miliuco
miliuco
Posted
Posted
1 hour ago, eSaF said:

The one caveat in rectifying Bluetooth PAN not showing up within Network when a clean install of Monterey is performed and to overcome this by way of upgrading BS, is the Disk remains named as Big Sur at the boot menu but I suppose that is a typical behaviour of a Beta release. :wallbash:

Easiest method is the first proposed by @antuneddu  

Rename the disk to your like in Finder and Disk Utility >> install or reinstall Intel Power Gadget >> reboot. 

SavageAUS
SavageAUS
Posted
Posted
Hello.
Since it became 5140.1, the item of SMBIOS has increased, so I set it.
Because they searched the values for us,I think the values that OpenCore put together as Autogen.c are better.
I'm sorry for the automatic translation of Japanese pages, but the setting method is as follows.
https://mifmif-mydns-jp.translate.goog/alpha/?p=2117&_x_tr_sl=ja&_x_tr_tl=en&_x_tr_hl=ja&_x_tr_pto=nui
Thank you.
 

So what your saying is to use the new smbios features in clover 5140 & 5140.1, the extendedfirmwarefeatures and it corresponding mask is to use the ones generated from OpenCore based on specific smbios?

I will do a test boot with the above config later from USB.


Sent from my iPhone using Tapatalk
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...