Jump to content

[GUIDE] Dell Latitude E6230 10.10.x [100%] [ENG]

dell El Capitan latitude 6230 e6230

  • Please log in to reply
18 replies to this topic

#1
duduclx

duduclx

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 219 posts
  • Gender:Male
  • Location:France
  • Interests:Datacenter and freecooling system

Hi,
Here a guide to install El Capitan on the Dell Latitude E6230.

specs:
- core I5-3320 2.6Ghz
- Intel HD4000
- intel 7 series
- network intel
- wifi AR928x (not original wifi card)
- audio IDT 92HD93

max_dell-latitudea_569eb8976f671.jpeg
not working:
- wifi/BT (need card replacement)

working:
- audio
- built-in multi screen (hdmi)
- powermanagement
- brightness
- hdmi port
- usb
- wired network
- trackpad (two fingers)
- battery statut

Not working:
- hdmi audio (should work with Voodoohda)
- brightness FN keys (dsdt fn keys for dell e6410 should work)

1/ CREATE USB INSTALLER

Spoiler


2/ INSTALL CLOVER
Spoiler

Add HFSPlus.efi

3/ CLOVER CONFIG FILE
Spoiler


Copy fakeSMC.kext in:
- /EFI/CLOVER/Kexts/Others
- /EFI/CLOVER/Kexts/10.10
- /EFI/CLOVER/Kexts/10.11

4/ BIOS CONFIGURATION:

Your Bios must be in A06 to A11 version, lower or upper bios version are not recommended.

Before, plug the USB installer on a usb port.
Press F12 at startup, then select Bios Configuration.
Spoiler

Others value are normaly configured by default.

5/ INSTALLATION:

You can install Mac OS X from the USB installer to the target drive, but on reboot on freshly installed system, the USB port, will not be recognised.
So, you will not be able to configure your account and reach the desktop.

We need to patch the DSDT from an other Mac/Hackintosh computer.
Spoiler


6/ DSDT PATCHES:
Spoiler


7/ POST INSTALLATION:
Here, replug the USB installer on your Dell E6230, select the freshly installed mac os x to boot.
Spoiler


8/ SSDT PATCHES:
Spoiler


9/ OTHERS
Spoiler


10/ PACK FILES:
Spoiler


11/ TRACKPAD ISSUE:
Spoiler


Cheers



#2
vusun123

vusun123

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPip
  • 1,065 posts
  • Gender:Male

El Capitan is 10.11. I have a Dell Latitude E6220 which is the smaller version of yours, and I have a few disaggrements here:

+ No trackpad issues for me

+ Brightness Fn keys works but is hardware-based not software-based. Changing the brightness setting in the bios can permanently disable brightness Fn keys.

+ Why stay at the lower bios version ? My bios is A13 and I don't have any strange issues aside from the brightness fn keys and an unknown key pressed rapidly at boot sometimes ( which is not a big deal, press another key and it's gone )



#3
duduclx

duduclx

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 219 posts
  • Gender:Male
  • Location:France
  • Interests:Datacenter and freecooling system

El Capitan is 10.11. I have a Dell Latitude E6220 which is the smaller version of yours, and I have a few disaggrements here:

disaggrements, so much ? :)

+ No trackpad issues for me

Well, first time i have this issue. the trackpad is workind good when on bios.
Maybe something wrong (bad caches, dual voodoops2 like in clover and L/E, old version, ... i have to check)

 

+ Brightness Fn keys works but is hardware-based not software-based. Changing the brightness setting in the bios can permanently disable brightness Fn keys.

what ? i just think than i have to patch the dsdt to activate this FN keys, like i done for my E6410.
fn keys are enabled in bios, brightness too, and also brightness is working.

read : - brightness FN keys (dsdt fn keys for dell e6410 should work)

BTW, mapping keyboard is "hardware-based" or more "software-based" ? because the keyboard is working, so the hardware part is working.

 

+ Why stay at the lower bios version ? My bios is A13 and I don't have any strange issues aside from the brightness fn keys and an unknown key pressed rapidly at boot sometimes ( which is not a big deal, press another key and it's gone )

