PCIMatchedFamily" - no such string in Info.plist...
235 replies to this topic
#221
Posted 31 December 2012 - 06:12 PM
What is this?? "
#222
Posted 04 January 2013 - 03:24 PM
Open info.plist with plist editor.
In PXHCD dictionary add IOPCIPrimaryMatch string 0x01941033
In PXHCD dictionary add IOPCIPrimaryMatch string 0x01941033
#223
Posted 22 January 2013 - 05:11 AM
Attached Files
#224
Posted 20 February 2013 - 05:34 AM
#225
Posted 05 March 2013 - 06:00 AM
Thanks guys! Kext in post 200 worked perfectly for me! I have the StarTech 2 port card. Just installed and restarted.
#226
Posted 05 March 2013 - 11:30 AM
Use the patched AppleUSBXHCI kext. It works a lot better than PXHCD.
#227
Posted 14 March 2013 - 10:30 PM
I used the 1.0.8 PXHCD (not sure about the more current versions working on Snow Leopard). I used the Kext Wizard utility to install it, made sure all USB drives were disconnected first, installed the kext, ran the Kext Wizard Maintenance, rebooted, and the Super-Speed Bus appeared in the System Profiler | Hardware | USB.
Before using this driver, the USB 3.0 ports were not recognized by SL. My Gigabyte board uses the Etron Technology EJ168 USB 3.0 Controller (quantity two). I have one USB 3 external drive enclosure (Anker). Unfortunately, the Seagate Momentus 7200.4 (ST9500420ASG) inside it can only muster a 1.5 Gb / s SATA connection, even though it is supposed to be 3.0 Gb / s. However, with this USB 3 aware kext, the drive has the same transfer speed with USB 3 as it does with eSATA (about 77 MB / s). With a USB 2 connection the drive is about 32 MB / s. Sometimes the eSATA connection can reach 82 MB / s, which I believe is a direct result of how the 7200.4 can merely connect to a SATA II controller, not necessarily have transfer rates at SATA II speeds (ever).
If curious, search the web for the negotiated link speed issues with this particular Momentus flavor. I pulled the Seagate drive from my MacBook Pro when I was suspecting the drive was going to die (3 year warranty is almost up). The Seagate would always connect with 1.5 Gb / s negotiated link speed on my MacBook Pro (and continues to with the Gigabyte eSATA connection). After getting my new MacBook Pro hard drive up and running (a WD Scorpio Black), all of a sudden the potential slow SATA speed issue went completely away, by having a hard drive that can operate at the highest speed possible (the 2010 MacBook Pro 6,1 maxes out with 3.0 Gb / s controllers).
Before using this driver, the USB 3.0 ports were not recognized by SL. My Gigabyte board uses the Etron Technology EJ168 USB 3.0 Controller (quantity two). I have one USB 3 external drive enclosure (Anker). Unfortunately, the Seagate Momentus 7200.4 (ST9500420ASG) inside it can only muster a 1.5 Gb / s SATA connection, even though it is supposed to be 3.0 Gb / s. However, with this USB 3 aware kext, the drive has the same transfer speed with USB 3 as it does with eSATA (about 77 MB / s). With a USB 2 connection the drive is about 32 MB / s. Sometimes the eSATA connection can reach 82 MB / s, which I believe is a direct result of how the 7200.4 can merely connect to a SATA II controller, not necessarily have transfer rates at SATA II speeds (ever).
If curious, search the web for the negotiated link speed issues with this particular Momentus flavor. I pulled the Seagate drive from my MacBook Pro when I was suspecting the drive was going to die (3 year warranty is almost up). The Seagate would always connect with 1.5 Gb / s negotiated link speed on my MacBook Pro (and continues to with the Gigabyte eSATA connection). After getting my new MacBook Pro hard drive up and running (a WD Scorpio Black), all of a sudden the potential slow SATA speed issue went completely away, by having a hard drive that can operate at the highest speed possible (the 2010 MacBook Pro 6,1 maxes out with 3.0 Gb / s controllers).
#228
Posted 22 March 2013 - 02:51 PM
Dr. Hurt, on 05 March 2013 - 11:30 AM, said:
Use the patched AppleUSBXHCI kext. It works a lot better than PXHCD.
Can you please post a link to this patched KEXT from Apple ? Do you know if it support Hubs ?
Did I read right somewhere on this thread...someone said that the LaCie 1.0.11 driver supposedly supports HUBS ? Can someone confirm that please ?
#229
Posted 30 March 2013 - 03:52 PM
carboon, on 08 August 2012 - 01:05 AM, said:
http://www.caldigit....ex.asp?KBID=108
I installed the Caldigit USB3 Driver (CalDigitUSBxHCI.kext and CalDigitFastIO.kext) for Mountain Lion. By removing the IOPCISecondaryMatch and IOPCIMatch parts in Info.plist, leaving only IOPCIClassMatch, the kexts make my Etron EJ168 on-board controller work...only for the first mount. If I umount the USB stick, I can't mount it again without a reboot (the device won't even show up in diskutil).
I didn't run the pkg installer, rather copied the two kexts to S/L/E.
Any thoughts?
I installed the Caldigit USB3 Driver (CalDigitUSBxHCI.kext and CalDigitFastIO.kext) for Mountain Lion. By removing the IOPCISecondaryMatch and IOPCIMatch parts in Info.plist, leaving only IOPCIClassMatch, the kexts make my Etron EJ168 on-board controller work...only for the first mount. If I umount the USB stick, I can't mount it again without a reboot (the device won't even show up in diskutil).
I didn't run the pkg installer, rather copied the two kexts to S/L/E.
Any thoughts?
Yeah - I actually bought a CalDigit FASTA-6GU3, to avoid all this hassle... and it has all the same issues... (SL 10.6.8)
I fear it's just that the driver is useless, not that it's not working with your particular hardware.
Oh, I did sort of get it to recognise my HUB, but only the first device I plugged in worked, and it would instantly KP on boot.
#230
Posted 12 May 2013 - 09:38 PM
macintrash, on 30 March 2013 - 03:52 PM, said:
Yeah - I actually bought a CalDigit FASTA-6GU3, to avoid all this hassle... and it has all the same issues... (SL 10.6.8)
I fear it's just that the driver is useless, not that it's not working with your particular hardware.
Oh, I did sort of get it to recognise my HUB, but only the first device I plugged in worked, and it would instantly KP on boot.
I fear it's just that the driver is useless, not that it's not working with your particular hardware.
Oh, I did sort of get it to recognise my HUB, but only the first device I plugged in worked, and it would instantly KP on boot.
Brilliant. Useless driver then. It doesn't seem like CalDigit, or any of the card manufacturers are interested in keeping up the drivers.
You might think at some point they'd just put the code for the drivers out. It's not like they're going to be losing money if they're not supporting the cards,
and frankly they'd be earning themselves the good will of the public because they've given people the opportunity to make something of the hardware.
#231
Posted 13 May 2013 - 01:25 AM
Is it possible to patch the 1.0.11 kext to stop it flooding the console with messages? It actually enabled the hub-attached rear USB3 ports on my P9X79. Any other kext will cause a KP with these ports so I normally have to enable just the front controller.
There's no logging with the 1.0.10 driver but devices plugged into the rear ports don't work. It would be nice to have all my USB ports working but I can't put up with the constant logging.
There's no logging with the 1.0.10 driver but devices plugged into the rear ports don't work. It would be nice to have all my USB ports working but I can't put up with the constant logging.
#232
Posted 13 May 2013 - 08:10 AM
marcelol, on 22 March 2013 - 02:51 PM, said:
Can you please post a link to this patched KEXT from Apple ? Do you know if it support Hubs ?
http://www.insanelym...00#entry1892642
Riley Freeman, on 13 May 2013 - 01:25 AM, said:
Is it possible to patch the 1.0.11 kext to stop it flooding the console with messages?
http://www.insanelym...-x-with-source/
#233
Posted 13 May 2013 - 11:22 AM
Thanks shiecldk. After further testing it seems the kext wasn't working as well as I'd thought last night. So I'll stick with just having the front USB3 ports active.
#234
Posted 17 May 2013 - 06:33 PM
#235
Posted 17 May 2013 - 10:28 PM
#236
Posted 18 May 2013 - 03:53 PM
Riley Freeman, on 17 May 2013 - 10:28 PM, said:
I'm running 10.6.8 so neither of those are an option. Ideally I'd prefer not to use patched Apple kexts so I was hoping the Lacie kext was going to do the job.
People had tried replacing USB related kexts for their Ivy Bridge USB 3.0 ports after MBPR, which used a newer version of OSX, released to market.
It seemed no one had serious problem with the newer version of USB kexts in their older system.
It might be a good try for your 10.6.8.
Just remember to backup the original USB kexts before trying anything.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users



Sign In
Create Account










