Jump to content

[pre-release] macOS Big Sur in VMWare

gengik84
 Share
1,188 posts in this topic

Recommended Posts

yapan4
yapan4
Posted
Posted
9 minutes ago, Djlild7hina said:

Yeah, it should work.  Not sure why it’s not working for me. Have you tried it?

Don't work on my C422 Mobo, so I ask how to X299...

I can run kernel but still stop on "PCI configuration end"

20200628_192727.jpg

Link to comment
Share on other sites
mav96
mav96
Posted
Posted
58 minutes ago, tore2003 said:

I’m doing some experiments, with clover 5102 I can see the HDD where I installed Big Sur. But with clover 5119 it disappears. 

 

I tried both 5102 and 5119 and I can't see the BigSur volume. Can you share your apfs.efi from the 5102 Clover? Thanks!

Link to comment
Share on other sites
Gravarty
Gravarty
Posted
Posted (edited)

Are there any problems with Whatevergreen+Lilu in Big Sur? I was able to install the OS directly on the SSD in a VM without any problems. With OpenCore it also seems to boot "problem-free" but unfortunately the GPU (Radeon RX 590) does not work properly. -lilubetaall is included as a bootarg. Those colored lines appear first and then blackscreen.

 

I also uploaded my terrible configured OC config, i never used this bootloader before and just did some basic modifications. 

(ASUS STRIX Z270E Intel i7 7770k AMD Radeon RX 590)

 

EFI.zip

IMG_20200628_181044.jpg

Edited by Gravarty
Link to comment
Share on other sites
Cyberdevs
Cyberdevs
Posted
Posted
1 minute ago, Gravarty said:

Are there any problems with Whatevergreen+Lilu in Big Sur? I was able to install the OS directly on the SSD in a VM without any problems. With OpenCore it also seems to boot "problem-free" but unfortunately the GPU (Radeon RX 590) does not work properly. -lilubetaall is included as a bootarg. Those colored lines appear first and then blackscreen.

 

I also uploaded my terrible configured OC config, i never used this bootloader before and just did some basic modifications. 

I'm using iMac18,1 SMBIOS to avoid the black screen issue on my R9 270X GPU for now, the AGDP patches don't seem to work I guess.

  • Like 1
Link to comment
Share on other sites
yapan4
yapan4
Posted
Posted (edited)
Just now, Djlild7hina said:

 

Hmm not sure then.  maybe the range is different on C422?  If I use the SSDT I get ACPI errors.  AE_ALREADY_EXISTS and _STA namespace lookup failure

I tryed both patch and SSDT, - no errors and also no effect. So behavior on C422 and X299 some different.

Thank you.

Edited by yapan4
Link to comment
Share on other sites
The Tech
The Tech
Posted
Posted
3 hours ago, luki1979 said:

Cards from 2012/2013 Macs and earlier are blocked in Big Sur, there is workaround by installing 


IO80211Family.kext

from Catalina but it's not pretty due to new APFS and system snapshots. 

Is all fixed now. 

 

Thanks for all the help :)

 

  • Thanks 1
Link to comment
Share on other sites
luki1979
luki1979
Posted
Posted

From my understanding OS now boots from snapshot of the system. Making any patches to kexts and replacing system kexts on the fly impossible hence Clover failing immediately. OpenCore is somehow injecting essential third party kexts but when I’ve tried load IO80211Family.kext from Catalina with OC it won’t boot. Instant KP.

3 minutes ago, The Tech said:

Is all fixed now. 

 

Thanks for all the help :)

 

What card do you have and did you make it work. I’m interested in this stuff.;)

Link to comment
Share on other sites
The Tech
The Tech
Posted
Posted
3 minutes ago, luki1979 said:

From my understanding OS now boots from snapshot of the system. Making any patches to kexts and replacing system kexts on the fly impossible hence Clover failing immediately. OpenCore is somehow injecting essential third party kexts but when I’ve tried load IO80211Family.kext from Catalina with OC it won’t boot. Instant KP.

Hmm. I see. 

Link to comment
Share on other sites
luki1979
luki1979
Posted
Posted

https://medium.com/@andv/making-wifi-on-big-sur-unsupported-macs-with-failed-with-66-error-36c98e3f7965

 

here is a current method of replacing IO80211Family.kext but I think it’s dangerous and you would have to do it after every update most likely, this method is for the real Mac. I hope injecting and patching will be possible with future updates of OpenCore and Clover. 

Link to comment
Share on other sites
luki1979
luki1979
Posted
Posted
On 6/28/2020 at 9:54 PM, matgeo said:

For rebuilding cache can we still use sudo kextcache -i / ?

From my understanding system is loading from a snapshot, you don’t have access to system hence you can’t put the drive in read and write mode. Rebuilding cache won’t work, even if you manage to add something to system partition you won’t be able to boot as it won’t correspond to snapshot. Hence people boot from installation USB/ Recovery and use commands from there and building new bootable snapshot. Read what involved in simple kext replacing. https://medium.com/@andv/making-wifi-on-big-sur-unsupported-macs-with-failed-with-66-error-36c98e3f7965

On 6/28/2020 at 11:47 PM, wern apfel said:

After playing around, I can mount the drive without an error and delete kexts. I am not sure what helped, but will repeat any changes I made and let you know what helps.

 Interesting, did you try to reboot? 

Link to comment
Share on other sites
wern apfel
wern apfel
Posted
Posted
4 minutes ago, luki1979 said:

From my understanding system is loading from a snapshot, you don’t have access to system hence you can’t put the drive in read and write mode. Rebuilding cache won’t work, even if you manage to add something to system partition you won’t be able to boot as it won’t correspond to snapshot. Hence people boot from installation USB/ Recovery and use commands from there and building new bootable snapshot. Read what involved in simple kext replacing. https://medium.com/@andv/making-wifi-on-big-sur-unsupported-macs-with-failed-with-66-error-36c98e3f7965

 Interesting, did you try to reboot? 

Yes , rebooted a couple of times, it still works. I will reinstall to see if my assumption is correct. I think it's the new APFS FS.

kextcache also works  

kextcache -i /
kextcache -arch x86_64 -local-root -all-loaded -kernel /System/Library/Kernels/kernel -prelinked-kernel /Library/Apple/System/Library/PrelinkedKernels/prelinkedkernel -volume-root / /Library/Extensions /AppleInternal/Library/Extensions /Library/Apple/System/Library/Extensions /System/Library/Extensions
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
KernelCache ID: 35C54583567155D1C30E7D0CF0930038
symlink("../../../PrelinkedKernels/prelinkedkernel", "/Library/Apple/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 2 (No such file or directory)
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for /Library/Apple/System/Library/Extensions/AppleMobileDevice.kext: IOCFUnserialize: syntax error near line 1.

 

Link to comment
Share on other sites
+ira
+ira
Posted
Posted (edited)

Hi everyone,

 

Finally got a "vanilla" macOS Big Sur running here, no VM, no real Mac install, no pre-build image.

 

I'll try my best to describe the processes:

 

Build:

 

i5 7500

Gigabyte B250M-D3H

 

Prep:

 

I was running the latest Catalina version.

Enrolled to beta channel.

Downloaded the 10.16 update.

First time it got corrupted and the download finished 80% of the way.

Downloaded it again.

I tried the createinstallmedia method on a 8GB thumb drive but it would not finish due to the size of the installation being ~10GB.

So I created a 16GB partition on a spare SSD that I have with High Sierra and ran the createinstallmedia on it.

I was a long time Clover user, so I had to port my setup to OpenCore.

I thoroughly followed the dortania OpenCore Desktop guide https://dortania.github.io/OpenCore-Desktop-Guide/ for my CPU family I didn't use anything from my previous Clover setup except for the SMBIOS information which I ended up generating a new one in later attemps.

 

This is my current EFI:

i5-7500-b250m-d3h-EFI.zip

 

Installation:

I tried the Install macOS Beta first, it would always give me a black screen but I could see it was doing something either by hearing fan noise or the LED indicator, eventually I would reboot whenever it stop doing whatever it was doing just to find out I didn't Install anything, then I moved on to the install media method.

 

The install media would lead to a black screen but I found out that if I change sources on my monitor back and forth it would display something eventually in some stages in others it would be just black but I went on whenever I saw activity hoping it was doing something, and it was.

 

I booted into High Sierra dozen of times between stages until I saw it was not going any further and most of the time it would lead to a pink screen with the Apple logo and a stationary progress bar.

 

So I did the prelinked kernel on Preboot volume method which you guys (can't remember who, thank you anyway) brought to us from MacRumors on another post and I was pretty sure this was the last attempt.

 

Tried to boot again. Nothing.

 

Then I came to the forum and downloaded the EFI posted by @Bios-PC here. (much thanks)

 

I copied most of the quirks and kexts but kept the specifics of my system.

 

And......

 

It booted!

 

The screen would go black and I had to use the switch sources method but eventually it went ahead and finished installing the system.

 

770065577_ScreenShot2020-06-28at16_49_12.thumb.png.a312890a19330d9f99ceeefb751c0414.png

 

I hope you guys find this post useful.

I'm sorry for not being able to pinpoint exactly what was needed to make it work, hopefully the OpenCore\Clover devs can workaround this soon.

 

Some photos from installation:

WhatsApp Image 2020-06-28 at 02.17.22.jpeg

WhatsApp Image 2020-06-28 at 02.31.43.jpeg

Edited by +ira
  • Like 6
  • Thanks 1
Link to comment
Share on other sites
junologue
junologue
Posted
Posted

Is it just me, or is this developer beta surprisingly stable? Except small visual things, i even find it more stable than 10.15.

Too bad it will take some time before some of my goto third party apps gets updated to support it.

 

But it seem very promising for this OS, imo.

  • Like 2
Link to comment
Share on other sites
Djlild7hina
Djlild7hina
Posted
Posted
1 hour ago, yapan4 said:

I tryed both patch and SSDT, - no errors and also no effect. So behavior on C422 and X299 some different.

Thank you.

 

You might have to do a DSDT dump and compare the SSDT-Range but yeah most likely different on C422 VS X299.  Talked to slav and found out that the SSDT will not work with AWAC due to already having STA.

Link to comment
Share on other sites
notsnsone
notsnsone
Posted
Posted
On 6/28/2020 at 9:43 PM, Gravarty said:

Are there any problems with Whatevergreen+Lilu in Big Sur? I was able to install the OS directly on the SSD in a VM without any problems. With OpenCore it also seems to boot "problem-free" but unfortunately the GPU (Radeon RX 590) does not work properly. -lilubetaall is included as a bootarg. Those colored lines appear first and then blackscreen.

 

I also uploaded my terrible configured OC config, i never used this bootloader before and just did some basic modifications. 

(ASUS STRIX Z270E Intel i7 7770k AMD Radeon RX 590)

 

EFI.zip

use latest nightlies of OC (use OC compare to make sure you are using a correct config.plist), lilu, weg, vsmc

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...