Jump to content

Hervé

Administrators
  • Posts

    10013
  • Joined

  • Last visited

  • Days Won

    560

Everything posted by Hervé

  1. I said to try the (PS2) kext, not the pack! It's obviously not fully applicable to your own E6320 if the hardware differs, it should be clear enough...
  2. Try the kext from the pack posted in the guide here.
  3. Patched kernel for 10.10/10.10.1 and process to build a Yosemite USB installer can be found here.
  4. Why don't you try and report back? It's easy to revert if things then go wrong with OS X...
  5. You should not use those tools then come for support here, in a myHack subsection! It's a little offending. Those tools you used are not supported here, they have their own web site... You'd be better off with a manual Yosemite USB installer creation on which you'll install either Clover or Chameleon. For Chameleon, I recommend version r2401, it works well with all my 10.10. installations. Example: https://osxlatitude.com/index.php?/topic/6731-d630-nvidia-yosemite/&do=findComment&comment=40833 You can actually install Chameleon directly on your USB installer without using Clover 1st. Just make sure to copy all eventual DSDT + boot plist + SMBIOs plist to /Extra folder. Any additional kext you may add will need to go to /System/Library/Extensions.
  6. SSD or HDD mode is set in BIOS, not in Terminal! So go back into your BIOS settings, load default settings, then set the disk mode to AHCI.
  7. Hervé

    e6520 help

    By the way, watch the syntax of Chameleon options, it's very important to ensure the parameters are not ignored: it's kext-dev-mode=1, not kext_dev_mode=1.
  8. Look for the inventory published in R&D->Hardware section of the forum.
  9. Performance tuning: https://osxlatitude.com/index.php?/topic/2673-performance-tuning-with-fakesmc/ Yosemite: https://osxlatitude.com/index.php?/topic/7055-d830-nvidia-yosemite/ If you're unsure about Yosemite, you may opt for Mavericks.
  10. Try with the older FakeSMC v5.2.678 maybe, it's available in the performance tuning thread in R&D->Other Research section. I have not been using Lion since 2012 on my D630n so would have to do a fresh build again to check things out... Maybe by the end of the week... Why don't you opt for Mavericks or Yosemite instead?
  11. Several of the above statements are incorrect, I guess due to lack of knowledge. For instance, the AppleACPIPlatform kext mentioned is actually v1.3.5 or v1.3.6 which comes respectively from 10.6.7 or 10.6.8. These kexts are not expected to work with 10.6.0 or 10.6.3 (the retail versions outside 10.6.8) of course and, clearly, no need to place such kext in /E/E for 10.6.7 or 10.6.8... There is actually no need for those kexts in Snow Leopard at all, the vanilla kexts will do nicely. The rollback to SL's AppleACPIPlatform kext is needed for Lion and ML. The patched AppleRTC kext is required to avoid CMOS reset and will not do any harm at all, quite the contrary... For SL, it's now been long stated that myHack v3.1.2 should be used, not v3.3.1 due to a known bug. The older version is available on request. True, the provided default bootpack is certainly incorrect and the default EDP settings not optimised. That's already been raised but the EDP and bootpack clean-up exercise started last summer has not completed yet.
  12. That's for Mountain Lion (10.8), not Lion (10.7). If you want to install Lion, use only the regular myHack-based process as that's the last OS X version to officially support 32bit kernel mode. Look up for pack + tuning info in the Dell Latitude D4xx support section.
  13. Try additional Chameleon boot options such as npci=0x2000 or 0x3000.
  14. I've posted the full pack in the D4xx section some time ago. Look it up. No further need of EDP required.
  15. 1st of all, check that your HDD mode is set to AHCI in BIOS. Then, try and boot with Chameleon boot option PciRoot=4 as it's very probably the value set in this workstation's BIOS DSDT table (it's the case with most Dell's high-end PCs and workstations). If you don't use a patched DSDT file, once you manage to boot the OS to dekstop, extract your raw DSDT with a tool such as Chameleon Wizard or DSDTEditor so that the default PCI root value (i.e. UID of device PCI0) can be changed to 0. This will avoid the need to specify the value at boot time, 0 being the default value for Chameleon bootloader. Can you list your exact system specs (exact Intel Xeon CPU model, chipset, graphics card, LAN card, etc.)?
  16. You can use the same process as detailed for D630 or E6440 to manually create your Yosemite USB installer on which you can directly install Chameleon r2401 for instance (and thereby avoid Clover). You then create a folder /Extra in which you copy the M4300 ML or Mav bootpack (for DSDT + boot plist + SMBIOS plist); I've posted them a few times in this forum. The kexts from /E/E will have to be copied to /S/L/E directly (no myHack tool to take care of that). https://osxlatitude.com/index.php?/topic/6731-d630-nvidia-yosemite/&do=findComment&comment=40833 https://osxlatitude.com/index.php?/topic/7387-dell-latitude-e6440-with-i5-4300m-hd4600-and-1600x900-lcd-mavericksyosemite/page-2&do=findComment&comment=45123 Upon installation, you'll have to manually do the same again knowing that the kext cache will have to be rebuilt with the following Terminal 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 /
  17. Most of the answers to your wifi kext patching questions are in front of your eyes... You need to read things with just a bit more attention, it's all there, really. PCI ids = Vendor id + Product id. To look inside a kext, right click on it. You can patch the Info.plist file with a simple tool like TextEditor. To patch a kext found in /S/L/E, make a copy to your desktop, patch the copy and move that patched copy to /S/L/E, replacing the original kext. Then repair permissions and rebuild cache as detailed above. Why do you use a distro? It's often more trouble than good. Why don't you make your own vanilla and USB installer with a genuine copy of Yosemite?
  18. No, not OOB, it needs a patch as detailed in the thread I linked above...
  19. Check that you do not have NullCPUPM or SleepEnabler or anything like that in /E/E. In fact, do list the kexts you have in there. There's a good chance EDP replaces tuned up kexts such as FakeSMC by default ones unless you choose the manual optimised choices... Then check your hibernate mode with Terminal command sudo pmset -g. It should be 0. If set to 3 (default value), use the following commands to reset sleep mode to working values: sudo pmset hibernatemode 0 sudo rm -f /var/vm/sleepimage I'm note sure EDP is actually compatible with Yosemite: EDP always relied on myFix and myHack does not support Yosemite... But I could be wrong of course, I've stopped using EDP yonks ago. I found direct packs to be a quicker method as I went along through the years.
  20. I would suggest you set nVidia graphics to "true", not leave it to "false"... DSDT seems to be of E6400 origin, but I presume it works Ok on the E6500. Re: Chameleon, as I said, chances are you simply had an incorrect configuration. You would have needed the attached tuned FakeSMC kext (plugins moved inside), the MBP5,1 SMBIOS profile and P&C states generation selected in the Chameleon boot plist. A recent Chameleon version such as r2377, r2395 or r2401 would have done too. FakeSMC.kext.zip
  21. For the SSDT generator, no need to change permissions. Simply drag the file icon into an opened Terminal window to prepare to run the command; then, just add the parameters for your CPU. Which version of the Broadcom LAN kext did you install? v2.3.5 of approx 82/83KB? BCM5722D.kext.zip Instead of using kext wizard (I'm not 100% certain if works Ok for Yosemite), I'd simply manually copy the kexts to /S/L/E and run the following Terminal 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 /
  22. Nothing wrong there. It'll be due to a config.plist configuration issue... Post the file. Which SMBIOS profile does Clover select? Do you need those PS2 keyboard and mouse kexts by the way? You could try and go back to Chameleon.
  23. You would not normally need VoodooTSCSync with a Penryn CPU (it's required for Merom CPU with 945GM chipset). It's most likely a problem of incorrect Chameleon boot plist settings and/or SMBIOS profile. Which Chameleon version did you use? Speeds reported by Clover are indeed correct (the FSB may not run exactly at 200MHz). Can you post your zipped /Extra folder?
  24. @wai, remind us how much you pay for all this, support included? If you found you way round potholes, you must have learnt a few things on the way. Good, that's much better than being spoonfed in ignorance, isn't it?
  25. Nope, it's not supported.... https://osxlatitude.com/index.php?/topic/2120-supportedunsupported-wireless-cards-inventory/
×
×
  • Create New...