1. Install Mac Os On Dell Xps 15z

. Specification Details of the system: Please keep the discussion as close to El Capitan as possible.Sadly, due to my lack of time I couldn’t keep up with the changes and improvements found in the wealth of the thread to this guide. With Sierra out and the recent introduction of MBP’s nearly identical to this 2015 device (ah Apple, so sad) (minus our better discrete GPU) a Sierra guide will be done – but by someone more capable. I will update this guide with the latest changes to finalize it once the Sierra guide is out and I can incorporate the lessons learned since writing this up. In order to boot the Clover from the USB, you should visit your BIOS settings: – “VT-d” (virtualization for directed i/o) should be disabled if possible (the config.plist includes dart=0 in case you can’t do this) – “DEP” (data execution prevention) should be enabled for OS X – “secure boot ” should be disabled – “legacy boot” optional – “CSM” (compatibility support module) enabled or disabled (varies) – “boot from USB” or “boot from external” enabledNote: If you get a “garbled” screen when booting the installer in UEFI mode, enable legacy boot and/or CSM in BIOS (but still boot UEFI).

Enabling legacy boot/CSM generally tends to clear that problem. In my case I left VT-d and Fastboot as they were. Also, update your 9550 to the latest BIOS.

Don’t forget to set mode to “AHCI” in the sub-menu “SATA Operation” of “System Configuration”. It’s mandatory. (Old) Warning for 4k / UHD screen owners: Do not use the EFI shell to to edit the DVMT Pre-allocation for getting your screen to work. This bricked a user’s machine already. Instead, make use of a patch explained in a later section of this guide. All you need to do is follow the instruction in this guide.

If you do not know about DVMT Pre-allocation, do not worry. You not need it. So in short: Do not use UEFI shell to edit DVMT allocation. 1.2 Prepare the USB Simply follow rehabman’s install guide referenced earlier for a USB install.

For this you need a real Mac or a Hack with access to the Apple Store for downloading 10.11.4 or newer – =.4 is necessary for initial Skylake Support. If you download freshly from the Apple Store, you’ll get 10.11.5 or newer During the preparation of the USB install it’s best to go for a fail-safe clover configuration. A streamlined, all patches active configuration comes after your system said Hello world and is ready for usage. In short, please use this by rehabman for the initial setup on your USB stick. This plist includes important patches, some of which we’ll activate after the initial installation. In this plist you need to adjust a couple of things: Into “Devices” section.

0x19160000 The rest of the config.plist can stay as rehabman pre-configured it. Please don’t make too many edits to your config.plist before finalising your install.

1.3 Kernel Extensions for Install You may need extra kexts, apart from the mandatory FakeSMC and VoodooPS2 (as per rehabman’s install guide):. HackrNVMeFamily-10116.kext – for seeing and installing on a stock SSD if you have a M2 NVMe SDD! It’s attached to this guide and valid for 10.11.6 – see below in 3.7 if you are installing an earlier or later version of MacOS. Recommended escalation of getting your drive to cooperate:.

Use the HackrNVMeFamily kext. If the Installer doesn’t see your SSD with this kext, then it might be missing the patches for your device. In this case you have to use for install. Please report if you have to do so, maybe your drive can be “hacked” post-install. Of course, delete HackrNVMeFamily. Should you still face problems, see this.

Please refrain from using other kexts during install. Go with a bare minimum. All you want is to get the system on your Laptop and boot. Please see 3.7 of the post install section to update the included HackrNVMeFamily-10116.kext to newer OS versions or even Sierra 2.

Installation Installation is pretty much 100% in alignment with rehabman’s guide Just make sure, again, to follow the I split up the drive into two partitions to prepare the second one for Windows later. So I left the second one just untouched by formatting it HFS+ which was later overwritten by the Windows 10 install routines. But that is just if you also want to use the silenced beast that is the GTX 960M for gaming outside of serious Mac business. How to get MacOS booting again after installing Windows: When installing Windows after having installed Clover, it will install its own bootloader into your EFI partition.

To get back to boot macOS, you need to have the USB key from the install handy, so you can add Clover’s UEFI boot entries. So don’t panic.

Post install After your install went smooth and you installed Clover to your SSD as per guide, it’s time for the real work. It’s also a good idea to keep the USB stick handy and not fiddle with it’s config.

