Jump to content
PayPal donations: [email protected] ×
bulletproof

Dell Latitude E6430 / E5430 Hard Drive Temp with Clover EFI

Recommended Posts

I have set up several Dell Latitude E6430 / E5430's, with different hard drive configurations, and all appear to have the same issue; the hard drive runs at a constant 118*-122* F. I've tried tweaking several settings, but nothing seems to help. The drive operates at a normal 80* F when booted to Windows or Ubuntu, so it's clearly not a BIOS / Hard Drive issue. And as I have already mentioned, this is consistent across several different systems. I haven't found any other reports of hard drive's overheating, but can't believe that I would be the only one.

 

If you find that you also have this issue, please post a "Me Too" in the comments with as much information about your system as well.

 

HWMonitor Screen Shot:

HWMonitor-HD-Temp.png

 

 

 

Just to clear up some possible assumptions; I have been successfully building hackint0sh's for about 10 years. I have only recently started messing with Hackbook Pr0's (about 2 years). Initially I was using Chameleon, but decided to switch to Clover when I found Chameleon seemed to have trouble performing certain tasks (like patching the video output for Intel Graphics). While using Chameleon, I was actually manually patching the binary with the outputs of my system to get everything to work as it should (if you have no idea what I'm referring to, it doesn't really matter, so don't even worry about it). ;)

 

The problem with doing this was upgrading. Every time I needed to upgrade the OS, I would need to re-patch the updated kext. Such a pain! In finding that Clover did this rather simply, and that updates would no longer be an issue, I made the switch. Since using Clover, the main things I've had to fight with are; getting the trackpad (which works pretty well (with multi-touch)), bluetooth, and the battery percentage to function properly. But, addressing those things are issues for another time.

 

Shortly after I switched to Clover, I found THIS VERY HELPFUL GUIDE (Thank You VERY MUCH pokenguyen!!!), and tweaked things from there.

 

I probably have several hundred hours in tweaking, and researching, all the configuration settings/options in Clover itself. And although, I don't completely understand everything it can do, I know enough to get a system working as it should. I've just come to an end in trying to address this overheating hard drive issue, which seems to only exist in laptops.

 

The one thing I have absolutely no understanding in, is DSDT...and maybe that's where my issues are. I really wished I understood the code within an aml file, but sadly, I do not. I am very good at learning how to take knowledge from someone else's experience and convert it to something I can apply to my own hardware, but aml files are beyond me.

 

I'm going to post as much information as I can about the system(s) I am using, and would appreciate any suggestions/feedback on how to resolve this Hard Drive temperature issue.

 

 

 

System 1:

 

Dell Latitude E6430

  • Processor: i7-3540M
  • Graphics: Intel HD Graphics 4000 1024 MB (Vendor: Intel (0x8086) Device ID: 0x0166 Revision ID: 0x0009)
  • Graphics: Dell NVS 5200M (Vendor: NVIDIA (0x10de) Device ID: 0x0dfc Revision ID: 0x00a1) (NOT USED)
  • SATA: Seagate ST95005620AS Hard Drive

About-This-Mac-and-MacBook-Pro---E6430.p

 

 

 

EFI: Clover 3193

 

 

 

/EFI/EFI/CLOVER/drivers64UEFI/

  • DataHubDxe-64.efi
  • EmuVariableUefi-64.efi
  • FSInject-64.efi
  • HFSPlus.efi (Project/Support Link)
  • OsxAptioFix2Drv-64.efi
  • OsxFatBinaryDrv-64.efi

 

 

 

/EFI/EFI/Clover/kexts/Other/

 

 

 

/Extra/Extensions/ (/System/Library/Extensions/myHack.kext/Contents/PlugIns/)

 

 

 

/System/Library/Extensions/ (additional)

 

 

 

Config.plist

config.no.sn.plist.zip

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>Fixes</key>
			<dict>
				<key>AddDTGP_0001</key>
				<true/>
				<key>FixDarwin_0002</key>
				<true/>
				<key>FixShutdown_0004</key>
				<false/>
				<key>AddMCHC_0008</key>
				<false/>
				<key>FixHPET_0010</key>
				<false/>
				<key>FakeLPC_0020</key>
				<false/>
				<key>FixIPIC_0040</key>
				<false/>
				<key>FixSBUS_0080</key>
				<true/>
				<key>FixDisplay_0100</key>
				<true/>
				<key>FixIDE_0200</key>
				<false/>
				<key>FixSATA_0400</key>
				<false/>
				<key>FixFirewire_0800</key>
				<false/>
				<key>FixUSB_1000</key>
				<true/>
				<key>FixLAN_2000</key>
				<true/>
				<key>FixAirport_4000</key>
				<false/>
				<key>FixHDA_8000</key>
				<false/>
				<key>NewWay_80000000</key>
				<true/>
				<key>FIX_DARWIN_10000</key>
				<false/>
				<key>FIX_RTC_20000</key>
				<true/>
				<key>FIX_TMR_40000</key>
				<true/>
				<key>AddIMEI_80000</key>
				<false/>
				<key>FIX_INTELGFX_100000</key>
				<false/>
				<key>FIX_WAK_200000</key>
				<true/>
				<key>DeleteUnused_400000</key>
				<true/>
				<key>FIX_ADP1_800000</key>
				<true/>
				<key>AddPNLF_1000000</key>
				<true/>
				<key>FIX_S3D_2000000</key>
				<true/>
				<key>FIX_ACST_4000000</key>
				<true/>
				<key>AddHDMI_8000000</key>
				<true/>
				<key>FixRegions_10000000</key>
				<true/>
			</dict>
			<key>Name</key>
			<string>DSDT.aml</string>
			<key>DropOEM_DSM</key>
			<false/>
			<key>ReuseFFFF</key>
			<false/>
		</dict>
		<key>DropTables</key>
		<array>
			<dict>
				<key>Signature</key>
				<string>DMAR</string>
			</dict>
		</array>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<true/>
			<key>Generate</key>
			<dict>
				<key>CStates</key>
				<false/>
				<key>PStates</key>
				<false/>
			</dict>
		</dict>
	</dict>
	<key>Boot</key>
	<dict>
		<key>DefaultVolume</key>
		<string>LATITUDE</string>
		<key>Arguments</key>
		<string>-v dart=0 kext-dev-mode=1</string>
		<key>Legacy</key>
		<string>LegacyBiosDefault</string>
		<key>Log</key>
		<false/>
		<key>NeverHibernate</key>
		<false/>
		<key>Secure</key>
		<false/>
		<key>Timeout</key>
		<integer>2</integer>
		<key>XMPDetection</key>
		<string>Yes</string>
	</dict>
	<key>Devices</key>
	<dict>
		<key>Audio</key>
		<dict>
			<key>Inject</key>
			<string>0</string>
		</dict>
		<key>USB</key>
		<dict>
			<key>FixOwnership</key>
			<true/>
			<key>Inject</key>
			<true/>
			<key>HighCurrent</key>
			<true/>
			<key>AddClockID</key>
			<true/>
		</dict>
		<key>UseIntelHDMI</key>
		<false/>
	</dict>
	<key>DisableDrivers</key>
	<array>
		<string>VBoxHfs</string>
	</array>
	<key>GUI</key>
	<dict>
		<key>Language</key>
		<string>en:0</string>
		<key>Mouse</key>
		<dict>
			<key>Enabled</key>
			<false/>
		</dict>
		<key>Scan</key>
		<dict>
			<key>Entries</key>
			<true/>
			<key>Legacy</key>
			<false/>
			<key>Tool</key>
			<false/>
		</dict>
		<key>ScreenResolution</key>
		<string>1600x900</string>
		<key>TextOnly</key>
		<false/>
		<key>Theme</key>
		<string>bootcamp</string>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>DualLink</key>
		<integer>1</integer>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<true/>
			<key>NVidia</key>
			<true/>
		</dict>
		<key>ig-platform-id</key>
		<string>0x01660004</string>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleRTC</key>
		<true/>
		<key>AsusAICPUPM</key>
		<true/>
		<key>Debug</key>
		<false/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>AppleHDA IDT 76DF #1</string>
				<key>Find</key>
				<data>ixnUEQ==</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>33YdEQ==</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>AppleHDA IDT 76DF #2</string>
				<key>Find</key>
				<data>hBnUEQ==</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>AAAAAA==</data>
			</dict>
			<dict>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Find</key>
				<data>QbzHAgDgPQABAAA=</data>
				<key>Replace</key>
				<data>QbzHAgDgPQAAAAA=</data>
				<key>Comment</key>
				<string>Disable XHCI</string>
			</dict>
			<dict>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Find</key>
				<data>xoDIAAAAAQ==</data>
				<key>Replace</key>
				<data>xoDIAAAAAA==</data>
				<key>Comment</key>
				<string>Disable the sleep code</string>
			</dict>
			<dict>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Find</key>
				<data>dU1Ii7voAQAA</data>
				<key>Replace</key>
				<data>601Ii7voAQAA</data>
				<key>Comment</key>
				<string>Enable PCI power management</string>
			</dict>
			<dict>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Find</key>
				<data>gUkIAABAAA==</data>
				<key>Replace</key>
				<data>gUkIAAAAAA==</data>
				<key>Comment</key>
				<string>Patch MSI 1</string>
			</dict>
			<dict>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Find</key>
				<data>QcdHCAAAQAA=</data>
				<key>Replace</key>
				<data>QcdHCAAAAAA=</data>
				<key>Comment</key>
				<string>Patch MSI 2</string>
			</dict>
			<dict>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Find</key>
				<data>QcdHCAAAQAA=</data>
				<key>Replace</key>
				<data>QcdHCAAAAAA=</data>
				<key>Comment</key>
				<string>Patch MSI 3</string>
			</dict>
			<dict>
				<key>Name</key>
				<string>AppleUSBXHCI</string>
				<key>Find</key>
				<data>9oDUAAAAgHU0</data>
				<key>Replace</key>
				<data>9oDUAAAAgOs0</data>
				<key>Comment</key>
				<string>Disable Intel</string>
			</dict>
			<dict>
				<key>Name</key>
				<string>AppleIntelFramebufferCapri</string>
				<key>Find</key>
				<data>BAYAAAAEAACBAAAA</data>
				<key>Replace</key>
				<data>BAYAAAAIAAAGAAAA</data>
				<key>Comment</key>
				<string>Patch audio HDMI HD4000 1366x768</string>
			</dict>
			<dict>
				<key>Name</key>
				<string>AppleIntelFramebufferCapri</string>
				<key>Find</key>
				<data>BABmAQEDAQEAAAAC</data>
				<key>Replace</key>
				<data>BABmAQECBAIAAAAE</data>
				<key>Comment</key>
				<string>Patch HDMI-DP port HD4000 1600x900 #1</string>
			</dict>
			<dict>
				<key>Name</key>
				<string>AppleIntelFramebufferCapri</string>
				<key>Find</key>
				<data>MAIAAAAAAAABAAAAQAAAAAAAAAABAAAAQAAAAAAAAAABAAAAQAAAAAAAAAAAAAAA</data>
				<key>Replace</key>
				<data>MAIAAAIFAAAABAAABwQAAAMEAAAABAAAgQAAAAQGAAAACAAABgAAAAAAAAAAAgAR</data>
				<key>Comment</key>
				<string>Patch HDMI-DP port HD4000 1600x900 #2</string>
			</dict>
		</array>
	</dict>
	<key>SMBIOS</key>
	<dict>
		<key>BiosReleaseDate</key>
		<string>21/03/12</string>
		<key>BiosVendor</key>
		<string>Apple Computer, Inc.</string>
		<key>BiosVersion</key>
		<string>MBP91.88Z.00D3.B00.1203211536</string>
		<key>Board-ID</key>
		<string>Mac-</string>
		<key>BoardManufacturer</key>
		<string>Apple Computer, Inc.</string>
		<key>BoardType</key>
		<integer>10</integer>
		<key>ChassisAssetTag</key>
		<string>MacBook-Aluminum</string>
		<key>ChassisManufacturer</key>
		<string>Apple Computer, Inc.</string>
		<key>ChassisType</key>
		<integer>8</integer>
		<key>Family</key>
		<string>MacBook Pro</string>
		<key>Manufacturer</key>
		<string>Apple Computer, Inc.</string>
		<key>Mobile</key>
		<true/>
		<key>ProductName</key>
		<string>MacBookPro9,2</string>
		<key>SerialNumber</key>
		<string></string>
		<key>Trust</key>
		<false/>
		<key>Version</key>
		<string>1.0</string>
	</dict>
	<key>SystemParameters</key>
	<dict>
		<key>InjectKexts</key>
		<string>Yes</string>
		<key>BacklightLevel</key>
		<string>0x0101</string>
	</dict>
</dict>
</plist>

SSDT (Generated by ssdtPRGen)

ssdt.aml.zip

 

 

 

DSDT (un-patched, dumped by Clover (F4))

DSDT.aml.dump.zip

 

 

 

DSDT (autopatched by Clover)

DSDT.clover.autopatched.dsl.zip)

Share this post


Link to post
Share on other sites

Have you tried patching your DSDT yet? Are you using a Samsung SSD with TRIM? Usually the HWMonitor app requires a few DSDT edits before it starts working right. Sometimes you get lucky and everything works, but I always have to patch something... Moreover, make sure that the S.M.A.R.T. hard drive reporting is functioning properly.

 

 

This is my DSDT patch for the SATA on a Latitude E6400 XFR... This patch adds MacBookPro 5,1 ACHI variables and injects a device id for ICH-10 chipset.

            Device (SATA)
            {
                Name (_ADR, 0x001F0002)  // _ADR: Address
                
                Method (_STA, 0, NotSerialized)  // _STA: Status
                {
                    Return (0x0F)
                }
                
                Name (PRIT, 0x00) // MacBookPro 5,1 DSDT SATA device variables
                Name (SECT, 0x00)
                Name (PSIT, 0x00)
                Name (SSIT, 0x00)
                Name (SYNC, 0x00)
                Name (SDT0, 0x00)
                Name (SDT1, 0x00)
                Name (STD2, 0x00)
                Name (SDT3, 0x00)
                Name (ICR0, 0x00)
                Name (ICR1, 0x00)
                Name (ICR2, 0x00)
                Name (ICR3, 0x00)
                Name (ICR4, 0x00)
                Name (ICR5, 0x00)
                Name (MAPV, 0x00)


                Device (PRT0)
                {
                    Name (_ADR, 0x00)  // _ADR: Address
                    Method (_STA, 0, NotSerialized)  // _STA: Status
                    {
                        Return (0x0F)
                    }
                }


                Device (PRT1)
                {
                    Name (_ADR, 0x01)  // _ADR: Address
                    Method (_STA, 0, NotSerialized)  // _STA: Status
                    {
                        Return (0x0F)
                    }


                    Device (MAST) // This device notifies the OS that it's a hot pluggable ESATA port...
                    {
                        Name (_ADR, 0x00)  // _ADR: Address
                        Name (_RMV, 0x00)  // _RMV: Removal Status

                        Method (_EJ0, 1, NotSerialized)  // _EJx: Eject Device
                        {
                            SMI (0x90, 0x08)
                            Return (0x00)
                        }


                        Method (_STA, 0, NotSerialized)  // _STA: Status
                        {
                            Store (SMI (0x86, 0x00), Local0)
                            If (Local0)
                            {
                                Return (0x0F)
                            }


                            Return (0x00)
                        }
                    }
                }


                Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                {
                    Store (Package (0x04)
                        {
                            "device-id", 
                            Buffer (0x04)
                            {
                                 0x22, 0x3A, 0x00, 0x00 // Spoofed ICH-10 device id to boot os with native drivers...
                                                        // Can also be spoofed using Clover EFI...
                            }, 


                            "device_type", 
                            Buffer (0x10)
                            {
                                "AHCI Controller"
                            }
                        }, Local0)
                    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
                    Return (Local0)
                }
            }

