macOS 13 Ventura on Unsupported Macs Thread

[K two]

I only upgrade my Mac when the macOS upgrade appears in my System Settings > General > Software Update. So far, the .2 upgrade has not appeared for me.

Never had this issue before upgrading from USB made w/OCLP.

 

[K two]

I haven't seen it on my MacBookPro11,4 yet. Should I update OCLP to 1.2.0 before or after I try upgrading?

Running the release version of OCLP is preferred on Unsupported Macs

 

[deeveedee]

Running the release version of OCLP is preferred on Unsupported Macs

I'm still patching Ventura with OCLP 0.6.8. It seems to me that the focus of OCLP has been on Sonoma, so I prefer to allow OCLP to mature before upgrading the patch on my reliable Ventura volume. Just my preference.

EDIT: Also, I think this MacWorld article implies that 13.6.2 is only for M3. Looks like there is some confusion about 13.6.2.

 

[davidlv]

I'm still patching Ventura with OCLP 0.6.8. It seems to me that the focus of OCLP has been on Sonoma, so I prefer to allow OCLP to mature before upgrading the patch on my reliable Ventura volume. Just my preference.

EDIT: Also, I think this MacWorld article implies that 13.6.2 is only for M3. Looks like there is some confusion about 13.6.2.

Yah, it confused me too! I saw a post on https://www.xlr8yourmac.com/ about the update, didn't read it carefully and went directly to Mr. Macintoshes page, download that and tried to make a USB installer, which errored out.
So confused.... then I reread the xlr8yourmac post and Mr. Macintoshes page and realized it was all my mistake.
Happens to all of us at times.
Apple has never, in my not so long memory, put out an "out-of-date update" like that, so it is not surprising that there is some confusion.

 

[K two]

I'm still patching Ventura with OCLP 0.6.8. It seems to me that the focus of OCLP has been on Sonoma, so I prefer to allow OCLP to mature before upgrading the patch on my reliable Ventura volume. Just my preference.

EDIT: Also, I think this MacWorld article implies that 13.6.2 is only for M3. Looks like there is some confusion about 13.6.2.

Ventura has been perfectly acceptable w/v.1.2.0. This update gollywallop is NOT an OCLP problem.

 

[davidlv]

Ventura has been perfectly acceptable w/v.1.2.0. This update gollywallop is NOT an OCLP problem.

Amid all of that gollywallop (great word, have to remember it), I did a search and found that version23B417 of 13.6.2 is available as a Developer's Beta. Installed that on my iMac on a separate Volume, with OCLP 1.2.0 and all is good.
no more .

 

[deeveedee]

Ventura has been perfectly acceptable w/v.1.2.0. This update gollywallop is NOT an OCLP problem.

Good to know and generally agree with your advice to use the latest OCLP release. Ventura 13.6.1 is my production macOS volume, so I'm much more conservative when it comes to updates. As others like you report success with Ventura and OCLP 1.2.0+, I'll start to look at an OCLP upgrade. With my production macOS, I don't need OCLP bragging rights.

 

[RK78]

Holding off for now on updating OCLP + 13.6.2 until the dust settles.

Question: want to create a backup (most likely SuperDuper) which would involve space on Firewire connected external drive. Check the box for Firewire booting in OCLP settings (1.1.0), but on logout and login that check mark disappears. What does that mean? No Firewire booting?

Also, that external drive in question is formatted APFS, but connected to my High Sierra internal. Is that a no go?

 

[K two]

Holding off for now on updating OCLP + 13.6.2 until the dust settles.

Question: want to create a backup (most likely SuperDuper) which would involve space on Firewire connected external drive. Check the box for Firewire booting in OCLP settings (1.1.0), but on logout and login that check mark disappears. What does that mean? No Firewire booting?

Also, that external drive in question is formatted APFS, but connected to my High Sierra internal. Is that a no go?

Sorry for the dust, my bad. 🤥

 

[RK78]

No problem, Endust? (Although latest Endust I've tried is a bit greasy - trade dust for grease?)

But what about the backup question?

 

[K two]

No problem, Endust? (Although latest Endust I've tried is a bit greasy - trade dust for grease?

But what about the backup question?

HS and OCLP on the same disk is a no-go. Try the release version v.1.2.0 for the FW issue? 🤷‍♂️

 

[internetzel]

Holding off for now on updating OCLP + 13.6.2 until the dust settles.

Question: want to create a backup (most likely SuperDuper) which would involve space on Firewire connected external drive. Check the box for Firewire booting in OCLP settings (1.1.0), but on logout and login that check mark disappears. What does that mean? No Firewire booting?

Also, that external drive in question is formatted APFS, but connected to my High Sierra internal. Is that a no go?

Any OCLP settings on the tabs "Build", "Extras", "Advanced" and "Security" aren't settings in the way we are used to but are only applied to the "Build and Install OpenCore" process. They aren't even remembered when restarting the OCLP app.
The settings on the tab "Root Patching" in the same way apply to the process "Post-Install Root Patch".
Only the settings on the tab "App" seem to be settings of the OCLP app itself, which are potentially saved and reloaded when reopening the OCLP app.

 

[K two]

Any OCLP settings on the tabs "Build", "Extras", "Advanced" and "Security" aren't settings in the way we are used to but are only applied to the "Build and Install OpenCore" process. They aren't even remembered when restarting the OCLP app.
The settings on the tab "Root Patching" in the same way apply to the process "Post-Install Root Patch".
Only the settings on the tab "App" seem to be settings of the OCLP app itself, which are potentially saved and reloaded when reopening the OCLP app.

The only place in OCLP for FW is under the Build option, don't have a USB3 to FW adapter to test further. 🤷‍♂️

 

[internetzel]

The only place in OCLP for FW is under the Build option, don't have a USB3 to FW adapter to test further. 🤷‍♂️

The key aspect in my answer was that checking the FireWire boot option without subsequently hitting "Build and Install OpenCore" and rebooting afterwards will have zero effect.
Any options on the "Build", "Extras", "Advanced" and "Security" tabs need a "Build and Install OpenCore" executed afterwards in order to have any effect at all.

 

[K two]

The key aspect in my answer was that checking the FireWire boot option without subsequently hitting "Build and Install OpenCore" and rebooting afterwards will have zero effect.
Any options on the "Build", "Extras", "Advanced" and "Security" tabs need a "Build and Install OpenCore" executed afterwards in order to have any effect at all.

Got it, now. Thanks. 😶‍🌫️

 

[davidlv]

Holding off for now on updating OCLP + 13.6.2 until the dust settles.

Question: want to create a backup (most likely SuperDuper) which would involve space on Firewire connected external drive. Check the box for Firewire booting in OCLP settings (1.1.0), but on logout and login that check mark disappears. What does that mean? No Firewire booting?

Also, that external drive in question is formatted APFS, but connected to my High Sierra internal. Is that a no go?

You can use Superduper or Carbon Copy Cloner to make a backup on that APFS Firewire disk and it should be readable under the other systems available now. The Problem with High Sierra is it doesn't completely understand disks formatted using a later edition of APFS. It also corrupts its own preboot partition. Unless you have pressing reasons for staying with HS, using a later macOS is advisable. Mojave is the last to support 32-bit apps. I switched to Big Sur back in the day when it came out and never went back. Firewire too is mostly dead and gone. Can you use your hardware with a newer system? That is, what computer are you using? (put that info in your signature?

 

[RK78]

You can use Superduper or Carbon Copy Cloner to make a backup on that APFS Firewire disk and it should be readable under the other systems available now. The Problem with High Sierra is it doesn't completely understand disks formatted using a later edition of APFS. It also corrupts its own preboot partition. Unless you have pressing reasons for staying with HS, using a later macOS is advisable. Mojave is the last to support 32-bit apps. I switched to Big Sur back in the day when it came out and never went back. Firewire too is mostly dead and gone. Can you use your hardware with a newer system? That is, what computer are you using? (put that info in your signature?

Thanks.

I realize that I'm not really doing justice to the Ventura via OCLP and know that I will have to bite the bullet at some point and erase the current internal High Sierra 10.13.6 volume and install the Ventura there.

I've mentioned this before, but if it weren't for Firefox being deprecated for 10.14 and below by next September - and Brave, my backup browser already no longer getting any updates, I would happily stay with this current HS, 10.13.6, where I have years of accumulated stuff, and know just where to find things. Have zero interest in any of the new features, whatever they may be - in fact, from what I can see, at least with this compromised trial run with Ventura, at least for me, Apple has removed more useful stuff than it has added. For example, there used to be an option to uncheck Allow Bluetooth devices to wake this computer - very useful with my Apple bluetooth mouse, or with other nearby bluetooth, completely gone now in Ventura. As a replacement, in order not to find the Mac had been woken and was running all night long, had to install 3rd party extension bluesnooze. https://github.com/odlp/bluesnooze.

Also energy saver prefs completely changed and made far less useful.

In any case, would it still be a reasonable crapshoot to go ahead and try to create a backup on this APFS formatted Firewire drive? Maybe in order to be able to recover specific items, but nothing bootable?

 

[davidlv]

Thanks.

I realize that I'm not really doing justice to the Ventura via OCLP and know that I will have to bite the bullet at some point and erase the current internal High Sierra 10.13.6 volume and install the Ventura there.

I've mentioned this before, but if it weren't for Firefox being deprecated for 10.14 and below by next September - and Brave, my backup browser already no longer getting any updates, I would happily stay with this current HS, 10.13.6, where I have years of accumulated stuff, and know just where to find things. Have zero interest in any of the new features, whatever they may be - in fact, from what I can see, at least with this compromised trial run with Ventura, at least for me, Apple has removed more useful stuff than it has added. For example, there used to be an option to uncheck Allow Bluetooth devices to wake this computer - very useful with my Apple bluetooth mouse, or with other nearby bluetooth, completely gone now in Ventura. As a replacement, in order not to find the Mac had been woken and was running all night long, had to install 3rd party extension bluesnooze. https://github.com/odlp/bluesnooze.

Also energy saver prefs completely changed and made far less useful.

In any case, would it still be a reasonable crapshoot to go ahead and try to create a backup on this APFS formatted Firewire drive? Maybe in order to be able to recover specific items, but nothing bootable?

Yes I do think you should make a back up soon, like now!
If at all possible, that new backup APFS SSD should be formatted using a system later than HS. HS really has the poorest version of APFS Apple produced. HS can usually write to such a disk, and it will ensure the data is good when you connect to a Ventura or Sonoma system.
You are also worrying about several things that just hurt your head without any necessity.
Like: Wake for network access is now in the Battery section in Sonoma, it is in the Energy Saver section in Ventura, it is still available. But that is not Bluetooth. Bluetooth and Network are two different things. So you may indeed have to use that utility "Bluesnooze." See: https://www.google.com/search?q=in+...BgewgIGEAAYHhgPwgIHEAAYExiABA&sclient=gws-wiz
Another: Brave now gets updates automatically, get the latest version at https://github.com/brave/
Click on the blue "Brave-browser" sort of top left, and then on "latest" lower right, to get access to tons of platform specific versions. These will work with Big Sur up through Sonoma.
And anothe; in regard to "accumulated stuff, and know just where to find things", make a Carbon Copy Cloner (CCC) regular backup to a new SSD (not a bootable clone). When you install the new system, be it Ventura or Sonoma whatever, at the last part of the install, you will be prompted to connect a Mac or disk. Connect that CCC backup disk and let the Migration Assistant copy your data back to the newly installed system. When you are finished you will have everything back where it was! Easy.
Learning not to fret and adapting to the new system without any unnecessary stress may give you a few more years on this world, that might make it easier if you think about it. Later in your memoirs, you can write about how Apple caused years of unnecessary pain, and then all the little ones will say, "Really, I had no issues adapting to that!" Good for a laugh or two that will be.

 

[Komyea]

does anyone have a confirmed list of apple wifi/bt cards that work with ventura? i purchased a 653-00005 however no devices will stay connected. they disconnect within a second or two of connecting to BT. wifi works fine.

 

[deeveedee]

@Komyea You might find what you want by looking at the OCLP Sonoma patches that enable Wi-Fi. This is extracted from OCLP's data/pci_data.py:

    AirPortBrcmNIC = [
        # AirPortBrcmNIC IDs
        0x43BA,  # BCM43602
        0x43A3,  # BCM4350
        0x43A0,  # BCM4360
    ]   
        
    # Not natively supported, but supported by AirportBrcmFixup
    AirPortBrcmNICThirdParty = [
        0x4357,  # BCM43225
        0x43B1,  # BCM4352
        0x43B2,  # BCM4352 (2.4 GHz)
    ]   
        
    AirPortBrcm4360 = [
        # AirPortBrcm4360 IDs (removed duplicates for 4360 class cards)
        0x4331,  # BCM94331
        0x4353,  # BCM943224
    ]

 

[Komyea]

@Komyea You might find what you want by looking at the OCLP Sonoma patches that enable Wi-Fi. This is extracted from OCLP's data/pci_data.py:

    AirPortBrcmNIC = [
        # AirPortBrcmNIC IDs
        0x43BA,  # BCM43602
        0x43A3,  # BCM4350
        0x43A0,  # BCM4360
    ]  
       
    # Not natively supported, but supported by AirportBrcmFixup
    AirPortBrcmNICThirdParty = [
        0x4357,  # BCM43225
        0x43B1,  # BCM4352
        0x43B2,  # BCM4352 (2.4 GHz)
    ]  
       
    AirPortBrcm4360 = [
        # AirPortBrcm4360 IDs (removed duplicates for 4360 class cards)
        0x4331,  # BCM94331
        0x4353,  # BCM943224
    ]

thank you for that.

i just noticed in my system information under BT that discoverable is off even though in the system settings BT is on...i think this is why it's not working correctly. anyway to resolve this?

 

[deeveedee]

thank you for that.

i just noticed in my system information under BT that discoverable is off even though in the system settings BT is on...i think this is why it's not working correctly. anyway to resolve this?

Always provide your OCLP version and macOS version number when asking for help. There have been OCLP updates depending on your OCLP version. Just guessing, but if you're using OCLP 0.6.8 or older, you would benefit from OCLP 1.2.0. Download OCLP 1.2.0, "Build and Install OpenCore" with 1.2.0 and apply post-install patches with 1.2.0. Then reboot.

EDIT: After you reboot, tap the space bar to show the Open Core extended menu and select "Reset NVRAM." Allow your Mac to reboot.

 

[Komyea]

Always provide your OCLP version and macOS version number when asking for help. There have been OCLP updates depending on your OCLP version. Just guessing, but if you're using OCLP 0.6.8 or older, you would benefit from OCLP 1.2.0. Download OCLP 1.2.0, "Build and Install OpenCore" with 1.2.0 and apply post-install patches with 1.2.0. Then reboot.

EDIT: After you reboot, tap the space bar to show the Open Core extended menu and select "Reset NVRAM." Allow your Mac to reboot.

of course how silly of me, my apologies.

OCLP version: 1.2.0
macOS version: 13.6.1

resetting nvram did not solve.

 

[deeveedee]

of course how silly of me, my apologies.

OCLP version: 1.2.0
macOS version: 13.6.1

resetting nvram did not solve.

Not silly, but hard to help without knowing.

Please execute the following in terminal and report results:

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version

kextstat | grep -i bluetool

EDIT: @Komyea Also please provide your Mac's SMBIOS Model.

 

[Komyea]

Not silly, but hard to help without knowing.

Please execute the following in terminal and report results:

nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:OCLP-Version

kextstat | grep -i bluetool

1.2.0%00

48 0 0xffffff8002abb000 0x37000 0x37000 com.apple.iokit.IOBluetoothFamily (9.0.0) 48641460-E7DF-3897-ADA1-FD90A95D31A9 <47 25 16 9 8 7 6 3 1>

161 0 0xffffff7f978a0000 0xfff 0xfff com.apple.iokit.BroadcomBluetooth20703USBTransport (9.0.0) 7B70575D-1DA2-3667-851F-B12CCE183E0C <9 8 7 6 3>

163 0 0xffffff7f978a3000 0x1000 0x1000 com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport (9.0.0) A80AE7AC-7FDB-3968-BC23-F13F20FE9EC4 <9 8 7 6 3>

164 0 0xffffff7f978a6000 0xfff 0xfff com.apple.iokit.CSRBluetoothHostControllerUSBTransport (9.0.0) 23D674AC-7739-32F5-B64D-3C1104EA4DE8 <9 8 7 6 3>

165 0 0xffffff7f97a2a000 0xfff 0xfff com.apple.driver.IOBluetoothHostControllerPCIeTransport (9.0.0) 4416A03B-7349-31B1-9E35-E2CA2644C673 <9 8 7 6 3>

166 0 0xffffff7f97a2d000 0xfff 0xfff com.apple.iokit.IOBluetoothHostControllerTransport (9.0.0) 6992EFEA-B257-3462-9185-C3D870DD7B85 <9 8 7 6 3>

167 0 0xffffff7f97a30000 0xfff 0xfff com.apple.iokit.IOBluetoothHostControllerUARTTransport (9.0.0) 3B804DF9-6F64-3895-81F1-D5312EB9155F <9 8 7 6 3>

168 0 0xffffff7f97a33000 0x1000 0x1000 com.apple.iokit.IOBluetoothHostControllerUSBTransport (9.0.0) 605B865E-EE05-31D5-9458-28B8BC19FD0C <9 8 7 6 3>

169 0 0xffffff7f97a36000 0x1000 0x1000 com.apple.iokit.IOBluetoothPacketLogger (9.0.0) 9D6725C5-4683-305C-AA29-D963B6DE6C13 <9 8 7 6 3>

170 0 0xffffff7f97a39000 0xfff 0xfff com.apple.iokit.IOBluetoothSerialManager (9.0.0) D1A02830-07A6-3FCB-A615-82E15509D37A <9 8 7 6 3>