Jump to content

Hervé

Administrators
 View Profile  See their activity

  • Posts

    10013

  • Joined

  • Last visited

  • Days Won

    560

 Content Type 

Everything posted by Hervé

  1. 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.
  2. Hervé
    Please read the FAQ section... https://osxlatitude.com/index.php?/topic/8696-is-my-wireless-card-compatible-with-os-x/
  3. 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.
  4. 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
  5. 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/
  6. 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 .
  7. 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...
  8. 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.
  9. Hervé
    Moving to the correct "Help and Support section"... Guys, what's the trouble? Can't read "Complete guides for Dell computers. No support here." as indicated under each Guide subsection? Try and look at the existing Latitude 5480 threads in the 5000 Series section.
  10. Hervé
    Just follow the instructions posted on the blog.
  11. Hervé
    Look in the forum FAQ section...
  12. Hervé
    You can look thing up here: http://www.insanelymac.com/forum/topic/301324-toshiba-l855-14j-108x All in all, you'll probably have to inject your AMD dGPU specs in DSDT and setup Clover to inject ATI, possibly select "Load vBios" + "Patch vBIOS" + the correct framebuffer.
  13. Hervé
    Top and bottom of screen don't show? I've got that on my TV when plugged in through HDMI and I have to adjust the underscan (or overscan?) parameter. Try that through your display PrefPane. That certainly allows me to perform a sort of zoom in/zoom out and get the full macOS desktop on screen.
  14. Hervé
    The only other thing I can think of is CPU power management. Does that work Ok? To me, if the power led does not fade in and out, your computer has not gone into sleep mode.
  15. Hervé
    Did you check or consult our posted (non-exhaustive) inventory? https://osxlatitude.com/index.php?/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/ If you have a WWAN slot and want a perfect card that'll work OOB and as on a real Mac, I highly recommend Apple's own Broadcom BCM94360CD. It needs an adapter (but they exist in mini-PCIe and M.2 form) and it's more expensive than other cards but works fantastic and at great speed. https://osxlatitude.com/index.php?/topic/7554-apple-broadcom-bcm4360cd-80211-ac-wifi-and-bluetooth-combo-card/
  16. Hervé
    That'll work.
  17. Hervé
    You can add the patch to FakeSMC Info.plist. It'll then be sustainable to macOS updates, as long as Apple does not change the kext name and the associated Info.plist entries syntax like they often do between releases. It's the same as for any such patches (AGPM, WWAN, Bluetooth) where you add an entry rather than modify existing ones.
  18. Hervé
    Silly question probably but did you disable hibernation? Re: wifi USB dongle, it should not be a problem as long as you do not enable "USB wake" in BIOS". Make sure it's the same for LAN: no "Wake on LAN". Your kexts are Ok.
  19. Hervé
    That's right; unsupported afaik.
  20. Hervé
    Try the attached. * DSDT mods done: combined both _DSM methods of LPCB device into a single one _PWR methods of GLAN/HDEF/EHCx devices changed from returning (0x0D,0x04) to (0x0D,Zero) removed "If" tests in _PWR method of EHCx devices to keep a single "Return" statement NB: It would be interesting to know what mods you made to the _WAK method. revised_DSDT.aml.zip * Clover config mods done: removed all selected ACPI fixes removed USB FixOwnership option injected proper MBP6,2 SMBIOS revised_Clover_config.plist.zip
  21. Hervé
    Check your add-on kexts then; there's clearly something wrong somewhere.
  22. Hervé
    Patch details sure are Ok but it seems you somehow screwed the framebuffer kext. Maybe you made another binary mod by mistake somewhere... Why don't you update to 10.12.6 and use the patched kext I uploaded? Save yourself some time!
  23. Hervé
    No, proceed as follows: place the FakePCIID kexts in /L/E place the Brcm kexts in /S/L/E manually repair permissions to both folders manually rebuild your cache remove those kexts from Clover kexts folder if present there reboot and check behaviour If you don't know how to manually repair permissions and rebuild the cache, check the FAQ forum section.
  24. Hervé
    Any update will re-instate vanilla kexts in /S/L/E and overwrite any patched kexts, That's a general matter that should be known by all. Make a good note of that. Hence the explanations I just wrote above regarding patched SNB framebuffer kext (the kext versioning trick can be generalised too). It's a little silly to revert to a backed-up 10.12.3 installation when repatching the 10.12.5 vanilla framebuffer would have sorted you out. If you run Enoch, you know what to do now (and update to 10.12.6)... If you use Clover, you should configure the patch in the "on-the-fly" manner.
  25. Hervé
    When you rebuild the cache, OS X/macOS includes kexts in /S/L/E and /L/E. Kexts in Clover EFI folder are injected, not cached. Obviously, don't duplicate kexts in both places (/S/L/E or /L/E and EFI/kexts/xxx).
×
×
  • Create New...