Hervé

That thread is about full Vanilla ML installation on D630 nVidia models. If you require support for ML on D630 X3100, please start a new one but we won't discuss MLPostFactor internals... Please read the guides, they are very clear about that. PM me if necessary.

Guys, read up the articles we publish on the Web site. No progress on the 4500MHD, consider that dead.

I said that, yes, but that was back in September and things have evolved since. Now, you install whatever you want.

The guide from p1 of this thread should be considered obsolete. Use the guide detailed in the EDP pages of our seb site (click on EDP tab at the vey top of this window). We also have a guide to install and run ML on D630 X3100. And it's fully compatible with our EDP package. In a nutshell, whether for Lion of ML: - prepare your myHack installer with your downloaded Mac OS installation app + OSXL bootpack - install Mac OS X - after 1st reboot, download and install EDP - do an EDP System Build for your specific D630 model Thats it. You may only proceed with some manual tuning if you have a wireless card like a DW1395 or any other one that is not natively supported by OS X and not covered by EDP. Apart from that, nothing else to do really.

Re: ML -> look at the web site's article about ML on "unsupported" systems, then at the associated guides...

I'm not running Lion but ML actually! It's not bad, better than Lion I think, but naturally not performing like a F1... I still believe the best OS on those little toys is SL.

I recently installed SL 10.6.8 on a 32bit D420 using our usual procedure: myHack (v3.1.2) installer + retail SL 10.6.3 + OSXL bootpack. There was no issue at all and I finalised the installation with EDP5. That D420 was quickly replaced by a 64bit D430 and, although I did not proceed with SL on that model (though I could try it on an external USB drive), I can assure you that the above procedure worked for Lion and ML. Things have considerably changed since July 2012: myHack is up to v3.1.2 and EDP up from v1.9.2 to v5.2. I strongly recommend you actually use a myHack installer. I am not aware of any particular issue with that method to successfully install SL on a D430. What are your specs?

->PM

Just to complement this, today I got access to my friend's D830 nVidia (135M) again so I implemented this fine-tuning. The laptop runs ML 10.8.3 on a 2.2GHz T7500 and WXGA 1280x800 LCD, still I used the MBP5,1 settings and all works just fine afterwards: native SpeedStep + GPU clocking. The only differences I see compared to the D630 are the reported GPU core/memory frequencies: 168/100MHz, 275/199MHz and 400/399MHz, where I was seeing higher memory clockings on the D630. Can't see any obvious performance impact though, everything remains very smooth. The reported T° appear excellent too: CPU idles around 45-48°C and GPU around 54-55°C at 168/100MHz. I noticed a Tjmax at 90 in the system log so I manually edited the CPUSensors kext's plist to set Tjmax to 100 (previously, this sort of things was done in IntelCPUMonitor kext), otherwise reported CPU T° are a good 10° lower. XBench 32bit gave me a result of 3063 on 1st run (D830 has 2Go DDR2-667 and 120Go 5400rpm HDD). NB: MB5,1 and/or MBP5,1 SMC ids and SMBIOS profiles can both be used. I did not see any obvious difference between the 2 during my tests (though they were not extensive), although GPU throttling might be a bit quicker with MBP5,1 than MB5,1. MB4,1 settings break native SpeedStep and limit GPU to 275MHz, so that cannot be used. Regardless of the selected SMC id & SMBIOS profile, IDA BIOS mode is not supported with that T7500 CPU: if enabled, FSB speed gets reduced from 200 to 182MHz. That differs from the T9300 with which IDA can be enabled without impact.

Did you install and run EDP to do a System Build? That would normally take care of everything. patched STAC92xx audio drivers and VoodooHDA kexts both work on the D620 nVidia. You should use one of them. Check that you have either in your /E/E folder and, if EDP did not copy them across for some unknown reason, copy them from /Extra/Storage/kextpacks. Remember to re-run myFix (full) afterwards. the D620 nVidia 110M does indeed suffer from that black/gray screen issue you've experienced where the screen (not the computer) does not wake properly from sleep: it stays gray. To recover from that, you can sleep&wake the computer or configure power savings so that screen sleep and computer sleep have the exact same timer. closing the lid should put the laptop to sleep without problems and re-opening it should wake it Ok. Regarding the link you mentioned for sleep, please note that only the hibernation part applies to the D620 nVidia. The BIOS part only applies to the GMA950 model, the nVidia model does not need this BIOS password. However, I recommend that you configure your BIOS settings according to the pinned post on the matter.

May be a more recent Chameleon boot file could fix that little thing; it may just be a processor id # incorrectly interpreted in your current version.

Do you have AppleACPIPlatform kext in /E/E and in /S/L/E? Does your kextcache get re-created when you do a myFix (full)? Look at the file timestamp. The kext cache is normally in /System/Library/Caches/com.apple.kext.caches/Startup folder. I would also do a "repair permissions" for your OS X partition in Disk Utility. You could have issues there.

