Hervé

There's a Mavericks /Extra for the E6320 in the Supported Models with Guides section and in other threads. The CPU-specific item is the SSDT. What you should do is remove the SSDT from the packs, then create your own using the well-known script. Alternatively look for your specific CPU SSDT on the Net, other sites have substantial lists of ready-made Intel "i" Core CPU SSDT files.

http://ark.intel.com/products/75105/Intel-Core-i3-4005U-Processor-3M-Cache-1_70-GHz Do you have full graphics acceleration?

Ok, so half-size mini-PCIe Foxconn T77H047.31 (Atheros AR5B93) card based on Atheros AR9283 chip.

Could be a channel issue if those 802.11n networks operate on channels beyond 11. If you can, check which channels these networks operate on. It was not the case for my own Atheros AR5B91 (a Lite-On WN6600A model), but I had to change the channel that my home wireless network ran on by default to get an 802.11n USB dongle to work properly. My Atheros AR5B91 wireless card supports channels up to #13. -> In SysProfiler/Hardware/PCI: -> In SysProfiler/Network/Wi-Fi (if you wonder about the software versions, please note that I'm up to latest 10.10.2 Beta): I would suggest you check the exact card model. I could not definitely identify it according to the registered information on wikidevi. It's probably the Foxconn T77H047.31. There seems to be discrepancies between Subsystemid (0xE01F) and OUI (0c:60:76), though the wiki could be incomplete of course. You should also verify your antennas connection. https://wikidevi.com/wiki/Special:Ask?title=Special%3AAsk&q=%5B%5BVendor+ID::168c%5D%5D+%5B%5BDevice+ID::002a%5D%5D&po=%3FInterface%0D%0A%3FFCC+ID%0D%0A%3FManuf%0D%0A%3FManuf+product+model=Manuf.+mdl%0D%0A%3FVendor+ID%0D%0A%3FDevice+ID%0D%0A%3FSubvendor+ID%0D%0A%3FSubdevice+ID%0D%0A%3FChip1+model%0D%0A%3FChip2+model%0D%0A%3FChip3+model%0D%0A%3FSupported+802dot11+protocols=PHY+modes%0D%0A%3FMIMO+config%0D%0A%3FOUI%0D%0A%3FEstimated+year+of+release=Est.+year&eq=yes&p%5Bformat%5D=broadtable&order%5B0%5D=ASC&sort_num=&order_num=ASC&p%5Blimit%5D=500&p%5Boffset%5D=&p%5Blink%5D=all&p%5Bsort%5D=&p%5Bheaders%5D=show&p%5Bmainlabel%5D=&p%5Bintro%5D=&p%5Boutro%5D=&p%5Bsearchlabel%5D=…+further+results&p%5Bdefault%5D=&p%5Bclass%5D=sortable+wikitable+smwtable NB: It's a separate issue, but I also note that your wireless card is set as en0; ideally that should be your LAN card so that you can connect to AppStore, get FaceTime to work, etc.

Antennas correctly connected? MAC address filtering? Wireless switch in the ON position? Try and boot without cache then rebuild it. The card definitely works OOB.

Strange that your DCPIManager window reports a Xeon CPU and a desktop Intel HD4600 GPU (8086:0412), unless you're injecting that through Clover of course. No sign of the nVidia discrete card either (maybe you've disabled it). You graphics lagging will be due to the fact that Yosemite does not natively support the mobile version of Intel's HD4600 GPU. As such, you need to patch the kexts/FrameBuffer to handle it. The process is described in the Dell Latitude E6440 guide I linked in my 1st response to you. Brightness control is directly related to the fact that you don't have graphics acceleration at the moment. For audio, what are you using? If nothing specific at the moment, try a recent VoodooHDA (v2.8.4 for instance)/AppleHDADisabler kext set and see how it goes. VoodooHDA.kext.zip For Bluetooth, check the USB section of your SysProfiler. If the Bluetooth controller appears, you should be able to get that Intel module working (but only the bluetooth part, the wireless part is a definite no). External mouse + USB3.0 are clearly linked. Does your laptop have USB3.0 ports only or are any USB2.0 at all? USB2.0 ports should work OOB. Try the USB3.0 generic kext. For the Atheros Qualcomm QCA8171, I think the ALX kext should work. It certainly seems to apply to that card according to the listed target PCI ids. ALXEthernet.kext.zip You should also consult this IM thread; it's about the Y510p model, but I'm sure there are common features and things to learn from it.

https://osxlatitude.com/index.php?/topic/2120-supportedunsupported-wireless-cards-inventory/ Make sure your wireless card is activated (in BIOS and/or with any wireless switch on the laptop side) and installed in Network PrefPane. The card will only work with opened wireless networks. The supporting kext needs to be properly installed of course, so check your permissions and cache.

You can't manually adjust SpeedStep, it's automatic and under the control of AICPUPM kext in conjunction with recent/latest Kozlek's FakeSMC kext + SMBIOS profile (once suitably tuned/configured), P + C States generation being activated in the bootloader. I would make sure that your Clover-based installation: . uses same FakeSMC kext (version + key tuning) as the Mavericks installation. Kozlek's latest versions can be used. . uses MacBookPro5,1 profile (set in Clover config). . uses P States + C States generation and nothing else (set in Clover config). Clover normally automatically selects MBP5,1 SMBIOS profile for those nVidia-based D630/D830 models, but if you notice that SpeedStep is not as efficient under Clover, resulting in higher T°, why don't you switch to Chameleon ? It totally supports Yosemite with recent versions such as v2.2 r2395 or r2401 for instance (I use r2401). Later Chameleon releases fully support Yosemite too but I have experienced issues booting Mavericks with v2.3 r2510 on a multi-OS X installation disk.

Indeed, another "iOS" effect...

Morale of the story: don't use distros!

With Yosemite, the "chirping" sound is now a configurable option in the audio PrefPane.

Are you using this one? Works Ok on all my hacks, from Snow Leopard to Yosemite... Alternatively, try DCPIManager:

Try that one. Just verified behaviour on my D630 and all was Ok. Once app is opened and showing IOService info, just do File->Save as...

Use the attached fake STAC9205 pack; it's normally available as an option in EDP. Copy both kexts to /Extra/Extensions, then run myHack->myFix (quick). You should immediately gain audio without even needing to reboot. FakeSTAC9205_pack.zip Please note that Chameleon is a bootloader and KextWizard a tool to manage driver installation. They do not provide any form of hardware support per sé.

You don't need SoundFlower, 'causes more trouble than good. Just use the STAC92xx kexts.

Did you specify any ATI Config value at all? Try those things that were suggested and report accordingly...

Try the attached kexts in /E/E then run myFix (quick). Needs a light finger to move the mouse pointer; a heavier finger does scrolling within the active page (by rolling up/down your finger tip, finger heavily down, without actually lifting the finger). Archive.zip

Try AtiConfig=Hoolock + GraphicsEnabler=Yes as manual Chameleon boot options (use exact same syntax and casing). If it works, just add them to your boot plist. Use Chameleon Wizard if you need assistance.

You're somehow mistaken. First of all, myHack does not provide support for any hardware per sé, it's an OS X installation tool. Hardware support is provided by drivers (i.e. kexts), patched DSDTs and/or SSDTs, patches, etc. myHack provides assistance in such drivers or files installation, nothing else. If you include the necessary drivers or suitably patched drivers in the bootpack, myHack will automatically support the related hardware. Clover is no different in that respect, it's just that it provides a lot more built-in features to cover hardware. It's therefore a lot richer but, also, a lot more complicated to understand. Secondly, current version of myHack does not support Yosemite installation. As such, you indeed have to resort to alternative methods to install Yosemite. Like Chameleon, Clover is a bootloader, not an installation or USB installer creation tool: it does not create the USB installer like myHack does for Mac OS X/OS X versions from SL 10.6 to Mavericks 10.9. myHack uses Chameleon as bootloader. Clover is installed on a USB installer once it has been created and it is also installed on the target partition once OS X has been installed on it. However, you can easily manually create your Yosemite USB installer, on which you then install Chameleon. There are tons of guides related to that on the usual forums, this one included (look here or here for instance). This manual method is basically what myHack more or less does in the background without users knowledge. It hides all the complexity to provide a nice and easy tool to the user. This being said, it's also nice to know the actual details, at least for educational purposes... To sum things up: Clover = sophisticated bootloader with built-in advanced hardware detection support; somehow difficult to understand / install / use Chameleon = goold old very reliable bootloader with limited hardware detection support. Very easy to understand / install / use myHack = OS X USB installer creation tool + advanced driver installation & management tool

Hi, a few questions: . which OS X version are you trying to install? . what are the problems you experience with myHack? I'm not a great fan of Clover (you need a Clover university degree to understand it in my opinion), so I tend to stick to myHack and Chameleon as much as possible.

You'll find it easier to use Chameleon Wizard, it offers a nice UI where you simply tick a case for 32bit kernel mode and then save the config in the boot plist.

https://osxlatitude.com/index.php?/topic/2120-supportedunsupported-wireless-cards-inventory/ Cards from Apple Macs are of course supported.

Use Terminal command lspci -nn (need lspcidrv kext installed and loaded) to post us your exact system specs. Difficult to know what audio, Bluetooth or LAN hardware you have otherwise. Intel wireless cards are not supported so you'll have to replace your card by another model or use a USB dongle. USB3.0 ports are usually working once you add the generic USB3.0 kext. Alternatively, some systems just require the AppleHPET kext to be removed (it's known to affect USB3 functionality). Bluetooth may require a patch, depending on the hardware or it may be fixed with AppleHPET removal. Mobile Intel HD4600 is not natively supported by OS X (only the desktop version is) so you have to do some patching to obtain full graphics acceleration. There's a good thread about it on InsanelyMac forum or you can refer to existing Dell threads here on that same matter. You can start with my guide for the Latitude E6440 for instance.

Corrupt download? Try with another copy or another version.

Look up the wireless card inventory in the relevant R&D->Hardware section of the forum.