Contribute
Register

[Guide] Lenovo Y50/Y70 (UHD or 1080p) using Clover UEFI

Status
Not open for further replies.
RehabMan said:
Unless you manage to reset the setting. For example, I wonder if resetting BIOS to defaults will affect it?

I suppose if it did, you'd need to flash unlocked BIOS, change it, then reflash newer BIOS...



If you can confirm Lenovo part#/FRU#, I'll add it to post #1... assuming it is not already there.
Click to expand...

Lenovo PN# 20200480
 
shadowk155 said:
Lenovo PN# 20200480
Click to expand...

OK... two different posts from two individuals for the same part...

Note: One may be an FRU, the other a part#.
 
RehabMan said:
OK... two different posts from two individuals for the same part...

Note: One may be an FRU, the other a part#.
Click to expand...

I can confirm one is FRU and one is part#
They refer to the same chipset
 

Attachments

  • TB1mfrbIFXXXXX9XXXXXXXXXXXX_!!0-item_pic.jpg_600x600.jpg
    TB1mfrbIFXXXXX9XXXXXXXXXXXX_!!0-item_pic.jpg_600x600.jpg
    113.7 KB · Views: 100
masterscarhead1 said:
I can confirm one is FRU and one is part#
They refer to the same chipset
Click to expand...

Data I have:

Lenovo FRU 04X6020, Lenovo PN: 20-200480.

Was looking for clear confirmation by those who actually have ordered it...
 
RehabMan said:
Data I have:

Lenovo FRU 04X6020, Lenovo PN: 20-200480.

Was looking for clear confirmation by those who actually have ordered it...
Click to expand...

Look at image I attached above
 
For those who use Y50 4K and cannot change DVMT settings via BIOS or UEFI shell, there is a temporary solution for the screen mess up issue which caused after following RehabMan's guide (and without the step of changing DVMT to 128MB).
I've only tested it on Y50 4K i7-4710HQ GTX860M@2GB edition.
I've found this on pcbeta.com, a Chinese hackintosh fourm. And this solution is written by [email protected].(Original page link: http://bbs.pcbeta.com/viewthread-1597393-5-1.html can't visit if you are not in China)
First MAKE SURE you have done everything and stuck in a messed up screen after start up.
Then Mount EFI partition on another os and open clover/config.plist.
Step 1
In this step you can either use clover patch or patch the AppleIntelFrameBufferAzul.kext itself.
Change the ig-platform-id in config.plist to 0x0d260007
Config.plist:
Code: 
<key>ig-platform-id</key>
<string>0x0d260007</string>

Step 2
For 10.10.2
Clover patch(config.plist):
Code: 
<dict>
<key>Comment</key>
<string>xvip4420's patch</string>
<key>Find</key>
<data>0700260D0103040300000004000020020000500100000060A1070000A1070000000000000000000000000800020000003000000001050B00000400000701000002040B0000040000070100000306030000080000060000001E03000005050900040000000000000000000000000000000000000000000000320000000E000000</data>
<key>Name</key>
<string>AppleIntelFramebufferAzul</string>
<key>Replace</key>
<data>
0700260D01030403000000060000200200000000000000809914000099140000000000000000000000000800020000003000000001050B00000400000701000002040B0000040000070100000306030000080000060000000200000001010000040000000000000000000000000000000000000000000000320000000E000000</data>
</dict>
For 10.10.3
Clover patch(config.plist):
Code: 
<dict>
<key>Comment</key>
<string>xvip4420's patch</string>
<key>Find</key>
<data>0700260D0103040300000004000020020000500100000060A1070000A1070000000000000000000000000800020000003000000001050B00000400000701000002040B0000040000070100000306030000080000060000001E0300000505090004000000320000000E00000000000000</data>
<key>Name</key>
<string>AppleIntelFramebufferAzul</string>
<key>Replace</key>
<data>0700260D01030403000000060000200200000000000000809914000099140000000000000000000000000800020000003000000001050B00000400000701000002040B000004000007010000030603000008000006000000020000000101000004000000320000000E00000000000000</data>
</dict>

This can fix the screen mess up issue but not helpful to the black line on the bottom. But if you change HiDPI to under 1920x1080, the black line will disappeare.
If not useful or have any other screen rendering issues, try log out and re-login. Then if still not useful, try use both clover patch and patched AppleIntelFrameBufferAzul.kext.
This solution haven't been tested on 10.10.5.
This solution have used script "AppleIntelFrameBufferAzul.sh" written by"test.sh v3.0 Copyright (c) 2012-2015 by Pike R. Alpha".
Attached patched AppleIntelFrameBufferAzul.kext
View attachment patched.zip
 
Last edited:
l89669 said:
For those who use Y50 4K and cannot change DVMT settings via BIOS or UEFI shell, there is a temporary solution for the screen mess up issue which caused after following RehabMan's guide (and without the step of changing DVMT to 128MB).
I've only tested it on Y50 4K i7-4710HQ GTX860M@2GB edition.
I've found this on pcbeta.com, a Chinese hackintosh fourm. And this solution is written by [email protected].(Original page link: http://bbs.pcbeta.com/viewthread-1597393-5-1.html can't visit if you are not in China)
First MAKE SURE you have done everything and stuck in a messed up screen after start up.
Then Mount EFI partition on another os and open clover/config.plist.
Step 1
In this step you can either use clover patch or patch the AppleIntelFrameBufferAzul.kext itself.
Change the ig-platform-id in config.plist to 0x0d260007
Config.plist:
Code: 
<key>ig-platform-id</key>
<string>0x0d260007</string>

