Jump to content
Kogen Mantis

Lenovo ThinkPad T420 with UEFI Only

4,583 posts in this topic

Recommended Posts

Advertisement

@timewalker75a - wow that was easy. fantastic. just curious how do you/we know 1312 is the right max?!

 

@zhangqq - interesting. does this make  shutdown work (period) - meaning it did not work at all - or that is makes shutdown work better (ie not hang)?

1312 is the maximum PNLF (Apple's Display Panel) can handle. And this is the value it defaults to after sleep, as in.. the brightness cap increases after sleep from 0710 to 1312.

 

Re: reset address and values - this fix was originally discovered by fassl and was needed for older hardware where FACP table didn't contain this data, so restart was not functional. Bootloaders are now altering this table and increasing it's length for platforms where FACP doesn't include this data. If you dump your native ACPI tables from clover by pressing F4 in GUI and then open up your FACP table from /EFI/CLOVER/ACPI/origin you'll see that this data is already in there .. and it only affects restart, which is done through PS/2 controller, which is a part of Embedded controller... so shutdown was fixed by SLPE, not this... this doesn't even need to be there.  

[000h 0000   4]                    Signature : "FACP"    [Fixed ACPI Description Table (FADT)]
[004h 0004   4]                 Table Length : 000000F4
[008h 0008   1]                     Revision : 03
[009h 0009   1]                     Checksum : E6
[00Ah 0010   6]                       Oem ID : "DELL  "
[010h 0016   8]                 Oem Table ID : "QA09   "
[018h 0024   4]                 Oem Revision : 00000002
[01Ch 0028   4]              Asl Compiler ID : "PTL "
[020h 0032   4]        Asl Compiler Revision : 00000002
....

[074h 0116  12]               Reset Register : [Generic Address Structure]
[074h 0116   1]                     Space ID : 01 [SystemIO]
[075h 0117   1]                    Bit Width : 08
[076h 0118   1]                   Bit Offset : 00
[077h 0119   1]         Encoded Access Width : 00 [Undefined/Legacy]
[078h 0120   8]                      Address : 0000000000000064

[080h 0128   1]         Value to cause reset : FE

Share this post


Link to post
Share on other sites

Hi guys-

This is not important of course, but aiming to a perfect laptop running OS X...

The wifi light is not on, even if the wifi is enabled. Any easy fix that could correct this?

 

Thanks,

AJ

Share this post


Link to post
Share on other sites

TimeWalker - thanks that is great information.

 

well the FACP table shows this info - which according to the WIKI,Clover will read and use. in this case the PCI bus. agree with that for the T420 - the reset values do not need to specified in the config.plist

 

 

 

[074h 0116  12]               Reset Register : [Generic Address Structure]
[074h 0116   1]                     Space ID : 01 [systemIO]
[075h 0117   1]                    Bit Width : 08
[076h 0118   1]                   Bit Offset : 00
[077h 0119   1]         Encoded Access Width : 00 [undefined/Legacy]
[078h 0120   8]                      Address : 0000000000000CF9
 
[080h 0128   1]         Value to cause reset : 06
[081h 0129   3]                     Reserved : 000000
[084h 0132   8]                 FACS Address : 00000000DAF2D000
[08Ch 0140   8]                 DSDT Address : 00000000DAFEB000
 
@AJ - will look at this later to see if i can figure out which LED lights that up. there is a DSDt function called SI that i used to reset the power and sleep LEDs. may be manual since OSX may not have this?

Share this post


Link to post
Share on other sites

 

@okcakep (get blank monitor if you're using custom EDID in config.plist)

then make this change in red (delete or change)

InjectEDID to false is enought if your EDID is not the good one it would become the good one in newer system

------------------

 

good edid can be found this thisattachicon.gifgenEDID_3c.zip

 

unzip drag & drop genEDID.sh on Terminal.app window, key name of screen for example LCD

 

tetonne$ /Users/tetonne/Desktop/genEDID.sh LCD press enter
 
result  in terminal
Collecting some data...
Detected Vendor ID: 0x6af (hex) 1711 (dec)
Detected Product ID: 0x313c (hex) 12604 (dec)
Flipbyted Vendor ID: 0xaf06 (hex) 44806 (dec)
Detected EDID: 00ffffffffffff0006af3c310000000000140103801f11780a10b597585792261e505400000001010101010101010101010101010101121b5646500023302616360035ad100000180000000f0000000000000000000000000020000000fe0041554f0a202020202020202020000000fe004231343058573033205631200a0029
Encoded EDID: AP///////wAGrzwxAAAAAAAUAQOAHxF4ChC1l1hXkiYeUFQAAAABAQEBAQEBAQEB
AQEBAQEBEhtWRlAAIzAmFjYANa0QAAAYAAAADwAAAAAAAAAAAAAAAAAgAAAA/gBB
VU8KICAgICAgICAgAAAA/gBCMTQwWFcwMyBWMSAKACk=
Job done!
 
report that green number in OEMConfig
Graphic CustomEDID data (in XML part)
00ffffffffffff0006af3c310000000000140103801f11780a10b597585792261e505400000001010101010101010101010101010101121b5646500023302616360035ad100000180000000f0000000000000000000000000020000000fe0041554f0a202020202020202020000000fe004231343058573033205631200a0029
 
you'll seen Encoded EDID: AP///////wAGrzwxAAAAAAAUAQOAHxF4ChC1l1hXkiYeUFQAAAABAQEBAQEBAQEB
AQEBAQEBEhtWRlAAIzAmFjYANa0QAAAYAAAADwAAAAAAAAAAAAAAAAAgAAAA/gBB
VU8KICAgICAgICAgAAAA/gBCMTQwWFcwMyBWMSAKACk=
there

set InjectEDID to true

 
result on destop :
put the created folder DisplayVendorID-6af (example) in S/L/Display/Overrides
repair permissons

 

Tetonne....amazing...work....!!!

Thank you....

Share this post


Link to post
Share on other sites

@okcakep : you're welcome :)

@all could you please add your signature ;)

 

feed back about  T420_UEFI_Clover-b2236_10.8.5_10.9.0_16-Oct-2013

As usual great work :) brightness is equal as before sleep

I add tluck's pack url in my signature (a way say :thanks_speechbubble: )

 

@timewalker75a : thanks for your contribution too

@tluck : thanks for the great pack you provide each time 

Share this post


Link to post
Share on other sites

I want to install OS X Mavericks on Thinkpad T420s, how can I patch my own dsdt based on your patched files?

 

I also want to use ultrabay to replace my dvd drive by a hdd, I saw some posts long ago said that the system can only boot to internal drive Clover without it, is it fixed yet?

Share this post


Link to post
Share on other sites

I also want to use ultrabay to replace my dvd drive by a hdd, I saw some posts long ago said that the system can only boot to internal drive Clover without it, is it fixed yet?

Use shell from within Clover (new revision preferably) and add bcfg boot entry pointing to your optibay (utrabay?) drive. The entry will then appear under F12 boot menu..

Share this post


Link to post
Share on other sites

@pokenguyen - there is dsdt.aml and dsdt.dsl (source with change comments) for any T420 - ready for use in the zip bundle. otherwise i don't understand your question. 

Share this post


Link to post
Share on other sites

@pokenguyen - there is dsdt.aml and dsdt.dsl (source with change comments) for any T420 - ready for use in the zip bundle. otherwise i don't understand your question.

T420s model can't use the same dsdt, but I think it will be very similar. I want to know which patches you applied to your dsdt so I can patch it myself.

Share this post


Link to post
Share on other sites

@pokenguyen - there is dsdt.aml and dsdt.dsl (source with change comments) for any T420 - ready for use in the zip bundle. otherwise i don't understand your question.

T420s model can't use the same dsdt, but I think it will be very similar. I want to know which patches you applied to your dsdt so I can patch it myself.

Share this post


