Jump to content

[pre-release] macOS Big Sur


3,698 posts in this topic

Recommended Posts

@Matgen84 yep. Signed it is.

 

@MorenoAv and @eSaF what do you guys have set on your Misc > Boot > PickerAttributes? I had mine set to 1 and was seeing "Preboot" as volume name on my picker screen, then while reviewing things I changed to 3 and it instantly changed the volume name to "Big Sur" during picker. Which make sense, according to the documentation: that's how I labeled my volume.

Edited by Alex HQuest
  • Thanks 2
Link to comment
Share on other sites

35 minutes ago, Alex HQuest said:

@Matgen84 yep. Signed it is.

 

@MorenoAv and @eSaF what do you guys have set on your Misc > Boot > PickerAttributes? I had mine set to 1 and was seeing "Preboot" as volume name on my picker screen, then while reviewing things I changed to 3 and it instantly changed the volume name to "Big Sur" during picker. Which make sense, according to the documentation: that's how I labeled my volume.

 

@Alex HQuest Change PickerAttributes to 3, I always see "Preboot" as volume name on my picker screen. Reset NVRAM twice, no change.

 

EDIT: I forgot to label my Big Sur Volume. I don't know how.

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

To update Big Sur volume label from PreBoot to what ever you named it (if you named it) install something that updates the preboot volume like intel power gadget (then remove if unwanted) reboot, success!


Sent from my iPhone using Tapatalk

  • Like 4
Link to comment
Share on other sites

@Alex HQuest Actually to change Preboot name I did nothing, apart from after the installation I went into Disk Utility and ran a First Aid Scan on all BS volumes and then done a reboot and it was changed to the name that I designated the disk as. Whether this had a bearing on the name change I don't know but judging by the numerous methods advocated by others, who knows what actually triggers the change. As we go deeper toward the final release, probably we will know more.

  • Like 4
Link to comment
Share on other sites

47 minutes ago, eSaF said:

@Alex HQuest Actually to change Preboot name I did nothing, apart from after the installation I went into Disk Utility and ran a First Aid Scan on all BS volumes and then done a reboot and it was changed to the name that I designated the disk as. Whether this had a bearing on the name change I don't know but judging by the numerous methods advocated by others, who knows what actually triggers the change. As we go deeper toward the final release, probably we will know more.

 

Hi @eSaF I follow your procedure to change Preboot name: don't work for me. It does not matter. We will see the next Beta and the release of course.

Link to comment
Share on other sites

On 8/10/2020 at 3:47 PM, chris1111 said:

 OC 0.6.1 03 August 2020 Its always update when I have time

You can try USB Installer for make Update ??

The update is made, because I inserted this SSD in another PC, with its own EFI, and boots up Big Sur Beta 4, but I can´t boot Beta 4 on my 2570P, in the firsts lines, I could see "Couldn´t alloc class AppleIntelPCHSeriesAHCI"

I just imagined that all things in relation with AHCI, is a problem with SATA or SSD or Intel Chipset.

Thanks in advance

Cheers.

  • Confused 1
Link to comment
Share on other sites

19 minutes ago, asdesoso said:

The update is made, because I inserted this SSD in another PC, with its own EFI, and boots up Big Sur Beta 4, but I can´t boot Beta 4 on my 2570P, in the firsts lines, I could see "Couldn´t alloc class AppleIntelPCHSeriesAHCI"

I just imagined that all things in relation with AHCI, is a problem with SATA or SSD or Intel Chipset.

Thanks in advance

Cheers.

Try to change the kext VodooPS2Controller or make sure your kext is in the good order in config.plist

Link to comment
Share on other sites

7 minutes ago, chris1111 said:

Try to change the kext VodooPS2Controller or make sure your kext is in the good order in config.plist

Hi Chris, I have the latest version of VoodooPS2Controller, which is 1.9.2. What kext I must try?

Thanks.

Link to comment
Share on other sites

1 minute ago, asdesoso said:

Hi Chris, I have the latest version of VoodooPS2Controller, which is 1.9.2. What kext I must try?

Thanks.

Try this one

https://github.com/acidanthera/VoodooPS2/releases/tag/2.1.6

make sure is good setting up in config because this kext as more plugins

Link to comment
Share on other sites

5 minutes ago, asdesoso said:

I will try it, but which more plugins I need to put into Kexts folder, VoodooInput?

Thanks.

<dict>
				<key>BundlePath</key>
				<string>VoodooPS2Controller.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/VoodooPS2Controller</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>BundlePath</key>
				<string>VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Trackpad.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/VoodooPS2Trackpad</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>BundlePath</key>
				<string>VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Keyboard.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/VoodooPS2Keyboard</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>BundlePath</key>
				<string>VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Mouse.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/VoodooPS2Mouse</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>BundlePath</key>
				<string>VoodooPS2Controller.kext/Contents/PlugIns/VoodooInput.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/VoodooInput</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>

