Jump to content

Hervé

Administrators
  • Posts

    10027
  • Joined

  • Last visited

  • Days Won

    561

Everything posted by Hervé

  1. AR9485 is not the best compatible card for OS X/macOS. You'll actually require a patched kext to get it supported and you'll find speed limited to 11Mbps. It's probably best to replace that card by a fully compatible model. https://osxlatitude.com/index.php?/topic/2120-inventory-of-supported-and-unsupported-wireless-cards/ Your Clover config has lots of incorrect settings. Try this one instead and remove NullCPUPM kext from your Clover Other folder. config.plist.zip
  2. Why don't you just simply make a vanilla ML installer with myHack, then install standard 64bit ML on your X61. Then, you'll be able to apply the MLPF hack which requires to have a legit' ML installer package in Applications folder. You can't just overwrite the vanilla 64bit kernel with the fat binary version from ML Beta 1. Whilst it may then run in 64bit kernel mode, it just won't allow you to run ML in 32bit kernel mode since you wouldn't have the necessary fat binary kexts. So follow the principles explained in our posted MLPF guides: https://osxlatitude.com/index.php?/topic/2464-dell-latitude-d630-intel-gma-x3100-ml-with-full-qeci/ https://osxlatitude.com/index.php?/topic/2468-dell-latitude-d830-intel-gma-x3100-ml-with-full-qeci/ https://osxlatitude.com/index.php?/topic/2495-dell-latitude-d530-intel-gma-x3100-ml-with-full-qeci/ https://osxlatitude.com/index.php?/topic/2467-dell-latitude-d430-intel-gma950-ml-with-full-qeci/ Again, if you previously ran Lion 10.7.5 on that X61, you probably can re-use the add-on kexts you had installed, again, as long as they're fat binary.
  3. Clearly not... https://osxlatitude.com/index.php?/topic/9961-how-do-i-repair-permissions-and-rebuild-the-cache-yosemite-and-later/
  4. Please state the method you use for installation and post the relevant files. For instance, if you use Clover, post the zipped EFI folder (less the Themes subfolder to limit the size). Re: wireless, Atheros ar94 is incomplete data; it'll be something like AR94xx.
  5. HDAU is the device for HDMI audio. Regular audio uses HDEF. On E6x40 laptops, audio is silent if you reboot from Windows. To get audio working, always perform a cold start.
  6. You can't have VoodooHDA (+ AppleHDADisabler) at the same time as patched AppleHDA. Use either/or (latter will be better than former) but not both at the same time. So, apart from audio, what would not be working now?
  7. You could simply read the info relating to the page you linked. https://github.com/RehabMan/OS-X-Atheros-3k-Firmware Then contact the author, he's sufficently known throughout the Hackintosh community...
  8. Where did you get your Clover config file from??? Change your SMBIOS profile from MBP10,2 which is an IvyBridge system to MacBookPro11,1 or MacBookAir6,2 which are Haswell systems and correct profiles for the E6x40. You appear to be missing Rehabman's FakePCIID kexts that are necessary for full graphics acceleration: FakePCIID FakePCIID_Intel_HD_Graphics You appear to be missing the dummy ALC292 kext that's necessary to obtain audio. It's available in all our guides related to the E6x40/E7x40 systems. If you want to get HDMI audio, you'll also need the Azul FB binary patch for HDMI Rehabman's FakePCIID_Intel_HDMI_audio kext If you want USB3.0/2.0 multiplexing to work, you'll also need: Rehabman's FakePCIID_XHCI_mux kext Please follow our existing guides for your system: https://osxlatitude.com/index.php?/topic/8506-dell-latitude-inspiron-precision-xps-clover-guide/ You'd also find useful guidance + files here: https://osxlatitude.com/index.php?/topic/7387-dell-latitude-e6440-with-i5-4300m-hd4600-and-1600x900-lcd-mavericksyosemiteel-capitansierra/
  9. Make sure they're fat binary or they just won't load and you could find yourself unable to boot initial 64bit-only ML installer/installation. You can use lipo command (from Xcode) to that effect.
  10. It's all in the relevant guide in the Guides section of the forum... Please look it up.
  11. https://osxlatitude.com/index.php?/forum/161-faqs-tutorials/
  12. Then try without this patched kext (for which there is no garantee because I cannot test it) and just boot without the Clover SKL patch to verify the dual external output. Then try with the suggested 2xDVI / 1xDVI+1xDP Clover patch for FB #4/port #7. NB: you'll have to boot without cache to bypass /L/E.
  13. Yup, combination of missing EFI partition + BIOS EFI settings. This SSD is clearly bootable.
  14. 'sounds like you have something corrupt in your installation so, unless you can identify what's likely causing the freeze through the logs, you'll most probably have to re-install from scratch.
  15. The version provided by myHack should suffice but you can upgrade to any version published after that as long as it remains under r25xx. I run version r2468 on my ageing Latitude D Series under old Mac OS X versions including MLPF'ed ML. Later versions gave me boot issues. Chameleon-2.3svn-r2468.pkg.zip
  16. Ok, you have Skylake HD520 graphics and use the usual layout-id 0x19160000; that's what I was asking for in case it still eluded you... As explained here and at many other places, OS X/macOS supports up to 4 x display ports and at least 6 x connector types: 0000 ... for framebuffer #0 / port #0 0105 ... for framebuffer #1 / port #5 0204 ... for framebuffer #2 / port #6 0306 ... for framebuffer #4 / port #7 0100 0000 for VGA 0200 0000 for LVDS (built-in LCD of laptops) 0400 0000 for eDP (built-in LCD of laptops) 0002 0000 for DVI 0004 0000 for DP 0008 0000 for HDMI Now, if you look at your IOReg data, you'll see 3 x different framebuffers under device iGPU@2: AppleIntelFramebuffer@0 ​connector-type: 02000000, i.e LVDS output port-number: 00 AppleIntelFramebuffer@1 ​connector-type: 00080000, i.e HDMI output port-number: 05 AppleIntelFramebuffer@2 connector-type: 00040000, i.e DP (or DVI since, in practice, DVI also works with DP's connector-type) port-number: 06 As such, your SKL layout only support 3 x possible display ports: the built-in LCD, the HDMI and 1 x DP/DVI. If you want 2 x DVI or 1 x DVI + 1 x DP, you have to set the framebuffer #1 to DVI/DP connector type. You'd lose HDMI capability in the process. The other alternative would be to patch the layout 0x19160000 to support 4 x display outputs and this would be the built-in LCD, 1 x HDMI and 2 x DVI/DP. Let's look at the code for layout 0x1916000 in High Sierra (10.13.3 beta2) SKL framebuffer kext : 00001619 00000000 C4820800 00000000 01030303 00002002 00005001 00000060 6C050000 6C050000 00000000 00000000 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00040000 87010000 FF000000 01000000 20000000 0F090000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 103C0E00 00000000 703C0E00 00000000 C03C0E00 00000000 01000000 08000000 01000000 00000000 In that layout code, the default output ports are as follows: 0000 0800 02000000 98000000 // --> 0000 = FB #0/port #0, 02000000 = LVDS connector type 0105 0900 00040000 87010000 // --> 0105 = FB #1/port #5, 02040000 = DP connector-type 0204 0A00 00040000 87010000 // --> 0204 = FB #2/port #6, 00040000 = DP connector-type ` Now, in your Cover config, you apply a SKL framebuffer patch for HDMI output & audio (it's labelled HD 520 HDMI #1): In: AppleIntelSKLGraphicsFramebuffer Find: 01050900 00040000 Replace by: 01050900 00080000 This basically converts FB #1/port #5 from DP to HDMI as reflected in your IOReg. The patch is therefore effective and works as you stated yourself. If you want 2 x DVI or 1 x DVI + 1 x DP, simply disable this Clover HDMI patch with Clover Configurator app (check the 'Disabled' case). I'm pretty sure it'll work. DP connector-type 00040000 usually work for DVI ports and it does in your case. This being said, FB #1/port #5 is usually reserved for HDMI output so if you still did not obtain 2 x independant displays, try to change FB #1/port #5 of the layout to FB #4/port #6 through the following Clover patch: In: AppleIntelSKLGraphicsFramebuffer Find: 01050900 00040000 Replace by: 03060900 00040000 ` If you want a 4th display output port, then we have to patch layout 0x19160000 much further. This will be done by: changing the layout from a 3xport model to a 4xport one add the 4th port entry (FB # + port # + priority + connector type + delay) Going by experience with earlier Intel Framebuffers, the number of ports should be defined in the following code of the layout: 01030303 // --> ??/PipeCount/PortCount/FramebufferCount and the 4th port would have to use FB #4/port #7: 0306 As such, a modified 4 x port layout could be: 00001619 00000000 C4820800 00000000 01030404 00002002 00005001 00000060 // 01030404 = 4 port/4 FB 6C050000 6C050000 00000000 00000000 00000800 02000000 98000000 01050900 // 0000=FB #0/port #0, 02000000=LVDS, 0105=FB #1/port #5 00080000 87010000 02040A00 00040000 // 00080000=HDMI, 0204=FB #2/port #6, 00040000=DP/DVI 87010000 03060A00 00040000 87010000 // 0306=FB#4/port #7, 00040000=DP/DVI FF000000 01000000 20000000 0F090000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 103C0E00 00000000 703C0E00 00000000 C03C0E00 00000000 01000000 08000000 01000000 00000000 No guarantee that'll work but worth testing. You can try the patch by installing the attached modified kext in /L/E (binary modded + kext versioning up'ed). It'll take precedence over the vanilla kext in /S/L/E, so it's very easy to revert back to the vanilla kext if required. Simply repair permissions and rebuild your cache. AppleIntelSKLGraphicsFramebuffer.kext.zip
  17. We're not going to make anything out of those IORegistryExplorer screenshots. You've selected the data related to the monitors (which is kind of useless, especially the built-on LCD), not the data related to the framebuffers (i.e. the output ports), which is what interests us here. Please save the output in a file, zip it and attach it directly to the forum rather than use an external place. The behaviour you described when using DVI + DP port is as I thought: you most likely require to patch your SKL framebuffer for those output ports, assuming graphics run on the SkyLake iGPU. So, to recap: post your graphics specs state which layout you use post a saved IORegistryExplorer output post your Clover config file
  18. You're gonna have to tell us which external display is detected. Somehow, I doubt the VGA output can properly work (it's probably wired to the DVI port, hence the mirroring). Bear in mind that there's been no support for VGA since Ivy Bridge HD4000 era and it could last be patched on SandyBridge HD3000 platforms (granted some Haswell laptops with HD4400 graphics do have VGA working OOB but these usually had a dGPU too).. Use IORegistryExplorer to identify the output port of the detected display or plug only 1 at a time and see which gets detected. Though one would have expected you to have done this already. If you want 2 x independant external displays, I'm pretty sure you'll have to use DVI and/or DP on the PR03x and/or HDMI on your laptop. You forgot to mention whether your system has SKL iGPU only or if it's fitted with the AMD dGPU too. I would not expect VGA output in the former case but you might get it OOB (like with some Haswell laptops) in the latter case. So, post your graphics specs or add your E5470 specs in your signature (which is the desired mode on Hackintosh forums).
  19. As I said, move all your add-on kexts to /L/E, repair permissions and rebuild your cache. Your DSDT already has a PNLF device that seems properly defined so I'd say all looks Ok on that front. Personally speaking, I don't use the IntelBacklight or IntelGraphicsFixup kexts on my Ivy Bridge/HD4000 E6230 laptop and all is Ok regarding LCD brightness and its settings bar. Why don't you try without?
  20. Check what add-on kexts you had previously installed in /S/L/E and/or /L/E. These may clash with kexts you inject from Clover EFI folder. Ideally, move (not copy) your Clover kexts to /L/E to cache them. It's much better than injecting kexts.
  21. Your DSDT injects layout 3. Your Clover config shows AppleHDA patches for ALC269. No idea about the dummy ALC269 kext for codec definition, you've not mentioned it. I can only assume you previously had audio working under the previous version of Sierra so make sure to rebuild your cache because that's what Clover patches. https://osxlatitude.com/index.php?/topic/9961-how-do-i-repair-permissions-and-rebuild-the-cache-yosemite-and-later/
  22. Tried Display Menu app yet? It has an option to set mirroring on and off. https://osxlatitude.com/index.php?/topic/2366-finders-bar-display-tool/
×
×
  • Create New...