The new Mac Pro (6,1) and TRIM

With its economical internal design and limited internal expansion options, the new Mac Pro depends heavily on the speed and flexibility of Thunderbolt 2 for expansion. In the old days, we could add four HDs in the internal bays and one more under the optical drive. This also allowed us, if we used SSDs instead of HDs, to enable TRIM for other than Apple drives.
We know that TRIM doesn't work with a USB 3.0 connection. The question is, can TRIM be enabled on an SSD connected in some fashion through Thunderbolt? I know that graphics cards can be plugged into an external PCIe expansion chassis and that eSATA SSDs, such as the OWC Mercury Accelsior_E2, can plug in too. But does having to pass through the Thunderbolt interface interfer with or prevent TRIM support? For that matter, what kind of external connection to an SSD at the other end of the Thunderbolt cable would be able to support TRIM? I'm currently using a CalDigit PCIe card which provides two eSATA external connections, and when a NewerTech Voyager Q is connected and an SSD plugged into it (like putting bread in a toaster), the drive is seen as "Rotational" in System Information, and TRIM cannot be enabled.
Since TRIM support is important for continued performance and longer life of SSDs, is this an issue with the new Mac Pro's design philosophy?

Hopeful but not comforting.
With Mavericks, not all SSDs will report TRIM support, but doing a benchmark both before and after the change should confirm that TRIM is functional.
I should see TRIM = YES and not from some benchmark.
Thunderbolt support for TRIM is good. But Intel has as yet? never supported TRIM on an array, so not sure how that is accomplished.
"Is" or "may" and "could" - I just  wouldn't make a "TRIM is supported by 10.8.5 and later" as it may vary by Macs that had native SATA III with PCIe support, the new Samsung controller Apple has been using. Certainly not in 5,1 Mac Pro except if and only for an Apple SSD BTO upgrade.

