iamprabhuantony Posted July 28, 2020 Share Posted July 28, 2020 1 hour ago, jsl2000 said: At last Clover bootloader works at Big Sur beta3 in my FX-6300 hackintosh. Wake up from S3 sleep working too. By OpenCore 0.6.0 it always got CMOS Reset issue. Major bugs in AMD CPU hackintoshs to be fixed: 1. Only Firefox Developer Edition and Google Chrome fully working, Safari and Firefox not fully compatible yet ! please share your EFI... Link to comment Share on other sites More sharing options...
Cyberdevs Posted July 28, 2020 Share Posted July 28, 2020 3 hours ago, Matgen84 said: I don't use Opencanopy and I can't boot into Big Sur's Recovery. What ScanPolicy do you use ? The scan policy is set to 0 1 Link to comment Share on other sites More sharing options...
Partime Posted July 28, 2020 Share Posted July 28, 2020 10 hours ago, eSaF said: Hide contents @MorenoAv - Yes Big Sur will appear in the Startup Disk section if you have another OS X disk on the system as well but if you remove it leaving just Windows and BS, it will no longer be in there - Well that is how it is on my system. I use an EFI 99.9% identical to yours. I see the same in Startup Disk, but only after recompiling OC & Kexts to latest builds. 2 Link to comment Share on other sites More sharing options...
jsl2000 Posted July 28, 2020 Share Posted July 28, 2020 2 hours ago, iamprabhuantony said: 4 hours ago, jsl2000 said: At last Clover bootloader works at Big Sur beta3 in my FX-6300 hackintosh. Wake up from S3 sleep working too. By OpenCore 0.6.0 it always got CMOS Reset issue. Major bugs in AMD CPU hackintoshs to be fixed: 1. Only Firefox Developer Edition and Google Chrome fully working, Safari and Firefox not fully compatible yet ! please share your EFI... EFI.zip 3 1 Link to comment Share on other sites More sharing options...
MorenoAv Posted July 28, 2020 Share Posted July 28, 2020 (edited) Hi guys, Today I'm at work, and as you remember I had 2 updates for my Mac mini 2018, today I installed it again... and now I have the installation appear although I already made it... and the one in system preferences satay there. BS weirdness strikes again, how do I remove the update from system preferences and the reminder that I have one update in about this Mac? If you feel that this post is off topic feel free to move it elsewhere... Thanks Edited July 28, 2020 by MorenoAv Link to comment Share on other sites More sharing options...
Alex HQuest Posted July 28, 2020 Share Posted July 28, 2020 12 hours ago, eSaF said: Reveal hidden contents @MorenoAv - Yes Big Sur will appear in the Startup Disk section if you have another OS X disk on the system as well but if you remove it leaving just Windows and BS, it will no longer be in there - Well that is how it is on my system. That is not a standard, though. Windows, BS and Catalina are on this same system. Spoiler Link to comment Share on other sites More sharing options...
MorenoAv Posted July 28, 2020 Share Posted July 28, 2020 Hi @Alex HQuest, In my system there are only 3 ssd with BS, beta 2 and Beta 3... and Win 10... Link to comment Share on other sites More sharing options...
Alex HQuest Posted July 28, 2020 Share Posted July 28, 2020 18 hours ago, Cyberdevs said: I think you need to update the OC and the drivers as well, here's what happens, with the latest build of OC and the Kexts there is no need for vsmcgen=1 but if you use an older version of the OC and the kexts it will get stuck at boot. I cleaned my build tools and fetched 100% fresh sources as of July 28. Compiled them, reset NVRAM, I'm still required to use vsmcgen. I tried your kexts, same thing. Link to comment Share on other sites More sharing options...
Cyberdevs Posted July 28, 2020 Share Posted July 28, 2020 1 minute ago, Alex HQuest said: I cleaned my build tools and fetched 100% fresh sources as of July 28. Compiled them, reset NVRAM, I'm still required to use vsmcgen. I tried your kexts, same thing. it happened to me several times so as a workaround I removed the whole opencoremaster folder and cloned it from the github and rebuilt the OC and then built the latest. 2 1 Link to comment Share on other sites More sharing options...
darthsian Posted July 28, 2020 Share Posted July 28, 2020 (edited) 13 minutes ago, Alex HQuest said: I cleaned my build tools and fetched 100% fresh sources as of July 28. Compiled them, reset NVRAM, I'm still required to use vsmcgen. I tried your kexts, same thing. Yeap, same here. Build from fresh last sources of OC and kexts, but still need vsmcgen=1 for booting Big Sur. Edited July 28, 2020 by darthsian Link to comment Share on other sites More sharing options...
Stefanalmare Posted July 28, 2020 Share Posted July 28, 2020 After I used this: I never had to reset nvram again. No matter what I changed. 1 Link to comment Share on other sites More sharing options...
dvil Posted July 28, 2020 Share Posted July 28, 2020 (edited) Hi, I just managed to boot BS using Clover 5120 in addition to OC 0.6. The interesting bit is that with Clover I can see and select BS as the startup disk in System Preferences. With OC BS is not listed as a startup disk option! I haven't found the reason for the difference in behaviour, but it seems like is just a misconfiguration issue. Cheers Spoiler Edited July 28, 2020 by dvil 1 1 Link to comment Share on other sites More sharing options...
greythorne Posted July 28, 2020 Share Posted July 28, 2020 On 7/27/2020 at 9:36 PM, Shaneee said: Yeah sleep is working with Big Sur. It doesn't work on Catalina with the same EFI though. Exactly. I am experiencing the same. Sleep works well in BS beta3, however not in Catalina. In Catalina i have to manually put it to sleep. On 7/27/2020 at 9:03 PM, mick3lson said: It's possible with opencore 0.60 dual boot big sur and windows 10 on same drive, I tried but don't work, windows start but it crashes immediately. I triple booted Windows 10 Pro + Catalina + BS on the same m.2 SSD. Now removed BS and put it on separate SATA SSD as per my sig. Link to comment Share on other sites More sharing options...
Alex HQuest Posted July 28, 2020 Share Posted July 28, 2020 On 7/27/2020 at 9:03 AM, mick3lson said: It's possible with opencore 0.60 dual boot big sur and windows 10 on same drive, I tried but don't work, windows start but it crashes immediately. If you are injecting any DSDT/SSDT tables, patching them with OC or the likes, then you should exclude these if the OS isn't Darwin, therefore not touching them for Windows. Link to comment Share on other sites More sharing options...
eSaF Posted July 28, 2020 Share Posted July 28, 2020 29 minutes ago, dvil said: Hi, I just managed to boot BS using Clover 5120 in addition to OC 0.6. The interesting bit is that with Clover I can see and select BS as the startup disk in System Preferences. With OC BS is not listed as a startup disk option! I haven't found the reason for the difference in behaviour, but it seems like is just a misconfiguration issue. Cheers Reveal hidden contents Yea if your finding is correct with Clover, then there is something flaky with or a misconfiguration in Opencore causing the BS disk not to show in the Startup Disk section in System Preferences. It has been a daily task of mine trying to find out why and I've yet to track it down. 3 Link to comment Share on other sites More sharing options...
markl18 Posted July 28, 2020 Share Posted July 28, 2020 (edited) hi mr @Cyberdevs as per your suggestion trying to install from new betta 3 why I am getting can't mount errors Edited July 28, 2020 by markl18 Link to comment Share on other sites More sharing options...
Diepnguyen90hn Posted July 28, 2020 Share Posted July 28, 2020 Hi im trying to install big sur beta 3 but got error as below. Im using config.plist of my catalina with all beta kexts like lilu, virtuasmc... does anyone know the issue. Thank you. Link to comment Share on other sites More sharing options...
eSaF Posted July 28, 2020 Share Posted July 28, 2020 @dvil - Although I've posted about this bug a few times, can I ask if your Clover finding is just with Windows and BS alone connected, because I found BS will only be present if and when another OS X disk is connected. If it is easy for you to do can you just boot your system with just BS and Windows Disk connected and check the result in System Preferences/Startup Disk please. Link to comment Share on other sites More sharing options...
Sbrillo Posted July 28, 2020 Share Posted July 28, 2020 (edited) 22 hours ago, iCanaro said: create an SSDT for the custom PM for your CPU https://github.com/Piker-Alpha/ssdtPRGen.sh tried. but I don't think this change anything... I remove the prebuilt ssdt, reboot, run the script, generate the file, rename in ssdt-plug, copy in the ACPI folder, enable via OpenCore configurator and reboot. This is the result Edited July 28, 2020 by Sbrillo Link to comment Share on other sites More sharing options...
STLVNUB Posted July 28, 2020 Share Posted July 28, 2020 (edited) Big Sur runs on my 2011 MacBook Pro without any hacks. Wifi and sound not working though Edited July 28, 2020 by STLVNUB 2 Link to comment Share on other sites More sharing options...
AppleBreak Posted July 28, 2020 Share Posted July 28, 2020 (edited) 3 hours ago, MorenoAv said: Hi guys, Today I'm at work, and as you remember I had 2 updates for my Mac mini 2018, today I installed it again... and now I have the installation appear although I already made it... and the one in system preferences satay there. BS weirdness strikes again, how do I remove the update from system preferences and the reminder that I have one update in about this Mac? If you feel that this post is off topic feel free to move it elsewhere... Thanks Delete the items under AttentionPrefBundleIDs then log out. Edited July 28, 2020 by AppleBreak 2 Link to comment Share on other sites More sharing options...
dvil Posted July 28, 2020 Share Posted July 28, 2020 1 hour ago, eSaF said: @dvil - Although I've posted about this bug a few times, can I ask if your Clover finding is just with Windows and BS alone connected, because I found BS will only be present if and when another OS X disk is connected. If it is easy for you to do can you just boot your system with just BS and Windows Disk connected and check the result in System Preferences/Startup Disk please. Still working fine in Clover just with BS and Windows. Cheers. Spoiler 1 Link to comment Share on other sites More sharing options...
mav96 Posted July 28, 2020 Share Posted July 28, 2020 Hi guys, Currently I have Catalina 10.15.6 and Big Sur Beta 2. I tried to update to beta 3 and it created a Preboot entry in OC, but every time I try to boot it, it results in the kernel panic from the attached picture. I tried it with the latest Clover v2020 and with a compiled OC from today - it results in the same error. Both bootloaders are booting successfully Catalina and BigSur Beta 2. I even downloaded and created a usb installer for beta 3. But unfortunately, it also resulted in the same error (both in Clover and OC). Please if you have encountered this error before and know how to fix it, help me! Many thanks!!! Link to comment Share on other sites More sharing options...
markl18 Posted July 28, 2020 Share Posted July 28, 2020 (edited) 19 minutes ago, mvitanov said: Hi guys, Currently I have Catalina 10.15.6 and Big Sur Beta 2. I tried to update to beta 3 and it created a Preboot entry in OC, but every time I try to boot it, it results in the kernel panic from the attached picture. I tried it with the latest Clover v2020 and with a compiled OC from today - it results in the same error. Both bootloaders are booting successfully Catalina and BigSur Beta 2. I even downloaded and created a usb installer for beta 3. But unfortunately, it also resulted in the same error (both in Clover and OC). Please if you have encountered this error before and know how to fix it, help me! Many thanks!!! I could be wrong but it looks like you don't have a ssd-tpl0 or what ever your device is called to identify the touch hub in order for Big Sur to move on mark it present and go on booting I posted my ssd-tpl0 for any one to get compiled but so far no takers Edited July 28, 2020 by markl18 Link to comment Share on other sites More sharing options...
mav96 Posted July 28, 2020 Share Posted July 28, 2020 7 minutes ago, markl18 said: I could be wrong but it looks like you don't have a ssd-tpl0 or what ever your device is called to identify the touch hub in order for Big Sur to move on mark it present and go on booting I use Samsung 970 EVO SSD - NVMe m.2; I haven't had any problems so far with it (using it since High Sierra). And the other betas of Big Sur were not making this problem, so I assume apple changed sth yet again related to that. Link to comment Share on other sites More sharing options...
Recommended Posts