Jump to content

[pre-release] macOS Big Sur

gengik84

By gengik84,
in New Releases and Updates

 Share
3390 posts in this topic

Recommended Posts

MICKHAEL
MICKHAEL
Posted
Posted (edited)
31 minutes ago, mnfesq said:

 

Yes, definitely use -disablegfxfirmware to get rid of the problem of the igpu boot loop.

yes. its better, but in final stage of booting, its stuck, already for 30 minutes, on final APPLE loading screen after all verbose text. strange 
could be that USB3 port works on USB2 speed... but 30 minutes its something ..

Edited by MICKHAEL
mnfesq
mnfesq
Posted
Posted
45 minutes ago, MICKHAEL said:

yes. its better, but in final stage of booting, its stuck, already for 30 minutes, on final APPLE loading screen after all verbose text. strange 
could be that USB3 port works on USB2 speed... but 30 minutes its something ..

 

I get that with the new Clover v.5120.  I don't get that with the modified Clover version I picked up several pages ago in this thread.

MICKHAEL
MICKHAEL
Posted
Posted (edited)
8 hours ago, mnfesq said:
 
I get that with the new Clover v.5120.  I don't get that with the modified Clover version I picked up several pages ago in this thread.

Ohooo, interesting. I will try then tomorrow with that patched 5119
Thanks

 

UPDATE: stuck on same APPLE screen


Trimis de pe al meu Pixel folosind Tapatalk
 

Edited by MICKHAEL
lottenow
lottenow
Posted
Posted (edited)
10 hours ago, mnfesq said:

 

I get that with the new Clover v.5120.  I don't get that with the modified Clover version I picked up several pages ago in this thread.

 

@mnfesq & others: Can I ask you whether you can boot to Catalina with the same OC/Clover configuration as Big Sur?

 

I am now wondering whether the installer can be patched at all... and if so, how? I do not think OC can patch the installer, because whenever I block the "IOAHCIFamily.kext" and "IOAHCIBlockStorage.kext" under Kernel > Block properties, they are still being loaded.

 

I checked under Terminal during Install.

 

I am now trying to mess with my configuration to see if I can get the SATA controller recognised natively...

 

@ameenjuz: Do you have the decompiled .asl of your DSDT?

 

Great work guys!

Edited by lottenow
  • Like 1
MICKHAEL
MICKHAEL
Posted
Posted (edited)
3 hours ago, lottenow said:
 

[mention=270804]mnfesq[/mention] & others: Can I ask you whether you can boot to Catalina with the same OC/Clover configuration as Big Sur?

 

I am now wondering whether the installer can be patched at all... and if so, how? I do not think OC can patch the installer, because whenever I block the "IOAHCIFamily.kext" and "IOAHCIBlockStorage.kext" under Kernel > Block properties, they are still being loaded.

 

I checked under Terminal during Install.

 

I am now trying to mess with my configuration to see if I can get the SATA controller recognised natively...

 

[mention=1517934]ameenjuz[/mention]: Do you have the decompiled .asl of your DSDT?

 

Great work guys!

Hello. Yes. Clover (5120 or patched 5119) configuration are booting both, Catalina and Big Sur install.

But, Big Sur already installed just stuck on image 

Spoiler

IMG_20200722_025915.thumb.jpg.567fedf70278e0b4b1d4fb8295912ad9.jpg

Trimise pe al meu Pixel folosind Tapatalk

 

 

 

Edited by MICKHAEL
lottenow
lottenow
Posted
Posted
6 minutes ago, MICKHAEL said:

Hello. Yes. Clover (5120 or patched 5119) configuration are booting both, Catalina and Big Sur install.

But, Big Sur already installed just stuck on imagead201a50c5bff87924045589d9f288cc.jpg&key=ee71e204200149ff3d1999fd81ac47c19ebe3f870cca2707540ecd192acb616a

 

Trimis de pe al meu Pixel folosind Tapatalk

 

 

 

 

Add -v boot-flag to show verbose.

  • Like 1
lottenow
lottenow
Posted
Posted

Okay, interesting find. Although, no success.... I have modified the SATA-unsopported.kext as followings:

Spoiler 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>CFBundleGetInfoString</key>
	<string>Version 0.9.2, Copyright 2018, RehabMan (GPLv2)</string>
	<key>CFBundleIdentifier</key>
	<string>org.rehabman.injector.SATA-unsupported</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundleName</key>
	<string>SATA-unsupported</string>
	<key>CFBundlePackageType</key>
	<string>KEXT</string>
	<key>CFBundleShortVersionString</key>
	<string>0.9.2</string>
	<key>CFBundleSignature</key>
	<string>????</string>
	<key>CFBundleVersion</key>
	<string>0.9.2</string>
	<key>IOKitPersonalities</key>
	<dict>
		<key>Intel100Series-AHCI-unsupported</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.apple.driver.AppleACPIPlatform</string>
			<key>Chipset Name</key>
			<string>100 Series Chipset</string>
			<key>IOClass</key>
			<string>AppleACPIPCI</string>
			<key>IONameMatch</key>
			<array>
				<string>pci8086,a103</string>
			</array>
			<key>IOProbeScore</key>
			<integer>900</integer>
			<key>IOProviderClass</key>
			<string>IOACPIPlatformDevice</string>
			<key>Vendor Name</key>
			<string>Intel</string>
		</dict>
	</dict>
	<key>OSBundleRequired</key>
	<string>Local-Root</string>
</dict>
</plist>

 

 

And I can actually see that the correct SATA controller is being loaded, pci8086,a103, yet no SATA drive under Disk Utility/diskutil? Weird... it does match what I see in Catalina as well in terms of IOReg.

 

Spoiler

Schermata 2020-07-22 alle 20.44.44.png

 

 

Spoiler

14393A7B-AE2C-42AB-B8F1-DA278F691CA9.jpeg

 

  • Like 1
mnfesq
mnfesq
Posted
Posted
18 minutes ago, lottenow said:

Okay, interesting find. Although, no success.... I have modified the SATA-unsopported.kext as followings:

  Reveal hidden contents 


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>CFBundleGetInfoString</key>
	<string>Version 0.9.2, Copyright 2018, RehabMan (GPLv2)</string>
	<key>CFBundleIdentifier</key>
	<string>org.rehabman.injector.SATA-unsupported</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundleName</key>
	<string>SATA-unsupported</string>
	<key>CFBundlePackageType</key>
	<string>KEXT</string>
	<key>CFBundleShortVersionString</key>
	<string>0.9.2</string>
	<key>CFBundleSignature</key>
	<string>????</string>
	<key>CFBundleVersion</key>
	<string>0.9.2</string>
	<key>IOKitPersonalities</key>
	<dict>
		<key>Intel100Series-AHCI-unsupported</key>
		<dict>
			<key>CFBundleIdentifier</key>
			<string>com.apple.driver.AppleACPIPlatform</string>
			<key>Chipset Name</key>
			<string>100 Series Chipset</string>
			<key>IOClass</key>
			<string>AppleACPIPCI</string>
			<key>IONameMatch</key>
			<array>
				<string>pci8086,a103</string>
			</array>
			<key>IOProbeScore</key>
			<integer>900</integer>
			<key>IOProviderClass</key>
			<string>IOACPIPlatformDevice</string>
			<key>Vendor Name</key>
			<string>Intel</string>
		</dict>
	</dict>
	<key>OSBundleRequired</key>
	<string>Local-Root</string>
</dict>
</plist>

 

 

And I can actually see that the correct SATA controller is being loaded, pci8086,a103, yet no SATA drive under Disk Utility/diskutil? Weird... it does match what I see in Catalina as well in terms of IOReg.

 

  Reveal hidden contents

Schermata 2020-07-22 alle 20.44.44.png

 

 

  Reveal hidden contents

14393A7B-AE2C-42AB-B8F1-DA278F691CA9.jpeg

 

 

The only difference I see is that the device name in Big Sur is pci8086,a102 with a compatibility device name of pci8086,a103 and in Catalina, the device name is pci8086,a103 without the compatibility id.  I'm not sure what the impact, if any, is of that fact since my SATA controller is supported OOB - pci8086,9d03 so it can't be that device id spoofing doesn't work in Big Sur.

  • Like 1
MICKHAEL
MICKHAEL
Posted
Posted
Spoiler 14393A7B-AE2C-42AB-B8F1-DA278F691CA9.thumb.jpeg.c3b656d8abe997f95a25cfd43d121fec.jpeg
 
The only difference I see is that the device name in Big Sur is pci8086,a102 with a compatibility device name of pci8086,a103 and in Catalina, the device name is pci8086,a103 without the compatibility id.  I'm not sure what the impact, if any, is of that fact since my SATA controller is supported OOB - pci8086,9d03 so it can't be that device id spoofing doesn't work in Big Sur.
Okay, interesting. In Catalina I have pci8086,a102

Trimis de pe al meu Pixel folosind Tapatalk

lottenow
lottenow
Posted
Posted (edited)
6 minutes ago, mnfesq said:
  Reveal hidden contents

14393A7B-AE2C-42AB-B8F1-DA278F691CA9.jpeg

 

