Jump to content

OSX on DELL Vostro 3450 / Inspiron N4110 / XPS L702x UEFI Clover

1,149 posts in this topic

Recommended Posts

i can see from debug log, PCH die temp is higher than other, maybe i need a cooling mod. And, when windows 8.1 is out, dell doesn't release the video driver which means it gives up support 14R, fool sh..t. 

I try someone's catalyst driver, works well but brightness doesn't match the right one. so i think i should stay away with windows.

Share this post

Link to post
Share on other sites

Yeah, PCH is hotter because DELL uses just a silicon thermal pad on it to make contact with the heatsink.

For me even if I leave the laptop completely idle CPU die can be as low as 39C, while PCH die will be 46C.. and they share same heatsink/heatpipe assembly..

On AMD SG models of both 14R and 3450 the heatsink is massive if you compare it to intel models .. and yet the tems are high for chipset..


We are at least lucky to have a heatink on it, 3360 and 3560 (newer generation ivy bridge vostro) have PCH underneath the keyboard just above the touchpad and there's no heatsink on it.. it gets to 60C even if you type in word and fan runs most of the time to cool it down, while it can't actually cool anything down .. becase again, no heatsink. Dell kept the firmware in EC to behave same as on our generation of laptops - if either CPU or PCH get to 57C - enable fan. But since there's no heatsink on PCH these laptops are f*cked to be hot and noisy.

Share this post

Link to post
Share on other sites

I know this may be unrelated to this thread, but I presume most of us are multi-booting.

I've taken another project as a base to start my own thing (consider  this an alpha?)... currently fan control has been made possible.. Anyone care to try fan override for windows?


It will publish GPU temps for AMD models as well. See readme for configuration details. 



Share this post

Link to post
Share on other sites

I tested it but it seen like doesnt control fan because between range of safe temp to trip (52-62) the steady speed sometime stay below 2950 and sometime doesnt.





Share this post

Link to post
Share on other sites

Its not setting custom speed, its not possible on any dell laptop. It catches or should I say tries to catch the fan at the speed that you've pit in the config file. Manual control sometimes resets by EC, hence the fan may unstick, but it will revert to a steady sped when there's an opportunity.

Share this post

Link to post
Share on other sites

I have further noticed that the more you read from EC the more garbage information appears there for no reason. I guess this memory space is just too sensitive.. 

I'm now reading the following http://puu.sh/6VRAs.png and it constantly reads gpu temps, chipset temps, cpu temps as 100, fan speeds as 16k rpm etc.. at one point my battery said "no battery installed" even though all the data about it was in ec and it was obviously installed. on second iteration i lost power adapter .. i guess just the fan control would be enough for those who need it .. 

Share this post

Link to post
Share on other sites

this is my testing, and temp is lower than OS X, it causes i use Audible mode. gonna wait for your more mod. BTW, test under windows 8.1.


Share this post

Link to post
Share on other sites

I've done some crucial changes to the slim app. the notifyicon text can hold only 64 characters, so it's not much we can utilize- don't go with  profile names.. been looking at baloontips (which can update when you have them show up), but they are ugly.


1. config changed, now each setting is a separate entry. no more legacy point entries.

2. some crucial checks for when the fan is not controlled by bios. if fan has locked at a greater speed than requested - give bios control back. if fan speed is 0 and 0 is not requested per profile's config - give bios control back

3. because of changes in 2 I made the fan speed bar colorize depending on the mode. if fan has locked the speed bar will be white, if bios still controls the fan it will be green. if passive mode is used the notifyicon text will say that "Mode: Locked" if fan was locked in off state because there's no bar to report this.

4. if gpu temp is found to be 0 then never again should the program read gpu temp from 0x56 register, because it will produce garbage if done otherwise

5. added possibility to specify -delay XX in the app shortcut to delay the start of the application, since the port driver takes some time to start (with SSD anyway).

I will push the code later at some point. (setting in your shortcut IT8518E-SCT-FC.exe" -delay 15 will delay the app start for 15 second)


6WQKG.png 6WQLp.png



I've done some changes to OSX ACPI tables for fan control .. the one thing that you need is _PTS patch to reset TCTL bit after every power state transition. Also, I should implement additional checks from (2) into the acpi table as well. but you can use it none the less at its current state.  https://github.com/Dolnor/Vostro-3450-Fan-Override (the alt one is the one that locks the fan at 3000rpm, you can change the value if you want). Basically you replace the PollDevc table with this one, all the configuration is done inside this table. Then you just edit the ACPISensors plist for ACPIProbe to math the name PLL0000 and not POLL0000. Then it should work in the same manner as the windows app does (except the checks i've mentioned).



Share this post

Link to post
Share on other sites

thx for great job. just test under windows, works well, but seems dell quits win8.1, so i use os x more than windows. 


For alt-ssdt test, i found there are two methods named  "XCNT", "OSYS" under "Platform Profile" of "ACPI Debugging Plugin", so i get :


2/15/14 6:21:15.000 PM kernel[0]: ACPIProbe (PLLD): [Error] unable to register method "XCNT"

2/15/14 6:21:15.000 PM kernel[0]: ACPIProbe (PLLD): [Error] unable to register method "OSYS"

But i correct "TAVG","TCTL" instead. then get.... it works.


2/15/14 6:36:12.000 PM kernel[0]: ACPIProbe (PLLD): method "TAVG" registered

2/15/14 6:36:12.000 PM kernel[0]: ACPIProbe (PLLD): method "FCTL" registered
2/15/14 6:36:12.000 PM kernel[0]: ACPIProbe (PLLD): TAVG = 57
2/15/14 6:36:12.000 PM kernel[0]: ACPIProbe (PLLD): FCTL = 1
2/15/14 6:36:13.000 PM kernel[0]: ACPIProbe (PLLD): TAVG = 57
2/15/14 6:36:13.000 PM kernel[0]: ACPIProbe (PLLD): FCTL = 1
2/15/14 6:36:15.000 PM kernel[0]: ACPIProbe (PLLD): TAVG = 58
2/15/14 6:36:15.000 PM kernel[0]: ACPIProbe (PLLD): FCTL = 1

Share this post

Link to post
Share on other sites

There you go .. the behavior coded in is the same as "Audible" profile under Windows.

I will update the "Passive" profile's analog and push this to git when I have time. 

HWMonitor application has been patched to include monitoring for fan control mode. As expected - it's either auto or steady.





mirror: https://www.dropbox.com/s/t69jtriziymbtih/osx-fan-control.zip

Share this post

Link to post
Share on other sites

wow, wonderful, this is what i expect thing when i join hackintosh world. BTW, tw can u upload it to a cloud site? cause download speed is sucks. 




works now. thanks a lot. 


Share this post

Link to post
Share on other sites

Thanks for testing both of the apps. The behavior in OSX is more stable because it directly reads from ACPI and writes by means of ACPI too, while in Windows it requires third party driver to access EC port.. and this driver sometimes writes rubbish data into EC memory space.


I will see if I can persuade @kozlek to implement profile switching for acpi probe. 

As in, you could have a set of profiles defined in SSDT. Each profile should have a INVL value defining the update interval in ms and a set of method names that should be polled based on that profile. Then it would be cool to have a button somewhere in HWMonitor's GUI which would report all the parsed profiles from SSDT table and would actually let you chose the profile you want. This will allow to have multiple fan control profiles and profiles for debugging certain things in ACPI tables.


P.S. Pushed acpi tables (with comments) and binaries (with HWMonitor patch) to my git.

Share this post

Link to post
Share on other sites



I'm getting the following error message when I type 


bcfg boot add 3 fs3:\EFI\CLOVER\CLOVERX64.efi "Clover"


bcfg is not recognized as an internal or extenal command, operable program , or batch file


My hard disk is fs0 fs1 fs2, while usb drive is fs3


Any suggestions how to resolve?



Share this post

Link to post
Share on other sites

You are using wrong shell binary that has no bcfg support. The shell you are supposed to use is hidden and will appear when you press F3 in GUI. The stock clover shell binary doesn't know bcfg.


Also, don't add clover from USB drive to bcfg, there's no point in doing that. This part is for adding boot entry that points to efi system partition.


Share this post

Link to post
Share on other sites

1. Flashing a UEFI-capable modified BIOS

BIOS images are meant only for Dell Vostro 3450 and Inspiron 14R (both Intel model and AMD Switchable Graphics models) and no other! Vostro 3350 and 3550 use Inyde H2O BIOS, not SecureCore Tiano!

These models use Ami Aptio.

Share this post

Link to post
Share on other sites

I guess I stand corrected, I was under the assumption it was insyde. I guess I had it mixed up with some newer gen Vostros then... If even that. Does Dell even use Insyde yet? Or they are still paying premium for SCT and Aptio which both become sh+t after going through Dell's OEM customizations.


Share this post

Link to post
Share on other sites

Great! it working fine, now we know when is controlling by bios, very nice feature. can you set up a red flag on the number when goes over 68 or 70?




Share this post

Link to post
Share on other sites

The notifyicon text is rendered all together, so I can't set the color to individual part of it. The notifyicon icon is rendered from a font resource. The font color is plain white, so for it to turn red I'd need to recolor the font and add a secondary resource file. I suppose I could do that, but would it make a dramatic difference? Chances of it exceeding 70C when you are seeing your task bar are slim.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Simon's InsaneMac
      Hi, I'm kind of lost when scrolling to Clover Configurator, so I decided to use an EFI from the web and just configure the most basic stuff. But that sadly didn't work, im always getting the attached screen IMG_0054.HEIC (and I don't know whether all the errors are listed, as I can't scroll). 
      Anyways I thought it'd be better to do a custom setup. Can anyone give me some help with what to choose in the settings? Here's my rig:
      i7 8700k
      Asus z370-G (Rog Strix)
      gtx 1060 6gb
      samsung ssd (SATA)
      WD hard drive
      Your help would be much appreciated!
    • By kylon
      A big thanks to wegface for teaching me a lot of things.
      Tested on Catalina 10.15.4 and Clover EFI 5104 (Catalina Patcher)
      Not Working:
      - realtek sd card reader (pm me if you have a fix)
      **CPU patches are disabled, if you are using a locked BIOS you must enable them**
      Clover EFI:
      - Install it in UEFI Mode and change your hdd partition table to GPT.
      - You will be able to install ANY OS in EFI mode, even if this pc does not support EFI at all! (No guide available for this)
      You will need:
      My unlocked BIOS (OPTIONAL) (here) Latest Clover config from CCE Bank (here) (asus k53sj-kylon) Rehabman Voodoo PS2 Controller (here) acidanthera AppleALC (here) acidanthera Lilu (here) acidanthera VirtualSMC (here) acidanthera SMCBatteryManager (here) acidanthera SMCLightSensor (here) acidanthera WhateverGreen (here) Mieze Realtek RTL8111 (here)
    • By Rohan20
      Opencore is running really really slow on Catalina 10.15.4. So It was running perfectly before I put the ssdt-pnlf for enabling Brightness control. it is running really slow and I verified my config with the sanity checker and its all correct. can someone please help. I am attaching my oc folder.

    • By Georgiles
      Laptop: Asus Vivobook F510UA
      CPU: Intel Core i5-8250U
      Graphic: Intel UHD 620
      Wifi: Intel Dual Band Wireless-AC 8265 (no kexts for intel wifi) :(
      Card Reader: Realtek_CardReader(RTL8411B_RTS5226_RTS5227)
      Camera: ASUS UVC HD 7.Audio: Conexant Audio CX8050
      Touchpad: ELAN1300
       by parkrypto: thank you tctien342 for the amazing guide.
      Ebayed the laptop for $290 + tax = $350
      added: 16gb RAM + existing 8GB = 24GB          Timetec Hynix IC 16GB DDR4 2400MHz PC4-19200 Non ECC Unbuffered 1.2V CL17 2Rx8 Dual Rank 260 Pin SODIMM Laptop Notebook Computer Memory Ram Module Upgrade S Series (16GB)     
      added: cheap wifi         TP-Link USB Wifi Adapter for PC N150 Wireless Network Adapter for Desktop - Nano Size Wifi Dongle Compatible with Windows 10/7/8/8.1/XP/Vista Mac OS 10.9-10.15 Linux Kernel 2.6.18-4.4.3 (TL-WN725N)     
      added: NAND 1TB Internal PC SSD https://www.amazon.com/gp/product/B073SB2MXT/ref=ppx_yo_dt_b_asin_title_o01_s01?ie=UTF8&psc=1
      Gadget Reviews upgraded too, video: https://www.youtube.com/watch?v=39EquX5PTkQ
      I just installed. Everything works fine. I'll test final cut pro, premiere pro with 4k footage and get back with you on performance. 
      For now moves like a performant Mac book pro. 
      I installed Catalina first but I could not make the Intel UHD 620 Graphics get proper QE/CI. 
      Mojave is just fine. I want to use this system for quick video editing on the go.
      Geekbench in my signature.  
      If you need any files or have any questions pls ask.

      asus f510u mojave.zip
    • By y010204025
      Disclaimer: All files of this article are from itpwd.com and rehabman ’s github.com

      After Testing:
      Graphics card: NVIDIA K1000M / K2000M / K2100M / K3000M / K3100M / K4000M / M1000M (ordinary TN1600x900 or 1920x1080), AMD W5170M / W7170M (DC2 or 4K), Intel HD4000 (ordinary TN1600x900 or 1920x1080) can be driven normally, but NVIDIA graphics card Brightness adjustment is disabled. AMD W5170m and w7170m are the best choices on 8570W and 8770W. The brightness can be adjusted normally and the graphics performance is very good. For WX7100m and WX4170m, the graphics card fans cannot be controlled, and other methods are required to control the fans. CPU: 3rd generation Intel Core i3, i5 and i7 (Ivy Bridge architecture, including all dual-core and quad-core. Celeron and Pentium are not supported), frequency conversion is normal. In general: If you have 8570W, 8770W, and hope you can get the best Hackintosh experience, it is recommended to replace the CPU with i7-3840QM / i7-3940XM, 8570W is recommended to choose W5170M, 8770W, and it is recommended to choose W7170M. In addition: If you want to have a 4K experience or perfect HIDPI, W5170m / W7170M supports 4K output, you can choose a suitable 4K screen to replace, but because 4K screens are mostly edp interface, and 8570W / 8770W motherboard is lvds interface, This requires a custom screen cable, which seems to be a difficult choice, but you can choose to do it yourself or buy it separately. In China, taobao.com is almighty and may be more suitable for you than eBay.
      EFI features:
      out of the box, the relevant hardware can be driven after the OS is installed, and it is easy to use without code operation.
      Supported models: HP EliteBook 8470p, 8570p, 8570w, 8770w (click the model for official specifications)
      Wireless network card: Recommended: BCM94360cd (requires ipex4 to ipex1,3 antenna 1300mbps), BCM94352HMB / DW1550 (2 antennas, 867mbps)
      Wireless characteristics: no white list, wireless network card with Bluetooth does not support the Bluetooth function of the wireless network card (also does not need to shield the pins), but the wireless normal use, you need the Bluetooth function to use this machine comes with Bluetooth:
      Clover version: 5103, keyboard mapping has been added Command key = Alt key, Option key = Win key
      Supported systems: macOS Mojave 10.14.6 (18G103)-macOS Catalina 10.15.x,
      Notes on known issues:
      1. The touchpad and the left and right keys under the touchpad are normal, the pointing stick and the left and right keys above the touchpad are temporarily unavailable (recommended to use the second generation of Apple Magic Trackpad)
      2. Indicator display problem (can be ignored, function is normal): Caps light is sometimes not switched in time, mute / wireless key may be yellow
      3.AMD graphics card / Intel nuclear display has supported sleep and 15 levels of brightness adjustment, NVIDIA has no
      4. If the AMD graphics card enters Huaping, refer to editing the Clover startup parameters, and add the Boot parameter radpg = 15 (the EFI file that has been configured with this parameter has been uploaded, refer to the following EFI-guided download link)
      5. Using the above NVIDIA graphics card with a normal TN screen 1600x900 or 1920x1080 can not enter the installation interface, please check whether the VBiOS of the graphics card is exclusively for HP, thank you for your test face K1000M
      6. Due to product design defects, the MSata positions of 8570w and 8770w cannot be used as boot disks, so EFI boot can only be placed on the main hard disk (turn the machine over and open the hard disk in the lower left corner of the cover, which is the main hard disk). Put on msata plate
      Hardware requirements:
      Model: 8470p, 8570p, 8570W, 8770W 1 or more, it is recommended to use another notebook for emergency Hard disk: It is recommended to choose an SSD hard disk of 240g or more. Samsung or Intel SATA hard disk is a good choice. Wireless card: BCM94352HMB, DW1550, BCM94360CD, miniPCIe slot U disk: 1 for 16g and above, another winPE emergency USB disk is recommended If you use a rescue USB flash drive, it means that you read this post carefully
      Make and install a USB flash drive:
      Get the mirror: please do it your way Making and installing a USB flash drive: macOS command line production is recommended, whether it is a real macOS model or a virtual machine (although this is not allowed to be discussed in many forums)Or you can choose to use TransMac or ether under Windows. This is not recommended, but it is simple enough for those new to Hackintosh. Make boot U disk: If you know how to put the boot into the installation U disk, unzip the EFI file and put it in the EFI partition, or you can choose a fat32 format U disk to store the EFI file separately Note: EFI is an unzipped folder, not a zip or ISO suffix file.
      BIOS settings From RehabMan
      To start, set BIOS to defaults.
      Then insure:
      UEFI boot is enabled (hybrid/with CSM for best result) secure boot is disabled disable fast boot IGPU graphics memory set to 64mb, if available disable the serial port via BIOS option, if available disable "LAN/WLAN switching", if available disable "Extended Idle Power States" if you find it under "Power Management Options" disable "Wake on LAN" and "Wake on USB" disable Firewire/IEEE 1394, if your laptop has it for Skylake and KabyLake laptop, enable "Launch Hotkeys without Fn keypress" Note: If you have a laptop with switchable graphics, leave it enabled. You can still use it on Windows, although the discrete card will be disabled when running OS X by the ACPI patches provided here. If you want to also disable it in Windows (via BIOS option), make sure you read about the DGPU option in your model specific SSDT (source is in SSDT-HACK.dsl), as in the scenario where the DGPU is disabled by BIOS, DGPU should be set to zero.
      Please modify according to the above BIOS settings: Press F9 after booting, select the boot efi to file option, which is generally the last item. Enter your boot USB disk to find the location of cloverx64.efi, select cloverx64.efi, press Enter, and enter the clover boot interface. Select the location of the install entry and press Enter. Enter the macOS interface, use the disk tool to format the partition you need to install to hfs + or apfs format, do not choose the encryption option, this will make your efforts in vain. Note: The disk must be in gpt format, and the remaining EFI space is greater than 200M, 300mb + is recommended. If it is not, please try to modify it in WindowsPE environment. This may cause you to lose the Windows system boot and disk data. Please prepare for backup.
      After formatting the partition successfully, close the disk tool and select install, you will find the partition you installed, and follow the interface prompts. When the installation reaches a certain progress, it will restart. When restarting, select F9, enter from the boot U disk, select the disk partition where you installed macOS (no longer the U disk installation), the installation will continue, and it may restart 2 ~ 3 times Every time, you need F9 to select the boot. After entering the installation interface, except for the first installation, select the U disk, and then select the disk installation partition. Eventually you will enter the settings interface. After following the interface prompts, you will enter the macOS system interface. Remember the system password and turn off the Find my mac option.  
      Post install:
      After the installation is complete, you need to hang the EFI partition of the disk, copy the EFI file of the U disk to the EFI partition of the disk, so that you can directly use the disk to boot, otherwise you need to select the U disk to boot each time. The mount tool can choose cloverconfigurator. If after copying the EFI file to the disk, the computer cannot recognize your clover boot, you can use the custom boot option of bios: set the custom boot path to \efi\clover\cloverx64.efi, and set it as the first boot, Use bootice or easyUEFI to increase the clover boot option under Windows and set it as the first boot. If you do not have a wireless network card available temporarily, you can use the USB binding function of your Android phone to share the network. This may require the HoRndis driver. It is not recommended to use a US wireless network card. If you need Windows or Linux, you can install it normally. Be careful not to let Windows overwrite your boot files.  
      For other uses of macOS and brew, please pay attention to forums and other communities. Hackintosh is just the beginning.
      Finally, I would like to thank rehabman, vit9696 and others who contributed to Hackintosh. I also thank Cwen for his efforts to modify files and hardware tests. I hope that Hackintosh will be eternal.
      Please comply with the laws and regulations of your country or region. My description may not be clear or professional, but I think it is necessary. I think the existence of Hackintosh is everyone's technical hobby and experience macOS, not as a substitute for macOS cheap hardware.

      EFI_8x70_5103_W7170m_20200116 .zip