Jump to content

LaCie USB 3.0 drivers are here for OS X


antic
 Share

240 posts in this topic

Recommended Posts

Does anyone have a Non-Cartri BIOS EP45-UD3P with a Seagate 750 or 1500 GB SATA drive that they could do a Disk Read/Write test on ? ( using AJA System Test v 3.1 with a 1.0GB file size and a video frame Size of 720x486 8bit )

 

 

AJASystemTest.zip

 

I am trying to determine where the issue is with my relatively slow motherboard SATA II speeds.

 

I am currently getting speeds in the same range as FW800, when I should be getting significantly faster speeds.

 

( See my previous posts in this topic )

 

Thank You!

Link to comment
Share on other sites

Does anyone have a Non-Cartri BIOS EP45-UD3P with a Seagate 750 or 1500 GB SATA drive that they could do a Disk Read/Write test on ? ( using AJA System Test v 3.1 with a 1.0GB file size and a video frame Size of 720x486 8bit )

 

 

AJASystemTest.zip

 

I am trying to determine where the issue is with my relatively slow motherboard SATA II speeds.

 

I am currently getting speeds in the same range as FW800, when I should be getting significantly faster speeds.

 

( See my previous posts in this topic )

 

Thank You!

 

I see that you have a raptor hd, what speeds are you getting on that drive?

 

RW

Link to comment
Share on other sites

Great Question RemoteWorks!

 

And you may have solved the puzzle in part too!

 

 

And, for more completeness...

 

FW800 test using Seagate SATA 750GB connected to StarTech FW 800 Card PEX1394B

 

post-493233-1289353563_thumb.jpg

 

300GB VelociRaptor connected to Motherboard SATA

 

post-493233-1289353575_thumb.jpg

 

THIS SATA result is more in line with what I would expect.. Therefore I suspect the issue is with the Seagate drives

vs the MB or Cartri's BIOS

 

Thanks for the question RW!

 

( and no, I have no jumpers on the seagates forcing them to SATA I )

Link to comment
Share on other sites

Nicely done Modbin, thank you!

 

My cheap USB3 interface still reports 480mb/s when plugged in to the USB3 port, but is almost three times faster on the AJA System test than when plugged into USB2.

 

Same speeds in 32 or 64 bit kernel modes.

 

It's not as fast as my eSata, but I'm using the old 5400 RPM drive from my macbook for testing, so no complaints.

 

Now if someone could only port the Marvell 9128 . . .

 

(built in USB3 Gigabyte X58A-UD7 (Rev 1))

Link to comment
Share on other sites

Nicely done Modbin, thank you!

 

Now if someone could only port the Marvell 9128 . . .

 

(built in USB3 Gigabyte X58A-UD7 (Rev 1))

 

I second that motion - with the USB 3.0 ports now working, the Marvell 9128 is the only thing left that doesn't work on my UD7 rev 1.0.

Link to comment
Share on other sites

Great Question RemoteWorks!

 

And you may have solved the puzzle in part too!

 

 

And, for more completeness...

 

FW800 test using Seagate SATA 750GB connected to StarTech FW 800 Card PEX1394B

 

300GB VelociRaptor connected to Motherboard SATA

 

THIS SATA result is more in line with what I would expect.. Therefore I suspect the issue is with the Seagate drives

vs the MB or Cartri's BIOS

 

Thanks for the question RW!

 

( and no, I have no jumpers on the seagates forcing them to SATA I )

 

Hmm, try testing the Seagate on the same sata port as the Raptor, but i think it's more likely related to the Seagate hard disk and not the Mb or Catri's bios.

Also confirm that Spotlight is not indexing while testing the drive.

 

RW

Link to comment
Share on other sites

Hmm, try testing the Seagate on the same sata port as the Raptor, but i think it's more likely related to the Seagate hard disk and not the Mb or Catri's bios.

Also confirm that Spotlight is not indexing while testing the drive.

 

RW

 

ditto, can you explain in which port are you using the seagate?

As the bios is emulating the whole macpro 4,1 ich10 sata ahci, id suggest you to use the third port (PRT2) as the 1 1st ports could be reserved for dvds.

Link to comment
Share on other sites

It shows up in profiler as "Unknown AHCI controller"

 

I have the same controller on an add in PCI-e card as Cartri says it works OOB all I had to do was plug in the card and the drive connected to it boot and start transferring data it shows the up same as yours in my profiler so that is just a cosmetic display issue, OS X won't boot from it now mind you which is a shame as I wanted to put my SSD on it otherwise works fine. Is yours bootable Cartri?

Link to comment
Share on other sites

I have the same controller on an add in PCI-e card as Cartri says it works OOB all I had to do was plug in the card and the drive connected to it boot and start transferring data it shows the up same as yours in my profiler so that is just a cosmetic display issue, OS X won't boot from it now mind you which is a shame as I wanted to put my SSD on it otherwise works fine. Is yours bootable Cartri?

Never tried to boot from it, but it has a bridge and says osx that the ports are eSata so maybe is why you can't boot, if this is your problem, this is our same on the orange icon problem in gigabyte motherboards, and sits on how to write the capabilities we want: we know even how to generate it in 64 instead of 32bit format, but we did not find where the bar0 capabilities can be forced. Anyway, if the IOAHCIBlockStorage kext gives us a internal status to the disk, some kext like this one could do the same to your ahci: even better because marvell will be matchable in a different kext if you desire. The problem is that - "oh no" - our asus expansion has a bios, and a undefined bridge.

We can create this bridge definition in dsdt, even force them by the early booted dsdt inside the mainboard bios, but that would "eat" us a slot. (you would never be able to have another thing but this board working on the hacked slot)

Link to comment
Share on other sites

Never tried to boot from it, but it has a bridge and says osx that the ports are eSata so maybe is why you can't boot, if this is your problem, this is our same on the orange icon problem in gigabyte motherboards, and sits on how to write the capabilities we want: we know even how to generate it in 64 instead of 32bit format, but we did not find where the bar0 capabilities can be forced. Anyway, if the IOAHCIBlockStorage kext gives us a internal status to the disk, some kext like this one could do the same to your ahci: even better because marvell will be matchable in a different kext if you desire. The problem is that - "oh no" - our asus expansion has a bios, and a undefined bridge.

We can create this bridge definition in dsdt, even force them by the early booted dsdt inside the mainboard bios, but that would "eat" us a slot. (you would never be able to have another thing but this board working on the hacked slot)

 

Ok I think I take most of what your saying here in. The gist of it being if I can get it recognized as internal (IORegistryExplorer shows it attached to PEX2@1c,2 on PRT0,0) where in the device tree the PRT0,0 shows AHCI-Built-In True but the actual IOAHCIDevice@0 that attached to the port as Physical Interconnect Location of External. It would be this last part of the output that needs to be changed to Internal right and would a modification/new entry in my DSDT declaring the PEX2 as built-in 0x01 like for a network card do this? Looking further down the device tree everything else shows as Physical Interconnect Location of Internal for the AppleAHCIDiskDriver, IOAHCIBlockStorageDevice and I do get an internal icon as I Have the IOAHCIBlockStorage.kext installed. Although now I look at the rest of my disks connected on the motherboard ports the attached IOAHCIDevice@0 for them shows Physical Interconnect Location of External with the same Internals on the the same entries below them in their device tree as shows for the Marvell controller and they can be booted from. So I think I am lost again on where to start doing this modification don't suppose you would have any sample snippet of code for the DSDT mod(s) needed. Sorry for hijacking the thread with this definitely off topic posting.

Link to comment
Share on other sites

ditto, can you explain in which port are you using the seagate?

As the bios is emulating the whole macpro 4,1 ich10 sata ahci, id suggest you to use the third port (PRT2) as the 1 1st ports could be reserved for dvds.

 

I will have to check tomorrow which port they were connected to; but I did use the same port for all SATA tests - this probably eliminates the question of the MB - My bet is on a firmware issue with the drives as they were in the Seagate batch that had all the firmware issues. My guess at this point is that Seagate locked the drives to SATA I when they issued the replacement firmware. This is a guess, but it does look like the drive to me. I will see if I can borrow an SSD to test in the next few weeks too.

Link to comment
Share on other sites

And your hard disks dont work in them?

I have a marvell ahci controller on the Asus U3S6 expansion card and it works out of the box

 

Hard disks work in them, they just don't work at 6Gb/s in OS X, and the driver just says

Unknown AHCI Standard Controller

Marvell Virtuall

in profiler

 

Been watching the price on these - http://www.newegg.com/Product/Product.aspx...6-557-_-Product and when it comes down to at least half what it is now, I will get 2 to use the Marvell ports. If SL doesn't have SATA III support by then, I'll probably format them NTFS and use them strictly with Win7.

Link to comment
Share on other sites

Hard disks work in them, they just don't work at 6Gb/s in OS X, and the driver just says

Unknown AHCI Standard Controller

Marvell Virtuall

in profiler

 

Been watching the price on these - http://www.newegg.com/Product/Product.aspx...6-557-_-Product and when it comes down to at least half what it is now, I will get 2 to use the Marvell ports. If SL doesn't have SATA III support by then, I'll probably format them NTFS and use them strictly with Win7.

 

AHCI is a universal standard, in theory to give the controller the capabilities and just report as a disk type to the system, what matters sometimes to the system is the AHCI-CAP but there is no exclusivity to sata2 speeds, sata3 ahci should be a faster generic port then a "named" interface - can you test and see if you get better results?

Link to comment
Share on other sites

My MSI X58 Big Bang X-Power has the Marvell® 88SE9128 chipset which allows for RAID 0/ 1 mode OOB in OS X. It's also completely bootable without any sort of trickery. It's badass.

 

-Stell

 

 

Did you just need to use Chameleon +/- the boot file from PC EFI 10.6 ?

 

No kexts ?

 

( this is OT... Should this be discussed elsewhere? )

 

Thanks Stell !

Link to comment
Share on other sites

Did you just need to use Chameleon +/- the boot file from PC EFI 10.6 ?

 

No kexts ?

 

( this is OT... Should this be discussed elsewhere? )

 

Thanks Stell !

 

I'll be creating a dedicated MSI X58 Big Bang thread soon. I'll discuss the information there, instead of clutter this one anymore than we already have.

 

-Stell

Link to comment
Share on other sites

New trouble:

 

11/13/10 8:54:51 PM kernel PXHCD 0xffffff80ffcf1000::UIMAbortEndpoint: slotID is not valid

11/13/10 8:54:51 PM kernel PXHCD 0xffffff80ffcf1000::UIMDeleteEndpoint: slotID is not valid

11/13/10 8:54:53 PM kernel USBMSC Identifier (non-unique): 00000000000000000000 0x174c 0x5106 0x1

11/13/10 8:54:53 PM kernel USBF: 80058.424 Endpoint 0x81 of the USB device "AS2105" at location 0x200000: converting Bulk MPS from 1024 to 512 (USB 2.0 Spec section 5.8.3)

11/13/10 8:54:53 PM kernel USBF: 80058.424 Endpoint 0x2 of the USB device "AS2105" at location 0x200000: converting Bulk MPS from 1024 to 512 (USB 2.0 Spec section 5.8.3)

11/13/10 8:55:03 PM kernel PXHCD 0xffffff80ffcf1000::IssueEndpointCommand - Deconfigure Endpoint

11/13/10 8:55:03 PM kernel PXHCD 0xffffff80ffcf1000::XHCIRootHubResetPort detect device on port 2

11/13/10 8:55:03 PM kernel UIMCreateControlEndpoint - EP type 0x2

11/13/10 8:55:03 PM kernel UIMCreateControlEndpoint - EP type 0x2

 

The device is no longer mounting on GA-X58A-USB3

 

I have updated to 10.6.5 and wonder if this borked it. Anyone else made the update to 10.6.5 having issues?

Thanks,

g\

 

EDIT

well rebooted with the dock still attached and it mounted the disk properly on boot so i'm not sure if that was just a fluke. I'll do some more testing soon.

/g

Link to comment
Share on other sites

New trouble:

 

11/13/10 8:54:51 PM kernel PXHCD 0xffffff80ffcf1000::UIMAbortEndpoint: slotID is not valid

11/13/10 8:54:51 PM kernel PXHCD 0xffffff80ffcf1000::UIMDeleteEndpoint: slotID is not valid

11/13/10 8:54:53 PM kernel USBMSC Identifier (non-unique): 00000000000000000000 0x174c 0x5106 0x1

11/13/10 8:54:53 PM kernel USBF: 80058.424 Endpoint 0x81 of the USB device "AS2105" at location 0x200000: converting Bulk MPS from 1024 to 512 (USB 2.0 Spec section 5.8.3)

11/13/10 8:54:53 PM kernel USBF: 80058.424 Endpoint 0x2 of the USB device "AS2105" at location 0x200000: converting Bulk MPS from 1024 to 512 (USB 2.0 Spec section 5.8.3)

11/13/10 8:55:03 PM kernel PXHCD 0xffffff80ffcf1000::IssueEndpointCommand - Deconfigure Endpoint

11/13/10 8:55:03 PM kernel PXHCD 0xffffff80ffcf1000::XHCIRootHubResetPort detect device on port 2

11/13/10 8:55:03 PM kernel UIMCreateControlEndpoint - EP type 0x2

11/13/10 8:55:03 PM kernel UIMCreateControlEndpoint - EP type 0x2

 

The device is no longer mounting on GA-X58A-USB3

 

I have updated to 10.6.5 and wonder if this borked it. Anyone else made the update to 10.6.5 having issues?

Thanks,

g\

 

EDIT

well rebooted with the dock still attached and it mounted the disk properly on boot so i'm not sure if that was just a fluke. I'll do some more testing soon.

/g

 

 

I have these same errors when device is plugged in @ system boot.

 

-Stell

Link to comment
Share on other sites

  • 2 weeks later...
For a MacPro you would get the drivers from Lacie when you purchased one of their USB 3.0 cards so you would use the original drivers unaltered.

 

 

huh?

 

I see no reason why this modbin patched file wouldn't work on a mac pro. Real Mac users can also use any USB3 storage device with this driver, instead of being locked to LaCie devices.

 

g\

Link to comment
Share on other sites

huh?

 

I see no reason why this modbin patched file wouldn't work on a mac pro. Real Mac users can also use any USB3 storage device with this driver, instead of being locked to LaCie devices.

 

g\

 

Probably would but if wanting support if anything goes wrong from said manufacturers your not getting it using a hacked driver and lets face the facts someone using a MacPro is not going to cheap out saving $10 on a generic card + hacked driver even I am not that cheap and I am one tight fisted SOB...

Link to comment
Share on other sites

 Share

×
×
  • Create New...