Jump to content

Search the Community

Showing results for tags 'pci'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • OSXLatitude
    • Announcements & News
    • The Lobby
    • Feedback
    • The Archive
    • Others
  • OS X Installation Guides
    • Acer
    • Asus
    • Dell
    • Gigabyte
    • HP
    • Lenovo
    • Samsung
    • Toshiba
    • Others
  • Help and Support
    • FAQs & Tutorials
    • Dell Systems
    • Acer Systems
    • Asus Systems
    • HP Systems
    • Lenovo systems
    • Samsung Systems
    • Toshiba systems
    • Intel-based Systems
    • AMD-based Systems
    • Software matters or issues
    • macOS beta (before 1st official release)
    • General hardware support
  • Technical Information, R&D
    • Hardware technical information
    • R&D

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL










Found 2 results

  1. Hi all, I'm using an original Airport BCM943602CS card with a pci-e adapter. Wifi is working great OOTB but not BT. Since my motherboard only has a single USB3 header connecter that is used for the front USB connectors of the case, I decided to buy a third-party NEC Renesas based PCI-E USB controller, and to connect the BCM943602CS to it via USB (since USB connection is necessary for the BT part). This is the part that is not working correctly : the BT controller is not correctly detected by macOS -> no BT panel. The current state is the following: - In System Information, the bluetooth panel is empty - In System Information, the USB host controller of the Airport card is visible under the second USB 3.0 bus provided by the NEC Renesas card - In IORegistryExplorer, it is shown that this USB card is mounted under [email protected] - which seems logical since PXSX is used for a generic PCIe device. The Broadcom BT controller is show under [email protected] BUT, strangely enough, the USB ports of the cards are not named! Each port has a location (0x00500000, 0x00600000, ...) but no name. I looked at my DSDT and, indeed, there are no named port definitions under the PXSX device. As opposed, say, for the XHC device which has multiple named ports in the DSDT. - In Hackintool, both controllers are shown but only the ports of the main Intel controller are listed (HS01-14, USR1-2, SS01-10) - For testing purpose i'm using USBInjectAll and port-limit disabling hacks. So where are the ports of PXSX?! So, how is it possible that the BT controller is clearly visible on the secondary USB bus (even in System Information / USB panel) but not detected as such by macOS? Is it because it can only be connected on the primary USB controller/bus? The Airport card is indeed working and is not the problem: if I plug it directly on the motherboard USB3 header it shows up instantly in macOS and everything is working great. So, clearly, the problems is with the connection through a 3rd party USB controller card. I'm using the following driver for the NEC USB controller card: https://github.com/chris1111/USB-3.0-NEC. I tried switching it with GenericUSBXHCI.kext to see if this driver handle ports differently, but the card is not even recognized with this one. At this stage, the only ideas I have are: - try to add names to PXSX ports - in a patched DSDT I suppose, but I have no idea where to start. - try to rename PXSX to something else in order to please macOS (XHC0, XHC1 maybe?) Any suggestion is appreciated. Thanks for your help!
  2. I have the Asus G75vw with the nvidia 670m graphics card. I've tried both mountain lion and mavericks with the same results both times: when I first boot up the myHack pen drive, it hangs at "pciconfiguration end" I've verified that my PciRoot is 0 and that I can boot up fine with the uni_beast method. I'm hoping to get myHack working so I can integrate my model completely into the EDP. I at first thought it was the boot loader since this was an older one and so tried another version of chameleon but got the same results. Any ideas? **Edit** I read elsewhere that this can also be caused by ehci issues. So I put GenericUSBXHCI.kext into the E/E of the pendrive and sure enough, problem solved.
  • Create New...