It was good enough for a install, it’s good enough to start your machine with and fix the errors your.dsl patching and config.plist adjustments brought along. 3.1 DSDT/SSDT Patching Patching DSDTs and SSDTs will enable the following:. Turn off the NVIDIA GPU for OS X – this is a must – it saves a lot of battery and the discrete GPU won’t be utilized by MacOS anyway.

Backlight control, important for proper sleep and resume. Fn keys for Backlight control via Fn keys. Audio, see below for the special section pertaining how to enable our codec rehabman, again, provides all info needed for patching these files. His master is a “ must be open at all time” 3.1.1 Extract When in the Clover boot menu, press F4 to extract vanilla DSDT and SSDTs from the system and save them in your Clover ACPI folder. These files shall be the base for all the patching following. 3.1.2 Prepare For all DSDTs and SSDTs, please remove or rename. The preparation work is done, let’s patch!

For starters, you can check the DSDT and SSDTs attached in the archive. But you should extract yourself and patch yourself. Who knows what Firmware and Bios is driving your 9550. The first patch you should apply to your DSDT is “Rename DSM methods to XDSM” – then continue. Rehabman’s guide also gives hints at usually good and unproblematic patches. Try it yourself – rather don’t patch too much, try to boot and see if you get the desired effect after every patch.

3.2.1 Backlight control for backlight control. All you need is the “OS Check Fix (Windows 8)” and a kext, see below. In addition to this, you need to follow for adjusting your DSDT for getting our dedicated brightness keys to work. One of the following patches need to be added to your DSDT via MaciASL’s patch window: For VoodoPS2Trackpad. End; I opted for ApplePS2SmartTouchPad.kext – I found it to offer better Palm rejection while also supporting more gestures.

Version 4.x works just fine. Retain brightness value upon resume from sleep and benefit from super fine brightness steps This is courtesy of:. If installed, remove ‘IntelBacklight.kext’ from S/L/E.

If patched, remove brightness fixes from DSDT. Remove the existing PNLF device from the DSDT.

Compile and install the SSDT from post to the ‘PATCHED’ folder of your Clover installation – add it to your named list of SSDTs in config.plist, if you are using a named list. Create a ‘AppleBacklightInjector’ kext as mentioned in the post above and install it in S/L/E. Rebuild kextcache. Sudo kextcache - system - caches 3.2.2 Turn off NVIDIA This video plus rehabman’s helped me. I patched most of the SSDTs and the DSDT, but this may not be necessary: patched mostly the DSDT only and turnf the discrete GPU off as well. His method is in 3.2.3 Rename iGPU There are patches and a by rehabman Most essential for me to get it working were:.

“Rename GFX0 to IGPU”. “Cleanup/Fix Errors (SSDT)” But it always depends on your SSDTs. Just be sure to follow the guide, especially making sure you treat every SSDT with the rename. 3.3 SSDT.aml via pikeralpha Needed for native Power Management. Please refer, to once again, a great by rehabman. You have to chose between this method for power management and the new fancy Speed Shift method mentioned below. Speed Shift ignores SSDT and OS-level settings.

Obviously, you must find your own Serial No. – If you take the SMBIOS posted here and simply copy and paste them, they WILL not work 3.6 Full QE/CI, 4k and fix memory allocation Thanks to 10.11.4+ this is super simple. Just take out the Fake-ID and ensure you kept the InjectedID as in the beginning of the guide. If you employ the Backlight Fix and IntelBacklight.kext – which you should – you’ll have a super smooth boot-up experience, too. Additional steps for 4k / UHD screens: If you have a 4k screen, you must make two additional changes, courtesy of the by “the-darkvoid” for the Dell 9350 and rehabman: Open a Terminal and run these commands. Sudo codesign - f - s - / System / Library / Frameworks / IOKit.

Framework / Versions / Current / IOKit Only after these changes will 4k work. Which you want, if you paid $$$ for 100% AdobeRGB 3.7 iMessage, App Store, iCloud etc. For proper functionality you need to generate MLB and SMUUID. As usually, the guide from rehabman covers that in depth. I was successful with the following steps:. Generate a proper Serial No not in use yet by others.

Either through Clover configurator for supported System and its SMBIOS generator, or by. Make sure you don’t have a MLB or SmUUID value set. You can take the Board-ID and Bios from the examples in this guide for the system definitions provided. Reboot after setting Serial number, Board-ID and Bios. Use Clover Configurator’s Rt variable generator for getting the MLB, SmUUID value. ROM is usually set correctly automatically.

Save the details given by the configurator into SMBIOS fields. Reboot and try iCloud, Message etc. I also found that the aforementioned NullEthernet.kext enables a reliable connection to these services. Please follow the instructions when installing. As explained by rehabman, you also need to place ssdt-rmne.ssdt with a custom MAC address and edit the ssdt into your config.plist For advanced help, please see this 3.8 Audio Since I last wrote about Audio, things have improved a lot.

No more Voodoo, now let’s patch native via injection, yeah. You need two kexts and the SSDT-ALC298.aml attached to this post. Place and into your Clover kexts folder. Place the afromentioned ALC298.aml int your ACPI/patched folder – don’t forget to adjust your config.plist if you use a named SSDT list.

Inject Audio ID 13 via config.plist If you previously committed Audio patches, like injecting Audio ID through DSDT or even renaming the Audio device (I did that, thus finding the device was a bit harder), then you need to adjust the Audio ID in your DSDT as well. End; 3.9 Speed Shift Skylake brings a new, fancy method of managing your C- and P-States of your CPU called Speed Shift. This means quicker throttling up and down, can mean higher power or longer battery, depending on your needs. Bare in Mind, this is a pretty new development in the Hackintosh world, so use this as an alternative to generating states via the guide linked in 3.4. If you are interested (I’m happily using it, it keeps the fan on lower settings), there are two ways: 1. Enable HWP in Clover.

– My changes for HWP support in Clover are already in repo and will be included into next build – Fully rewrote my kext. I like it now! You can got it here – Normal support of HWP needs not only CPU configuration, but also frequencyVectors with HWP flag.

Currently in El Capitan this is only MacBook9,1. So who want to have best possible CPU performance with incredible battery life – change your smbios to MacBook9,1. Also, for those who has generated ssdt.aml – delete it and forget, we don’t need it anymore bcz HWP will handle all power management! Yarrr Yes, change your SMBIOS to MacBook9,1 – with Sierra this could be MacBookPro13,1 as well, we’ll have to see.

Keep Speed Shift after sleep To retain Speed Shift after resume from sleep, you need to follow a few simple steps outlined in post. Otherwise, Speed Shift won’t work after your system slept. Kinda pointless, so follow the simple steps. Remember: It’s either Speed Shift or SSDT.aml patching via Pike R.

Alpha for Power Management, not both. 3.10 Native NVMe In the pasts months the Hackintosh world has evolved even further, also again thanks to the work of the likes of rehabman and pikeralpha. A new method has been found to directly patch NVMe kexts by Apple to avoid NVMeGeneric. Mkdir /Projects && cd Projects git clone patch-nvme.git cd patch-nvme.git./patchnvme.sh 10116 This will yield in a kext you can install or add to your Clover kexts.

Install Mac Os On Dell Xps 15z

This method could also be used to create a kext for NVMe patching before updating to 10.12 – you need to adjust the target platform in the command line accordingly. Updating 4.1 10.11.6 & Security updates Updating to 10.11.6 worked for me via the App Store (see 3.3.6 for getting the App Store to work). Here’s the steps I took:. Make sure that the App Store is working by providing a proper SMBIOS. Download the Update and let it install itself, it will reboot when it’s done to the Clover boot menu. With FHD, you’re done at this point, apart from re-patching or re-installing kexts in S/L/E Additional steps for 4k/UHD. After the initial installation restart, don’t boot directly boot OS X, instead enter Clover Options during OS selection after boot.

In the Clover boot menu, open the “Graphics injector menu” and inject a fake ID for the Intel IGPU, much like during install, for example. # Run the following command in order to patch IOKit in order to disable CheckTimingWithRange sudo perl -i.bak -pe ‘s xB8x01x00x00x00xF6xC1x01x0Fx85 x33xC0x90x90x90x90x90x90x90xE9 sg’ /System/Library/Frameworks/IOKit.framework/Versions/Current/IOKit sudo codesign -f -s – /System/Library/Frameworks/IOKit.framework/Versions/Current/IOKit. After patching, simply reboot and you’re golden – you may need to reinstall.kexts or kext patches depending on your setup ToDo I probably forgot important things, so this guide will be updated accordingly. AppleHDA patching instead of Voodoo Audio.

