Jump to content

Hervé

Administrators
  • Posts

    10013
  • Joined

  • Last visited

  • Days Won

    560

Everything posted by Hervé

  1. https://osxlatitude.com/index.php?/topic/8281-e6220-bios-settings/
  2. You'll need the correct CPU for that, i.e. CoreDuo/Core2Duo (a Celeron would probably require a legacy kernel), but it seems this model is based on GMA 4500M graphics which means you'll never enjoy graphics support/acceleration; as such, it's kind of worthless. It does not look like a good platform to run OS X unfortunately.
  3. https://osxlatitude.com/index.php?/topic/7807-nvidia-gpu-performance-tuning-with-agpm/
  4. Those files are of course reusable from Yos to EC.
  5. Or this E6420 guide... All necessary files included in the pack.
  6. You may not have any GPU power management.
  7. i5-2520M is supported. You can grab the associated SSDT in my E6220 guide.
  8. I can confirm Bronxteck's statements. Due to chipset/GPU, this old laptop will only support OS X in 32bit kernel mode so the upper limit is Lion 10.7.5. You may attempt ML with the special MLPF hack but it's kind of awkward and a little buggy anyway. Best to stick to a full vanilla installation. The GeForce 7400 should be supported by the standard nVidia kexts (NV40 architecture from memory) but getting full graphics acceleration may require a DSDT patch or an EFI string injection (more or less the same effect), indeed as per the Dell Latitude D620/D820. No Intel wireless card will be supported and would therefore have to be replaced by a supported model in order to enjoy wireless networking. Regarding an installation guide, I invite you to consult the myHack-based installation instructions found in the EDP->Documentation page.
  9. BCM5722D is available in all D630/D830 packs posted on the forum or in the bootpacks repository. There are several versions which work differently in 64bit-only OS X versions, so make sure to use the latest version available. Look at my D630 El Capitan thread in the R&D section for instance.
  10. Afaik, installing or running OS X on PC hardware has never killed a motherboard! You'd have to run on seriously incorrect settings to damage the underlying hardware, like incorrect power management leading to sustained/prolonged overheating or something to that effect.
  11. Check your hibernation mode in Terminal with command: sudo pmset -g Make sure to disable hibernation as it's a prerequisite to get sleep & wake to work Ok on a Hackintosh. If you have a sleepimage file in /var/vm, delete it: sudo pmset hibernatemode 0 sudo rm /var/vm/sleepimage For additional tranquility, you may even set your sleep image to null device so that no file ever exists and prevents wake/reboot: sudo pmset hibernatefile /dev/null
  12. Like most Intel CPUs since Sandy Bridge, power management is not entirely natively obtained, it requires the generation of a CPU-specific SSDT. Improved power management and boost mode management can then be enjoyed. You don't need NullCPUPM with a Haswell CPU, just the kernel patch. Your poor 3D performance will be due to lack of suitable GPU power management.
  13. Let's keep this thread to its's own topic please: DSDT fix.
  14. +1 You should be Ok running SL or Lion in 32bit mode but you probably won't have any graphics support from ML. It's old hardware...
  15. Yes, it would be most useful to load this 3rd party kext and rebuild the cache.
  16. Make sure to use a SSDT created for your own Sandy bridge CPU, do not use a SSDT table generated for another CPU model.
  17. It only seems to be difficult with the combination of Clover and UEFI mode. I've never had any issues with Chameleon/Enoch and legacy mode on Sandy Bridge or Haswell-based models such as E6220, E6320, E6420 or E6440.
  18. Oh well, with a little 5min search, here you are: https://wikidevi.com/wiki/Netgear_WNA1000M http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true Use the 10.8 package. If the app won't run due to OS X version difference, just extract the kexts from it or modify the Info.plist of the app so that it matches your OS version.
  19. We have a non-exhaustive list of supported/unsupported wireless devices here. The NetGear USB dongle that was tested and reported (by me) is the WNA3100M. You've mentioned a WNA1000M, can you post the PCI device id to identify the chip it's built on? This will greatly assist in establishing whether it is supported or not under OS X and finding the eventual driver. If the laptop is fitted with a RealTek RTL8111 LAN card, you may try the 10.7 drivers posted on their support web site.
  20. Your /S/L/E folder is empty, i.e. the kext files are not written to the USB installer. But I see a lot more is missing in /System/Library... I'd say you either missed a step in the procedure or there is something very wrong with the installation package you're using or the process you're following.
  21. Hervé

    M6700

    None that was discussed or reported here... Please post your M6700 hardware specs (exact CPU model, graphics, audio, LAN, wireless, bluetooth, card reader, etc. Battery, RAM, DVD, we don't care). I suspect it'll be close to the M4700 for which I've seen an existing thread listing an Ivy Bridge CPU and some unsupported discrete AMD GPU. This meant only the integrated Intel HD4000 GPU could work. But, on paper, this kind of laptops can theoretically run Mavericks 10.9, Yosemite 10.10 or El Capitan 10.11. Mountain Lion 10.8 is a bit old and obsolete these days...
  22. Yes, PCs with Sandy and Ivy Bridge CPUs require AICPUPM kext to be patched to avoid kernel panic. Using NullCPUPM voids the vanilla AICPUPM that causes the panic.
  23. Please provide your own E5520-specific hardware specs for items that may vary such as wireless card and bluetooth module. LAN, audio, graphics, are all already known.
  24. Erm... You browse through the USB key file system! I assume you know how to tick the case to display disks in Finder preferences, right?
  25. Ideally, LAN interface should be en0 and wifi en1. This to prevent issues with AppStore, FaceTime, etc. You can easily fix that by deleting the interfaces from Network PrePane and all the plist from /Library/System/Preferences, reboot and let the system auto-discover/install the network elements.
×
×
  • Create New...