Replace the kext in kexts folder then setup config.plist

Edited by chris1111
Link to comment
Share on other sites

1 minute ago, chris1111 said:

<dict>
				<key>BundlePath</key>
				<string>VoodooPS2Controller.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/VoodooPS2Controller</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>BundlePath</key>
				<string>VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Trackpad.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/VoodooPS2Trackpad</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>BundlePath</key>
				<string>VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Keyboard.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/VoodooPS2Keyboard</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>BundlePath</key>
				<string>VoodooPS2Controller.kext/Contents/PlugIns/VoodooPS2Mouse.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/VoodooPS2Mouse</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>
			<dict>
				<key>BundlePath</key>
				<string>VoodooPS2Controller.kext/Contents/PlugIns/VoodooInput.kext</string>
				<key>Comment</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>ExecutablePath</key>
				<string>Contents/MacOS/VoodooInput</string>
				<key>MaxKernel</key>
				<string></string>
				<key>MinKernel</key>
				<string></string>
				<key>PlistPath</key>
				<string>Contents/Info.plist</string>
			</dict>

 

This is for the config.plist, right?

Link to comment
Share on other sites

50 minutes ago, asdesoso said:

The update is made, because I inserted this SSD in another PC, with its own EFI, and boots up Big Sur Beta 4, but I can´t boot Beta 4 on my 2570P, in the firsts lines, I could see "Couldn´t alloc class AppleIntelPCHSeriesAHCI"

I just imagined that all things in relation with AHCI, is a problem with SATA or SSD or Intel Chipset.

Thanks in advance

Cheers.

 

I had the problem of my HP not being able to find any internal drives.  Using VoodooI2C.kext solved the problem for me.  But you only need one VoodooInput.kext.  I deleted mine from VoodooPS2Controller.kext and only kept the one in VoodooI2C.kext.

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

10 minutes ago, mnfesq said:

 

I had the problem of my HP not being able to find any internal drives.  Using VoodooI2C.kext solved the problem for me.  But you only need one VoodooInput.kext.  I deleted mine from VoodooPS2Controller.kext and only kept the one in VoodooI2C.kext.

In my case I can see all internal drives, but thank you for your note.

Best regards.

Link to comment
Share on other sites

14 minutes ago, chris1111 said:

Replace the kext in kexts folder then setup config.plist

I replaced it, ProperTree has take the plugins from acidanthera´s VoodooPS2Controller, but it stucks at AppleKeyStore failed, seeing again in the firsts lines "Couldn´t alloc class AppleIntelPCHSeriesAHCI".

The problem was after updating Beta 3 to Beta 4.

I upload here my 2570P´s current EFI.

EFI.zip

Link to comment
Share on other sites

Guys got rid of the problematic X299 platform. It was just so unreliable with everything. Got Gigabyte Z490 Vision G and Intel Core i5 10600 CPU. I am seeing immediate responsiveness in normal Windows and macOS Big Sur operations. I am sharing my EFI OpenCore folder for anyone interested in this model. USB ports are mapped and USBPorts.kext is used instead of SSDT-UIAC.aml and  SSDT-EC-USBX.aml. 

If you want to map your own ports,

  1. Enable SSDT-EC-USBX.aml
  2. Enable USBInjectAll.kext
  3. Disable USBPorts.kext

Use Hackintool to map.

 

What is working? Everything if you have a Discreet AMD GPU. 

OC 0.6.0 EFI Gigabyte Z490 Vision G Big Sur.zip

  • Like 2
Link to comment
Share on other sites

3 hours ago, Matgen84 said:

 

Hi @eSaF I follow your procedure to change Preboot name: don't work for me. It does not matter. We will see the next Beta and the release of course.

I just installed Intel power Gadget and the volume name changed automatically from Preboot to Big Sur. Easy enough :)

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

47 minutes ago, asdesoso said:

I replaced it, ProperTree has take the plugins from acidanthera´s VoodooPS2Controller, but it stucks at AppleKeyStore failed, seeing again in the firsts lines "Couldn´t alloc class AppleIntelPCHSeriesAHCI".

The problem was after updating Beta 3 to Beta 4.

I upload here my 2570P´s current EFI.

EFI.zip

I think order of your kext is not good try this one

 

config.plist.zip

  • Like 2
Link to comment
Share on other sites

6 minutes ago, chris1111 said:

Stange issue ?

The system starts up to something more than a half, but can´t reach to the Desktop.

As I can see in your HP OC Guide in Github, you mentioned BIOS versions F.61, F.62 and F.64, but I have in my EliteBook 2570P, the F.73, I don´t know if it is a problem.

Edited by asdesoso
BIOS
Link to comment
Share on other sites

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