Jump to content

Hervé

Administrators
 View Profile  See their activity

  • Posts

    10027

  • Joined

  • Last visited

  • Days Won

    561

 Content Type 

Everything posted by Hervé

  1. Hervé
    I very much doubt it's a matter of Azul framebuffer patch...
  2. Hervé
    I've had that before on my E6230. Turns out I was using the wrong CPU power management SSDT after I changed my motherboard and went from an i5 to an i7 CPU. Once I generated the correct SSDT, all worked well again. Check that out or regenerate your SSDT. If you're not using one, check out your Clover power management settings. That's where it'll be.
  3. Hervé
    LVDS has supported high resolution displays for years. Dell fitted HiRes WUXGA 1920x1200 LCD panels to some of their 15" laptops as far as 15 years ago (eg: old Inspiron 8500/8600/6000) and all those used an LVDS interface.
  4. Hervé
    Ouh, those Clover configs would require serious revisiting!
  5. Hervé
    You're probably not using the correct compiler settings... Here goes (GPU id + layout id injection removed): DSDT.aml.zip As for the connector type, you're on the wrong path. Changing a connector-type in the framebuffer type ain't going to change the physical LCD connector, is it? Anyway, the thread is about Ivy Bridge HD4000 and our rules do not allow posting links to TMX...
  6. Hervé
    That won't be of any help. Try the following: Remove the id faking + layout id injection from your DSDT Make sure you do not activate "Inject Intel" or any graphics layout id in your Clover config Reinstall latest whatevergreen kext (latest WEG apparently requires no injection at all)
  7. Hervé
    I only checked the last one you posted, i.e. the debug one...
  8. Hervé
    macIASL but you do not need to make any edits to your DSDT; it's perfectly fine as it stands.
  9. Hervé
    A few comments: your DSDT injects correct desktop HD4600 id 0x0412 + correct layout id 0x0a260006; as such, it's not required to do so in Clover; you can simply tick "Inject Intel" only you're injecting Rehabman's FakePCIID kexts alongside lilu + whatevergreen; that could clash Try and remove the following kexts: AppleBacklightFixup + lilu + whatevergreen. Normally, with: desktop HD4600 id 0x0412 + layout 0xa260006 injected in DSDT "Inject Intel" ticked in Clover FakePCIID + FakePCIID_Intel_HD_Graphics kexts injected through Clover you should be getting full graphics acceleration on your HD4400 You may also need to revise your Clover config on the following fronts: ACPI tab: activate "Fix Headers" remove dropping of SSDT tables "CpuPM" + "Cpu0Ist" activate "APSN" + "APLF" Boot tab: remove "-xcpm" Kernel & Kext patches: activate "KernelXCPM" System parameters: set "Inject Kexts" to Yes
  10. Hervé
    Unlike High Sierra, Mojave converts partitions to APFS without offering or supporting any facility not to do so. If you want to run Mojave on HFS+, you have to apply patches to your installer. You could try Dosdude1's patcher for instance.
  11. Hervé
    Distros are best avoided. This being said, if Niresh Mavericks is booting with Chameleon -and I believe it does by default-, you won't be able to boot Mojave which requires Clover at this point of time (or Enoch if you know how to set it up). But you cannot possibly "brick" your E7240, no. At worst, you'll break your boot loader, that's it. You'd be better off by: taking a backup/clone of your Mavericks current installation installing Mojave on a 2nd partition install clover in the EFI Normally, Clover should be able to boot Mavericks but since there are significant changes between the 2 x OS and their respective ACPI patching/Clover setup, you may encounter trouble. Question is: why do you want to keep running Mavericks 10.9. It's 5 years behind and obsolete these days. If you're adamant on keeping Mavericks, you could always use your Mojave USB installer to boot Mojave on a 2nd partition of your disk.
  12. Hervé
    You can simply move your wireless card to those other 2 x slots to test. It could be interesting to compare the E6230's DSDT with the D630's because on the latter, the switch performs as expected OOB in all OS X/macOS versions.
  13. Hervé
    Try with this DSDT: DSDT.aml.zip where I've changed the PinConfigurations part of your HDEF device from this: "PinConfigurations", Buffer (0x04) {} to this: "PinConfigurations", Buffer (Zero) {} If you still get no joy with AppleALC, try to: remove AppleALC replace the vanilla AppleHDA in /S/L/E by the patched copy below install the dummy IDT90HD92 kext below in /L/E repair permissions to /S/L/E + /L/E rebuild your cache AppleHDA.kext.zip AppleHDA_IDT90HD92.kext.zip
  14. Hervé
    Maybe I misunderstood your thread but this is essentially a soft switch, equivalent to what the little physical switch on the right side of the laptop does, right? Granted that your soft switch lits the Wifi LED when a BT device is paired with the laptop's internal DW380. The side switch basically controls power to the WLAN mini-PCIe slot + internal bluetooth. Does your soft switch control power of a card fitted to one of the other 2 x expansion slots?
  15. Hervé
  16. Hervé
    I would suggest that, in your Clover config, you revert to MacBookPRo8,1 SMBIOS and adjust your SIP (CSRActive) + Booter config parameters.
  17. Hervé
    I have a Latitude E6440 and CPU SpeedStep/power management is running fine under OS X/macOS with the generated CPU power management SSDT. I've never nor experienced any CPU speed limitation due to a power adapter and I do not believe there would be one (I use a cigarette lighter-to-Dell adapter in my car w/o issues). SpeedStep should be enabled/ON in BIOS as well as all CPU cores. In OS X/macOS, make sure you do not use the Turbo disabler kext when on battery. My E6440 with i5-4300M @2.6GHz throttles as expected between 800MHz when idle to 3.3GHz Turbo boost, granted that all intermediary frequencies between LFM and HFM cannot be achieved, only very few. As for behaviour under Windows, well this is a Hackintosh forum, so....
  18. Hervé
    It's been mentioned before...
  19. Hervé
    In all likelyhood, your DSDT needs patching to support USB3. Check if and where you define OSYS according to "Darwin" OS detection, if at all. You need something like this. Best thing to do is what JaleLo suggested: post a zipped copy of your Clover folder (without the Themes subfolder). Or better, follow this.
  20. Hervé
    High Sierra's HD3000/SNB graphics kexts can be used too with the same minor graphics defects that anyone will experience of those unsupported non-Metal platforms.
  21. Hervé
    PRO2X in v1 (USB2) or v2 (USB3) versions are supported and you can get dual display off it as detailed in the suggested thread. Dual DVI, dual DP, DVI + HDMI, DP + HDMI, DVI + DP should all be supported as long as you patch your Azul framebuffer kext accordingly, knowing that you can only have a maximum of 2 x external displays on top of the built-in LCD.
  22. Hervé
    If you want to install Mojave on the E6220, you have to apply specific non-vanilla adjustments as detailed here. As Bronx said, Mojave dropped support for HD3000 graphics so you'll have to install SNB/HD3000 graphics kexts from, say, High Sierra 10.13.6 and accept some minor graphics defects. MBP8,1 SMBIOS won't support Mojave installation so you'd need to use a different and supported SMBIOS to kick off the installation process. You may then patch the SupportedPlatform plist to revert to MBP8,1. Alternatively, the -no_compat_check boot option should normally do. As for Clover EFI, you can re-use the same as for Sierra or High Sierra; simply update the add-on kexts as/if necessary so that they support Mojave (eg: lilu, AppleALC, etc.). You'll need a Mojave-compatible Clover version so use the latest available version.
  23. Hervé
    Unless you have a DSDT that was repatched off BIOS A22, expect to experience garbled graphics on screen. To avoid this, maximum BIOS version is A12. To revert to that BIOS version, 1st downgrade to tjhe lowest possible version available on Dell's web site, then upgrade to A12. You'll find full installation details in this guide: The HD4000 Capri layout to use depends on your built-in LCD resolution. Inject layout-id 0x01660004 for resolution GTE 1600x900, otherwise use 0x01660003 for lower resolutions such as 1366x768. All your USB ports will workj as long as you: 1) rename EHCx devices to EH0x 2) inject/install a USB injector kext (Rehabman's USBInjectAll highly recommended) 3) use the appropriate SMBIOS (MBP9,x)
  24. Hervé
    Core2Duo CPU is not an issue in itself as long as it's a Penryn model. The issues at hand are: SMBIOS profiles such as MBP7,1 (anything older than a 2012 model is natively unsupported) Vanilla telemetry plugin triggers KP on C2D platforms GPU support (no native support for non-Metal GPUs) Dosdude1's patcher normally takes car of this: it patched the PlatformSupport plist to inject some of those natively unsupported models (eg: MBP7,1, MBP8,x, etc.) it replace the telemetry plugin by a previous version from High Sierra As for GPU support, older nVidia GPUs can be supported by installing nVidia kexts from a previous macOS version such as High Sierra 10.13.6 See details re: D630 in my Mojave beta thread here.
  25. Hervé
    Look at the HD4600 guide available in R&D->Graphics forum sub-section
×
×
  • Create New...