Jump to content

Hervé

Administrators
  • Posts

    10026
  • Joined

  • Last visited

  • Days Won

    561

Everything posted by Hervé

  1. You can always try to patch the vanilla Atheros kext. One easy and safe way to do this is to make a copy of the vanilla AirportAtheros40.kext on the desktop (it should be a PlugIn of /S/L/E/IONetworking or /S/L/E/IO80211Family kext - can't remember off-hand) and patch it with your card's PCI ids (168c,001c). Then move the patched kext to /E/E and re-run myFix (quick).
  2. Yes, it's all tweaked & tuned-up, nothing further to do, except any potential wireless card setup if non-OOB model in place. You can easily check up the tweak through: 1) System Profiler->Hardware: look at the model identifier & SMC version reported 2) SMBIOS plist: look at the Mac profile used 3) Run HWMonitor and look at CPU throttling -> All should be as per the article you read. Re: bluetooth Assistant annoyance, go to the Bluetooth PrefPane and uncheck those 2 cases you will immediately notice. You'll easily understand...
  3. Use whatever pack (=/Extra) you're currently using for your Lion installation. As I said, the packs posted for other models contain model-specific DSDTs. Don't expect that to work on your own Inspiron 1520. You can follow the same process as explained in the guides, but use your current /Extra as a pack instead.
  4. Ok, so where are you at now?
  5. Well, if I said those bootpacks should work, I meant the kexts and Chameleon/SMBIOS plists but not necessarily the DSDT table (that's very model specific). So, if you've use the packs "as is", yes, I would not be surprised you encountered problems. 1st try with the Generic bootpack. If you manage to boot the installer and install OS X (SL or Lion), then post the output of Terminal command lspci -nn. This will show us the precise hardware pieces of your Inspiron 1520 (well the large majority of it) and we'll take it from there. NB: with Intel GMA X3100 graphics, you can only run 32bit kernel mode or you won't have any graphic acceleration (i.e.full QE/CI). But there's nothing wrong with running in 32bit kernel mode.
  6. There's no wishful thinking. There's a substantial piece of EDP re-engineering going on and several versions of the same kext to take into account sometimes. There are bugs and probably some database mistakes. Such is life... it's a hobby and, sometimes, people have less spare time...
  7. It seems that once you've booted into Lion, you need to re-run myFix (quick) to repair permissions and rebuild cache (so that you don't have to boot ignoring it). This being said, sometimes myHack.kext proves to be damaged, so you can then delete it from /System/Library/Extensions and re-run myHack app and proceed with Install myHack Utilities to reinstall the whole (myHack) thing.
  8. Clearly, the EDP issues have not been sorted yet. Meantime, you can safely use the pack offered here for your initial Lion 10.7.2 installation as well as for your expected 10.7.5 update. No EDP required. Use it when you create your USB installer and when you install Lion 10.7.2. After that, there should be no issues at all updating to 10.7.5 (combo update or update via Apple menu) without further action. NB: You should answer Yes to all questions about kext removal at the end of the installation, but do not install MBR patch (there's a little bug in myHack v3.3.1 and it's not needed on a GUID partitioned disk).
  9. You could also try with Virtualization Technology on. Surprisingly, I've had a Dell Latitude E6xxx that would not boot Mavericks unless Virtualization was enabled in BIOS...
  10. Possibly. There are indeed AMD8000Controller and AMD9000Controller kexts in 10.10 and that's new. Support might be ported to 10.9 in some later releases. http://netkas.org/?p=1331 http://forum.netkas.org/index.php?topic=8481.0
  11. That list shows names of ATI FrameBuffer personalities. Look those up on the web. To work under OS X, your integrated graphic chip would have to belong to a family of ATI cards/GPUs currently supported by OS X. It's not the case here...
  12. In theory, yes. As I always say, try and you'll see. GT 820M, I can't say I've seen that much...
  13. You should still have same HD3000 graphics...
  14. I would have expected the DSDT to be the same regardless of the CPU; however, if you're using one, the SSDT table would naturally differ from one CPU to another. The SSDT generator tool has been mentioned in many posts, you'll quickly find out about it and it's very to use to make your own tuned-up table.
  15. Pending EDP fixing, you can use the attached /Extra. It covers everything in terms of hardware support so no need for EDP on that front. You'll have full QE/CI, audio, battery management, CPU power management, etc. once you've re-run myFix (quick) and rebooted. D630i_HiRes_10.7.5.zip
  16. Full /Extra below. It contains all the kexts and settings you need to support your complete hardware (i.e. no need for EDP fine-tuning re: hardware). Please note the DSDT in that pack was edited to reflect DW1490. It's just cosmetic and can be easily edited with tools like DSDTEditor (or TextEditor if you decompile it). D430_10.7.5.zip
  17. Nope, clicking HDD means it's started the end of its life. It may last a while like that but prepare to change it. Anyway, that's off-topic.
  18. Assuming your BIOS is configured for PCIe graphics card to be primary, you may need a DSDT patch to inject the card details. You could may try to boot in safe mode (-x flag) to see if that gets you to Mavericks desktop. You may then manage to extract a raw DSDT from BIOS and a full IOReg output.
  19. Glad you eventually got there. Now what you write about partitions in point 2) is misleading. It's perfectly Ok to have several partitions and it's perfectly Ok to have an MBR partitioned HDD, not GUID, as long as you know it and apply the MBR patch if applicable. Your particular experience with an obviously incorrect/unknown HDD partition arrangement does not apply to everyone.
  20. Use the pack I provided, it has everything you need. Don't use EDP for the moment. To me, your problems are probably due to an incorrect or unfinished myHack USB installer. myHack installs Chameleon by the way. You can update to a subsequent version thereafter but it's not mandatory. I would recommend you proceed as follows for your installation: with myHack v3.3.1, build your 10.9 installer on your GPT-partitioned target USB key, having been erased and renamed to XYZ for the avoidance of doubts, re-run myHack and: install myHack utilities on your USB installer install Chameleon on your USB installer install Extra->"own" pack (not Generic) on your USB installer, pointing to the pack I provided and that you'll have downloaded boot the USB installer and proceed with installation on your target HDD/SSD towards the end, myHack should prompt for /Extra installation (use "Your own" and point to /Extra folder of USB installer) and kexts removal. If not, your installer is not correctly made
  21. Here's a good and working complete Mavericks pack for the D830 nVidia. Just tested on a D830n LoRes for a fresh 10.9.4 installation with myHack v3.3.1. BIOS was A16 and configured as per posted recommended settings. Target HDD was a SATA 120Go 7200rpm. D830n_Mav_pack.zip
  22. One never knows, but I doubt your integrated HD3000 would be dying. But if you were up for a CPU upgrade, you would soon find out...
  23. Maybe a little 10.9.4 bug? 10.9.5 will be out soon, hopefully it'll fix this.
×
×
  • Create New...