Notifications
Clear all

macOS up to 11 Big Sur  

 of  7
  RSS

mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 4 years ago
 

At WWDC 2020, Apple finally announced a major advancement to the Mac - the migration to Apple silicon with backwards-compatible support for Intel via Rosetta 2 on newer ARM Macs. macOS Big Sur (11.0) is a significant visual overhaul that brings design-language and architecture parity to the Apple ecosystem. Naturally, Apple did not (at all) dive deep into what's happening to existing kernel extensions, etc. so I'll find out soon once I get into testing this new OS when possible. Will update this post with details that would matter most to eGPU users.

To start off, check out the press release. This release of macOS has eliminated the first-ever Retina Macs from the lineup, with the following minimum requirements:

This means all Thunderbolt 1 Macs are excluded. But we all know dosdude and fam are going to roll up on the scene and change the minimum.

Announcements

June 27, 2020: Early testing for purge-wrangler support for macOS Big Sur is now available for advanced users. Please refer to the advanced handbook.

Consequences for eGPU Users

  • Unable to mount system volume as writable as of macOS Big Sur Beta 1, meaning on-disk patching is not possible. This will affect scripts such as purge-wrangler and purge-nvda, that will be unable to patch the system. Thunderbolt 2 eGPU users should stay away from this release for now.

    Update: I was able to mount the system volume as writable only in Recovery - so not all hope is lost. It should be possible to patch the system in recovery then, but I have not tried it yet.

    Update #2: Noticed that the root system volume does not show up as "Mounted" in Disk Utility even though its present in /Volumes. Mounting it, I get another disk in /Volumes which I can indeed mount as writable. Testing more.

    Update #3: Figured out how to do it. Await script updates.

  • All kernel extensions require notarization to execute.
  • Rebuilding kernel caches is a very different experience. Typically we build it via the command:
    sudo kextcache -i /

    But this results in the following output:

    Executing: /usr/bin/kmutil install --volume-root / --check-rebuild
    rebuilding local auxiliary collection
    kmutil done
    

    So we have a new KernelManagement utility - kmutil. The correct way to ensure kernel collection is recreated is as follows:

    kmutil install --update-all --force --volume-root /Volumes/Macintosh\ HD

    Note: There seems to be a bug with kmutil and it does not seem to rebuild kextcache properly. By following instructions in the release notes, I was able to fix it though (I think).

  • This version of macOS introduces a cryptographically signed system volume. Which explains the problems I’m having above. This prevents tampering of that volume.
  • I investigated the OS to see if existing macOS patches would work - it does seem that they will. The only thing to find is how to apply these patches.
  • According to @michael_mohr, it fixes problems with eGPUs on Mac mini - https://egpu.io/forums/postid/82173/

About Signed System Volume

Excerpt from an Apple article:

In macOS Catalina, Apple introduced the read-only system volume, which is a dedicated, isolated volume for system content. Now, macOS Big Sur adds strong cryptographic protections to store system content on a signed system volume (SSV). SSV features a kernel mechanism that verifies the integrity of the system content at runtime, and rejects any data — code and non-code — that doesn’t have a valid cryptographic signature from Apple.

SSV helps prevent tampering with any Apple software that is part of the operating system. Additionally, it makes macOS Software Update more reliable and much safer. SSV utilizes APFS snapshots, so if an update cannot be performed, the old system version can be restored without reinstallation.

More notably:

Signed system volume is transparent for most developers. Kernel developers who must interact with the root volume can do so via a new System Integrity Protection mode available in the csrutil command line tool. When you enable this mode, it allows the tagging of custom snapshots using apfs_systemsnapshot, which you can then boot into.

Bypassing SSV

So the way macOS Big Sur is supposed to boot is that it never boots off the live volume, but a snapshot of it (its not happening on all systems though). Naturally, it is impossible to mount a "snapshot" as writable. So what can be done is as follows:

  1. In recovery Terminal:
    csrutil authenticated-root disable

    As of Beta 1, FileVault needs to be disabled to turn off ART.

  2. Back in normal boot, mount the live volume as writable. This is possible as on Catalina:
    diskutil mount disk1s5 # Use your live volume's disk identifier.
    sudo mount -uw /Volumes/Macintosh\ HD\ 1 # Use your live volume's name.
  3. Make modifications to the live volume.
  4. Generate and tag new APFS System Snapshot as follows:
    # Create snapshot.
    sudo /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -s "SnapshotName" -v /Volumes/Macintosh\ HD\ 1
    
    # Tag snapshot for next boot.
    sudo /System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -r "SnapshotName" -v /Volumes/Macintosh\ HD\ 1
  5. Reboot and voila!

