Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

GSXB

macrumors regular
Jun 21, 2018
246
198
England
I’ve installed big sur beta 5 using opencore
Now it installed and working can I reboot to the recovery usb and reset nvram with the set-vars.sh and then reboot without opencore ???
 
  • Like
Reactions: TimothyR734

EdGlassgow

macrumors member
Jun 9, 2019
60
83
Which drive did you leave in? The pci drive
[automerge]1598081927[/automerge]

Yes done a pram reset no joy still bootloops

I installed to an SSD in Bay 1. I took the PCIe card out and may leave it out. Thinking back on all this, it kind of seems that when it reboots to finish the install, that it is not finding the correct drive to boot from.
 
  • Like
Reactions: TimothyR734

IbrahimFmc

macrumors member
Aug 11, 2020
54
60
successfully installed Dp5 but unable to make wifi working with old patch and it is giving random restart and this message after open
 

Attachments

  • Screen Shot 1442-01-03 at 8.28.29 AM.png
    Screen Shot 1442-01-03 at 8.28.29 AM.png
    493.1 KB · Views: 198
  • Screen Shot 1442-01-03 at 8.28.04 AM.png
    Screen Shot 1442-01-03 at 8.28.04 AM.png
    661.7 KB · Views: 176

thielsa

macrumors member
Dec 30, 2006
30
22
My technique to update my MacPro 5.1 was partially successful with Beta 5. I was able to use the Barry micro patch technique like the previous update. In my first try Big Sur did not install fully on my hard drive. On the reboot it rebooted to one of my other hard drives. I re-did the installation fully a second time but this time it worked fully. However, I did have a bump in the road relative to my Time Machine restoration. No matter which backup I selected it crashed partway through and booted back to the beginning of setting up Big Sur. I had to manually restore my apps to get things back and running again. So far things are running smoothly.
 

thatsmeonlyme

macrumors regular
May 30, 2018
222
303
Loewenstein Germany
@Barry K. Nathan @jackluke
I have the following problem. On my late 2011 MBP patched Install with Barry´s patcher V 0.1.0 BigSur DP4 is working fine. I did upgrade the WIFI / BT card with a Broadcom Card BCM94331PCIEBT4CAX. This is the card also used in MBP 9.1 MID 2012. After Install I got BT 4.0 oob but not Airdrop. I spent hours of searching the web, forums and so on but did not find a working solution. During my investigation I found that the IO family.kext is not installed with the BRCM 4360 driver there is only 4331 to find in the kexts. The airdrop Symbol appears in the finder without text after Terminal command :"defaults write com.apple.NetworkBrowser BrowseAllInterfaces 1". In the system profiler I can find Airdrop supported in WLAN. under bluetooth Handoff is not supported also not in system preferences general. ANY IDEA??

In Systemparameters.plist I have whitelisted the machine "continuity support <true/>
 
  • Like
Reactions: TimothyR734

IbrahimFmc

macrumors member
Aug 11, 2020
54
60
update , system failed to boot from Big Sur Partition Dp 5 , several time system restarted
 

Attachments

  • IMG_7727.jpg
    IMG_7727.jpg
    934.7 KB · Views: 158
  • Like
Reactions: TimothyR734

justperry

macrumors G5
Aug 10, 2007
12,627
9,933
I'm a rolling stone.
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:
Code:
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 /" .

I did this a few days ago, resulting in a stuck startup, problem was kernel cache.
I booted from a "Install Big Sur" USB stick and ran the rebuild-kc.sh, that worked.
 

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
Big Sur Public Beta 2 on iMac 2011 with AMD Polaris cards

Just a short update. Got this message from @Pascal Baillargeau tonight:

"Just got it working now. I have install it on an iMac 2011 with a NVIDIA 780M, apply your patches and clone Big Sur system on WX7100 iMac using ASR-Clone-SSD-macOS-Catalina-Big-Sur. I am testing it now. Sleep/Wake works. Wait and see."

Direct installation still fails, booting directly an installation made on an NVIDA system fails, too (STOP sign). Copying using this tool works. The target has to be bigger in size as the source and it is based on Apples asr commands.

We made the installations using @Barry K. Nathan 's micro patcher. But after the copy act we got the error 75 while trying to mount the root slice, but the old method mount -uw /; killall Finder works now. Have not done any "reverse engineering" of the ASR tool motioned above.

The AMD card works in the same way as with Catalina and Mojave. We spoof the iMacPro1,1 board ID using OpenCore to get the hardware features enabled like 4K H.264 and HEVC. This works, too.

NOTE:
Although the AMD card works now with all installed MacOS versions on this particular iMac in the same way something has changed. It does no boost the GPU core any longer to the max of 1053 MHz on load with every application running. GeekBench5 and UNIGINE Valley are running significantly slower, QuickTime is doing well. This might me a coincidence, the card may have a hardware problem occurred exactly after installing and checking the Big Sur PB2, I do not know. With different tweaks I can force the AMD card to boost to the max. core and memory frequency after boot, so in principle boosting works. But this draws more power (+10W) all the time and heats up the card card and heat sink in idle times. PRAM reset and reboot does not change this. The same card in another system without Big Sur installed runs fine all the time and boosts if necessary with every application using the exact same OpenCore config (same SD card, in fact).
 
Last edited:

RITAMA

macrumors member
Jul 15, 2020
45
67
@Barry K. Nathan

don't know whether this can help:
patched with your latest patcher (010) my MID 2012 MacBook 9.1 shows the following after applying jacklukes IvyBridge prelinked Kernel on DP4

Here Airdrop is working


Last login: Thu Aug 20 15:44:45 on ttys000


gerhard@macbookpro ~ % kextstat | grep AirPort


74 0 0xffffff7f81ed7000 0x588000 0x588000 com.apple.driver.AirPort.Brcm4360 (1400.1.1) 8DE38A76-B284-34D2-AF4E-DB727D7FF250 <73 72 69 18 13 8 7 6 5 3 1>


75 0 0xffffff7f824da000 0x1e8000 0x1e8000 com.apple.driver.AirPort.Brcm4331 (800.21.31) D4559F1A-005E-353C-B33F-3006C349EE5D <73 18 13 8 7 6 5 3 1>


gerhard@macbookpro ~ %
Would you like to share step by step ?
 
  • Like
Reactions: TimothyR734

Bug-Creator

macrumors 68000
May 30, 2011
1,783
4,717
Germany
O.k. I'm a bit confused right now (and that 1st WikiPost doesn't really help much)

I got:

- 6core Mid2010 MPro with a Radeon R9/280 running Mojave

- 2017 MacBook (12") running the current BigSur public beta

Lot of sites/posts talk about downloading the beta 1st but I can only find that installer.pkg
Next your supposed to apply patches, but to what? The actual OS download that I can't find? The installer??

So I tried a different approach, hooked up an 1TB HDD to the MacBook and installed the BigSur there (took ages) and then put that into the MacPro.
It did seem to find that drive bootable at 1st but I ended up with that forbidden symbol.

So is there a way to patch that install to work on the MPro?
 
  • Like
Reactions: TimothyR734

Ausdauersportler

macrumors 603
Nov 25, 2019
5,007
5,826
O.k. I'm a bit confused right now (and that 1st WikiPost doesn't really help much)

I got:

- 6core Mid2010 MPro with a Radeon R9/280 running Mojave

- 2017 MacBook (12") running the current BigSur public beta

Lot of sites/posts talk about downloading the beta 1st but I can only find that installer.pkg
Next your supposed to apply patches, but to what? The actual OS download that I can't find? The installer??

So I tried a different approach, hooked up an 1TB HDD to the MacBook and installed the BigSur there (took ages) and then put that into the MacPro.
It did seem to find that drive bootable at 1st but I ended up with that forbidden symbol.

So is there a way to patch that install to work on the MPro?
Search this thread using the search button above or scroll up some pages and read yourself. Public Beta 2 is out, I would assume the Beta 1 is no longer available. There is a micro patcher @Barry K. Nathan published on GitHub. Give it a try.
 

thatsmeonlyme

macrumors regular
May 30, 2018
222
303
Loewenstein Germany
O.k. I'm a bit confused right now (and that 1st WikiPost doesn't really help much)

I got:

- 6core Mid2010 MPro with a Radeon R9/280 running Mojave

- 2017 MacBook (12") running the current BigSur public beta

Lot of sites/posts talk about downloading the beta 1st but I can only find that installer.pkg
Next your supposed to apply patches, but to what? The actual OS download that I can't find? The installer??

So I tried a different approach, hooked up an 1TB HDD to the MacBook and installed the BigSur there (took ages) and then put that into the MacPro.
It did seem to find that drive bootable at 1st but I ended up with that forbidden symbol.

So is there a way to patch that install to work on the MPro?
First: I do not understand, where is your problem. Download micro patcher from
https://github.com/barrykn/big-sur-micropatcher !

Follow the steps 1-10 and reboot your cMP. Caution: Before doing that be sure you have upgrade to the actual firmware 144.0.0.0.
I am not sure but think you will find it on the latest High Sierra release. cMP does not automatically update the firmware. Maybe under Mojave you have only 142.0.0.0.

As you can see I have the same machine with the same GPU. All is working very fine so I can use this machine as my productivity machine since weeks and didn't have any bug until now.
 
  • Like
Reactions: TimothyR734

thatsmeonlyme

macrumors regular
May 30, 2018
222
303
Loewenstein Germany
Would you like to share step by step ?
Caution. this seems to work only to DP 4 or PB1

Download micro patcher from @Barry K. Nathan

Follow the steps 1- 10.
After that reboot into your patcher and do the following step for applying the kexts for ethernet, WIFI and so on.

Boot your machine.

Then download from @jackluke https://github.com/jacklukem/BigSur...eta3 prelinkedkernel fix.command.zip?raw=true

apply this patch using terminal
Caution : you have to have a working ethernet connection.

reboot and everything should work

NOTE. I also had to read carefully the pages and threads in this forum !
 

iMac-Oldschool

macrumors regular
May 22, 2019
149
157
Brexit
Since apple with BigSur beta 5 (I guess on purpose) reduced the BaseSystem ramdisk size (available space), I adjusted the "BaseSystem legacy usb fix" that still produces a working installer for non-APFS or legacy USB Mac:

BigSur BaseSystem legacy usb fix.zip

(stock beta5 BaseSystem.dmg size 745 MB , after legacy usb fix is 700 MB , on beta 4 was 840 MB )

so "patched prelinkedkernel" works for the beta 5 installer and allows to install BigSur beta 5, but not yet to boot BigSur after install or upgrade, you might need USBOpenCoreAPFSloader4 and CMD+S with "exit" to boot legacy USB Mac.

While for any recent USB Mac, there are no issues in using the BootKernelExtensions.kc , to apply kext patches use the micropatcher from its USB BigSur recovery environment.

Another weird working way to disable "snapshot booting" that means a working "sudo mount -uw /" is to skip the stage3 installer, I used it also for this beta 5 and it worked too.
Tried to install Public Beta 2 on an iMac8, largely following the procedure in post #2730. BigSur BaseSystem legacy usb fix.zip built the installer, as defined in post #3409, but it did would boot.
BigSur Penryn beta3 prelinkedkernel fix enables booting (post #3258), but system hangs at the end of progress bar.
Neither of the OpenCoreAPFS loaders solves the problem. USBOpenCoreAPFSloader3b and USBOpenCoreAPFSloader4 both install on a suitable USB stick and can be booted. However, macOS never starts and the system remains at the end of the progress bar.
Has anybody managed to boot PB2 on a non-metal Mac?
I also have an iMac 13,1, which has Metal graphics but Big Sur is not officially supported by Apple. Using Barry K. Nathan's Micropatcher.sh, Big Sur installs and runs without major problems.
 
  • Like
Reactions: TimothyR734

Alex-Microsmeta

macrumors 6502
Jul 14, 2018
376
630
Rome
Tried to install Public Beta 2 on an iMac8, largely following the procedure in post #2730. BigSur BaseSystem legacy usb fix.zip built the installer, as defined in post #3409, but it did would boot.
BigSur Penryn beta3 prelinkedkernel fix enables booting (post #3258), but system hangs at the end of progress bar.
Neither of the OpenCoreAPFS loaders solves the problem. USBOpenCoreAPFSloader3b and USBOpenCoreAPFSloader4 both install on a suitable USB stick and can be booted. However, macOS never starts and the system remains at the end of the progress bar.
Has anybody managed to boot PB2 on a non-metal Mac?
I also have an iMac 13,1, which has Metal graphics but Big Sur is not officially supported by Apple. Using Barry K. Nathan's Micropatcher.sh, Big Sur installs and runs without major problems.

Similar situation here, but it loads fine with 0.1.0 patcher + OpenCoreLoader4. With Macmini 2010 until beta 4 I was able to boot without OpenCoreLoader4 and Wifi was working fine, with Beta 5 (PB2) it runs faster, but without essential features like WIFI and acceleration it is useless. I really hope that @jackluke @ASentientBot @Barry K. Nathan and others will find the way to improve patchers for older models. Luckily I have also an iMac 2013 that works perfectly with BS Beta 3 and I can stay with it until golden master will be released...
 
Last edited:

AbominableFish

macrumors newbie
Jul 4, 2020
16
13
Sorry for being annoying, but just another question about updating since I don't know where to look on this thread.
Never mind, not worth it imo.
 
Last edited:
  • Like
Reactions: TimothyR734

IbrahimFmc

macrumors member
Aug 11, 2020
54
60
Sorry for being annoying, but just another question about updating since I don't know where to look on this thread.

I want to update from b1 to b5 on my MacBook Pro 2012 13" retina. How would I go about doing so? Anyone have a link?
beta 5 for unsupported Mac not Recommended , you will face several restart , failure boot , wifi patch will not work , no airdrop , no handoff
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.