Jump to content

Bronxteck

Administrators
  • Posts

    5778
  • Joined

  • Last visited

  • Days Won

    124

Everything posted by Bronxteck

  1. yeah the apple installer always puts in a fresh kernel. it does not recycle the one on the installer.
  2. you might have to patch HPET in your DSDT. open your dsdt in an dsdt editor and check to see if your HPET section looks like this Device (HPET) { Name (_HID, EisaId ("PNP0103")) Name (BUF0, ResourceTemplate () { IRQNoFlags () {0} IRQNoFlags () {8} IRQNoFlags () {11} IRQNoFlags () {15} Memory32Fixed (ReadOnly, 0xFED00000, // Address Base 0x00000400, // Address Length _Y10) }) if you only see IRQNoFlags () {0} IRQNoFlags () {8} add this behind it IRQNoFlags () {11} IRQNoFlags () {15} recompile the DSDT save it as .aml and test it hopefully that resolves your issue. another test would be to backup then remove System/Library/Extensions/AppleHPET.kext then rebuild your catches. you can try that before the DSDT edits to see if it really is HPET conflicting and stealing your IRQ values. if it works fine after that then replace the kext and test the DSDT edits for a permanent solution. the problem with HPET can manifests itself as non working devices after sleep, can be USB ports, DVDROM, Wlan, Trackpad basically anything the gets designated an IRQ value.
  3. did you try adding the resolutions.dylib module to the modules folder as for trackpad if you do not like the performance of your existing trackpad try another kext for it. edp had a few different options with different characteristics.
  4. you have to replace or patch the kernel as well on the new install if not you get the issue you describe.
  5. if the wifi is not supported then you need to replace it with a supported one. it is not very expensive swap.
  6. theres a guide here https://osxlatitude.com/index.php?/topic/6372-dell-latitude-5x30-6x30-clover-install-guide/?hl=%2Be5530+%2Byosemite search the forum
  7. in terminal try sudo pmset hibernatemode 0
  8. try booting with kext_dev_mode=1 sounds like you might have a cache issue.
  9. can you upload your EFI folder.
  10. have you tried adding voodootscsync.kext it sounds like you are having issues with tsc. i think you can modify it in clover you might have to look at clover wiki under cpu section. clover might not be reading your frequency/bus speed properly. also try a more current clover if possible.
  11. i think you use find and replace, then tell it it's a plist edit in kernel and kext patches with clover configurator. tell it to find 0x02148086 and replace with 0x0a168086 then check the plist edit box at the end of that entry line.
  12. well the issue is apple changed the installer. 10.6.8 brought changes that are not compatible with oder versions of the boot packs.
  13. try a newer chameleon version maybe the one your using is too old for 10.6.8 and above.
  14. well according to the KP it's an appleEFI nvram issue.
  15. find the kext thats loading for it in yosemite and try it in maverics?
  16. remove nvram.dylib from the modules folder in Extra
  17. do you have kext-dev-mode=1 boot flag in your org.plist? it might not be loading those kexts into you cache.
  18. that usually happens when you have a kernel that is not named mach_kernel and or not in the location that it usually resides in.
  19. you sure you do not have more then one fakesmc installed? one in extra one in sle?
  20. i guess you need to mess with the chameleon FB entries.
×
×
  • Create New...