Jump to content
Slice

Dell Latitude E6430 full solution

64 posts in this topic

Recommended Posts

Advertisement

you have said that you installed high Sierra on this laptop ..... NVS5200M working now with high Sierra or it still not working

On 5/21/2018 at 7:41 PM, Slice said:

Yes, other things work.

 

Снимок экрана 2018-05-21 в 20.40.54.png

nvs5200m is working with high Sierra or it is still not working ?

Share this post


Link to post
Share on other sites
On 1/5/2019 at 10:23 PM, Momen1/2001 said:

you have said that you installed high Sierra on this laptop ..... NVS5200M working now with high Sierra or it still not working

nvs5200m is working with high Sierra or it is still not working ?

No. I said that I boot High Sierra with Intel Graphics not Nvidia.

Share this post


Link to post
Share on other sites

Hello,

I have a E6330 that I have had off and on again problems with rebooting. The problem seems to come from the ALPS PS2 trackpad kext because if I remove it then it will behave. I would also see an occasional error message relating to the trackpad in verbose while booting. This was with different kexts from OSXL.

 

I have tried your ALPS PS2 kext and now have not seen any errors while booting and have not had a reboot. The original problem was very random and, at times, I could go quite a while before any issue. I am not sure why there would be a difference with your driver. It appears to based on the same code. Accounts from other people at OSXL suggest that they have been successful with the driver I was using originally.

 

In any case, thank you for sharing your work.

Share this post


Link to post
Share on other sites
El 30/9/2017 a las 8:15, Slice dijo:

Instalé con éxito macOS 10.11.6 y Windows 7 Pro SP1 en modo UEFI en la computadora portátil.
A lo largo de mi camino, no hay un acuerdo con ellas.
 
Hardware
Intel® Core i5-3320M CPU @ 2.60GHz, el speedstep funciona con la configuración predeterminada del
chipset Clover Chipset serie Intel 7, no se le parche parche
Video: IntelHD4000 o NVS5200M conmutable en BIOS, funciona en ambos casos
LAN; Intel 82579LM, funciona con IntelMausiEthernet.kext v2.2.1
Audio: IDT 92HD93BXX, funciona con VoodooHDA 2.9.0.
Lector SDHC O2Micro; trabaja con AppleSDHC.kext nativo con propiedades arbitrarias de Clover.

USB3.0 funciona de forma nativa si no está deshabilitado en el
teclado DSDT PS2 y el panel táctil funciona con VoodooPS2.
WiFi: Dell Intel WiFi fue reemplazado por  Dell DW1520, Broadcom BCM943224HMS. DeviceID = 4353
Pantalla LCD 1366x768

BIOS A12. Inicialmente fue A02. Entonces encendí A23 y encontré que es bastante malo. La pantalla está llena de artefactos. Flash A12 y todo está bien. No se han probado otras versiones.

Por alguna razón, la BIOS puede cambiar de Intel a Nvidia por sí mismo, así que tengo que hacer que mi solución funcione de manera independiente en este estado.

 

Wifi

No está funcionando OOB aunque tiene una ID de dispositivo conocido por Apple. El motivo es WhiteList en el driver.

Configuré MacModel como MacBookPro10,1, mientras que el WiFi funcionará en MacBookAir. Hago un parche en trébol.

También hay un parche para canales.

Se eliminó un kext Brcm4331 porque tiene el mismo DeviceID. Deje kext Brcm4360 para trabajar solo.

 

Tarjetas de video

En Bios podemos configurar Optimus = Habilitar / Deshabilitar

Si se activa, tenemos dos tarjetas de video Intel primero y Nvidia segundo. En este caso, SSDT-3.aml adicional apagará a Nvidia.

Si se desactiva solo tenemos tarjeta Nvidia. Funcionará si Board-ID se toma de iMac13,2.

Pero aquí hay una contradicción con WiFi con la ID de placa requerida de MacBookAir.

Así que tomo MacModel como MacBookPro10,1, que está más cerca de la CPU IvyBridge.

Configure BoardID como iMac13,2 para hacer que Nvidia funcione.

Parche BoardID en Brcm4360 para hacer que WiFi funcione.

Ahora tengo

Inyectar->

-> Intel = SI

-> Nvidia = SI

y SSDT-3.aml en la carpeta ACPI \ parcheada. Este SSDT apagará Nvidia si la tarjeta Intel está activada.

Para los gráficos de Intel hay un parche contra 8 manzanas al inicio.

 

Brillo

No hay kexts especiales.

El brillo controlado por las teclas F1, F2 y el control deslizante en el Panel de control en ambos casos, Intel o Nvidia. Detalles aquí   # 72 

 

DSDT y SSDT

Esta es una historia muy larga y, finalmente, tengo un trabajo de reposo en ambos casos, Intel o Nvidia.

 

Sensores

Yo uso mis HWSensors3 con FakeSMC 3.5.0.

Tengo el seguimiento:

Temperatura de la CPU

Temperatura de la GPU

Frecuencia principal de GPU

Frecuencia de sombreado de GPU

Estado de la batería% lleno, tiempo de carga o tiempo de vaciado.

Tensión de la batería dinámicamente.

Amperaje de la batería dinámicamente. Puedo ver que cambia en juegos pesados.

Temperatura del disco duro.

Battery.png

 

Audio

Me gusta VoodooHDA y no tengo problemas con eso.

El sonido es claro, fuerte y conmutable entre el altavoz interno y los auriculares.

El micrófono está funcionando.

 

Bluetooth

Acaba de probarse con BTFirmwareUpdate.kext y funciona. No lo necesitaba así que lo apagué por interruptor inalámbrico en el lado derecho.

 

Teclado, Touchpad y Touchstick

Puesto # 14

 

Mi configuración, archivos ACPI y kexts están adjuntos.

05.12.2017

EFI.7z

 

EDITADO:

Mejor DSDT en el post # 6.

El sueño funciona incluso cuando se inserta CA.

 

EDITADO 06.12.2018

Ahora tengo HighSierra y esta es mi carpeta EFI

 

Снимок экрана 2018-12-06 al 11.00.50.png

 

 

Bienvenido a la discusión!

EFI-E6430.7z

Hi friend. Excuse my English.
Thank you very much for your work and for sharing it.

I've been trying to do an installation on my Latitude E6530 for more than a week, which is the same as yours and I do not get it. It always gets stuck before finishing the installation. Might you help me? What guide did you follow? The Clover folder you share is copied to a postinstallation, right?

Thanks again. I'm very excited to work on this machine.

Share this post


Link to post
Share on other sites
Posted (edited)

@Slice

I've tried to use your EFI settings on High Sierra and I've got still black screen (with nvidia optimus turned on). Only case when it works was when I added to boot nv_disable=1 what is kinda weak...
BIOS A12
CPU: i7-3740QM

Edited by dindu5678

Share this post


Link to post
Share on other sites
20 hours ago, dindu5678 said:

@Slice

I've tried to use your EFI settings on High Sierra and I've got still black screen (with nvidia optimus turned on). Only case when it works was when I added to boot nv_disable=1 what is kinda weak...
BIOS A12
CPU: i7-3740QM

It looks like you have no Optimus and using Nvidia graphics instead of Intel. No way. This nvidia will work in ElCapitan, no more.

As well I have special DSDT and SSDT to switch nvidia off during start and wake.

Share this post


Link to post
Share on other sites

I successfully use bluetooth in 10.13.6 with the kext BRCMInjector with modified info.plist.

Attached to topic.

Share this post


Link to post
Share on other sites
Posted (edited)

I tried also to install 10.11 with same result - black screen when it tries to show a "Select language" in installer. 

 


CPU: i7-3740QM
Display: 1600x900
RAM: 16gb DDR3 1600mhz
GPU: nvs5200m + intel HD4000
BIOS: A12

 

When Optimus is enabled, my linux returns:

Quote

VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
VGA compatible controller: NVIDIA Corporation GF108GLM [NVS 5200M] (rev a1)

but without it shows only nvs 5200m. Still I don't know how to run only with this intel gpu. 

Edited by dindu5678
Add specs

Share this post


Link to post
Share on other sites

Hi Guys,

 

Just one quick question.

Is it required to have the A12 BIOS installed or an earlier version like A02 is ok?

 

Best regards,

voidRunner

Share this post


Link to post
Share on other sites

I don't remember exactly what was the problem with A02. Anyway you can flash A12 from Windows and then flash A02 again. There is no restriction for changing versions. 

Share this post


Link to post
Share on other sites
6 hours ago, godzilla5123 said:

Hi,
I used your EFI files and sleep doesn't work for me. Is there another DSDT file that might work?

There is current folder ACPI/patched from working 6430 in HighSierra

Sleep works fine.

 

ACPI.zip

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 glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By AppleBytes
      Hello,
      I'm working on a re-install of OSX on a dell inspiron 9400. I was finally able to get a copy of SL on it. But it still needs MUCH work, as the graphics (NVIDIA Geforce Go 7800) isn't properly recognized -- either by model, or installed VRAM.
      It has 512Mb, but only initializes 256Mb VESA.
      Anyway, as a start, I thought it best to use a valid dsdt.dsl for compilation, and start there. I've managed to remove all the warnings, and errors save 2
      OUTPUT:
      # sudo iasl -ta ./dsdt.dslll Intel ACPI Component Architecture ASL Optimizing Compiler version 20110527-64 [May 27 2011] Copyright (c) 2000 - 2011 Intel Corporation ./dsdt.dslll   3519:                                 Return (0x00) Error    4080 -           Invalid object type for reserved name ^  (found INTEGER, requires Buffer) ./dsdt.dslll   3956:                     Return (Package (0x00) {}) Remark   5072 -         Effective AML package length is zero ^ ASL Input:  ./dsdt.dslll - 4997 lines, 158533 bytes, 1633 keywords Compilation complete. 1 Errors, 0 Warnings, 1 Remarks, 577 Optimizations I'm attaching a copy of the above output, and the dsdt.dsl file in a tarball to this post in hopes someone with the required knowledge can help me fix it.
      FWIW
      SMBIOS I'm using indicates this is a MBP 3,1
      cpu: cd2 (T7400 @2.16Ghz)
      graphics: NVIDIA Geforce Go 7800 ( G70M? )
      ram: 4Gb
      dell inspiron 9400 (Laptop)
       
      Thank you for all your time, and consideration!
       
      --Chris
       
      DSDT-DSL.tar
    • By fantomas1
      Hi InsanelyMacaholics   

      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
       
      10.12.6
      Nvidia Web Driver - 378.05.05.25f16 --> build 16G2016 (thanks to Cyberdevs) New!
      Nvidia Web Driver - 378.05.05.25f15 --> build 16G1918 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f14 --> build 16G1917 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f13 --> build 16G1815 (thanks to flowrider)
      Nvidia Web Driver - 378.05.05.25f12 --> build 16G1710 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty)
      Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo) 
      Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
      Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
      Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
      Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
      Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
       
       
      10.12.5
      Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
       
       
      10.12.4
      Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
      Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr)  Pascal support!!!
      Nvidia Web Driver - 367.15.10.45f01 --> build 16E195 (thanks to Lanc)
       
       
      10.12.3

      Nvidia Web Driver - 367.15.10.35f01 --> build 16D32 (thanks to shatterhenner)
       
       
      10.12.2
      Nvidia Web Driver - 367.15.10.25f02 --> build 16C68 (see this post)
      Nvidia Web Driver - 367.15.10.25f01 --> build 16C67 (see this post)
      Nvidia Web Driver - 367.15.10.25b06 --> build 16C60b/16C63a (see this post)
       
       
      10.12.1
      Nvidia Web Driver - 367.15.10.15f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
      Nvidia Web Driver - 367.15.10.15f01 --> build 16B2555 (thanks to Moviemakergr)
       
       
      10.12.0
      Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
       
       
      GM
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
       
       
      DP/PB
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun) 
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
      Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)
       
    • By fantomas1
      macOS Mojave 10.14.6 beta (18G29g)
    • By fantomas1
      This update:
      • Adds AirPlay 2 support for sharing videos, photos, music and more from your Mac directly to your AirPlay 2-enabled smart TV
      • Adds the ability to follow a magazine from the Apple News+ catalog browsing view
      • Includes support for the Reiwa (令和) era of the Japanese calendar
      • Improves audio latency on MacBook Pro models introduced in 2018
      • Fixes an issue that prevented certain very large OmniOutliner and OmniPlan documents from rendering properly
       
      Update
      Combo

      View full article
×