Jump to content

nijhawank

Just Joined
  • Content Count

    62
  • Joined

  • Last visited

About nijhawank

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

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

  1. nijhawank

    [GUIDE] Lenovo T460 macOS with Clover

    Hi @tluck I also came across https://github.com/acidanthera/CPUFriend and it seems to be the newer way to do what you did via X86PlatformPluginInjector. However, I didn't understand the instructions. Anybody using it? It's also supposedly to be used together with LiluFriend
  2. nijhawank

    [GUIDE] Lenovo T460 macOS with Clover

    Thanks @tluck Do you think that there are duplicate CpuSsdt one from the OEM and one from your DSDT.T460 pack? Look at the first screenshot in my post above.
  3. nijhawank

    [GUIDE] Lenovo T460 macOS with Clover

    Hi @tluck Please see my above message. Yesterday the x86platformplugin was not loaded. However today when I checked, x86platformplugin is loaded. Then when I checked the available SSDTs from MaciASL, I see that there were two entries for CpuSsdt. One is the OEM version and other one is from your DSDT.T460 package. See the screenshot below. Could that be the reason for the random behavior for x86platformplugin. I see that DropOem=false in your config.plist. If this is the problem, how can I remove only this CpuSsdt? Nope. I'm confused. I see this in System Report which suggests that X86PlatformPlugin is not loaded. But then IORegistryViewer Shows X86PlatformPlugin properly attached to CPU0. What is correct?
  4. nijhawank

    [GUIDE] Lenovo T460 macOS with Clover

    I am using the v2019.1.24 release for my Lenovo T460 and everything is working. However, when I saw the kexts loaded, X86PlatformPlugin doesn't seem to be loaded but ACPI_SMC_PlatformPlugin. The laptop is otherwise running smooth. Is this the correct behavior or something is missing. I did generate and using my own DSDTs using the included DSDT.T460 package.
  5. nijhawank

    WhatEverGreen Support Topic

    I updated the IOProbeScore to 5500 in IntelBacklight and updated to WEG v1.2.6. Rebuilt kextcache and added applbkl=0 to boot Params. Rebooted and macos never reached the login screen. So guess IOProbeScore=5500 trick is only for custom AppleBacklightInjector and doesn't work with IntelBacklight and WEG consonants.
  6. nijhawank

    [GUIDE] 1st Generation Intel HD Graphics QE/CI

    @Badruzeus I fixed the annoying second stage boot graphics glitch. The problem was that I was using Intel->Inject=True but without that it couldn't load the frame buffer. So I had it always enabled. I re-read the 1st post in this thread, and in the troubleshooting section, it said if it stucks at spinning wheel and desktop never loads, you will need to inject certain properties in the DSDT. I had never tried this earlier, because for me it was working with Intel->Inject=True. So I tried disabling it and I injected the following _DSM method to my IGPU device (and renamed the original one to XDSM) and voila it worked. No more that annoying flickr. Thank you for being so patient with all my never ending questions and hats off to all the amazing people who have made all of this possible. + Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method + { + Store (Package () + { + "AAPL,os-info", + Buffer () + { + 0x30, 0x49, 0x01, 0x11, + 0x01, 0x10, 0x08, 0x00, + 0x00, 0x01, 0x00, 0x00, + 0x00, 0x00, 0x00, 0x00, + 0xFF, 0xFF, 0xFF, 0xFF + }, + + "VRAM,totalsize", + Buffer () + { + 0x00, 0x00, 0x00, 0x12 + }, + + "model", + Buffer () + { + "Intel HD Graphics" + } + + }, Local0) + DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) + Return (Local0) + } +
  7. nijhawank

    Purpose of AptioMemoryFix

    Thank you. Now I understand how the emulated nvram was working even when I had NO EmuVariableUefi in the drivers64 folder.
  8. nijhawank

    WhatEverGreen Support Topic

    I thought that ioprobescore is for specifically setting in custom backlight injector but I will try adding it for intelbacklight and state my results.
  9. nijhawank

    WhatEverGreen Support Topic

    Thanks @Badruzeus Somehow I'm not able to get rid of that second stage graphics glitch. I tried your suggested KTP, statically pre-patched IOGraphicsFamily kext and WEG v1.2.4 (of course one by one and only one method at a time) is there any specific section that you put in your config.plist for WEG? I'm asking this because any thread for WEG only talks about Intel 2nd Generation and above and how to enable Framebuffer patching by adding the properties section. Can you share your EFI folder or config.plist for your 1st Gen Graphics laptop.
  10. nijhawank

    WhatEverGreen Support Topic

    So that's exactly was my question. Is there any use of WEG for Intel 1st Gen Graphics? And you are saying "No". So any protected video playback fixes (inherited from Shiki) or fixing second stage boot glitch etc. are not applicable or not performed by WEG when using Intel 1st Gen Graphics. Is that a correct statement?
  11. nijhawank

    WhatEverGreen Support Topic

    I already said that I must use intelbacklight or acpibacklight because my machine doesn't expose IGPU PWM registers. Also I already followed the guide for Intel 1st Gen Graphics device and using pre-patched framebuffers from High-Sierra. So in this condition i want to ask is there any other reason for using WEG? And if yes, my concern is that latest WEG breaks Intel/Acpi backlight kexts even when using applbkl=0 or even -wegoff
  12. nijhawank

    WhatEverGreen Support Topic

    WhateverGreen versions higher than v.1.2.4 that have the Backlight Brightness changes breaks using IntelBacklight or ACPIBacklight. Some of us must use these older kexts (along with Bergdesign's Brightness app) for enabling brightness because our hardware do not expose IGPU PWM registers. I tried using applbkl=0 and also -wegoff but it doesn't help. I must remove WEG for my brightness to work. Can we fix that? Also, for some of us who have Arrandale Intel 1st Gen Graphics, and use the KextsToPatch or statically pre-patched AppleIntelHDGraphics* kexts from High-Sierra or earlier, is there any use of WhateverGreen. If yes, what is the corresponding config.plist section we need to add for WEG. I'm asking this because per the thread https://www.insanelymac.com/forum/topic/334899-intel-framebuffer-patching-using-whatevergreen/ I don't understand what should I add for Intel 1st Gen.
  13. nijhawank

    Purpose of AptioMemoryFix

    I tried a lot but couldn't get proper answer for the function of AptioMemoryFix (and older OsxAptio*) drivers. From the name of it or the most straight results tell me that its to fix memory allocation problems for APTIO boards and in the process enable native nvram. However, I also see it being used on laptops such as Lenovo T420, T460 which I guess don't use APTIO, or do they? Basically, I have a Lenovo T410 and I currently use EmuVariableUefi for emulating nvram but no version of AptioMemoryFix or any of its older friends. My system is overall stable. So my questions are... Is AptioMemoryFix should be used generally or strictly on motherboards with Aptio UEFIs or other UEFI firmwares. The T410 does NOT have UEFI support only older BIOS. Does any version of AptioMemoryFix or older friend is useful for me? Does my T410 has native nvram. I have tried the simple test of command line setting nvram testvar=hello and checking it across reboot, and it doesn't work. Thanks in advance.
  14. nijhawank

    [GUIDE] 1st Generation Intel HD Graphics QE/CI

    I also use BergDesign's Brightness app along with either of IntelBacklight or ACPIBacklight. Both works, but I see that when using IntelBacklight, the brightness always get sets to minimum on reboot. I use EmuVariableUefi and the problem is not with ACPIBacklight. Do you face the same problem with IntelBacklight?
×