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.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I'm sure I followed the instructions here after opening the 'spoiler' and I did of course change the UUID to my own. but i must be making an error somewhere as this is the result I get.
I repeated the steps several time in case I did something obviously wrong but I get the same result ... No such file or directory
/dev/disk4 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +479.9 GB disk4
Physical Store disk0s2
1: APFS Volume SSD BigSur beta 2 - ... 274.2 GB disk4s1
2: APFS Volume Preboot 360.1 MB disk4s2
3: APFS Volume Recovery 887.8 MB disk4s3
4: APFS Volume BigSur beta 15.8 GB disk4s4
5: APFS Snapshot com.apple.os.update- ... 15.8 GB disk4s4s1
6: APFS Volume VM 1.1 MB disk4s6
david@Davids-QuadPro-4 ~ % sudo diskutil mount disk4s2
Password:
Volume Preboot on disk4s2 mounted
david@Davids-QuadPro-4 ~ % ls -l /System/Volumes/Preboot
total 0
drwxr-xr-x 11 _nsurlsessiond _nsurlsessiond 352 Jul 22 14:47 1B08D35B-CCDB-4E60-8BCB-B5A71C2F9054
david@Davids-QuadPro-4 ~ % sudo mv ~/Users/apple/Downloads/.disk_label.contentDetails /System/Volumes/Preboot/1B08D35B-CCDB-4E60-8BCB-B5A71C2F9054/System/Library/CoreServices/.disk_label.contentDetails
mv: rename /Users/david/Users/apple/Downloads/.disk_label.contentDetails to /System/Volumes/Preboot/1B08D35B-CCDB-4E60-8BCB-B5A71C2F9054/System/Library/CoreServices/.disk_label.contentDetails: No such file or directory
david@Davids-QuadPro-4 ~ %
What am I doing wrong that I cannot see?
you did not specify the path to Terminal correctly
sudo mv ~/Downloads/disk_label.contentDetails /System/Volumes/Preboot/1B08D35B-CCDB-4E60-8BCB-B5A71C2F9054/System/Library/CoreServices/.disk_label.contentDetails
[automerge]1595799493[/automerge]
Yes you can, I don't see a problem in this
Can the file be created from scratch instead of copied from the zip?
Code:
getdiskinfo () {
# $1 = the disk you want info for (either a mountpoint like "/" or a device "disk0s1")
# $2 = prefix for variable names
eval $(diskutil info -plist $1 | plutil -p - | perl -nE 'if (s/ *"([^"]+)" => "?(.*?)"?$/'$2'\1=\2/) { s/"/\\"/g; s/([^=]+=)(.*)/\1"\2"/; print $_ }')
}
setbootername () {
local thedisk="$1"
local NewBooterName="$2"
getdiskinfo "$thedisk" Root
if [[ -n $RootBooterDeviceIdentifier ]]; then
diskutil mount $RootBooterDeviceIdentifier
getdiskinfo $RootBooterDeviceIdentifier Preboot
if [[ -n $PrebootMountPoint ]]; then
local theUUID=""
if [[ -d $PrebootMountPoint/$RootVolumeUUID ]] then
theUUID=$RootVolumeUUID
echo "using VolumeUUID"
elif [[ -d $PrebootMountPoint/$RootAPFSVolumeGroupID ]] then
theUUID=$RootAPFSVolumeGroupID
echo "using APFSVolumeGroupID"
else
echo "unknown UUID in booter"
ls -l "$PrebootMountPoint"
return 1
fi
thefile="$PrebootMountPoint/$theUUID/System/Library/CoreServices/.disk_label.contentDetails"
[[ -f "$thefile" ]] && { echo "$thefile already exists: $(cat "$thefile")" } || { sudo bash -c "echo \"$NewBooterName\" > \"$thefile\""; echo "$thefile is created" }
else
echo "$RootBooterDeviceIdentifier is not mounted"
fi
else
echo "No booter device"
fi
}Then use it like this:
Code:
setbootername / "BigSurBeta3onTB"
Volume Preboot on disk3s4 mounted
using APFSVolumeGroupID
/System/Volumes/Preboot/0AB9A108-98D7-4D65-BA3E-E5B63810D6AE/System/Library/CoreServices/.disk_label.contentDetails already exists: BigSurBeta3onTB
setbootername CatalinaTest "CatalinaTest"
Volume Preboot on disk2s2 mounted
using VolumeUUID
/Volumes/Preboot/A09D8599-5B1A-4269-9957-496E439C45C3/System/Library/CoreServices/.disk_label.contentDetails already exists: CatalinaTest
setbootername "Big Sur Beta 3" "Big Sur Beta 3"
Volume Preboot on disk6s2 mounted
using APFSVolumeGroupID
/Volumes/Preboot 1/1A7E15CC-7A0E-3E99-B3BD-C18BF906C185/System/Library/CoreServices/.disk_label.contentDetails is created
setbootername "Big Sur Beta 3" "Big Sur Beta 3"
Volume Preboot on disk6s2 mounted
using APFSVolumeGroupID
/Volumes/Preboot 1/1A7E15CC-7A0E-3E99-B3BD-C18BF906C185/System/Library/CoreServices/.disk_label.contentDetails already exists: Big Sur Beta 3
Last edited:
At the moment I get "permission denied". So how do I get permissions set to allow this to run?
I'm not sure what could cause "permission denied". Maybe post results of commands? Maybe try executing the commands manually one at a time?
I made a correction : Big Sur Preboot volumes use APFSVolumeGroupID instead of VolumeUUID of root for the UUID folder name.
"Big Sur Preboot" UUID "folder name" matches with the APFS "BigSur Data Volume" UUID (
diskutil apfs list), before BigSur it matched instead with "System Volume" UUID , I guess this APFS Preboot UUID change depends from the fact that apple introduced SSV .
Could expect that on the next "Big Sur beta 4" also the Incremental update (about 5 GB) works only with VMM flag ?
Have you managed to play DRM contents in BigSur?
Last edited:
Kepler still runs fine in BigSur
[automerge]1595868809[/automerge]
I have csr-active-config:
But :
And:
Why is
[automerge]1595868809[/automerge]
I have csr-active-config:
Code:
<key>csr-active-config</key>
<data>
D/8=
Code:
csrutil status
System Integrity Protection status: unknown (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: enabled
NVRAM Protections: enabled
BaseSystem Verification: disabled
Code:
csrutil authenticated-root
Authenticated Root status: disabledNVRAM Protections: enabled?
Last edited:
Not yet, and I won't go deeper until Lilu / WEG fully support Big Sur.
what is your
nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-active-config output?
I also had "SIP as Custom Configuration", in my case was due to SIPManager.kext installed on LE or SLE, then I removed it and I can normally disable SIP, but another case is that you have a patched boot.efi (non apple stock) installed in these paths:
/ Preboot UUID /System/Library/CoreServices/
/System/Library/CoreServices/
/usr/standalone/i386/
in those paths you should instead use stock apple boot.efi (from the macOS you are using) if you want to disable SIP correctly with "csrutil disable", after those you can have this output:
System Integrity Protection status: disabled.
that is weird. And this?:
Code:
nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-active-config| awk '{split($NF,chars,""); for(n=0;n<256;n++){ord[sprintf("%c",n)]=n}; i=1; j=0; while(i<=length($NF)){if(substr($NF,i,1)=="%"){printf "%s",toupper(substr($NF,i+1,2)); i=i+2} else {printf "%x",toupper(ord[chars[i]])} j=j+2; i++} print("")}'I changed:
Code:
<key>csr-active-config</key>
<data>
dwgAAA==
Code:
nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-active-config
7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-active-config w%08%00%00
Code:
csrutil status
System Integrity Protection status: disabled.77080000, which makes no sense when converted to binary so Dortania manual is not correct:Despite 'No such file or directory' the Boot Selector has started to show as "BigSur" and no longer "Preboot".
Figure???
Last edited: