yup that is the correct one from barry instructions
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 11 Big Sur on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
-
- Tags
- 10.16 macos unsupported
- Sort by reaction score
- Status
yup that is the correct one from barry instructions
I start from catalina, make partition for install BS, make patch usb instaler, follow the instruction from micropatcher.. and then install , just wait until show region, shutdown, patch kexts again with usb micropatcher, done.
Last edited:
Hi Will,
think we all want to help you here. also think all think why the sh he does not get further.
Therefore my question: how do you get into the installer?
The above is what you said together with the above picture, you were wrong, proven by another poster which replied to you, you can see clearly you typed the command wrong, that's why I said to use the good one and counteracted your claim.
Fact is, you were wrong, and now you start to get pissed of by me while you yourself made the mistake.
I try to help and then I get this...
I am done helping you out.
Have a nice day.
Big Sur Beta 6 successfully installed, still using micropatcher 0.16, I see no need to keep changing or updating this script, once it worked, it will always work, in all updates or future versions of macOS Big Sur.
I replaced the wifi card with an Airport compatible with 802.11ac.
So my system is as original as possible, because of that, I changed the arguments in the reset-vars.sh file to stay in the default.
reset-vars.sh:
csrutil authenticated-root enable
csrutil enable
echo
echo boot-args and csrutil settings restored to defaults. Please reboot.
In this build, a lot of internal changes were made to the system, many commercial apps from Apple needed updates: Final Cut Pro, Motion, Compressor were the ones I could see here.
There was a bizarre bug in the graphics, it was also fixed. It was something related to Word 2019.
You start typing a document, and the lines would disappear as the next line started, then they would appear again, and then they would disappear, but the text was there, it just wasn't visible, it was blinking, I even sent that Feedback Assistant report, I sent a video demonstrating, Apple asked me for more details, but I didn't have time to send it, I believe that other people reported this same problem.
I couldn't believe it had been fixed, but I opened Word and started typing and wow, it was working.
I replaced the wifi card with an Airport compatible with 802.11ac.
So my system is as original as possible, because of that, I changed the arguments in the reset-vars.sh file to stay in the default.
reset-vars.sh:
csrutil authenticated-root enable
csrutil enable
echo
echo boot-args and csrutil settings restored to defaults. Please reboot.
In this build, a lot of internal changes were made to the system, many commercial apps from Apple needed updates: Final Cut Pro, Motion, Compressor were the ones I could see here.
There was a bizarre bug in the graphics, it was also fixed. It was something related to Word 2019.
You start typing a document, and the lines would disappear as the next line started, then they would appear again, and then they would disappear, but the text was there, it just wasn't visible, it was blinking, I even sent that Feedback Assistant report, I sent a video demonstrating, Apple asked me for more details, but I didn't have time to send it, I believe that other people reported this same problem.
I couldn't believe it had been fixed, but I opened Word and started typing and wow, it was working.
Last edited:
For those who don't understand the differences between a / and a \, back/forward slash.
A Forward slash is used in a path while a backward slash followed by a space is a space in a name.
Example, I have 2 Folders, 1 called Perry, the 2nd one called Perry 1
Paths are
/Users/***/perry
/Users/***/Perry\ 1
A Forward slash is used in a path while a backward slash followed by a space is a space in a name.
Example, I have 2 Folders, 1 called Perry, the 2nd one called Perry 1
Paths are
/Users/***/perry
/Users/***/Perry\ 1
first you need to navigate to the folder.
cd /Volumes/Image\ volume/
once inside the folder, you can give the command "ls"to list the files.
then use the argument
./set-vars.sh
can't forget the dot "."
http://swcdn.apple.com/content/down...qay4n78q85cpe85rcsdu00qy/InstallAssistant.pkg is this beta 6? Comes up as 12.16GB
H I N T !!
DP 6 is able to break the connection of your network shares. For all who have run in this problem.
Open terminal and type in
sudo kextload /System/Library/Extensions/smbfs.kext
fixed
DP 6 is able to break the connection of your network shares. For all who have run in this problem.
Open terminal and type in
sudo kextload /System/Library/Extensions/smbfs.kext
fixed
please have an exact look at the terminal picture first line. he was correct
Haven't heard anyone else on the thread speak on it, but after some digging around, looks like 4k playback in Safari has now been disabled on devices older than 2018. I've heard some complaints on the BS6 thread, but nothing here. Unless its just a bug, my working theory is they did something similar to the sidecar rollout in Catalina. Limiting older devices as further Beta's rolled out. Maybe has to do HEVC hardware limitations. Even after a complete rebuild of my install disk and reinstall, still nothing, both Netflix and Youtube stuck at 1080p
Safari 4k is fine on my Late 2012
Attachments
Thanks for the heads up! Very strange. Maybe I need to amend my theory. I'm running a mid 2012 13"... maybe it has to do with integrated vs dedicated graphics? Or its just a bug. Anyone else running into the same problem?
Does anyone with a MacPro 5.1 have stability issues with the latest beta? I had to move back to Mojave again as my PC was crashing every 30-40 minutes. The only thing I can think of that might have created the issue absent an unstable release was an issue with my TimeMachine restore.
In GitHub, Barry K. Nathan gives the following advice on keying in the command.
It worked for me when set-vars.sh would not run.
Open Terminal (in the Utilities menu), then run /Volumes/Image\ Volume/set-vars.sh. This script will change boot-args and csrutil settings as needed, and also set things up so the Installer will run properly. Don't forget that tab completion is your friend! You can type /V<tab>/I<tab>/se<tab> at the command prompt -- that's much less typing! (Run /Volumes/Image\ Volume/set-vars.sh -vinstead if you want verbose boot, which can be very useful for troubleshooting.)
In beta
There's a whole nother thread so why don't you keep it there
macOS 11 Big Sur Safari YouTube 4K HDR VP9 support
Only going to mention this once in this thread.. the current sitch is that in beta 5, machines as far back as 2013 even with only integrated graphics could play 8K YT videos with the VP9 codec nice and smooth. In beta 6, machines with discrete GPUs can still play 4K, some 8K, but 4K and 8K have been yanked from machines with integrated GPUs only.
Its mostly likely Apple behind this as it was the beta change that did it; I restored a clone of BS beta 5 and got back 8K on my Late 2013 13-inch rMBP
There's a whole nother thread so why don't you keep it there
macOS 11 Big Sur Safari YouTube 4K HDR VP9 support
Only going to mention this once in this thread.. the current sitch is that in beta 5, machines as far back as 2013 even with only integrated graphics could play 8K YT videos with the VP9 codec nice and smooth. In beta 6, machines with discrete GPUs can still play 4K, some 8K, but 4K and 8K have been yanked from machines with integrated GPUs only.
Its mostly likely Apple behind this as it was the beta change that did it; I restored a clone of BS beta 5 and got back 8K on my Late 2013 13-inch rMBP
Though this may seem a bit off-topic meanwhile -
On my MBP5,2, a legacyUSB machine, continued installation exercises without resorting to SATA for the BS disk.
Did this with BS PB1 because I had no success with newer versions on that machine.
So I was able to install and boot PB1 using the on-board USB2 plus the USB3 on nanoTECH ExpressCard. Exactly the way @Larsvonhier has described in an earlier post: start booting on USB2, when it hangs due to legacyUSB support not (yet) in place, hot-swap to USB3, and it continues.
Then later after installation, legacy USB etc support becomes availably by applying one of @jackluke prelinkedkernel fixes.
It took a while to get hold of the expresscard: >10 weeks surface mail from Hongkong. Worth waiting and paying the 35USD! The two USB3 connectors also serve well for faster backups.
Some more detail:
- made a USB BS installer from PB1 with createinstallmedia and jackluke's BigSur BaseSystem legacy usb fix (the older one, dated 4 Aug)
- after doing the @ASentientBot Hax3.sh the installer sees the freshly erased SSD connected to USB3
- installer phase1 proceeds, then for booting into phase2 the SSD needs to go to USB2. Then while hanging with the Apple but no progress bar, hot-swap to USB3. Phase2 and the white-on-black phase3, with progress bar and timing, proceed to the end
- for rebooting, hook on USB2 again then hot-swap to USB3 (twice if I remember correctly)
- boot to Catalina to apply the BigSur beta3 Nvidia Tesla fix
- BS now boots fine from USB2, migrated everything from Catalina living on the internal SATA SSD.
May sound complicated, but is easier and healthier than opening the machine to swap disks between SATA and USB.
It would be nice to boot directly from expresscard USB3 ports, without starting on USB2. Maybe there is a way with Opencore.
Attachments
Last edited:
Thanks for the heads up on the other thread, and the info! I think that information can benefit those on this thread as well. I'm sure I wasn't the only one in the dark on that change. But I figured it was something along those lines. Thanks again
I have beta 6 running and very stable on 3 Mac Pro 5,1 machines. They were all installed differently. One was a fresh install, one was installed over a Catalina partition (that had been installed using dosdude1's patcher) and one was installed over a previoous install of Beta 5. All are running good and stable. Kudos to Barry for the MicroPatcher!!
The only issue that I currently have is that Google has not updated Backup and Sync for Big Sur compatibility (or Apple has not made Big Sur compatible yet, whichever is the actual scenario).
I have a 2008 model 8 core Mac Pro 3,1, upgraded with a Metal-supported (and EFI flashed) GeForce GTX 680, a BCM94360 WiFi AC + BT4.0 card, 56GBs of memory and a PCIe USB 3.0 card. What is the best way to go about installing Mac OS Big Sur on it?