Contribute
Register
Status
Not open for further replies.
4k@60 might be a stretch for macOS/Haswell,... but you might try with -cdfon and WhateverGreen.kext.
Thanks a lot! It works!!
upload_2018-10-11_0-20-57.png

upload_2018-10-11_0-21-6.png

I don't know why lenovo says that with hd4400 & dp port ---> 4k@30hz
 
Successfully got High Sierra to work! Thank you so much for your detailed guide.

Is a Mojave guide being made for the T440p?
 
Successfully got High Sierra to work! Thank you so much for your detailed guide.

Is a Mojave guide being made for the T440p?

Hi MaxMaxBoBax,

I do confirm that Mojave works on T440p. I have installed High Sierra first, then updated it to Mojave using standard installation from AppStore. I had only to reapply alc_fix. Besides that everything works perfectly.

@RehabMan - maybe you can explain this phenomenon to me. After updating macOS to Mojave my Bluetooth started to work: https://screenshot.net/6ez6yse. I still haven't replaced standard Intel WiFi (but I have modded BIOS). Sometimes it disappears, sometimes it shows up, but when it shows up it works flawlessly...
 
Hi MaxMaxBoBax,

I do confirm that Mojave works on T440p. I have installed High Sierra first, then updated it to Mojave using standard installation from AppStore. I had only to reapply alc_fix. Besides that everything works perfectly.

@RehabMan - maybe you can explain this phenomenon to me. After updating macOS to Mojave my Bluetooth started to work: https://screenshot.net/6ez6yse. I still haven't replaced standard Intel WiFi (but I have modded BIOS). Sometimes it disappears, sometimes it shows up, but when it shows up it works flawlessly...

The FAQ has BT/WiFi hardware recommendations:
http://www.tonymacx86.com/el-capita...faq-read-first-laptop-frequent-questions.html
 
Is there any need to flash a modded BIOS if you don't need WiFi? Looking through the BIOS (t440p, v2.50), I can disable anti theft and the security chip, but there's no TPM option.
 
Is there any need to flash a modded BIOS if you don't need WiFi? Looking through the BIOS (t440p, v2.50), I can disable anti theft and the security chip, but there's no TPM option.

In my opinion - no. I was using T440p with standard BIOS and USB dongle WiFi for few weeks and if you don't need Bluetooth - it doesn't make much sense to spend bunch of dollars for BIOS mod and accessories.

Currently I have modded BIOS and DW1830 - works flawlessly, but Bluetooth was "must-have" for me.
 
In my opinion - no. I was using T440p with standard BIOS and USB dongle WiFi for few weeks and if you don't need Bluetooth - it doesn't make much sense to spend bunch of dollars for BIOS mod and accessories.

Currently I have modded BIOS and DW1830 - works flawlessly, but Bluetooth was "must-have" for me.

Good to know, thanks! I'll skip the BIOS mod for now then. I've literally never used bluetooth, and I don't need wifi 90% of the time. A dongle will suffice. Cheers
 
Hi MaxMaxBoBax,

I do confirm that Mojave works on T440p. I have installed High Sierra first, then updated it to Mojave using standard installation from AppStore. I had only to reapply alc_fix. Besides that everything works perfectly.

I updated from 10.13.6 to 10.14.1 using the App Store, after a few reboots of the installer Clover no longer shows my MacOS partition to boot from, only the recovery partition and Windows which is installed on a separate drive are displayed.

I'm running the latest clover with all the latest EFI files in EFI/CLOVER/drivers64-UEFI.

I have attached a screenshot of some APFS error messages that are displayed just before Clover starts and I've used Windows to create a ZIP of the EFI folder and attached that too.

One interesting thing I've found is that if i replace the config.plist from the OP with the default one that is provided with Clover then every partition i have is displayed by Clover. However once it boots to the FileVault unlock screen it reboots after I type the password. I have no idea which things to copy and paste from this config.plist into the correct one for the T440p provided by the OP.

Any advice would be very much appreciated as i've been tearing my hair hour for several hours now. :/
 

Attachments

  • EFI.zip
    2.1 MB · Views: 86
  • IMG_20181117_201419.jpg
    IMG_20181117_201419.jpg
    395.9 KB · Views: 95
I updated from 10.13.6 to 10.14.1 using the App Store, after a few reboots of the installer Clover no longer shows my MacOS partition to boot from, only the recovery partition and Windows which is installed on a separate drive are displayed.

I'm running the latest clover with all the latest EFI files in EFI/CLOVER/drivers64-UEFI.

I have attached a screenshot of some APFS error messages that are displayed just before Clover starts and I've used Windows to create a ZIP of the EFI folder and attached that too.

One interesting thing I've found is that if i replace the config.plist from the OP with the default one that is provided with Clover then every partition i have is displayed by Clover. However once it boots to the FileVault unlock screen it reboots after I type the password. I have no idea which things to copy and paste from this config.plist into the correct one for the T440p provided by the OP.

Any advice would be very much appreciated as i've been tearing my hair hour for several hours now. :/

See guide for correct drivers64UEFI content:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/
 

Thanks, i'm not trying to boot from a USB installler, I'm trying to boot an already existing and previously bootable installation.

I have everything I need in the Drivers64UEFI folder already. It recognised the partitions under High Sierra and it also recognises them with Mojave if I replace the T440P config.plist from the OP with an incorrect config.plist, so I'm assuming there is something in the default clover plist that is needed for Mojave but missing in the previously working T440P plist.

What that is though I honestly have no idea.

