Jump to content
1699 posts in this topic

Recommended Posts

36 minutes ago, Tecnicaso Rico said:

It’s always recommended to use a SMBIOS as close as possible to your hardware specs. When using different board-id’s, these board id’s must be part of the SMBIOS being used. As mention before as an example,  iMac 17,1 has three different board-id’s so when using iMac 17,1 SMBIOS I should use one of those three board-id’s and not a board-id from a different SMBIOS.
People sometimes use a SMBIOS that doesn’t matches their hardware because they have different priorities (Like having full VDA Decoder support) but they get away from Power Management problems with the help of CPUFreind. There is also an interesting scenario where two different board-id’s are being used at once, and it’s with the Wonderfull magic perform by the WhateverGreen kext. This kext can spoof a different board-id only to the video section for full VDA Decoding purposes without changing the main board-id being used by macOS.
So finally when switching between different SMBIOS’s don’t mix board-id’s, just get away of Power Management problems with the help of CPUFreind.

If for example iMac17,1 can have three different board-id then it can have four them.

  • Haha 1
37 minutes ago, Tecnicaso Rico said:

It’s always recommended to use a SMBIOS as close as possible to your hardware specs. When using different board-id’s, these board id’s must be part of the SMBIOS being used. As mention before as an example,  iMac 17,1 has three different board-id’s so when using iMac 17,1 SMBIOS I should use one of those three board-id’s and not a board-id from a different SMBIOS.
People sometimes use a SMBIOS that doesn’t matches their hardware because they have different priorities (Like having full VDA Decoder support) but they get away from Power Management problems with the help of CPUFreind. There is also an interesting scenario where two different board-id’s are being used at once, and it’s with the Wonderfull magic perform by the WhateverGreen kext. This kext can spoof a different board-id only to the video section for full VDA Decoding purposes without changing the main board-id being used by macOS.
So finally when switching between different SMBIOS’s don’t mix board-id’s, just get away of Power Management problems with the help of CPUFreind.

 

I know that. I use an i7 3630QM while Board-ID C3EC7CD22292981F is for a 3615QM… can't get any closer than that.

 

My point was to use this ID for SMBIOS MBP11,4 as well. But since this ID isn't allowed in/supported by macOS Monterey this leads to the crossed-out circle. I have a working SSDT-PM, but when switching to another SMBIOS which is based on newer CPU family it's no longer as efficient since this SMBIOS is for Haswell. As far as I know, CPUFriend can only be used for CPUs which support XCPM which IvyBridge doesn't in current macOS. I patched it in once for testing and it didn't perform well, so that's that.

14 hours ago, mnfesq said:

 

I take back what I said about OC's configurability.  I have not begun to memorize all of the options available in the sample-custom.plist and there certainly are many.  That said, the OC Configurator developers have Board Product filled out automatically when selecting an SMBIOS.  

 

EDIT: Don't forget to tick the check boxes "Add this section in config.plist" before saving. I forgot to do that first and I was wondering why all the sections were missing from the confi.g :D

Edited by 5T33Z0

I think that soon they are probably gonna fully address the compatibility hw issues with the OC legacy patcher. iMac 15,1 was added as well. https://dortania.github.io/OpenCore-Legacy-Patcher/MONTEREY-DROP.html#newly-dropped-hardware 

3 hours ago, 5T33Z0 said:

 

I know that. I use an i7 3630QM while Board-ID C3EC7CD22292981F is for a 3615QM… can't get any closer than that.

 

My point was to use this ID for SMBIOS MBP11,4 as well. But since this ID isn't allowed in/supported by macOS Monterey this leads to the crossed-out circle. I have a working SSDT-PM, but when switching to another SMBIOS which is based on newer CPU family it's no longer as efficient since this SMBIOS is for Haswell. As far as I know, CPUFriend can only be used for CPUs which support XCPM which IvyBridge doesn't in current macOS. I patched it in once for testing and it didn't perform well, so that's that.

 

I thought this was the exact purpose for CPUFriend.kext/CPUFriendDataProvider.kext.  You can use a different board for power management than the one that is designated for your SMBIOS.  I use it to get many more P-States for speed-stepping.

