System configuration	GPU - OpenCL Performance 4731

Compare with these.

1. Intel Bluetooth could not support some Bluetooth devices like some Bluetooth mouse since it is only a firmware injector; please, report any issues not here but only on OpenIntelWireless/IntelBluetoothFirmware Gitter Chat
2. Touchscreen support is disabled by default since release v. 1.8.0. Why? It seems that all VoodooI2C versions after 2.4 are affected to a greater or lesser extent by Multi_GPI0 issues. The solution proposed so far by VoodooI2C developers is only a workaround and not a real fix: proposing to use the GPI0 pinning for touchpad and polling method for touchscreen is not a real fix because this approach increases interrupts and causes a degrade in battery life. This being the case and not needing to use the touchscreen in my daily work, for the moment I have disabled this function pending improvements that can only come from VoodooI2C developers.
3. If you would like to increase benchmark values for your Intel UHD 620 Graphics card, you need to set rps-control key in DeviceProperties -> PciRoot(0x0)/Pci(0x2,0x0), but keep in mind that rps-control property has been removed to lower down GFX Request:

...
<key>DeviceProperties</key>
<dict>
    <key>Add</key>
    <dict>
        ...
        <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
        <dict>
            ...
            <key>rps-control</key>
            <data>AQAAAA==</data>
            ....
        </dict>
        ...
    </dict>
</dict>
...

Intel UHD 620 Graphics card works well with external display from both USB type-C ports.

• Suggestion: prefer USB type-C to DisplayPort cable over USB type-C to HDMI one where possible
• Removed for PciRoot(0x0)/Pci(0x2,0x0) the key force-online (which was set to <data>AQAAAA==</data>). Why?
  • With latest WhateverGreen releases our available connector types are 1 LVDS (internal monitor) and 2 DP; using an external monitor connected with a USB C-type to DP cable I verified the correct recognition and functioning of my BenQ PD2500Q even after the system wake-up. This force-online key could instead be useful for connections using a USB-C type to HDMI cable.
  • Eliminating this key reduces tons of warning messages like [IGFB] [ERROR] [AGDC] Failed with status -536870212 for stream access aux in system log during boot phase: that warning is correct/normal since it reports that the display is not connected for the remaining ports (i.e. FB1 and FB2 in our case using only FB0 i.e. internal display); eliminating those warnings reduces log-file size (in debug-mode) from 2.6 to 1.6 MB thus reducing slightly boot loading time. Reference
• force-online and force-online-framebuffers work around (possible) HDMI black screen issues after waking from sleep

...
<key>DeviceProperties</key>
<dict>
    <key>Add</key>
    <dict>
        ...
        <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
        <dict>
            ...
            <key>force-online</key>
            <data>AQAAAA==</data>
            <key>force-online-framebuffers</key>
            <data>Af////////8=</data>
            ....
        </dict>
        ...
    </dict>
</dict>
...

1. Very rarely some users reported the following kernel panic after sleep:

panic(cpu 0 caller 0xffffff800b6ce860): nvme: "Fatal error occurred. CSTS=0xffffffff
...

It's certainly a NVMe error, but it is not due to EFI released in the present repo:

• it may be due to the power management of your NVMe device (mine is a LiteON SSD PCIe NVMe 512 GB [CA3-8D512])
• reference to this issue is in acidanthera/bugtracker#1193 IGP causes NVMe Kernel Panic CSTS=0xffffffff

In case you run into such an issue, it is recommended adding forceRenderStandby=0 boot-args in your config.plist to disable RC6 Render Standby.

2. If your laptop has a Samsung PM981 NVMe SSD or any unsupported SSD listed in dortania/bugtracker#192, then it's obviously not supported here. I have no way to make my EFI work on broken IONVME compatibility SSDs.

Obvious solutions:

• buy another (internal) NVMe SSD
• or install macOS on an external SSD drive

Even if your macOS installed on an external SSD drive, you need to add a new ACPI patch to disable PM981 (or other non-supported NVMe SSDs) detection on macOS:

DefinitionBlock ("", "SSDT", 2, "HUAWEI", "_DRP05", 0)
{
	External (OSDW, MethodObj)

    External (_SB_.PCI0.RP05, DeviceObj)

    Scope (\_SB.PCI0.RP05)
    {
        OperationRegion (DE01, PCI_Config, 0x50, One)
        Field (DE01, AnyAcc, NoLock, Preserve)
        {
                ,   1, 
                ,   3, 
            DDDD,   1
        }
    }

    Scope (\)
    {
        If (OSDW ())
        {
            \_SB.PCI0.RP05.DDDD = One
        }
    }
}

Starting from BIOS version 1.33 and newer, Huawei added to default DSDT.aml a new method, called _QBF, related to battery thermal management.

As default, in config.plist in ACPI -> Add section it has been added SSDT-BIOS.aml (as enabled) for introducing method _QBF also for BIOS versions up to 1.30: proper BIOS version check has been implemented.

For dual-booting systems, Windows Activation may fail due to different hardware UUID generated by OpenCore

• According to OpenCore Official Configuration, you are highly recommended to inject the original Windows system UUID to PlatformInfo -> Generic - >SystemUUID in EFI/OC/config.plist: run wmic csproduct get UUID command in Windows PowerShell app

If you use this release in macOS Catalina you need to make the following changes in the config.plist to make AirportItlwm.kext support active:

• DmgLoading set to Signed
• SecureBootModel set to Default

As reported in NotebookCheck review our Matebook X pro (2018) is utilizing only half the PCIe lanes for its single Thunderbolt 3 port (TB). Thus, its PCIe x2 Thunderbolt 3 port is only capable of providing a maximum of 20 Gbps instead of 40 Gbps when compared to a standard Thunderbolt 3 port with PCIe x4 lanes.

The connector type is Usb-C and it can do multiple protocols (TB, USB 2/3/3.1, DP, etc...) with different backing controllers. The problem on Hackintoshes is mostly about TB on Usb-C, because the firmware and power management of Apple's TB-controllers works entirely different than those for other OS'es. So even if it's the same hardware found on Windows laptops, they don't "just work" because of the different firmware.

The ACPI-part for handling Thunderbolt 3 port and its power management has been implemented:

• it enables not only the PCIe-to-PCIe bridge-mode of the TB controller but also the native drivers which make it possible to completely poweroff the controller after using the TB port, saving battery life and prevent the controller from preventing the CPU goes into deeper C-State
• the ICM is disabled on boot to let OSX' drivers take over the job
• the TB port works when any device is plugged into it at the boot time: this means no hot-plug
• the TB 3 XHC Controller is working fine when any device is plugged into it at boot time
• the TB drivers are loaded even if no device is plugged into it at boot time
• the TB 3 XHC Controller bus is loaded even if no device is plugged into it at boot time

Since I was given an OWC Envoy Express Thunderbolt 3 Controller is enabled in my default config.plist.

Steps for disabling support for Thunderbolt controller (\_SB.PCI0.RP09):

• disable SSDT-JHL6240-AR2.aml
• enable SSDT-DTB3.aml
• disable all TB3: * binary patches

Real-time power management for Thunderbolt controller with Discrete GPU (NVIDIA GeForce MX150) removed at PCI level are shown:

For reference, see Thunderbolt 3 Fix and ThunderboltPatcher for related attempts to fix TB by patching its firmware.

• Discrete graphics card (NVIDIA GeForce MX150) is not working, since macOS doesn't support Optimus technology
  • Have used SSDT-DDGPU.aml to disable it in order to save power.
  • Removed it at PCI level reducing time for putting machine to sleep and for resuming it from sleep (i.e. laptop is more reactive during these phases!)
  • \_SB.PCI0.RP01 is not present anymore in IORegistryExplorer tree (this is proof for having disabled GPU at PCI level!)

• Fingerprint sensor is not working
  • Fingerprint readers on Macbooks are managed by T2 chip which has not been very throughly reverse engineered yet
  • Have used SSDT-XHC.aml to disable it (in order to save some power).

Starting from VoodooI2C v. 2.4.1, the click down action is emulated to force touch, which causes the failure of click down and drag gestures.

