Lenovo ThinkPad T420 with UEFI Only

[tluck]

2 hours ago, Lucratskill said:

 

I have a problem while booting Mojave. I installed the latest EFI from github, and when i'm booting i choose one of the .plist files. But, it shows me the apple logo for two secs and then my system is rebooting. I choosed some of the .plists from the folder and doing the same thing. But sometimes the same plist that reboot, booting successfully! Then i reboot again and i'm choosing the latest succesful plist and it don't work. Any help?

so it sometimes works ... which is different and better than never works. I am seeing a similar pattern with Mojave - about 1 out 5 boots I get a random KP. I say random as the crash dump shows the last kexts installed - and the last kext not the same from crash to crash.

it could be just a timing issue - not sure why it does this because it is not consistent. maybe add -v on boot flags to watch the progress and see if you see something.

[Lucratskill]

1 hour ago, tluck said:

so it sometimes works ... which is different and better than never works. I am seeing a similar pattern with Mojave - about 1 out 5 boots I get a random KP. I say random as the crash dump shows the last kexts installed - and the last kext not the same from crash to crash.

it could be just a timing issue - not sure why it does this because it is not consistent. maybe add -v on boot flags to watch the progress and see if you see something.

 

Adding "-v" was a brilliant idea! It's booting fine. But I feel that the system is slow. Is more laggy than Sierra.

[snike]

On 11/18/2018 at 7:57 PM, tluck said:

@SuperReaper - hard to know what is going on in your situation. i was able to install Sierra, HighSierra and Mojave with the same configuration i posted... 

 

 

@snike - where did you install the GFX kext in /L/E or /S/L/E? - i cant figure out how to not get the slider!? 

 

run these commands to see what you get:

 

$ ioreg -l|grep -v Diag |grep IODisplayPar

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

    | |   | | |       "IODisplayParameters" = {"commit"={"reg"=0},"fade-time2"={"min"=0,"max"=10000,"value"=4000},"linear-brightness-probe"={"min"=0,"max"=4866,"value"=4866},"ggsc"={"min"=0,"max"=65536,"value"=65536},"vblm"={"min"=0,"max"=196608,"value"=65536},"dsyp"={"min"=0,"max"=2,"value"=2},"rgsc"={"min"=0,"max"=65536,"value"=65536},"fade-style"={"min"=0,"max"=10,"value"=0},"fade-time1"={"min"=0,"max"=10000,"value"=500},"bgsc"={"min"=0,"max"=65536,"value"=65536},"brightness-probe"={"min"=0,"max"=1024,"value"=1024},"fade-time3"={"min"=0,"max"=10000,"value"=500},"bklt"={"min"=0,"max"=4882,"value"=4866},"linear-brightness"={"min"=0,"max"=4866,"value"=4866},"brightness"={"max"=1024,"min"=0,"value"=1024},"brightness-fade"={"min"=0,"max"=1023,"value"=0},"usable-linear-brightness"={"min"=1220,"max"=4866,"value"=4866}}

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

    | |       "IOMatchCategory" = "IODisplayParameters"

    | |       "IODisplayParameters" = {"brightness"={"max"=255,"min"=40},"commit"={"reg"=0}}

 

 

$ ioreg -l|grep -v Diag |grep ApplePanel

    | | |   "ApplePanelRawBrightness" = 4882

    | |       "ApplePanel" = {"F10T02e3"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>}

 

I copied the Kexts to S/L/E. 

This is the o/p from my commands 

$ ioreg -l|grep -v Diag |grep IODisplayPar

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

    | |   | | |       "IODisplayParameters" = {"bgsc"={"min"=0,"max"=65536,"value"=65536},"rgsc"={"min"=0,"max"=65536,"value"=65536},"bklt"={"min"=0,"max"=1808,"value"=1808},"vblm"={"min"=0,"max"=196608,"value"=65536},"ggsc"={"min"=0,"max"=65536,"value"=65536}}

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

    | |   | | |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"

    | |   | | |       "IOMatchCategory" = "IODisplayParameters"

 

The $ ioreg -l|grep -v Diag |grep ApplePanel

doesn't return anything.

[tluck]

@snike - do you have a PNLF (panel) device in your DSDT?

 

you should see something like this:

 

$ ioreg -l|grep PNLF

    | +-o PNLF@0  <class IOACPIPlatformDevice, id 0x100000204, registered, matched, active, busy 0 (30 ms), retain 10>

    | | |   "acpi-path" = "IOACPIPlane:/_SB/PNLF@0"

    | | |   "device-properties" = {"acpi-device"="IOACPIPlatformDevice is not serializable","acpi-path"="IOACPIPlane:/_SB/PNLF@0"}

Edited November 28, 2018 by tluck

[snike]

7 hours ago, tluck said:

@snike - do you have a PNLF (panel) device in your DSDT?

 

you should see something like this:

 

$ ioreg -l|grep PNLF

    | +-o PNLF@0  <class IOACPIPlatformDevice, id 0x100000204, registered, matched, active, busy 0 (30 ms), retain 10>

    | | |   "acpi-path" = "IOACPIPlane:/_SB/PNLF@0"

    | | |   "device-properties" = {"acpi-device"="IOACPIPlatformDevice is not serializable","acpi-path"="IOACPIPlane:/_SB/PNLF@0"}

Hi Tluck, 

This is the o/p from the command 

$ ioreg -l|grep PNLF

    | +-o PNLF@0  <class IOACPIPlatformDevice, id 0x10000015b, registered, matched, active, busy 0 (910 ms), retain 8>

    | |     "device-properties" = {"acpi-device"="IOACPIPlatformDevice is not serializable","acpi-path"="IOACPIPlane:/_SB/PCI0@0/IGPU@20000/PNLF@0"}

[downlord]

Hi Tluck,

since last release on github (Lenovo-T420-Clover-2018.10.31.zip) I've problems with the built in audio.
It used to work 100% in all previous releases.
My main system is still 10.11.6 and I'm getting "No input devices found" and "No output devices found".

I'm using the default config.plist and all kexts are stock.

 

But strangely audio is working on a test High Sierra install on USB disk.

What could be wrong?

Here my System Profiler from 10.11 and Bdmesg.txt

 

BDMESG.txt

Edited November 29, 2018 by downlord
TYPO

[downlord]

Update:

If I change the Layout to 13 in config.plist (dock configuration) everything seems working.

Strange behaviour.

[tluck]

@downlord

 

are you sure you have the latest AppleALC and Lilu? your layout-id should 7 in the UI

the kext takes 13 or 14 and then sets 7 for 

 

tluck@Toms-Mac ~

$ kextstat|grep vit

   38    2 0xffffff7f82e95000 0x79000    0x79000    as.vit9696.Lilu (1.2.8) 43A47FDC-3C92-315E-BF72-E65DC04E7F6B <8 6 5 3 2 1>

   42    0 0xffffff7f82fa2000 0xf0000    0xf0000    as.vit9696.AppleALC (1.3.4) 7801575A-DE67-3C8A-A5EF-0171253D4B2C <38 13 8 6 5 3 2 1>

 

tluck@Toms-Mac ~

$ ioreg -l|grep layout-id

    | |   | |   "layout-id" = <07000000>

    | |   | |   "alc-layout-id" = <0e000000>

 

[MikeDece]

I've been having an issue with the install process, and I don't know if anyone has had it before so I'll outline it as verbosely as I can. 

 

The Issue:

When I try to install macOS High Sierra when booting through clover, I wait a long time for the black apple loading screen, which starts about halfway and then turns completely black about 3/4ths of the way there, at which point it seems to be doing something with my USB drive for a little bit, but then I let it sit there for a half hour and it just idles and I can't tell what it does. When I try to run the installer in verbose mode, it will run for a while, and then at a certain point it completely clears and gives me a black screen.

 

Since I try to have faith in the process, I let it continue, however it does nothing but go to sleep something like 15 minutes after the black screen appears. I wake it up by pressing the power button and it continues to be black. I can tell that there is feedback from the system because the USB flashes in discrete steps rather than flowing on and off when it idles. When I try pressing key combinations like win+space or alt+q, the USB Flashes in responses, but nothing appears on the screen. The mute mic utility button at the top left corner can be turned on and off, but the microphone can't. If I press fn+F4, the computer just immediately suspends, and can be woken up by pressing the power button. This all tells me that there is a live filesystem running on my USB, so it's some kind of graphics issue.

 

When loading into clover, I am presented with a single option, that is, my MacOS USB Installer. I don't change any of the configs, but do run the installation USB in verbose mode. When clover loads up, I don't have a working TrackPoint/Touchpad as the one seen in this video of an installation of High Sierra 10.12.3 on an X220. The config file that I'm booting up with is the default config.plist. 

 

Since I can't get into the installer I figured that maybe I'm supposed to format my HDD ahead of time. I used an ubuntu 18.04 Live USB to delete the existing MSDOS partition table and replace it with a GPT Partition table, and created the partitions as outlined in step 1.4, using HFS+ as the Filesystem. That obviously did nothing for me, but it's something that I've tried. I'm also going to try using different configs and mess around in the settings a bit and so I will update. 

 

 

Contextual Information:

The bootable  is being created onto a 32GB SanDisk Cruzer, in a VM running macOS Sierra version 10.12. The High Sierra Installer App I'm using is version 13.6.02 which I use as directed in the installation guide tluck made. I'm using his latest revision that's up on his GitHub to place into my EFI directory. I followed all the steps in part 1, all the way up to 1.5, which is where I stopped. I didn't use the clover configuration tool that is referenced, as I wanted to do it completely as follows, and feel as though I'm probably missing some information.

 

Relevant Specifications:

Model:				ThinkPad T420  
CPU:				i5 2520m @2.50Ghz
UEFI BIOS Version:		1.46 (83ET76WW)
Embedded Ctrl. Version:		1.20 (83HT30WW)
LCD Resolution:			1366x768
Graphics Chip:			Dell HD3000

 

BIOS Settings:

At the time of writing this, my BIOS settings are as needed in the original post, with the sole difference being:

UEFI/Legacy Boot		[Both]
UEFI/Legacy Boot Priority	[UEFI First]

 

Update:

I changed my config.plist to remove the alt-configurations listed at the bottom and replaced the default 960x600 with 1366x768 and then I ran the clover configuration package and it worked! I'm pretty sure it was the config.plist that changed it though and not the configuration but it's still great. Will continue updating if I run into any issues.

 

Update 2:

I got the installer to write to my main partition and try to install to it, however I got the "macOS could not be installed on your computer" error, and I have a feeling it's because of running the clover configuration

Edited December 5, 2018 by MikeDece
it was not fixed

[MikeDece]

As a follow up to my previous post, it was in fact just the config.plist that needed to be renamed. However, when I got to step 1.5 where you boot into the actual partition, I was given the "macOS could not be installed on your computer" error yet again. This time I realized that you can open the bash shell so I did that and found what seems to be the relevant error message in /private/var/log/install.log. 

 

/private/var/log/install.log

2018-12-05 11:34:47+00 MacBook-Pro OSInstaller[552]: PackageKit: ----- Begin install -----
2018-12-05 11:34:47+00 MacBook-Pro OSInstaller[552]: PackageKit: request=PKInstallRequest <3 packages, destination=/Volumes/macOS>
2018-12-05 11:34:47+00 MacBook-Pro OSInstaller[552]: PackageKit: packages=(
	    "PKLeopardPackage <id=com.apple.pkg.Core, version=10.13.6.1.1.1530695593, url=file:///Volumes/InstallESD/Packages/Core.pkg>",
	    "PKLeopardPackage <id=com.apple.pkg.EmbeddedOSFirmware, version=10.13.6.1.1.1530695593, url=file:///Volumes/InstallESD/Packages/EmbeddedOSFirmware.pkg>",
	    "PKLeopardPackage <id=com.apple.pkg.SecureBoot, version=10.13.6.1.1.1530695593, url=file:///Volumes/InstallESD/Packages/SecureBoot.pkg>"
	)