Edited by mnfesq
10 minutes ago, mnfesq said:

 

I thought this was the exact purpose for CPUFriend.kext/CPUFriendDataProvider.kext.  You can use a different board for power management than the one that is designated for your SMBIOS.  I use it to get many more P-States for speed-stepping.

 

Yes, you can do that – if it supports XCPM. Otherwise you have to use ssdtPRGen.

On 9/8/2021 at 10:45 AM, ombra88 said:

When I tried If I am not mistaken the smbios needed to run both r9 290x and iGpu with Haswell is not supported by monterey

Opencore works on my i7 3770 as a Mac Pro 6.1 (as recommended by the dortania guide). I’m using Clover running the beta 6 Monterey public preview. I’m using an external graphic card so I can’t comment further.

Edited by sonicthehedgehog2
Auto correct

Anyone having sleep issues with Monterey?

 

pmset -g log|grep -e " Sleep  " -e " Wake  "
2021-09-09 08:08:26 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 08:09:29 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:10:33 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 08:11:35 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 20 secs   
2021-09-09 08:12:40 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 08:13:43 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:14:47 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 08:15:50 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:16:54 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 08:17:56 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:19:00 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 08:20:03 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:21:07 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 08:22:09 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:23:13 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 08:24:16 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:25:20 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 08:26:22 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:27:26 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 08:28:29 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:29:33 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 08:30:35 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:31:39 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 08:32:42 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:33:46 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 08:34:48 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:35:52 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 08:36:54 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 20 secs   
2021-09-09 08:37:59 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 08:39:01 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 20 secs   
2021-09-09 08:40:06 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 08:41:08 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 25 secs   
2021-09-09 08:42:18 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 08:43:20 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:44:24 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:45:28 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:46:32 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 08:47:34 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:48:38 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 08:49:41 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 08:50:45 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 08:51:48 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 14 secs   
2021-09-09 08:52:47 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 08:53:50 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 1036 secs 
2021-09-09 09:11:51 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 09:12:55 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 09:13:59 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 09:15:01 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 09:16:05 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 09:17:08 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 928 secs  
2021-09-09 09:33:21 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 20 secs   
2021-09-09 09:34:26 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 09:35:30 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 09:36:32 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 997 secs  
2021-09-09 09:53:54 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   
2021-09-09 09:54:57 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 20 secs   
2021-09-09 09:56:02 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 17 secs   
2021-09-09 09:57:04 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 19 secs   
2021-09-09 09:58:08 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=active Using AC (Charge:0%) 18 secs   

 

Sleep was working perfectly on macOS Big Sur, but since installing Monterey it doesn't. I haven't changed any sleep related settings, it was working with these (and yes, power nap was working great):

PS I have 3200Mhz RAM but I have under clocked it @ 2666Mhz.

 

Screen Shot 2021-09-12 at 7.06.11 PM.png

13 hours ago, eSaF said:


@WizeMan - Hi Bro look in System Preferences/Sharing and deselect all the tick boxes there because that is where the readout '(sleep prevented by coreaudiod, sharingd, bluetoothd)' is pointing then test sleep again. I had this exact problem with Sleep in Monterey and that solved it, this tip is also mentioned on Apple Forum. Good luck.

 

Thanks my main man, it seems like everything is already unchecked.

Screen Shot 2021-09-13 at 10.20.47 AM.png

 

I am afraid Handoff could be causing this:

1856130089_ScreenShot2021-09-13at10_26_06AM.thumb.png.5779e4c9de353755ad60a72cd54cd424.png

 

 

I disabled Handoff  but the problem persists.

 

pmset -g log|grep -e " Sleep  " -e " Wake  " -e  " DarkWake "
2021-09-13 10:29:41 +0300 Sleep               	Entering Sleep state due to 'Software Sleep pid=192':TCPKeepAlive=active Using AC (Charge:0%) 26 secs   
2021-09-13 10:30:07 +0300 DarkWake            	DarkWake from Normal Sleep [CDNP] : due to PEG1 PEGP PEG2 PEGP PXSX RP10 PXSX RP11 PXSX RP12 PXSX RP13 PXSX PXSX RP02 PXSX RP03 PXSX RP04 PXSX RP05 PXSX PXSX PXSX RP18 P/Network Using AC (Charge:0%) 36 secs   

 