Hopefully better palm rejection for the Touchpad – solved by an alternative TouchPad driver. Replacing NVMeGeneric with a more stable method Repo A git of the current kexts, cofnigs & ACPI files I use can be found.

As always, be careful when using ACPI files from other systems. Files attached All the files attached are tuned to i7 systems. You need to adjust the injected ID pertaining your CPU (see above for details) as well as decide on using NVMeGeneric.

Clover.zip: This zip file provided should only be a starting point to discover how a complete system is configured. It’s based on my running i7 setup – It’s not a good idea to deliver a running setup, as it maybe not up to date and not optimized for your system. Instead, use this guide and rich thread to create your streamlined, optimized setup. Everything you need is there. Minimalforinstallexample.zip: This is the actually setup I used when installing the system.

It’s minimal, without many kexts and config.plist edits SSDT-ALC298.aml: The verb to be used in combination with CodecCommander and AppleALC to relish native audio support HackrNVMeFamily-10116.kext – Required to install and use MacOS on 9550s fitted with NVMe M.2 drives Display #1 2016-11-13 14-13 2.2 F-S XYZLUT+MTX – ICC profile for 4k screen calibrated with Spyder4Pro colorimeter and DisplayCAL. Every panel is different, so don’t expect too much precision, but this profile works great for sRGB and AdobeRGB dellxps15icon.png – An icon to brand your Desktop Apply with LiteIcon or manually Please take care when using files contained, especially ACPI related ones./size Source: Download attachments here.

Okay I have found another issue that I hope I can help everyone else with should they have the same issue. VIDEO SOON Ahhh A New Laptop At work we got in these beautiful new Dell XPS 14 Laptops, Dell has finally started to make some nice machines when they came out with the XPS line-up. We have had a lot of people in house comment that they thought it was a Mac Book Pro or Mack Book Air. These new XPS 14 laptops come with a new technology built on board called “Intel Responsiveness Technology” or IRT for short.

The point of this technology is to make your system faster by using a small independent mSATA Solid State Drive or a slice of a larger SATA SSD. There are 3 different technologies that apply here:. Intel Smart Response Technology (ISRT) – Smart Response is a feature that uses both a traditional hard disk drive (HDD) and a solid state drive (SSD) of greater than 32GB together.

It dynamically monitors file, data, and application use, and stores frequently used content on a special partition on the SSD device for faster access. It provides SSD-like read/write performance for the files used most frequently, while providing lower overall storage cost by sorting and storing less frequently accessed content on the larger-sized traditional HDD. Intel Rapid Start Technology (IRST)– Rapid Start is a feature that provides power savings similar to Windows hibernate state, while improving resume time vs.

Hibernate by 2x. Rapid Start may be combined with Smart Response on some systems to enhance overall system performance while also reducing power consumption when not in use. Intel Smart Connect Technology (ISCT) – Smart Connect is a feature that periodically wakes the system from the Windows sleep state to refresh email or social networking applications. When the system is equipped with specific wireless devices, it can detect the presence of known networks while asleep, waking only when connectivity is available (this feature is called Net Detect). When properly equipped with specific wireless devices, Smart Connect can also provide quick internet connection readiness by keeping wireless devices active in a low-power mode during sleep (this feature is called Quick Connect). Smart Connect may be combined with Rapid Start on some systems to help reduce power consumption while still keeping email and other application data current.

I have had some really bad luck here at work with my XPS14 Laptops. I thought that IRST was the issue so i built a brand new Windows 8 machine with a SSD and removed the 32 GB mSATA card. I returned the system to regular BIOS mode. I can get Windows to stay stable until it falls asleep on its own (meaning I didn’t close the lid or force it to sleep) if I wake it up I get the Blue Screen Unhappy Face. It only happens after I do the updates waiting for windows after the install.

Very strange!! I am still playing around with it! Till i figure out this issue there is no IRST for us!!! HiI just reinstall the windows.I tried hard to follow the instruction from the help desk of DellI tried every way to setupbut it always show error after I installed the Intel Rapid Storage driver.I have to restore to the image file I made earlier.I nearly gave up to use the latest technology.I actually buy this labtop due to those high technology.I donno why now I disabled it I setup the Smart Response as the SATA operation modeand no drive detected in the partition page of window installation.

And Dell ppl asked me to install the driver of IRST but I failed again and the error said my driver is not certified. Crazy.I downloaded both from dell and inteland all failed. I install the windows for 5 times alreadybut it seems not really helpful.I read many many webpages as you did.but no one really can help me I try to use your solution to set up!! This is a tricky one that most people have issues with. In a normal computer your OS can talk directly to your hard drives through the motherboard. This makes the computer very easy to setup and use.

In the case of when you set your BIOS to be Smart Response you are turning on a RAID controller now. What you have now is the OS has to talk to the RAID controller then it talks to the hard drive. Nakamichi ca-5 service manual. You have more or less put an extra step in the middle before you can talk to the dive. This is great because it give us unlimited options for redundant disks, caching of data so we make sure its written to disk even in a power failure, etc. Problem is Windows has no idea how to talk to about 90% of these RAID controllers.

Every company does something a little different so it makes it difficult for Windows to make “Standard Drivers or Generic Drivers” for them. So what manufacturer of RAID controllers do is provide a driver for their controller so that Windows knows how to talk to the RAID controller perfectly. When you install Windows and you do not see one or more of your drives listed it is normally because the OS does not have the proper driver to talk to the RAID controller to see the drives. Windows now makes it a lot easier to install the drivers for RAID controllers compared to Windows XP where you were forced to use a floppy or embed them in the CD image. When you get to the point of the Windows installer where it asks you for a location to install Windows, you might see your 32 GB or 64 GB SSD but not your large hard drive. This is because the OS needs the driver to see the hard drives that are run by the RAID controller (see my attached picture) You will need to find the drivers for your model (every model is different) if you cannot find it let me know your manufacture and model of laptop and I can help you find it. Once the drivers are installed you will see your drive listed and you can do what you want with it before you install Windows like deleting all the partitions etc.

I went to a single drive setup and deleted all partitions and created just one large C drive (keep in mind if you are using BIOS or UEFI Windows may create a few extra partitions to support it) Please let me know if you need any help. Yes this will for sure work with a XPS14 as that is what I use from Dell.

As for installing the OS when using IRST mode for SATA this is correct you won’t be able to see the drive. This is expected! Have a look at the comment I made to Trevin.

I explain that you will need drivers so that the Windows installer will see your drive behind the IRST card, you can get these from the dell drivers site for your machine. You will have to do some digging but they are there in one of the Intel downloads. You can then save those files to a flash drive ans use it during the Windows install when it comes to that screen where it cannot see your drive. Let me know if that clears it up. Depending on if you are installing an image you won’t need this but if you are installing from scratch you will need this to see the drive to install Windows. If you use AHCI to install and then you turn on IRST mode it will just blue screen because the OS does not know how to talk to the drive. It’s kind of like enrolling in an English school and on the first day every one start talking Spanish you will Blue Screen:).

I’m only interested in Smart Response, have tried everything from different sites, including all the steps here, and still this stupid software will not give me the option to do anything. No Performance option, no Create RAID option.

I was not able to shrink my C: partition (last partition on drive) by more than 80MB due to fragmentation (have 60GB free). So instead I extended the volume by 1GB since I had free space at the end of the disk. Still didn’t work. I went back and shrank the volume by 1GB.

Still didn’t work. Tearing my hair out for over 10 hours trying everything! This was one of the most comprehensive tutorials setting up Rapid Response Technology that I’ve been able to find.

Unfortunately it didn’t seem to fix my problem. I had the caching working before my computer crashed. After reformatting, the performance tab is present, but only shows link power management. I’ve tried resizing the OS drive, using diskpart to clean the SSD and left it unallocated (tried both GPT and MBR on SSD). My HDD is UEFI.

The BIOS has RAID setting for SATA. In the manage tab both drives show Usage: Available and Disk Data Cache: Enabled.

Not sure what else to do, any help would be appreciated. Okay going to go out on a guess here that I remember reading somewhere but cant find it now, I don’t think IRST support above 32 GB SSD for acceleration. I think the reason is because your OS can install on 64 GB so why not use the SSD. I could be wrong but can you try setting up your SSD smaller then 32 GB just to see if that makes the option change on the top row of buttons. I know Intel does a check to see if you meet all the requirements before giving you this option. So to test initialize your SSD and only make it 30 GB (30720 MB). I am using 30 so that it for sure is below 32 GB mark.

Let me know the outcome.