Really, i don't know, but somes got trouble with A14 and UEFI boot.
I haven't tested by myself.
I just said "not recommended", i haven't said that will not works !
But, you have strange issue with your A13, so, if someone intend to update his bios before installing mac, i just say that will not be usefull and that's not recommended.
So he better stay with his actual bios version.

BTW, why update bios to have "strange issues" ?

Well, this dell E6230 is not mine, and i bring it back to his owner, i got only one evening to perform the installation.
Missing time, not all is perfect (like hdmi audio, trackpad, fn keys).

But if you have tips, please, share.
Just say "i have dissagrements" doesn't help.

 

Maybe i will read your E6220 install guide, if you have done one ? do you ?

 

thank you anyway !

:)



#4
Hervé

Hervé

    InsanelyMacaholic

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,958 posts
  • Gender:Male
  • Location:Rennes, BZH of course!

Topic title is wrong: it says E6320 (i.e. the 13" SandyBridge/HD3000 model) when the guide is about the E6230 (i.e. the 12" IvyBridge/HD4000 model). Once the OP amends the topic title, he will avoid some inevitable confusion and "disagreements" (single s, single g, double e) like vusun123's understandable yet erroneous comparison with E6220 and for which latest BIOS A13 bears, indeed, no issue whatsoever (see my sig)...

 

With the E6230, BIOS is Ok up to version A11, not beyond. If downgrading for Hackintosh purposes, one must 1st revert to a much older version like A03 before upgrading to A11 max.

 

VoodooHDA does not support HDMI audio. You need the patched AppleHDA kext for that. There are IDT 92HD93 patches flying around, no big deal to patch the vanilla AppleHDA kext whatever the (recent) OS X release installed (Mav/Yos/EC).

 

There are full guides at OSXL for these E6x20/E6x30 models.

 

NB: Fn-<key> combinations are ACPI controlled so DSDT/SSDT code can be written to program the correct event key combinations. There are guides/tutos on this. It's kinda "advanced" stuff…



#5
duduclx

duduclx

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 219 posts
  • Gender:Male
  • Location:France
  • Interests:Datacenter and freecooling system

Title ang tag edited !

 

bad form of the code area for dsdt patch, edited to have a working copy/paste.

 

cheers



#6
Hervé

Hervé

    InsanelyMacaholic

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,958 posts
  • Gender:Male
  • Location:Rennes, BZH of course!

You've not mentioned it but I take it you don't actually have Sleep working on that E6230, do you?



#7
duduclx

duduclx

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 219 posts
  • Gender:Male
  • Location:France
  • Interests:Datacenter and freecooling system
This computer is not mine.
I got it for 2 days only.
The owner may borow it to me.
I'll try to look at it.
I think have tested it and have it working (not sure).

Why do you think it is not working ?

#8
Hervé

Hervé

    InsanelyMacaholic

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,958 posts
  • Gender:Male
  • Location:Rennes, BZH of course!

Well... the text file inside your pack that says "Sleep is not working"... which is confirmed when I use your posted DSDT.



#9
duduclx

duduclx

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 219 posts
  • Gender:Male
  • Location:France
  • Interests:Datacenter and freecooling system
Do you have tips to have it working ?

#10
Hervé

Hervé

    InsanelyMacaholic

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,958 posts
  • Gender:Male
  • Location:Rennes, BZH of course!

It's a simple matter of applying Rehabman's "USB _PRW" DSDT patch. Or you simply manually edit the EHCx/XHC/GLAN/HDEF devices so that their _PRW method returns (0x--, 0x00) as opposed to say (0x--, 0x03) or (0x--, 0x04).



#11
truongphu178

truongphu178

    InsanelyMac Protégé

  • Members
  • Pip
  • 6 posts

Thank you very much.



#12
Blaggah

Blaggah

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 453 posts
  • Gender:Male
  • Location:MA

Did that work for you truongphu178? 



#13
Hervé

Hervé

    InsanelyMacaholic

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,958 posts
  • Gender:Male
  • Location:Rennes, BZH of course!