Here's also a link to a RampageDev thread on hot plug SATA patches: https://rampagedev.wordpress.com/more-guides/hot-plugging-to-your-sata-ports/

 

Some Dell Latitude laptops can have 2 Flash Cache Modules / mSATA cards that can be installed in place of the WWAN or WPAN slots. Usually ports 4 and 5 are reserved for those cards even if you don't have them installed.

Share this post


Link to post
Share on other sites

You've listed NullCPUPowerManangement kext alongside FakeSMC. What's the reason for this?

 

Running nullCPUPM probably leads your CPU to run permanently at max nominal speed (3.0GHz), meaning unecessary higher energy consumption and unecessary CPU + overall system T°. You should ideally get rid of nullCPUPM and operate native SpeedStep. Your CPU will then auto adjust speed according to load, use Turbo boost speeds up to 3.7GHz (which aren't probably available right now) and this would ensure a much more efficient operation of the computer. You've already got the generated SSDT, so all should be Ok to run native SpeedStep...

Share this post


Link to post
Share on other sites

Thanks for the Reply!
 
I'm using NullCPUPowerManangement because I can't get the system to boot without it. However, Intel Power Management and Speed Step are both working fine (as you will see from the screen shot below).
 
Intel Power Gadget Screen Shot:
Intel-Power-Gadget-Dell-E6430.png

Share this post


Link to post
Share on other sites

Have you tried patching your DSDT yet? Are you using a Samsung SSD with TRIM? Usually the HWMonitor app requires a few DSDT edits before it starts working right. Sometimes you get lucky and everything works, but I always have to patch something... Moreover, make sure that the S.M.A.R.T. hard drive reporting is functioning properly.

 

This is my DSDT patch for the SATA on a Latitude E6400 XFR... This patch adds MacBookPro 5,1 ACHI variables and injects a device id for ICH-10 chipset.

 

...

 

Here's also a link to a RampageDev thread on hot plug SATA patches: https://rampagedev.wordpress.com/more-guides/hot-plugging-to-your-sata-ports/

 

Some Dell Latitude laptops can have 2 Flash Cache Modules / mSATA cards that can be installed in place of the WWAN or WPAN slots. Usually ports 4 and 5 are reserved for those cards even if you don't have them installed.

Thanks for the reply!

 

The only DSDT patching I've done is via Clover. As I've said before, sadly, I don't really understand the code in an aml file. I've never been able to successfully patch a DSDT with MaciASL. I can never get it to compile without errors. :(

 

I'm trying to learn, but something hasn't quite clicked within my understanding so I can grasp it.

 

As I listed in my first post, I am using a Seagate ST95005620AS Hard Drive. It is a 7200 RPM SSD Hybrid drive (500GB with 4GB SSD). TRIM is not enabled because from everything I've read, it's not necessary for this drive. The drive is a standard 2.5" hard drive, and is installed in the primary (only) hard drive slot.

 

Thanks for your links, and the code from your DSDT, I'll take a look and see if I can incorporate it somehow. :)

Share this post


Link to post
Share on other sites

Same thing on the E6410, Primary HDD overheats, where as my HDD on the Caddy doesnt.

 

Clover user as well...

Thanks for the Reply!

 

Any chance you can include your system specifications, Clover config.plist, and what "extra" kexts you are using?

 

Thanks!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...