macOS 11 Big Sur on Unsupported Macs Thread

[jhowarth]

Hello, few notes about BigSur beta 3 now the BaseSystem.dmg is 884 MB (beta 2 was 740 MB), also from single user mode they introduced two new commands to easily mount the Data and Preboot Volume (both Volumes writable from single user mode even with a sealed system snapshot booting):

mount -P 1
mount -P 2
mount -vat nonfs

thanks to the @ASentientBot "apfs_systemsnapshot method", I have disabled on BigSur beta 3 snapshot booting directly from BigSur (without its Recovery), here are the steps, the two requirements are from a macOS Recovery or terminal recovery:

nvram boot-args="-no_compat_check"
csrutil disable

then from BigSur normal booting, open terminal and follow these steps:

sudo mkdir ~/Snapshot/

(this makes an empty folder mount point on your home folder so copy exactly as written)

mount

(on the first output line you can notice a diskXsYsZ you have to consider only diskXsY)

sudo mount -o nobrowse -t apfs /dev/diskXsY ~/Snapshot/

tmutil listlocalsnapshots ~/Snapshot/

(this show eventually the snapshots in form of "com.apple-UUID" rather than date time)

sudo mount -uw ~/Snapshot/

(this makes writable the mount point)

cd /S*/L*/File*/apfs*/C*/R*/

sudo ./apfs_systemsnapshot -v ~/Snapshot/ -r ""

(credit to ASentientBot for the apfs_systemsnapshot that tags an empty string to disable snapshot)

if for some reason using this posix path ~/Snapshot/ won't allow to tag the snapshot, then use instead /Users/yourusername/Snapshot/

if after those commands you get this message:
Attempting tagging of snapshot on volume: /Users/yourusername/Snapshot

then after reboot you can use "sudo mount -uw /" .

This isn't working on a supported machine with csr disabled. I get the following...

% mount
/dev/disk3s5s1 on / (apfs, sealed, local, read-only, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk3s4 on /System/Volumes/VM (apfs, local, noexec, journaled, nobrowse)
/dev/disk3s2 on /System/Volumes/Preboot (apfs, local, journaled, nobrowse)
/dev/disk3s6 on /System/Volumes/Update (apfs, local, journaled, nobrowse)
/dev/disk3s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
/dev/disk1s1 on /Volumes/Macintosh HD - Data (apfs, local, journaled, nobrowse)
/dev/disk1s5 on /Volumes/Macintosh HD (apfs, local, read-only, journaled)
map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
/dev/disk4s2 on /Volumes/Untitled (hfs, local, nodev, nosuid, journaled, noowners)
% sudo mkdir ~/Snapshot/
% sudo mount -o nobrowse -t apfs /dev/disk3s5 ~/Snapshot/
% tmutil listlocalsnapshots ~/Snapshot/
Snapshots for volume group containing disk /Users/howarth/Snapshot/:
com.apple.os.update-72524D5EC190DF0AE2C4679432BB338E6FE880E04E512EE7E9E225E3EFD5E098
% sudo mount -uw ~/Snapshot/
mount: unknown special file or file system /Users/howarth/Snapshot/.
% sudo mount -uw /Users/howarth/Snapshot/
mount: unknown special file or file system /Users/howarth/Snapshot/.
% sudo mount -uw /Volumes/BigSur/Users/howarth/Snapshot/
mount: unknown special file or file system /Volumes/BigSur/Users/howarth/Snapshot/.

Any idea what is going wrong here? This is for a normal boot (actually the first boot at the end of the installation of Big Sur beta3).

 

[Barry K. Nathan]

I'm still catching up on the forum posts (I probably have another 2 pages or so to read), but I just wanted to mention that I've now released v0.0.15 of my patcher. Quoting from the release notes:

The important change in this release is that patch-kexts.sh now checks for errors after each kmutil invocation. If anything goes wrong with kmutil, this makes the resulting output far easier to read for troubleshooting purposes. I have not yet tested this release against Big Sur developer beta 3, but this bug fix will make it easier for me to properly test with beta 3.

There's also a new feature: If you have renamed the installer USB or it is otherwise not at the usual location in /Volumes for some reason, you can specify the path to the installer USB on the command line for micropatcher.sh or unpatch.sh. (You can add that path to the command line by dragging and dropping the installer USB from Finder into Terminal. You must drag the installer USB from the Computer view in the Finder -- dragging and dropping the installer USB from the Finder sidebar will not work, nor will dragging and dropping the Install application that is on the USB drive.)

(I realize that very few people are going to need the new feature that I added to micropatcher.sh/unpatch.sh, but I ended up needing it myself, and it was faster for me to just implement the feature than to work around its absence.)

I'll try to test against beta 3 later tonight.

GitHub - barrykn/big-sur-micropatcher: A primitive USB patcher for installing macOS Big Sur on unsupported Macs

A primitive USB patcher for installing macOS Big Sur on unsupported Macs - barrykn/big-sur-micropatcher

github.com

[automerge]1595555385[/automerge]

Still no wifi or ethernet working after reinstall BS Beta 3 I think the volume has to be unsealed for BarryKn's patch-kexts.sh to work as I either get /Volumes\ is a directory or file or directory not found. And I noticed if you open the terminal type sudo -s then hit enter then type sudo mount -uw /; killall Finder does work without error 66 but because the volume is sealed and read-only you can't replace the IO80211Family.kext

The script is failing very early for you for some reason. It's not even getting far enough for sealed vs unsealed volumes to possibly be an issue. (For what it's worth, the script has worked on sealed volumes for me when I've tested that.)

If I knew exactly what you were entering on the command line, I might be able to point out what's wrong -- but if you consider the volume name to be private then don't worry, I understand. The ideal solution would be to enhance the script so that it can find the volume automatically, and I intend to do that pretty soon, but I'm not sure whether I can do it in the next release or if it's going to be a few releases out.

 

[Barry K. Nathan]

This isn't working on a supported machine with csr disabled. I get the following...

% mount
/dev/disk3s5s1 on / (apfs, sealed, local, read-only, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk3s4 on /System/Volumes/VM (apfs, local, noexec, journaled, nobrowse)
/dev/disk3s2 on /System/Volumes/Preboot (apfs, local, journaled, nobrowse)
/dev/disk3s6 on /System/Volumes/Update (apfs, local, journaled, nobrowse)
/dev/disk3s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
/dev/disk1s1 on /Volumes/Macintosh HD - Data (apfs, local, journaled, nobrowse)
/dev/disk1s5 on /Volumes/Macintosh HD (apfs, local, read-only, journaled)
map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
/dev/disk4s2 on /Volumes/Untitled (hfs, local, nodev, nosuid, journaled, noowners)
% sudo mkdir ~/Snapshot/
% sudo mount -o nobrowse -t apfs /dev/disk3s5 ~/Snapshot/
% tmutil listlocalsnapshots ~/Snapshot/
Snapshots for volume group containing disk /Users/howarth/Snapshot/:
com.apple.os.update-72524D5EC190DF0AE2C4679432BB338E6FE880E04E512EE7E9E225E3EFD5E098
% sudo mount -uw ~/Snapshot/
mount: unknown special file or file system /Users/howarth/Snapshot/.
% sudo mount -uw /Users/howarth/Snapshot/
mount: unknown special file or file system /Users/howarth/Snapshot/.
% sudo mount -uw /Volumes/BigSur/Users/howarth/Snapshot/
mount: unknown special file or file system /Volumes/BigSur/Users/howarth/Snapshot/.

Any idea what is going wrong here? This is for a normal boot (actually the first boot at the end of the installation of Big Sur beta3).

I think it's the trailing slash after "Snapshot". Try ~/Snapshot instead of ~/Snapshot/ and see what errors (if any) you get then.

 

[eikic1]

MacPro 5,1 - All Working Minus Wifi View attachment 926581

how step bro?
i have macPro 2012 (5,1)
or anyone who can give me step by step for upgrade macPro 5,1 (2012) to MacOS 11.
.
..
.
.
And I try to iMac 2009 but showing error, how to fix
thanks

 

[jhowarth]

I think it's the trailing slash after "Snapshot". Try ~/Snapshot instead of ~/Snapshot/ and see what errors (if any) you get then.

Okay...

sudo mount -uw ~/Snapshot

works and I now get...

% cd /S*/L*/File*/apfs*/C*/R*/
% sudo ./apfs_systemsnapshot -v ~/Snapshot/ -r ""
Attempting tagging of snapshot on volume: /Users/howarth/Snapshot/

but when I reboot, I still get a failure for

% sudo mount -uw /
mount_apfs: volume could not be mounted: Premission denied
mount: / failed with 66

Executing 'mount' also still shows...

/dev/disk3s5s1 on / (apfs, sealed, local, read-only, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk3s4 on /System/Volumes/VM (apfs, local, noexec, journaled, nobrowse)
/dev/disk3s2 on /System/Volumes/Preboot (apfs, local, journaled, nobrowse)
/dev/disk3s6 on /System/Volumes/Update (apfs, local, journaled, nobrowse)
/dev/disk3s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
/dev/disk1s1 on /Volumes/Macintosh HD - Data (apfs, local, journaled, nobrowse)
/dev/disk1s5 on /Volumes/Macintosh HD (apfs, local, read-only, journaled)
map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
/dev/disk4s2 on /Volumes/Untitled (hfs, local, nodev, nosuid, journaled, noowners)

Shouldn't the sealed snapshot be gone after the reboot?

Also does 'csrutil authenticated-root disable' also have to be set? Also, is it possible that running under Big Sur saavy bootrom firmware might be blocking this?

 

[TimothyR734]

I'm still catching up on the forum posts (I probably have another 2 pages or so to read), but I just wanted to mention that I've now released v0.0.15 of my patcher. Quoting from the release notes:



(I realize that very few people are going to need the new feature that I added to micropatcher.sh/unpatch.sh, but I ended up needing it myself, and it was faster for me to just implement the feature than to work around its absence.)

I'll try to test against beta 3 later tonight.

GitHub - barrykn/big-sur-micropatcher: A primitive USB patcher for installing macOS Big Sur on unsupported Macs

A primitive USB patcher for installing macOS Big Sur on unsupported Macs - barrykn/big-sur-micropatcher

github.com

[automerge]1595555385[/automerge]

The script is failing very early for you for some reason. It's not even getting far enough for sealed vs unsealed volumes to possibly be an issue. (For what it's worth, the script has worked on sealed volumes for me when I've tested that.)

If I knew exactly what you were entering on the command line, I might be able to point out what's wrong -- but if you consider the volume name to be private then don't worry, I understand. The ideal solution would be to enhance the script so that it can find the volume automatically, and I intend to do that pretty soon, but I'm not sure whether I can do it in the next release or if it's going to be a few releases out.

I used the name like you have in the instructions to see if that would be easy enough but I would either get /Volume\ is a directory or when I tried again I would get file or directory not found but I did get my ethernet working I called my provider and had them remotely reset my network and router so now ethernet works in Catalina and Big Sur
[automerge]1595564841[/automerge]

Okay...

sudo mount -uw ~/Snapshot

works and I now get...

% cd /S*/L*/File*/apfs*/C*/R*/
% sudo ./apfs_systemsnapshot -v ~/Snapshot/ -r ""
Attempting tagging of snapshot on volume: /Users/howarth/Snapshot/

but when I reboot, I still get a failure for

% sudo mount -uw /
mount_apfs: volume could not be mounted: Premission denied
mount: / failed with 66

Executing 'mount' also still shows...

/dev/disk3s5s1 on / (apfs, sealed, local, read-only, journaled)
devfs on /dev (devfs, local, nobrowse)
/dev/disk3s4 on /System/Volumes/VM (apfs, local, noexec, journaled, nobrowse)
/dev/disk3s2 on /System/Volumes/Preboot (apfs, local, journaled, nobrowse)
/dev/disk3s6 on /System/Volumes/Update (apfs, local, journaled, nobrowse)
/dev/disk3s1 on /System/Volumes/Data (apfs, local, journaled, nobrowse)
/dev/disk1s1 on /Volumes/Macintosh HD - Data (apfs, local, journaled, nobrowse)
/dev/disk1s5 on /Volumes/Macintosh HD (apfs, local, read-only, journaled)
map auto_home on /System/Volumes/Data/home (autofs, automounted, nobrowse)
/dev/disk4s2 on /Volumes/Untitled (hfs, local, nodev, nosuid, journaled, noowners)

Shouldn't the sealed snapshot be gone after the reboot?

Also does 'csrutil authenticated-root disable' also have to be set? Also, is it possible that running under Big Sur saavy bootrom firmware might be blocking this?

I have noticed if I have SIP disabled and enter sudo-s in the terminal followed by sudo mount -uw / I get the failed with 66. But if I disable SIP and Authenticated-Root and try sudo -s in the Terminal, followed by sudo mount -uw it works

 

[TimothyR734]

[automerge]1595566355[/automerge]
After getting Ethernet working I applied jackluke's ivybridgeprelinkkernel patch wifi is working thank you jackluke awesome

 

[RogueB]

Successful Install of Big Sur Beta 3 on iMac 13,2 (late 2012 model)

I used parotgeek's instructions and his "tool2" to create a bootable USB thumb drive installer (for Big Sur Beta3).

Installation of Big Sur Beta3, over an existing Beta 2 installation, went without problems.
Jackluke's latest Ivy_Bridge prelinkedkernel allowed full WiFi functionality.

In order to access WiFi network, I had to change my router setting to make network "visible".

Thereafter, I had to logout (not reboot) from Big Sur, and then log back into Big Sur, for WiFi network to become accessible from the computer. Note, that once logged into the WiFi network, I set the network control panel functions to "remember joined network" and "ask to join new networks". I logged back into the router and set "wireless network" to invisible again; the WiFi remained functional after toggle to "invisible".

A huge "thank you" to the principals, and the many other individuals who contributed to this thread

Hope this may be of help.

 

[TimothyR734]

It didn't take me long to mess up my wifi as I started getting beachballs and lockups so I tried reinstalling Big Sur with the same usb Big Sur usb installer but go error preparing the installation message so I guess Apple had made it so you can't reinstall with the same usb and forced to do a clean install

 

[Barry K. Nathan]

It didn't take me long to mess up my wifi as I started getting beachballs and lockups so I tried reinstalling Big Sur with the same usb Big Sur usb installer but go error preparing the installation message so I guess Apple had made it so you can't reinstall with the same usb and forced to do a clean install

No, a reinstall with the same USB should work, a clean reinstall shouldn't be necessary. I've tested it. (However, I just realized, I haven't tested it on an installation that's been changed over to use prelinkedkernels. Edit: To be clear, I wouldn't actually expect that to break things -- it has to be able to upgrade from older macOS releases that use prelinkedkernels, after all -- it's just that it's something I haven't actually tested, and I just realized that as I was writing this post.)

 

[jackluke]

Shouldn't the sealed snapshot be gone after the reboot?

Also does 'csrutil authenticated-root disable' also have to be set? Also, is it possible that running under Big Sur saavy bootrom firmware might be blocking this?

I disabled only the standard SIP , I done that directly from an unsupported Mac, but during the stage2 installer on the "BigSur Data Volume"/macOS Install Data/ I replaced the attached file (@ResEdit_ResEdit noticed this file).

But that file only produced a writable BigSur System from Catalina, from BigSur itself I still had a snapshot booting (without "sudo mount -uw /"), then I removed the snapshot in that way, maybe before that method, make first a new snapshot with bless command, then reboot and retry.

Since for legacy USB Mac can't use the micropatcher (because of BigSur Recovery without responsive USB input devices) there is also another way to disable the snapshot booting and it is, right after stage2 installation "29 minutes remaining", hold alt-option key , and instead of select the "macOS Installer" (stage3 installer that seal the volume and tags a bootable snapshot of it), just select the "BigSur Data" at apple startup manager, if boot to the desktop then delete any "macOS Install Data" folder on the "BigSur Data Volume", and you can directly use "sudo mount -uw /".

 

[koyado]

Hi, how update catalina to Big Sur beta 3, in MBP 5,5 mid 2009??

 

[jackluke]

Hi @jackluke I have executed the command, but it doesn't patch my Preboot (mounted as requested) and I think that the correct one is disk2s1 (internal SSD) not the bigger Preboot. Where I'm wrong? Thank you!

From the pictures from Catalina terminal:

diskutil unmount Preboot
diskutil mount disk2s1

then relaunch the BigSur beta3 Penryn prelinkedkernel fix .

 

[LuisN]

I'm still catching up on the forum posts (I probably have another 2 pages or so to read), but I just wanted to mention that I've now released v0.0.15 of my patcher. Quoting from the release notes:



(I realize that very few people are going to need the new feature that I added to micropatcher.sh/unpatch.sh, but I ended up needing it myself, and it was faster for me to just implement the feature than to work around its absence.)

I'll try to test against beta 3 later tonight.

GitHub - barrykn/big-sur-micropatcher: A primitive USB patcher for installing macOS Big Sur on unsupported Macs

A primitive USB patcher for installing macOS Big Sur on unsupported Macs - barrykn/big-sur-micropatcher

github.com

[automerge]1595555385[/automerge]

The script is failing very early for you for some reason. It's not even getting far enough for sealed vs unsealed volumes to possibly be an issue. (For what it's worth, the script has worked on sealed volumes for me when I've tested that.)

If I knew exactly what you were entering on the command line, I might be able to point out what's wrong -- but if you consider the volume name to be private then don't worry, I understand. The ideal solution would be to enhance the script so that it can find the volume automatically, and I intend to do that pretty soon, but I'm not sure whether I can do it in the next release or if it's going to be a few releases out.

v0.0.15
Fresh install replacing beta2 in mbp 13" mid 2012 and restoring from Time Machine backup: SUCCESS
Install over beta2, (update), in mbp 15" retina 2012: SUCCESS

 

[jhowarth]

I used the name like you have in the instructions to see if that would be easy enough but I would either get /Volume\ is a directory or when I tried again I would get file or directory not found but I did get my ethernet working I called my provider and had them remotely reset my network and router so now ethernet works in Catalina and Big Sur
[automerge]1595564841[/automerge]

I have noticed if I have SIP disabled and enter sudo-s in the terminal followed by sudo mount -uw / I get the failed with 66. But if I disable SIP and Authenticated-Root and try sudo -s in the Terminal, followed by sudo mount -uw it works

When you are executing 'sudo -s; sudo mount -uw /' successfully, is 'mount' showing a seal in place? I don't understand how this tagging is working if the seal is never actually removed.

Update: As usual 'sudo -s; sudo mount -uw /' still produces the 66 error despite tagging the snapshot for removal prior to the reboot. It would be nice if ASentientBot would pop back onto this mailing list and carefully explain his exact configuration that these methods are being tested on. I have yet to get any of his methods to work on a supported or unsupported machine.

 

[Barry K. Nathan]

I've just released v0.0.16 of my patcher. There's only one code change, and it makes no difference if you don't use verbose boot. So, for most users, the updates to the README (mainly to note that I've tested it with beta 3) are probably the most important part of this release.

It's a tiny release, but I have riskier changes planned for the next couple of releases, and I didn't want those to hold up the README update. Also, I've tested this release pretty thoroughly, so if things go awry with v0.0.17 or v0.0.18 or whatever, I'll be able to point to this as an older stable release for people to try.

GitHub - barrykn/big-sur-micropatcher: A primitive USB patcher for installing macOS Big Sur on unsupported Macs

A primitive USB patcher for installing macOS Big Sur on unsupported Macs - barrykn/big-sur-micropatcher

github.com

 

[Alex-Microsmeta]

From the pictures from Catalina terminal:

diskutil unmount Preboot
diskutil mount disk2s1

then relaunch the BigSur beta3 Penryn prelinkedkernel fix .

Done, from Catalina doesn't work, but from BigSur Beta 1 YES ? Wifi, USB, Audio Bluetooth, webcam, menu icons OK on Beta 3. Mouse seems faster. Thank you!

 

[Barry K. Nathan]

Just a heads up for anyone who cares about this:

I just tried using Japanese input with Big Sur beta 3 on my MacBook6,1 and it has the same crash problem as on Catalina. After I moved the USB SSD back over to my MacBookPro8,1, Japanese input started working. (I didn't get a chance to try with previous Big Sur betas.) And, as with Catalina, it's an illegal instruction crash.

(For anyone who's not familiar with the Catalina Japanese input issue, the Japanese IME on Catalina blindly assumes that AVX1 instructions are available, so it crashes on any pre-Sandy Bridge CPU -- anything before the 2013 Mac Pro or 2011 models of other Macs. I don't know if anyone ever managed to fix the issue on Catalina.)

Maybe someone else tried it on Big Sur earlier, but if so, I missed it.

 

[GermanyUSER02]

Hello Folks.

in the first, ... sorry (i cam from Germany, and yes, i know my Englisch is a little rusty).

I came here over Siri-Sarch, becaus i interest me, wath is with my old Mac(Books) to get a upgrade to "BS".

My first Sarch bring me to Dosdude.com (wich produckt i allredy use --> Catalina-Patch - thanks for this), but - there was (on this time ?) nothing to find ;-)

As i read here some Lines, i get a little angry ... why came some people here to force a result - or to cry and yelling "buhuu, Apple let me down (... with the -over 10 years old- computer ...)" ?

On my own House, we use 2 "Wihtebody A1342" 1 20" late 2008 IMac and a 24" early 2009 IMac ... all with the Catalina-Patch who i get form Dosdude ... - if there - a Way, that i cam kepp it, i am thankfull, if not .. than it is so ...

Anyway, we can use the Computer in every case the next 5 Year´s ... that makes (in Case i have to chance all 4 in one Time) max 80 Bugs to save the Month.

If there anyone who say "i cant" ... he/she can buy a newer one in the next Years, patch this and save Mony for a newone ...

Tru, that we going to be forced to buy newer one, is ... "not nice" ... but, nothing is forever ... (and a old Computer have to change from Time to Time.

....So mutch Words ... what i have to Say --> tihs Change cam not from jet-to-now ... we have Time to do that.

And, is there a Way, we can keep our Computers, these Community will find a Way (and if this over Tools for a not longer suported Catalina ... Like ThenfourFox or something ... enyway ... a little Time is still there to find a Way ...

best Regards

 

[GDMSR]

My first Sarch bring me to Dosdude.com (wich produckt i allredy use --> Catalina-Patch - thanks for this), but - there was (on this time ?) nothing to find ;-)

Dosdude1 normally releases his patcher software when there is a public release of the macOS. In the case of Big Sur, this release has not yet occurred, and likely won't until the fall. Even then, since a lot appears to have changed since Catalina, there's no guarantee of a patcher... but here's hoping

 

[Bravo2zero]

Updated to Beta 3 today on a Mac mini 2012 without making a new partition etc... went as smooth as butter upgrade from beta 1.0 ( I didn't go beta 2 as my MacBook 2017 had lots off issues on that ).

basically made did this ,

I have a 2017 Mac so I grabbed the Beta 3 download off that to start with

macOS Big Sur Patcher Is No Longer Available

parrotgeek.com

made the USB stick only

booted to the USB

Terminal and typed csrutil disable - press return

in terminal again type csrutil authenticated-root disable - press return and close terminal but didn't reboot.

I then get back to the option screen and I chose upgrade/install and followed the few click screens followed by a 14 min to install boot screen.

after it had all done on final reboot it took AGES to come back on and I fair gave up and hard powered the Mac down ( holding power down for 5 seconds )

The Mac then booted as normal and Beta 3 was installed as I noticed the red Music tab at the bottom and all my software was still there.

 

[jackluke]

@ASentientBot, first thanks again for all yours BigSur patches till now (in particular HaxLib.dylib , apfs_systemsnapshot and patched boot.efi), I understand that achieving on BigSur video acceleration for non-Metal GPU is near impossible, but if you already achieved the correct display and brightness, could you share how to get "Nvidia GeForce Tesla" video framebuffer loaded ?

Maybe you binary patched some IOGraphicsFamily or IONDRVSupport ?

I made all known tests using NDRVShim but can't fix that symbol for NVDAResmanTesla .

 

[jhowarth]

@ASentientBot, first thanks again for all yours BigSur patches till now (in particular HaxLib.dylib , apfs_systemsnapshot and patched boot.efi), I understand that achieving on BigSur video acceleration for non-Metal GPU is near impossible, but if you already achieved the correct display and brightness, could you share how to get "Nvidia GeForce Tesla" video framebuffer loaded ?

Maybe you binary patched some IOGraphicsFamily or IONDRVSupport ?

I made all known tests using NDRVShim but can't fix that symbol for NVDAResmanTesla .

Have you actually gotten the proposed apfs_systemsnapshot method to work? It seems like yet another dead end here. Also, is it possible to use Hax3 on a supported machine in order to disable sealing? That is seeming like the most likely approach but I am unclear how to use it so that the installer only avoids sealing and leaves the rest of the installation as normal (for a supported machine).

Where can Hax3.dylib be downloaded from? The tool on https://parrotgeek.com/bigsur/ seems to have Hax.dylib rather than Hax3.dylib.

 

[jackluke]

Also, is it possible to use Hax3 on a supported machine in order to disable sealing?

Yes, but you need csrutil disable and nvram boot-args="-no_compat_check amfi_get_out_of_my_way=1" before using ASentientBot Hax3.app and you should copy the "Install macOS Big Sur Beta.app" (12,88 GB) to the Catalina Applications path.

 

[ASentientBot]

@ASentientBot, first thanks again for all yours BigSur patches till now (in particular HaxLib.dylib , apfs_systemsnapshot and patched boot.efi), I understand that achieving on BigSur video acceleration for non-Metal GPU is near impossible, but if you already achieved the correct display and brightness, could you share how to get "Nvidia GeForce Tesla" video framebuffer loaded ?

Maybe you binary patched some IOGraphicsFamily or IONDRVSupport ?

I made all known tests using NDRVShim but can't fix that symbol for NVDAResmanTesla .

I'd think you can just use NDRVShim, but here's the version I binary patched to work on Catalina without it, which should work on BS too. Hope that helps!

As for acceleration, it may be near-impossible but it's not 100% impossible. Certainly don't hold your breath, but I haven't given up on it yet.