Contents of drivers64UEFI folder:
Code:
ApfsDriverLoader-64.efi
AppleImageCodec-64.efi
AppleKeyAggregator-64.efi
AppleKeyFeeder-64.efi
AppleUiSupport.efi
AppleUITheme-64.efi
AptioMemoryFix-64.efi
DataHubDxe-64.efi
EmuVariableUefi-64.efi
Fat-64.efi
FirmwareVolume-64.efi
FSInject-64.efi
HashServiceFix-64.efi
HFSPlus.efi
OsxAptioFix2Drv-64.efi
OsxFatBinaryDrv-64.efi
PartitionDxe-64.efi
SMCHelper-64.efi

edit:

I've attatched the preboot.log. The following messages look like everything should be ok to me which is why it's so baffling.

Code:
 === [ LoadDrivers ] =======================================
0:105  0:000  Loading DataHubDxe-64.efi  status=Success
0:126  0:020  Loading FSInject-64.efi  status=Success
0:126  0:000  Loading SMCHelper-64.efi  status=Success
0:127  0:000  Loading Fat-64.efi  status=Success
0:128  0:000   - driver needs connecting
0:128  0:000  Loading AppleImageCodec-64.efi  status=Success
0:129  0:000  Loading AppleKeyAggregator-64.efi  status=Success
0:130  0:000  Loading AppleKeyFeeder-64.efi  status=Success
0:130  0:000  Loading AppleUITheme-64.efi  status=Success
0:131  0:000  Loading FirmwareVolume-64.efi  status=Success
0:131  0:000  Loading HashServiceFix-64.efi  status=Success
0:131  0:000  Loading ApfsDriverLoader-64.efi  status=Success
0:132  0:000   - driver needs connecting
0:132  0:000  Loading EmuVariableUefi-64.efi  status=Success
0:132  0:000  EmuVariableUefi Initialize: VariableCommonInitialize = Success, orig services stored, install gEmuVariableControlProtocolGuid = Success
0:133  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
0:133  0:000  Loading PartitionDxe-64.efi  status=Success
0:134  0:000   - driver needs connecting
0:134  0:000  Loading AppleUiSupport.efi  status=Success
0:236  0:102  Loading AptioMemoryFix-64.efi  status=Success
0:238  0:002  Loading HFSPlus.efi  status=Success
0:240  0:001   - driver needs connecting
0:240  0:000  4 drivers needs connecting ...
0:240  0:000  PlatformDriverOverrideProtocol not found. Installing ... Success
0:240  0:000  Partition driver loaded:
0:240  0:000  HFS+ driver loaded
0:240  0:000  APFS driver loaded
0:240  0:000  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok

Code:
1:226  0:000  === [ ScanLoader ] ========================================
1:226  0:000  - [03]: 'EFI'
1:229  0:003          AddLoaderEntry for Volume Name=EFI
1:229  0:000       skipped because path `PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x5,0x0,0x0)\HD(2,GPT,B1A09B84-DF83-42AC-9CC8-8EE8FB36BDC2,0xFA000,0x32000)\EFI\microsoft\Boot\bootmgfw.efii` already exists for another entry!
1:231  0:001          AddLoaderEntry for Volume Name=EFI
1:231  0:000          skipped because entry is hidden
1:231  0:000  - [06]: 'EFI'
1:232  0:000          AddLoaderEntry for Volume Name=EFI
1:232  0:000          skipped because entry is hidden
1:232  0:000  - [08]: 'Preboot', hidden
1:232  0:000  - [09]: 'Hackintosh HD'
1:232  0:000  - [10]: 'Recovery'
1:234  0:001          AddLoaderEntry for Volume Name=Recovery
1:240  0:005  === [ AddCustomTool ] =====================================

Using the default Clover config.plist the preboot.log shows the same for the driver loading but the following for the ScanLoader section:

Code:
1:126  0:000  === [ ScanLoader ] ========================================
1:126  0:000  - [02]: 'EFI'
1:127  0:000          AddLoaderEntry for Volume Name=EFI
1:127  0:000          skipped because entry is hidden
1:127  0:000  - [05]: 'EFI'
1:130  0:003          AddLoaderEntry for Volume Name=EFI
1:132  0:001          AddLoaderEntry for Volume Name=EFI
1:132  0:000          skipped because entry is hidden
1:132  0:000  - [08]: 'Preboot'
1:134  0:002          AddLoaderEntry for Volume Name=Preboot
1:137  0:002      Check if volume Is Hibernated:
1:137  0:000      Check sleep image 'by signature':
1:137  0:000      using default sleep image name = \private\var\vm\sleepimage
1:137  0:000      sleepimage not found -> Not Found
1:137  0:000      hibernated: no - sign
1:139  0:001          AddLoaderEntry for Volume Name=Preboot
1:145  0:006  - [09]: 'Hackintosh HD'
1:146  0:000  - [10]: 'Recovery'
1:147  0:001          AddLoaderEntry for Volume Name=Recovery
1:153  0:005  Scanning legacy ...
1:153  0:000   4: 'Legacy HD1' (vista,win) add legacy
1:153  0:000   added 'Boot Windows from Legacy HD1' OSType=2 Icon=vista,win
1:153  0:000   5: 'EFI' (vista,win) add legacy
1:153  0:000   added 'Boot Windows from EFI' OSType=2 Icon=vista,win
1:153  0:000   7: 'Legacy HD4' (vista,win) add legacy
1:153  0:000   added 'Boot Windows from Legacy HD4' OSType=2 Icon=vista,win
1:153  0:000  === [ AddCustomTool ] =====================================
 

Attachments

  • preboot.log.txt
    28.6 KB · Views: 135
Last edited:
Status
Not open for further replies.
Back
Top