Popular Post TimeWalker75a Posted October 28, 2013 Popular Post Share Posted October 28, 2013 This guide will discuss the process of getting OS X Mavericks or Yosemite to run on Vostro 3450 / Inspiron N4110 / XPS L702x using UEFI Clover, no other discussions please. I should start by saying that I'm not responsible for any bricks that may happen if you follow this guide and I'm not saying I will be updating this with every bit of changes I do to my personal system after every minor OSX upgrade. Though, with this kind of setup you shouldn't have to lift a finger after installing OSX updates... Also, don't mirror my files! This is your goal: I'm sure if you ended up here you probably know the majority of limitation that Phoenix SecureCore Tiano firmware applies to this system, but I'll mention them none the less:- Can't boot GPT formatted disk with legacy bootloader such as XPC, Chameleon, Chi*mera- Can't boot UEFI OS or bootloader as UEFI is locked down from the factory- Cardreader is not bootable- Secondary disk installed in place of DVD drive is not bootable either- BIOS doesn't let you disabled Turbo Boost or Hyper ThreadingSo, let's get to the point, shall we?1. Flashing a UEFI-capable modified BIOSBIOS images are meant only for Dell Vostro 3450, Inspiron N4110 and XPS L702x (both Intel model and AMD/nVidia models) and no other! Vostro 3350 and 3550 use AMI Aptio BIOS, not SecureCore Tiano!Modified BIOS images includes the following changes:- Unlocked write access to MSR 0xE2 - credits to RevoGirl;- Unlocked Advanced Setup options (includes UEFI Boot option) - credits to jkbuha, HairyCube and myself;- CPUID 206A7h microcode updated to V28 - credits to jkbuka (again) and Florin9doi;- Video BIOS for Intel updated from 2098 to 2170 with GOP protocol support (bring 1366x768 resolution to GUI) - credits to Ash;- BIOS DSDT modified to fix Dell's ACPI syntax screw-up while checking for MBT (media buttons) - credits for PhoenixTool fix in 2.14 to AndyP.In order to flash the modified BIOS image you have to obtain it first. Make sure to read the enclosed readme.- Vostro 3450 A13-C4: LINK - Inspiron N4110 A12-C4: LINK - XPS 17 L702x A19-C4: LINK Use WinFlash method if you are on stock DELL BIOS. If you already have UEFI capable BIOS I recommend using PFlash method to prevent BIOS settings from being reset.When you are done flashing go to your BIOS Setup and navigate to Advanced tab, go to Boot Configuration section and enable UEFI Boot.2. How to install OSXIn case you want to boot Legacy Windows from primary HDD (because let's face it, Dell made it pretty hard to use UEFI Windows with all the freezing issues caused by their proprietary software while having a UEFI installation) and you have a caddy in place of your DVD drive with a disk you want to dedicate to booting OSX simply put you can't do that by default BIOS means as caddy is not bootable. You can only make it bootable as a UEFI medium and there is why this guide was even put together. Also I should mention that booting Legacy Windows from UEFI Clover is a big no go with Tiano firmware, so don't expect that. The only way to access Legacy Windows is to either use F12 and choosing Hard Disk or exiting Clover.Now go ahead and download Clover bootloader that you will need for this guide :Required Pre Installation files: LINK 2.1. You have to have a flash drive prepped with UEFI Clover (no need to prepare it in some weird way, just copy the files to it). Just format the flashdrive to FAT32 and put the contents of "UEFI Clover USB" onto it. N.B. Make sure to rename EFI/CLOVER/config-17 or config-14 (depending on the computer model) to just config.plist, EFI/CLOVER/ACPI/patched-17 and patched-14 to just patched respectively!2.2. You need a second flash drive as well as an access to a genuine Apple computer (or a VM) that is capable of accessing Mac AppStore in order to download the free Mavericks installation app. Then, using DiskMakerX application you have to make a bootable OSX drive. 2.3. When that's done use UEFI Clover USB drive to boot your OSX medium and partition your HDD in the DVD caddy as you desire, but make sure partition map is GPT. You can then install OSX to that target disk while you are at it. The installation process is usually subdivided into 2 stages. 3. Post installation I've put together a convenient installer that allows you to put some needed finishing touched to your OSX installation on your supported DELL laptop. Go ahead and download the installer (only OSX 10.9 & 10.10 is supported): DELL SCT OSX Support Package v1.1.3 - HERE | - PREV - When you run the installer you will need to select the destination disk you are installing it to. Please note, the files will be copied to EFI System Partition of active boot disk. - Select laptop model - Select motherboard type - Select daughterboard type - Select wireless module (limited support available) - Select "About This Mac" customizations for either Vostro, Inspiron, XPS - Select applications to install If you are installing Support Package for the first time new serial numbers for MBP8,1 model identifier will be generated automatically, if you are reinstalling and already have your config in EFI partition serial numbers will be retained. The installer will put CLOVER onto your system partition and install all the necessary kernel extensions (preconfigured) to support your hardware. 4. Adding Clover to your F12 Boot Manager When you have installed the Dell SCT OSX Support Package package remove your Clover USB drive, reboot your laptop and boot into Clover GUI, press F3 and start the Shell entry that has appeared. While in shell you first need to determine what is the number of file system of the EFI System Partition on your DVD caddy drive. Perform the command: map fs* The ESP on the GPT disk will be marked as GPT,1 and is usually either fs2 or fs3. Let's assume fs3 is ESP. We don't want the BOOT folder as it won't ever be bootable with HDD sitting in DVD caddy, so we get rid of that: fs3: cd \EFI rm -r BOOT Then, to add custom Clover Boot Manager entry you need to do the following: bcfg boot add 3 fs3:\EFI\CLOVER\CLOVERX64.efi "Clover" We used 3 here as by default in BIOS 0 is diagnostics, 1 is Bios Setup and 2 is Boot Manager. Now, go to your BIOS Setup and just for emergency set the boot order as follows: - USB - CD/DVD Drive - Clover - Hard Disk - eSata - Network - Removable Disk Having this boot order configuration first off will be as a precaution if something ever happens and you can't start the laptop normally, so USB as the first device will allow you to boot a crisis bios recovery PFlash.efi with a BIOS capsule. Also, this kind of boot order will allow you to boot legacy Windows installed on your primary HDD by just exitting Clover, so there won't be a need to go to boot menu (F12) to select HDD when you need to boot Windows. You can add Shell binary to boot menu the same way, you just have to point it to the other EFI application: bcfg boot add 9 fs3:\EFI\CLOVER\tools\Shell64U.efi "Shell" That's it. If you followed the guide at this point you should have a fully working OS X Mavericks installation. 5. Known issues If anyone has any insights on fixing these remaining problems on this range of machines I would be very grateful. So far the problems are as follows: 1. Wireless interface toggle hotkey (Fn+F2) doesn't work in UEFI mode and causes system to freeze, hence it was disabled in OSX ACPI using a custom patch. This is caused by a buggy UEFI implementation by DELL, which is the reason they originally locked it down from the factory. Use software toggles to control status of Bluetooth and Wi-Fi. 2. HD3000 still has the ability to utilize VGA port with some minor annoyances, namely - no hotplug support. You have to connect the monitor before you start OSX and when you unplug the monitor in running system, OSX will still think it's connected until you reboot. 3. No support for docking mode for HDMI connector (works ok with VGA), meaning if you close the LID when HDMI screen or projector is connected laptop will enter sleep. 4. Having HDMI screen connected during shutdown and restart will cause the system to stall. Turn of the screen and unplug from laptop before shutting down or restarting. 5. On XPS L702x HDMI connector is physically linked to NVIDIA chip and therefore will not work in OSX due to Optimus being unsupported. DisplayPort connector is linked with Intel graphics and is known to work. 6. Soft rebooting from Windows into OSX will leave the headphone socket non-operational until you cold boot OSX. Credits to @Dokterdok for providing detailed research and solution for Handoff & Continuity support. Tested with BCM943225HMB card. Table design courtesy of OSX Latitude. I hope they are ok with me borrowing the canvas. Updated - 14th Jun 2015:- DELL SCT OSX Support package updated to v1.1.3 Updated - 14th Feb 2015:- DELL SCT OSX Support package updated to v1.1.2 Updated - 28th Sep 2014: - DELL SCT OSX Support package updated to v1.1.1 - No reports from L702x Optimus users to this day... Updated - 5 Sep 2014: - DELL XPS 17 L702X Optimus support added - Major update to SCT OSX Support package bringing it's version to 1.1.0 (active testing needed!!) Update - 26 Jul 2014: - DELL SCT OSX Support Package updated to v1.0.4, includes Yosemite Beta support Update - 1 Jul 2014: - DELL SCT OSX Support Package updated to v1.0.3 Update - 8 Mar 2014: - Mandatory BIOS updates have been posted. See enclosed readme for changes and installation information. - DELL SCT OSX Support Package updated to v1.0.2 Update - 3 Mar 2014: - Clover updated to 2638 - Post installation files packaged into .pkg installer v1.0.1 for convenience - Guide partially rewritten to be less confusing Update - 25 Feb 2014: - Clover updated to 2608 - Updated grand majority of kernel extensions - Added fully remapped keyboard profile, all the keys can now be toggled to either use Fn or not .. straight from OSX (kudos RehabMan) - Added memory compartment temperature monitoring sensor - Added subtle brightness control using ACPIBacklight, levels adjust gradually and not in rough steps (kudos RehabMan, again) - Added fan control profiles - choose between automatic, audible (~3000 rpm) or passive modes from HWMonitor menu - Got rid of IOWMIFamily for display backlight control, now VoodooPS2 handles these too (1.8.11 and later) 26 Link to comment Share on other sites More sharing options...
Mirone Posted October 28, 2013 Share Posted October 28, 2013 For those who have this notebook is an excellent guide, Congratulations. Link to comment Share on other sites More sharing options...
mac.HoBONG Posted October 29, 2013 Share Posted October 29, 2013 Is it Possible to implement this guide with Dell Vostro 3350, I think It has a same specification with Vostro 3450 the difference is on Screen Size ? Link to comment Share on other sites More sharing options...
TimeWalker75a Posted October 29, 2013 Author Share Posted October 29, 2013 Same as 3550, the 3350 has completely different BIOS (Insyde H20, I'm not even sure its unlocked and UEFI capable) - so every carefully crafted DSDT patch goes down the drain, completely different audio codec - all audio solutions out of the way as well .. and different keyboard in terms of WMI implementation, so no.. sorry. This guide is valid for 3750 though as its virtually the same machine as 3450 only with 17" and an added secondary HDD feature. Link to comment Share on other sites More sharing options...
TimeWalker75a Posted October 30, 2013 Author Share Posted October 30, 2013 Support added for Inspiron 14R (N4110) AMD Switchable Graphics model, which in hand means support for Vostro AMD model as well. Posted in the original post is the modified custom BIOS of version A12 that includes: - Unlocked write access to MSR 0xE2 - credits to RevoGirl; - Unlocked Advanced Setup options (includes UEFI Boot option) - credits to jkbuha, HairyCube and myself; - Video BIOS for Intel updated from 2098 to 2158 with GOP protocol support (bring 1366x768 resolution to GUI) Modified BIOS A12: LINK The post install files package for 14R includes: * UEFI Clover USB for OEM Board 03NKW8 (perhaps Vostro AMD model uses same id, someone can confirm?) - Clover updated to r2260 - No prepatched DSDT here, same as for Vostro, everything done through SSDT and Clover patches - AMD Switchable Graphics disabled with PEG0._INI method calling for ^PEGP._OFF () in SSDT-2.aml - HWSensors monitoring supported same as on Vostro - SSDT-1.aml is used for that - No pre-coded SSDT for CpuPm, enabled Generate P and C states in Clover config.plist - Dell's MBT device check by _OSI is fixed by DSDT patch, on Vostor this is fixed at BIOS level - Added @Zeniths's USB3.0 patches for NEC Renesas controller, no additional kexts required - Config includes custom EDID to fix screen artifacts (thanks to @Zprood). * Files for /System - Created custom com.apple.macbookpro-13-unibody icon to install into CoreTypes.bundle for Profiler customization - Added @Zprood's DisplayVendorID-6af:DisplayProductID-183c display override to support more scaled resolution and fix screen panel name in System Profiler - Extensions with Platform Profile option have been updated to include Inspiron 14R 03NKW8 board - Network kext has been swapped for one that supports onboard RTL8136 controller. This comes from Realtek official page (RTG NIC 2.0.6) and will probably require you to set Configuration mode to manual. IF you experience sleep/wake issue remove this kext to see if it is the cause of the problem. UEFI Clover & post install files: LINK Get the rest of the files for this guide from Vostro package. Update (11/01/13): If your 14R has AMD 6470M graphics rename OEM 03NKW8 folder to 0WVPMX. If your 14R has AMD 6630M graphics then keep the name as is. Update (01/01/14): If your 14R is an Intel-only model rename OEM 0YW3P2 folder to 05TM8C. Link to comment Share on other sites More sharing options...
DavidRocha Posted October 30, 2013 Share Posted October 30, 2013 With this VoodooPS2Controller can not shine through the multimedia key and the function does not disable the touchpad. Link to comment Share on other sites More sharing options...
Zprood Posted October 31, 2013 Share Posted October 31, 2013 With this VoodooPS2Controller can not shine through the multimedia key and the function does not disable the touchpad. you should take a look about rehabman's voodoops2controller github guide. i give some advice about it. if you use TW's kext, add your board-id under Dell's alias, or you take stock one from rehabman. 1. for brightness key work, install TW's IOWMIController from his guide. then mod dsdt like this( DO IT BOTH _Q80 method and _Q81): before: If (LEqual (OSYS, 0x07D6)) { //......// If (PWRS) { Store (Local0, BRGA) } Else { Store (Local0, BRGD) } Store (0x03, ^^^^AMW0.INF0) Store (Zero, ^^^^AMW0.INF1) Store (0xE006, ^^^^AMW0.INF2) Store (Local0, ^^^^AMW0.INF3) If (LEqual (DMFG, Zero)) { Notify (AMW0, 0xD0) } //....// } after: If (LEqual (OSYS, 0x07D6)) { //......// } If (PWRS) { Store (Local0, BRGA) } Else { Store (Local0, BRGD) } Store (0x03, ^^^^AMW0.INF0) Store (Zero, ^^^^AMW0.INF1) Store (0xE006, ^^^^AMW0.INF2) Store (Local0, ^^^^AMW0.INF3) If (LEqual (DMFG, Zero)) { Notify (AMW0, 0xD0) } 2. for disable touchpad from TW's voodoops2controller, you can use PrintScr key to do that, because his remap fn+f3 to PrintScr key. one more thing, you can have it back to Fn+F3, just remap it twice in the custom ps2 map, like: e01e=e037 e037=e01e e01e is scan code of Fn+F3, e037 is PrintScr. @TW, i think i should say great work this time. 1 Link to comment Share on other sites More sharing options...
KaBuu Posted October 31, 2013 Share Posted October 31, 2013 I can use this bios with Vostro 3550 ? Link to comment Share on other sites More sharing options...
TimeWalker75a Posted October 31, 2013 Author Share Posted October 31, 2013 With this VoodooPS2Controller can not shine through the multimedia key and the function does not disable the touchpad. Sorry, I think that aliases don't seem to work in VoodooPS2, just copy vostro's custom profile and name it 03NKW8. Attached is a modified kext that should hopefully work. Brightness keys are commanded through WMI, so you need an extra extension. VoodooPS2Controller.kext.zip I can use this bios with Vostro 3550 ? NO! Can't you read? BIOS images are meant only for Dell Vostro 3450 and Inspiron 14R (both Intel model and AMD Switchable Graphics models) and no other! And same question has been answered in this thread already. @Zprood, no need to modify anything, it should work as is. Link to comment Share on other sites More sharing options...
Zprood Posted October 31, 2013 Share Posted October 31, 2013 @TW, yes, it doesn't needed now. Link to comment Share on other sites More sharing options...
DavidRocha Posted October 31, 2013 Share Posted October 31, 2013 The kext IOWMIFamily already installed, but it still did not work with this kext you passed! But with this option works only kext attached Fn + F3 (disable / enable touchpad), but the brightness does not work! VoodooPS2Controller.kext.zip Link to comment Share on other sites More sharing options...
TimeWalker75a Posted October 31, 2013 Author Share Posted October 31, 2013 VoodooPS2 has nothing to do with controlling the brightness on these laptops. Link to comment Share on other sites More sharing options...
DavidRocha Posted October 31, 2013 Share Posted October 31, 2013 ok, why can`t I control through IOWMIFamily? Link to comment Share on other sites More sharing options...
TimeWalker75a Posted October 31, 2013 Author Share Posted October 31, 2013 Either you have installed an original unmodified driver that won't work for new generation of Dell laptops or you have no DSDT patch applied for this kext to attach. You have to see this in IOReg .. if this is absent then something is clearly wrong. I gave you all the files to have a completely working OSX install, I've even written a manual and yet you ask questions that have answers in this thread. Link to comment Share on other sites More sharing options...
DavidRocha Posted October 31, 2013 Share Posted October 31, 2013 Look how my ioreg! I believe there is nothing wrong .. ioreg.tiff ioreg mac.zip Link to comment Share on other sites More sharing options...
TimeWalker75a Posted October 31, 2013 Author Share Posted October 31, 2013 Have you actually tried installing the kext I HAVE PROVIDED? Also, your IORegistryExplorer produces corrupted dumps. Link to comment Share on other sites More sharing options...
DavidRocha Posted October 31, 2013 Share Posted October 31, 2013 I tested this and it worked here ioreg. MacBook Pro de David.zip Link to comment Share on other sites More sharing options...
TimeWalker75a Posted October 31, 2013 Author Share Posted October 31, 2013 Version 3 of IORegistryExplorer produces broken dumps, use version 2.0 if you want someone to look at them. Link to comment Share on other sites More sharing options...
DavidRocha Posted October 31, 2013 Share Posted October 31, 2013 Now guess work! kext.tiff Mac David.zip Link to comment Share on other sites More sharing options...
TimeWalker75a Posted October 31, 2013 Author Share Posted October 31, 2013 It looks fine indeed, I have no way of testing this for you. If it works for @Zprood it should work for you as well. If it doesn't then it's obviously an error somewhere on your part. Try enabling these to see if brightness even works for you -> http://puu.sh/552IS.png Link to comment Share on other sites More sharing options...
DavidRocha Posted October 31, 2013 Share Posted October 31, 2013 Thanks TW, What I did was to modify the shortcuts Fn + F4 (decrease) Fn + F5 (increase) and it worked! Another question, according to my ioreg you saw, my graphics is disabled completely? Eye on Graphics / Displays and it appears it is correct anyway? Graphics.tiff Link to comment Share on other sites More sharing options...
TimeWalker75a Posted October 31, 2013 Author Share Posted October 31, 2013 It's not disabled and this can be the cause of default WMI brightness controls failing for you. Your IOReg also shows AMD as still being active: http://puu.sh/553Gc.png Your PtidTabl and Cpu0Ist tables are not dropped, whilst they should have been with the config I have provided for 14R. And you obviously didn't follow the guide even in a slightest bit, because you have a custom SSDT table loaded for VOSTRO and not 14R, so this table doesn't have AMD graphics disabling code and to add to that it has IGPU injection which can't be used on 14R because SgRef table already has _DSM method for GFX0 (IGPU) and Clover DropOEM_DSM is unable to drop it properly. Link to comment Share on other sites More sharing options...
DavidRocha Posted November 1, 2013 Share Posted November 1, 2013 I believe that these tables are set up for me 14R. I do not understand why the graphics card not being disabled because the method is already implemented in SSDT-2 Scope (\ _SB.PCI0.PEG0). SSDT-3 I extracted the script Revogirl. Actually I had not put this method before and now put, and now my audio and wifi does not work. One detail that is present now in the ioreg GFX0, Please find attached files. config.plist.zip patched.zip ioreg GFX0.zip Link to comment Share on other sites More sharing options...
pokenguyen Posted November 1, 2013 Share Posted November 1, 2013 It's not disabled and this can be the cause of default WMI brightness controls failing for you. Your IOReg also shows AMD as still being active: http://puu.sh/553Gc.png Your PtidTabl and Cpu0Ist tables are not dropped, whilst they should have been with the config I have provided for 14R. And you obviously didn't follow the guide even in a slightest bit, because you have a custom SSDT table loaded for VOSTRO and not 14R, so this table doesn't have AMD graphics disabling code and to add to that it has IGPU injection which can't be used on 14R because SgRef table already has _DSM method for GFX0 (IGPU) and Clover DropOEM_DSM is unable to drop it properly. Can you explain what is the role of PtidTabl? Should we really drop it? Link to comment Share on other sites More sharing options...
DavidRocha Posted November 1, 2013 Share Posted November 1, 2013 @ Zprood's if possible, can you attach your ioreg me to analyze? Thank you. Link to comment Share on other sites More sharing options...
Recommended Posts