2018-12-05 11:34:47+00 MacBook-Pro OSInstaller[552]: Evaluating 1 disks
2018-12-05 11:34:47+00 MacBook-Pro OSInstaller[552]: Evaluating <SKDisk 0x7fba46b98990: { Volume Name: "OS X Base System" BSD Name: disk22s1 Mount point: /Volumes/OS X Base System 1 Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS isValid: YES volumeUUID: A9B8826A-0097-3FBF-90D1-31A71529AF8B}>
2018-12-05 11:34:47+00 MacBook-Pro OSInstaller[552]: Warning: Couldn't find boardID, chipID, & ECID in new namespace, falling back
2018-12-05 11:34:47+00 MacBook-Pro OSInstaller[552]: Warning: Couldn't find boardID, chipID, & ECID in new namespace, falling back
2018-12-05 11:34:47+00 MacBook-Pro OSInstaller[552]: OS X Base System is a valid target.
2018-12-05 11:35:46+00 MacBook-Pro Installer Progress[180]: Status is "Installation is in progress. Calculating time remaining…"
2018-12-05 11:35:49+00 MacBook-Pro OSInstaller[552]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=110 "An error occurred while extracting files from the package “Core.pkg”." UserInfo={PKInstallPackageSHA256Digest=f6947c0c5ae5d2bd3bf90a557647131c186627831e182a624c8239b5ed9cd2c4, NSLocalizedDescription=An error occurred while extracting files from the package “Core.pkg”., NSFilePath=/Volumes/macOS/.OSInstallSandboxPath/Root, NSURL=Core.pkg -- file:///Volumes/InstallESD/Packages/OSInstall.mpkg, PKInstallPackageIdentifier=com.apple.pkg.Core, NSUnderlyingError=0x7fba4786a1f0 {Error Domain=PKXARArchiveErrorDomain Code=101 "archive verify failed" UserInfo={NSURL=file:///Volumes/InstallESD/Packages/Core.pkg#Payload, NSFileOwnerAccountID=0, NSFileHFSTypeCode=0, NSFileSystemFileNumber=462, NSFileExtensionHidden=false, NSFileSystemNumber=16777245, NSFileSize=4460809648, NSFileGroupOwnerAccountID=0, NSFileOwnerAccountName=root, NSFilePosixPermissions=420, NSFileHFSCreatorCode=0, NSFileCreationDate=2018-07-04 19:40:30 +0000, NSFileType=NSFileTypeRegular, NSFileGroupOwnerAccountName=wheel, NSFileReferenceCount=1, NSFileModificationDate=2018-07-04 19:42:05 +0000, NSLocalizedDescription=archive verify failed}}} {
	    NSFilePath = "/Volumes/macOS/.OSInstallSandboxPath/Root";
	    NSLocalizedDescription = "An error occurred while extracting files from the package \U201cCore.pkg\U201d.";
	    NSURL = "Core.pkg -- file:///Volumes/InstallESD/Packages/OSInstall.mpkg";
	    NSUnderlyingError = "Error Domain=PKXARArchiveErrorDomain Code=101 \"archive verify failed\" UserInfo={NSURL=file:///Volumes/InstallESD/Packages/Core.pkg#Payload, NSFileOwnerAccountID=0, NSFileHFSTypeCode=0, NSFileSystemFileNumber=462, NSFileExtensionHidden=false, NSFileSystemNumber=16777245, NSFileSize=4460809648, NSFileGroupOwnerAccountID=0, NSFileOwnerAccountName=root, NSFilePosixPermissions=420, NSFileHFSCreatorCode=0, NSFileCreationDate=2018-07-04 19:40:30 +0000, NSFileType=NSFileTypeRegular, NSFileGroupOwnerAccountName=wheel, NSFileReferenceCount=1, NSFileModificationDate=2018-07-04 19:42:05 +0000, NSLocalizedDescription=archive verify failed}";
	    PKInstallPackageIdentifier = "com.apple.pkg.Core";
	    PKInstallPackageSHA256Digest = f6947c0c5ae5d2bd3bf90a557647131c186627831e182a624c8239b5ed9cd2c4;
	}
2018-12-05 11:35:49+00 MacBook-Pro OSInstaller[552]: OSIInstallElement <OSIInstallElement: 0x7fba444c8f60> errored out: Error Domain=PKInstallErrorDomain Code=110 "An error occurred installing macOS. To use Apple Diagnostics to check your Mac hardware, shut down, press the power button, and immediately hold the ‘D’ key until diagnostics begins." UserInfo={NSLocalizedDescription=An error occurred installing macOS. To use Apple Diagnostics to check your Mac hardware, shut down, press the power button, and immediately hold the ‘D’ key until diagnostics begins.}
2018-12-05 11:35:49+00 MacBook-Pro OSInstaller[552]: ------- Install Failed -------

From the looks of it it seems like it needs to verify something and wasn't able to. I'v attached the rest of install.log if there's anything else that I might be missing. I suspect that me not downloading the correct version probably did this, so I'm gonna try reinstalling with a version that I got directly from Apple (not sure why I didn't before).

install.log

Edited December 5, 2018 by MikeDece
i came up with an idea

[MikeDece]

I thought that the error was that they couldn't verify the file or something so I had my friend grab me an authentic installation of High Sierra and tried doing it with that but I got the same error. Although it didn't make much sense, since you should be able to verify files without an internet connection, I tried plugging mine in anyway as a last ditch effort, which also did nothing. The same error as above is what I got.

[tluck]

@MikeDece

 

hmm. i just went through creating a HighSierra and Sierra Installer to validate the process not long ago.

 

so for you, it seems like the installer runs and started to do the install - without black screen when you removed ScreenResolution 900x600?

did it complete install?

is there a microsoft install on the disk?

[snike]

On 11/28/2018 at 11:21 PM, snike said:

Hi Tluck, 

This is the o/p from the command 

$ ioreg -l|grep PNLF

    | +-o PNLF@0  <class IOACPIPlatformDevice, id 0x10000015b, registered, matched, active, busy 0 (910 ms), retain 8>

    | |     "device-properties" = {"acpi-device"="IOACPIPlatformDevice is not serializable","acpi-path"="IOACPIPlane:/_SB/PCI0@0/IGPU@20000/PNLF@0"}

Any suggestions anyone, on how to fix this?

[downlord]

On 12/1/2018 at 4:29 AM, tluck said:

@downlord

 

are you sure you have the latest AppleALC and Lilu?

@tluck

Spot on, as always. Yes I discovered an older version of AppleALC in L/E.
Thank you, now it's working again.

 

[tluck]

@snike

 

are you using the CLover ESP bundle as is? trying to figure out what is missing? 

you have a PNLF device

 

what is your LCD?

 

ioreg -l|grep -v Kit|grep Backlight

    | |   | | | +-o AppleBacklightDisplay  <class AppleBacklightDisplay, id 0x10000042b, registered, matched, active, busy 0 (0 ms), retain 8>

    | |   | | |       "IOClass" = "AppleBacklightDisplay"

    | |   | | |       "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0/display0/AppleBacklightDisplay-30e4-2e3"

    | | |   "AppleBacklightAtBoot" = 4882

    | |       "CFBundleIdentifier" = "com.apple.driver.AppleBacklight"

    | |       "IOPersonalityPublisher" = "org.rehabman.driver.AppleBacklightInjector"

 

 

 

[snike]

20 hours ago, tluck said:

@snike

 

are you using the CLover ESP bundle as is? trying to figure out what is missing? 

you have a PNLF device

 

what is your LCD?

 

ioreg -l|grep -v Kit|grep Backlight

    | |   | | | +-o AppleBacklightDisplay  <class AppleBacklightDisplay, id 0x10000042b, registered, matched, active, busy 0 (0 ms), retain 8>

    | |   | | |       "IOClass" = "AppleBacklightDisplay"

    | |   | | |       "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0/display0/AppleBacklightDisplay-30e4-2e3"

    | | |   "AppleBacklightAtBoot" = 4882

    | |       "CFBundleIdentifier" = "com.apple.driver.AppleBacklight"

    | |       "IOPersonalityPublisher" = "org.rehabman.driver.AppleBacklightInjector"

 

 

 

I am using the CLOVER ESP. Only change is for the AW123 wireless/bluetooth card I am using. The changes are in the config file. 

 

I tried using RehabMan backlight fix, but that didnt work too.

 

LCD is 1600 X 900

Edited December 8, 2018 by snike
Added LCD info

[skoon432]

Hi all-

 

I'm hoping for some advice. I own an X220 that I originally set up as a dual boot Win 7 and OSX Yosemite 10.10 via Clover bootloader. All had been working fine until dummy here decided to update Clover. The result was that it somehow trashed the OSX side (thankfully Win7 survived). Anyway, the OSX side has been inaccessible since June and I've been afraid to mess with it as I can't afford to hose up the Windows partition.

 

The last Clover upgrade I attempted was 2.4k rev 4586. This is the one that hosed up OS X.  If I force a verbose boot from clover and attempt to boot OSX, here is the result:

 

I hope it can be seen well enough. Apologies for the smaller image as I didn't know how else to grab a shot of the erroneous boot sequence. This is as far as OSX goes before it stalls out and goes no further.

 

Does anyone anywhere have a thought on this, or should I contact the Clover devs for additional support?  I'm well out of my league of understanding things at this point.

 

Thanks-

Steve

 

 

[tasteTheBacon]

Hi @tluck !

 

First off, thank you for all of your work and help.

I’m new here, recently got my hands on a retired T420 from my workplace to play around and geek out with it.

With the help of your ESP bundle I was able to install Mojave 10.14.1 on it and boot it up from the EFI of the SSD.

I use the ESP bundle as is (just renamed the Mojave 1600x000 plist to config.plist) and most of the things work, but unfortunately I have similar issues as @snike has.

My install is missing too the brightness slider in system preferences and also the keyboard shortcuts for brightness aren’t working.

I have a 1600x900 model too, with dedicated Nvidia card (disabled in BIOS).

I’ve installed GFX kext in /S/L/E and updated permissions as advised.

 

The outputs of your previously mentioned commands for me are the following:

$ ioreg -l|grep -v Diag |grep IODisplayPar
    | |   |   |   "IODisplayParameters" = "IOFramebufferParameterHandler is not serializable"
    | |   |   |       "IOMatchCategory" = "IODisplayParameters"
    | |   |   |       "IODisplayParameters" = {"bgsc"={"min"=0,"max"=65536,"value"=65536},"rgsc"={"min"=0,"max"=65536,"value"=65536},"vblm"={"min"=0,"max"=196608,"value"=65536},"ggsc"={"min"=0,"max"=65536,"value"=65536}}
    | |       "IOMatchCategory" = "IODisplayParameters"
    | |       "IODisplayParameters" = {"brightness"={"max"=255,"min"=40},"commit"={"reg"=0}}


$ ioreg -l|grep -v Diag |grep ApplePanel
    | |       "ApplePanels" = {"F10T0366"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>,"F10T159e"=<00110000001c002c003f00510068008a00ab00cc00fa0135018101dd024402c9035903e8>,"F10T02e3"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>,"F10T11ed"=<00110000004f007a00b000e30122017f01db023802b7035a042e052e064c07bc094b0ad8>,"F10T050b"=<00110000001c002c003f00510068008a00ab00cc00fa0135018101dd024402c9035903e8>,"F10T02e2"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>,"F10T213e"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>,"F10T313c"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>,"F10T40e2"=<00110000008c00d80136018f01fe02a3034503e704c70535075a091c0b130d9b10591312>}

$ ioreg -l|grep -v Kit|grep Backlight
    | |       "CFBundleIdentifier" = "com.apple.driver.AppleBacklight"
    | |       "IOPersonalityPublisher" = "org.rehabman.driver.AppleBacklightInjector"

$ ioreg -l|grep PNLF
    | +-o PNLF@0  <class IOACPIPlatformDevice, id 0x10000015b, registered, matched, active, busy 0 (99 ms), retain 9>
    | | |   "device-properties" = {"acpi-device"="IOACPIPlatformDevice is not serializable","acpi-path"="IOACPIPlane:/_SB/PCI0@0/IGPU@20000/PNLF@0"}

Do you might see a pattern here? 
Additionally, my issue seems to be a bit more severe since in system report I can only see 5mb of VRAM for my HD3000 as per the attached image.

Also, it might be related that my install seems to randomly hang at boot from time to time, even with -v verbose mode added.

When it hangs the last message are usually either "IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0," or "IOCTL not recognised : 221 out of 2xx".

Searching around it seems like at least one of these messages is a sign for an issue with integrated graphics and there are numerous tips out there (removing fakeID, patching DSDT.).

 

Since I'm currently stuck any help would be much appreciated. 
If I can help you troubleshoot this in any way please let me know. 

[goodguess]

Your HD3000 kexts are not loaded Bacon, thats why the graphics are reported as 5MB.

I had exactly that output too when starting the Mojave quest.

Be sure to run Kext Utility (again) after installing the HD3000 kexts to S/L/E.

As the system cache files have been refreshed, your setup should work - hopefully.

 

Your screenshots are showing the HD3000 kexts in EFI/EFI/Clover/10.14 if I´m not mistaken.

Is that for backup purposes? 

 

Edited December 12, 2018 by goodguess

[tluck]

this will fix perms on the HD3000 kexts. 

 

list="/System/Library/Extensions/*[SNB,3000]*"
sudo chmod -R go-w ${list}
sudo chown -R root:wheel ${list}
sudo xattr -cr ${list}
sudo kextcache -i /

I am not near my T420 until Sunday to see if having the 10.14 folder in ESP causes a conflict. but they can be removed from ESP once you put them in /S/L/E

 

@skoon432 offhand i dont know why your macOS wont boot after upgrading Clover. do you have the required UEFI Drivers installed? you need these:

AptioMemoryFix-64.efi

FSInject-64.efi

SMCHelper-64.efi

VBoxHfs-64.efi

 

 

[skoon432]

Hi tluck-

 

Are these drivers for a later macOS installation (10.12 or later) or are they meant for ANY Apple installation?  Because I'm still using OSX 10.10 Yosemite. Not one of the later macOS versions. I'll verify what I have from this list you provided and attempt to install them from Clover assuming that's even possible.

 

The thing I can't understand is that Win7 / OSX 10.10 dual boot was working perfectly until I attempted the Clover upgrade. After that, OSX boot was broke and nothing I do seems to fix it.

 

I've been learning to live without it but it sure was a handy thing to use out in the field when I needed it. It has been sorely missed!

[tasteTheBacon]

7 hours ago, tluck said:

this will fix perms on the HD3000 kexts. 

 

list="/System/Library/Extensions/*[SNB,3000]*"
sudo chmod -R go-w ${list}
sudo chown -R root:wheel ${list}
sudo xattr -cr ${list}
sudo kextcache -i /

I am not near my T420 until Sunday to see if having the 10.14 folder in ESP causes a conflict. but they can be removed from ESP once you put them in /S/L/E

 

@skoon432 offhand i dont know why your macOS wont boot after upgrading Clover. do you have the required UEFI Drivers installed? you need these:

AptioMemoryFix-64.efi

FSInject-64.efi

SMCHelper-64.efi

VBoxHfs-64.efi

 

 

Hi. 

 

Thanks for the hint @tluck and @goodguess

I ran these commands and changed nothing else. Even left the ESP untouched. 

Unfortunately now every boot attempt halts at the previously mentioned lines. No matter how many times I try it just hangs. I tried to block the HD3000 and SNB kext from being injected to avoid conflict but it didn’t help. 

Also tried to disable inject intel in clover options but got the same results. 

Its a bit confusing, do you might have any idea why this could happen?

[tluck]

@tasteTheBacon

 

the HD3000 kext set really need to be in the OS (/S/L/E) as they don't seem to work properly from the ESP.  

 

but now you are saying it wont boot into graphics mode at all?

 

you can try to boot up in non-HD3000 by setting the GFX ID in the Clover Options menu. then you go to graphics sub menu to set the product id to 0x12345678 - then it should boot up in basic mode. this way you can remove stuff from the ESP and and validate stuff in /S/L/E 

Edited December 13, 2018 by tluck

[tluck]

@skoon432

if you just updated clover then is strange that your Yosemite install is busted. Do you have a way to revert to the older version?

 

my Guide/github has a recent the bundle of Clover and kexts that I test on Sierra, High Sierra and Mohave (I have no idea if it works with earlier versions)

 

If you can build a USB installer (of say High Sierra) you can install on top of your installed OS - get it running and not lose your data.

 

[tasteTheBacon]

4 hours ago, tluck said:

@tasteTheBacon

 

the HD3000 kext set really need to be in the OS (/S/L/E) as they don't seem to work properly from the ESP.  

 

but now you are saying it wont boot into graphics mode at all?

 

you can try to boot up in non-HD3000 by setting the GFX ID in the Clover Options menu. then you go to graphics sub menu to set the product id to 0x12345678 - then it should boot up in basic mode. this way you can remove stuff from the ESP and and validate stuff in /S/L/E 

 

@tluck

Yes, unfortunately it won’t boot into graphics mode at all now. 

In the meantime I’ve deleted the 10.14 folder from the ESP (ultrabay hdd has windows 10, used it for deletion ). So conflict shouldn’t be an issue in any case now. 

I’ve tried to boot with product id 0x12345678, but sadly it didn’t make any difference. 

I’m pretty confident that the HD3000 and SNB kext is in the right place, even checked permissions with “ls -l” after all the previously ran commands in /S/L/E. 

Tried again with -v, -x, nv disabled, injection of edid , without injecting intel , without injecting any kext and the combinations of all of the above. 

Its all lead to the same result. 

 

Edited December 13, 2018 by tasteTheBacon
Typo