Jump to content

[pre-release] macOS Big Sur in VMWare


1,188 posts in this topic

Recommended Posts

4 minutes ago, CMMChris said:

Guys, how often do I need to repeat that I booted Big Sur with the latest RELEASE of Clover and a custom kernel patcher? The necessary commits have not yet been submitted. It's experimental and Slice is not involved with it. Don't even try to build his last commit, it breaks kext injection and kernel patcher.

I'm not really expert. But can you explain me how you got a custom kernel patcher? I'd like to try that too. Thank you :D

Link to comment
Share on other sites

4 minutes ago, thepickboy said:

Hi all, I installed to external HDD using Vm method. when I try to boot from HDD (not on vm) I get stuck on this lines. anynone can help?

Attach the external HDD to another USB port and try again.

Link to comment
Share on other sites

2 hours ago, The Tech said:

Any idea why the AirportBrcmFixup isn't working?

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. 

  • Like 1
Link to comment
Share on other sites

Hey guys,

 

I have always used clover until now, but I am giving OC a try for BigSur. I followed the official guide to build my EFI for my hardware (skylake) and added the necessary beta flags. I am posting the outputs when I try to boot the BigSur Installer and my existing Catalina that I boot with clover. Please help me if you have any idea where the problem might be.

 

Thank You!

 

Laptop

Intel Generation: Skylake

Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz

Intel HD Graphics 530

 

scpu failed to get system model is the BigSur verbose (the other one is Catalina).

Catalina.JPG

BigSur.JPG

Link to comment
Share on other sites

3 minutes ago, C.Frio said:

hi...

Big Sur beta2..!!?

 

661683691_ScreenShot2020-06-28at12_31_49PM.png.193439fd24196199b1fcb6b110053095.png

 

c.frio

 

No, for Catalina.

Bir Sur or is 10.16 or 11.0

  • Like 1
Link to comment
Share on other sites

13 hours ago, Zhen-zen said:

@tunglamvghy1210 @Anonym323 my bad, I wiped the partition and installed it again. Now I know what's going on.

Use the terminal to ls what's in the data partition. If the folder called "macOS install data" still exist, then the system files are still not extracted. Also, after the stage 1, there should be a new volume called "Update", which can also be an indicator.

So the first reboot may end earlier than expected. It just shows "About 29 minutes remaining…" and then rebooted. It seems some data are written to the nvram and cause a RTC loss on my desktop. But it didn't prompt the detail after I rebooted into Catalina.

That also happened last time, but I thought it's something like DW1820a PCIe bug so I just rebooted and didn't write about it. And I suppose you're also stucked at this stage.

So reboot into the installer one more time and wait for the system file to be extracted completely. This time it should reboot after like 19 minutes remaining (but not 29 minutes!). Sorry for the confusion.

Also please check step 5 for a fix on Safari. It's not updated automatically.

I've got loop boot with many lines "Service exited due to SIGABRT" how to fix it??

 

Edited by tunglamvghy1210
Link to comment
Share on other sites

11 minutes ago, Djlild7hina said:


I could not get it to boot with this. Haven’t looked further but the rename from rtc to rtc0 isn’t working for me.

This is possible solution for stop on "PCI configuration end" only!!!

Link to comment
Share on other sites

2 minutes ago, thepickboy said:

Great man, you made my day, but after boot completes I can see only a grey screen and the cursor

Cool :)

If you are using a USB 2.0 port that might be normal, it might take some time for the OS to load the welcome window (if it is in the first stage of the boot process that you are waiting for) give it some time.

Link to comment
Share on other sites

Just now, Cyberdevs said:

Cool :)

If you are using a USB 2.0 port that might be normal, it might take some time for the OS to load the welcome window (if it is in the first stage of the boot process that you are waiting for) give it some time.

I gave it half an hour on usb and then I attached to sata port and the result is the same. Maybe some igpu related issue? i can boot only with -disablegfxfirmware but my smbios is imac 19,1 which needs also igpu

Link to comment
Share on other sites

7 minutes ago, thepickboy said:

I gave it half an hour on usb and then I attached to sata port and the result is the same. Maybe some igpu related issue? i can boot only with -disablegfxfirmware but my smbios is imac 19,1 which needs also igpu

Well I'm not sure what's going on, what's your hardware spec (you can update your profile and add them to your signature) and how you installed it.

Link to comment
Share on other sites

×
×
  • Create New...