macOS 11 Big Sur on Unsupported Macs Thread

[jackluke]

Also, when moving a perfectly working BS beta 4 install over to the MP3,1, it seems to crash at a very similar point with that verbose dump as well.

If for moving you meant plug directly a disk with BigSur installed to internal SATA or to an external USB then:

from a macOS Recovery or Installer (El Capitan for example) set csrutil disable directly on your target machine, then from another macOS for booting an already installed BigSur try this fix: BigSur Penryn beta3 prelinkedkernel fix.command.zip

in case not worked, to remove the fix use this: BigSur generic BKE.command.zip

 

[GSXB]

Use Barry K. Nathan's method and just don't execute the scripts.

Tried that same result, constant bootloops. The installer will not complete ?

 

[darthgeekonius]

Unfortunately, you will have to boot into the usb. There really isn't much of a workaround.

I'm lazy... I'll probably just wait for a patcher like dosdude1 where it'll patch and install from the desktop. However, if this USB method is flawless save reboot from USB, then I'll probably do it. I shouldn't need the bootscreen for that though, I should be able to tell MacOS to boot from USB and go from there I hope...

 

[Pachnes]

Pubilc Beta: Firefox 79 Tabs do crash very often, even on a supported MacMini Late 2018 with i7 6 core CPU. So use Safari to browse the Internet.

Did someone try the latest Carbon Copy Cloner? I think, CCC can not read the System Container.

 

[Larsvonhier]

If for moving you meant plug directly a disk with BigSur installed to internal SATA or to an external USB then:

from a macOS Recovery or Installer (El Capitan for example) set csrutil disable directly on your target machine, then from another macOS for booting an already installed BigSur try this fix: BigSur Penryn beta3 prelinkedkernel fix.command.zip

in case not worked, to remove the fix use this: BigSur generic BKE.command.zip

Thanks, yes, I meant attaching a drive with the installation to internal SATA or as external USB shuttle.
As the processors are Xeon 56xx, I suspect that Penryn kernel patches might not be needed - especially as the source was a C2D machine...
But perhaps I can try the BKE remove tool/script to get it working instead.

 

[Barry K. Nathan]

I just released v0.1.0 of the micropatcher. I'll just quote the release notes below.

I've spent more time working on it in the last few days than I had intended, so as I turn my attention to other things, I might fall behind on forum posts and not catch up again until maybe Friday or Saturday.

So, so many improvements. I could justify the version number bump to v0.1 on many different grounds, but the most succinct is that this is the first version of my patcher that is stable enough for me to consider using my MacBookPro8,1 as my daily driver. Other users will find that this is the first version with stable WiFi, or the first version that is usable or stable for them for a variety of other reasons.

Any user who has had WiFi problems, or who has had installation attempts fail with mystery errors, or who has tried to boot the patched USB only to have it fail immediately with a prohibited/no-entry sign, or who has had kernel panics on a 2011 Mac, should try again with this release.

In more detail:

• The highvoltage12v WiFi patch has been updated. Stability is massively improved. If your Mac has not been upgraded to an 802.11ac WiFi card, then you should download the new patcher release, run unpatch.sh followed by micropatcher.sh on your USB stick, and repeat step 9 of the instructions; this will apply the WiFi patch update.
• There is a new shell script, remount-sysvol.sh, to allow the System volume to be easily modified, for tasks like installing your own kexts. There is a new section in the README which explains this process in more detail. There is some room for improvement -- for instance, there is at least one minor bug that needs fixing, and the rebuild-kc.sh helper script handles kernel/kext collections but not prelinkedkernels yet. However, for users who want to install their own kexts under Big Sur just as they could under previous releases, hopefully this will be helpful. (For users who have been seeking a solution to mount error 66, this might be it.)
• Under certain specific circumstances, previously the patcher could completely fail to apply any patches to the installer USB when running under macOS Catalina. The patcher now reliably detects these conditions and attemps to correct them. (Ultimately the user must grant Terminal permission, but the patcher no longer silently malfunctions and now forces macOS Catalina to ask the user for permission.) If your installer USB was immediately showing a prohibited/no-entry sign even though you used the patcher, you were almost certainly a victim of this bug, and you should try again with this release.
• I have forked Hax3, in order to disable the patch to the installer's disk space check (that particular patch was doing more harm than good) while still allowing the installer to be run with or without sealing. I have also provided a shell script that builds the Hax dylibs from source. (Two dylibs are compiled from one source code file by using two sets of compiler flags, which is unusual. Otherwise I would have used a Makefile instead of a shell script.)
• Some of the Intel HD 3000 graphics driver kexts, related to hardware-accelerated video decoding, have been removed. Accelerated video decoding wasn't working anyway, but these kexts were causing some kernel panics. The rest of the (unaccelerated) Intel HD 3000 framebuffer still works. Ironically, removing these kexts made Big Sur on my MacBookPro8,1 usable for rudimentary video editing using QuickTime Player.
• There is a new misc-scripts directory, for shell scripts that are not used by the patcher but which may be useful to some patcher users. In particular, kc-list-kext-paths.sh can list every kext inside a .kc file (either Xcode command line tools or binutils on Linux required).
• Some extraneous boot options have been removed from com.apple.Boot.plist. This may prevent kernel panics when booting the patched installer USB on some Macs.
• patch-kexts.sh has a small change in parameters for kmutil so it no longer shows "No variant specified, falling back to release". The message was harmless, but people often asked questions about it.
• various other minor bug fixes and documentation updates

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

 

[Barry K. Nathan]

DO you think Bir Sur shall be able to run on this hardware (of course, with the proper patches and such)?

Intel® Core™2 Duo Processor E8500 (6M Cache, 3.16 GHz, 1333 MHz FSB) Product Specifications

Intel® Core™2 Duo Processor E8500 (6M Cache, 3.16 GHz, 1333 MHz FSB) quick reference guide including specifications, features, pricing, compatibility, design documentation, ordering codes, spec codes and more.

ark.intel.com

I think so, if it's compatible with your motherboard. It's the correct generation of CPU to be compatible with Big Sur.

 

[EdGlassgow]

I just released v0.1.0 of the micropatcher. I'll just quote the release notes below.

I've spent more time working on it in the last few days than I had intended, so as I turn my attention to other things, I might fall behind on forum posts and not catch up again until maybe Friday or Saturday.

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

Awesome work Barry!

 

[nandor690]

Not sure if this is true but I guess that command is the same as resetting NVRAM thereby erasing setting made by the user, that would make the mac not to boot, good you found the fairly easy solution, redoing the set-vars.sh solves the problem.

Yes. Rerunning the set-vars.sh

once The drive is formatted and ready do you have to reboot from the usb and do you need to see the boot screen ie install original or flashed card? I still have my gt card I just hate the whole switching out gpu thing

not really. You can just pick the usb from the startup disk option in system preferences.

 

[nandor690]

DO you think Bir Sur shall be able to run on this hardware (of course, with the proper patches and such)?

Intel® Core™2 Duo Processor E8500 (6M Cache, 3.16 GHz, 1333 MHz FSB) Product Specifications

Intel® Core™2 Duo Processor E8500 (6M Cache, 3.16 GHz, 1333 MHz FSB) quick reference guide including specifications, features, pricing, compatibility, design documentation, ordering codes, spec codes and more.

ark.intel.com

Why kind of Mac are you upgrading?

 

[luccax]

ok once i change the wifi card in my early 2013 mbp what is the next step for public beta??

 

[Pachnes]

advice to non professionals: as firefox does close after about every second click on a supported machine (MacMini Late 2018), you should be patient. It is still very unstable. At least the developers of software for Mac need more time, to pass patches to their software. CCC does not work either.

Until now here the challenge is only, to install Big Sur on an unsopported machine and to boot it, not more. Software you use might (and will not) work, as you expect.

and as CCC does not work, you are not able to revert to an earlier Big Sur configuration.
so children: wait, it is to early to install Big Sur at your Rack, even dodsude not seen quite for a few days now, he is working on it. Aapple did try to give him some challenges. And I am sure, the difficulty is only, because Apple tried to stop dosdude. And maybe, with the "sealed" container they did make a big hurdle for dosdude.

to boot a system: ok, but work with it: that is the hurdle. dosdude: please do the miracle!

here on a MacMini Late 2018, Firefox does starve every second click. So be patient.

we will get Big Sur, but the heroes need time to find a solution (for a couple of Hardware devices) before they say: Try this and report

Am I the only follower here?

 

[GSXB]

I just released v0.1.0 of the micropatcher. I'll just quote the release notes below.

I've spent more time working on it in the last few days than I had intended, so as I turn my attention to other things, I might fall behind on forum posts and not catch up again until maybe Friday or Saturday.

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

still no joy with my Mac Pro 4.1/5.1, more of the same BOOTLOOPS
even with any nvram boot-args just BOOTLOOPS
I now think I'm resigned to Catalina " ANNOYED " !!!!!!!!!!!!!

 

[nandor690]

still no joy with my Mac Pro 4.1/5.1, more of the same BOOTLOOPS
even with any nvram boot-args just BOOTLOOPS
I now think I'm resigned to Catalina " ANNOYED " !!!!!!!!!!!!!

Damn man. That’s so weird.

 

[EdGlassgow]

still no joy with my Mac Pro 4.1/5.1, more of the same BOOTLOOPS
even with any nvram boot-args just BOOTLOOPS
I now think I'm resigned to Catalina " ANNOYED " !!!!!!!!!!!!!

Same here... Tried with Developer Beta 4 and Public Beta 1 and with 2 different "known good" usb sticks. Same bootloop at the same point in the installation process every time.

 

[nandor690]

Same here... Tried with Developer Beta 4 and Public Beta 1 and with 2 different "known good" usb sticks. Same bootloop at the same point in the installation process every time.

You have a 4,1 (5,1) as well?

 

[EdGlassgow]

You have a 4,1 (5,1) as well?

sorry, I should have said upfront that this wason a MacPro 5,1...

 

[nandor690]

sorry, I should have said upfront that this wason a MacPro 5,1...

Yea but I mean pretty much the same thing and same firmware. Iv had a few boot loops with mine but it always ends up finishing the install.
Mine is a single cpu Mac Pro

 

[Vyzantion]

Why kind of Mac are you upgrading?

Not a Mac. This machine used to be a Hackintosh running Catalina. Now it has Linux, because both Mojave and Catalina suddently stopped installing from USB. 2008-2009 ASUS motherboard.

 

[MacHacJac]

I'm lazy... I'll probably just wait for a patcher like dosdude1 where it'll patch and install from the desktop. However, if this USB method is flawless save reboot from USB, then I'll probably do it. I shouldn't need the bootscreen for that though, I should be able to tell MacOS to boot from USB and go from there I hope...

I'm creating an automated patcher right now, it should be ready in a week or two.

 

[MacHacJac]

UPDATE #2 on my patcher:
I have successfully created a patcher with a working usb installer recovery. Everything works PERFECTLY on a 2011 MBP, and I hope the same is the case for other Macs. My current project is to make variants of the kext patching for different Macs so that unneeded kexts won't be added to any Mac. I am also working on making a better UI and UX for the person downloading, similar to what dosdude1 has been doing. If anyone can give me any tips on patcher UI, it would be much appreciated. I can't give an ETA but I'm hoping that by August 15th it'll be ready.

 

[nandor690]

Not a Mac. This machine used to be a Hackintosh running Catalina. Now it has Linux, because both Mojave and Catalina suddently stopped installing from USB. 2008-2009 ASUS motherboard.

Ok never mind then. I was gonna say if your upgrading cpu on older Mac you also need to make sure the FSB on the ‘new’ cpu matching the one OEM one. But of course you don’t need to worry about that lol

 

[nandor690]

Tried that same result, constant bootloops. The installer will not complete ?

I’m gonna fresh install on my 2009 Mac Pro with the newest installer and see if I get any errors.
I wonder if the dual cpu is causing a weird problem for some reason. Although I don’t see why it would

 

[baronsekeber]

@jackluke it's normal this behaviour creating install media? Thank you!

sudo /Applications/Install\ macOS\ Big\ Sur\ Beta.app/Contents/Resources/createinstallmedia --volume /Volumes/Install\ macOS


objc[2406]: Class IASNightInstallSupport is implemented in both /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x1152abac0) and /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x102ab4080). One of the two will be used. Which one is undefined.


objc[2406]: Class IASSystemInformation is implemented in both /Applications/Install macOS Big Sur Beta.app/Contents/Frameworks/OSInstallerSetup.framework/Versions/A/Frameworks/IAESD.framework/Versions/A/Frameworks/IAInstallerUtilities.framework/Versions/A/IAInstallerUtilities (0x1152abbd8) and /System/Library/PrivateFrameworks/IASUtilities.framework/Versions/A/IASUtilities (0x102ab41c0). One of the two will be used. Which one is undefined.


Ready to start.


To continue we need to erase the volume at /Volumes/Install macOS.


If you wish to continue type (Y) then press return:

same, here.

i also would like to ask the same question.
every time i want to make the installer, always come that notice.

Its is normal? and are the installer is good to use?

 

[tankerthebub]

barrykn patcher works Mac Pro 4,1 flash to 5,1. after install goes to setup screen with no problems just wifi doesn't work after setup. Followed Barrykn instructions but commands not found in Big Sur install public beta after running commands from bigger beta 4 not supported any help would be awesome and yes I'm rocking an rx 570 which is metal compatible .