Step 2
For 10.10.2
Clover patch(config.plist):
Code: 
<dict>
<key>Comment</key>
<string>xvip4420's patch</string>
<key>Find</key>
<data>0700260D0103040300000004000020020000500100000060A1070000A1070000000000000000000000000800020000003000000001050B00000400000701000002040B0000040000070100000306030000080000060000001E03000005050900040000000000000000000000000000000000000000000000320000000E000000</data>
<key>Name</key>
<string>AppleIntelFramebufferAzul</string>
<key>Replace</key>
<data>
0700260D01030403000000060000200200000000000000809914000099140000000000000000000000000800020000003000000001050B00000400000701000002040B0000040000070100000306030000080000060000000200000001010000040000000000000000000000000000000000000000000000320000000E000000</data>
</dict>
For 10.10.3
Clover patch(config.plist):
Code: 
<dict>
<key>Comment</key>
<string>xvip4420's patch</string>
<key>Find</key>
<data>0700260D0103040300000004000020020000500100000060A1070000A1070000000000000000000000000800020000003000000001050B00000400000701000002040B0000040000070100000306030000080000060000001E0300000505090004000000320000000E00000000000000</data>
<key>Name</key>
<string>AppleIntelFramebufferAzul</string>
<key>Replace</key>
<data>0700260D01030403000000060000200200000000000000809914000099140000000000000000000000000800020000003000000001050B00000400000701000002040B000004000007010000030603000008000006000000020000000101000004000000320000000E00000000000000</data>
</dict>

This can fix the screen mess up issue but not helpful to the black line on the bottom. But if you change HiDPI to under 1920x1080, the black line will disappeare.
If not useful or have any other screen rendering issues, try log out and re-login. Then if still not useful, try use both clover patch and patched AppleIntelFrameBufferAzul.kext.
This solution haven't been tested on 10.10.5.
This solution have used script "AppleIntelFrameBufferAzul.sh" written by"test.sh v3.0 Copyright (c) 2012-2015 by Pike R. Alpha".
Attached patched AppleIntelFrameBufferAzul.kext
View attachment 149538
Click to expand...

Using that framebuffer is likely to be problematic. 0x0d260007 assumes a 64mb DVMT-prealloc. This patch changes to 96mb. The default for most Haswell laptops is 32mb.

I looked at the actual changes being made...

header data...
from:
Code: 
0700 260d 0103 0403 0000 [B]0004[/B] 0000 2002
0000 5001 0000 [B]0060[/B] [B]a107[/B] 0000 [B]a107[/B] 0000
0000 0000 0000 0000

to:
Code: 
0700 260D 0103 0403 0000 [B]0006[/B] 0000 2002 
0000 0000 0000 [B]0080[/B] [B]9914[/B] 0000 [B]9914[/B] 0000 
0000 0000 0000 0000

changes:
DVMT-prealloc from 64mb -> 96mb
VRAM from 1536mb -> 2048mb
BCL freq from 1953Hz -> 5273Hz (this affects backlight operation of the kext, but is insignificant when using ACPIBacklight.kext)

connectors:
Code: 
0000 0800 0200 0000 3000 0000
0000 0800 0200 0000 3000 0000

0105 0b00 0004 0000 0701 0000 
0105 0B00 0004 0000 0701 0000

0204 0b00 0004 0000 0701 0000
0204 0B00 0004 0000 0701 0000

0306 0300 0008 0000 0600 0000
0306 0300 0008 0000 0600 0000

No change (HDMI-audio not implemented)

trailer data...
from:
Code: 
[B]1e03[/B] 0000 [B]0505[/B] [B]0900[/B] 0400 0000 3200 0000 0e00 0000 0000 0000

to:
Code: 
[B]0200[/B] 0000 [B]0101[/B] [B]0000[/B] 0400 0000 3200 0000 0E00 0000 0000 0000

The meaning of this data is not known... comparing against the same data in 0x0a2e0008...

0xa2e0008:
Code: 
[B]1e00[/B] 0000 [B]0505[/B] 09[B]01[/B] [B][B]0000[/B][/B] 0000 3200 0000 0000 0000 0000 0000
 
RehabMan said:
Unless you manage to reset the setting. For example, I wonder if resetting BIOS to defaults will affect it?

I suppose if it did, you'd need to flash unlocked BIOS, change it, then reflash newer BIOS...



If you can confirm Lenovo part#/FRU#, I'll add it to post #1... assuming it is not already there.
Click to expand...

This one I can confirm, I downgrade the bios to 1.14 and use the EFI-Tool to change the DMVT. However with 1.14 there is problem in Win10 to find the NV card, so I had to upgrade the bios. But the setting survived. I think if there is a resetting, I will just downgrade it to 1.14 and change it and flash back.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top