So if you boot disk's name is "macOS" and you mount your live volume, it will show up as /Volumes/macOS\ 1.

To the Adventurous

Before installing macOS Big Sur beta, note the following:

  • Updating to macOS Big Sur 11 beta from previous versions of macOS might take significantly longer than expected. Data loss could occur if the update is interrupted. (59101197)
  • APFS containers with non-default allocation block sizes aren’t currently supported for installation. (64312561)
  • Update iMac Pro to macOS High Sierra 10.13.6 or later before installing macOS Big Sur 11 beta. (64314272)
  • If macOS Big Sur 11 beta is installed into the same APFS container as previous versions of macOS, system software updates can no longer be installed on the previous versions of macOS. (64411484)
  • Installation on Core Storage Fusion volumes with FileVault encryption enabled isn’t currently supported. (64472080)

 

The full changelog for Beta 1 is here:

Spoiler
macOS Big Sur Beta 1 Changelog

Overview

The macOS 11 SDK provides support to develop apps for Macs running macOS Big Sur 11. The SDK comes bundled with Xcode 12 beta. For information on the compatibility requirements for Xcode 12 beta, see Xcode 12 Beta Release Notes.

General

Known Issues

Third-Party Apps

Known Issues

  • CMake might not run, install, or might generate invalid outputs. (62905973)

    Workaround: Update to CMake 3.18rc1.

Accessibility

Known Issues

  • VoiceOver might be unavailable at certain times while installing macOS Big Sur 11 beta. (63025357)

App Store

New Features

AppKit

Auto Unlock

Known Issues

  • You might be unable to set up Auto Unlock. (64120075)

Calendar

Known Issues

  • If you click the Directions button on a calendar notification, Maps might not launch as expected. (63697152)

  • It isn’t possible to edit Calendar widgets. (63984003)

  • Accounts might not be visible in Preferences. (64117985)

Continuity

Known Issues

  • Continuity Handoff isn’t currently available in macOS Big Sur 11 beta. (64140413)

Core ML

Known Issues

Deprecations

  • The default initializer on the auto-generated model interface has been deprecated in favor of init(configuration:). Please use init(configuration:) or the newly introduced .load() method and handle model load errors as appropriate. (64432588)

Desktop Picture

Known Issues

  • If the desktop picture was never changed from the default macOS Catalina 10.15 image, it will persist after updating to macOS Big Sur 11 beta, even though the new default desktop picture is displayed in Desktop and Screen Saver preferences. (64390185)

Installer and Software Update

Known Issues

  • If you updated to macOS Big Sur 11 beta from a previous version of macOS, Software Update might show “Unable to check for updates - Failed to download the documentation for the minor update. Please try again later”. (63158434)

    Workaround:

    1. Start up from macOS Recovery.

    2. If your data volume is encrypted, use Disk Utility to mount it.

    3. In Terminal type rm -rf "/Volumes/Macintosh HD - Data/private/var/folders/zz/zyxvpxvq6csfxvn_n00000y800007k".

    4. Restart your Mac.

  • You might need to adjust Energy Saver settings so your Mac doesn’t go to sleep while preparing to install macOS Big Sur 11 beta. (63166401)

  • APFS containers with non-default allocation block sizes aren’t currently supported for installation. (64312561)

  • Update iMac Pro to macOS High Sierra 10.13.6 or later before installing macOS Big Sur 11 beta. (64314272)

  • Installation might pause on Macs that don’t have input devices connected. (64348347)

    Workaround: Connect an input device and dismiss the alerts to continue installation.

  • You might be unable to install macOS Big Sur 11 beta onto additional volumes. (63677460, 64445236)

    Workaround: Create a bootable installer using the createinstallmedia command.

  • Software Update might unexpectedly indicate updates for your Mac are being managed by swscan.apple.com, instead of indicating your Mac is enrolled in the Apple Beta Software Program. This doesn’t impact your ability to update macOS Big Sur 11 beta. (64407436)

  • If macOS Big Sur 11 beta is installed into the same APFS container as previous versions of macOS, system software updates can no longer be installed on the previous versions of macOS. (64411484)

  • Installation on Core Storage Fusion volumes with FileVault encryption enabled isn’t currently supported. (64472080)

Kernel

New Features

  • The kern.argmax limit has been increased, allowing programs to receive longer argument lists. (48661669)

  • Darwin kevent now allows non-parent processes to register for NOTE_EXITSTATUS, which delivers the same values as the wait() family of functions in the event data. Refer to the wait4() man page for more information. This event is subject to the following security checks:

    • The requesting process is allowed to send signals by sandbox restrictions.

    • The requesting process and the target process are running as the same user or the requesting process has root privileges. (58134463)

Known Issues

  • Installing a new kernel extension requires signing in as an Admin user. During kernel extension development, every time a kernel extension is changed, it must be signed and notarized. In both cases, your Mac must be restarted to load the extension. (55068348)

  • Remote panic dumps aren’t currently available. (57915324)

  • New in macOS Big Sur 11 beta, the system ships with a built-in dynamic linker cache of all system-provided libraries. As part of this change, copies of dynamic libraries are no longer present on the filesystem. Code that attempts to check for dynamic library presence by looking for a file at a path or enumerating a directory will fail. Instead, check for library presence by attempting to dlopen() the path, which will correctly check for the library in the cache. (62986286)

  • kmutil install might fail to build a development kextcache. (63772702)

    Workaround: Copy the release .elides to the locations of the development .elides:

    sudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.development.elidessudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.kasan.elides sudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.debug.elidessudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.development.elidessudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.kasan.elidessudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.debug.elides
  • Use only absolute paths with the --volume-root option of kmutil, and don’t use a trailing /. (63773848)

  • After removing a DriverKit extension, restart your Mac to complete uninstallation. (63995046)

  • Adhoc signed kernel extensions are displayed with a developer name of unknown in update dialogs and in Security preferences. (64215260)

  • Symbols exported by both xnu and Apple kernel extensions will change. Recompile your kernel extension with each update to macOS Big Sur 11 beta to ensure compatibility. (64262563)

  • Moving a kernel extension bundle out of /Library/Extensions might not completely uninstall it. (64331929)

    Workaround:

    1. Remove the extension from /Library/Extensions.

    2. Boot to macOS Recovery.

    3. Run Terminal.

    4. Enter the command kmutil invoke-panic-medic.

    5. Restart your Mac.

    6. Follow the prompt to open System Preferences and navigate to Security & Privacy.

    7. Follow the prompt to restart.

  • An unexpected System Extension Updated alert for third-party kernel extensions which are included in macOS might appear. These include: Accusys, Inc., ATTO Technology, Inc., Areca Technology Corporation, CalDigit, Inc., HighPoint Technologies, Inc., Promise Technology Mobile Apps, and Other World Computing. (64337113)

Deprecations

  • Kernel extensions using certain deprecated KPIs no longer load. Refer to the support page. While macOS Big Sur remains in development, you can temporarily disable System Integrity Protection to allow these deprecated extensions to load. (55068348)

Localization

Known Issues

  • Certain languages might exhibit clipped or misaligned layout. (63105445)

  • Certain languages might display unlocalized text. (63105674, 64040564, 64045718)

  • Some keyboard shortcuts might not work when running macOS Big Sur 11 beta in a language other than English. (63834383)

Location

Known Issues

Logging

New Features

  • New APIs are available for using os_log from Swift as part of the os framework:

    • A new type Logger can be instantiated using a subsystem and category and provides methods for logging at different levels (debug(_:), error(_:), fault(_:)).

    • The Logger APIs support specifying most formatting and privacy options supported by legacy os_log APIs.

    • The new APIs provide significant performance improvements over the legacy APIs.

    • You can now pass Swift string interpolation to the os_log function.

    Note: The new APIs can’t be back deployed; however, the existing os_log API remains available for back deployment. (22539144)

Mac Catalyst

Known Issues

  • Content Extensions require a temporary workaround. (57442394)

    Workaround: Add the following key/value pair to the NSExtension dictionary in the Info.plist: "NSExtensionContainingViewControllerClass" = "_UNNotificationContentExtensionViewController".

  • The new PHPickerViewController API currently produces unexpected results. (63631906)

Messages

