Jump to content

Hervé

Administrators
  • Posts

    9248
  • Joined

  • Last visited

  • Days Won

    462

Community Answers

  1. Hervé's post in Dell E7280: 99% working! was marked as the answer   
    I'm not certain you need to change pipe value or inject flags for your iGPU connectors. Injecting/faking the iGPU's own device id is, of course, of no use. I also believe injecting enable-hdmi20 to be inapplicable on platforms that only support HDMI 1.4...

     
    All I do on my Skylake i7-6600U/HD520 E7270 is inject HDMI type (00080000) to con1 and use boot arg igfxonln=1. I have adjusted DVMT pre-allocated memory through Grub shell-based BIOS data mod. Try that and see if these settings makes a difference. I detailed my observed behaviour with HDMI in my E7270 guides.
     
    I believe all you need to inject is:
    AAPL,ig-platform-id 00001619 DATA AAPL,slot-name Built-in STRING framebuffer-patch-enable 1 NUMBER framebuffer-fbmem 00009000 DATA -> not needed if you change DVMT pre-alloc mem to 96MB through Grubshell framebuffer-stolenmem 00003001 DATA -> not needed if you change DVMT pre-alloc mem to 96MB through Grubshell framebuffer-con1-enable 1 NUMBER framebuffer-con1-type 00080000 DATA  
  2. Hervé's post in Latitude E7440: graphics problem after OC update was marked as the answer   
    Of course, you need to adjust your config; that's the little pleasures every month with every new OC version.
    https://www.insanelymac.com/forum/topic/349151-how-to-opencore-073-074-differences/
    https://www.insanelymac.com/forum/topic/349485-how-to-opencore-074-075-differences/
  3. Hervé's post in Latitude E7440: graphics problem after OC update was marked as the answer   
    Of course, you need to adjust your config; that's the little pleasures every month with every new OC version.
    https://www.insanelymac.com/forum/topic/349151-how-to-opencore-073-074-differences/
    https://www.insanelymac.com/forum/topic/349485-how-to-opencore-074-075-differences/
  4. Hervé's post in [Solved] Optiplex 3050 Sound issue was marked as the answer   
    Your IOReg shows next to nothing under device HDEF so, indeed you have no audio enabled. Assuming there's nothing in BIOS to block this, you should consider implementing the HPET IRQ patch. That should fix your audio issues.
    https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-easy.html#so-what-can-t-ssdttime-do
     
    Did you fix your config conflicts regarding codec layout id? Because the config you posted in port #1 showed:
    codec layout 11 being injected in Device Properties codec layout 3 being injected through NVRAM boot arg
     
    You need to decide on one method or the other, not both and opt for the correct layout of course!
  5. Hervé's post in [Solved] E5470: USB3.0 ports was marked as the answer   
    I'm pretty confident your issue derives from using that single unified SSDT which I believe to be incomplete. I would advise you gradually get rid of this SSDT and return to a more standard set of patched SSDTs. You'll then avoid such issues as that you currently encounter.
     
    When it comes to USB ports power settings, your single SSDT contains the following code and nothing else:
            Device (USBX)         {  [...] Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method             {                 [...] Return (Package (0x08)                 {                     "kUSBSleepPowerSupply",                      0x13EC,                      "kUSBSleepPortCurrentLimit",                      0x0834,                      "kUSBWakePowerSupply",                      0x13EC,                      "kUSBWakePortCurrentLimit",                      0x0834                 })             }  
    E5470 is Skylake, right? On my Skylake E7270, I also inject the attached standard XHC/USB3.0 patched SSDT which defines the following power settings:
                    "AAPL,current-available",                  0x0834,                                          "AAPL,current-extra",                  0x0898,                                          "AAPL,current-extra-in-sleep",                  0x0640,                                          "AAPL,max-port-current-in-sleep",                  0x0834                         
    Try and add that XHC patched SSDT to your setup.
    SSDT_XHC.aml.zip
  6. Hervé's post in [Solved] HP 430 G3: no HDMI audio was marked as the answer   
    All off-topic posts deleted. Guys, I remind that this topic is about HDMI audio...
     
    Looking at the zipped EFI provided above, I can se that the OC config lacks the required, yet well-known, properties injection for HDMI audio: that of the HDMI connector type for the relevant iGPU connector/port (usually con1).
    framebuffer-con1-enable       1        NUMBER framebuffer-con1-type         00080000 DATA If audio is working from the onset, the above will enable HDMI audio. Of course, the exact connector used by HDMI output needs to be verified and adjusted as required (con2, con3).
     
    See the Whatevergreen user manual for details.
  7. Hervé's post in [Solved] E7270: OCS: No schema errors & OC: No vault provided error was marked as the answer   
    Nope, what you get/see is perfectly normal. Mainstream multi-core CPUs have always been reported as single CPUs with n cores, something that totally reflects the hardware. Here's my own i7-based E7270 SysInfo:

     
    In no way does "dual-core/4 threads CPU" mean 2 x processors and 4 cores; you misunderstood things.
  8. Hervé's post in [Solved] E6220: Brightness toggle via Fn keys (UP & DOWN) was marked as the answer   
    Look up my recent Mojave and Catalina updates in my E6220 guide. They offer an installation free of patched DSDT, in UEFI mode and the posted pack contains all the SSDT tables + ACPI renamings in the Clover config to cater for brightness keys. You'll find the necessary code for Fn-UP/Fn-DOWN operation in the SSDT-Q66 table.
  9. Hervé's post in Unable to Update mac os big sur on Dell Latitude E6530 was marked as the answer   
    Updates are not offered when running macOS with the -no_compat_check boot arg. There are 2 x pre-requisites for obtaining Big Sur update offers:
    the SMBIOS of a Mac model compatible/supported by Big Sur (MBP11,x minimum). a SIP value that does not enable Apple Internal; it's disabled by default and must be kept disabled (bit #5 of SIP value, see here for details).
  10. Hervé's post in [Solved] Help with HD 4000 on Big Sur was marked as the answer   
    It's the fbmem patch that prevents the graphics glitches and defects as explained in our HD4000 patching guide; so make sure you implement it. You do not modify/patch memory count, pipe count, port count or stolenmem with LoRes/4-port layout 0x01660003, only with HiRes/1-port layout 0x01660004.
     
    Therefore, your framebuffer patch for [email protected] should set the following parameters to the following values:
    ig-platform-id -> 03006601 // LoRes/4-port Capri mobile layout framebuffer-patch-enable -> 1 // enables framebuffer patching framebuffer-fbmem -> 00008000 // reduces framebuffer memory from default 16MB to 8MB framebuffer-conX-enable -> 1   // enables conX patching, where X is your identified connector for HDMI output port framebuffer-conX-type -> 00080000 // sets conX to HDMI type, where X is your identified connector for HDMI output port hda-gfx -> onboard-1 // for HDMI-audio and nothing else. Target connector will most probably be con1.
     
    In the future, please post system's specs (add those in signature!) and copy of your bootloader config so that it can be properly read with the relevant tools, rather then leave people use Base64 to Hex/Text converter to decode your patches... Here, we assessed it was a Clover config but also specify this sort of things.
     
    For a complete and detailed set of information on framebuffer patching, I invite you to consult the Whatevergreen user manual:
    https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md
  11. Hervé's post in [Solved] Latitude 7400: no success with OpenCore was marked as the answer   
    You appear to have a Micron 2200s SSD in that Latitude 7400. Those are known to be troublesome with macOS and you should consider replacing it.
    https://dortania.github.io/Anti-Hackintosh-Buyers-Guide/Storage.html
  12. Hervé's post in [Solved] D620 OS X 10.7.5 Pointing Stick Support? was marked as the answer   
    The track stick is actually supported with the ApplePS2Controller kext provided in the D620 bootpacks once you remove the VoodooPS2Trackpad PlugIn kext.
×
×
  • Create New...