http://forum.osxlati...-capitansierra/

 

There are Clover-based guides too at the same place.



#14
bisk

bisk

    InsanelyMac Protégé

  • Members
  • PipPip
  • 78 posts

Does anyone have a more recent AppleHDAIDT.kext compatible with the final El Capitan 10.11.6 ?

 

The one supplied in the package fails to load with bad link symbols !

 

Thanks in advance

 

:)



#15
Hervé

Hervé

    InsanelyMacaholic

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,958 posts
  • Gender:Male
  • Location:Rennes, BZH of course!

Use the kexts provided in the pack of the guides I linked to in post #13... Bear in mind that the dummy IDT kext remains the same throughout but it's best to patch the vanilla AppleHDA kext. Re-using an older pre-patched AppleHDA may not work indeed.



#16
bisk

bisk

    InsanelyMac Protégé

  • Members
  • PipPip
  • 78 posts

Audio is good !!!

 

Thank you so much for helping me crack this :)

 

With the injector/dummy kext, the patches in the clover config.plist file AND the layout mod in the DSDT, it never even occurred to me that the AppleHDA kext needed to be patched as well ! I had just been going with the vanilla 10.11.6 version.

 

What's the purpose of the clover "on the fly" patches ? I had assumed that the below were doing the necessary AppleHDA binary patching.

 

I found these in several guides :

 

<key>KextsToPatch</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>IDT 76DF #1 (Zeroing 11d41983 codec)</string>
                <key>Disabled</key>
                <true/>
                <key>Find</key>
                <data>gxnUEQ==</data>
                <key>Name</key>
                <string>AppleHDA</string>
                <key>Replace</key>
                <data>AAAAAA==</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IDT 76DF #2 (Zeroing 11d41984 codec)</string>
                <key>Find</key>
                <data>hBnUEQ==</data>
                <key>Name</key>
                <string>AppleHDA</string>
                <key>Replace</key>
                <data>AAAAAA==</data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>IDT 76DF #3 (Patching 11d4198b with 111d76df codec)</string>
                <key>Find</key>
                <data>ixnUEQ==</data>
                <key>Name</key>
                <string>AppleHDA</string>
                <key>Replace</key>
                <data>33YdEQ==</data>
            </dict>
            <dict>

 

Some guides used the IDT 76DF #1 patch and some did not, so I tried both with and without that first one.

 

Also, I always thought that the "dummy" kext was simply to activate an alternative layout ID, in this case, #12.

 

HDAEnabler.kext often accomplished this but I know that sometimes the injector goes by another name.

However, the HDAEnabler is not necessary at all when the layout ID mod is done in the DSDT.

I noticed that the AppleHDA_IDT92HD93.kext had more to it than the typical HDAEnabler so knew to use it even tho' I have the HDEF layout mod in my DSDT.

 

So, I have HDEF mod in DSDT, AppleHDA_IDT92HD93.kext injector AND 2-3 clover "on the fly" patches for AppleHDA.kext but STILL need a patched AppleHDA.kext !

 

If we can't just go with a vanilla AppleHDA in SLE why bother with the injector kext and clover "on the fly" patches ?

 

Seems so much simpler to make all the changes in the AppleHDA.kext bundle and have it all in one place.

 

Could you please explain to me the thinking here ?

 

Anyway, my audio is working fine now, thanks again.

 

For the record, I have a Dell Latitude E6330: i5-3320M, MacbookPro9,2, clover r2.3k_r3998, Mac OS X 10.11.6.

 

Previously, I had 10.10.5 on this laptop and everything was perfect EXCEPT for USB. I never got those two ports to work right.

With no kext installed for USB, inserting a device in either port would make the system freeze, requiring a hard reboot.

With a couple year old version of GenericXHCI installed, the back port worked for both USB 2 and 3 devices but the side port recognized no devices and only worked for charging. With Fake_PCIID/Fake_PCIIDMux, both ports worked for USB2 but inserting USB3 devices caused a system freeze requiring a hard reboot. I tried all sorts of USB series 7/multiplexing mods all to no avail. This went on for months.

 