Link to post
Share on other sites

I don't have a 420 to confirm, but gendalo and I have different t430's and it turns out that the dsdt's are identical. Likely it is true of 420's as well.

Share this post


Link to post
Share on other sites

I don't have a 420 to confirm, but gendalo and I have different t430's and it turns out that the dsdt's are identical. Likely it is true of 420's as well.

I will give it a try, thank you for confirm.

Share this post


Link to post
Share on other sites

@Tluck now im using 10.8.5 with your package. work !!!. i must be reconfigure Athereos WiFi to pci168c,2b

Sound work perfect...thanks...!!!

@Tetone your EDID work...but i still get glich sometime :)

 

Update...

Suddenly no sound in internal speaker,

Headphone ok

Share this post


Link to post
Share on other sites

            If (LEqual (Arg0, 0x05))


            {


                TRAP ()


                AWON (0x05)


                Store (Zero, SLPE)


                Sleep (0x10)


           


 


I guess store(zero,SLPE) should be store(one, SLPE). (I won't use the tags for shutdown now.)


I also add Store (One, SLPE) and Sleep (0x10) to arg0 = 0x01 0x03 0x04.


Then I add Store (Zero, SLPE) and Sleep (0x10) ad the beginning of _WAK and _INI.


 


The shutdown and sleep work fine till now.

Share this post


Link to post
Share on other sites

 

            If (LEqual (Arg0, 0x05))

            {

                TRAP ()

                AWON (0x05)

                Store (Zero, SLPE)

                Sleep (0x10)

           

 

I guess store(zero,SLPE) should be store(one, SLPE). (I won't use the tags for shutdown now.)

I also add Store (One, SLPE) and Sleep (0x10) to arg0 = 0x01 0x03 0x04.

Then I add Store (Zero, SLPE) and Sleep (0x10) ad the beginning of _WAK and _INI.

 

The shutdown and sleep work fine till now.

 

That's right - you GUESS, while Intel STATES:

4Clbb.png

Every state passed as the argument to _PTS is a sleep state, be it suspend type (0x1 and 0x3), lid 0x4 or soft-off (0x5).

Share this post


Link to post
Share on other sites

@pokenguyen - misunderstood your model is a T420S and not plain T420. here is a zip of the original dsdt and current dsdt.dsl (with comments) - you can diff them to see what was add/changed. 

 

t420_dsdt.zip

 

@okcakep

 

1) the sound loss from laptop speaker is known to be result of changes in 10.8.5 v1.8 AppleACPIPlatform.kext. laptop will lose speaker after wake from sleep. if you rollback to 10.8.4 v1.7 AppleACPIPlatform.kext this will not happen. 

 

2) EDID and glitches. is your native EDID different than the one Tetonne provided. is it v1.3? look for 0103 string vs 0104 string. i am injecting a different EDID (v1.3 seems work) than what was native/built-in to fix the glitches. 

 

in reality i never figured out why one EDID worked and another didn't. here were 2 v1.3 EDIDs for LCD 1600x900 - one was native (from windows) - i suspect it is the diff in detail clocking timings info? works is 96 Mhz and the glitchy one is 110 Mhz

 

works:

 

Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   30 e4 e2 02 00 00 00 00 00 14
version:         01 03
basic params:    80 1f 11 78 0a
chroma info:     43 45 97 59 57 8e 28 21 50 54
established:     00 00 00
standard:        01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:    80 25 40 80 60 84 1a 30 30 20 35 00 36 ae 10 00 00 19
descriptor 2:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 3:    00 00 00 fe 00 4c 47 20 44 69 73 70 6c 61 79 0a 20 20
descriptor 4:    00 00 00 fe 00 4c 50 31 34 30 57 44 32 2d 54 4c 42 31
extensions:      00
checksum:        38
 
Manufacturer: LGD Model 2e2 Serial Number 0
Made week 0 of 2010
EDID version: 1.3
Digital display
Maximum image size: 31 cm x 17 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
Standard timings supported:
Detailed mode: Clock 96.000 MHz, 310 mm x 174 mm
               1600 1648 1680 1728 hborder 0
                900  903  908  926 vborder 0
               -hsync -vsync 
 

 

 

glitches:

 

Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   30 ae a1 40 00 00 00 00 01 14
version:         01 03
basic params:    80 1f 11 78 ea
chroma info:     cc ce 99 58 50 8e 26 24 4b 53
established:     00 00 00
standard:        01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:    f8 2a 40 9a 61 84 0c 30 40 2a 33 00 35 ae 10 00 00 18
descriptor 2:    cf 23 40 9a 61 84 0c 30 40 2a 33 00 35 ae 10 00 00 18
descriptor 3:    00 00 00 0f 00 a9 09 32 a9 09 32 19 09 00 06 af 56 31
descriptor 4:    00 00 00 fe 00 42 31 34 30 52 57 30 32 20 56 31 20 0a
extensions:      00
checksum:        7b
 
Manufacturer: LEN Model 40a1 Serial Number 0
Made week 1 of 2010
EDID version: 1.3
Digital display
Maximum image size: 31 cm x 17 cm
Gamma: 2.20
DPMS levels: Standby Suspend Off
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
Standard timings supported:
Detailed mode: Clock 110.000 MHz, 309 mm x 174 mm
               1600 1664 1706 2010 hborder 0
                900  903  906  912 vborder 0
               -hsync -vsync 
Detailed mode: Clock 91.670 MHz, 309 mm x 174 mm
               1600 1664 1706 2010 hborder 0
                900  903  906  912 vborder 0
               -hsync -vsync 

Share this post


Link to post
Share on other sites

 

@pokenguyen - misunderstood your model is a T420S and not plain T420. here is a zip of the original dsdt and current dsdt.dsl (with comments) - you can diff them to see what was add/changed. 

 

attachicon.gift420_dsdt.zip

 

 

Thank you very much, I'm new to Thinkpad and waiting my caddy to arrive before installing. I will give it a look.

Btw, I think you should replace VboxHFS-64.efi by HFSPlus.efi for better OSX Install support. With the drivers, you can create install usb for 10.8 by restoring InstallESD.dmg, or use createmediainstall tool for 10.9. Very easy.

Share this post


Link to post
Share on other sites

I just studied P8Z68-V PRO's dsdt  and found something interesting.

 

                Name (SMCR, 0x0430)

 

                OperationRegion (SLPR, SystemIO, SMCR, 0x08)
                Field (SLPR, ByteAcc, NoLock, Preserve)
                {
                        ,   4,
                    SLPE,   1,
                        ,   31,
                    SLPX,   1
                }

 

 

                Method (SWAK, 1, NotSerialized)
                {
                    Store (Zero, SLPE)
                    If (LNot (RTCS))
                    {
                        Notify (PWRB, 0x02)
                    }
                }

 

    Method (_PTS, 1, NotSerialized)
    {
        Store (Zero, P80D)
        P8XH (Zero, Arg0)
        If (Arg0)
        {
            Store (One, \_SB.PCI0.LPCB.SLPX)   <==I think this is another one we missed.
            Store (One, \_SB.PCI0.LPCB.SLPE)  <== ASUS put SLPE here, it is the same as our SLPE.
            If (LAnd (LGreater (Arg0, 0x03), LLess (Arg0, 0x06)))
            {
                Store (Arg0, \_SB.SMIC)
                Store (One, GP27)
            }
        }
    }
    Method (_WAK, 1, Serialized)
    {
        ShiftLeft (Arg0, 0x04, DBG8)
        \_SB.PCI0.LPCB.SWAK (Arg0)
        Store (Zero, \_SB.PCI0.LPCB.PLED)
        Return (Package (0x02)
        {
            Zero,
            Zero
        })
    }
}


I found the follow combination worked.

 

1) SlpSmiAtWake => true

