Hervé

Guys, we're looking at it; thanks for reporting it.

'looks like a nice laptop to Hack... Have you thought about trying out a Vanilla install with myHack as opposed to a distro? This would help us re: EDP integration.

Yes, it's an acceleration/boost feature (i.e. a frequency/rate increase) available on some Core 2 Duo CPUs where 1 core can briefly run at a higher multiplier/speed than the maximum nominal speed whilst the other core is idle. A kind of ancestor to Turbo boost modes of Core "i" CPUs.

 

Let's take the example of a Core2Duo T7500, a very common CPU on laptops such as the Dell D630:

• FSB: 800MHz quad-pumped (i.e. 4 x 200MHz)
• nominal max multiplier: x11
• nominal max. frequency: 2.2GHz (i.e. FSB x multiplier -> 200 x 11 = 2200MHz)

Dynamic Acceleration allows this T7500 CPU to briefly run 1 core at x12 = 2.4GHz whilst the other core is idle.

 

More info at:

http://en.wikipedia.org/wiki/Intel_Dynamic_Acceleration

http://www.cpu-world.com/Glossary/D/Dynamic_Acceleration_technology.html

http://www.intel.com/cd/channel/reseller/apac/eng/products/mobile/processors/core2duo_m/feature/index.htm

 

The reason we mention IDA is because, although it's fully supported in Windows for all C2D that are IDA-capable, it's not the case with Mac OS X. For instance, with IDA enabled in BIOS, we notice reduced/lower (~10%) FSB and CPU speeds with Merom T7x00 CPUs in Mac OS X. However, FSB and CPU speeds are properly reported when IDA is disabled. On the other hand, we don't notice this misbehaviour at all if IDA is enabled with Penryn T9x00 or T8xxx CPUs.

Well, you should be ok with the OSXL procedure then. With Lion, I recommend booting wuth option "USBBusFix=No" to avoid keyboard issue.

Last updated 13 Jul 2016

- - - - - - - - - - - - - - - - - - - - -

 

Further to our article on the matter, it's probably useful to provide a list of successful settings that provide native SpeedStep and, possibly, improved GPU management on some of our good old legacy Dell laptops.

 

 This applies to Intel Core2Duo/Core2Quad, 1st gen Arrandale i3/i5/i7 (and affiliated Xeon) systems with vanilla AICPUPM

 2nd/3rd gen Sandy/Ivy bridge i3/i5/i7 (and affiliated Xeon) systems require patched AICPUPM kext + generated SSDT

 4th/5th/6th gen Haswell/Broadwell/Skylake i3/i5/i7 (and affiliated Xeon) systems require patched kernel + generated SSDT

 
Dell Latitude D430 Intel GMA950

Dell Latitude D620 Intel GMA950

• with 32/64bit FakeSMC v5.2.678 & plugins version
• SMC keys -> use id of MacBook5,1 i.e. 1.32f8
• SMC compatible -> use "smc-napa"
• SMBIOS plist -> use MacBook5,1 profile from Chameleon Wizard
• Remove CPUMonitor + NullCPUPowerManagement + VoodooPState + SleepEnabler kexts from /Extra/Extensions
• Keep VoodooTSCSync kext in /Extra/Extensions
• Native SpeedStep fully supported through entire CPU speed range
• Native Sleep/Wake with System password set in BIOS + hibernatemode set to 0 and /var/vm/sleepimage file deleted
• No monitoring for GMA950

 

Dell Latitude D620 nVidia Quadro NVS 110M

Dell Latitude D820 nVidia Quadro NVS 120M

• with 32/64bit FakeSMC v5.2.678 & plugins (except GPUSensors) version -> GPUSensors kext causes KP
• SMC keys -> use id of MacBookPro5,1 i.e. 1.33f8
• SMC compatible -> use "smc-napa"
• SMBIOS plist -> use MacBookPro5,1 profile from Chameleon Wizard
• Remove CPUMonitor + NullCPUPowerManagement + VoodooPState + SleepEnabler kexts from /E/E
• Keep VoodooTSCSync kext in /E/E
• Native SpeedStep fully supported through entire CPU speed range
• Native Sleep/Wake with System password set in BIOS + hibernatemode 0 and /var/vm/sleepimage file deleted
• No monitoring for NVS 110M or NVS 120M

 

Dell Latitude D630 Intel GMA X3100

Dell Latitude D830 Intel GMA X3100

• with 32/64bit FakeSMC v5.2.678 & plugins version
• SMC keys -> use id of MacBook5,1 i.e. 1.32f8
• SMC compatible -> use "smc-mcp"
• SMBIOS plist -> use MacBook5,1 profile from Chameleon Wizard
• Remove CPUMonitor + NullCPUPowerManagement + VoodooPState + VoodooTSCSync + SleepEnabler kexts from /E/E
• Native SpeedStep fully supported through entire CPU speed range
• Native Sleep/Wake with hibernatemode set to 0 and /var/vm/sleepimage file deleted
• X3100 monitoring should be supported but appears bugged (it works in 64bit kernel mode, not in 32bit)

NB: With OS X, IDA BIOS activation supported only with Penryn CPUs (eg: T8xxx or T9xxx),  not with Merom CPU (eg: T7xxx)
 
 
Dell Latitude D630 nVidia Quadro NVS 135M

• With 32/64 or 64bit FakeSMC v5.2.678 & plugins version (or later v6.x.xxxx)
• SMC keys -> use id of MacBookPro5,1 i.e. 1.33f8
• SMC compatible -> use "smc-mcp"
• SMBIOS plist -> use MacBookPro5,1 profile from Chameleon Wizard
• Remove CPUMonitor + NullCPUPowerManagement + VoodooPState + VoodooTSCSync + SleepEnabler kexts from /E/E
• From Mavericks onwards, remove AppleACPIPlatform kext v1.3.x from /E/E (i.e. run vanilla kext). Use/keep it only for Lion and ML.
• Native SpeedStep fully supported through entire CPU speed range
• Native Sleep/Wake with hibernatemode set to 0 and /var/vm/sleepimage file deleted
• GPU/memory clockings showing at 168/100, 275/300 and 400/594MHz

NB: With OS X, IDA BIOS activation supported only with Penryn CPUs (eg: T8xxx or T9xxx),  not with Merom CPU (eg: T7xxx)

 

 

D830 nVidia Quadro NVS 135M/140M

• With 32/64 or 64bit FakeSMC v5.2.678 & plugins version (or later v6.x.xxxx)
• SMC keys -> use id of MacBookPro5,1 i.e. 1.33f8
• SMC compatible -> use "smc-mcp"
• SMBIOS plist -> use MacBookPro5,1 profile from Chameleon Wizard
• Remove CPUMonitor + NullCPUPowerManagement + VoodooPState + VoodooTSCSync + SleepEnabler kexts from /E/E
• From Mavericks onwards, remove AppleACPIPlatform kext v1.3.x from /E/E (i.e. run vanilla kext). Use/keep it only for Lion and ML.
• Native SpeedStep fully supported through entire CPU speed range
• Native Sleep/Wake with hibernatemode set to 0 and /var/vm/sleepimage file deleted
• GPU/memory clockings showing at 168/100, 275/199 and 400/399MHz

NB: With OS X, IDA BIOS activation supported only with Penryn CPUs (eg: T8xxx or T9xxx),  not with Merom CPU (eg: T7xxx)

 

 

Dell Precision M2300 nVidia Quadro FX 360M

Dell Precision M4300 nVidia Quadro FX 360M

• With 32/64 or 64bit FakeSMC v5.2.678 & plugins version (or later v6.x.xxxx)
• SMC keys -> use id of MacBookPro5,1 i.e. 1.33f8
• SMC compatible -> use "smc-mcp"
• SMBIOS plist -> use MacBookPro5,1 profile from Chameleon Wizard
• Remove CPUMonitor + NullCPUPowerManagement + VoodooPState + VoodooTSCSync + SleepEnabler kexts from /E/E
• From Mavericks onwards, remove AppleACPIPlatform kext v1.3.x from /E/E (i.e. run vanilla kext). Use/keep it only for Lion and ML.
• Native SpeedStep fully supported through entire CPU speed range
• Native Sleep/Wake with hibernatemode set to 0 and /var/vm/sleepimage file deleted
• GPU/memory clockings showing at 168/100, 275/199 and 400/399MHz

NB: With OS X, IDA BIOS activation supported only with Penryn CPUs (eg: T8xxx or T9xxx),  not with Merom CPU (eg: T7xxx)

 

 

 Edit SMC keys/compatible of attached fat-binary FakeSMC kext as required. Use attached HWMonitor app for hardware monitoring (under SL, use older HWMonitor app v2.3.20).

FakeSMC_v5.2.678.zip     FakeSMC_v5.2.678_no-GPUSensors.kext.zip     HWMonitor_v5.2.678.zip     HWMonitor_v2.3.20.zip

Thanks for the info guys. As a matter of fact, the report of the DW1510 not working OOB turned out as a red herring...

To prevent BIOS resets, try and use "Patched_10.7_AppleRTC.kext" (put it in /E/E and repair permissions + rebuild kext cache -> myFix (full) if you're using myHack).

Patched_10.7_AppleRTC.kext.zip

 

You say your wifi card is supported, but which model is it?

How about PCI ids (Vendor + Device)?

Mmm, external keyboards usually always work on a D630. Do you see your PS2 kexts in /Extra/Extensions? I'd redo a myFix (full) in case the cache or permissions got screwed.

'sounds like you do not have the correct PS2 kextpacks for your machine. But what are we talking about here???

Mmm, -v should give you lots of text until the very last moment where OS X goes to Desktop display.

 

Try: -f -v GraphicsEnabler=No

Great that you could confirm the DW1510 works OOB (as expected) and with various encryption method whether rebranded or not.

 

@desterly, in that case, make sure you re-instated the original IO80211 kext in /S/L/E ok and that your cache was properly rebuilt after running myFix (full). Check the kextcache file timestamping in /S/L/Caches/com.apple.kext.caches/Startup.

Hi, would it be possible to get more details about that DW1510 rebranding? What needs to be done and how? What is the card reported as before and after rebranding? Preferably in a dedicated thread in R&D -> Network section.

 

it seems it may not be fully supported without such rebranding: https://osxlatitude.com/index.php?/topic/1617-mountain-lion-anyone/page-20

You should not touch S/L/E except for the removal of the ACPI kext. Leave the IO80211 untouched in there, only the patched kext from /E/E is to be removed.

 

This being said, I read that those who have the DW1510 working properly appear to have a rebranded version. I don't have the details as far as this rebranding is concerned, but it's possibly something that makes the card appear as an "Airport Extreme" or something like that instead of the 3rd party card. How is your DW1510 reported in System Preferences?

 

We need to get details of that rebranding process from the people who did it. Apologies, I'm totally ignorant on that particular matter.

Hi,

 

Can you try to boot with -v option  (for verbose) and tell us what you get (error message, last message before it possibly hangs, that kind of thing)?

I probably need to review my guides for 10.8.4, something I have not done yet, but remember that you need to apply MLPF v0.3 to support 10.8.4. I understand v0.22 does not.

 

I'm surprised you have no Ethernet with the BCM5751 kext as that is the kext required to support the built-in Ethernet of the D620; the BCM5722D is usually for the built-in Ethernet fitted to the D630/D830. Maybe you could provide the lspci info for that particular hardware too so that we clarify this point.

 

I take it that, without Ethernet, you never managed to install EDP and make a system build. This would explain why you do not have sound as that is only supported by kexts installed at EDP System Build (the bootpack only contains essential kexts).

 

NB: note that your DW1395 will only support Clear or WEP wireless networks under 10.8.4 (AES is unsupported)...

Can you list your specs? Especially CPU + wireless card.

I understood DW1510 to be supported OOB. Are you using a patched kext for that wireless cards? If so, can you try without?

Mmm, I'll try a new SL installation on my D430 with an external USB HDD and will let you know the outcome.

Safe update for D830 nVidia (with appropriate wifi cards of course - 'had one with DW1490). Deleted ACPI kext from /S/L/E and rebuild permissions + caches and all Ok after reboot.

That does not sound like battery management, does it? Without Apple or Voodoo battery management, you'll have nothing... That would be taken care of by an EDP system build.

Look in your /E/E folder. There's no battery management prior to EDP system build as far as I remember.

No native SpeedStep with MBP3,1 as far as we know...

Which battery manager do you use?

EDP can integrate your machine once you've built it and established all that is required. Updating EDP is not really a forward-process in that respect. It's based on the understanding that the Hackintosh is built and fine-tuned through /Extra folder. We then use this to prepare the EDP system build and boot package.

 

Start by listing your system's specifications and we can take it from there. Ideally, you would try to install SL, L and ML; Maverick in the future...