The only difference I see is that the device name in Big Sur is pci8086,a102 with a compatibility device name of pci8086,a103 and in Catalina, the device name is pci8086,a103 without the compatibility id.  I'm not sure what the impact, if any, is of that fact since my SATA controller is supported OOB - pci8086,9d03 so it can't be that device id spoofing doesn't work in Big Sur.


I realised after and changed it to a103 via OpenCore. Still, no luck. Would you be able to try the kext and use your pci8086,9d03?

 

Check before in Terminal using ‘ioreg -l’ and after the kext with the same command. It might work for you?

Edited by lottenow
MICKHAEL
MICKHAEL
Posted
Posted
10 minutes ago, ameenjuz said:

anybody have dmg Beta Access Utility for macOS Big Sur 11.0 beta 3 or link

terminal
sudo python installinstallmacos.py --raw --seedprogram DeveloperSeed

installinstallmacos.py

ameenjuz
ameenjuz
Posted
Posted (edited)
5 minutes ago, Rocky12 said:

@ameenjuz

Only PKG link if you want 

http://swcdn.apple.com/content/down...fasb0217grmmyplfd6o7mqfp/InstallAssistant.pkg

i want to developer access utility pkg or link

i want to download Install macOS Big Sur Beta.app

Edited by ameenjuz
edited
Alex HQuest
Alex HQuest
Posted
Posted (edited)
1 hour ago, PC IT said:

12 gb update, seems it has many fixes

macOS Big Sur 11 Beta 3 Release Notes

Note: For this macOS Big Sur build, you will see the full installer in the main window of the System Preferences > Software Update. If you would rather install the smaller software update, click on the "More Info" link and choose the update for this build.

 

Installer and Software Update

Known Issues

  • You might be unable to update macOS Big Sur 11 Beta 3, if Secure Boot is set to No Security. (63434409)

  • Your Mac might restart but isn't updated to a newer version of macOS Big Sur 11 Beta. (65298753)

    Workaround: Create a bootable installer using the createinstallmedia command.

  • When updating to macOS Big Sur 11 Beta 3, you might be offered an unexpectedly large download rather than an incremental software update. (65753086)

    Workaround: Under the "Another update is available" text, click the "More info…" link. This will reveal the incremental update where you can click the Install Now button.

  • You might need to adjust Energy Saver settings so your Mac doesn't go to sleep while preparing to install macOS Big Sur 11 beta. (63166401)

  • APFS containers with non-default allocation block sizes aren't currently supported for installation. (64312561)

  • If macOS Big Sur 11 beta is installed into the same APFS container as previous versions of macOS Catalina 10.15, system software updates can no longer be installed on the previous versions of macOS. (64411484)

    Workaround: Update the previous version of macOS Catalina to 10.15.6.

Resolved in macOS Big Sur 11 Beta 3

  • Installations no longer pause on Macs that don't have input devices connected. (64348347)

  • You can now install macOS Big Sur 11 beta 3 onto additional volumes. (63677460, 64445236)

  • Software Update now correctly indicates that your Mac is enrolled in the Apple Beta Software Program. (64407436)

  • It's no longer necessary to update to an intermediate macOS release before installing macOS Big Sur 11 beta 3. (64314272)

  • If you updated to macOS Big Sur 11 beta from a previous version of macOS, Software Update now works as expected. (63158434)

Edited by Alex HQuest
  • Like 2
  • Thanks 1
mnfesq
mnfesq
Posted
Posted

TA-DA!!!!!Finder.thumb.jpg.13917d96216e601a40dae5f89e145314.jpg

 

Want to know what made Big Sur detect my internal drives?

Spoiler

I installed the VoodooI2C kexts -- VoodooI2C.zip

 

I have been having problems with my trackpad in Big Sur so I thought I would try the I2C kexts to see if that would help.  It didn't help my trackpad but it sure found my internal drives.  Interestingly, they are detected in disk utility as external drives.  Nonetheless, they are finally there.  Hope this works for the rest of you.

 

  • Like 4
  • Thanks 1
ameenjuz
ameenjuz
Posted
Posted (edited)

@Alex HQuest @Rocky12 thanks for information

12 minutes ago, mnfesq said:

TA-DA!!!!!Finder.thumb.jpg.13917d96216e601a40dae5f89e145314.jpg

 

Want to know what made Big Sur detect my internal drives?

  Reveal hidden contents

I installed the VoodooI2C kexts -- VoodooI2C.zip

 

I have been having problems with my trackpad in Big Sur so I thought I would try the I2C kexts to see if that would help.  It didn't help my trackpad but it sure found my internal drives.  Interestingly, they are detected in disk utility as external drives.  Nonetheless, they are finally there.  Hope this works for the rest of you.

 

Finally detect your internal SSD beta 3

Edited by ameenjuz
edited
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...