感谢，作为一个伸手党，只能表示感谢。
楼主你好，我现在电量显示跟睡眠问题，还是兰牙，亮度，这几个问题未解决。能否加个联系方式请教，谢谢！
无线网卡现在是买USB黑网卡650M的，可以应付。谢谢
试一试了。。。。。。。。
一时时的，有时候重启可以用，有时候不行
楼主驱动怎么安装啊？
oldenmoon 发表于 2020-4-5 11:41 https://www.pcbeta.com/static/image/common/back.gif
楼主你好，我现在电量显示跟睡眠问题，还是兰牙，亮度，这几个问题未解决。能否加个联系方式请教，谢谢！
...
电量显示确实有BUG,因为有几个反映是有问题的，不过我的是日版机器，所以这方面我自己调的DSDT可能存在不通用，睡眠同理。亮度的快捷键在设置里面，可以自己调的，蓝牙我也不知道怎样解释。。。。。估计还是机器版本的问题。
supi93 发表于 2020-4-10 14:16 https://www.pcbeta.com/static/image/common/back.gif
楼主驱动怎么安装啊？
驱动放在EFI里面，建议看看置顶帖，慢慢研究一下
linliufang 发表于 2020-4-10 16:23 https://www.pcbeta.com/static/image/common/back.gif
电量显示确实有BUG,因为有几个反映是有问题的，不过我的是日版机器，所以这方面我自己调的DSDT可能存在不 ...
朋友，能否PM个联系方式。我现在亮度是用软件先用，其它的都不行。刚换了DW1830网卡，wifi能用，蓝牙好象不行。蓝牙win也不行。
小红点，及 电量都不能使用
linliufang 发表于 2020-4-10 16:23 https://www.pcbeta.com/static/image/common/back.gif
电量显示确实有BUG,因为有几个反映是有问题的，不过我的是日版机器，所以这方面我自己调的DSDT可能存在不 ...
兄弟，亮度的快捷键在设置里，能说下具体是哪里设置？谢谢，电量显示老是搞不定。能否告知下，用你整个EFI开不了机。现在就想弄个电源显示， 还有就是DW1830 win驱动蓝牙没搞定
下载试下，感谢，
我的休眠回来声音就没了 耳机孔也有莎莎响 求大神怎么解决
你好，链接似乎失效了，能再发一个吗，或者邮箱195528189@qq.com，谢谢楼主！！！！
顺便问下 你们bios什么版本呀 我的有些东西找不到很多不一样
下载一个。
下载不了啊
怎么下载不了呢
怎么下载不了呢
配置相同，安装后可以正常使用了，谢谢
And some of the techniques to change DVMT-prealloc, even if possible, can be dangerous and you may not want to risk it.
There is the minStolenSize patch, which can disable the check for adequate DVMT-prealloc, but that patch is likely to cause instability, glitches, or other strange behavior. There is likely good reason for the assertion in the framebuffer code.
Fortunately, it is possible to patch the framebuffer to fit within the 32mb DVMT-prealloc.
Details, Broadwell example
Of course, patching the framebuffer for an alternate DVMT-prealloc is a bit more involved than using the minStolenSize patch because the patch is specific both to the ig-platform-id you're using.
Let's take a look at the framebuffer data for a commonly used ig-platform-id on Broadwell, 0x16260006:
06002616 01030303 00002002 00005001
The 06002616 is just 0x19260006 byte reversed.
The 01030303 has to do with port and pipe counts.
The next two 32-bit items are the framebuffer memory size and the cursor bytes size (in WhateverGreen, these are referred to as framebuffer-stolenmem, and framebuffer-fbmem).
The sum of those two items must be less (or equal) than the DVMT-prealloc setting.
So, 0x02200000 is 34MB, and 0x01500000 is 21MB. The sum is 55MB. So, clearly it is not going to work with a DVMT-prealloc of 32MB.
We can change these values so only 32MB (actually a bit less) is required. For example, we know that on Haswell AppleIntelFramebufferAzul and ig-platform-id 0x0a260006 only require 32MB.
The AppleIntelFramebufferAzul kext has this in the header for 0xa260006:
0600260A 01030303 00000002 00003001 00006000
Byte reversing the values, we get 0x02000000 (32MB) for DVMT-prealloc requirement, 0x01300000 (19MB) for framebuffer size, and 0x00600000 (6MB) for cursor bytes. Of course we usually patch the 6MB to 9MB, otherwise there are glitches.
So... a patch for Broadwell 0x16260006:
Comment: 0x16260006, 32MB BIOS, 19MB framebuffer, 9MB cursor bytes (credit RehabMan)
Name: AppleIntelBDWGraphicsFramebuffer
Find: 06002616 01030303 00002002 00005001
Replace: 06002616 01030303 00003001 00009000
The above KextsToPatch patch results in ig-platform data that requires only 28MB.
You could also shorten the Find/Replace data such that it applies to more ig-platform-id values.
For example, this patch:
Comment: 0x16260006/etc, 32MB BIOS, 19MB framebuffer, 9MB cursor bytes (credit RehabMan)
Name: AppleIntelBDWGraphicsFramebuffer
Find: 01030303 00002002 00005001
Replace: 01030303 00003001 00009000
... would apply to the following: 0x19160002, 0x16160002, 0x16260002, 0x16220002, 0x162b0002, 0x16260005, 0x16260006.
These patches are much easier and more reliable (and less likely to stop working) using WhateverGreen.kext:
framebuffer-patch-enable=1
framebuffer-stolenmem=<00003001>
framebuffer-fbmem=<00009000>
Or, as it would look in Xcode (this example taken from guide plist config_HD615_620_630_640_650.plist):
32mb DVMT whatevergreen.png
Read here for more information on WhateverGreen.kext: https://www.tonymacx86.com/threads/guide-intel-framebuffer-patching-using-whatevergreen.256490/
Conclusion
There is no need to use the minStolenSize patch or change DVMT-prealloc... Instead, you can patch the framebuffer to match your BIOS configuration for DVMT-prealloc.
Patching the framebuffer to match your BIOS setting for DVMT-prealloc is likely to be more stable than the minStolenSize patch and with limited BIOS options, comes with less risk than changing DVMT-prealloc.