Closed ghost closed 6 years ago
@PavelLJ Yes, my card works pretty well under Windows 10. What about this driver below? This is what they gave me. I think you need to uninstall the drivers at first that don't work. BroadcomWirelessWin8x64.exe.zip
@stevezhengshiqi thanks, it's working now! I can't say about your question though, looks like there is no such option.
HI @stevezhengshiqi !! I bought a brand new xiaomi notebook pro i7 with 16gb of RAM. I used your latest CLOVER folder. Everything works perfect in 10.13.6 (17G2112). But, I have poor results in geekbench. I post it too in tonymac forum. Maybe you can tell me if Im doing something wrong...
EDIT: Ok, with release "XiaoMi NoteBook Pro EFI v1.2.4", or 1.2.3, I just get 11.400 score. But, If I boot with release "XiaoMi NoteBook Pro EFI v1.2.2" I have 16.900 in geekbench. There should be something wrong in CLOVER folder related with CPU. Can you check your geekbench score and post it please? :)
Ok, I get it. If I use XiaoMi NoteBook Pro EFI v1.2.4 with v1.2.2 CPUFriendDataProvider.kext and CPUFriend.kext (released on 13 May) instead of 1.2.4 versions, geekbench is fine again with 16.500 score in geekbench. I think the updated release and CLOVER folder of @stevezhengshiqi and @daliansky have wrong CPUFriend kext, because I cant get good score. Who can check that?
@alexmenn Issue moved to #53 @PavelLJ Hi, Could I submit you and Cyb's script in my Github? They are really great. For sure I will update the credit.
@stevezhengshiqi I asked about it, Cyb agreed, but it's still in testing phase as we're adding new features, for example we managed to modify Nuvoton EC ROM to get fans kicked on 55 and not on 43, feels great - laptop is silent in most cases. Also now I'm testing DVMT=64MB, so we maybe will get rid of DVMTFixup. Wait untill it will be more finished, okay? Big thanks to Cyb by the way, the patches are mostly his work while I just suggested and tested things. Russian hackers rocks 👓
Hello again! I'm enthusiast so I don't know much about Native Power Management, but I found some faulty things in our setup: At first, SSDT-XCPM (or PluginType if you wish) configured wrong, as KabyLake+ DSDT (and our too), got the _PR0.PR00 tree, not _PR0.CPU0 as it was configured by rehabman by default (he made notes about KabyLake+ systems). I checked in MaciASL and yeah - our DSDT is using PR00 so I guess this should be fixed. Also I don't think CPUFriend is needed with this fix, as of my AppleIntelInfo report all is okay with HWP (pure setup, almost no kext and the only patched SSDT is SSDT-XCPM) AppleIntelInfo Report: