[pre-release] macOS Big Sur

[SavageAUS]

[mention=1083558]SavageAUS[/mention] I would not wait on OC team: they already stated this is not the intended use case for their loader. The intent of OC is to be as much similar to the real Apple boot loader. Therefore it is on us (end users) to fix ACPI tables (amongst other things) so the system boots under OS A or B. Might sound unfortunate but I understand now their rationale in such move and I too agree it make sense.

Is it not true that real Macs can boot windows from the picker without having to patch dsdt to avoid ACPI errors on windows? I get it, this is a hackintosh so it’s different but if OC was intended to be “as Mac as possible” then windows booting should be as important. Not having a dig at anyone, just my thoughts, I really appreciate all the work that everyone has done with this boot loader. Just wish booting windows was on the radar as not everything runs on macOS.


Sent from my iPhone using Tapatalk

[Stefanalmare]

5 minutes ago, SavageAUS said:

Is it not true that real Macs can boot windows from the picker without having to patch dsdt to avoid ACPI errors on windows? I get it, this is a hackintosh so it’s different but if OC was intended to be “as Mac as possible” then windows booting should be as important. Not having a dig at anyone, just my thoughts, I really appreciate all the work that everyone has done with this boot loader. Just wish booting windows was on the radar as not everything runs on macOS.


Sent from my iPhone using Tapatalk

Use refind. Personally, I have a lot of benefit from they work. After, I adapt all to my needs. Not cool to give advice to someone work if you're not involve.

[Alex HQuest]

7 minutes ago, SavageAUS said:

Is it not true that real Macs can boot windows from the picker without having to patch dsdt to avoid ACPI errors on windows? I get it, this is a hackintosh so it’s different but if OC was intended to be “as Mac as possible” then windows booting should be as important. Not having a dig at anyone, just my thoughts, I really appreciate all the work that everyone has done with this boot loader. Just wish booting windows was on the radar as not everything runs on macOS.

It is true and you are correct: real Apple hardware will boot Windows right off the picker, regardless of set on NVRAM or selected at boot time. Now, if Bootcamp does add or not ACPI patches during boot time to be loaded and interpreted by the Apple boot loader, or if patches its entire and primary ACPI tables, provided by Apple during their own firmware updates, I do not know: I understand that one way or another they have to, since Apple support only up to a certain version of Windows OS on a specific Apple device. So they too "fix" their own ACPI tables making them able to run the newer Windows OS, as they have done before. How they do it is unknown to me - my gut tells me this is done over firmware updates and not at boot load time.

 

Which then brings us back to where we are. Since we want macOS on our non-supported, non-approved hardware, we are the ones that have to fix/provide what the hardware vendor should had done. The vendor never would as they cannot officially endorse running macOS on non-Apple hardware without being sued. And since OC follows Apple's loader behavior, we are on our own. A stance that has multiple problems. For one, something even the UEFI group recognizes as issues within their own world (see image below). And the risk of creating incompatible ACPI tables that works on macOS and not on Windows, which was exactly the problem we were trying to fix.

 

So while yes, the "most versatile" option would be for OC to not enforce ACPI changes if _OSI is anything other than "Darwin", seeing how OC is also used on real Apple hardware, and with their approach of "vanilla", unless enough people would make them to change their minds...

 

I don't speak by the Acidanthera team and I'm in no way related to the group. We can continue this discussion on the OpenCore section of this forum if needed so we don't sidetrack too much on the actual macOS Big Sur Beta topic.

 

Spoiler

 

[sonicthehedgehog2]

Just got stuck at a black screen after selecting install from OC menu....going to try arg -lilubetaall

[sonicthehedgehog2]

32 minutes ago, eSaF said:

Also check in config.plist CFG lock/unlock corresponds with the actual CFG settings of your M/B, wrong setting can also lead to black screen.

Thanks eSaF, that's very true, I'm currently using the preconfigured SSDTs. When I dumped my DSDT using Clover (using F4) it gave me lots of (some 30 odd) SSDTs. should I install all of them. I was hoping to keep EFI as streamline as possible. Still that will be next on my list. I'll do a new dump of DSDT tomorrow.

[sonicthehedgehog2]

4 minutes ago, eSaF said:

You need to read the OC Guide to see exactly what kexts and SSDTs you need for your system, 30 of anything sounds a bit excessive to me.

Thanks eSaF, I'll give it another go.

[bisdak4920]

16 hours ago, diskeeper said:

Make sure You have only the necessary files in Your Drivers folder and in the config.plist UEFI/Drivers section. I struggled with the same thing.

 

  Hide contents

 

Can you share your installer EFI sir.