You are using the HWMonitor version that was very specifically indicated in the article, aren't you?

Haha, not on the public forum. There are facilities like the chat room or PM for that...

Now would be a good time to sit down, browse our web site (and other places on the Net too) and do a little information gathering.

You'll find a wifi card at places that sell computers parts. That naturally extends to on-line places (I'm sure you can think of a well-known one) or private ads. You can lookup for supported models in the inventory published in the R&D->Hardware->Network section of this forum. The D620 takes a full size mini-PCIe card. You can install Snow Leopard on your D620 as is, but it still wouldn't support any Intel wireless card.

You should no longer need those xxxSensors kexts in /E/E. If you lookup within the PlugIns folder of the FakeSMC kext, I'd expect you to see 4 sensor kexts in there. This could be the cause of your issue.

Hmm, "Centrino" is a platform branding, not a CPU model per sé. You should look up in the info page of your BIOS settings, there'll be a CPU identifier (like a 4digit number). If you still have a Windows installation for that laptop, the CPU will be listed under "My Computer -> Properties" or in the device manager.

The D620 supports Intel Core Solo, Core Duo and Core2Duo FSB667 CPUs. Lion requires a computer fitted with a Core2Duo CPU or it won't install. So, you need to identify your exact CPU model before you carry on. Examples of FSB667 CPUs fitting the D620: Core Solo: T1400 & family Core Duo: T2500 & family Core2Duo: T5600 & family, T7200 & family If you have a Core Solo or Core Duo, you're limited to Snow Leopard, unless you upgrade to a C2D, in which case Lion (or even Mountain Lion) will be possible.

Are you using that FakeSMC kext and are you running ML? If so, what kexts do you have in /E/E?

When we did our tests, the difference between MBP4,1 and MPB5,1 were indeed subtle but visible when pushing on graphics. For instance, we would kick off some HD video on YouTube or play a DVD with VLC, click on the HWMonitor menu bar icon to display GPU clocking, then play a lot with multiple Ctrl-UP, Ctrl-LEFT, Ctrl-DOWN. At the same time, we were looking at eventual screen artifacts or video stuttering, whilst keeping en eye on GPU clocking. We felt GPU clocking was ramping up quicker and graphics response was better with MBP5,1. In your case, it may be that there's no difference at all, in which case go with whatever settings look good/best.

If you've used the article published on the Web site, it's clearly explained in there: 8) At the bottom of the Keys list, open down REV, RVBF and RVUF. By default, FakeSMC should be using SMC version 1.30f3 which is displayed in Data field as 01300F00 0003. In the case of our D630 laptops with T9300 CPU and nVidia Quadro NVS 135M, Mario and I tried the SMC version listed for the 15″ MacBookPro5,1 -> 1.33f8 (SMC 1.2). This translated to 6bytes Data 01330F00 0008.

The MBP5,1 SMBIOS and SMC id (15" model) works perfectly on D630 nVidia 135m HiRes fitted with T9300 CPU. The specs of the 15" MBP4,1 (T9300 FSB800, 15" 1440x900, nVidia 8600M GT) looked like a better match, yet SMC id of the 15" MBP5,1 (T9x00 FSB1066, 15" 1440x900 LCD nVidia 9600M GT) gave a better performance, especially with graphics clocking. You 1st need to make sure to choose SMBIOS and SMC ids for Mac models that best resemble your own D830 model. You may find it impossible to match everything within the specifications. With a WUXGA display, try and experiment a bit with the SMC id of a 17" model instead of a 15" model, if that exists. We're dealing with Hackintoshes here, not real Macs, so you can never totally predict what may or may not work with that kind of fine-tuning... In your case, I would try the MB5,1 not the MBP5,1... There was a MacBook 5,1 with 2.0GHz P7350 CPU and GeForce 9400M GPU. That could be a closer match to your own specs. If your graphics card is reported as 8400M, a little DSDT edit will fix it: it's a simple matter of changing a line of text and recompiling the table. Open up your DSDT.aml table with a tool like DSDTEditor, save the DSL file, edit it to replace the nVidia 8400 string to whatever suits you and recompile the table. Your system will then report the graphics card exactly as you specified it in the DSDT table.

Please use the search facility! These questions have been asked and answered many times before.

Some Chameleon boot plists of our booptacks have USBBusFix set to Yes. I have often found that, unless that option is set to No, Lion prompts for a BT keyboard during or after installation (can't remember which), which then requires a USB keyboard to be plugged in. When you manually specify the parameter at Chameleon startup, it overrides the plist settings. If you're proceeding with combo update straight after initial installation, no, there is no real point installing EDP and doing a system build before the Combo update. The critical point is to do an EDP system build before any reboot after the combo update is installed. Great that you got there and can now enjoy your Lion Hackintosh!