I would suggest that you have something misconfigured on your system. As you can see, I was able to build and run the app using Python 3.10.7 with no problem. I'm glad you were successful in the end, but there seems to be an issue there.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 13 Ventura on Unsupported Macs Thread
- Thread starter 0xCUBE
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I would suggest that you have something misconfigured on your system. As you can see, I was able to build and run the app using Python 3.10.7 with no problem. I'm glad you were successful in the end, but there seems to be an issue there.
Just curious. Will the final OLCP version be released about the same time that Ventura is released to the public?
So I upgraded to Python 3.10.7, installed the same dependencies as in 3.9
pip3.10 install requests
pip3.10 install -U pyobjc
pip3.10 install -U wxPython
pip3.10 install pyinstaller... then ran the code-signing certs, verified install by CLI
python3 --version
Python 3.10.7building reports success:
~/Downloads/OpenCore-Legacy-Patcher-ventura-alpha/Build-Binary.command ; exit;
- Starting build script
- Current Working Directory:
~/Downloads/OpenCore-Legacy-Patcher-ventura-alpha
- Starting preflight processes
- Deleting extra binaries...
- Downloading required resources...
- Downloading Universal-Binaries.zip...
- Moving into payloads
- Generating DMG...
- DMG generation complete
- Found OpenCore-Patcher.app, removing...
- Building GUI binary...
- Starting postflight processes
- Patching LC_VERSION_MIN_MACOSX
- No commit data provided, adding source info
- Adding commit data to Info.plist
- Build script completed in 104.51 seconds
... resulting GUI.app runs when clicked and all settings work fine, with report:
Building Configuration on model: MacBookPro11,1
Created build folder
- Adding OpenCore v0.8.3 RELEASE
- Adding config.plist for OpenCore
- Adding Lilu.kext 1.6.2
- Adding CPUFriend.kext 1.2.5
- Enabling SMC exemption patch
- Adding FeatureUnlock.kext 1.0.9
- Fixing PCIe Storage Controller (1) reporting
- No 3rd Party NVMe drives found
- Found Wireless Device 14E4:43A0
- Adding AirportBrcmFixup.kext 2.1.3
- Setting Wireless Card's Country Code: DE
- Found ARPT device at PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)
- Adding USB-Map.kext
- Adding AppleUSBTopCase.kext 1.0.0
- Adding AppleUSBMultitouch.kext 1.0.0
- Adding OpenCanopy GUI
- Enable Beta Lilu support
- Enabling ShowPicker
- Adding ipc_control_port_options=0 to boot-args
- Adding AutoPkgInstaller.kext 1.0.1
- Set SIP to allow Root Volume patching
- Disabling Library Validation
- Adding CSLVFixup.kext 2.6.1
- Disabling SecureBootModel
- Enabling USB Rename Patches
- Adding bootmgfw.efi BlessOverride
- Enabling VMX Bit for non-macOS OSes
- Allowing FileVault on Root Patched systems
- Adding EFICheckDisabler.kext 1.0.6
- Using Model ID: MacBookPro14,1
- Using Board ID: Mac-B4831CEBD52A0C4C
- Using Advanced SMBIOS patching
- Cleaning up files
- Validating generated config
Your OpenCore EFI for MacBookPro11,1 has been built at:
/var/folders/dl/__rp20zx7cdfg5q43jn_26_00000gn/T/tmpwgl2mj4_/Build-Folder/OpenCore-Build... but then it fails on the final step of "Install to Disk", by throwing this garbled mess where literally nothing (tabbing, scrolling, selecting or resizing) in the window works anymore:
Probably not by coincidence, this is the exact same thing I saw when compiling it in Big Sur.
Has anyone else seen something like this? Most disturbing!!
PS: When I run the GUI.command in Python (without compiling), it shows this in Terminal:
Downloads/OpenCore-Legacy-Patcher-ventura-alpha/OpenCore-Patcher-GUI.command ; exit;
- Loading...
- No arguments present, loading GUI mode
Allow Native Models
SMBIOS Spoof Level: Advanced
SMBIOS Spoof Model: MacBookPro14,1
Allow Native Spoofs Enabled
disk0 - APPLE SSD SM0512F - 500.3 GB
Traceback (most recent call last):
File "/Users/BGS/Downloads/OpenCore-Legacy-Patcher-ventura-alpha/gui/gui_main.py", line 618, in build_install_menu
self.build_start()
File "/Users/BGS/Downloads/OpenCore-Legacy-Patcher-ventura-alpha/gui/gui_main.py", line 644, in build_start
self.install_menu()
File "/Users/BGS/Downloads/OpenCore-Legacy-Patcher-ventura-alpha/gui/gui_main.py", line 776, in install_menu
wx.Point(
TypeError: Point(): arguments did not match any overloaded call:
overload 1: too many arguments
overload 2: argument 2 has unexpected type 'float'
overload 3: argument 1 has unexpected type 'int'
overload 4: argument 1 has unexpected type 'int'on which a Google search leads to some fairly complicated stuff
wx.Colour does not accept float values in debug mode · Issue #1442 · wxWidgets/Phoenix
Operating system: Debian Testing, Xorg with 200% scaling wxPython version & source: 4.0.7 gtk3 (phoenix) wxWidgets 3.0.4 from debian repos Python version & source: 3.7.5 from debian repos Descripti...
github.com
"Not an incompatibility, but rather a change in Python 3.10 to disallow passing floats to extension modules where ints are expected."
So it looks as if my Python 3.10.7 install on 12.6 is somehow not clean or incomplete - does anyone see what I have missed or know how to do this in a foolproof way?
Last edited:
I think this is what the devs are aiming for but obviously there are no guarantees. It could equally well be 6 months later ...
I can't reproduce it here, using python 3.9, but I vaguely recall that I've seen it once quite a while ago. If I remember correctly, remaking the EFI cured it, but could also have been the py version.So I upgraded to Python 3.10.7, installed the same dependencies as in 3.9
pip3.10 install requests pip3.10 install -U pyobjc pip3.10 install -U wxPython pip3.10 install pyinstaller
... then ran the code-signing certs, verified install by CLI
python3 --version Python 3.10.7
building reports success:
~/Downloads/OpenCore-Legacy-Patcher-ventura-alpha/Build-Binary.command ; exit; - Starting build script - Current Working Directory: ~/Downloads/OpenCore-Legacy-Patcher-ventura-alpha - Starting preflight processes - Deleting extra binaries... - Downloading required resources... - Downloading Universal-Binaries.zip... - Moving into payloads - Generating DMG... - DMG generation complete - Found OpenCore-Patcher.app, removing... - Building GUI binary... - Starting postflight processes - Patching LC_VERSION_MIN_MACOSX - No commit data provided, adding source info - Adding commit data to Info.plist - Build script completed in 104.51 seconds
... resulting GUI.app runs when clicked and all settings work fine, with report:
Building Configuration on model: MacBookPro11,1 Created build folder - Adding OpenCore v0.8.3 RELEASE - Adding config.plist for OpenCore - Adding Lilu.kext 1.6.2 - Adding CPUFriend.kext 1.2.5 - Enabling SMC exemption patch - Adding FeatureUnlock.kext 1.0.9 - Fixing PCIe Storage Controller (1) reporting - No 3rd Party NVMe drives found - Found Wireless Device 14E4:43A0 - Adding AirportBrcmFixup.kext 2.1.3 - Setting Wireless Card's Country Code: DE - Found ARPT device at PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0) - Adding USB-Map.kext - Adding AppleUSBTopCase.kext 1.0.0 - Adding AppleUSBMultitouch.kext 1.0.0 - Adding OpenCanopy GUI - Enable Beta Lilu support - Enabling ShowPicker - Adding ipc_control_port_options=0 to boot-args - Adding AutoPkgInstaller.kext 1.0.1 - Set SIP to allow Root Volume patching - Disabling Library Validation - Adding CSLVFixup.kext 2.6.1 - Disabling SecureBootModel - Enabling USB Rename Patches - Adding bootmgfw.efi BlessOverride - Enabling VMX Bit for non-macOS OSes - Allowing FileVault on Root Patched systems - Adding EFICheckDisabler.kext 1.0.6 - Using Model ID: MacBookPro14,1 - Using Board ID: Mac-B4831CEBD52A0C4C - Using Advanced SMBIOS patching - Cleaning up files - Validating generated config Your OpenCore EFI for MacBookPro11,1 has been built at: /var/folders/dl/__rp20zx7cdfg5q43jn_26_00000gn/T/tmpwgl2mj4_/Build-Folder/OpenCore-Build
... but then it fails on the final step of "Install to Disk", by throwing this garbled mess where literally nothing (tabbing, scrolling, selecting or resizing) in the window works anymore:
View attachment 2080497
Probably not by coincidence, this is the exact same thing I saw when compiling it in Big Sur.
Has anyone else seen something like this? Most disturbing!!
PS: When I run the GUI.command in Python (without compiling), it shows this in Terminal:
Downloads/OpenCore-Legacy-Patcher-ventura-alpha/OpenCore-Patcher-GUI.command ; exit; - Loading... - No arguments present, loading GUI mode Allow Native Models SMBIOS Spoof Level: Advanced SMBIOS Spoof Model: MacBookPro14,1 Allow Native Spoofs Enabled disk0 - APPLE SSD SM0512F - 500.3 GB Traceback (most recent call last): File "/Users/BGS/Downloads/OpenCore-Legacy-Patcher-ventura-alpha/gui/gui_main.py", line 618, in build_install_menu self.build_start() File "/Users/BGS/Downloads/OpenCore-Legacy-Patcher-ventura-alpha/gui/gui_main.py", line 644, in build_start self.install_menu() File "/Users/BGS/Downloads/OpenCore-Legacy-Patcher-ventura-alpha/gui/gui_main.py", line 776, in install_menu wx.Point( TypeError: Point(): arguments did not match any overloaded call: overload 1: too many arguments overload 2: argument 2 has unexpected type 'float' overload 3: argument 1 has unexpected type 'int' overload 4: argument 1 has unexpected type 'int'
on which a Google search leads to some fairly complicated stuff
wx.Colour does not accept float values in debug mode · Issue #1442 · wxWidgets/Phoenix
Operating system: Debian Testing, Xorg with 200% scaling wxPython version & source: 4.0.7 gtk3 (phoenix) wxWidgets 3.0.4 from debian repos Python version & source: 3.7.5 from debian repos Descripti...
"Not an incompatibility, but rather a change in Python 3.10 to disallow passing floats to extension modules where ints are expected."
So it looks as if my Python 3.10.7 install on 12.6 is somehow not clean or incomplete - does anyone see what I have missed or know how to do this in a foolproof way?
Anyway as for the Python version, in principle the OCLP doc says they use Python 3.9:
OpenCore-Legacy-Patcher/SOURCE.md at ventura-alpha · dortania/OpenCore-Legacy-Patcher
Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.
github.com
In my case the Python installations look like in the attached Terminal output. If you also have py 3.9 installed, you could try invoking it explicitely with python3.9 as terminal command.
Also if you like it may be interesting to look at some of OCLP's Python sources, e.g. the one causing the problem reported in the traceback: https://github.com/dortania/OpenCore-Legacy-Patcher/blob/ventura-alpha/gui/gui_main.py
Good luck! Good that you try to run from source rather than take a pre-built app (the SOURCE.md links it, but seems not up to date).
Attachments
Last edited:
Thanks for the input: do I understand correctly you've seen the garbled/frozen OCLP.GUI from own build at one stage and that "remaking the EFI" (from which your machine boots) may have resolved it?I can't reproduce it here, using python 3.9, but I vaguely recall that I've seen it once quite a while ago. If I remember correctly, remaking the EFI cured it, but could also have been the py version.
Anyway as for the Python version, in principle the OCLP doc says they use Python 3.9:
see under Getting Started. Though binarysmurf runs fine with 3.10.
OpenCore-Legacy-Patcher/SOURCE.md at ventura-alpha · dortania/OpenCore-Legacy-Patcher
Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.
In my case the Python installations look like in the attached Terminal output. If you also have py 3.9 installed, you could try invoking it explicitely with python3.9 as terminal command.
Also if you like it may be interesting to look at some of OCLP's Python sources, e.g. the one causing the problem reported in the traceback: https://github.com/dortania/OpenCore-Legacy-Patcher/blob/ventura-alpha/gui/gui_main.py
Good luck! Good that you try to run from source rather than take a pre-built app (the SOURCE.md links it, but seems not up to date).
If so, what did remaking EFI consist of exactly?
Yeah, I had heard somewhere that Python3.9 is more compatible with OC.
I get the following when doing the same commands you had in Terminal:
BGS@MacBook-Pro ~ % python3
Python 3.10.7 (v3.10.7:6cc6b13308, Sep 5 2022, 14:02:52) [Clang 13.0.0 (clang-1300.0.29.30)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> ^D
BGS@MacBook-Pro ~ % which python3
/Library/Frameworks/Python.framework/Versions/3.10/bin/python3
BGS@MacBook-Pro ~ % ls -l /Library/Frameworks/Python.framework/Versions/
total 0
drwxrwxr-x 11 root admin 352 Sep 26 02:01 3.10
drwxrwxr-x 11 root admin 352 Sep 25 19:06 3.9
lrwxr-xr-x 1 root wheel 4 Sep 26 02:01 Current -> 3.10
BGS@MacBook-Pro ~ % python3.10
Python 3.10.7 (v3.10.7:6cc6b13308, Sep 5 2022, 14:02:52) [Clang 13.0.0 (clang-1300.0.29.30)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> ^D
BGS@MacBook-Pro ~ % python3.9
Python 3.9.13 (v3.9.13:6de2ca5339, May 17 2022, 11:23:25)
[Clang 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> ^D
BGS@MacBook-Pro ~ % pyinstaller --version
5.4.1
BGS@MacBook-Pro ~ % python3 -m pip --version
pip 22.2.2 from /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/pip (python 3.10)
Two possible things to try:
- as you have python3.9 installed, run the OpenCore-Patcher-GUI.command explicitely unter 3.9 from the Terminal, rather than by double-clicking it (easiest is to pull the path to the command from the Finder window to the Terminal window after having typed python 3.9 . Maybe it works under 3.9 as this should do less type checking than 3.10.
If not:
- I've forgotten what I did to clear the EFI at the time, but tried now this as a useful possibility: the Disk Utility app doesn't show the EFI partitions, but the diskutil command in Terminal shows it and gives equivalent options.
Use the 2nd and 3rd screenshot to inspect what is in the EFI partition at present (after the mount the EFI is shown on the desktop).
I used reformat to erase the EFI partition's contents, and then OpenCore-Patcher-GUI.command to build/install it again. Both System and EFI directories are re-created.
Attachments
Cheers. All things considered, though, I don't see how anything in the EFI partition could possibly produce the garbled OCLP.GUI with the error messages as shown, so I will go with blitzing Python off my machine and doing a fresh install of 3.9 using Homebrew, to see if that resolves the issue.
I use Python installed with Brew to compile OpenCore Legacy Patcher (3.10 at the moment).
What I experienced was that when there is an XCode update, sometimes it screws up with the paths in my Python installation. Then, I remove Brew, reinstall it, and install Python (and the dependencies) again and all paths are fixed.
Thanks a lot to all developers......
Finally I was able with their aid to install Ventura b8 on my old 10 years Mac mini 6,2 A1347 late 2012 quad core on external SSD.
I used the os.dmg file, Kernel debug kit b8 and open core 0.5.0 built with python 3.10.7.
The same disk works also on Mac mini 6,1 A1347 late 2012 dual core
Thanks very much
Finally I was able with their aid to install Ventura b8 on my old 10 years Mac mini 6,2 A1347 late 2012 quad core on external SSD.
I used the os.dmg file, Kernel debug kit b8 and open core 0.5.0 built with python 3.10.7.
The same disk works also on Mac mini 6,1 A1347 late 2012 dual core
Thanks very much
Attachments
Last edited:
Yes, this sounds most likely to cure my woes. I had not previously installed Python using Homebrew. Will report beck tomorrow ...
Apple Seeds Ninth Beta of macOS 13 Ventura (22A5358e) to Developers
Could reproduce the problem now...
Installed python3.10 directly from the Python site, then the rest using OCLP's requirements.txt file.
Now using the lastest OCLP ventura alpha from just an hour ago.
Works with python 3.9 and with 3.10, shows what you saw before.
Could cure it by making a small modification in gui_main.py in line 776 as the traceback said - just avoided the float by writing 7 instead of 7.5. Now it also works in 3.10 (and it still does in 3.9).
I think I'll suggest it as a change in Discord.
Attachments
@hvds
Good find. I see it already added to OCLP (8 instead of 7). 👍
Good find. I see it already added to OCLP (8 instead of 7). 👍
Big thank you to khronokernel who does such tiny fixes immediately, among the large improvements like cryptex fixup for AVX2 and many others.
Given the good stability of 13.0b8 on my MBP5,2 (Penryn), did an OTA update to b9.
Worked completely unattended right to login. Using OCLP 050n (ventura alpha) from yesterday.
Graphics acceleration for non-Metal (Nvidia Tesla here) is a largely independent ongoing development if I understand correctly which might take long to very long. But even without it I can use the MBP5,2 without problems. The fun of being able to participate in Ventura more than compensates the slow response of the system.
Attachments
Last edited:
Totally agree. @khronokernel does a great and quality work. No doubt.
To conclude the saga -- I blitzed all Python & XCode from the machine then reinstalled Python 3.10.6 via Homebrew, including Command-Line Tools 14.0, downloaded latest OCLP 0.5.0 sourcecode, ran
Built an EFI spoofed as MBP14,1, copied to USB key & booted with it into external Ventura_B8_SSD, then root-patched that with Haswell5000 Graphics, which after a reboot gives full acceleration and is looking very presentable indeed.
The GeekBench 5.4.5 GPU Metal test still crashes the machine on the Canny task (as in Monterey), but otherwise the results are excellent, all keyboard controls, trackpad gestures and fan speed regulation work perfectly and the machine seems very stable on Ventura.
Am delighted with the results and foresee making Ventura my daily driver on this machine once 13.0 final is released.
Thanks again to all who assisted above & OCLP-Team for getting it this far!
pip3.10 install -r requirements.txt to install a heap of dependencies, then the build worked very smoothly and resulting GUI.app suffers no more nasty glitches ... YESS!!Built an EFI spoofed as MBP14,1, copied to USB key & booted with it into external Ventura_B8_SSD, then root-patched that with Haswell5000 Graphics, which after a reboot gives full acceleration and is looking very presentable indeed.
The GeekBench 5.4.5 GPU Metal test still crashes the machine on the Canny task (as in Monterey), but otherwise the results are excellent, all keyboard controls, trackpad gestures and fan speed regulation work perfectly and the machine seems very stable on Ventura.
Am delighted with the results and foresee making Ventura my daily driver on this machine once 13.0 final is released.
Thanks again to all who assisted above & OCLP-Team for getting it this far!
Just wondering, hows the performance for yall on pre-Haswell with Ventura?
Might need to upgrade from my early 2013 if it screws up with Ventura even more.
Thanks
Might need to upgrade from my early 2013 if it screws up with Ventura even more.
Thanks
^^^ An interesting new feature of the latest ventura-alpha 0.5.0 nightly: Library Validation and AMFI settings in the GUI; sadly, I still had to disable AMFI, in order to be able to boot my MBP11,3 (otherwise, it hangs halfway, without progress): but at least now it’s easier. BTW, will LV and AMFI disabling be required also in the final version, or is it only a temporary thing…?
Potentially dumb question ... Should I delete/re-download Universal-Binaries.zip and payloads.dmg every time before I rebuild the app after a repository pull?
I might take the plunge on Ventura when I know iMac13,2 is supported. 🤞🏼
I might take the plunge on Ventura when I know iMac13,2 is supported. 🤞🏼
i've searched but wanted to know how is it that you have graphics and i'm not so lucky. MBP11,2.To conclude the saga -- I blitzed all Python & XCode from the machine then reinstalled Python 3.10.6 via Homebrew, including Command-Line Tools 14.0, downloaded latest OCLP 0.5.0 sourcecode, ranpip3.10 install -r requirements.txtto install a heap of dependencies, then the build worked very smoothly and resulting GUI.app suffers no more nasty glitches ... YESS!!
Built an EFI spoofed as MBP14,1, copied to USB key & booted with it into external Ventura_B8_SSD, then root-patched that with Haswell5000 Graphics, which after a reboot gives full acceleration and is looking very presentable indeed.
View attachment 2082787
The GeekBench 5.4.5 GPU Metal test still crashes the machine on the Canny task (as in Monterey), but otherwise the results are excellent, all keyboard controls, trackpad gestures and fan speed regulation work perfectly and the machine seems very stable on Ventura.
Am delighted with the results and foresee making Ventura my daily driver on this machine once 13.0 final is released.
Thanks again to all who assisted above & OCLP-Team for getting it this far!
unknown display and 20mb should be same as you with Intel Iris 1536 MB
it's showing under Monterey
