Jump to content

tasteTheBacon

Just Joined
  • Content Count

    5
  • Joined

  • Last visited

About tasteTheBacon

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. tasteTheBacon

    Lenovo ThinkPad T420 with UEFI Only

    So this is what I've done : When I created the USB installer for Mojave I've renamed the Mojave 1600x900 config plist to config.plist in the USB EFI / Clover folder. My intention was to convert it to become the default config that clover selects. While installing MacOS from the USB this setup worked. Once MacOS finished install to the SSD I've copied everything from the USB EFI to the SSD EFI. When I tried to boot from the SSD it failed as detailed in previous comments. Clover properly highlighted my config.plist (which was originally the 1600x900 Mojave config) as the selected one, despite this I had to manually select a different config and re-select the default one to make a successful boot attempt. I suspect that if I delete all other config.plist it will boot just fine and this is a Clover bug, but I didn't have the time to check this yet.
  2. tasteTheBacon

    Lenovo ThinkPad T420 with UEFI Only

    To be pro-active: I've tried everything, even reset my bios settings, deleted and re-copied everything to the SSD ESP. None of these helped. But fortunately, I figured it out, sort of. The solution for me was to go in to the Clover Options menu while booting up and manually select a different config.plist and then re-select the default one (Which was highlighted by default). Without this manual step the boot hangs. With it it boots fine. I've even got the HD3000 kext loaded and brightness working with this step. If you ask me it doesn't make any sense to me. Can this be a Clover bug? Not sure if you have any tip on how to skip this manual step, but either way, thank you for the support @tluck , and also @goodguess for the tip. It's all highly appreciated.
  3. tasteTheBacon

    Lenovo ThinkPad T420 with UEFI Only

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

    Lenovo ThinkPad T420 with UEFI Only

    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?
  5. tasteTheBacon

    Lenovo ThinkPad T420 with UEFI Only

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