Jump to content

Hervé

Administrators
 View Profile  See their activity

  • Posts

    10040

  • Joined

  • Last visited

  • Days Won

    563

 Content Type 

Everything posted by Hervé

  1. Hervé
    Seems issues are linked to: 1) EFI BIOS settings (point to USB key + internal SSD whilst OP boots off a USB HDD) 2) NVRAM plist files placed in EFI folder The NVRAM file seems to be the main cause as it clearly overwrote SMC keys + SMBIOS parameters defined in the Clover config file.
  2. Hervé
    Once again... Read the FAQ section. https://osxlatitude.com/index.php?/forum/161-faqs-tutorials/
  3. Hervé
    FakePCIID_Intel_HD_Graphics.kext useless without Fake_PCIID.kext... Just like VoodooHDA without AppleHDADisabler.
  4. Hervé
    You can build a USB installer on a key formatted with an MBR partition scheme, yes.
  5. Hervé
  6. Hervé
    https://sourceforge.net/projects/hwsensors/files/
  7. Hervé
    There must be some rogue trace of an older VoodooPS2Controller v1.8.21 somewhere. Remove DrHurt's VoodooPS2controller v4.0.0 from Clover EFI folder and put it in /L/E. Then repair permissions and rebuild your cache. I'm not aware of anything the sort but you wouldn't have anything linked to an older VoodooPS2Controller in your PrefPanes, would you? If you can't get rid of the KP, all I can suggest is a fresh re-installation...
  8. Hervé
    So you're still getting KPs on VoodooPS2Controller? Give the attached version a try (uploaded from my E6230 on which it works perfectly). It's Dr Hurt's R4. VoodooPS2Controller.kext.zip
  9. Hervé
    You've kept KernelBooter_kexts set to Yes, consequently you can only boot without cache (i.e; with -f flag) and with add-on kexts in /E/E. Copy (not move) your add-on kexts to /L/E, repair permissions, rebuild your cache, set KernelBooter_kexts to No and you'll be able to boot normally. You're using MBP7,1 SMBIOS which is Ok but it seems you simply copied the plist from some place and did not update it to remove/replace the CPU and RAM speeds manually set there. Remove these or adjust according to your M6400.
  10. Hervé
    The USB device renaming applies to USB2.0 ports. In case you ignored this, please note that: UHCI refers to USB1.x controllers EHCI refers to USB2.0 controllers XHCI refers to USB3.0 controllers https://en.wikipedia.org/wiki/Host_controller_interface_(USB,_Firewire)
  11. Hervé
    Afaik, there is no ready-made bootpack here for this machine, so do as usual: list your hardware specs and look for eventual support & drivers. You have a 2nd gen Sandy Bridge system so you'll have to apply the AppleIntelCPUManagement kext patch to avoid KP. Graphics will depend on HD3000 iGPU or discrete GPU. If HD3000 iGPU, graphics acceleration will be obtained by simple injection of the SNB laptop layout. These are the 2 x priority items. For the rest (audio, LAN, wifi, etc), we'll see as you post your specs.
  12. Hervé
    Difficult to say with so little info. Try it.
  13. Hervé
    55C to 60C-ish is perfectly normal if CPU runs at Turbo boost speeds. Expect it to idle around/just under 50C. Don't expect 45C or even lower...
  14. Hervé
    OP should go for latest Sierra version, regardless...
  15. Hervé
    You need to activate AICPUPM aka AsusAICPUPM aka AppleIntelCPUPowerManagement patch on Sandy Bridge and Ivy Bridge platforms. User Clover Configurator app to tune your Clover config.
  16. Hervé
    https://osxlatitude.com/index.php?/topic/9961-how-do-i-repair-permissions-and-rebuild-the-cache-yosemite-and-later/
  17. Hervé
    Or it could simply be a duff physical connection at one cable end...
  18. Hervé
    Further to fresh experiments with VRAM allocation, I can confirm that the 8th byte of the 2nd line of Azul framebuffers/layouts as displayed above (in 8 groups of 4 bytes per line) is for VRAM allocation and can be set as follows: 40 -> 1024MB 60 -> 1536MB 80 -> 2048MB In my case, changing the Azul FB #12/layout 0x0a260006 from this: 0600 260A 0103 0303 0000 0002 0000 3001 0000 6000 0000 0060 D90A 0000 D90A 0000 to this: 0600 260A 0103 0303 0000 0002 0000 3001 0000 6000 0000 0080 D90A 0000 D90A 0000 increased VRAM from 1536MB to 2048MB.
  19. Hervé
    Please read the FAQ section... https://osxlatitude.com/index.php?/topic/8696-is-my-wireless-card-compatible-with-os-x/
  20. Hervé
    if you need/want to regulate audio volume with VoodooHDA, you can try and play with values such as iGain in the kext's plist. It's a long time since I've played with VoodooHDA but the VoodooHDA PrefPane (if you install it) allows you to adjust these too.
  21. Hervé
    You don't need to quote every message you directly reply to... In all likelyhood, it's a USB issue. Try to unplug and replug the key with the macOS installer. But I would recommend you only use 1 key, not 2. You may also try this revised DSDT where the device-id injection was removed from USB devices + iGPU. DSDT.aml.zip
  22. Hervé
    AR9285 needs a DSDT or Atheros40 kext patch to be fully supported but would not be expected to block startup. https://osxlatitude.com/index.php?/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/
  23. Hervé
    M6400 is same family as M2400 & M4400, just larger (17"). All have Penryn CPUs at FSB 1066MHz + nVidIa GPUs. M6400 have either Quadro FX 2700M or FX 3700M. M2400 have nVidia FX 770M and that's supported under OS X (don't know about Sierra though). M4400 have nVidia FX770M or FX 1700M which is also supported afaik. All those dGPUs are based on nVidia G9x architecture and should therefore all be supported: https://www.notebookcheck.net/NVIDIA-Quadro-FX-770M.11707.0.html Since what you actually seek is most probably a step-by-step guide, look up existing M2400 and/or M4400 threads if you can't find anything for the M6400. But the only way to know for sure if Sierra will run on your M6400 is to try, so roll-up your sleeves and jump ! No reason why it wouldn't work. Your signature shows you had a M2400 with El Capitan before, so should already be in familiar territory... I posted a Mavericks/Yosemite bootpack for the M4400 at the top of this very section earlier this year; use that as a base to build-up from. As stated at bottom of the thread, you'll obviously have to apply those DSDT patches mandatory for USB ports since El Capitan .
  24. Hervé
    lTunix, no double/multiple posting on the forum please... It seems you also tried to use Chameleon boot options with Clover ("bootflags npci=0x2000 & npci=0x3000 USBBusFix=Yes"). Needless to say that wouldn't work...
  25. Hervé
    APFS only Ok on SSD; it's a disaster on mechanical HDD. Card reader, Sleep & Bluetooth will require the same adjustments as for Sierra. If they work under 10.12, they'll work under 10.13 too.
×
×
  • Create New...