Jump to content

[pre-release] macOS Big Sur


3,698 posts in this topic

Recommended Posts

1 minute ago, Blu24 said:
  • Boot into Catalina 
  • open Disk utility 
  • In Disk Utility, right-click. rename your USB

 

 

Thanks :) I don't know why, Picker see only data partition instead of main partition :cry:

Link to comment
Share on other sites

23 minutes ago, Matgen84 said:

 

Thanks :) I don't know why, Picker see only data partition instead of main partition :cry:

I think it's to do with the new file structure. At the moment you can access your Catalina HD from Big Sur but you can't access Big Sur from Catalina. Have you noticed "Incompatible Disk info" Top right? when you boot into Catalina?

Screenshot 2020-07-12 at 12.42.18.png

Edited by Blu24
  • Like 2
Link to comment
Share on other sites

1 hour ago, MorenoAv said:

@manmo71

I tried it, removed the said parameters and lost boot and graphic acceleration ... 

Thanks

@MorenoAv I have just edited the Platform-ID for iGPU in your config.plist, everything else remains untouched.

Replace your existing config.plist (after backing up a copy) with this one and give it a try.

If this does not work, then I am out of idea's for the moment.

 

config.plist

Edited by manmo71
  • Thanks 1
Link to comment
Share on other sites

12 hours ago, chris1111 said:

I Just use OpenCore with  the necessary good files and the good System Definiton

 

 

Hi Chris, could you upload your EFI folder for this HP Probook laptop?

Thanks.

Link to comment
Share on other sites

36 minutes ago, Matgen84 said:

 

Thanks @fusion71au :)  It works now. Do you if  there is a setting for also disabling Authenticated Root at the same time.
I don't understand why OC Picker show "BigSur - data" and not "BigSur HD" (I name BigSur my HD, of course)



 

 

12 minutes ago, Matgen84 said:

 

Thanks :) I don't know why, Picker see only data partition instead of main partition :cry:

 

For disabling Authenticated Root, you can set the NVRAM csr-active-config parameter to 0x77080000 in OC config.plist, then resetting NVRAM through the OC boot menu or with booting to Big_Sur's Recovery/Installer USB and disabling it with csrutil in terminal (see my post on APFS Snapshot Procedure and the examples in it).

 

OC uses the content of the hidden text file /System/Volumes/Preboot/UUID/System/Library/CoreServices/.disk_label.contentDetails to label the macOS volume...

 

Spoiler

468017673_OpenCanopyGUI.thumb.png.69309f45bc271e3494159a1b1c24c2c1.pngdisk_label.contentDetails.thumb.png.0f51e4e07876eaea5f9f579d0d9cd6bb.png

 

 

Also check your OC boot log eg if you have the debug version of OC, type in terminal

 

ioreg -lw0 -p IODeviceTree | grep boot-log | sort | sed 's/.*<\(.*\)>.*/\1/' | xxd -r -p

 

and you might see something like this output...

17:915 05:721 OCB: Should boot from 8. Big_Sur (T:2|F:0|G:0|E:1|DEF:0)
17:916 00:000 OCB: Perform boot Big_Sur to dp PciRoot(0x0)/Pci(0x14,0x0)/USB(0xD,0x0)/HD(2,GPT,C3AD6E1F-42A9-4F06-98A4-5CC879F6554E,0x64028,0x6F80FC8)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,35D21426674BBC44A2CC3FC394EAD3BC)/\1DF588CB-10D4-48C2-BE99-71CF80DD2FBF\System\Library\CoreServices\boot.efi (0/0)


02:217 00:000 OCB: Trying to get label from \1DF588CB-10D4-48C2-BE99-71CF80DD2FBF\System\Library\CoreServices\.disk_label.contentDetails
02:229 00:012 OCB: Registering entry Big_Sur (T:2|F:0|G:0|E:1) - PciRoot(0x0)/Pci(0x14,0x0)/USB(0xD,0x0)/HD(2,GPT,C3AD6E1F-42A9-4F06-98A4-5CC879F6554E,0x64028,0x6F80FC8)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,35D21426674BBC44A2CC3FC394EAD3BC)/\1DF588CB-10D4-48C2-BE99-71CF80DD2FBF\System\Library\CoreServices\boot.efi

 

  • Thanks 1
Link to comment
Share on other sites

32 minutes ago, Blu24 said:

I think it's to do with the new file structure. At the moment you can access your Catalina HD from Big Sur but you can't access Big Sur from Catalina. Have you noticed "Incompatible Disk info" Top right? when you boot into Catalina?

Screenshot 2020-07-12 at 12.42.18.png

 

no ...i fallow you long tine, since 5 days... you are wrong in 90 % cases ..open diskutility , select data dis of big sur , open in finder ... you can copy anythyngs in this place

Link to comment
Share on other sites

34 minutes ago, Blu24 said:

I think it's to do with the new file structure. At the moment you can access your Catalina HD from Big Sur but you can't access Big Sur from Catalina. Have you noticed "Incompatible Disk info" Top right? when you boot into Catalina?

 

 

I can't explain myself well, sorry. When I boot on the Big Sur disk, OC only displays the data partition of Big Sur and not the System partition. So I have to boot on the data partition to start Big Sur. I hope that it's clearer.

 

I will continue the investigations proposed by Fusion71au

Link to comment
Share on other sites

1 hour ago, manmo71 said:

@MorenoAv I have just edited the Platform-ID for iGPU in your config.plist, everything else remains untouched.

Replace your existing config.plist (after backing up a copy) with this one and give it a try.

If this does not work, then I am out of idea's for the moment.

 

config.plist

Changed config.plist, it boots have sound, graphic acceleration... but not HEVC yet...

Thanks anyway ... 

Link to comment
Share on other sites

On 7/11/2020 at 6:24 AM, Matgen84 said:

 

Good news :yes:
 

Re-download BS Beta 2, recreate USB with your EFI folder, launch install to USB hard drive .... Stuck "Less than a minute remaining" since 15 minutes :whistle:

Same problem trying to install on a USB3 flash drive.  I was able to install successfully on an external USB2 hard drive.  There was mention of the installer being unable to “bless” a USB3 drive in another forum (MacRumors).

  • Thanks 1
Link to comment
Share on other sites

1 hour ago, jlcdgd said:

Still. having the Memory problem... any ideas?

 

Please find enclosed my EFi X99 Designare EX, Intel Xeon CPU E5-2670 v3 @ 2.30GHz...

 

Spoiler

FullSizeRender.thumb.jpeg.0d8e07943ea69f36b70a532b0a1c6332.jpeg

 

 

add kernel path to config.plist/Kernel/Patch/..you will see the panic kext..

<dict>
				<key>Base</key>
				<string></string>
				<key>Comment</key>
				<string>10.16 Disable panic loaded kexts list</string>
				<key>Count</key>
				<integer>1</integer>
				<key>Enabled</key>
				<true/>
				<key>Find</key>
				<data>
				AIA6AHRE
				</data>
				<key>Identifier</key>
				<string>kernel</string>
				<key>Limit</key>
				<integer>0</integer>
				<key>Mask</key>
				<data>
				</data>
				<key>MaxKernel</key>
				<string>20.8.0</string>
				<key>MinKernel</key>
				<string>20.0.0</string>
				<key>Replace</key>
				<data>
				AIA6AOtE
				</data>
				<key>ReplaceMask</key>
				<data>
				</data>
				<key>Skip</key>
				<integer>0</integer>
			</dict>

 

 

Link to comment
Share on other sites

Finally my Big Sur beta 2 is running 99% with Opencore and I would like to thank everyone for helping each other in achieving such great hacks. I am waiting for the next challenge ;-).

 

The other strange thing is that when I want to modify system files I have to boot with Clover, as I still get error 66 when booting with Opencore and to be honest I don't mind, as I am learning quite a lot in the process. My Airplay is now also up & running after moving to AR5B95 wifi card. Trackpad with gestures was fixed by installing the VoodooPS2Controller-Mojave.kext in Library/Extensions, as Opencore did not want it at all and I will try later again. Now trying my luck with installing the second Intel WiFi in the 1/2 mini for the bluetooth and will let you know if I succeed ;-)

 

Well people of the palace I have succeeded with the installation of the second wifi card in the 1/2 mini slot of my dell, in order to have a working bluetooth from the Intel card, while I am getting wifi from the Atheros card and all is working :thumbsup_anim::):drool:

Edited by Takiller
Feedback as promised
  • Like 3
Link to comment
Share on other sites

2 hours ago, fusion71au said:

 

 

For disabling Authenticated Root, you can set the NVRAM csr-active-config parameter to 0x77080000 in OC config.plist, then resetting NVRAM through the OC boot menu or with booting to Big_Sur's Recovery/Installer USB and disabling it with csrutil in terminal (see my post on APFS Snapshot Procedure and the examples in it).

 

OC uses the content of the hidden text file /System/Volumes/Preboot/UUID/System/Library/CoreServices/.disk_label.contentDetails to label the macOS volume...

 

Also check your OC boot log eg if you have the debug version of OC, type in terminal

 


ioreg -lw0 -p IODeviceTree | grep boot-log | sort | sed 's/.*<\(.*\)>.*/\1/' | xxd -r -p

 

and you might see something like this output...


17:915 05:721 OCB: Should boot from 8. Big_Sur (T:2|F:0|G:0|E:1|DEF:0)
17:916 00:000 OCB: Perform boot Big_Sur to dp PciRoot(0x0)/Pci(0x14,0x0)/USB(0xD,0x0)/HD(2,GPT,C3AD6E1F-42A9-4F06-98A4-5CC879F6554E,0x64028,0x6F80FC8)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,35D21426674BBC44A2CC3FC394EAD3BC)/\1DF588CB-10D4-48C2-BE99-71CF80DD2FBF\System\Library\CoreServices\boot.efi (0/0)


02:217 00:000 OCB: Trying to get label from \1DF588CB-10D4-48C2-BE99-71CF80DD2FBF\System\Library\CoreServices\.disk_label.contentDetails
02:229 00:012 OCB: Registering entry Big_Sur (T:2|F:0|G:0|E:1) - PciRoot(0x0)/Pci(0x14,0x0)/USB(0xD,0x0)/HD(2,GPT,C3AD6E1F-42A9-4F06-98A4-5CC879F6554E,0x64028,0x6F80FC8)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,35D21426674BBC44A2CC3FC394EAD3BC)/\1DF588CB-10D4-48C2-BE99-71CF80DD2FBF\System\Library\CoreServices\boot.efi

 

 

Thanks a lot :) I follow all your explantations: 

 

  • OC Debug: I don't have any output with Ioreg command. macOS 10.16 recognizes the right names which is not the case with Opencore. Strange.

     

 

SOLVED :)  change name in the hidden text file /System/Volumes/Preboot/UUID/System/Library/CoreServices/.disk_label.contentDetails

 

 

Edited by Matgen84
  • Like 1
Link to comment
Share on other sites

2 hours ago, Blu24 said:

I think it's to do with the new file structure. At the moment you can access your Catalina HD from Big Sur but you can't access Big Sur from Catalina. Have you noticed "Incompatible Disk info" Top right? when you boot into Catalina?

Screenshot 2020-07-12 at 12.42.18.png

 

Blu24, yes that's what i observed too when i boot into Catalina. When in Catalina the incompatible disk message will appear and on the desktop i can see the update disk.

 

So you or anyone have any idea what is it and how to resolve it? Thanks.

Edited by greythorne
  • Like 1
Link to comment
Share on other sites

8 hours ago, SavageAUS said:


Worked great for me. Got stuck at step 5 I think it was until I entered the “”
Now my DW1820A works and also fixed the lag I had with the menu bar.


Sent from my iPhone using Tapatalk

glad to hear that your DW1820a is working now on big sur
me too have dw1820a, lately i have tried the tutorial from @fusion71au and successfully delete the APFS snapshots, but when i replace bigsur's IO8211Family kext with the older one from catalina 10.15.5, i got some wrong messages when rebuild kext cache. I still insist to reboot my laptop, then it's get stuck.
if you dont mind, could you share your IO8211Family.kext that working well with DW1820a?

Edited by aryaone
some typo
Link to comment
Share on other sites

14 minutes ago, greythorne said:

 

Bu24, yes that's what i observed too when i boot into Catalina. When in Catalina the incompatible disk message will appear and on the desktop i can see the update disk.

 

So you or anyone have any idea what is it and how to resolve it? Thanks.

When I made a clean install of Big Sur via USB, this doesn't happen.

Link to comment
Share on other sites

14 minutes ago, greythorne said:

 

Bu24, yes that's what i observed too when i boot into Catalina. When in Catalina the incompatible disk message will appear and on the desktop i can see the update disk.

 

So you or anyone have any idea what is it and how to resolve it? Thanks.

 

The only way I can access to BS from Catalina is from Disk Utility. Right click/Show in Finder. 

  • Like 1
Link to comment
Share on other sites

glad to hear that your DW1820a is working now on big sur me too have dw1820a, lately i have tried the tutorial from [mention=846696]fusion71au[/mention] and successfully delete the APFS snapshots, but when i replace bigsur's IO8211Family kext with the older one from catalina 10.15.5, i got some wrong messages when rebuild kext cache. I still insist to reboot my laptop, then it's get stuck.

if you dont mind, could you share your IO8211Family.kext that working well with DW1820a?

 

I used the one from iPixelGalaxy’s video.

https://mega.nz/file/AOoTXSCJ#P6lgSvNaj_LZp-lCG2kudZccuZ9-pn355hzOp0G-UhM

I’m not sure which version of macOS it’s from to be honest.

Make sure you run all commands after you have replaced the kext.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

8 minutes ago, greythorne said:

 

I made a clean install of BS beta 2 via USB, I observed the message and the update disk appearing.

 It doesn't happen to me, I can even use the data on the disk:

 

3LXFrRF.png

Link to comment
Share on other sites

@fusion71au still i m faiiure to deleting snapshot using booting usb installer 

First step work

Second step work

Third step work

Fourth step and fifth step  uuid of snapshot i didn' understand

I have installed big sur catalina and windows in one drive

Can you guide me clearly for better understanding

 

Edited by ameenjuz
edited
Link to comment
Share on other sites

 
 
 
 
 
 
 
 
6
2 hours ago, corint1 said:

 

no ...i fallow you long tine, since 5 days... you are wrong in 90 % cases ..open diskutility , select data dis of big sur , open in finder ... you can copy anythyngs in this place

I didn't know you could access Big Sur using the open finder, Technically the file structure is different because you can not access the normal way, like previous versions of macOS. 

Regarding I'm wrong In 90% of cases. That's your opinion!!!

I'm only going by my experience. I can install Big Sur Via USB, using my original EFI settings, I compiled from source(OC 0.6.0) :)

  • Like 1
Link to comment
Share on other sites

55 minutes ago, ameenjuz said:

@fusion71au still i m faiiure to deleting snapshot using booting usb installer 

First step work

Second step work

Third step work

Fourth step and fifth step  uuid of snapshot i didn' understand

I have installed big sur catalina and windows in one drive

Can you guide me clearly for better understanding

 

1. The UUIDs are something like this "1486A08F-9233-452B-85F3-50D6B1ECE523B"

2. When I run this command "diskutil apfs listSnapshots <volume mount point>" this will give you a list of UUID, take a good look at the output, in my case I had two

3. This command "diskutil apfs deleteSnapshot <volume mount point> -uuid <uuid of snapshot>" will delete the UUID you must do with each. Example "diskutil apfs deleteSnapshot <volume mount point> -uuid 1486A08F-9233-452B-85F3-50D6B1ECE523B"

4. Finally to verify that all the UUIDs have been removed run again "diskutil apfs listSnapshots <volume mount point>" and the output of this should be "No Snapshots for disk"

  • Like 2
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...