Jump to content
About Just Joined group Read more... ×
K0gen

Lenovo ThinkPad T420 with UEFI Only

5,179 posts in this topic

Recommended Posts

On 10/24/2018 at 4:19 AM, tluck said:

@davidian - I successfully tested the HD3000 kexts from Sierra and High Sierra with Mojave, but i recall a failure with the el cap gfx kexts. 

High Sierra is the last properly supported version for aHD 3000 system like the T420

 

 

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?

Edited by Lucratskill

Share this post


Link to post
Share on other sites
Advertisement
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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

@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 by tluck

Share this post


Link to post
Share on other sites
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"}

Share this post


Link to post
Share on other sites

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

 

MACAudio.jpg

MACAudio2.jpg

BDMESG.txt

Edited by downlord
TYPO

Share this post


Link to post
Share on other sites

Update:

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

Strange behaviour.

MACAudio3.jpg

Share this post


Link to post
Share on other sites

@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>

 

Share this post


Link to post
Share on other sites

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 by MikeDece
it was not fixed

Share this post


Link to post
Share on other sites

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 by MikeDece
i came up with an idea

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

@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?

Share this post


Link to post
Share on other sites
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?

Share this post


Link to post
Share on other sites
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.

 

Share this post


Link to post
Share on other sites

@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"

 

 

 

Share this post


Link to post
Share on other sites
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 by snike
Added LCD info

Share this post


Link to post
Share on other sites

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

 

 

IMG_1391.jpg

Share this post


Link to post
Share on other sites

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. 

Screenshot 2018-12-12 at 0.36.12.png

Screenshot 2018-12-12 at 0.51.18.png

Screenshot 2018-12-12 at 1.02.27.png

Screenshot 2018-12-12 at 1.04.14.png

Share this post


Link to post
Share on other sites

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 by goodguess

Share this post


Link to post
Share on other sites

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

 

 

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites
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?

ADD3C510-5523-44E2-824C-4958274C3DAA.jpeg

A374F65F-944F-4570-B35C-51AB20F74FA9.jpeg

Share this post


Link to post
Share on other sites

@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 by tluck

Share this post


Link to post
Share on other sites

@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.

 

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By y010204025
      Update: On October 24, 2020, using clover to solve the macOS11 beta10 boot problem, you can now enjoy macOS11beta10, and the compatibility of subsequent versions is not guaranteed.
      HIDPI uses a modified version. You can directly execute the hidpi script to get a better experience. If you lose the repair, it is not within the scope of my support.
      Support upgrades without destroying the integrity of the original image.
      There seems to be a problem with the shortcut keys. If you can help solve it, thank you for your contribution.
       
      Perhaps it was the first NEC (Lenovo) Lavie Z HZ550 to install hackintosh. I hope more people who like Lavie Z series can experience Hackintosh at HZ550. She is really great.
       
      I found HZ550 & HZ750 on the Chinese website, which is amazing. It weighs only 790g, 13.3 inches, and the standard 2k screen, which is too attractive to me. I am a Hackintosh enthusiast. I think HZ550 or HZ750 with MacOS is the best Unfortunately, the Lavie Z series is not listed in China, only exists in the Japanese and American markets, and in the Japanese market is the NEC brand, while the American market uses the Lenovo logo.
       
      Fortunately, I got an HZ550 from Taobao. Yes, not HZ750. In comparison, HZ750 has more touch screens and 360 ° flip. These are hard to attract me. More importantly, HZ750 is about 200g heavier than HZ550 That's why I chose HZ550. Well, because he is only 2,000 RMB.
       
      The specific introduction can refer to NEC Japan official website:http://nec-lavie.jp/products/hz13b/
       
      The HZ550 hardware list I obtained:
                                    
                       -/+:.          ningnan@ningnandeMacBook-Air
                      :++++.          OS: 64bit Mac OS X 10.15.5 19F96
                     /+++/.           Kernel: x86_64 Darwin 19.5.0
             .:-::- .+/:-``.::-       Uptime: 19m
          .:/++++++/::::/++++++/:`    Packages: 1
        .:///////////////////////:`   Shell: zsh 5.7.1
        ////////////////////////`     Resolution: 3840x2160
       -+++++++++++++++++++++++`      DE: Aqua
       /++++++++++++++++++++++/       WM: Quartz Compositor
       /sssssssssssssssssssssss.      WM Theme: Blue (Dark)
       :ssssssssssssssssssssssss-     Disk: 11G / 108G (12%)
        osssssssssssssssssssssssso/`  CPU: Intel Core i7-5500U @ 2.40GHz
        `syyyyyyyyyyyyyyyyyyyyyyyy+`  GPU: Intel Iris Graphics 6100
         `ossssssssssssssssssssss/    RAM: 4376MiB / 8192MiB
           :ooooooooooooooooooo+.    
            `:+oo+/:-..-:/+o+/-     
       
       
      Advantages: small size, light weight, 2K screen, 8G memory, 512g SSD, keyboard feels good, and wireless network card can be replaced, which is unimaginable in today's thin and light books.
      Disadvantages: The sound is small, almost the same as the mosquitoes.
       
      Ok, bragging is over!
      In order to use the wireless network, I changed the wireless network card from inter 7265 to BCM94352ZAE. Some people called it DW1560. It is uncomfortable that in China, this card and his elder brother DW1830 were hyped to a high price of 480RMB. of. Fortunately, I bought it early, and this card is also very stable under win10, and there is no high delay and outage. The hard disk should be PM951 of Samsung, not PM981, which is lucky.   Before installing Hackintosh: You need to prepare a 16G U disk, SanDisk is not a rough choice for making MacOS installation disk, I used the latest MacOS Catalina 10.15.5, got config.plist from Rehabman, and put together an EFI, the latest version of clover and kext drivers. Thanks to Rehabman and the developers of the Black Apple community. I do n’t like that OC team very much.
      Make an installation disk: If you have a computer running MacOS, you can use the command line to make it, if you do n’t have a computer running MacOS, you can try VMware, I know that the insanelymac forum allows discussion, or use ether to write the image to U disk, use the EFI I provided to boot into the installation process.   BIOS setting: Press F12 at boot to enter the BIOS settings, Tab switches to "Security-Secure boot", set to "DISable", this is what we need, and switch to "Boot -Boot devices", set the U disk as the first boot item You can directly enter the clover guide interface, please follow it for google it.
      It is worth noting that the remaining space of your EFI partition needs to be greater than 200M, otherwise, the disk format will be wrong. In addition, the format partition format is APFS, do not choose to encrypt, your data is not valuable, at least you must have this awareness of Hackintosh, the file safe is also the same, do not enable, do not use to find your mac, otherwise, change the machine, OK .   Fortunately, no additional ssdt patch is required. All the patch functions are implemented through clover. The flat Apple is turned on. This is to solve the problem of the flower screen. You can find a solution yourself.
      Experience your black apple, this will bring a better experience than MacBook Pro.  
       
    • By Del
      I have been trying to get my Lenovo G570 i5 2430M with HD3000 (id: 116) to work for almost 2 months. Mountain Lion works flawlessly but Mavericks onwards, display stays off with the exact same setup (Chameleon: Extra folder with smbios mbp8,1 included in attachment)
       
      I'm able to boot and see the screen with remote desktop but internal display stays off.
       
      found an old post which fixed issue for few users
       
      I understand HD3000 is natively supported till High Sierra, which is why I'm totally baffled and out of ideas to proceed with.
       
      Any help is greatly appreciated
      Thanks
       
      @jl4c
      Alex.zip
    • By MaLd0n
      -OpenCore Vanilla TUTORIAL-
       
       
      -USB Port Mapping TUTORIAL-
       
        1 -Create a USB bootable
       
      Create your usb installer, use this tool and download Catalina or Big Sur from Apple servers
       
      Catalina
      installScript_allfullapp.zip
       
      Big Sur
      installScript_1016fullapp.zip
       
      Credits: crazybirdy
       
      Copy Catalina / Big Sur installer to Applications folder, open terminal and run
       
      Catalina
       
       
      Big Sur
       
       
      If you want check one step by step, check here
       
      -Opencore Vanilla Tutorial
      https://tinyurl.com/ycvcnp8h
       
      2- EFI folder USB installation
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/yxsw7d3t
       
      3- EFI folder SSD
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD 
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD
      https://tinyurl.com/yxsw7d3t
       
      4- Start Fine Tune
       
      Run this app and post full dump here for full ACPI solution
       
      RunMe.app
      https://tinyurl.com/y9562hz7
       
       
      If you like a SSDT way, here we go
      SSDT-OLARILA.aml.zip
       
      5- USB Solution
      USB INTEL SERIE 400.zip
       
      Use these kexts, enable XHCI port limit patch and follow this tutorial for remap USB ports
       
       
       
      --DSDT PATCHES--
       
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE ID -DMAC -REMOVE LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM -REAL TIME CLOCK -SLPB -DARWIN / WINDOWS -XHCI -PLUGIN TYPE -HDEF -ARTC -IPIC -TIMR -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -kUSBCompanionIndex -io-device-location -IMEI -EC -PNLF -ARPT -GFX0 -NVME -ACPI-WAKE-GPE -DTGP -HDMI / HDAU  
      --SCREENSHOTS--































      -If you want to buy me a beer - Donations with PayPal
      https://tinyurl.com/r2bvzm7
       
      Big Thanks to XLR and your Badass Motherboard, Ultrafast CPU, Coolest Heatsink, Huge Graphics Card, Tonnes of RAM,
      Gigantic Hard Drive, Lightspeed Disk Burner, Professional Sound Card, Massive LCD Display.
       
       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!

      We're all here to have fun and learn from each other!
    • By qmgoqwe
      I have installed MacOS and Windows on the following hardware:
       
      AMD Ryzen 7 3700X MSI B450M Mortar Max Sapphire Radeon Pulse RX 5600 XT 6G Samsung 860 QVO, 1 TB SSD (PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x1)/Sata(0x5,0xFFFF,0x0)) - MacOS on this disk Kingston A2000 SSD 1TB M.2 2280 NVMe (PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,15-AD-CD-26-28-B7-26-00)) - Windows on this disk  
      OpenCore 0.6.1 MacOS 10.15.7 both disks GPT UEFI  
      Both OSs boot nicely and work as a charm when selecting either of the disks as boot disks in the BIOS.
       
      However, trying to boot Windows 10 from the Opencore Bootmanager (no matter whether PickerMode=internal or OpenCanopy) causes a Windows Blue Screen ("SYSTEM THREAD EXCEPTION NOT HANDLED").
      To be on the safe side, I have added an appropriate entry to Misc->Entries:
      <key>Arguments</key> <string></string> <key>Auxiliary</key> <false/> <key>Comment</key> <string>Not signed for security reasons</string> <key>Enabled</key> <true/> <key>Name</key> <string>Windows 10</string> <key>Path</key> <string>PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,15-AD-CD-26-28-B7-26-00)/HD(1,GPT,2E9695CB-0F9A-4005-AADB-2FF9C96AD02C,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi</string> It points to the Windows 10 bootmanager on the Windows disk's EFI partition.
       
      What's wrong with that? Why does this cause a BSOD? It is not clear to me why it works when booting from BIOS but not here.
       
      config.plist attached (but maybe it has no relevance for the problem).
      config.plist
×