Known Issues

  • If Messages is launched immediately after logging into iCloud, a login window might be displayed unexpectedly. (56309057)

    Workaround: Relaunch Messages after a few minutes or try restarting your Mac.

  • You might be unable to type in the photo picker search field when attaching a photo. (60011306)

    Workaround: Click the search field, press the tab key, then click the search field again.

  • You might receive an alert that indicates the maximum number of pinned conversations has been reached. (62919406)

    Workaround: Pin the conversation using drag and drop instead of using a swipe action or quick action with Haptic Touch.

  • Keyboard navigation to move focus between controls isn’t currently available. (63987810)

  • Messages Preferences are inaccessible until at least one message has been sent or received. (64122975)

  • Autocomplete fields and conversation titles aren’t visible while Messages is in full-screen mode. (64134303)

  • Message outlines might be missing when printing or exporting a conversation as a PDF. (64181169)

  • The first and last name fields in Messages Preferences might be misaligned. (64346872)

    Workaround: Set up your name in Messages Preferences by following the placeholder text then close and reopen Messages Preferences.

Metal

Known Issues

  • The logs property isn’t currently available from Swift while using Shader Validation. (64055248)

Migration Assistant

Known Issues

  • You might need to reset the password for a Standard account after migration, if the previous password doesn’t work. (63878129)

    Workaround: Log into an Admin account and change the Standard account’s password in the Users & Groups system preference.

Motion

Known Issues

  • Many elements of the user interface are currently missing when running Motion on macOS Big Sur 11 beta. (62531765)

Music

Known Issues

  • Music might quit unexpectedly while using the search field. (64183834)

Networking

New Features

  • Experimental HTTP/3 support can be enabled in Safari via Experimental Features in the Developer menu, and enabled system-wide using the Terminal command defaults write -g CFNetworkHTTP3Override -int 3. (62969220)

Known Issues

  • HTTP/3 Draft 29 isn’t yet supported. (63524866)

Phone and FaceTime

Known Issues

  • Regular and emergency Wi-Fi calling using iPadOS 14 beta, macOS Big Sur 11 beta, and watchOS 7 beta isn’t currently available for T-Mobile USA customers. (63078572)

Quartz

Known Issues

  • Importing Quartz or PDFKit frameworks in the macOS SDK might result in an errors such as “Umbrella for module ‘Quartz.PDFKit’ already covers this directory”. (63886438)

Safari and Webkit

New Features

  • Support for Web Extensions is now available. Existing Chrome and Firefox extensions can be converted for Safari using xcrun safari-web-extension-converter and distributed through the App Store for use in Safari 14. (55707949)

  • Webpage Translation is now available in the U.S. and Canada. Supported languages include English, Spanish, Simplified Chinese, French, German, Russian, and Brazilian Portuguese. Safari will automatically detect if translation is available based on your Preferred Languages list. (64437861)

Known Issues

  • Safari might quit unexpectedly when opening the Start Page if Frequently Visited Sites are visible as thumbnails. (63945984)

    Workaround: Make the window wider, hide the sidebar, or Control-click on Frequently Visited Sites and choose View as Icons.

Security

New Features

  • macOS Big Sur 11 beta improves system security by requiring an administrator password when a certificate trust settings change is made in the admin trust domain. Running as the root user alone is no longer sufficient to modify certificate trust. User trust domain settings continue to require confirmation by entering the password for the user’s account. This change may affect you if one of the following is true:

    • You have written scripts which call /usr/bin/security add-trusted-cert -d ... as root.

    • Your process runs as root and calls the SecTrustSettingsSetTrustSettings function to trust a certificate.

  • Workflows that add trust settings in the admin trust domain, such as for an enterprise root certificate, may require modification if the user can’t authenticate as an administrator at the time settings are changed. (21855995)

    Workaround: Use Apple Configurator 2 to create and install a configuration profile containing your root certificate.

Spotlight

Known Issues

  • When quickly typing a search query in Spotlight, the result from a previous search might appear, then pressing return may create a wrong launch shortcut for subsequent queries. (64428836)

    Workaround: Type your query and click the desired result from the list that appears.

  • If you can’t find an application using Spotlight, launch the application at least once using Finder. (64463806)

SwiftUI

Known Issues

  • Disclosure groups in Forms might produce unexpected results. (64079102)

  • Nested disclosure groups generated by OutlineGroup might produce unexpected results. (64097731)

  • The SceneStorage property wrapper isn’t yet supported. (64414712)

  • A label used with a symbol image might appear misaligned. (60193698)

SystemExtensions

Known Issues

  • Driver extensions might not launch on-demand after installation. (51229724)

    Workaround: Disable System Integrity Protection, then launch Terminal and execute the following command before approving the newly installed driver: sudo touch /Library/DriverExtensions.

Touch ID

Known Issues

  • Touch ID might become unexpectedly disabled on Macs with a T2 Security Chip after installing multiple operating systems. (62608379)

    Workaround: Reset the SMC of your Mac.

Virtualization

New Features

Deprecations

Vision

Known Issues

Deprecations

Xcode Previews

Resolved Issues

  • Rebuilding against the iOS 14, macOS 11, watchOS 7, and tvOS 14 SDKs changes uses of GeometryReader to reliably top-leading align the views inside the GeometryReader. This was the previous behavior, except when it wasn’t possible to detect a single static view inside the GeometryReader. (59722992) (FB7597816)

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
Topic Tags
itsage
(@itsage)
Illustrious Member Admin
Joined: 4 years ago
 

@mac_editor, It really is no longer Mac OS X! Here's the terms for the Developer Transition Kit - Mac mini. I'm ready to do a teardown and see what other changes Apple did besides the CPU.

 

external graphics card builds
best laptops for external GPU
eGPU enclosure buyer's guide

 
2013 Mac Pro (FP D500 x2) [3rd,12C,E] + RX 5700 XT @ 16Gbps-TB2>TB3 (Mantiz Saturn Pro) + macOS 11 [build link]  


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 4 years ago
 

@itsage, indeed! While it had its ups and downs, macOS 10 was a phenomenal journey - especially for me.

 

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ikir and joysthokkins liked
ReplyQuote
mysterylake
(@mysterylake)
Active Member
Joined: 4 months ago
 

@mac_editor

Watching the keynote, I didn't catch how Bootcamp is going to work on the new ARM machines (or if it works at all!). That makes me wonder how Mac users like myself are going to play Windows games. Perhaps eGPU support in VMware or Parallels would be the way to go?

 

 

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 4 years ago
 

@mysterylake, My only guess -> if Apple has implemented proper virtualization advancements (which they claimed), they might (have a feeling they will) forego Bootcamp entirely.

 

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


itsage liked
ReplyQuote
Roedi78
(@roedi78)
Trusted Member
Joined: 2 years ago
 

@mysterylake, had nearly the same thoughts. I think BootCamp (resp. the way of running Windows natively on a Mac hardware) is gone. 🙁 

I read somewhere these days that only 2% of MacOS users have installed a BootCamp partition. That's incredible less... ?! if that's true, I think Apple will just kick these.

Perhaps lets hope that they will allow installing ARM version of Windows 10 somehow, but afaik that's only available for 32 Bit apps. So no chance for running most modern game titles... 🙁

 

This post was modified 3 months ago

MacBook Pro 15" Late-2016 w/TB 16GB with RP460 4GB
 macOS Catalina 10.15.6 w/Win10 (2004) BootCamp
 AORUS RTX 2080 Ti Gaming Box 11GB


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 4 years ago
 

@roedi78, well guess what - https://docs.microsoft.com/en-us/windows/uwp/porting/apps-on-arm

Windows 10 does support ARM64 - very recently added. Does that mean bootcamp support remains? Idk as not sure how that would impact the apps users want to run on Windows ARM.

 

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
Roedi78
(@roedi78)
Trusted Member
Joined: 2 years ago
 

@mac_editor, already know that article. ".....Windows 10 on ARM supports x86, ARM32, and ARM64 UWP apps from Store on ARM64 devices...."

I understand it that way: You can run x86 (=32bit) apps, apps compiled for ARM32 and ARM64 and ARM64 UWP apps - and only apps from special (windows) store?!

So no support for native x64 apps... or did I miss something?

 

This post was modified 3 months ago

MacBook Pro 15" Late-2016 w/TB 16GB with RP460 4GB
 macOS Catalina 10.15.6 w/Win10 (2004) BootCamp
 AORUS RTX 2080 Ti Gaming Box 11GB


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 4 years ago
 

@roedi78, From that article:

If you only submit the x86 version of your app, the OS will install that version and run it under emulation.

Which I assumed they would do for x64 too. If not, well sucks for bootcamp users.

Update: Ah no it's not (you're right) -

Note that 64-bit x64 Win32 apps are not supported, but the vast majority of apps have x86 versions available. When given the choice of app architecture, just choose the 32-bit x86 version to run the app on a Windows 10 on ARM PC.

 

purge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
mysterylake
(@mysterylake)
Active Member
Joined: 4 months ago
 

@mac_editor

One way I see out of this would be if Apple's new computers support more powerful dGPUs, which we could then use with the improved virtualization software to run Windows apps.

 

Imagine a MacBook Pro with a dGPU more powerful than a mobile RTX2080ti... the days of wimpy AMD dGPUs would be behind us!

 

One can always dream..

 

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
 of  7