Similar Messages

  • Bootcamp and Windows 7 and 8 on the new Mac Pro (Dec 2013)

    I want to install bootcamp on my new Mac Pro (Dec 2013).
    Bootcamp says it supports Windows 7 and 8, but there is a bunch of new hardware with the new Mac Pro, so I am concerned about bootcamp support for it.
    Are there any issues with Windows 7 Pro install?  How about Windows 8 Pro?

    From what I see, only Windows 8 is supported on the new Mac Pro (Late 2013) with Bootcamp.
    See Boot Camp: System requirements for Microsoft Windows operating systems
    Look under Boot Camp requirements by Mac model
    Mac Pro
    Mac model
    Windows 8, 64-bit
    Windows 7, 64-bit
    Windows 7, 32-bit
    Windows Vista, 64-bit
    Windows Vista, 32-bit
    Windows XP, 32-bit
    Mac Pro (Late 2013)
    BCA
    "BCA"  indicates that Boot Camp drivers are automatically downloaded as part of the Boot Camp Assistant in OS X, for 2013 or later models of Mac computers.

  • HT1209 I have a music collection on my iPod (160GB Classic). I have that collection on my old Mac Book. Now I have a new Mac Pro and want to transfer the collection to the new Mac Pro, is that doable?

    I have a music collection on my iPod (160GB Classic). I have that collection on my old Mac Book. Now I have a new Mac Pro and want to transfer the collection to the new Mac Pro, is that doable?

    Thanks roaminggnome. Can I do that transfer wirelessly or do I have to get a large jump drive to copy and transfer. I presume that I cannot use my iPod right?

  • Premiere Pro CC and the New Mac Pro (2014)

    I'm expecting delivery soon of a new Mac Pro, nicely loaded, which I purchased mainly because of all the work I do with video. Yet, I read in a review that Adobe Premiere Pro isn't optimized to take advantage of the new Mac Pro, won't run faster, and I'm better off using Apple's Final Cut.
    1. Is this true?; and
    2. If so, will Premiere Pro be updated any time soon to run best on a 2014 Mac Pro?
    My new Mac Pro will have the following configuration:
    3.5GHz 6-core with 12MB of L3 cache
    32GB (4x8GB) of 1866MHz DDR3 ECC
    1TB PCIe-based flash storage
    Dual AMD FirePro D700 GPUs with 6GB of GDDR5 VRAM each

    My main problem is that when i export using gpu open gl it crashes hard boot the mac pro. A 3 min timeline with 4k footage n a bunch of color grading.  I get lucky if the timeline is shorter. But i think it is a gpu issue n my mac must be fixed. Currently under apple tech support. N my case is unique. No one has had the same issue and that makes it harder for me to figure the isse and to apple figure the issue.
    If i export using software only mercury then the export goes smoothe no mattrr how long. But that defeata the point of owning a mac pro with 2 GPUs
    Enviado desde mi iPhone
    El 29/03/2014, a las 01:51 p.m., BanksMeador <[email protected]> escribió:
    Re: Premiere Pro CC and the New Mac Pro (2014)
    created by BanksMeador in Premiere Pro - View the full discussion
    I have had my 12 core 2014 Mac Pro for a couple of weeks now, and I'm not very impressed with Premiere CC performance with 4K R3D on a 1920 x 1080 timeline.
    I understand that there may be an update soon that will take adantage of the CPU's and GPU's when it comes to the complex task of de-bayering the R3D footage, but it's just not there now.
    I get similar playback performance to what I experienced on my 09 Mac Pro tower.
    Any insights on getting better playback performance in this scenario would be greatly appreciated.
    Thanks!
    Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/6253414#6253414
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/6253414#6253414
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/6253414#6253414. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Premiere Pro at Adobe Community
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

  • Premiere Pro CC and the new Mac Pro - are all upgrades necessary?

    Monday I'm ordering the new Mac Pro because my Mid 2012 Mac Pro tower is simply too slow and crashy no matter how much money I sink into it. Thing is, every little upgrade I add onto this new Mac Pro is very expensive, so I want to make sure I don't add anything that won't make a difference in edit performance.
    My ultimate goal is to be able to work with 4k, and even 5k footage in 2014. More and more clients are giving me Red media, and my system right now can't handle it (I have to render proxy files for everything).
    Attached are my hardware upgrade options for my processor and graphics card. These options can only be offered when I order the computer. Neither the processor or the GFX card can be changed by me later. Note that these options alone almost double the computers's price (3600). As of now I assume that getting the fastest everything is the way to go, but is there any reason I should not go this high?
    jesse

    We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason
    Anyone else got that too with Premiere Pro CC and the new Media encoder?
    Lack of detailed info makes your question impossible for anyone to answer you!
    eg. ...."Doctor it hurts...anyone else got something that hurts?" 

  • After Effects and the new Mac Pro

    I recently got one of the new Mac Pros and it doesn't get along great with After Effects, particularly when it comes to ray-tracing.  There is no Nvidia GPU option for the new machines, so ray-tracing defaults to CPU.  But then, even with a simple solid, it gives you an out of memory error.  I've seen postings saying this is fixed in 12.2 but I've got 12.2 and the newest CUDA driver installed and run the machine with all other apps closed, but no luck.  Presumably I'll figure out how to get it running after a fashion eventually, but even then, even with the new machines' many fast cores etc, CPU ray-tracing on the new Mac Pro is not looking promising on the speed/usability front.
    Element 3D is an option, but its reflections can't interact with the comp the E3D object is within, only with the environment map in the plug-in itself, so there are many cases where it's a poor substitute.
    My question isn't really how to get ray-tracing to work with the new machines.  That would be great, but my sense is the answer there is, it effectively can't. 
    My question is, given that motion graphics increasingly involve the complex interplay of light, reflection, transparency, and three dimensional objects, and that from here on out Mac Pros will no longer accommodate nvidia cards, and that many creative types will only work on Macs, how long will this state of affairs continue?  How long can it continue?  Are there any plans to make After Effects fully functional on the new Mac Pros?  Ray-tracing has always been balky and wonky and prone to error messages and crashes, but despite all that it's also an indispensible part of After Effects. 

    A fun update, long after the fact:
    So I've learned Cinema 4D in order to reacquire the capability After Effects once offered internally and have succeeded after a fashion.  Let's look at the relative ease of the new method versus the old one using a real-world scene from my project:  Adding a bus shelter over actors on a bench.
    In ray-trace enabled After Effects of old, I could draw simple draw shapes in Illustrator, extrude them into objects, collect them under a null and position it in my scene.  Particularly powerfully, I could bend 2D photograph layers into half-domes for a fun roof, and create planes of transparent glass of any thickness I chose with refraction levels that made for interesting visuals as actors moved behind it, and add reflectivity to any layer I chose -- including the dome roof, for instance, which would then pick up the reflections of any other objects in my scene.  I could also put 2D layers in front of my bus shelter as easily as placing a layer closer to the camera than the makeshift model.  Well, sometimes it didn't work as advertised; sometimes you also had to have the foreground layer above the background one in your comp even when both were 3D and that wasn't supposed to still apply, but at least it was After-Effectsy.  The whole thing was After-Effectsy, which of course is good because presumably AE users know AE, but also it was similarly logical.
    To achieve a similar end with C4D and Cineware, all you have to do is this:  Build your bus shelter model in Cinema 4D.  Wait, first learn Cinema 4D, a hugely complicated piece of software.  Come back in 3 months, I'll wait.  Hi again.  I see you've built your bus shelter.  In fairness, you were able to add textures and complicated curves you couldn't in After Effects.  But then you always could, if you were willing to learn a hugely complicated piece of software.  Anyway, let's get that model into after effects.  Just drag that C4D project into your AE project and put it in the comp.  Put other layers in front of it or behind it.  Easy!  Now just a few caveats.  1.  Scale.  There is no formula available anywhere for the relative scales of your two projects.  So tweak that.  Just go back and forth between the two software suites -- I hope your computer can have both up and running at the same time! -- until you get that right.  2.  Cameras.  You can import your AE camera into C4D and vice-versa as easy as pressing a button in Cineware.  It shows up somewhere strange in C4D unless you use a workaround unless you are also camera tracking in AE in which case you can't.  3.  Scale again:  Your camera will match its moves in both suites now.  But they are drastically different sizes.  If you import your C4D camera into AE it becomes tiny tiny tiny, if the scale of commercial C4D models is to be considered at all standard.  Just shrink your model down to say 1% and you should be good to go.  And if you tweak your camera in AE or C4D, you have to junk your imported camera and re-do that step.  4.  Reflectivity.  Your C4D model will only reflect items in your C4D project, not the, um, scene it's going in.  5.  Refraction.  Transparent C4D items will indeed show your AE items behind them.  But you can't add refraction.  6.  I've saved the best for last.  Say you want your actors in your bus shelter, meaning part of the model is in front of them and part behind them.  You used to place them (shot on a greenscreen or roto'd) in the bus shelter model.  Now you simply do this:  Divide your bus shelter model into halves, the in-front half and the behind half.  Put both under nulls.  Give the front null a C4D "tag" called compositing.  At least its name makes sense.  Then go into the tag and enable a numerical "object buffer."  You're almost done!  Next simply go into "render options" in C4D and into "multi-pass" there and then enable object buffers again there, so intuitive!  Make sure to enable the same numerical object buffer you enabled in your compositing tag. Good?  Good!  Now, all you have to do is place two copies of your C4D project heirarchically in your AE project.  You're still almost done!  Now all you have to do is go into "multi-pass" in your Cineware plug in in the instance of it that goes in front of the actors and specify your numerical object buffer again.  Wait, one tiny thing:  If your Cineware plug-in is still set on the default "Standard" setting that option will be grayed-out.  Just switch it to the much slower-rendering C4D opions and you're good to go!  And don't worry about two copies of your C4D project in your AE one meaning it will now take twice as long to render, because it will.  But, as a bonus, you've probably learned a lot of ways to render C4D models really well when learning C4D because Adobe made you.  So you can use those to make your AE comp really shine... or wait, could, but they're not supported.  You can however render it in that flat ugly video early Pixar style, but life is full of trade offs, no?  You end up rendering out the layer you need in C4D and comping it into AE exactly as effects artists have done ever since always.  Which is to say AE gave up even trying to do 3D and sent you into the waiting arms of a more-capable competitor, their seeming specialty in the world of video.  Maybe it's better this way.  AE was only ever for comping.  It briefly got a swole head.  Now it's back in its comfort zone.  The end

  • I have the new macbook pro with retina and I am trying to back up with wd passport for mac and is telling me it is going to take 7days

    I have the new macbook pro with retina and I am trying to back it up, with wd passport for mac and is telling me it is going to take 7days. Any Ideas? Im afraid that means there is something wrong with my hard drive. I have verified the disk and it says everthing is ok.

    It seems to be a common problem that those drives don't perform well, at least not with Time Machine.
    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Post the messages timestamped from then until the end of the backup, or the end of the log if that's not clear.
    Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into a message.
    Some personal information, such as the names of your files, may be included — edit that out, too, but don’t remove the context.

  • AMD Crossfire, Boot Camp, and the new Mac Pro Issue

    Hello, all.
    I have a new Mac Pro (Late 2013) with 6 cores, 32 GB RAM, and dual D700 AMD graphics cards.  I'm using an older 30 inch Apple Cinema Display (with the dual link DVI adapter).  I've successfully installed Windows 8.1 under Boot Camp.  Here's my problem...
    I understand that for the new Mac Pro under Boot Camp enables AMD CrossfireX by default from multiple sources online.  However, it's disabled on mine, and every time I try to enable it (and hit "Apply" in the AMD Control Center), it disables again.
    Is Crossfire only available for use with a Thunderbolt Display attached?  Could that be the problem?  Or is the AMD Control Panel lying to me?
    Now, games in Windows are still running well... But I'd like to take full advantage of the dual graphics cards in the new Mac Pro with Crossfire.  Any help is greatly appreciated, thanks!

    Fixed it!
    So, not only would Crossfire not enable under Windows 8.1 on my Mac Pro in Boot Camp... But Windows started crashing massively.  I was about to wipe Boot Camp entirely and try a clean install (even though the only three things I'd installed were Windows itself using Apple's exact instructions, Steam, and Skyrim), but decided in a last ditch effort to try disconnecting and reconnecting peripherals.
    Turns out the culprit was my Belkin Thunderbolt Express Dock.
    Disconnecting the Belkin Thunderbolt dock not only stopped Windows from crashing, but now I can enable Crossfire, as well!
    Now, this is especially strange since I have read elsewhere that people have no problems using the Belkin dock under Boot Camp with other Macs... This issue is probably isolated to using it in Boot Camp with the new Mac Pro.  But disconnecting the dock from my Mac Pro has solved not just one but all of my Boot Camp issues.  (Of course, using the Belkin dock under OSX on my Mac Pro is no problem.)
    Long story short, if you have a new Mac Pro and plan on using Windows 8.1 under Boot Camp, don't have the Belkin Thunderbolt Express Dock attached.
    I'm going to contact Belkin and tell them what I've discovered.
    Hope that helps y'all.

  • Performance with the new Mac Pros?

    I sold my old Mac Pro (first generation) a few months ago in anticipation of the new line-up. In the meantime, I purchased a i7 iMac and 12GB of RAM. This machine is faster than my old Mac for most Aperture operations (except disk-intensive stuff that I only do occasionally).
    I am ready to purchase a "real" Mac, but I'm hesitating because the improvements just don't seem that great. I have two questions:
    1. Has anyone evaluated qualitative performance with the new ATI 5870 or 5770? Long ago, Aperture seemed pretty much GPU-constrained. I'm confused about whether that's the case anymore.
    2. Has anyone evaluated any of the new Mac Pro chips for general day-to-day use? I'm interested in processing through my images as quickly as possible, so the actual latency to demosaic and render from the raw originals (Canon 1-series) is the most important metric. The second thing is having reasonable performance for multiple brushed-in effect bricks.
    I'm mostly curious if anyone has any experience to point to whether it's worth it -- disregarding the other advantages like expandability and nicer (matte) displays.
    Thanks.
    Ben

    Thanks for writing. Please don't mind if I pick apart your statements.
    "For an extra $200 the 5870 is a no brainer." I agree on a pure cost basis that it's not a hard decision. But I have a very quiet environment, and I understand this card can make a lot of noise. To pay money, end up with a louder machine, and on top of that realize no significant benefit would be a minor disaster.
    So, the more interesting question is: has anyone actually used the 5870 and can compare it to previous cards? A 16-bit 60 megapixel image won't require even .5GB of VRAM if fully tiled into it, for example, so I have no ability, a priori, to prove to myself that it will matter. I guess I'm really hoping for real-world data. Perhaps you speak from this experience, Matthew? (I can't tell.)
    Background work and exporting are helpful, but not as critical for my primary daily use. I know the CPU is also used for demosaicing or at least some subset of the render pipeline, because I have two computers that demonstrate vastly different render-from-raw response times with the same graphics card. Indeed, it is this lag that would be the most valuable of all for me to reduce. I want to be able to flip through a large shoot and see each image at 100% as instantaneously as possible. On my 2.8 i7 that process takes about 1 second on average (when Aperture doesn't get confused and mysteriously stop rendering 100% images).
    Ben

  • How can I move my three SATA HDDs to the new Mac Pro without backing up?

    Hello,
    I am doing initial shopping for the new Mac Pro but have come to the frustrating realization that I cannot move my HDDs to the new computer for free. Sure, I can migrate my OS drive to the new one, but my other three disks inside my 2007 Mac Pro are in a pickle. I want an economically viable method of getting those three drives to the new Mac without backing them up, formatting or something like that. Also, I would prefer a transfer method that will rival the speed of it being internal. I don't think USB 3.0 can do this, but Thunderbolt 2 can? Everything I've seen online has been outrageiously expensive or requires me to reformat (RAID).
    What I'm looking for:
    Connect three or more HDDs of various capacities to new Mac Pro
    Have the transfer speeds rival or exceed that of my current grandpa computer (Mac Pro 1,1)
    Have it not be incredibly expensive (anything over $300 is ridiculous)
    Have it be no more than two devices, one prefered unless they are individual enclosures that can either daisy chain and/or are inexpensive.
    Safe for my drives.

    >  a 3 TB, a 1.5 TB and a 500 GB.
    Most 3TB drives are going to be "green"
    The 1.5TB may or may not
    The 500GB is likely old, due for retirement if not worse.
    A pair of two drives of 2TB likely would be enough for now and plenty of dual drive USB3 cases.
    For a single drive and Thunderbolt docking adapter for using one drive at a time:
    http://www.amazon.com/Seagate-Backup-Portable-Thunderbolt-Adapter/dp/B009HQCARY/
    Under $300 case
    http://eshop.macsales.com/item/OWC/METB7DK0GB/
    Or this one is fine and USB3
    http://www.amazon.com/StarTech-com-External-Enclosure-3-5-Inch-SAT3520U3SR/dp/B0 09C5VSFU/
    NO backup? You DO have some backups I hope, or you are on thin ice or walking tight rope.
    Some helpful guides on USB3 vs TB
    http://www.macperformanceguide.com/topics/topic-USB3.html
    http://www.macperformanceguide.com/index_topics.html#MacPro2013Transition
    http://www.macperformanceguide.com/topics/topic-Thunderbolt.html
    1TB WD Blue go for $60?

  • Using the New Mac Pro (can) - AE will not let me use Race Traced 3-D

    Using the New Mac Pro (can) - AE will not let me use Race Traced 3-D
    Hi, I'm using the new Mac Pro
    2.7 GHz 12-core Intel Xeon E5
    64 GB 1867 MHz DDR3
    AMD FirePro D700 6144 MB
    OSX 10.9.2
    I'm using After Effects 12.2.1.5
    When I attempt to invoke the race trace 3D renderer in a comp, I get this error
    "After Effects Error: Ray-traced 3D: Out of paged mapped memory for ray tracer. Your project may exceed GPU limits. Try closing other applications. Try updating the CUDA driver. (5070::2)"
    My preferences are set to use the CPU for Raytraced 3D since I do not have an Nvidia card.
    So, obviously there is an issue here in that it thinks I have an Nvidia card.
    I know (or assume I know) the cause for this is that when I set up this machine, I used Apple's migration assistant to move most of my data over from the previous gen Mac Pro which DID have a CUDA card.
    So my question is, what files can I delete/reset to cause After Effects to no longer look for CUDA files that do not exist on this machine?
    I do not have the CUDA control panel in System Prefs, so THAT did not carry over.
    Any ideas would be appreciated, thanks!

    > I know (or assume I know) the cause for this is that when I set up this machine, I used Apple's migration assistant to move most of my data over from the previous gen Mac Pro which DID have a CUDA card.
    Ugh. That causes so many problems.
    The first thing to try is deleting the CUDA frameworks from your Mac: Look in /Library/Frameworks for the CUDA.Framework and get rid of it.

  • New Mac Pro (Late 2013) and CC 2014

    Ok, I've been working on one of the new Mac Pro's from late 2013 and using CC 2013 with R3D footage quite successfully (though without great debayering performance on the R3D - I know it's supposed to be improved in CC 2014).
    I'm running 10.9.2 Mac OSX.
    When football season here in the states starts in two weeks, I will have a VERY deadline intensive 30 minute television show that I have to turn around from Saturday night at 2am until 8am Sunday morning.
    I have purchased CC 2014, but have read in the past few weeks about the headaches the combination of OS 10.9.3 (and .4) and CC 20014 have caused.
    My question is, where do we stand with those issues, and what would the community / Adobe moderators say about me heading up to the latest OS and CC 2014 under these circumstances? Thanks so much for the insight everyone.
    Banks

    jameskachan wrote:
    …The obvious reason [sic] seems to suggest…
    That's what it suggests to you, in the limited scope of your vision and knowledge, and without your having provided detailed specs about your hardware.
    Due to the current unavailability of clairvoyants and mind-readers in the forum, we respectfully request you supply sensible, complete details.
    We don't even know what your specific issues are, and for all we know you may be running the pathetic, buggy Yosemite OS—which Apple is giving away for free.
    In this case, you have been enormously fortunate in that you received a reply from none other than Gµrµ Chris Cox, a top Adobe engineer who has been writing Photoshop code since the last millennium.
    It's hight time you drop the attitude and avoid further embarrassing yourself in a public forum.  Just my two cents.

  • Will my LED 27 Cinema Display work with the new Mac Pro?

    Will my LED 27 Cinema Display work with the new Mac Pro?

    Mini DisplayPort (like 27" LED Cinema Display) is a direct subset of ThunderBolt (like Mac pro late 2013). It plugs right in and the display portion "just works", no adapters required.

  • Can video cards for the new Mac Pro be installed in the field?

    Current Configuration of the new Mac Pro is as follows:
          ACES MacPro Workstation Seat
    Processor
    6-Core/3.5GHz/Xeon E5
    Memory
    32 GB
    Graphics
    2X AMD FirePro D500
    Hard Disk
    1 TB
    Display
    24" LED / HP
    Media Player
    2GB FIPS USB Drive
    Mouse
    Apple Magic Mouse
    Keyboard
    USB
    Ports
    4-USB 3.0;
    6-Thunderbolt
    1- HDMI
    Netwk Interface
    Ethernet/802.11n
    Card Reader
    NIST SP 800 Compliant
    My question is can the Graphic Display cards be removed and replaced in the field by an experience Mac Technician?
    Any special tools required?

    Now here is the back, showing the heatsink paste still in place, and the thermal pads used to cool the RAM chips to the central cooler:
    note that the two cards are not interchangeable -- they have their power lugs on opposite sides. One card has chips to support actual display output to the thunderbolt Busses, the other card has none, but has the custom micro-PCIE slot for the PCIe SSD "stick".
    One reason for this design is that to make a leap forward, you would have to water-cool the slots for a traditional form-factor PCIe slot Mac pro. Then do it again to include a second GPU. In my opinion, this model Mac Pro is about conquering the cooling problem of this much CPU and GPU compute-power in one box.
    NVIDIA graphics card replacements? maybe eventually, but not at this writing.

  • I urgently need to know how I can connect 8 thunderbolt display, I was thinking with the new mac pro will come out, but I wonder if it is possible to connect an iMac to 4GB of graphics card, but suffers from the imac. thanks

    I urgently need to know how I can connect 8 thunderbolt display, I was thinking with the new mac pro will come out, but I wonder if it is possible to connect an iMac to 4GB of graphics card, but suffers from the imac. thanks

    I tightened all HD screws and it didn't help. With the machine running and side of the case off, I physically stopped both the video card fan and the front case fan with my finger for a couple seconds and the noise continued. I also took all hard drives out one by one and rebooted each time. Again, the noise continued until I took out the Mac HD in Bay 1, rebooted, and I had a very quiet, silent machine. The issue is the hard drive in bay 1 that shipped with the computer, it's without a doubt causing the hum/woosh sound. I still need to know if I can safely swap the Mac HD from bay 1 to bay 4 without any issues to the operating system. I would like to try that to see if it dampens the noise but I also want to make sure this swap won't screw up my machine at all.

Maybe you are looking for