E6410 nVidia - Yosemite Help Thread

[PlutoDelic]

http://www.notebookcheck.net/NVIDIA-Quadro-NVS-3100M.24738.0.html

 

If by renaming you mean the cosmetic change, it's useless in terms of QE/CI improvement. What matters is that the card details are suitably injected through DSDT if that proves required (for instance if the card is not natively recognized). Once the card details are properly injected, OS X will load the correct nVidia kext and framebuffer; everything should then be Ok.

 

But if the card is natively detected and the OS X-provided nVidia family + framebuffer kexts are loaded, there's nothing else you can do. The only possible "better" kexts could be nVidia's own, if they exist for OS X (for that GPU).

 

Call me stupid for this, but, i went through an experiment as i had nothing to lose. My target was not QE/CI, but i just felt we were using old drivers. I did something, it worked, and probably only you can explain why it works .

 

I downloaded the latest nVidia Web Driver for 10.10.1 in the Quadro section, however from experience i know that it will report incompatible system and wont process further. So i dig a bit more and found a way to extract .pkg files. Copied all the kexts to /S/L/E and pref pane to /S/L/Pref*. Did a kext utility checkup and restarted with the nvda_drv=1 bootflag this time (somewhere i read it doesnt work in Clover??).

 

The Web Drivers seem to have a Web at the end of each file, and it only required one file to be overwritten: NVDAStartup.kext

 

This is the result so far:

 

bash-3.2# kextstat | grep NVD
   78    0 0xffffff7f81012000 0x3000     0x3000     com.nvidia.NVDAStartup (10.0.1) <12 4 3>
  107    2 0xffffff7f82e7e000 0x275000   0x275000   com.nvidia.web.NVDAResmanTeslaWeb (10.0.1) <88 79 12 5 4 3 1>
  109    0 0xffffff7f830f3000 0x2ae000   0x2ae000   com.nvidia.web.NVDANV50HalTeslaWeb (10.0.1) <107 12 4 3>
bash-3.2# 

bash-3.2# kextstat | grep GeF
  110    0 0xffffff7f833a1000 0xce000    0xce000    com.nvidia.web.GeForceTeslaWeb (10.0.1) <107 88 79 12 7 5 4 3 1>
bash-3.2# 

 

Is there any way i can test the difference between the two kext bundles? So far the system feels good, not any major difference but not problems either. I also have my doubts that, even though kextstat displays the kexts with the Web at the end, the version remains 10.0.1, however, Cuda pref pane reports 10.1.43.

 

@, jump in ship please...

[v3ct0r]

Hey Pluto,

 

Great job! That seems like an awesome breakthrough.

 

What kexts were ADDED to /S/L/E? They may be named something different. I'd try filtering by Date Added/Created

 

Basically, by finding out, you may be able to determine which kext is delivering the version number of 10.1.43.

 

Also, in case you want to try and revert back to your previous state to see the difference, I give you the unmodified NVDAStartup.kext from my system:

NVDAStartup.kext.zip

 

Hopefully just a rename of the old NVDAStartup + Other kexts that the install added and a permissions repair after you drop in the attached kext should put you back where you were prior to installing the newer driver. 

 

Again, great job and I can't wait to see what this leads to . 

 

EDIT: Wanna do us all a favor and try sleep? If I remember correctly, it didn't work previously due to graphics power management! Would the new driver fix that? :0

[PlutoDelic]

No sleep im afraid, but i think i did do something with the Hibernate mode when i initially installed, not sure what though as i cant remember. what about darkwake, could that boot flag help?
 
Also, let me break down what i did.
 
Downloaded latest web drivers from here: http://www.nvidia.co.uk/download/driverResults.aspx/80901/en-uk
As they wont install due to incompatibility, i used unpkg to extract the package.

 

It extracts two folders inside the main directory, one for the /S/L/E and one for /S/L/PreferancePane

 

I cross-compared all files, and they are similar in file naming, though the new ones differ with the *Web.kext at the end, of course as i noted except the aforementioned NVDStartup.kext, which of course, i backed up just in case.

 

it wont activate the drivers unless you boot with the nvda_drv=1 bootflag

 

So to summarise

 

Original Kexts:

 

GeForce.kext

GeForceGA.plugin

GeForceGLDriver.bundle

GeForceTesla.kext

GeForceTeslaGLDriver.bundle

GeForceTeslaVADriver.bundle

GeForceVADriver.bundle

NVDAGF100Hal.kext

NVDAGK100Hal.kext

NVDANV50HalTesla.kext

NVDAResman.kext

NVDAResmanTesla.kext

 

 

10.10.1 Web Drivers

 

GeForceWeb.kext

GeForceGLDriverWeb.bundle

GeForceTeslaGAWeb.plugin

GeForceTeslaGLDriverWeb.bundle

GeForceTeslaWeb.kext

GeForceTeslaVADriverWeb.bundle

GeForceVADriverWeb.bundle

NVDAGF100HalWeb.kext

NVDAGK100HalWeb.kext

NVDAGM100HalWeb.kext

NVDANV50HalTeslaWeb.kext

NVDAResmanTeslaWeb.kext

NVDAResmanWeb.kext

 

 

Replaced

 

NVDAStartup.kext

 

I personally just dragged and dropped and let Kext Wizard do the usual in /S/L/E

Wondering why the Driver Manager preference pange doesnt work...

 

[PlutoDelic]

Just booted without nvda_drv=1, and kextstat shows this:

Memlis-MacBook-Pro:~ memlirobaj$ kextstat | grep nvidia
   84    0 0xffffff7f81012000 0x3000     0x3000     com.nvidia.NVDAStartup (10.0.1) <12 4 3>
  101    2 0xffffff7f8106d000 0x26a000   0x26a000   com.apple.nvidia.classic.NVDAResmanTesla (10.0.0) <85 78 12 5 4 3 1>
  102    0 0xffffff7f812e1000 0x2aa000   0x2aa000   com.apple.nvidia.classic.NVDANV50HalTesla (10.0.0) <101 12 4 3>
  113    0 0xffffff7f82715000 0x2000     0x2000     com.nvidia.CUDA (1.1.0) <4 1>

so version 10.0.0 shows up, at least something has updated for real.

[PlutoDelic]

It seems that the WiFi connection drops (disconnecting from AP) after the screen times out (and goes in to the login window) seems to be caused by 802.1x, which is the standard that defines Enterprise Security for WiFi. I am not having this issue on my WPA2 Private APs at home.

 

PS, sorry if i am double posting, feel free to merge if one must.

[Tengokuu]

Is there any explanation as to why the battery meter goes in and out? The system appears to report my 6510 dead way before it's really low, too.

[PlutoDelic]

Is there any explanation as to why the battery meter goes in and out? The system appears to report my 6510 dead way before it's really low, too.

 

Initially, the built in battery monitor from apple was toast, very inconsistent results, then i got SmartBatterySlim but even this one showed very odd numbers due to the battery being a double one (i think).

 

What i did is, updated these:

 

https://github.com/RehabMan/OS-X-ACPI-Battery-Driver

http://sourceforge.net/projects/hwsensors/ ( http://www.hwsensors.com/releases seems more updated) which will update FakeSMC as well.

 

Now HWSensors ICON in the BAR can be changed to show the percentage of the battery. So far, this has been the only way for me to have accurate battery output.

 

Your other option is chasing the 7 balls for Shenron

[knight0fdragon]

I apologize if this has been asked already, but I didn't see it in this thread.  Does anybody else get the SD cards mounting twice?  Does anybody know how to fix this?

[seesoftwr]

@patel4prez  thank so much for the guide and your time!

 

I am newbis in hackintosh. For me, I had issue of boot on the HD. But after some reinstall and Partition and erase  Install work like the guide said!

But was playing with "kext" around and lost mouse capability?? I might accidentaly removed or replaced kext... I did lost keyboard also?? but lucky keyboard is back and still dont know what I did lol.  Now i have to plug in a external USB for the mouse.

 

If not too musch asking. Is it possible for you to put a FIX for keyboard and mouse in a ZIP like you did for the AUDIO??

That you can stick at ---> https://osxlatitude.com/index.php?/topic/7376-dell-latitude-e6410-yosemite-nvidiaintel/

-->(Indtead of to reinstall from scrach + boot issue?? + Office, iLife, adobe... + update for sys and software etc...)

 

Thank you so much for the AUDIO fix. It work great!!

 

Edit: Solved the issue. I used kext Wizard from JANEK202 : http://wizards.osxla...t/download.html

- Reload  VoodooPS2Controller.kext from "E6410 Y" located /Extra/Extensions and voila!! (If you want more info: http://wizards.osxla...t/download.html).

 

Apparently only the "VoodooPS2Trackpad.kext" !!!Ver1.8.8!!! inside VoodooPS2Controller.kext work with our E6410 (At least in my MaConfig).

 

!!! AVOID to play with KEXT if you don't know what you are doing. Unless it is a test install.!!!

 

But Will be great to Add the Mouse and Keyboard. And also the SDCARD fix to --> https://osxlatitude.com/index.php?/topic/7376-dell-latitude-e6410-yosemite-nvidiaintel/

 

Thank again!

[v3ct0r]

@patel4prez  thank so much for the guide and your time!

 

I am newbis in hackintosh. For me, I had issue of boot on the HD. But after some reinstall and Partition and erase  Install work like the guide said!

But was playing with "kext" around and lost mouse capability?? I might accidentaly removed or replaced kext... I did lost keyboard also?? but lucky keyboard is back and still dont know what I did lol.  Now i have to plug in a external USB for the mouse.

 

If not too musch asking. Is it possible for you to put a FIX for keyboard and mouse in a ZIP like you did for the AUDIO??

That you can stick at ---> https://osxlatitude.com/index.php?/topic/7376-dell-latitude-e6410-yosemite-nvidiaintel/

-->(Indtead of to reinstall from scrach + boot issue?? + Office, iLife, adobe... + update for sys and software etc...)

 

Thank you so much for the AUDIO fix. It work great!!

 

Edit: Solved the issue. I used kext Wizard from JANEK202 : http://wizards.osxla...t/download.html

- Reload  VoodooPS2Controller.kext from "E6410 Y" located /Extra/Extensions and voila!! (If you want more info: http://wizards.osxla...t/download.html).

 

Apparently only the "VoodooPS2Trackpad.kext" !!!Ver1.8.8!!! inside VoodooPS2Controller.kext work with our E6410 (At least in my MaConfig).

 

!!! AVOID to play with KEXT if you don't know what you are doing. Unless it is a test install.!!!

 

But Will be great to Add the Mouse and Keyboard. And also the SDCARD fix to --> https://osxlatitude.com/index.php?/topic/7376-dell-latitude-e6410-yosemite-nvidiaintel/

 

Thank again!

Try booting with -f and if that doesn't work, list the kexts you have in /Extra/Extensions.