[pre-release] macOS Ventura

[miliuco]

@PoMpIs

This is with RestrictEvents, right? The warning is okay. 

[PoMpIs]

12 minutes ago, miliuco said:

@PoMpIs

This is with RestrictEvents, right? The warning is okay. 

 

That doesn't seem like a warning, it's just information... I like it😄

 

It's the same as this in monterey

 

 

PS: Yes of course it is RestrictedEvents, latest version:

 

https://dortania.github.io/builds/?product=RestrictEvents&viewall=true

 

Edited August 9, 2022 by PoMpIs

[Slice]

8 hours ago, Common_Sense said:

 

Yes that looks like a lot of memory, are you using Open Core or Clover? Clover does detect and correctly fill in memory information in SMBIOS automatically. I don't know about Open Core, I have not been using it much.

 

 

Clover has automatic RAM detection, SPD reading.

OpenCore assumes you will write all you want into config.plist.

[luky35]

On macOS Ventura Beta 4 and B5, the processor fan works at full power and its power does not decrease at all, so that the case is quite hot above the processor. I don't know what could be wrong.
It works the same for me on a clean install or upgrade from Monterey to Ventura.

In macOS Monterey, however, everything works normally.

Maybe this is happening to someone else?

[Extreme™]

25 minutes ago, luky35 said:

On macOS Ventura Beta 4 and B5, the processor fan works at full power and its power does not decrease at all, so that the case is quite hot above the processor. I don't know what could be wrong.
It works the same for me on a clean install or upgrade from Monterey to Ventura.

In macOS Monterey, however, everything works normally.

Maybe this is happening to someone else?

 

This is a known problem. I had it in beta 4 and now also in beta 5. When it occurs, Ventura doesn't go to slep. Until it's fixed once and for all you'll have to live with it. Thanks to @PoMpIs, you can manually fix it whenever it comes up by typing this command in the terminal:

 

sudo pmset schedule cancelall

 

[luky35]

1 minute ago, Extreme™ said:

 

This is a known problem. I had it in beta 4 and now also in beta 5. When it occurs, Ventura doesn't go to slep. Until it's fixed once and for all you'll have to live with it. Thanks to @PoMpIs, you can manually fix it whenever it comes up by typing this command in the terminal:

 

sudo pmset schedule cancelall

 

Thank you.

[Extreme™]

11 minutes ago, luky35 said:

Thank you.

Sorry, I forgot: can you confirm please that the problem occurred even after a clean installation of beta 4 or 5?

[luky35]

14 minutes ago, Extreme™ said:

Sorry, I forgot: can you confirm please that the problem occurred even after a clean installation of beta 4 or 5?

Yes

[surenmunoo]

1 hour ago, Extreme™ said:

 

This is a known problem. I had it in beta 4 and now also in beta 5. When it occurs, Ventura doesn't go to slep. Until it's fixed once and for all you'll have to live with it. Thanks to @PoMpIs, you can manually fix it whenever it comes up by typing this command in the terminal:

 

sudo pmset schedule cancelall

 

Thanks, worked for me as well.

[miliuco]

4 hours ago, eSaF said:

My contribution to the debate...

 

Memory info issue only occurs in MacPro7,1. iMac and iMacPro always show the memory ok without RestrictEvents. At least on Intel CPUs.

[Extreme™]

24 minutes ago, miliuco said:

 

Memory info issue only occurs in MacPro7,1. iMac and iMacPro always show the memory ok without RestrictEvents. At least on Intel CPUs.

SMBIOS 7.1 creates too many problems for my taste. I've always used iMac Pro 1.1 and it was ok. Unlike others, I didn't switch to MacPro 7.1 for the sole reason of not using WEG: I consider this nonsense. Instead, it seems that iMac Pro 1.1 has little future now: so some argue.

Edited August 10, 2022 by Extreme™

[miliuco]

31 minutes ago, Extreme™ said:

SMBIOS 7.1 creates too many problems for my taste. I've always used iMac Pro 1.1 and it was ok. Unlike others, I didn't switch to MacPro 7.1 for the sole reason of not using WEG: I consider this nonsense. Instead, it seems that iMac Pro 1.1 has little future now: so some argue.

MacPro7,1 SMBIOS can work fine with a lot of systems but it has more tasks to do. Not only RestrictEvents for about Memory, also (in my case) it needs CPUFriend and CPUFriendDataProvider to have CPU frequencies ok. iMac and iMacPro don't need them. 

As I have Coffe Lake R CPU (9th. gen) with iGPU, SMBIOS that works better seems to be iMac19,1 with iGPU on headless mode.

About iMacPro1,1 future, wait, maybe is longer than you expect.

[D3v1L]

ok guys...someone is little confused...

 

RestrictedEvents.kext , for MacPro7,1 smbios WITH INTEL CPU (!! pay attention, ONLY on INTEL CPU !!), ONLY HIDE the memory "problem" (the problem is only on Ventura...'couse , maybe , is an early beta?!?!?!?...) .So, sorry but, is only a placebo.

Coffee Lake...preferred iMac19,1 only for cpu power management (OK, but the benefit's stop here)...

iMac19,1 with CL ...ok, say me , from Monterey, how can i use complete DRM with this smbios? (simply, it will not)

Quicksynch with igpu on headless...ok is usefull maybe 4/5 years ago with 2xx/3xx AMD series or with older and supported nVidia... but absolutely NOT with Navi card...

switch to MacPro7,1 only for not using WEG?...i didn't use it in iMac19,1 with RX580, i didn't use it on iMacPro1,1 with RX580 and i didn't use it on MacPro7,1 with RX6600XT (and in other rig with RX6900XT)

switch to MacPro7,1 with NAVI cards, make more sense than using iMac19,1, also with Coffee Lake. 

(encoding 300% faster than iMac19,1 with quicksynch and 150% faster than iMacPro1,1...all test make on same rig with professional software, not with {censored} like videoproc etc.)

MacPro7,1 smbios need more task to do...Well, true!

but i think "more task to do", for an "hackintosher" is not really hard to do...or no?

certainly if you want everything to work right away without committing yourself, buy a real Mac ... However, sometimes I wonder why people install beta versions of operating systems if they don't even know how to use a terminal ... maybe for say "woah! i've installed the latest one! and you don't!" ...

 

imho

Edited August 10, 2022 by D3v1L

[Extreme™]

24 minutes ago, D3v1L said:

ok guys...someone is little confused...

 

RestrictedEvents.kext , for MacPro7,1 smbios WITH INTEL CPU (!! pay attention, ONLY on INTEL CPU !!), ONLY HIDE the memory "problem" (the problem is only on Ventura...'couse , maybe , is an early beta?!?!?!?...) .So, sorry but, is only a placebo.

Coffee Lake...preferred iMac19,1 only for cpu power management (OK, but the benefit's stop here)...

iMac19,1 with CL ...ok, say me , from Monterey, how can i use complete DRM with this smbios? (simply, it will not)

Quicksynch with igpu on headless...ok is usefull maybe 4/5 years ago with 2xx/3xx AMD series or with older and supported nVidia... but absolutely NOT with Navi card...

switch to MacPro7,1 only for not using WEG?...i didn't use it in iMac19,1 with RX580, i didn't use it on iMacPro1,1 with RX580 and i didn't use it on MacPro7,1 with RX6600XT (and in other rig with RX6900XT)

switch to MacPro7,1 with NAVI cards, make more sense than using iMac19,1, also with Coffee Lake. 

(encoding 300% faster than iMac19,1 with quicksynch and 150% faster than iMacPro1,1...all test make on same rig with professional software, not with {censored} like videoproc etc.)

MacPro7,1 smbios need more task to do...Well, true!

but i think "more task to do", for an "hackintosher" is not really hard to do...or no?

certainly if you want everything to work right away without committing yourself, buy a real Mac ... However, sometimes I wonder why people install beta versions of operating systems if they don't even know how to use a terminal ... maybe for say "woah! i've installed the latest one! and you don't!" ...

 

imho

 

I don't understand if all the speech you made was aimed at me. Either way, we're not nearly as ignorant as you seem to be treating us in your message, and we're not stupid enough to use a beta - macOS Ventura - as the primary operating system.
For example, despite what you write, the screen shows that RestrictEvents, at least in my hardware, doesn't work well on my Monterey 12.5 

 

P.S: If you want I can pass you one of my EFI that works also with Ventura Beta 5 where not only do I not use WEG, but not even AppleALC, Lilu, VirtualSMC, CpuTscSync.

Edited August 10, 2022 by Extreme™

[Cyberdevs]

@D3v1L

You are in the English Section, Please do not post in Italian.

[ndungu6678]

On 8/8/2022 at 8:23 PM, antuneddu said:

👍

 

Ventura Beta 5- 22A5321d-done!-no issues so far🙂. Thanks again to everyone here, moderators, donators ,the OC group and developers for all your help!. I would never have got this far without it

 

 

Build 1: iMac20,2, i5-9400F, Samsung 16GB DDR4 RAM, MSI Z390 Gaming Plus , Radeon RX 580 8GB, OC 0.8.4

Edited August 10, 2022 by ndungu6678

[Sherlocks]

Anyone who get that usb copy speed is low in ventura?

 

Strangely both front and back usb port is low speed.

There was no problem in monterey.

[miliuco]

@D3v1L

 

You >> RestrictEvents.kext, for MacPro7,1 smbios WITH INTEL CPU (!!pay attention, ONLY on INTEL CPU!!), ONLY HIDE the memory "problem" (the problem is only on Ventura...'couse , maybe , is an early beta?!?!?!?...). So, sorry but is only a placebo.

 

Me >> You know that RestrictEvents have more features. All of them are intended to block undesired processes in Hacks or in real Macs so, form this point of view, it's a placebo but do not forget that placebos have an effect on a percentage of people who take them as if they were real medicines 😂
Mac Pro 7,1 SMBIOS, in my opinion, often has the memory configuration issue, even without RestrictEvents, in the beta versions of Ventura released so far. Other users and I have tried different settings in the Memory section of config.plist but we have not managed to make disappear the info icon next to the memory in General >> Information and neither does the window that opens from that icon correctly say the number of occupied and free slots although it usually says well total and type of installed memory.
I think I remember that you have correct that info with the number of slots occupied and free, using MemoryDevices of config.plist and not RestrictEvents. But in other cases this does not happen.
In this sense, we can say that MacPro7,1 often presents this memory issue in the hackintoshes, on the other hand iMac and iMacPro recognize more directly the adjustment of the RAM memory.

 

You >> Coffee Lake... preferred iMac19,1 only for cpu power management (OK, but the benefit's stop here)...
iMac19,1 with CL ...ok, say me , from Monterey, how can i use complete DRM with this smbios? (simply, it will not)

 

Me >> The trick for me is iMac19,1 + unfairgva=6 in boot.args, DRM handling is not complete but TV app works fine. No problem with QuickSync (I guess).

 

Anyway, it's amazing to have 3 different SMBIOS to use in my hack thanks to OpenCore and Clover, one of the options is my favorite but from time to time I try the others and this way I get less bored 👍

 

Edited August 10, 2022 by miliuco

[Moviemakergr]

1 hour ago, Sherlocks said:

Anyone who get that usb copy speed is low in ventura?

 

Strangely both front and back usb port is low speed.

There was no problem in monterey.

Yes i have the same prob,extremely when copy on EFI folder.

[Ludox]

[deeveedee]

@Sherlocks and @Moviemakergr I haven't noticed a USB speed difference on the USB 3.1 ports of my HackMini8,1, but you made me curious, so I ran BlackMagic Diskspeed Test on a USB 2.0 thumb drive inserted into one of my front USB 3.1 ports.  My testing shows that there is a very slight decrease in both read and write performance in Ventura when comparing read/write for same USB port and same USB thumb drive.  If you want to test your own USB port(s), run BlackMagic and change the target drive by selecting File > Select Target Drive.

 

BlackMagic Diskspeed: Monterey 12.5

Spoiler

 

BlackMagic Diskspeed: Ventura Beta 5

Spoiler

 

Edited August 10, 2022 by deeveedee

[PoMpIs]

6 hours ago, Moviemakergr said:

Yes i have the same prob,extremely when copy on EFI folder.

 

My flash drives are bad and old, but not that bad...

You are right, copying certain things is slow, very very slow 😆

 

 

Try to copy the istat menus application in a USB 😁

 

 

 

 

 

 

 

[PoMpIs]

Today I entertained myself for a while with my son's computer....

I didn't expect it to install ventura beta 5 without the slightest problem, but it has... I'm going to have to put an RX6000 on it, because with the gtx1660ti it has I don't have graphics acceleration, but it still runs smoothly on basic tasks. .. it has been very very entertaining to put beta 5 on this computer 

 

 

and perfectly shows the memory

 

 

And it also has the same problem of copying files to a usb pendrive, It stays like this for a long time:

 

 

 

Edited August 11, 2022 by PoMpIs

[Sherlocks]

10 hours ago, Moviemakergr said:

Yes i have the same prob,extremely when copy on EFI folder.

 

6 hours ago, deeveedee said:

@Sherlocks and @Moviemakergr I haven't noticed a USB speed difference on the USB 3.1 ports of my HackMini8,1, but you made me curious, so I ran BlackMagic Diskspeed Test on a USB 2.0 thumb drive inserted into one of my front USB 3.1 ports.  My testing shows that there is a very slight decrease in both read and write performance in Ventura when comparing read/write for same USB port and same USB thumb drive.  If you want to test your own USB port(s), run BlackMagic and change the target drive by selecting File > Select Target Drive.

 

BlackMagic Diskspeed: Monterey 12.5

  Reveal hidden contents

 

BlackMagic Diskspeed: Ventura Beta 5

  Reveal hidden contents

 

 

3 hours ago, PoMpIs said:

 

My flash drives are bad and old, but not that bad...

You are right, copying certain things is slow, very very slow 😆

 

 

Try to copy the istat menus application in a USB 😁

 

 

 

 

 

 

 

 

thanks for check.

i determined that my alderlake desktop return to monterey for maintainance that backup efi and etc for other system..

 

[Naki]

Guys, when testing USB flash drives speeds - regardless of which OS you do the testing on - of course USB 2.0 is useless, as it is very old now.

Also, please avoid using (i.e. purchasing) and testing "fake", cheap USB 3.1 (was 3.0) drives, where you will often find they have a fairly good read speed, but horrible (too low) write speed.

(Often, such inferior USB drives do not even list any write speed in their official specs!)

 

Shoot for something that has at least 200 MB/sec read, and 100 MB/sec write speed.  

Edited August 11, 2022 by Naki
Grammar fix