2) Add SLPE = 0  to _WAK  and SLPE = 1 to _PTS(arg0 = 1,3,4,5)

Share this post


Link to post
Share on other sites

And yet Asus board have HAD this shutdown bug in UEFI boot until endless figured out that it has to write 0 and not 1 to SLP_SMI_EN register (which is SLPE) .. whats SLPX - nobody knows and it's not even documented in chipset specification, while PM30+4 bit register is.

 

SlpSmiAtWake was my request to slice, and it's actually broken and is poorly implemented, all it does is makes a change to your DSDT to unconditionally write 1 to SLPE when _WAK is called. On Tiano firmware this results in broken wake, when the laptop has been put to sleep by closing the lid.

Share this post


Link to post
Share on other sites

@pokenguyen - great.  glad to have another voice and platform on this thread

 

HFSPlus.efi (i have an HFSPlus-64.efi) ... but sure i can give that a try- what does that do better that Vbox?

i made my 10.8 and 10.9 installers using this approach - basically put "BaseSystem" on the USB. made it more like "regular OS" so was more intuitive to me. These are my notes on how i do it:


format USB GUID with 1 or 2 partitions
expand and show all files in downloaded installer app
 
find and open/mount InstallESD.dmg in Contents/SharedSupport
extract BaseSystem.dmg (will be hidden)
restore this image to USB using Disk Utility
remove /Volume/USB/System/Installation/Package (link file)
cp -rp Packages (from installer InstallESD.dmg) to /Volume/USB/System/Installation/
extract (pacifist) mach_kernel from Packages/BaseSystemBinaries.pkg and put in USB/
 
