Jump to content

Hervé

Administrators
  • Posts

    10013
  • Joined

  • Last visited

  • Days Won

    560

Everything posted by Hervé

  1. It does! It's what I use in my D630n. -> https://osxlatitude.com/index.php?/topic/2120-supportedunsupported-wireless-cards-inventory/
  2. I found those kexts had to be placed in /S/L/E (would not work in /E/E + myFix quick or full). I then manually set permissions and rebuilt cache: sudo chmod -R 755 /System/Library/Extensions sudo chown -R 0:0 /System/Library/Extensions sudo kextcache -system-prelinked-kernel I'd also suggest you redo your USB installer and boot with -f flag (or UseKernelCache=No) to see if it makes any difference. Which Mavericks version are you installing by the way?
  3. If you're booting a post-10.9.1 version, let me tell you that I encountered a similar issue on my old legacy Precision 670: very slow boot process and sort of hanging at "BootCacheControl: Unable to open /var/db/BootCache.playlist: 2 No such file or directory", though the LED would stay on; things were basically taking for ever to load. I found out that replacing AppleACPIPlatform + IOPCIFamily kexts by those from 10.9.1 actually fixed things. You may want to try that (keep a backup of originl kexts somewhere), the 10.9.1 kexts are available here. The post also links to the original IM post that gives explanation of code changes affecting nVidia graphics cards from 10.9.2. This being said, I'd be surprised if that were your actual problem (the Optiplex 9020 is such a recent system!) as, outside my Precision 670 oldtimer, I've never had any problems with those youngtimers that are my Vostro 200 and Latitude D630.
  4. For Ethernet, grab the BCM5722D kext from the pack available here.
  5. Well... the FakeSMC kext in my pack was specifically tuned for the D630, but whatever. If things are fixed for you, so be it. Regarding your initial questions: yes, the bootpack is what myHack refers to as "Extra" "can't find" message relates to kernel cache and means your cache was not built properly or is inexistant post v3.1.2 myHack versions no longer prompt for the bootpack at the end of the USB installer creation; you need to re-run myHack manually and opt for "Create Extra" for that. At the end of that process, myHack runs myFix automatically to rebuild the cache. if cache is damaged or missing, boot with -f flag If you have issues using FakeSMC v6.0.1111 kext in the pack I provided (I definitely use it since10.9.3, can't remember if I tested it with 10.9.2), use version v5.2.678 available in the R&D thread on performance tuning. Failing that, you should have just copied the /Extra folder from your existing D630s.
  6. Don't forget the absolute requirement to have Ethernet LAN port as 1st interface (=en0), or an "airport" wireless one. If you do a search on the forum, you'll find the various steps required to get that done. Use Terminal command ifconfig to check things out.
  7. You're allowed to experiment by yourself! If that means trying VoodooHDA kexts, go for it. What have you got to lose?
  8. Here it is: https://osxlatitude.com/index.php?/topic/6638-strange-happenings-after-edp/page-2&do=findComment&comment=39206 … and that pack was provided in response to you!
  9. Search the recent D630 threads, I've posted a full /Extra folder and I suggest you use it as opposed to run the EDP package which has been causing lots of issues for our oldish LatitudeD Series for some time now...
  10. The best way to learn is to experiment by oneself, try, fail and try again. Then start all over again.
  11. You'll need the SSDT specific to your particular i5-2430M CPU for sure, but there's a good chance the rest will be Ok. ssdt_i5_2430m.aml.zip
  12. All kexts need to go to Extra/Extensions (=/E/E), then you run myFix (quick) to install them. If you did not do so, it's normal that nothing works! So: DSDT + SSDT + SMBios & Chameleon boot plists -> in /Extra kexts -> in /E/E You can probably try again with that HP pack + SSDT I gave you if things were not in the right place. If they were, just remove SSDT + AICPM kext from /E/E and just use NullCPUPowerManagement in /E/E.
  13. SSDT will just be ignored with NullCPUPowerManagement, so you can keep it there. NullCPU means just that: no CPU power management.
  14. Indeed, on my E6320, the patched VoodooSDHC kext broke sleep when closing the lid; however, the laptop can still be put to sleep by pressing Fn-F1 or by clicking Apple menu->Sleep.
  15. You have an i7-2720QM, so you're safe to proceed (no such thing as a i7-2720M CPU). At worst, you'd be where you were before... You can start without the SSDT, then add it subsequently.
  16. No, no, no, that's totally different. There is no SSDT.aml file in the boot pack you've used, so nothing you can do. You can't delete a non-existing file... Try as suggested above with the HP's pack and report back afterwards. The pack has patched AppleIntelCPUPowerManagement and tuned FakeSMC kext for MBP8,2. That should hopefully avoid those KPs you're getting about your CPU. Replace the SSDT of the HP's pack by the attached SSDT for the i7 2720QM. This should give you full native speedstep + Turbo boost. SSDT_i7-2720QM.aml.zip
  17. Mario said SSDT, not DSDT. That's if there is a SSDT of course... This being said, I would suggest you try the pack I published for the EliteBook 8560w. As I said earlier, it's very close in terms of specs and that pack does not contain any DSDT, so no risk of HW mismatch. However, remove the SSDT from the pack if you try it out because that SSDT is specific to the i7-2630QM and won't be suitable for your i7-2720QM CPU, for which you'll have to look for an existing SSDT file or make up your own. There are tools to do that, look it up on the web.
  18. How did you install SL? You did not even read my PM...
  19. Thanks to IM member axmanA, the white screen or QE/CI lagging issue is now effectively solved. I've even updated to 10.9.4, running Bronya's 10.9.2 RC7 kernels and everything appears to work well. As described here by axmanA , the problem was due to a combination of driver changes by Apple from 10.9.2 and nVidia some time before. I found out I actually had to replace the IOPCIFamily kext directly in /S/L/E as OS X was ignoring the patched kext when placed in /E/E and installed with myFix (quick). So great news: I can now boot all post-10.9.1 Mavericks version with that patched kext (Chameleon option msibase=0x90 necessary). I was able to retain MacPro3,1 settings (SMBios profile + FakeSMC keys & smc-compatible). I then reverted to IOPCIFamily + AppleACPIPlatform kexts from 10.9.1 and obtained same result (and no need to boot with msibase option): So, I'm pleased to say that the graphics problems encountered since 10.9.2 are sorted and everything seems 100% Ok. I've noticed the odd picture corruption when doing screen dumps, but other AMD kernel users have reported the same, so it's not specific to this system. 10.9.1_IOPCIFamily.kext.zip 10.9.1_AppleACPIPlatform.kext.zip mach_kernel_rc5.zip mach_kernel_rc6.zip mach_kernel_rc6_fix.zip mach_kernel_rc7.zip Reverting to those 10.9.1 kexts also restores the ability to boot Mavericks on the Precision 670 off a USB external HDD, which was also lost from 10.9.2... As a final note, I noticed small graphics artefacts with RC5 so dismissed that one. RC7 appeared the only version supporting proper wake from sleep (the other ones do not wake screen), so I'm sticking to that version at the moment.
  20. AR9485 is unsupported. Look in JakeLo's signature for the shortcut to list of supported/unsupported cards.
  21. You can turn on/off font smoothing through the "General" preference panel if you want to experiment; though I can't say it makes much of a difference. This being said, I've never found the font to be a problem in terms of legibility on any screen. If anything, I'd like it a tad smaller in fact!
  22. Bear in mind that Intel GM45 graphics = GMA 4500MHD, so no graphics acceleration; that chip is not supported by Apple, which renders OS X kinda useless... GMA 4500MHD-based systems are not worth hackintoshing in my opinion.
×
×
  • Create New...