[mnfesq]

11 minutes ago, LIMITANT said:

Please Help 

 

Panic cpu caller 0 

vm_map_delete ......

no map entry at 0xfffff888888 ...

  Hide contents

 

 

Looks like you're using Clover.  Clover doesn't work with Beta 4 yet.  The only way to boot to Beta 4 is OC.

[diskeeper]

7 hours ago, bisdak4920 said:

Can you share your installer EFI sir.

Here You are Sir!

 

EFI

 

Removed my personal datas in Platforminfo, but leaved the iMacPro1,1.

 

You need to change the XXXXXXXXXX values that the picture shown to Yours and the 123456789876 ROM value to Your network cards MAC address.

 

Spoiler

 

Edited August 9, 2020 by diskeeper

[sonicthehedgehog2]

10 hours ago, sonicthehedgehog2 said:

Just got stuck at a black screen after selecting install from OC menu....going to try arg -lilubetaall

Mmmm...-lilubetaall made no difference.

 

I've also checked my SSDTs against the guide which didn't take long as it only recommends one for my PC (SSDT-EC) as I have an Ivy Bridge system running on a series 7 motherboard. I've had to guess at some stuff too like renaming a "delete" to "block" in the config.plist to make the "sanity checker" green light my config.plist.

 

I think I shall try MaLdon's guide next

[manmo71]

3 hours ago, LIMITANT said:

It's OC 0.6 and it boots Catalina 10.15.6 without problems...

Any idea? Thx

@LIMITANT Is this happening at the beginning of the installation or half way through the installation?

 

I had similar KP's after the sealing stage, which sort of kept failing with KP's.

I got myself a faster USB drive, downloaded a fresh copy of the BS Public Beta and created the installer and never had to look back.

Try a different USB drive after you ensure you have downloaded a good copy of the installer using CrazyBirdy's script.

Ensure you have OC updated to the latest, with the kexts.

Also try FakeSMC instead of VirtualSMC, sometimes, it works.

[mnfesq]

6 hours ago, LIMITANT said:

I use OC 0.6 , it boots Catalina 10.15.6 just fine , also i used it to install High Sierra without problems.

 

To get Beta 4 to boot, I needed to use OC 0.6.1.  My OC 0.6.0 did not work.  The fact that your OC can boot Catalina and High Sierra means that you can use those versions of macOS to your heart's content but you may never be able to boot Big Sur.  This thread exists because what worked for Catalina doesn't work for Big Sur. When you're ready, try it out and see. Also, I believe I got this error when I took a USB drive that I had created for Beta 3 and copied the Beta 4 app to it rather than using the createinstallmedia function to make a brand new USB drive.  For me, shortcuts always lead to failure.  Not saying this is what you did but it's what I did.  When I made a new USB installer just for Beta 4, I didn't have the problem with the prelinked copy of kexts having a different UUID.

Edited August 9, 2020 by mnfesq

[manmo71]

Spoiler

 

@LIMITANT Try updating your O.C to 0.6.1 as @mnfesq has recommended and also try resetting your NVRAM before you start your install. 

 

See if that helps...

Edited August 9, 2020 by manmo71

[Max.1974]

8 hours ago, LIMITANT said:

@manmo71

Yes it's happening in the beginning of installation 

I'm using that script , I've downloaded beta 4 and it's not corrupted as I've test it from inside Catalina before creating the installer USB ..

My USB drive is fast usb 3.0 sandisk  32 gb .. my others USB  2.0 drives is only 8 gb unfortunately 

 

I use OC 0.6 , it boots Catalina 10.15.6 just fine , also i used it to install High Sierra without problems..

I did that .. also I tried to use the minimum Kexts & Drivers and SSDTs in OC .. same result all time ...

I don't know how to solve it , ive searched google without any similar results .. 

Thank you for your suggestions 

 

 

Hi @LIMITANT if you wanted, im share my EFI folder (im change only serials). 

Just don't forget the RESET NVRAM always that you change your EFI. 

If was possible, try put only one EFI in HD/SSD folder, and preserve in backup your EFI. 

If works, use without modified essentials. 

Another think is my desktop was similar of your...

I hope help you and another with same chipsets...

EFI-z170-i7-6700k-Opencore-AMD-RX.zip

[d5aqoep]

Anyone knows how to make About this Mac to display my Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz CPU to display it's name correctly?

Right now it it displays under Processor 3.3Ghz

That's it. No name. Just speed. It's cosmetic but would be great to learn how to spoof name under OpenCore.

 

 

[Max.1974]

41 minutes ago, LIMITANT said:

I'd like to thank you very much and for everyone else as well @mnfesq @manmo71 

I think it was my fault as i didn't mention my PC that has this issue ... 

It's " Haswell 4600 Dell precision m6800 " this Laptop always problematic 

I will try again tomorrow with all your useful suggestions... at the moment i can't compile OC 0.6.1 as I haven't xcode installed in my machine ... 

 

Try this, take a shoot!! 

 

EFI-OC-Lenovo-E470-i5-7200u-Skylake.zip

[Max.1974]

7 minutes ago, LIMITANT said:

What version of OC ? I want to compile the latest one 0.6.1 as version 0.6 failed.. 

 

Last kexts and drivers..im just upgrade that...works for install BS B4 and run final boot...

Just not use two EFI at the same time...

Put in your EFI folder from HD, and back up your EFI in another place...usb for exemple. 

Just not give up...because Hackintosh require effort and patient...

Edited August 9, 2020 by Max.1974

[manmo71]

After I installed BS Public Beta, now it has happened a couple of times.

While playing youtube videos on Chrome, if I attempt randomly forwarding my timeline or do the same on VLC, to play a video file when having youtube running, my system freezes and on reboot I get this error.

 

 

Spoiler

 

Can someone figure out what this is pointing to?

[Max.1974]

4 minutes ago, manmo71 said:

After I installed BS Public Beta, now it has happened a couple of times.

While playing youtube videos on Chrome, if I attempt randomly forwarding my timeline or do the same on VLC, to play a video file when having youtube running, my system freezes and on reboot I get this error.

 

 

  Hide contents

 

Can someone figure out what this is pointing to?

 

Hi my friend, im think is occurs because is a fresh install...try upgrade from Catalina...just for try...!!!

Im recommend IINA video player....much better than VLC 

Edited August 9, 2020 by Max.1974

[Loloflat6]

3 hours ago, d5aqoep said:

Anyone knows how to make About this Mac to display my Intel(R) Core(TM) i9-7900X CPU @ 3.30GHz CPU to display it's name correctly?

Right now it it displays under Processor 3.3Ghz

That's it. No name. Just speed. It's cosmetic but would be great to learn how to spoof name under OpenCore.

 

 

 

My Intel(R) Core(TM) i5-7640X CPU @ 4.00GHz is named 4 GHz Quad-Core Intel i5 on my best build on Gigabyte X299 UD4 :

 

Seems OK for me, i did nothing special :

 

Spoiler

 

	   <dict>
			<key>Cpuid1Data</key>
			<data></data>
			<key>Cpuid1Mask</key>
			<data></data>
		</dict>

 

 

 

[Max.1974]

31 minutes ago, LIMITANT said:

 

That's true 100% .. I'm a clover user from so long time .. and OC is not comfortable for me till this moment.. maybe because i want to try BS on this machine I'm doing all this effort.

I think i have to wait till BS official release , Slice still have enough time to adapt Clover for BS with other Devs. and genius testers ...

Everything will be fine and easy 

 

Try create your own OC with PAVO OC Builder, its very useful. Try to start fresh install with iMacPro, 1,1 with Premade EFI from MaLD0n website. Don't forget ever to Reset Nvram, and use only one EFI...not use vm ware images.

Good Luck 

Im was Clover user for long time, but OC is, in fact, more easy, and im confess if not was MaLD0n, all guys help us, and theme from Chris1111 its will be more hard to put on up...

Im notice that more easy and functionally use Big Sur from update and not fresh install. Many programs still works after that, for exemple, Paragon NTFS and Internet Banking...

Edited August 9, 2020 by Max.1974

[SavageAUS]

Is anyone else having issues with AppleBusPowerController not loading in Big Sur? It loads in Catalina but the same OC EFI does not load ABPC in Big Sur according to ioreg. I’m trying to narrow down my sleep issue and I came across this.


Sent from my iPhone using Tapatalk

[CMMChris]

AppleBusPowerController loads fine for me. Attaches to IORTC like in Catalina.

[SavageAUS]

AppleBusPowerController loads fine for me. Attaches to IORTC like in Catalina.

Laptop? Desktop? Mines a laptop, it already has a EC device in my dsdt.
Anyone with a laptop can check for AppleBusPowerController and if it exists please post how.


Sent from my iPhone using Tapatalk

[asdesoso]

Hi @chris1111,

After update from Beta 3 to Beta 4 (Big Sur), Catalina is working fine, with the same EFI, on my HP EliteBook 2570P, I stuck at this point, the OS only boots up with vsmcgen=1 enabled, I used your post-install OC pkg from GitHub.

Thanks in adavnce.

Cheers.