Hervé

Then you need to base your CellPhoneHelper patch on an existing Gobi/Qualcomm entry. From memory, there aren't that many in the Info plist. You may also look for other devices that could be based on that chipset.

Well, what chip vendor did you use? What's the chip used on that card? Do not confuse programmed PCI ids of WWAN modules with real identity of the underlying hardware... The real hardware determines the card model to select for subsequent kext patching. You can't just pick any existing model, change the PCI ids and expect the WWAN module to work.

No, not really. A fresh install is a fresh install, regardless of the target HDD. The current one is GUID partitioned, i.e. no MBR patch involved? I'll try a fresh install of 10.6(.0) myself later on and will give you the complete pack that will not require any subsequent EDP involvement.

And you're starting from 10.6(.0), right?

Do you have the LoRes or the HiRes LCD model?

Then your /Extra folder is incorrect. Can you post it up? You've downloaded & used the correct pack, right? Try and boot with -f -v flags and tell us where system KPs.

Well, it's much closer to you than you think. Think like Spock...

Make sure the BIOS is configured as per recommended settings in dedicated pinned thread. If you have an Intel wireless card, remove it or disable it, it can cause KP and it's not compatible.

If you already use a patched DSDT file and need to apply new patches, you simply start from the existing file, not from a new extract or you would lose all existing patches. In the present case (BCM4352), a DSDT patch is not necessarily required; you may simply patch the Broadcom wireless kext with your own card's ids (eg: DW1550 -> PCI ids 14e4:43a0). https://osxlatitude.com/index.php?/topic/2120-supportedunsupported-wireless-cards-inventory/ Then, read this too.

Never really expected it but since Bronya published a new Yosemite AMD kernel... Works quite well on the Precision 670! axmanA's contribution to IOPCIFamily kext was again necessary to fully support my GeForce 9800GT with MacPro3,1 SMBIOS profile. For the rest, it's just the same kext pack + DSDT. Yosemite was installed the "usual" way now: manual creation of USB installer + Clover or Chameleon bootloader on USB installer. I used Chameleon r2401 with kexts copied to S/L/E, copied the extracted kernel file to /S/L/K and rebuilt the cache. Yosemite can then be safely booted (to avoid white/gray screen). With Chameleon bootloader, use attached kernel (placed in /S/L/K or at partition's root as mach_kernel), attached /Extra and replace /S/L/E/IOPCIFamily by axmanA's modified kext. Then rebuild the cache with: sudo chmod -R 755 /S/L/E sudo chown -R 0:0 /S/L/E sudo touch /S/L/E sudo kextcache -Boot -U / Bronya_10.10_kernel_RC2.1.zip axmanA_Yos_IOPCIFamily.kext.zip Precision670_Yos_Pack.zip With Clover bootloader, same idea with kernel/kexts/DSDT (to be placed in all appropriate /EFI/CLOVER subfolders) and use the attached config.plist file: config.plist.zip Many defects remain, mostly graphics related. However, it's early days for Yosemite AMD kernels so things will improve in coming weeks and months. It's a start and a rather good one I think.

Ok, so you're not installing 10.6.5 then but a lower version. With the right D630 Intel X3100 bootpack (HiRes or LoRes), you should have no issues at all. Is there a reason why you would only update to 10.6.5, not 10.6.8? You screenshot shows Darwin 10.0.0, so that's clearly not 10.6.5 but 10.6(.0)! You're not telling us everything or the proper things... If you're installing 10.6(.0) remove the AppleACPIPlatform kext from the bootpack as it is v1.3.6 from 10.6.8. You can safely run off the vanilla version all the way to 10.6.8.

Use Pacifist! Or just download the binaries dmg from one of Kozlek's repositories.

10.6.5 is not a retail version, so you must be using a distro or a real Mac backup media and that does not work because it does not have all the necessary installation file. You must install with a full retail version, i.e. 10.6, 10.6.3 or 10.6.8. To install SL, use myHack v3.1.2 + retail SL + the right bootpack and you'll get through in no time.

In Terminal: sudo chmod -R 755 /System/Library/Extensions sudo chown -R 0:0 /System/Library/Extensions sudo touch /System/Library/Extensions Wait a few minutes and check timestamping of kextcache file in /System/Library/Caches/com.apple..../Startup If no visible update, use command sudo kextcache -system-prelinked-kernel

You can try and follow the same process as detailed/explained for other cards: identify the chip and chip vendor, then modify the CellPhone kext accordingly.

Perfectly normal: a PC cuts off power to USB ports when going to sleep. Some laptops have the option to retain power, but only when mains are plugged in.

For the USB ports, try the following: remove AppleHPET kext from /S/L/E (keep a backup somewhere) rebuild cache with Terminal commands sudo touch /S/L/E + sudo kextcache -Boot -U / reboot

Well, obviously the arch=i386 option should only be used once MPLF has been applied. During initial "vanilla installation", use 64bit native mode (without graphics acceleration) of course, or you won't be able to boot ML. The pack I posted comes from a D620 running MPLF ML 10.8.5...

The guides were written at a time where EDP was different from what it has become now. But I'm not going to rewrite those guides. As stated above, with the above /Extra, you can basically bypass the EDP step; it's not required. Yes, Chameleon Wizard is the correct and easiest way to modifiy boot flags. Rebuilding cache is not linked at all to Chameleon flags. It's directly to kexts manipulation, so run the command to rebuild 32bit kext cache as myFix (quick) will have a tendancy to rebuild 64bit kext cache (ML being normally a 64bit-only OS).

It's highly likely that current EDP messes things up with this particular special MLPF setup but it may well be that you're not choosing the correct EDP options. Dell Latitude D Series with Intel GMA950 graphics require the well-known brigthness fix (i.e. an older Intel frame buffer). Replace your current /Extra by the attached one, add any specific kext you might need for wifi or anything else that might be required and run myFix (quick). You won't need EDP any more. D620_HiRes_MLPF_Extra.zip HWMonitor.zip NB: The DSDT contains a reference to a DW1395 wireless card; it is just cosmetic, so you can safely change that to whatever card you have, just make sure to adjust the string buffer (i.e. the number of characters) too.

How about you go to your nearest FNAC store and grab the info off a real Mac?

Just follow the same path as for previous WWAN modules as documented in R&D->Network forum section where there is an existing thread for that particular module. Please use the forum Search facility.

We don't really support or discuss Ozmosis here. It's kinda rare due to the limited boards that can support it and you probably know where it is usually discussed...

Off-topic. Note that this is just cosmetic. You could put 10GHz if you wanted to!

Moved on to Yosemite... Good news: everything that works under Mavericks also works under Yosemite. Installation process was the same one as I previously used for the D630n, i.e. manual USB installer creation + Clover boot loader: Mount InstallESD.dmg found in Install OS X Yosemite.app/Contents/SharedSupport Then mount BaseSystem.dmg (hidden file) open /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg Use Disk Utility to restore the contents of BaseSystem.dmg on a USB key (or HDD partition) formatted Mac OS extended (journaled). Remove link for Packages in folder System/Installation of your USB key rm /Volumes/OS\ X\ Base\ System\ 1/System/Installation/Packages Copy folder Packages located in InstallESD.dmg to folder System/Installation of your USB key cp -R /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System\ 1/System/Installation Copy the 2 hidden files (BaseSystem.dmg & Basesystem.chunklist) of InstallESD.dmg to the root of your USB key cp /Volumes/OS\ X\ Install\ ESD/BaseSystem.* /Volumes/OS\ X\ Base\ System\ 1 | For those who want to use Clover as boot loader: Install Clover_v2k_r2695.zip (or later) to your USB key. Configure your config.plist to boot with option "kext-dev-mode=1" as follows: <key>Boot</key> <dict> <key>Arguments</key> <string>-v kext-dev-mode=1</string> </dict> * About option "kext-dev-mode=1": in Yosemite, "unsigned or malsigned" kexts will not be loaded. To use such kexts, the restriction can be lifted by adding option "kext-dev-mode=1" at boot phase. Copy all your kexts (FakeSMC.kext, etc.) to EFI/CLOVER/kexts/10.10 (consider this the "kext" boot pack). Grab kexts from the Mavericks boot pack. Copy the SSDT + Yosemite-specific DSDT to EFI/CLOVER/ACPI/patched E6440_HD4600_Yos10.10_DSDT.aml.zip Adjust Clover config.plist as required (you can use this file E6440_HD4600_Clover_config.plist.zip). Start your USB key. The OS X installer should then load. Proceed with installation as usual. The DSDT differs from the Mavericks version in the sense that it injects fake desktop HD4600 id 0x0412 to replace mobile HD4600 id 0x0416. The reason for this is that Apple did not include support for Mobile HD4600 in their Yosemite Azul framebuffer and AppleIntelHD5000Graphics kexts. In that same sense, those 2 kexts also require to be patched to add/inject the mobile HD4600 id 0x04168086 in the Info plist and binmod the kext binary file to replace desktop HD4600 id (86 80 12 04) by mobile HD4600 id (86 80 16 04). All this is quite extensively documented on the web and results from the work of several well-known Hackintoshers like Pike.R.Alpha or RehabMan and others... The following patched kexts should be copied to /S/L/E to replace the original ones (keep a backup somewhere). AppleIntelFramebufferAzul.kext.zip AppleIntelHD5000Graphics.kext.zip You may also do the same with the following patched kext in order to avoid the corrupt screen on Yosemite desktop initialisation. IOGraphicsFamily.kext.zip For those who wish to use Chameleon instead of Clover (you can safely use r2395 or r2401 and possibly above): copy the Haswell-patched kernel to be placed as is at Yosemite partition's root or in /S/L/K as "kernel" to replace the vanilla file (here again, keep a backup).Haswell-patched 10.10 kernel available here create /Extra folder with Yosemite-specific DSDT + SSDT + SMBIOS & boot plists using the following pack:E6440_i5-4300M_HD4600_Yos-Pack.zip E6440_i5-4300M_HD4600_Yos-Pack#2.zip E6440_i5-4300M_HD4600_Yos-Pack#3.zip E6440_i5-4300M_HD4600_Yos-Pack#4.zip E6440_i5-4300M_HD4600_Yos-Pack#5.zip copy the Yosemite pack kexts to /S/L/E, replacing any vanilla kext (keep a backup beforehand); alternatively, copy kexts to /L/E open Terminal and rebuild permissions and cache with 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 / (replace /S*L/*E* by /L*/E* if you copied kexts to /L/E) With Chameleon, it's critical to rebuild the cache with above 4 commands or the installation will become unbootable. Chameleon cannot boot Yosemite without cache! As such, bear that in mind any time you add or modify kexts in Yosemite. Remember to set hibernate mode to 0 (zero) and to remove /var/vm/sleepimage. The system requires additional tuning so additional posts will follow in due course. Again, other E6440 laptops fitted with same graphics hardware config (GPU + LCD) but different CPUs will require a different SSDT table than provided in the above pack (can be looked up on the web or created with SSDT generator tool -> See RampageDev's blog for detailed guide). In such cases and in order to avoid CPU power management-related kernel panics (KP), NullCPUPowerManagement kext is recommended until the CPU-specific SSDT is generated. The kext just needs to be added to /Extra/Extensions or /S/L/E.