Jump to content
Slice

Dell Latitude E6430 full solution

68 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

Please respond to this...

I have dell latitude e6430 with i5-3320M

4GB ram 1333mhz with HD 4000 and nvs 5200m I want to install mac is Sierra but I can't install bios a12 because bios installation blocked (compurrace blocked it because another one have used it before me )

Now I stuck at bios a18 can't downgrade to any earlier version .... 

Is there is a way to patch DSDT And SSDT to work with this bios version I don't need my nvs5200m to work...

Share this post


Link to post
Share on other sites
On 9/30/2017 at 8:15 AM, Slice said:

For some reason BIOS can switched from Intel to Nvidia by itself so I have to do my solution working independent on this state.

Thank you @Slice

Please Can you share your DSDT solution for this particular issue ? 

I have dell precision m6800 intel + nvidia Optimus and everything works but bios switch from intel to Nvidia after reboot .

Its so annoying as I have dual setup Win + mac 

What I should add or modify in DSDT to stop that issue ?

Share this post


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

Please respond to this...

I have dell latitude e6430 with i5-3320M

4GB ram 1333mhz with HD 4000 and nvs 5200m I want to install mac is Sierra but I can't install bios a12 because bios installation blocked (compurrace blocked it because another one have used it before me )

Now I stuck at bios a18 can't downgrade to any earlier version .... 

Is there is a way to patch DSDT And SSDT to work with this bios version I don't need my nvs5200m to work...

I don't know what is the problem to downgrade and I see no solution to work with A18.

On 5/31/2019 at 10:40 PM, zkingtut said:

Thank you @Slice

Please Can you share your DSDT solution for this particular issue ? 

I have dell precision m6800 intel + nvidia Optimus and everything works but bios switch from intel to Nvidia after reboot .

Its so annoying as I have dual setup Win + mac 

What I should add or modify in DSDT to stop that issue ?

After reboot or after shutdown the BIOS can switch Optimus OFF. You have to enter BIOS and switch it ON again. No other solution exists.

Share this post


Link to post
Share on other sites
Posted (edited)

@Momen1/2001, you can probably live with BIOS A18 without graphics corruption if you apply the following Capri framebuffer patch:

https://osxlatitude.com/forums/topic/8883-dell-latitude-e6230-with-i5-3340mi7-3540m-hd4000-and-1366x768-lcd-mavericksyosemiteel-capitansierra/?do=findComment&comment=90029

 

It works fine on the E6230/E6330/E6430 (Intel HD4000 only) with all latest BIOS versions. I had personally worked around the issue with BIOS A19 on my E6230 by repatching A19's DSDT entirely and only saw corruption when shutting down or rebooting the laptop thereafter. The above patch totally fixes the screen garble/graphics corruption by adjusting the FB memory size from 16MB to 8MB.

 

Edited by Hervé

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 fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
    • By fantomas1
      Première bêta... macOS Catalina 10.15 beta (19A471t)
       
       
      anciennes carte graphiques Nvidia + Intel HD 3000
    • By fusion71au
      Patch Catalina or Mojave macOS Installer App for Unsupported Machines
       
      Often for economic reasons, Apple prevents the Installer.app for its latest macOS from installing on older machines perfectly capable of running it eg macOS 10.14 Mojave on Unsupported Macs Thread.
       

       
      In Mojave 10.14, @ASentientBot posted a method to patch the distribution file in OSInstall.mpkg to enable the Mojave installer to install on unsupported machines (with or without graphics card metal support). 
       
      In Catalina 10.15beta, the above method no longer works since Apple is checking OSInstall.mpkg for its file signature and the mandatory requirement in Catalina to install to 2 separate apfs volumes necessitates using the original Catalina macOS Base System Installer.  Fortunately, it is still possible to substitute High Sierra’s Apple Signed OSInstall.mpkg inside the Catalina or Mojave InstallESD.dmg by making it R/W.
       
      The procedure below will allow Macs or Hacks able to install High Sierra to also install Catalina or Mojave (eg SMBIOS MacPro5,1, iMac11,3, MacBook Pro7,1 which have been unsupported in macOS 10.14.x and 10.15beta) -credit to @ASentientBot's post.
       
      Prerequisites
      1. Mac or Hack capable of and running High Sierra 10.13.x
      2. An original, untouched copy of OSInstall.mpkg from High Serra InstallESD.dmg - attached OSInstall_10.13.6.mpkg.zip save to your ~/Downloads folder
      3. macOS Installer App eg for Catalina beta or Mojave downloaded to /Applications
      4. Add NVRAM boot arg (or Clover config.plist boot arg on a hack) -no_compat_check to enable system to boot to final completed Mojave or Catalina install.
       
      Procedure
      1. Open Terminal and type the following
       
      open /Applications/Install*/Contents/SharedSupport/InstallESD.dmg (assuming the Catalina or Mojave Installer App is in /Applications)  
      2. Open Disk Utility, click File|New Image|Image from ‘InstallESD”
      3. Save as read/write image, no encryption in /Applications
      4. Unmount InstallESD in DU by clicking the "eject" icon next to it
       
       
      5. Open the R/W InstallSD.dmg in /Applications and replace Catalina’s/Mojave's OSInstall.mpkg with High Sierra’s version by typing in terminal
       
      open /Applications/InstallESD.dmg cp ~/Downloads/OSInstall_10.13.6.mpkg /Volumes/InstallESD/Packages/OSInstall.mpkg  
      6. Unmount InstallESD in DU by clicking the "eject" icon next to it
      7. Replace original Catalina/Mojave InstallESD.dmg with our patched one, making a backup of the original.  In terminal, type
       
      sudo mv /Applications/Install*/Contents/SharedSupport/InstallESD.dmg /Applications/InstallESD_orig.dmg sudo mv /Applications/InstallESD.dmg /Applications/Install*/Contents/SharedSupport/  
      8.  Test the newly patched installer!…

×