tasco11

My touchpad is MSFT0001 ; TPAD I use voodooi2c 2.4.4 and the satelite is voodooi2chid. macOS Big Sur beta 4 The problem is, my touchpad stop working and unresposive after wake from sleeping? Anyone here know the solution?

Go to OC 0.6.1 and set the 'Rebuild Apple Map' to No/False on Booter Quirks. Have you fixed this problem via dsdt? Apfs snapshot is quite common in big sur, I have this case also.

Anyone here using BCM9464 as wifi card? Since the price quite affordable. Or does this wifi card support hackintosh?

OC 0.6.1 Clover still unable handle Big Sur

1. I didn't know yet. But once i tried to use dsdt from clover, it ended to kp. 2. Sure you can. I guess, clover has more parameter to be set rather than oc. So, if you transform from oc to clover. Not all parameter would filled by clover.

Done by update OC to 0.6.1 and latest kext.

Try remove broadcom fixup kext first.

It's not NVMe problem. Seems like EC problem.

Not sure from which one. It's look like theyre can't work together of put on same folder. First I put ps2, the system is fine. Then I add voodooi2c, the KP is exist. Or vice versa.

So, I just installed macOS Big Sur Beta 4 on my Ideapad S340-14IWL. The installation went well. The problem was coming while I try to add VoodooI2C kext to activate my Touchpad. While booting, it got kernel panic on verbose screen: Refus new kext : a prelinked copy with different executable UUID is already present. I knew, that the KP is caused by the plugin on voodooi2c/voodoops2controller, VoodooInput. While I remove the kext, the KP is gone. But I can't activate my I2C Touchpad or use ps2 keyboard on laptop(since the kext was removed). VoodooInput used as plugin on 2 kext, voodoops2controller and voodooi2c, but can they work together as plugin without causing KP? 20200810_054341.zip

Add Fix RTC _STA bug

Have you put the boot args keepsyms=1 and debug=0x100 ? Have you updated to OC 0.6.1?

Yes, you're right. I solve this case by update to 0.6.1 and last kext.

I guess the main problem isn't nvme, but the verbose line apfs_module_start:2411 Any idea what should I do to fix this?

I have same problem, but my device ec name is "EC" no "EC0" anymore. Do I need injected EC again?

Are there many differencies between public beta and developer beta?

No luck on beta 4. Same problem, stuck on AppleNVMe Assert Failed.

Where did you installed the OS? Laptop or Desktop? How many GB the Size?

I wonder, on my Big Sur beta 1 my laptop booting succesfully on installation and system. But while i upgrade to beta 3, the booting stuck on NVMe Asserts Failed. Following by apfs_module_starts:2411. Anyone know what happen? My gear is laptop with i5-8265U, Ram 8gb, UHD620+MX230, Sata 1 GB HDD and NVMe 128GB. But I installed the Big Sur on HDD.20200802_083922.zip

does OC 0.6.0 unable to boot Big Sur 11.0 (Beta 3) on laptop??

I need help! On Beta 1 my OC is fine, but while I try update to beta 3, the verbose stuck on this line. Any idea what should I do? Sometimes It got stuck on apfs_module_start:2411 I tried to put SSDT-EC-USBX and EC0 to EC but no differencies. My Laptop is IP S340 i5-8265U Intel UHD620 8GB 2400MHz Thank you! 20200802_083922.zip

i5 8265U UHD620

Hey, I have one problem recently. I installed Big Sur on my laptop using Opencore, and it's succed. Then, I tried to boot with clover. I could enter the os, but while I checked on Hackintool, it shows that I used Opencore instead Clover to boot. How to make hackintool detect the clover without clean nvram from opencore?

My Touchpad doesn't work, even have been patched. HElp me to resolve this issue. The Device is TPAD, MSFT0001. FIle attached below. http://s000.tinyupload.com/?file_id=66768851087447170764

The Trackpad still not working. What should I do?