Edited by WizeMan
1 minute ago, eSaF said:

Hi Bro another method to try, in System Preferences/Energy Saver disable 'Wake for network access' if enabled.

 

Was about to write that. That's what I disabled and it worked! Thanks mate, I have no idea how it used to worked earlier. Maybe upgrading to Monterey enabled this setting automatically!

3 minutes ago, eSaF said:

@WizeMan I know I don't have to tell you this but just incase you overlooked it also check the 'Power' tab in 'Hackintool' to make sure all is stable (see attached).

  Hide contents

53947673_Screenshot2021-09-13at08_50_03.thumb.png.af9bc6a60d3c9746572718466ffbdd47.png558420579_Screenshot2021-09-13at08_51_18.thumb.png.77e83dcdf99d592507c3cd5494892ff1.png

 

 

I already did this "fix" from Hackintool after upgrading because I know such major updates reset these settings to default, it seems like I just missed "wake for network access" :) Thank you @eSaF !

On 9/13/2021 at 10:47 AM, eSaF said:

Hi Bro another method to try, in System Preferences/Energy Saver disable 'Wake for network access' if enabled.

I have it enabled.

2021-09-15 08:29:53 +0300 Sleep               	Entering DarkWake state due to 'Software Sleep pid=172': Using AC (Charge:0%) 3 secs    
2021-09-15 08:29:56 +0300 Wake                	DarkWake to FullWake from Invalid [CDNVA] : due to HID Activity Using AC (Charge:0%) 7 secs    
2021-09-15 08:30:03 +0300 Sleep               	Entering DarkWake state due to 'Software Sleep pid=172': Using AC (Charge:0%)           
2021-09-15 08:30:18 +0300 Sleep               	Entering Sleep state due to 'Software Sleep pid=172': Using AC (Charge:0%) 7205 secs 
2021-09-15 10:30:23 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 7206 secs 
2021-09-15 12:31:16 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 7205 secs 
2021-09-15 14:31:21 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 7206 secs 
2021-09-15 16:32:13 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 7205 secs 
2021-09-15 18:33:04 +0300 Sleep               	Entering Sleep state due to 'Maintenance Sleep': Using AC (Charge:0%) 5267 secs 
2021-09-15 20:00:51 +0300 Wake                	Wake from Normal Sleep [CDNVA] : due to XDCI/UserActivity Assertion Using AC (Charge:0%) 5678 secs 
2021-09-15 21:35:29 +0300 Sleep               	Entering Sleep state due to 'Idle Sleep': Using AC (Charge:0%) 268 secs  
2021-09-15 21:39:57 +0300 Wake                	Wake from Normal Sleep [CDNVA] : due to XDCI/UserActivity Assertion Using AC (Charge:0%)     

 

6 hours ago, eSaF said:

And Sleep is stable without intermittent Wakes in between? If I have 'Wake for Network access' enabled the machine wakes periodically specially during the night and then sleeps again which can be annoying I think is a deliberate action by Apple (not absolutely certain) but I have it disabled and machine sleeps until I wake it with mouse click or keyboard.

May be you means PowerNap?

Screenshot 2021-09-16 at 05.35.11.png

2 hours ago, eSaF said:

Thanks - will try your suggestion. Another query, is 'Put hard drives to sleep when possible' option for mechanical drives (spinning disk type) if in the system hence that option is not available in Energy Saver? That is my thinking but I maybe wrong.

438160320_ScreenShot2021-09-16at5_30_20PM.thumb.png.3ac5992c4adeef2060db4656d707f1a2.png

 

I don't have any mechanical drives but that option is shown. What you see here, I think, is a combination of your SMBIOS, your motherboard energy settings, and maybe whatever ACPI patches you may have done.

Guys, end of Sept 2021 is nearing, which means release for all to use and not just testers is imminent.

Any wild/educated guesstimates on macOS 12.0 Monterey RTM/Final release possible release dates as of now, please? :) 

Edited by Naki
grammar/clarity

@Naki There will be quite a few more betas before final release, that is my opinion because Monterey is not nearly as stable in my particular environment as Big Sur is currently proving to be. 

 

Regards Henties

  • Like 1
  • Confused 1
@Naki There will be quite a few more betas before final release, that is my opinion because Monterey is not nearly as stable in my particular environment as Big Sur is currently proving to be. 
 
Regards Henties

I’m of a different opinion, I think Monterey has been super stable on both my Intel laptop and amd desktop and we should expect a release announcement soonish.


Sent from my iPhone using Tapatalk
  • Like 3
On 9/21/2021 at 6:37 AM, eSaF said:

:thumbsup_anim: Same here for me as well, boots faster than BS, no glitches or freezing, super impressive so much so that I use it as my daily driver but still have BS incase of an emergency.

Another fact to add, I am constantly hitting it with nightly OC releases with no adverse effects to the performance, at the moment running with OC 0.7.4 (03162e0) release.

Same here for me also. @Naki @Henties @SavageAUS

  • Like 3

@All. I am aware that Monterey is acceptable and preferable to a number of users here, however my main hacks, with the Intel i225-V onboard network implementation just do not cut it in my particular environment, whereas with Big Sur I experience no problems whatsoever with the i225-V.

I can of cause disable the i225-V NIC in bios and run Monterey on WiFi, but who wants to do that ? The available local 5G WiFi bandwidth will then invariably have to be shared between all my portable devices, limiting the overall data throughput of my hacks to much less than 1 GB, which is constantly available on a per port connection basis on a properly switched CAT-6 ethernet backbone. WiFi is therefore not considered an option on a permanent basis..

All my hacks run with 2 network interfaces the second being a gigabit AX88179 USB-3 lan controller which works flawlessly under Big Sur but is not configurable under Monterey at all. That USB lan controller is used as an ethernet backbone for an extensive DANTE based audio distribution network, without which I am not prepared to work.

I am also using Audio Highjack as well as Airfoil 2, both by Amoeba, and not yet working under Monterey.

In the end I may have to free up and sacrifice a PCIe slot - 4 lanes - for a type Aquantia AQ107 add on card, and my Monterey networking woes should be partially over, but it is still early days, in the meantime I will continue plodding along happily with Big Sur, on all my hacks.

An update for Monterey seems imminent, Xcode 13 and Safari 15 is already being seeded by Apple for Big Sur, an upgrade to the latest macOS currently under development, in this case Monterey, can be expected to follow shortly on their heels - my guess is tonight CAT.

 

Greetings Henties

 

Edit: Safari 15.00 is great, I love it.

Edited by Henties
On 9/21/2021 at 9:02 AM, Slice said:

Agree. Monterey is fast and stable, I installed it over BigSur and have no BigSur now.

Exactly the same with me on a AMD build, Everything bar the SmallTree.kext is perfect and we are working on trying to get AppleGB working properly over at AMDOSX as a replacement for the smalltree kext. 
Big Sur left my system from Monterey Beta 3 and I couldn’t be happier with it. :)

  • Like 2

Hi guys,

Quick question, in my Mac mini 2018 with mcOS Monterey 12 Beta (21A5506j) I was able to enable dark mode in google and in Microsoft Office, but in my hack at home that option don't appear to enable.

That is a limitation of our hacks, or I have something wrong in my hack?

Thanks 

On 9/21/2021 at 7:04 PM, MorenoAv said:

Hi guys,

Quick question, in my Mac mini 2018 with mcOS Monterey 12 Beta (21A5506j) I was able to enable dark mode in google and in Microsoft Office, but in my hack at home that option don't appear to enable.

That is a limitation of our hacks, or I have something wrong in my hack?

Thanks 

I have no GoogleChrome nor Microsoft Office and can't check but I see not reason for this issue.

Yandex.browser is like a Google and have this option

Screenshot 2021-09-21 at 19.11.30.png

  • Like 2
Guest
This topic is now closed to further replies.
×
×
  • Create New...