[pre-release] macOS Ventura

[Guest 5T33Z0]

I wouldn't clean install every beta update. It's a waste of time and disk longevity, imo. Do it once the GM version drops. But before that I don't really see a point in it. I think incremental updates are suffiecent for the beta phase. Especially since the system section and the user section are pretty much isolated from each other now, so the whole update process is pretty clean nowadays. I can only recall one incremental update ever causing issues. It was a security Update for Catalina and affected HD4000 drivers for Ivy Bridge. it was an issue with the code itself which would still be there even when performing a clean install.

Edited June 24, 2022 by 5T33Z0

[Cyberdevs]

2 minutes ago, Matgen84 said:

@Cyberdevs

I don't have another macOS installed. Before clean install, I erase my HDD from macOS installer to APFS format.

What about the EFI partition is there an oc version on your APFS formatted disk?

[Anto65]

8 minutes ago, Matgen84 said:

@Cyberdevs

I don't have another macOS installed. Before clean install, I erase my HDD from macOS installer to APFS format.

I tried to install without any other osx present ... it doesn't work 😞

 

https://www.insanelymac.com/forum/topic/351969-pre-release-macos-ventura/?do=findComment&comment=2786993

 

And anyway, it's all lowercase letters

 

 

 

Edited June 24, 2022 by antuneddu

[PoMpIs]

@eSaF
 

I'm trying to install beta 2..

I have removed all my disks, I have put a new disk and it is impossible to start the installation

 

 

 

If I put the ssd that has the previous MacOS installation if my user works....

 

 

 

Edited June 24, 2022 by PoMpIs

[Matgen84]

10 minutes ago, Cyberdevs said:

What about the EFI partition is there an oc version on your APFS formatted disk?

 

There is only Clover both HDD and USB Installer 

 

9 minutes ago, eSaF said:

Remember like I said you have to use all lower letters, also if you have something like  Mat-gen84, you have to include all but like this mat-gen84. What ever Admin P/W you use must be entered in lower case letters. If you have another Disk with Monterey and a different Admin P/W try that but use the format in lower case regardless how you usually enter it.

 

I try again and again using lower case format, without success like mathieu (usual admin user name) 🤔 

[PoMpIs]

This means that if I buy a new computer I cannot install Beta 2 macOS because I can never spend that part by not having an previous installation. ??
 

 

I have put the old SSD again with ventura installed and the beta 2 installer has already worked😆

[Anto65]

10 minutes ago, eSaF said:

Sono d'accordo sul fatto che la tua affermazione abbia meriti su cui vale la pena pensare, ma ricordo che in passato ho portato avanti problemi tecnici o disallineamenti da una beta all'altra con aggiornamenti incrementali, quindi perché mi piace eseguire installazioni beta pulite di tanto in tanto. In realtà sostengo installazioni pulite per le versioni GM e le versioni ufficiali. Inoltre, se alcuni di noi non hanno tentato di pulire l'installazione di Ventura Beta 2, non sapremmo di questo P/W amministratore da inserire quando si sceglie il disco di installazione se si tratta di un bug Beta o meno in questa fase. Tuttavia, hai un punto valido, preservare la vita al Drive.

 

@PoMpIs - Pensa a tutti i P/W di amministrazione che hai utilizzato per installare OS X di recente, più a ciò che stai attualmente utilizzando per accedere alla macchina all'avvio (non al tuo ID Apple a meno che non lo usi anche per sbloccare la tua macchina).

nope without another disk with osx on you can't install V .beta 2 ... ridiculous

[PoMpIs]

@eSaFI have tried with everyone name and password……  without a SSD on the computer that already has macOS installed it is impossible to move from that 😄

Edited June 24, 2022 by PoMpIs

[Anto65]

3 minutes ago, eSaF said:

But I did with my SSD Test Disk whilst Ventura was on a M.2 Drive and in the machine as well as my Windows M.2 also.

Try to install it on your SSD Test Disk, without any other drive present 

[PoMpIs]

If you have another SSD with macOS installed if it works, even Monterey,

Without that, beta 2 does not work, you can't install

There is no choice but to use beta 1 if you don't have a previous installation and update Beta 2

 

[Anto65]

6 minutes ago, eSaF said:

Ok will give it a try and report. I will not take the drives out as it is too much, just eliminate them in the BIOS.

If you also have the option in the bios to disable the units (which is great) it's easy to try ... so I did 🙂

[Cyberdevs]

I have a hunch that a Bios reset might resolve this issue because nvram reset fails to do anything  but I can’t test that theory right now because I’m not at home.

I’ll test that theory once I get back but if anyone can test it, it’ll be nice to know if that works or not.

[PoMpIs]

