Jump to content
Andy Vandijck

USB3 capable IOUSBFamily (10.6.5/10.6.6/10.6.7/10.6.8)

55 posts in this topic

Recommended Posts

I rewrote IOUSBFamily to be capable to use USB3 devices at full speed.

I also implemented the Orbyte legacy fix and the Slice errata fix + sleep fix (made sleep fix togleable in Info.plist of AppleUSBEHCI and AppleUSBOHCI).

 

Hello. Thx for those kexts, they really did make a difference.

 

I have a problem though, maybe you 've already come accross such a case.

 

System is AMD osx86, v. 10.6.8

I'm using your 10.8.0 R2 legacy kernel and nawcom's Sleepenabler.kext.

All is working F-I-N-E with the proper bootflags and kexts, except for one thing.

 

When I first tried the sleep function the system entered S3 mode withouth a hitch. But waking up yielded the following result. All USB ports were dead/powerless (No KB/mouse, replugging did not help so I had to restart to gain back USB functionality).

 

Cue some vigorous googling, I learned that my problem was related to the USB controller(s) being seen by OS X as "Expansion slots".

Then I came across this thread and did some testing.

 

Indeed the patched version of IOUSBfamily (v 4.2.4) which you uploaded did the trick and now controllers are seen as "Built in". This fixed the broken USB function after S3 resume but apparently only for the OHCI controllers. That is to say, any USB 1.1 device connected prior to S3 sleep will be online right after wakeup but the same doesn't hold true for USB 2.0 devices, such as pendrives, HDD's and webcams.

 

If a USB 2.0 device is hooked on any port after system wake from S3, then the device will not come back. Moreover the EHCI controller will appear (frozen) in System Profiler as though it still has the device connected when in fact it is already powered off (inserting any new device in any port will result in absolutely no USB connection). Also when this scenario takes place system will hang amid a restart/shutdown sequence. A hard reset is required.

 

Following are the USB controllers as listed by lspci -nn

 

 

00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397]

00:12.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398]

00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396]

00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397]

00:13.1 USB Controller [0c03]: ATI Technologies Inc SB700 USB OHCI1 Controller [1002:4398]

00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396]

00:14.5 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller [1002:4399]

 

Mainboard is ASUS M4A78T-E.

 

I've tried each and every possible solution I read to no success.

Most people talk about DSDT patching which unfortunately doesn't seem quite straightforward when it comes to the AMD platform...

Anyone got any clue as to what may be causing this glitch?

 

T.I.A., have fun h@ckint0shing

Share this post


Link to post
Share on other sites
Advertisement

Hello,

i ended here trying to find a way to use my usb 3 pci card...

i did download the files from Andy Vandijck

but i have no idea how i have to install them or to use them... any help would be really appreciate...

 

I did install the drivers from le lacie card... did freeze my mac...

 

So if anyone can explain me (really on a basic way as if i was retarded :D) that would be great..

 

For info, i'm on 10.6.8

 

Thanks a lot

Share this post


Link to post
Share on other sites

Anyone updated this lately ??

 

Just curious if anyone is keeping up with this, and.......does this driver work with any of the "generic" Renesas Express/34 cards out there ??

 

Bump

Edited by marcelol

Share this post


Link to post
Share on other sites

I gave this a try after the CalDigit driver for 10.6 (with edited info.plist) KP-ed my new system (P9X79/10.6.8) when it reached the desktop.

 

It works but it's writing constantly to the kernel log (I suspect it's the CalDigit driver). Is there any way to stop this?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×