TIPS:
turn on Disk Utility debug mode - you can see hidden partitions 
run:
defaults write com.apple.DiskUtility DUDebugMenuEnabled 1
 
if your usb is disk 2 
 
$ diskutil list
 
mount your ESP manually:
sudo mkdir /Volumes/ESP_USB
sudo mount -t msdos /dev/disk2s1 /Volumes/ESP_USB
 
unzip bundle (say in  Downloads)
 
cp -rp ~/Downloads/EFI /Volumes/ESP_USB
cd /Volumes/ESP_USB/EFI/CLOVER
mv OEM OEM.NU
 
 
@zhangqq - well interesting and this stuff may work on a different Mobo/embedded controller. but, for me i am not keen on testing as i don't want to brick my box! anyway,  i am happy with the restart and shutdown function currently. 

Share this post


Link to post
Share on other sites

 

@pokenguyen - great.  glad to have another voice and platform on this thread

 

HFSPlus.efi (i have an HFSPlus-64.efi) ... but sure i can give that a try- what does that do better that Vbox?

i made my 10.8 and 10.9 installers using this approach - basically put "BaseSystem" on the USB. made it more like "regular OS" so was more intuitive to me. These are my notes on how i do it:

format USB GUID with 1 or 2 partitions
expand and show all files in downloaded installer app
 
find and open/mount InstallESD.dmg in Contents/SharedSupport
extract BaseSystem.dmg (will be hidden)
restore this image to USB using Disk Utility
remove /Volume/USB/System/Installation/Package (link file)
cp -rp Packages (from installer InstallESD.dmg) to /Volume/USB/System/Installation/
extract (pacifist) mach_kernel from Packages/BaseSystemBinaries.pkg and put in USB/
 
@zhangqq - well interesting and this stuff may work on a different Mobo/embedded controller. but, for me i am not keen on testing as i don't want to brick my box! anyway,  i am happy with the restart and shutdown function currently. 

 

Using HFSPlus.efi can boot to special Install USB, which can create Recovery HD after installing. Creating Install USB is much easier than your method:

10.8: Restore InstallESD.dmg to flash drive

10.9: Run the following command:

sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --nointeraction

Share this post


Link to post
Share on other sites

@timewalker - here is what i get in the logs... on 10.9 no sound from speaker after sleep/wake (2 cycles) below:

 

Oct 17 14:11:44 toms-mac com.apple.kextd[14]: WARNING - Invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext "/Users/tluck/Downloads/CodecCommander.kext"