@eSaF You have to remove the sata cable from the disks, and if they are NVMe you have to remove it... otherwise the installation will pass

 

@Cyberdevs  i try it right now 😁 

 

I'll tell you soon

[PoMpIs]

@eSaF   @Cyberdevs   

 

I have reset the BIOS from the back panel button on the motherboard ....

it does not work 

 

[Anto65]

Game Over   ... waiting beta3

[Cyberdevs]

@eSaF

i misinterpreted your post

I am aware of the conversation of the uppercase to lowercase in macOS username creation. It been like this since the very beginning of the Mac OS X and later on macOS.

[Anto65]

4 minutes ago, eSaF said:

Ok I will have to take your word, it is too much to take my M.2 Drives out, I will near enough have to dismantle half the machine, but it is something I will bear in mind going forward.

Save yourself the trouble ... believe me it does not go on a single blank disk with no other osx around, without another "companion" 

 

The only solution for those who want to get to beta 2, will have to go through a clean install of beta1 first and then upgrade to beta 2 ... but not a direct beta2 clean install

[PoMpIs]

@eSaF  

 

Without SSD with previous installation of MacOS:

 

With SSD and a previous installation of MacOS:

 

 

😆

 

 

[Guest ricoc90]

When entering an username, according to the installer log it looks for the user file of said user. I assume it looks for that file on all mounted devices. If none is present then it can’t authenticate either because the credentials would always be wrong. It’s so stupid.

[dogansan]

On 6/24/2022 at 12:33 AM, Stefanalmare said:

OK, I take this back! I finally installed Ventura beta 2 on external SSD on Ivy desktop and laptop. Works with Opencore and Clover. Using

https://github.com/dortania/OpenCore-Legacy-Patcher/issues/998

https://mrmacintosh.com/apple-silicon-m1-full-macos-restore-ipsw-firmware-files-database/

https://forums.macrumors.com/threads/oc-ventura-install-on-cmp-5-1.2347310/?post=31172042#post-31172042

 

  Reveal hidden contents

 

 

  Reveal hidden contents

 

Stefanalmare , would you please share your Clover EFI folder, I remember you had Ivy bridge. I am able to run my Ventura with Opencore ,but it freezes whenever I start Edge or Chrome. I want give a try with Clover

[SavageAUS]

Does anyone else experience strange behaviour with dark mode? Dark mode works great once logged in but my login screen is light mode.

I have tried to reset nvram, changed to light mode - reboot - dark mode - reboot to no avail.

Edited June 25, 2022 by SavageAUS

[greythorne]

21 hours ago, fusion71au said:

 

I use the latest stable versions of Heliport app v1.41 and itlwm.kext v2.1.0 --> these work well in macOS 11 up to 13beta2.  In Monterey, the Kabylake graphics kexts load and I still get graphics acceleration using -igfxsklaskbl boot argument as discussed in my previous post...

 

  Reveal hidden contents

 

Haven't tried AirportItlwm.kext yet so can't comment on it.

 

Any success with your NUC6i3SYH in Monterey or Ventura loading Kabylake kexts with graphics acceleration?  I assume you've tried framebuffer 0x59160000 for Intel UHD 620?

 

  Reveal hidden contents

 

Good luck!

Yup. Managed to install Ventura. First installed the Beta 1 then update to Beta 2 thru Software Update. No issues at all. There was no prompts for the admin login.

 

Just a quick question. I have the -igfxsklaskbl in the boot-arg in my config.plist. Also spoofed the iGPU in the device properties. Do I still need the boot-arg flag?

I added the model = Intel Graphics 620 in the device properties, hence you can see the Chipset Model as the model name. Of course in actual fact it is still a SKL graphics.

 

Another question. How do you remove or delete bluetooth devices and add in again in the System Settings?

 

A big shout out to all the Developers who made it possible to be able to run Ventura on SkyLake and @aben & @fusion71au. Thanks guys!!

[Guest 5T33Z0]

@greythorne Whatevergreen lists it as a boot-arg:

 

"-igfxsklaskbl to enforce Kaby Lake (KBL) graphics kext being loaded and used on Skylake models (KBL device-id and ig-platform-id are required)"

 

I don't know if it is still a requirement. Just disable it, reboot and check if acceleration is still working and report back

[Ludox]

Beta 2 perfect upgrade

[aben]

@greythorne Congrats!  

 

With regards to -igfxsklaskbl:  this WEG boot-arg was implemented solely to force test the VP9 patch for SKL generation, when attempting to spoof to KBL, on macOS versions older than Ventura. Since WEG logic will automatically force this patch for SKL on macOS 13+, you may safely omit this boot-arg when booting Ventura.

Edited June 25, 2022 by aben