Notifications
Clear all

macOS 11 Big Sur  

 of  11
  RSS

Irakly Shanidze
(@irakly_shanidze_1)
Active Member
Joined: 6 months ago
 
Posted by: @mac_editor
Posted by: @irakly_shanidze_1

BaseSystem Verification: enabled

Here's the proof Smile  Also it says right there - unknown (Unsupported configuration).

This is what SIP disabled looks like:

[Please login to see this]

how do I disable that? When I do "csrutil disable", it just responds "system integrity protection disabled", like everything is OK. Also, like I mentioned previously, it refuses to do "csrutil authenticated-root disable" 🙁

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

.

ReplyQuote
Irakly Shanidze
(@irakly_shanidze_1)
Active Member
Joined: 6 months ago
 

I might have figured out the problem. It appears that the recovery partition is still High Sierra for some reason. At least this is what it suggests to install. So, I guess, the way to do it is to create a USB Big Sur installer, boot from it into the recovery mode and then tell Terminal what to do... Big Sur is surreal indeed.

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

.

ReplyQuote
Irakly Shanidze
(@irakly_shanidze_1)
Active Member
Joined: 6 months ago
 

This is insane... I tried to create a bootable USB drive using  a well-known commant "sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/UNTITLED --nointeraction" but Terminal said "command createinstallmedia not found"...

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

.

ReplyQuote
Irakly Shanidze
(@irakly_shanidze_1)
Active Member
Joined: 6 months ago
 

I figured it out. Once Big Sur is installed, creating a bootable USB drive involves one extra step. If the installer is in the Applications folder, it ain't gonna work period, as the system protects applications from a prying eye. It needs to be copied into Downloads, or elsewhere, and only then createinstallmedia will be available for use.

"sudo /Downloads/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/UNTITLED --nointeraction"

After that, boot from the USB drive, launch Terminal, disable SIP and ART. Reboot, launch purge-wrangler (if its prompt does not pop up automatically) and proceed as described.

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

.

ReplyQuote
Netcho
(@netcho)
Eminent Member
Joined: 2 years ago
 

Anybody having an issue disconnecting eGPU with TB2?

MacBook Pro 2015 15” 2.5 GHz

 
2015 15" MacBook Pro (R9 M370X) [4th,4C,H] + RX Vega 56 @ 16Gbps-TB2>TB3 (Razer Core X) + macOS 10.14.4 [build link]  


ReplyQuote
mwt0000
(@mwt0000)
New Member
Joined: 5 months ago
 

My original whining:

My eGPU isn't even recognized after upgrading to Big Sur. It's a Gigabyte RX 580 Gaming Box, which is officially supported, so I'm not sure why this could be the case. Everything was fine when I was using Catalina this morning. This is just within macOS on a 2017 model with no discrete GPU, so there should be no complications encountered by Bootcamp/Windows/NVIDIA things. Running purge-wrangler did not change anything, and my other troubleshooting options seem to be limited if it won't even connect.

 My first update:

Somehow, using a different wall outlet now lets the eGPU spin up. However, it won't use clamshell mode or even accept power from the eGPU. This is, again, despite everything working fine on Catalina.

And now, after fiddling with the Thunderbolt cable, everything seems to be operational. A few hours later, all I've managed to do is make myself look silly. That is, of course, ignoring the features of Big Sur that I'll probably never use. Lesson learned about being a early-ish adopter - I thought waiting a few weeks would be enough and I was wrong.

This post was modified 5 months ago

Gigabyte RX 580 Gaming Box with 2017 MacBook Pro


ReplyQuote
Rycco
(@rycco)
Reputable Member
Joined: 4 years ago
 

Apple usually releases a ~1GB update about one month after the new MacOS release. I'm waiting for it to upgrade. I always get anxious about getting the latest version, but I've learned the lesson a few years ago haha.

 

2017 15" MacBook Pro (RP555) [7th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.12.6 & Win10 [build link]  

ReplyQuote
lucasjackson87
(@lucasjackson87)
Active Member
Joined: 5 months ago
 

@mac_editor, can you not enable csrutil after having disabled it to get purge wrangler to work?

 

I tried enabling it and my computer just kept looping while restarting. Luckily I was able to boot in recover and disable csrutil again. 

 

This post was modified 5 months ago

2015 Mid 15" MacBook Pro + RX 580 @ 16 GB 1600 MHz DDR3 + macOS 10.15.7


ReplyQuote
mwt0000
(@mwt0000)
New Member
Joined: 5 months ago
 

Update to my post a few weeks, I'm still getting tons of weird behavior, including kernel panics within ~10-20 mins of booting. I re-installed Big Sur yesterday (now 11.1) and keep running into the same issues. Often the eGPU isn't even recognized at all, and, even worse, System Report sometimes detects that there is an eGPU connected but nothing beyond that (i.e. nothing indicating it detects a Radeon card at all).

Again, this is an RX 580, so I'd expect close to plug-and-play. No NVIDIA or Windows use cases for me with this eGPU at the moment.

 

Gigabyte RX 580 Gaming Box with 2017 MacBook Pro


ReplyQuote
lmnope1
(@lmnope1)
New Member
Joined: 4 months ago
 

@mac_editor is is possible to load purge wrangler via kernel extensions? Kext installation does not require SSV to be disabled.

I am seeking some way to keep filevault enabled (not disabling authenticated-root) and also install purge wrangler.

https://developer.apple.com/documentation/kernel/installing_a_custom_kernel_extension

 

Edit - I installed the AMDLegacySupport and AutomateeGPU kexts using this tool, and my eGPU works! Did not have to disable authenticated-root, and my filevault is intact!

Tool: https://github.com/chris1111/Kext-Droplet-Big-Sur

2015 Macbook Pro with AMD M370X

Big Sur 11.1 (20C69)

AMD 5700 in Sonnet Breakaway box

Connected over TB2

This post was modified 4 months ago

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

.

ReplyQuote
 of  11