Jump to content
InsanelyMac Forum
TimeWalker75a

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

Recommended Posts

Advertisement

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.

Share this post


Link to post
Share on other sites
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

  53Wt8.png

  - 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.

Share this post


Link to post
Share on other sites

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.  ;) 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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 ..

54Y8h.png

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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?

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 zebity
      Hi Hypervisors,
       
      I have been working to move my Late 2009 Xserve MacOS Server onto Ubuntu 18.04 LTS QEMU/KVM based virtual machine using OVMF and Clover.
       
      After much effort and testing based on the following information from: Kraxel's, Kholia, Gordon Turner and Clover site:
      https://www.kraxel.org/blog/2017/09/running-macos-as-guest-in-kvm/
      https://github.com/kholia/OSX-KVM
      https://gist.github.com/gordonturner/2a2e5ecde5e7860b52e2
      https://clover-wiki.zetam.org/Home
       
      I have now managed to get OVMF/Clover boot and install of MacOS Sierra.
       
      I started with Ubuntu 16.04 initially but this required download and compile of QEMU to get update of machines to: pc-q35-2.9 or better, so I moved to Ubuntu 18.04, which has pc-q35.2.11 available as standard.
       
      So I am now working with standard Ubuntu 18.04 LTS based systems with following packages: kvm/qemu/libvirt/bridge-utils/ovmf/virt-manager
       
      As I want to use PCIe Passthrough for a number of PCIe card currently installed in the server (SmallTree 10GbE & Areca ARC-1883 SAS RAID) I set up my machine with linux kernel boot configuration (/etc/default/grub) of: 
      GRUB_CMDLINE_LINUX_DEFAULT="iommu=1 intel_iommu=on" (as my machine is intel VT-d based HW virtualisation)
       
      This resulted in creation of a number of iommu groups (see /sys/kernel/iommu_group directory for this and this posting for information: https://forum.level1techs.com/t/ubuntu-17-04-vfio-pcie-passthrough-kernel-update-4-14-rc1/119639 , noting that Ubuntu 18.04 LTS has kernel version: 4.15.0-22-generic so there is no need to do kernel update for iommu to work).
       
      Using bare minimal Clover config.plist:
       
       
      And following Clover UEFI drivers:
       
      I can boot MacOS, but it is very very slow... it sits on the apple boot logo for over a minutes before finally moving onto the progress bar.
      The other problem I have is that no PCI or Network devices appear in the "About This Mac" System Information Report and I cannot get any network connectivity from bridged E1000 network device.
       
      Here is my virtlib.xml dump for the virtual machine:
       

      Can any one advise of whether I need to update the CLOVER config.plist to add extra items in to allow network and PCI Passthrough to work.
       
      Thank you.
       
      Regards,
       
      Zebity
       
    • By frankiee
      Hi there, time for my first guide after asking so many things
       
      Updated for newer Clover versions and with additional instructions for more apps: gdisk and RU.
       
      So what may be overlooked sometimes in the whole boot loader discussion is the ability of UEFI to do more than just loading an OS. This is why I see ".efi" files as "apps" because in fact they just are, built on a special kind of API: UEFI. So, you can actually do stuff like editing, diagnosing, testing certain stuff at the lowest possible system level without booting to any OS.
       
      DISCLAIMER: Use this guide at your own risk! For educational purposes only! Should do not any harm, but remember you are dealing with rather low level stuff. But at least for me everything went flawless.
       
      Prerequisites:
      Working clover installation Clover Configurator or some app to edit the config.plist  
      1) Memtest
       
      This is how to install the UEFI version of Memtest with Clover:
      Download memtest, I used this link: Image for creating boot-able USB Drive Open the archive by double clicking on it. Mount the file memtest86-usb.img within by double clicking again. Now, you should see a folder named EFI in this volume, containing a folder BOOT. Open it. The files containing it are the actual app, in 32 and 64 bit versions. Think in almost all cases we want to use the 64 bit version. Now, mount your EFI partition, using Clover configurator. Create a folder named MemTest86 in the EFI folder on your main drive. Copy all files in the EFI/BOOT folder from the mounted image to your newly created folder. That ends the basic setup! Now, we add the correct Menu entry to the clover boot menu, so that we can actually start this app.
       
      Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Under "Custom Entries", add an entry like this:
       

       
      Please note while the path you enter is not case sensitive, you must make sure you use the backslash "\" for entering paths, and not a slash. So basically what we do is tell clover where it can find the app, give it a name, and tell clover it is a "Windows" app. Note: with older Clover versions we had to set this to "Linux", but for now "Windows" is the setting that works.
       
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <true/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>MemTest86</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string>\EFI\CLOVER\themes\Icons\os_mint.png</string> <key>Path</key> <string>\EFI\MemTest86\BOOTX64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> Now, save and reboot and you should see the newly created entry. Note that I also used a custom Icon - this is optional - in case you don't you will just see a generic windows icon instead:
       

       
      And this is how it looks like:
       

       

       
      PS: also noticeably faster and you get also more features with this version than with the older version, for example it does now write a log file. For more Information, see: http://www.passmark.com/forum/showthread.php?4315-Memtest86-Version-5-Beta-%28Pure-UEFI%29
       
       
      2) gdisk
       
      Another app you can use is the UEFI version of gdisk (aka GPT fdisk), which you can use to edit and change your partitions.
       
      Warning! Install and use this app at your own risk! If you do something wrong here you might nuke your drive(s), so only use that if you know what you are doing.
       
      This is how to do it (even easier):
      Download here: https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.1/gdisk-binaries/gdisk-efi-1.0.1.zip/download Mount your EFI partition Unzip the file and copy the resulting folder to your EFI Folder, so your path goes like this "/Volumes/EFI/EFI/gdisk-efi" Get into clover configurator, open your standard config.plist from your boot drive and go to the GUI section. Add an entry like this:  
      If you prefer to do a manual config, add this entry to your config.plist, under GUI/Custom/Entries:
      <dict> <key>CustomLogo</key> <false/> <key>Disabled</key> <false/> <key>FullTitle</key> <string>GDisk</string> <key>Hidden</key> <false/> <key>Ignore</key> <false/> <key>Image</key> <string></string> <key>Path</key> <string>\EFI\gdisk-efi\gdisk_x64.efi</string> <key>Type</key> <string>Windows</string> <key>VolumeType</key> <string>Internal</string> </dict> When everything went OK you should see this after selecting the respective entry in Clover:
       

       
       
      3) RU
       
      I recently found one more app that might be interesting to some, and thats "Read Universal" or in short "RU". This is a tool that enables you to debug your BIOS and read (and modify!) every imaginable data, including UEFI variables, ACPI Tables etc.
       
      Warning, again! I think blindly messing around with this app is even more dangerous, but on the other hand it gives you access to a lot of potentially interesting stuff.
      Download here: http://ruexe.blogspot.de/ The next steps are basically the same as above so make a folder in your EFI partition, copy the .EFI files and make another custom entry in your config.plist Here are some screens:
       

       

       

       
       
      So this is what you also can do with UEFI and clover. I am curious which other useful applications might exist!
       
      Anybody who knows, maybe post it here?
    • By TimNeumann
      MB: Asus X99 A-II
      RAM: G.Skill Ripjaws V F4-3200C16D-32GVK (3200MHz, 4x 16GB DIMMs, so Total 64GB) in quad-channel configuration.
      CPU: i7 6800k @4.0Ghz
      GPUs: GTX 1080 Ti and GTX 1060 3GB
      (each one a monitor, because I can't get DVI to run parallel with DP on the 1080Ti, and my second monitor only has DVI/VGA)
      OS: High Sierra 10.13.2 (17C88) / Clover revision: 4392
       
      Hello everybody,
      I occasionally have system crashes and suspect that it is related to RAM. However, this RAM is completely new, and a run with MemTest86+ from the USB stick showed no errors. However, if I use Memtest on MacOS, I get a bunch of error messages, but sometimes none (I restart the computer between tests).  
      As I just discovered, my RAM is not on the recommended vendor list of my motherboard, nor is it on the manufacturer side of the RAM. I have read several times that the RAM may not have been tested by the manufacturer on this platform. Not a single X99 motherboard is listed for this RAM.
      So I also suspect that my RAM is not compatible.
      But if that were the case, how could it sometimes work completely error-free?
       
      During RAM tests in summer 2017 (a slightly different setup, 4x8GB but still G.Skill Ripjaws V) I had no errors at Memtest under MacOS, if I remember correctly. At that time it ran under Sierra 10.12.6. AptioMemoryFix.efi could also cause problems.
      I am appreciative for any help!
       
      Here is an excerpt from a faulty test.
      It is noticeable that it is always the same address during the test, but a different one after each test.
      Memtest version 4.22 (64-bit) Copyright (C) 2004 Charles Cazabon Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port) Licensed under the GNU General Public License version 2 only Mac OS X 10.13.2 (17C88) running in multiuser mode Memory Page Size: 4096 System has 12 Intel core(s) with SSE Requested memory: 57232MB (60012990464 bytes) Available memory: 57232MB (60012990464 bytes) Allocated memory: 57232MB (60012990464 bytes) at local address 0x00000001033e1000 Attempting memory lock... locked successfully Partitioning memory into 2 comparison buffers... Buffer A: 28616MB (30006495232 bytes) starts at local address 0x00000001033e1000 Buffer B: 28616MB (30006495232 bytes) starts at local address 0x00000007ffc4d800 Running 1 test sequence... (CTRL-C to quit) Test sequence 1 of 1: Running tests on full 57232MB region... Stuck Address : ok Linear PRN : testing 7 of 16 FAILURE! Data mismatch at local address 0x0000000e88133d30 Expected Data: 0xc4c340079ac9a645, Actual Data: 0xc4c3400788468846 Running comparison tests using 28616MB buffers... Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : testing 80 of 256 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x4f4f4f4f4f4f4f4f, BUFB Data: 0x4f4f4f4f88468846 Checkerboard : testing 3 of 64 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x5555555555555555, BUFB Data: 0x5555555588468846 Bit Spread : testing 1 of 128 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000005, BUFB Data: 0x0000000088468846 Bit Flip : testing 74 of 512 FAILURE! Data mismatch at local BUFA address 0x000000078b8c7530, BUFB address 0x0000000e88133d30 BUFA Data: 0x0000000000000200, BUFB Data: 0x0000000088468846 Walking Ones : testing 40 of 128 Clover Files attached
      config.plist
      drivers64UEFI.zip
      kexts.zip
      ACPI.zip
    • By BurpSuite
      screenshot:
       

       
      description:
      github: https://github.com/burpsuite/clover_theme
×