[pre-release] macOS Ventura

[maly70]

is there Mac OS beta profile for Ventura or I use Monterey one?

 

I removed beta program then I reinstall it again,,, now I am updating Ventura to b2

[HyperX7]

 

There was one problem during the installation. The problem is IGPU. My IGPU is HD 520 on Skylake CPU so that installation take longer than normal. During the installation appear the IGPU error and it takes 15-20 minutes than pass the error. After that evrything goes normal and finished the installation Ventura Beta 2 on Skylake CPU.

[NicolasBell]

44 minutes ago, meaganmargaret said:

So, I started the update, got distracted, came back 15-20 minutes later, wasn't paying attention like I should have, but when I came back, all done!  Smoothest update ever......

 

Added:  a lot of bugs are fixed! 

I get a panic the moment that I try to switch on Wi-Fi and connect to a network and no bluetooth .. 

Edited June 22, 2022 by NicolasBell

[Laqk]

Python is fixed in beta 2.

 

ProperTree works now.

 

[PoMpIs]

8 minutes ago, eSaF said:

Hi all - Apart from Apple TV is anyone able to screen films in Netflix or Amazon in Safari? The last two plays ok in Chrome but no go in the Apple browser on my machine with Ventura.

 

Everything works for me on Safari, Netflix, Disney+, HBO

 

 

[Stefanalmare]

No more mounting Preboot on Beta 2 to replace os.dmg. I have the feeling that the only solution to have Ventura on Ivy and lower is avx2 emulation. Let's see! If is possible............

[v-volodi]

7 hours ago, miliuco said:

@v-volodi

I doubt it fix your problem but do you have igfxonln=1 in boot-args? If not, try it.

 

Thanks, i have  igfxonln=1 in boot args, but it also dimmed screen

[surenmunoo]

Update to beta 2 went through like a charm. At least Auto Login now works and the Stage Manager is awesome.

 

[PMheart]

Hello,

 

https://github.com/acidanthera/WhateverGreen/pull/101 is now merged into WhateverGreen master branch. For Skylake graphics users this means that you can now switch back to the master branch, or wait for our 2022.07 release in which the spoofing support will be included.

 

PMheart

[Joshua60]

Clean installation, no issues, (macOS Ventura beta 13.0 22A5286j rig #2) 

Edited June 23, 2022 by Joshua60

[Cyberdevs]

7 hours ago, maly70 said:

Dear Cyberdevs, I installed Ventura into z490 with igpu 10400 and working great, still waiting for Nvidia patch  

Thank you 

Still not getting b2 update in system settings, keep saying 'Your up to date'
any idea!

Double check the SecureBootModel under the Misc->Security it must be set to "Default"

[Sherlocks]

51 minutes ago, PMheart said:

Hello,

 

https://github.com/acidanthera/WhateverGreen/pull/101 is now merged into WhateverGreen master branch. For Skylake graphics users this means that you can now switch back to the master branch, or wait for our 2022.07 release in which the spoofing support will be included.

 

PMheart

 

hi. thank you for work.

in monterey and blow, i used 0x1916 device-id and ig-platform-id for skylake.

can i maintain 0x1916 device-id and ig-platform-id ?

 

for example, el capitan or sierra. just in case i know this is old macos.

There is kabylake framebuffer kexts in Sierra. 

Edited June 23, 2022 by Sherlocks

[aben]

15 hours ago, Laqk said:

For those with the skylake HD 530 laptop black screen problem, you may want to try this.

 

Some skylake laptops with LVDS screen have a problem that, under macos, any screen brightness setting below max brightness will result in a black screen, until the first sleep/wake cycle. The problem is that after clearing the nvram, macos will initialize the "backlight-level" variable to a value that is below peek brightness, and therefore the screen will remain black. To complicate the problem even more, at this stage (installation media or recovery partition), the brightness keys don't seem to work, so there is no way to increase the brightness to its peek value and turn on the backlight.

 

To resolve this issue, you must add the variable "backlight-level" to the NVRAM section of your config.plist and initialize it with a value of peek brightness.

Nice find! Although my Skylake laptop does not suffer from this issue, I do have to point out that "backlight-level" variable will exist only when there is a presence of PNLF device, which means: without declaring this device in ACPI, macOS has no backlight variable to initialize "natively" and thus always boots with backlight to its native maximum peak brightness throughout. In cases where screen brightness in configurable at BIOS level, macOS always treats that pre-set value as its highest native. This is the behavior I have observed on laptop displays I have tested when under macOS while omitting PNLF including my Skylake Dell with LVDS. Feel free to test this on your laptop as well.

The approach you detailed above is indeed a viable workaround to the backlight issue however not all panels have the same peak brightness value and therefore the value provided above is not guaranteed to match other display's peak value; I believe the better approach here would be to find the correct peak value for that display from NVRAM (terminal command nvram -xp prints xml format of all NVRAM variables) and have that value set in config.plist when attempting to install the problematic macOS version, but of course this approach would require PNLF presence + access to macOS install on same device with brightness maxed out.

@PC IT @v-volodi Please test these methods as well for backlight issue.

Edited June 23, 2022 by aben

[PMheart]

1 hour ago, Sherlocks said:

 

hi. thank you for work.

in monterey and blow, i used 0x1916 device-id and ig-platform-id for skylake.

can i maintain 0x1916 device-id and ig-platform-id ?

 

for example, el capitan or sierra. just in case i know this is old macos.

There is kabylake framebuffer kexts in Sierra. 

Hi Sherlocks! Long time no see!

 

From the previous tests, it turned out that you can always spoof SKL as KBL. You can always use the boot-arg `-igfxsklaskbl` and KBL device-id and ig-platform-id  since Sierra instead.

 

For El Capitan, unfortunately you would have to use Skylake device-id and ig-platform-id, as there is no KBL support there. This means, that you may have to use another config.

[Guest ricoc90]

Update went fine. I do experience lots of issues in mainly the settings panel though. Such as the view not updating when interacting with its contents.

[Henties]

Ventura Beta 2 (22A5286j) installed without issues on my GA-Z490 Vision G builds, the onboard Intel i225-V is also working well.

I changed the name of my macOS beta download supplier to "Beetapple" considering that the last three macOS iterations are still presently being "beetad" 

 

Greetings Henties

[NicolasBell]

Manage to get wifi working .. But Bluetooth is a pain anybody else suffering this problem .. 

[aben]

36 minutes ago, NicolasBell said:

Manage to get wifi working .. But Bluetooth is a pain anybody else suffering this problem .. 

Hi- Could you please test replacing both kexts attached below: BlueToolFixup + Lilu

SKP_ADDR_13.zip

Edited June 23, 2022 by aben

[NicolasBell]

18 minutes ago, aben said:

Hi- Could you please test replacing both kexts attached below: BlueToolFixup + Lilu

SKP_ADDR_13.zip 198.26 kB · 0 downloads

I used this and now i have a fully working laptop .. 

 

https://github.com/dortania/build-repo/releases/tag/BrcmPatchRAM-8c04849

 

BlueToolFixup.kext BrcmFirmwareData.kext BrcmPatchRAM3.kext

Edited June 23, 2022 by NicolasBell

[aben]

3 minutes ago, NicolasBell said:

I used this and now i have a fully working laptop .. 

 

https://github.com/dortania/build-repo/releases/tag/BrcmPatchRAM-8c04849

 

BlueToolFixup.kext BrcmFirmwareData.kext BrcmPatchRAM3.kext

I see. Well, the version of the kexts I provided above are specifically to address BT issues on macOS 13. They're not part of the master branch yet except Lilu. Please test and report if those replacements solves the BT issue. Thanks!

[miliuco]

9 hours ago, eSaF said:

Thanks, do you have any special boot-arg to enable those in Safari? or how did you enable them in Safari?

Dear friend, IMO the only way that works for me to having DRM in Safari is setting MacPro7,1 or iMacPro1,1 SMBIOS model (iGPU disabled in BIOS). If SMBIOS is iMac19,x or iMac20,x (iGPU enabled in BIOS) I never have DRM in Safari. 

[SavageAUS]

Updated my laptop to beta2 no issues. Now that I have a new monitor I’ll try on my AMD desktop this weekend. 

[Cyberdevs]

On AlderLake rig is't also fine.

[miliuco]

38 minutes ago, eSaF said:

Ah yes, I completely forgot DRM in Safari depends on SMBIOS. What puzzled me is, with my current setup iMac Model 2020 with both independent and dedicated GPU, Apple TV plays all my stored iCloud movies plays so I assumed Netflix and Amazon would also without having to use Chrome.

Remember your own post. We can play TV app with iMac adding unfairgva=1 in boot-args or running those Terminal commands to enable AMD hardware acceleration. But, at least for me, DRM in Safari is a no go with iMac models.

[Henties]

1 hour ago, miliuco said:

Dear friend, IMO the only way that works for me to having DRM in Safari is setting MacPro7,1 or iMacPro1,1 SMBIOS model (iGPU disabled in BIOS). If SMBIOS is iMac19,x or iMac20,x (iGPU enabled in BIOS) I never have DRM in Safari. 

I don't believe that DRM with Ventura Safari, and other macOS incarnations, depends only on the SMBIOS version chosen.

I have no problems viewing DRM content with SMBIOS 20.2 at all when pulling audio off the mobo's SPIDF (digital) onboard header and using that digital signal to drive "compatible" speaker systems with either the digital coaxial and or the digital optical signal available from that onboard header. You just need the proper adapter that makes these signals available somewhere on the backplate.

Just my two cents worth.

 

Greetings Henties