Hervé

That's for Mountain Lion (10.8), not Lion (10.7). If you want to install Lion, use only the regular myHack-based process as that's the last OS X version to officially support 32bit kernel mode. Look up for pack + tuning info in the Dell Latitude D4xx support section.

Try additional Chameleon boot options such as npci=0x2000 or 0x3000.

I've posted the full pack in the D4xx section some time ago. Look it up. No further need of EDP required.

1st of all, check that your HDD mode is set to AHCI in BIOS. Then, try and boot with Chameleon boot option PciRoot=4 as it's very probably the value set in this workstation's BIOS DSDT table (it's the case with most Dell's high-end PCs and workstations). If you don't use a patched DSDT file, once you manage to boot the OS to dekstop, extract your raw DSDT with a tool such as Chameleon Wizard or DSDTEditor so that the default PCI root value (i.e. UID of device PCI0) can be changed to 0. This will avoid the need to specify the value at boot time, 0 being the default value for Chameleon bootloader. Can you list your exact system specs (exact Intel Xeon CPU model, chipset, graphics card, LAN card, etc.)?

You can use the same process as detailed for D630 or E6440 to manually create your Yosemite USB installer on which you can directly install Chameleon r2401 for instance (and thereby avoid Clover). You then create a folder /Extra in which you copy the M4300 ML or Mav bootpack (for DSDT + boot plist + SMBIOS plist); I've posted them a few times in this forum. The kexts from /E/E will have to be copied to /S/L/E directly (no myHack tool to take care of that). https://osxlatitude.com/index.php?/topic/6731-d630-nvidia-yosemite/&do=findComment&comment=40833 https://osxlatitude.com/index.php?/topic/7387-dell-latitude-e6440-with-i5-4300m-hd4600-and-1600x900-lcd-mavericksyosemite/page-2&do=findComment&comment=45123 Upon installation, you'll have to manually do the same again knowing that the kext cache will have to be rebuilt with the following Terminal commands: sudo chmod -R 755 /S/L/E sudo chown -R 0:0 /S/L/E sudo touch /S/L/E sudo kextcache -Boot -U /

Most of the answers to your wifi kext patching questions are in front of your eyes... You need to read things with just a bit more attention, it's all there, really. PCI ids = Vendor id + Product id. To look inside a kext, right click on it. You can patch the Info.plist file with a simple tool like TextEditor. To patch a kext found in /S/L/E, make a copy to your desktop, patch the copy and move that patched copy to /S/L/E, replacing the original kext. Then repair permissions and rebuild cache as detailed above. Why do you use a distro? It's often more trouble than good. Why don't you make your own vanilla and USB installer with a genuine copy of Yosemite?

No, not OOB, it needs a patch as detailed in the thread I linked above...

Check that you do not have NullCPUPM or SleepEnabler or anything like that in /E/E. In fact, do list the kexts you have in there. There's a good chance EDP replaces tuned up kexts such as FakeSMC by default ones unless you choose the manual optimised choices... Then check your hibernate mode with Terminal command sudo pmset -g. It should be 0. If set to 3 (default value), use the following commands to reset sleep mode to working values: sudo pmset hibernatemode 0 sudo rm -f /var/vm/sleepimage I'm note sure EDP is actually compatible with Yosemite: EDP always relied on myFix and myHack does not support Yosemite... But I could be wrong of course, I've stopped using EDP yonks ago. I found direct packs to be a quicker method as I went along through the years.

I would suggest you set nVidia graphics to "true", not leave it to "false"... DSDT seems to be of E6400 origin, but I presume it works Ok on the E6500. Re: Chameleon, as I said, chances are you simply had an incorrect configuration. You would have needed the attached tuned FakeSMC kext (plugins moved inside), the MBP5,1 SMBIOS profile and P&C states generation selected in the Chameleon boot plist. A recent Chameleon version such as r2377, r2395 or r2401 would have done too. FakeSMC.kext.zip

For the SSDT generator, no need to change permissions. Simply drag the file icon into an opened Terminal window to prepare to run the command; then, just add the parameters for your CPU. Which version of the Broadcom LAN kext did you install? v2.3.5 of approx 82/83KB? BCM5722D.kext.zip Instead of using kext wizard (I'm not 100% certain if works Ok for Yosemite), I'd simply manually copy the kexts to /S/L/E and run the following Terminal commands: sudo chmod -R 755 /S/L/E sudo chown -R 0:0 /S/L/E sudo touch /S/L/E sudo kextcache -Boot -U /

Nothing wrong there. It'll be due to a config.plist configuration issue... Post the file. Which SMBIOS profile does Clover select? Do you need those PS2 keyboard and mouse kexts by the way? You could try and go back to Chameleon.

You would not normally need VoodooTSCSync with a Penryn CPU (it's required for Merom CPU with 945GM chipset). It's most likely a problem of incorrect Chameleon boot plist settings and/or SMBIOS profile. Which Chameleon version did you use? Speeds reported by Clover are indeed correct (the FSB may not run exactly at 200MHz). Can you post your zipped /Extra folder?

@wai, remind us how much you pay for all this, support included? If you found you way round potholes, you must have learnt a few things on the way. Good, that's much better than being spoonfed in ignorance, isn't it?

Nope, it's not supported.... https://osxlatitude.com/index.php?/topic/2120-supportedunsupported-wireless-cards-inventory/

Finally updated to 10.10.1, replacing the vanilla IOPCIFamily kext again by axmanA's kext and the (reinstated) vanilla kernel by Bronya's. Graphics glitches and related applications bugs still present of course, no change of kernel for the time being.

Ouh, that's a totally obsolete pack you got there! Don't use EDP (you can delete the EDP app from Applications folder) and replace your entire /Extra folder by the attached. Then run myFix (quick) and reboot Lion. Extra_D830n_Lion.zip

That LAN card will be supported with the associated Intel kexts. You'll find it in my Vostro200 bootpack or with a Google search. Your installation issues may come from that old low-spec Pentium CPU; I'm not sure it's actually supported by vanilla kernels, even though dual core. Why don't you replace it with a Core2Duo instead? You'll easily find a cheap FSB800/1066 LGA775 C2D E6xxx/E7xxxx on the net...

From memory, I used the default installer settings. But that was an older version; things may be a little different now... Follow what seems appropriate according to the Clover documentation.

Please move your thread to the Dell D4xx section of the forum. You'll need a retail version of Snow Leopard to install it (10.6.0/10.6.3/10.6.8). That ithingie tool is not supported here, you know where to get support for that... With SL, if all you have is a legit' retail SL DVD, you can install Snow Leopard with Nawcom's ModCD. As I've said several times, it'll allow you to, at least, make a temp installation of SL from which you'll be able to make an image of your retail SL DVD and, subsequently, a myHack USB installer (use myHack v3.1.2 for SL) using the process documented in "EDP" menu at top of page.

Please post your /Extra folder.

If you mount your SL DVD, myHack should normally be able to use it to create the USB installer. Failing that, you'd need to create an image of the DVD that you'd then mount and use with myHack. You need to have an existing hack or a Mac to do that of course. Naturally, the alternative is to use ModCD that fully supports the direct use of a retail DVD.

It seems you're confusing BIOS modes, installation parameters and vanilla installations. You should be able to use the config file I posted for the D630 in the sister thread. Whatever the optional parameters and BIOS modes, Clover always provides for a vanilla installation. Non-vanilla installations = distros.

What does the KP message say?

32bit or 64bit mode is just a kernel mode. It's selected through a single bootloader parameter arch=/.

Erm... no driver can make an LCD display a resolution higher than the pixels it actually possesses. Mind you, I once used on a D830 a tool in ML (the name of which eludes me now) that could run the display in a sort of interlaced mode at higher res than the LCD specs, but it was really crap. With an external display, provided the VGA or DVI output is supported on your E6410, you can do what you want within the specifications limits of the external screen or the VGA output.