Oct 17 14:11:45 toms-mac kernel[0]: CodecCommander::init: Initializing

Oct 17 14:11:45 toms-mac kernel[0]: CodecCommander::init: make Lenovo

Oct 17 14:11:45 toms-mac kernel[0]: CodecCommander::probe: Probing

Oct 17 14:11:45 toms-mac kernel[0]: CodecCommander::start: Starting

Oct 17 14:11:45 toms-mac kernel[0]: CodecCommander: command 1470c02 written to ICW register

Oct 17 14:11:45 toms-mac kernel[0]: CodecCommander: status of ICB field changed to 1

Oct 17 14:11:45 toms-mac kernel[0]: CodecCommander: get status of IRV field

Oct 17 14:24:43 toms-mac kernel[0]: CodecCommander::power: is off

Oct 17 14:24:51 toms-mac kernel[0]: CodecCommander: command 1470c02 written to ICW register

Oct 17 14:24:51 toms-mac kernel[0]: CodecCommander: status of ICB field changed to 1

Oct 17 14:24:51 toms-mac kernel[0]: CodecCommander: get status of IRV field

Oct 17 14:24:51 toms-mac kernel[0]: CodecCommander: response latched in IRR register, IRV returned valid status 2

Oct 17 14:24:51 toms-mac kernel[0]: CodecCommander: command failed, IRV returned invalid status 2

Oct 17 14:24:51 toms-mac kernel[0]: CodecCommander: IRV field cleared, ready for next command

Oct 17 14:24:51 toms-mac kernel[0]: CodecCommander::power: is on

Oct 17 14:28:39 toms-mac kernel[0]: CodecCommander::power: is off

Oct 17 14:28:44 toms-mac kernel[0]: CodecCommander: command 1470c02 written to ICW register

Oct 17 14:28:44 toms-mac kernel[0]: CodecCommander: status of ICB field changed to 1

Oct 17 14:28:44 toms-mac kernel[0]: CodecCommander: get status of IRV field

Oct 17 14:28:44 toms-mac kernel[0]: CodecCommander: response latched in IRR register, IRV returned valid status 2

Oct 17 14:28:44 toms-mac kernel[0]: CodecCommander: command failed, IRV returned invalid status 2

Oct 17 14:28:44 toms-mac kernel[0]: CodecCommander: IRV field cleared, ready for next command

Oct 17 14:28:44 toms-mac kernel[0]: CodecCommander::power: is on

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

  • Similar Content

    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By Averyfreeman
      Dear @tluck 
       
      I have a T460s 20F9-003HUS - I5-6300U 2C 2.4GHz, FHD non-touch, 8GB DDR4, PM961 NVMe, vPro, AMT, etc.
      http://psref.lenovo.com/Detail/ThinkPad_T460s?M=20F9003HUS
       
      I have been following the following thread to hackintosh my T460s:
       but it's very long and hard to sort through, so I thought I'd start a new thread specifically for this issue
       
      Personally, my model has been doing pretty good with just the T460 EFI from github.  I did run the scripts to create and patch a new DSDT, though, after installing patchmatic and iasl.  I also manually installed VooDooPS2Controller.kext by following the guide on RehabMan's git wiki. 
       
      I also re-installed my kexts from CLOVER/kexts/other using kext helper to build them into the kext cache
       
      My only glaring issue is the touchpad.  It's unusably bad, I've had to use a mouse which kinda sucks on a laptop.
       
      It'll be really slow and then all of the sudden be really fast.  It hangs and skips intermittently.  Kind of hard to describe but it's {censored}. 
       
      So far I've tried: 
       
      installing latest version of VooDooPS2Controller, urning off all gestures, modifying speed, patching DSDT with autogen scripts (iASL, patchmatic). 
       
      Has anybody seen this problem?  What do you recommend I do?  
       
      Happy to provide any logs anyone believes would be relevant via pastebin, etc. 
       
      Thank you!
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
       
×