So, I finally just upgraded to El Capitan and now USB works perfectly for both USB2 and USB3 devices with NO additional kexts, just stock vanilla. Also, I have no USB2/3 multiplexing mods applied to my DSDT.

 

I just wanted to share my experience to, perhaps, help someone else with the E6330. It's just like the E6230 where the latest BIOS that will work w/o artifacts is version A11.

 

Finally, I have one more question, in addition to my AppleHDA confusion. Specifically, how do I learn more about customizing FakeSMC for a particular Mac model ? I was using a FakeSMC which specified Types->smc-compatible of "smc-napa" and switched to yours which specifies "smc-huronriver".  It looks like I only get 2 speeds despite the fact that I have a custom generated SSDT for my CPU.

This from watching HWMonitor in the top bar. This is the case with either FakeSMC, if that even matters.

 

I have this in my system.log ...

 

WARNING: IOPlatformPluginUtil : GetCPUIDInfo: this is an unknown CPU model 0x3a

-- power management my be incomplete or unsupported

 

Thanks in advance for anything that you can tell me and thanks for all that you do in the Hackintosh world !



#17
Hervé

Hervé

    InsanelyMacaholic

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,958 posts
  • Gender:Male
  • Location:Rennes, BZH of course!

As the name implies, Clover "on-the-fly" patching does what it says on the tin: it patches the cache, built on vanilla kexts. As such, no need to manually patch kexts.

 

On the other hand, older Chameleon/Enoch-based systems needed to manually apply the patches to kexts. Hence, the replacement of vanilla AppleHDA by it's patched equivalent in /S/L/E for instance. Recent Enoch versions now support a cache patching mechanism similar to Clover's.

 

The IDT 92HD93 patches for AppleHDA may vary according to the OS X/macOS release. For instance, the Sierra patches differ a little from El Capitan which themselves differ a little from Yosemite.

 

Regarding FakeSMC tuning, you can refer to here. No reason why this would effect CPU power management, on the contrary. You must have made a mistake along the way.



#18
bisk

bisk

    InsanelyMac Protégé

  • Members
  • PipPip
  • 78 posts

Thanks again Herve,

 

Well my clover "on the fly patches" were obviously NOT patching. I will test to see if removing them makes no difference and then just delete them if they are indeed useless.

 

It turns out that I am running through many P-States. Speeds just don't register on the individual "CPU Core #" readouts of HWMonitor only on the "CPU Package Average" readout. This is the case on 3 different clones that I'm building right now. So, just a bug in HWMonitor, I guess. Or maybe the functionality has been purposely altered ? I've been out of it for a little while.

 

Thanks for the lead on FakeSMC tuning ... on that :)

 

Oh, I should also add that attempting to get the media card reader working ends a bit in disaster.

I attempted to add the O2-Micro device id to AppleSDXC.kext and it loads but nothing attaches to RP06.PXSX and no SD cards are recognized and eventually KP happens at wake. Using VoodooSDHC.kext does work perfectly insofar that SD cards are recognized and mount BUT then no wake from sleep (most likely black screen KP)  :(



#19
Hervé

Hervé

    InsanelyMacaholic

  • Members
  • PipPipPipPipPipPipPipPipPipPipPip
  • 2,958 posts
  • Gender:Male
  • Location:Rennes, BZH of course!

Re: SD card reader, just patch the DSDT, it's far simpler and it'll then work OOB whatever the OS X/macOS version. It's a simple matter of adding a DSM method to decalre the device compatible with Apple's own Broadcom device. If you download the DSDT provided in my guides, you'll see the details under the relevant device (I think I rename RP06.PXSX to RP06.SDXC for increased visbility, just look it up).

 

Don't use VoodooSDHC, it's not required and, indeed, affects Wake after Sleep.

 

All in all, why don't you just follow the guides I posted at OSXL? This one was for Yosemite and never 100% accurate/complete.







Also tagged with one or more of these keywords: dell, El Capitan, latitude, 6230, e6230


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2017 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy