Hervé

One critical point for Mavericks (somehow ML too) is the graphics card fitted to these workstations. Dell tended to fit nVidia Quadro FX card and they're hardly supported under Mac OS. So be prepared to swap your graphics card for ML and/or Mavericks.

There are various ways to do that: boot a myHack USB installer that had the lspcidrv kext in /E/E -> should allow you to open up a Terminal window to type lspci -nn command If the PC still runs Windows, look at the various devices listed in Windows Device Manager use various Windows tools such as those listed by Dinesh in his R&D->DSDT/SSDT thread look up the published specs in the user manual (available off Dell's web site) etc, etc. Generally speaking, the main things to look at include CPU model, chipset (HDD controller), amount of RAM, model of graphics card (whether built-in and/or PCIe add-on), HDD type, audio chip, LAN and/or wireless card model, BIOS version (the BIOS settings can be important too). Have a look at the description I had made of my Precision 670 (a model much older than yours) in the EDP->Supported Models with Guides->Dell forum section. By the way, didn't you ask the same questions about ML for that particular machine in that same section last summer?

The M4300 is very close to the D830 (and therefore somehow to the D630), so it would have been much better to use the D830 bootpack rather than the D820 if there was no M4300 bootpack at that time. The DSDT are more likely to be similar had you used the D830 bootpack. Naturally, what you ought to do these days, is use the actual M4300 bootpack. I took delivery of a WSXGA+ M4300 today and it'll soon be running Mavericks. I'll be able to report how the installation goes

We need to look at our various bootpacks. Something was probably set incorrectly at generation. We know the workaround meantime, so the problem is kind of minor.

I will need to re-test DW1390 and DW1490 with Mavericks, it may well be that Apple have now done to the BCM4311 chip (DW1390/DW1490) what they did to the BCM4312 (DW1395/DW1397) from ML 10.8.4.

What's in the Chameleon boot plist of your USB installer?

MBP5,1 gives best graphics performance, whilst CPU speedstep still works as expected (no speedstep when choosing MBP3,1 profile).

All the models listed as supported can be a good fit. Just choose according to market availability, $$$, card size and compatibility with your target OS.

Are you still running default FakeSMC 4.0 with SMC id 1.30f3 and default SMBIOS plist? If so, follow our article about performance tuning to adjust your system's parameters.

Bootpack could have an erroneous Chameleon boot plist set for 32bit kernel mode. Try to boot with option: arch=x86_64.

1st of all, only use the correct bootpack; you can't go wrong, there's only 2 of them: one per LCD screen resolution (we assume you know what resolution your D630 LCD has). Then, check your BIOS parameters and configure them as per the recommended settings specified in the pinned thread in this D6xx section. Have a USB keyboard/mouse at hand because you'll probably find that, even if you manually enter boot option USBBusFix=No, your built-in keyboard and/or trackpad won't be recognised. If you play with the Extra folder (which I would not recommend you do), you need to re-run myFix on the target media, whether on your USB installer or on your OS X partition. Generally speaking, you should install the D630 bootpack on your USB installer using the myHack->Install Extra menu option. That is the safest way to do it. If you want to intall and run Mountain Lion, head over to the EDP->Supported models with Guides forum section.

Only applications specifically designed to use multi-threading will use this logical core functionality. It's an application implementation/usage more than an OS one. As such, it's perfectly normal to see different load/usage per logical core. I encourage you to search the Net about that. Re: FakeSMC, look at our article about performance tuning, it contains some of Kozlek's early and more recent FakeSMC kexts; You can also use Google of course, you'll quickly get the correct URL...

Again, look at the list of supported/unsupported wireless card in R&D->Hardware->Wifi section of the forum.

Update to 10.6.8, then re-run the EDP System Build. If VoodooHDA #3 does not work, try the Patched AppleHDA settings offered in the option list.

No, use MBP5,1 SMBIOS. MBP3,1 won't work. Please follow instructions.

That's just because you have a quad core CPU with 2 threads per core, i.e. 8 logical cores. http://ark.intel.com/products/64891/Intel-Core-i7-3720QM-Processor-6M-Cache-up-to-3_60-GHz You may have to change to one of Kozlek's FakeSMC kexts and update to the proper SMC id to get your 8 logical cores recognised. Right now, it looks like you're running default FakeSMC v4.0 with default SMC id 1.30f3.

Just use Chameleon Wizard for everything.

DW1395 does not support secured wireless network in ML 10.8.4/5 and Mav without reverting to previous airportd. It's clearly indicated on the post I mentioned above. Your laptop may be running at full CPU speed all the time and overheating. I would suggest you read the article about performance tuning in Articles section of our web site. I'm sure you would have much to gain from it.

What machine are we talking about here, let's start by the beginning to clarify everything. Trackpad kexts are called xxxPS2xxx. Did you replace the existing PS2 kexts you found in your /Extra/Extensions by those found in the same folder of the USB installer? Try that and re-run myFix (full), then report back.

I have the same issue, I can no longer log in and all my attempts show that the account needs activating. I've given up I admit... I have the NVRam.dylib module installed, so doubt it's linked to that.

I was actually praising the fact that you did your research on your own and met success without any spoon feeding as is too often the case these days unfortunately. But that's the way the world has gone I'm afraid... Anyway, once again, congratulations for your success. Those Intel wireless projects are actually quite old, only met limited success and have long been abandonned. But, yes, this was very interesting dev work at the time.

Hi, the 1st thing you should do to get help is provide the full specs of your machine. Without this, we're blind. Re: wireless, you should check the inventory published in R&D->Hardware->Wifi forum sectiopn as you may have one of those models that needs airportd modification. But we'll see that once you've provided those laptop details.

Mmm, weird. Well, I will own a M4300 beginning of next week, so I'll be able to work on this one with my own hands.

Ok, I understand better now, I thought you were asking about increasing the on-board video memory which is not possible. Anyway, if performance is not great, it's unlikely to be due to unsufficient Video memory, but more to non-optimum platform profile settings. I recommend that you read the article about "Performance Tuning with FakeSMC" in the Articles pages of the web site and adjust your laptop's settings accordingly. I can tell you that I do not experience any particularly poor performance on my D630 nVidia 135M with FakeSMC v5.2.678, SMC id set at 1.33f8 and SMBIOS profile set as MacBook Pro5,1. We tested this profusely a few months ago and reached top optimal performance, including graphics performance. On 64bit Mavericks 10.9, you may actually use any recent release of Kozlek's FakeSMC kext + HWMonitor app. Be cautious as the downloaded package will install the FakeSMC kext (with plugins inside) in /S/L/E. You need to move that back to /E/E and re-run myFix (full) for the kext to be used subsequently after reboot.

No, it's not possible. The Dell manual is pretty clear about that point: