Search results

Loading Google Results...
  1. gaydar120

    another USB 3.0 thread

    i dont understand what that means.. have i not been in the problem state this whole time?
  2. gaydar120

    another USB 3.0 thread

    oh, OK i see now. as for IOReg, can you point out the steps necessary to get a proper report?
  3. gaydar120

    another USB 3.0 thread

    So where should the SSDT-XWAK reside? or should I simply remove it?
  4. gaydar120

    another USB 3.0 thread

    Removed entries from sorted order, edited DSDT for disabling XWAK and placed it in /Clover/ACPI/patched ... have USB 3.0 showing up, but still no wake from sleep. Occasionally USB 3.0 ports are dead on login.
  5. gaydar120

    another USB 3.0 thread

    what I mean by "had to disable the XOSI patch in Clover config options just to be able to boot" is that, in Clover boot loader, I navigated through options to ACPI>Custom patches and unchecked the option for XOSI .. for whatever reason I was unable to boot without doing so. I was assuming there...
  6. gaydar120

    another USB 3.0 thread

    also facing kernel panic somewhere (haven't verbose yet to find out where/what) ... had to disable the XOSI patch in Clover config options just to be able to boot. Disabling XOSI patch also rids me of the dead USB on sleep wake o_0
  7. gaydar120

    another USB 3.0 thread

    CRAP. All USB ports are dead on wake from sleep :(
  8. gaydar120

    another USB 3.0 thread

    ah, yes, that SSDT shouldn't be there, actually. It's a leftover from my troubleshooting of HDMI audio. Got rid of that, removed SortedOrder entry, rebooted and ***BAM*** that did it!!! I now see USB 3.0 listed in system profile! :clap::mrgreen::headbang: THANK YOU SO MUCH, RehabMan! Thank you...
  9. gaydar120

    another USB 3.0 thread

    Ah, OK, I had an older version of MaciASL .. I think I got the AML in place and the SortedOrder now. About to reboot, but is this what you're asking for as far as "lspci -nn"? (attached text file) edit: Just rebooted and still seeing 2.0 speeds. Attached updated Clover files, Patchmatic dump...
  10. gaydar120

    another USB 3.0 thread

    when I go to compile the AML (from SSDT-XOSI.dsl) using MaciASL, I get these errors : 7/7/17, 8:38:28 PM, iASLtPIH2t.dsl(37) : Error 4096 - Invalid character (0x21), expecting ASL keyword or name 7/7/17, 8:38:28 PM, iASLtPIH2t.dsl(37) : Error 4096 - Invalid character (0x3D), expecting ASL...
  11. gaydar120

    another USB 3.0 thread

    I updated the BIOS to latest version but it did not add any options related to xHCI settings.
  12. gaydar120

    another USB 3.0 thread

    Theres nothing in the (very restricted) Dell BIOS about xHCI vs. EHCI. From what I can gather, the board should be set to xHCI according to this post: - http://en.community.dell.com/support-forums/desktop/f/3514/t/19629247
  13. gaydar120

    another USB 3.0 thread

    IOReg, Patchmatic and Clover EFI files attached .. Kextstat output: kextstat|grep -y acpiplat 13 1 0xffffff7f8312e000 0x60000 0x60000 com.apple.driver.AppleACPIPlatform (5.0) 65E05472-6AE7-3308-8CC8-FA6CB0DB2AEE <12 11 7 6 5 4 3 1> extstat|grep -y appleintelcpu 26 0...
  14. gaydar120

    another USB 3.0 thread

    is there anything im missing? (patchmatic and IOReg files attached)
  15. gaydar120

    another USB 3.0 thread

    OK I figured out the patchmatic thing .. zip attached
  16. gaydar120

    another USB 3.0 thread

    here's IOReg copy (attached) .. little confused about Patchmatic....
  17. gaydar120

    another USB 3.0 thread

    please advise edit: OK, so, IOReg and what else?
  18. gaydar120

    another USB 3.0 thread

    I reset CsrActiveConfig back to what it was (0x3) and the dead hub is working again, but still no 3.0 speeds.
  19. gaydar120

    another USB 3.0 thread

    Well I did all the steps mentioned above for the XOSI fix and rebooted, but still no 3.0 speeds. Then I ran the Inject All kext thru Kext Utility and rebooted again-- still no 3.0 speed and somehow one of the hubs is now dead.
  20. gaydar120

    another USB 3.0 thread

    ok, regarding the XOSI, I think I see now: 1. click the little + icon on the right 2. for comment put change _OSI to XOSI 3. for find* [HEX] put 5F4F5349 4. for Replace* [HEX] put 584F5349 Is that correct? Do I also need to do this?: In the Rt Variables section set your booterconfig to 0x28...
Back
Top