For example, you can turn off Force Click in System Preferences -> Trackpad or choose three finger drag in System Preferences -> Accessibility -> Mouse & Trackpad -> Trackpad Options

Suggested configuration:

To use iMessage and other Apple services, you need to generate your own serial numbers. This can be done using CorpNewt's GenSMBIOS:

• If Serial numbers have been correctly generated, these services (iMessage, FaceTime, ...) should work for you
• If not, clean up and generate new serial number for your SMBIOS.

Default SMBIOS settings of this repo is MacBookPro15,2 MacBookPro14,1 MacBookPro16,3

1. Launch Terminal app
2. Copy the following script, paste it into the Terminal window, then press Enter

   git clone https://github.com/corpnewt/GenSMBIOS && cd GenSMBIOS && ./GenSMBIOS.command 

3. Type 1 for downloading/updating MacSerial script
4. Type 3, then press Enter
5. Type MacBookPro15,2 10, then press Enter
6. Then, go Apple Check Coverage page to check your generated serial numbers. If the website tells you that the serial number is not valid, that is fine. Otherwise, you have to generate a new set.
7. Next you will have to copy the following values to your config.plist:
   • Serial Number -> PlatformInfo/Generic/SystemSerialNumber
   • Board Number -> PlatformInfo/Generic/MLB
   • SmUUID -> PlatformInfo/Generic/SystemUUID. Reboot and Apple services should work.

<key>PlatformInfo</key>
<dict>
    ...
    <key>MLB</key>
    <string>M0000000000000001</string>
    ...
    <key>SystemSerialNumber</key>
    <string>W00000000001</string>
    ...
    <key>SystemUUID</key>
    <string>00000000-0000-0000-0000-000000000000</string>
    ...
</dict>

8. If they don't work, follow this in-depth guide. It goes deeper into clearing Keychain (missing this step might cause major issues), and much more.

On a MacBook there are some stages of sleep:

• Sleep or memory sleep: this is what happens when you let the computer idle for some time (power to display is turned off);
• Standby or Safe Sleep: memory state is written to RAM and after a certain period memory power could be turned off;
• Hibernation: all power is off and all state has been written to a disk image (/private/var/vm/sleepimage); you know this has happened if when you open the lid you see OpenCanopy boot picker, and then see a progress bar while it is loading state from disk.

We could summarize sleep settings as the following:

1. if sleep == 0, the computer will not sleep or hibernate any more
   • For MacBooks, the effective setting automatically changes whenever the charger is plugged in:
     • Normally, sleep minutes are simply equal to displaysleep minutes, which you can set in System Preferences -> Energy Saver
     • But under the Power Adapter tab, checking Prevent computer from sleeping automatically when the display is off option will override sleep minutes to 0
2. if standby == 1 and hibernatemode == 3, the computer will wait another standbydelay seconds before really entering hibernation
3. autopoweroff is just an extra implementation to fulfill regulatory requirement and has the same impact equivalent to 2)
4. either 2) or 3) takes effect if one of them is reached at first
5. if standby == 1 and hibernatemode == 25, the computer will enter hibernation immediately after sleep minutes.

For our Huawei Matebook X Pro sleep/standby function works flawlessly (both via software and via clamshell) like hibernation (suspend to disk or S4 sleep).

In order to get automatic sleep working properly like real Macs, the following settings are mandatory:

sudo pmset -a powernap 0 
sudo pmset -a proximitywake 0
sudo pmset -a tcpkeepalive 0
sudo pmset -a womp 0

• powernap will wake up the system from time to time to check mail, make Time Machine backups, etc...
• proximitywake can wake your machine when an iDevice is near.
• tcpkeepalive has resolved periodic wake events after setting up iCloud.
• womp is wake on lan.

After every update, ALL these settings should be reapplied manually!

Suggested configuration in System Preferences -> Bluetooth -> Advanced for Bluetooth devices for avoiding random wake events during sleep:

Default macOS setting for MacBooks is hibernatemode 3 i.e. sleep mode:

• standby causes kernel power management to automatically hibernate a machine after it has slept for a specified time period
• standbydelay specifies the delay, in seconds, before writing the hibernation image to disk and powering off memory for standby

Concretely, the way I like to configure my Matebook X Pro is for it to do first a standby-only sleep, so that it quickly goes to sleep, with the chance of a very quick wake-up phase, and then, if I leave the laptop sleeping for a certain number of hours (say in my case 1 hour), it could write the RAM contents to disk and power off the computer, so as to save battery in case of an extended sleep (entering therefore hibernation phase).

In order to get this configuration, I suggest the following settings:

• add to config.plist in NVRAM -> Add -> 7C436110-AB2A-4BBB-A880-FE41995C9F82 -> boot-args section the value hbfx-ahbm=129 which controls auto-hibernation feature introduced by HibernationFixup kext (in particular it is an arithmetic sum of EnableAutoHibernation = 1 and DisableStimulusDarkWakeActivityTickle = 128 flags) Reference for deeper insight
• run in Terminal

sudo pmset -a standby 1 
sudo pmset -a hibernatemode 3
sudo pmset -a standbydelaylow 3600
sudo pmset -a standbydelayhigh 3600

• reboot your laptop

Note: Keep in mind that, with the above settings, after 3600 seconds the laptop wake up itself only partially (display remains off) for switching from standby sleep to hibernation sleep: it is standard behaviour since all Macs use maintenance wake (dark wake - display remains off) to switch laptop from regular sleep into hibernation. It is not an issue! Reference

Note: Hibernation mode can be enabled only via console command sudo pmset -a hibernatemode 25 and is fully supported by Matebook X Pro (obviously using HibernationFixup kext).

If, however, you would like to disable it, then

sudo pmset -a hibernatemode 0
sudo pmset -a autopoweroff 0
sudo rm -rf /private/var/vm/sleepimage
sudo touch /private/var/vm/sleepimage
sudo chflags uchg /private/var/vm/sleepimage

You can verify your power settings by typing in terminal sudo pmset -g live .

If you ever want to reset these settings: sudo pmset -a restoredefaults

About power consumption, HWMonitor reports for the idle state both before and after sleep phase the same value for "CPU package total" (0.65-0.70 W). Sleep discharge rate is about 1% every 4:30 hours (during night).

With CPUFriend.kext and SSDT-PM.aml we achieved a very good power management on battery for

鲜花

握手

雷人

路过

鸡蛋

专题导读

More+

10-27 六六分期app的软件客服如何联系？(六六分期
11-06 可心卡盟:win10系统火狐flash插件崩溃怎么
11-06 亲亲特价:怎么删除回收站图标
11-06 济南大学虚拟社区:鲁大师节能降温的具体办
11-06 xlueops.exe:无线网络安装向导
11-06 女斗合众国:win7系统cf与主机连接不稳定怎
11-06 0xc000022-[cf烟雾头]cf怎么调烟雾头
11-06 qizideyouhuo:应用程序无法正常启动0xc0000
11-06 ipz-185:win7系统vcf文件怎么打开
11-06 傻哥蹦迪:win10系统s4怎么打开usb调试
11-06 八神浩树gtaste:回收站清空了怎么恢复
11-06 妖尾之黑色守护:win10系统电脑没有1440x900
11-06 校园至尊魔王小说:win7系统浏览网页时字体
11-06 女斗合众国:win10系统访问共享文件夹提示请
11-06 tokyo hot n0654:恢复win7系统默认字体一招
11-06 雨酷仙境:设置win7系统转移临时文件夹腾出
11-06 阿穆纳伊之杖:win7系统开始菜单在右边还原
11-06 tunespotting:win10系统火狐flash插件总是
11-06 甘尔葛分析师：计谋网站seo关键词暴涨有什
11-06 蔡贵霖: 计谋网站seo关键词暴涨有什么秘密
11-06 博益网首页:ao3网页版进入不了解决方法
11-06 漏斗子专栏: 网站数据分析小白易懂精华篇
11-06 见证双虹怎么做:win7系统开启telnet命令的
11-06 颾狐蝶蜋:系统资源不足无法完成请求的服务
11-06 国光中学校歌:提交网站到alexa查询详细步骤
11-06 西安有情天:静态网页和动态网页的区别
11-06 红木雅尚斋:外部链接构造对网站的好处
11-06 前官礼遇：防止域名劫持–增强域安全性的10
11-06 密传二转答案: 中文分词算法有哪些
11-06 金泉家园邮编:百度快照劫持的表现及应对方

上一篇：

szzhiyang/PerfectWindows: Power Keys - 解放 Windows 和 macOS 使用效率发布时间：2022-08-18

下一篇：

Orama-Interactive/Pixelorama: A free & open-source 2D sprite editor, made wi ...发布时间：2022-08-18

热门推荐

More+

• 

  CVE-2022-23003

• 

  krishnaik06/Machine-Learning-in-90-days

• 

  armancodv/building-energy-model-matlab:

• 

  美元符号为什么是“$”

• 

  FGRibreau/import-tweets-to-mastodon: How

热门话题

More+

2022-11-06
剪的笔顺,诠释剪的笔画,认识剪的部首

六六分期app的软件客服如何联系？(六六分期
2023-10-27

florent37/ViewAnimator: A fluent Android
2022-08-15

florent37/Shrine-MaterialDesign2: implem
2022-08-17

CVE-2020-36276
2022-09-23

SimpleSoftwareIO/simple-sms: Send and re
2022-08-13

阅读排行榜

1 六六分期app的软件客服如何联系？(六六分期

六六分期app的软件客服如何联系？不知道吗？加qq群【895510560】即可！标题：六六分期
阅读：19230|2023-10-27
2 可心卡盟:win10系统火狐flash插件崩溃怎么

今天小编告诉大家如何处理win10系统火狐flash插件总是崩溃的问题，可能很多用户都不知
阅读：9996|2022-11-06
3 亲亲特价:怎么删除回收站图标

今天小编告诉大家如何对win10系统删除桌面回收站图标进行设置，可能很多用户都不知道
阅读：8331|2022-11-06
4 济南大学虚拟社区:鲁大师节能降温的具体办

今天小编告诉大家如何对win10系统电脑设置节能降温的设置方法，想必大家都遇到过需要
阅读：8700|2022-11-06
5 xlueops.exe:无线网络安装向导

我们在使用xp系统的过程中,经常需要对xp系统无线网络安装向导设置进行设置，可能很多
阅读：8645|2022-11-06
6 女斗合众国:win7系统cf与主机连接不稳定怎

今天小编告诉大家如何处理win7系统玩cf老是与主机连接不稳定的问题，可能很多用户都不
阅读：9667|2022-11-06
7 0xc000022-[cf烟雾头]cf怎么调烟雾头

电脑对日常生活的重要性小编就不多说了，可是一旦碰到win7系统设置cf烟雾头的问题，很
阅读：8630|2022-11-06
8 qizideyouhuo:应用程序无法正常启动0xc0000

我们在日常使用电脑的时候，有的小伙伴们可能在打开应用的时候会遇见提示应用程序无法
阅读：8004|2022-11-06
9 ipz-185:win7系统vcf文件怎么打开

今天小编告诉大家如何对win7系统打开vcf文件进行设置，可能很多用户都不知道怎么对win
阅读：8664|2022-11-06
10 傻哥蹦迪:win10系统s4怎么打开usb调试

今天小编告诉大家如何对win10系统s4开启USB调试模式进行设置，可能很多用户都不知道怎
阅读：7540|2022-11-06

• 关于我们

  创业团队 加入我们 媒体报道 合作伙伴 公益事业

• 产品与服务

  寻求合作 项目投资 干货视频 经理人培训 招聘代理

• 解决方案

  一站式 制造业 教育科研 行业案例

扫描微信二维码

查看手机版网站

随时了解更新最新资讯

139-2527-9053

在线客服（服务时间 9:00～18:00）

在线QQ客服

地址：深圳市南山区西丽大学城创智工业园

电邮：jeky_zhao#qq.com

移动电话：139-2527-9053

Powered by 互联科技 X3.4© 2001-2213 极客世界.|Sitemap