New Mac Pro 2013 late version USB 3.0 hub issue during boot

Hi all, I just purchased a new Mac Pro 8 core with 32GB of ram and 1 TB drive. When I connect a USB powered 3.0 hub and turn on my Mac Pro, it gets hung on while booting. (Gray screen before the Apple logo appears on boot). If I pull the USB 3.0 hub out, the Mac Pro proceeds to boot normally. Once I am fully booted on my Mac Pro and I plug the USB 3.0 hub back in, everything seems to work fine. I have an enclosure that works off of lightening connector and the enclosure has a USB 3.0 hub onboard. I plug the USB 3.0 hub in that device and every thing seems to boot up fine on the Mac Pro. Any idea why when I plug in the USB 3.0 directly why the Mac Pro ha issues booting up?
Thanks in Advance.

The Driver for the Hub does not get loaded until late in the Boot-up process.
It is common not to be able to use devices on a Hub during boot-up, as they will not be ready (and therefore not available) until the Login screen appears.
For devices you need during boot-up, attach directly to a built-in USB port on the chassis, not on a display or any other Hub.
If your issue is only that the device interferes with Booting in general, ask the guys at OWC. They select their stocked items for trouble-free, and train their support people to resolve remaining problems quickly. If there is a problem, they will help you get is fixed quickly -- often providing an advanced exchange if that seems appropriate.

Similar Messages

How do I speed up Lightroom on my new Mac Pro (2013)?

I have tried everything suggested in the forums like running imports in parallel, etc., and all my data is on the super fast built-in PCI-Express SSD of the Mac Pro. However, I have numerous speed problems with Lightroom 5.3 (latest version) when importing and working with photos.
Right now, here is what I am doing
* Performing three parallel imports for maximum speed as suggested in September, 2013 (to supposedly boost input from 25% CPU to 60% on a multi-core machine).
* Buildling 1:1 previews and all the other suggested official Lightroom Performance tips
And what I am getting:
* Between 11 to 15% CPU utilization, even when running imports and building previews in parallel.
* Data being read at only 2.5 to 6.5 MB per second.
* When I look at images even after the previews have been built, I see a sharp image for about 1/100th of a second, then it blurs for about 3/4 of a second, then it sharpens up again in about one second, as if Lightroom is redeveloping it again despite having a 1:1 preview fully built.
To my workflow, this is horrifically slow. I am tasked to go through about 5,300 sports photography images in an hour if possible, many taken at over 10 frames per second with a 1D X. To do this efficiently requires being able to INSTANTLY see the exact sharpness of a photograph, not being blurred for a full second, so that I can pick out the sharpest image from a burst of many images of each top play.
I love the features of being able to flag/unflag with P and U, star with 1-5, go full screen with F, zoom with Z, crop with R, etc., but the productivity potential that those fantastic keyboards shortcuts have is being utterly defeated by the fact that Lightroom is going SUPER slow even on this brand new 6-core Mac Pro. It literally is much slower than using Picasa or FastStone on a cheap Core i3 laptop with a regular HDD.
How can I configure Lightroom to use all six cores and more of the hard drive speed to speed up my workflow?
Obviously, Lightroom should be able to do much better if it were using more than 15% of the CPU and more than 1% of the SSD capability.
For me this is a SERIOUS problem and is preventing my new Mac Pro purchase from being any use to me. I am having to use other software right now to meet my production deadlines, and then go back through it later on Lightroom at a glacially slow pace. After a couple weeks of this duplicated workflow, I am just getting tired of it.

Maybe you could help us help you by providing your systen details in full the location of your files.
Thank you...

Creative Cloud Desktop App crashes on new Mac Pro 2013

After using Migration Assistant to move apps from my 2010 MBP to a new Mac Pro 6,1 (OSX 10.9.1), I find that the Creative Cloud Desktop App consistently crashes right after entering my ID and password (whether started as a menu bar item or separate window). I have uninstalled and reinstalled several times with the same result. Below is a partial crashdump (I have the complete listing available):
Process:         Creative Cloud [541]
Path:            /Applications/Utilities/Adobe Creative Cloud/*/Creative Cloud.app/Contents/MacOS/Creative Cloud
Identifier:      com.adobe.acc.AdobeCreativeCloud
Version:         1.4.0.348 (???)
Code Type:       X86 (Native)
Parent Process: launchd [159]
Responsible:     Creative Cloud [541]
User ID:         501
Date/Time:       2014-02-12 09:01:44.196 -0500
OS Version:      Mac OS X 10.9.1 (13B4116)
Report Version: 11
Anonymous UUID: 62963EDC-D8F8-8862-AD7C-BC6179E3E2DC
Crashed Thread: 31
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSXMLDocument initWithXMLString:options:error:]: nil argument'

Thanks for this. In the Cleaner App, I only saw Application Manager for OS 10.6 (other than my installed CC apps). I cleaned this one only. However after restarting, athough the cleaner said the uninstall was successful, I could not find any log file for the Cleaner App. I still reinstalled the CC Desktop App, but with the same results.
Do I need to uninstall ALL the CC apps?
Thanks again.

New Mac Pro with Thunderbolt and USB 3.0

it is exceedingly frustrating to be waiting with no surety that there will be an upgraded Thunderbolt and USB3.0 Mac Pro in the pipeline. professional doing advanced graphics and video need this and need it now and need for certain a time schedule to plan partial investment in new Equipment. Apple has let is down for two years now and surely the second largest corporation on the planet can afford the R and D for it and certainly it would cost the company nothing to let us in on this schedule. there is no real competition for this. it is not giving away any advantage but it certainly would give is some ammunition to prevent bean counters from instituting a wholesale move to Dell or others. We need some serious upgrading and we need a heads up on when.

The iMac would require a Magma outboard PCIx box that doubles the cost of the IMac and still does not do the job. that approach is a kludge to try to use an amateur user machine to do what a professional workstation can do, with The assorted updates I applied to my Mac Pro though it is not as fast at processing as the top of the line iMac it was much more flexible, can run many screens without having to buy new thunderbolt screens and with USB 3 and eSATA cards bypass reasonably the lack of Thunderbolt in the short term but it is a ridiculous and non Mac way to have to run,my work station. And..I am sure I am not alone...Apple better get their act together in the professional market or they will have kissed off many of is in another year.. that would be a huge pity. As well the iMac screen is insufficient and lacks a full Adobe colour palette and its incorrect black levels and inability to be controlled by such tools as a Huey make the screen good only for menus and control panels. that is why I still use the Mac 30 inch and also a Dell 30 inch screen as they can be calibrated accurately which the iMac can not. the only solution is a new Mac Pro. for the contributor who suggested I contact feedback already regarding this..I had done that but I figured that they must scan the discussion groups to find out what customers feel about user situations and the more responses to my comments the better the argument for new hardware.

Premiere pro cc and new mac pro 2013

There is so much being written about Adobe CC (Premiere Pro) not working well on the new mac pro that I just want a final clarification from Adobe:
1. Does Premiere Pro work well on the new machines and is the software set up to make use of the new machine elements- like dual GPUs etc??
2. If not is this in the pipeline for Premiere Pro CC updates and any estimates on when?
Thanks
David

Zomid wrote:
There is so much being written about Adobe CC (Premiere Pro) not working well on the new mac pro that I just want a final clarification from Adobe:
You do realize that, for the most part, this is a User forum, not a Support one? We have participation from various Adobe employees due to good will more than anything. They don't and won't share road map stuff with us until they're ready to announce it to the whole world.
I think you're asking the wrong question on the wrong forum.
Pr CC and AME CC are both set up to make use of the dual GPUs on the new Mac. Several of us have already shared our experience with CC on the new Mac Pro; for the most part it's very favorable. A few folks are still having some difficulty with it; hopefully they've opened support cases with Adobe to get that straightened out.

New Mac Pro 2013: some premature doubts...

Hi all!
The New Mac Pro seems really cool, but I have some doubts:
1) will it have just One processor? In terms computation speed, present Mac Pro is not the best on the market: doubling it, will Of course ne interesting, but not "incredible";
2) adopting just One proc will limit the number Of cores to the maximum amount Of a single E5 (8?): that's not that much;
3) just 4 RAM slots? So the Max RAM would be 64 GB...
If this is the hardware, it will not be suited for massively-parrallel computation...
I think (and hope) Apple will provide a 2-core Mac Pro like nowadays!!!
What do You think??
Best
H

One cpu with up to 12 cores, not two.
For now 64GB. Every time Apple rolls out a new Pro they under spec RAM (and don't change the support pages).
OWC and others are working on testing but the format docs do say that 10.9 will now support a full 128GB ($$$ for 4x32GB DIMMs)
E5's that support the higher clocked DIMMs may not be available except in labs and engineering.
10.9 does support 4x16GB (the 5,1 do not / did not, only 3x16) and that seems to be a firmware thing right now - you need to change the cpu daughter card (not happening likely) or the DIMM's firmware (maybe) or patch in the kernel (very possible and why 10.8 support for 96GB came and went).
So yes if you want 4-way / 24-48 core cpu and 256GB RAM you need to look elsewhere.
But a single cpu w/ 12 cores is more effecient, less latency, no need QuickPath or peeking or snooping or predictive memory addresses, 24MB L3 cache, and shuffling from one bank to another, from cpu A to cpu B (about 30% hit or 2nd cpu was only in some cases adding 70% to the task at hand).
Could dual AMD be using a CrossFire-X? that would make sense, yes?

PPro Performance Variance on Mac Pro 2013: CC Version 7.0 vs. Version 8.0

Hi,
I've been editing on a late 2013 Mac Pro model with Yosemite (see system specs in the JPEG below). I have really mixed results editing with the most up to date version of Premiere Pro CC. Playback in a timeline lags significantly with 4K and standard HD 1080p media and the software crashes more often than I would like. I have tried a few things like checking the permissions status of varying media and project folders. I do not use GPU-based rendering as that has been problematic, creating pink lines etc. in the resulting previews and exports. Even after previews are rendered for a timeline, playback still lags regardless of media resolution.
In general, as a Premiere project becomes more complex, crashes become more frequent and playback lags even more. Dynamic Linking with AE causes so many crashes that is basically not functional. The only plug-ins I'm using are Magic Bullet and FilmConvert.
I'm not a huge fan of the shift in workflow/edit logic in FCP X, and want to avoid making that transition if I can. In an attempt to test the varied performance of Premiere, I have reverted to a previous version, CC 7.0. MY initial testing shows that this version renders previews more quickly (still without GPU assistance) and playback seems to lag less. Of course I imported an XML from a project originating in V. 8.0 and there are a few translation issues mostly related to warp stabilizing and color correction, which can be fixed if the overall performance boost is greater.
I have read a handful of forums of users experiencing similar or even more drastic difficulty running Premiere on a new MacPro platform. I have explored some of the troubleshoots suggested, but no major changes in performance. It seems to be hit or miss in terms of Premiere/MacPros playing well together. Strange that no one factor can seem to be pinpointed.
Has anyone else been fiddling with this option of using a previous version of Premiere on a Mac Pro? Any success? Other suggestions to improve performance in the latest version?
Thanks!

I just had an interesting thought.
I use the method of dragging a clip to the "new item" button to create a matching sequence of my majority media type for a project. Have there been any bugs or issues reported with this technique on the latest version of Premiere Pro CC? This is a possibility I haven't yet explored in terms of the issues I am experiencing with playback. When this thought dawned on me today, I took a look at my sequence settings in a troublesome clip, and am not sure it quite matches up. In this example, details in screenshot below, my majority footage was shot on a Canon XA20. The resulting sequence is using at ARRI Cinema editing mode. That seems to be a mis-match, but maybe not? Thoughts? Suggestions? Helpful resources about "editing modes" and optimization for playback? Any help appreciated. Thanks!

How can i use 3(or more) hdmi monitors with the new Mac Pro(2013)?

I've been looking around, trying to find a solution to this problem.
I saw at one place that an active thunderbold -> DVI will work with the older mac pro model.
Will this work with the new one as well?
Will i be able to connect 3 screens if i use 2 passive thunderbold->hdmi and one
active thunderbold->dvi and then a dvi->hdmi?

If you need to buy Apple's $99 Mini DisplayPort to Dual-Link DVI Adapters you may find you need to return and replace the adapter/s till you find one that works.
Recently, after my nMP arrived I bought two adapters. It took 3 trips to the Apple store to find a second one that worked properly. This also happened a few months ago when I was buying those adapters.
You should be aware that you'll also need the DVI cable that has the full set of pins, not the one with the row in the middle missing.
If you check on the Apple customer reviews in the online store you'lll find the issues and possible solutions to this situation.
Eventually I returned the second adapter when I found a way to get 2560 x 1600 through the HDMI port. I now have two 30" monitors that display 2560 x 1600.

Mac pro stopped charging after used old OS X dvd during boot camp partitioning

Macbook Pro, 15", Mid 2010, 2.4GHz i5, OS 10.6.8.
Need to split hard drive and install (via boot camp) Win 7 as want to run windows only CAD software.
During partitioning, boot camp asked me to insert original install discs. Couldn't find discs (don't recall ever seeing them)... so borrowed "15" Mac Book Pro Mac OS X Install DVD" disc from neighbour... inserted that (fingers crossed)... and completed partitioning.
But then found Mac switched off when I accidentally knocked power cable out of the Mac. Also note clock/caldendar needs resetting on each power up now, mac doesnt charge anymore (according to icon/batt status) running when on mains power only ...
Have just upgraded to Lion 10.7.2 (as wanted new features and hoped that might sort problem) but no improvement. Guess I've screwed up some of the low levels drivers....!?!
Too late to use time machine or time capsule as only just learnt about them!
Can anyone advise please?

You cannot use discs from another Mac unless they are exactly the same OS build as yours, for the exact same model as yours. The discs contain only the drivers for the hardware on that Mac, and there are other variants in software.
It's a minor miracle you can still boot at all.
Your own original discs will probably still be in the box, in a small box labeled 'everything else' (or something similar) which also contains the warranty booklet and a welcome to OS X guide.
You'll need to find those and start from scratch with a re-install to repair the damaged power management software, then do the Lion upgrade again.
Unfortunately, it may not work as simply as that, as getting back to SL from Lion isn't straightforward; just check the forums for the multiple threads on the issue.

New Mac Pro (late 2013) crashes / freezes while rendering or editing in Premiere Pro CC

We recently purchased a new Mac Pro desktop (Late 2013, 16GB memory, D700 Graphic Card, 2.7 GHz -12 Core, OSX 10.9.3) and we are running Adobe CC on it. When using Premiere Pro CC (7.2.2) I am having major issues while rendering and editing. About 50% of the time when I try to render it starts off real fast then just freezes. This happens in Premiere and Media Encoder. Sometimes I can just Force Quit Premiere or Media Encoder and other times I have to do a hard restart on the entire computer because the entire computer freezes. The computer will also occasionally freeze whenever doing simple editing or stacking layers. The computer will also just decide to suddenly stop and restart when editing or doing simple tasks like browsing the web. Additionally there has been several times if the render does finish, the final video will have digital glitches throughout the video. I have to redo the render once or twice and it will finally be fine. This all is happening several times a day. This never happened on our previous Mac Pro, but we were not running Mavericks. I used Migration Assistant to transfer from old computer to new computer. So I don't know if this is an a problem with the actual Mac Pro, Mavericks, graphic card or Adobe? But right now I am very frustrated as you can imaging spending all this money for a computer that has been giving us more issues than our previous computer. Any help would be greatly appreciated!

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. All it does is to collect information about the state of the computer. That information goes nowhere unless you choose to share it. However, you should be cautious about running any kind of program (not just a shell script) at the behest of a stranger. If you have doubts, search this site for other discussions in which this procedure has been followed without any report of ill effects. If you can't satisfy yourself that the instructions are safe, don't follow them. Ask for other options.
Here's a summary of what you need to do, if you choose to proceed:
☞ Copy a line of text in this window to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
The sequence is: copy, paste, wait, paste again. You don't need to copy a second time. Details follow.
4. You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode, under the conditions in which the problem is reproduced. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
5. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
6. The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in the browser window, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
Triple-click anywhere in the line of text below on this page to select it:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec;clear;cd;p=(Software Hardware Memory Diagnostics Power FireWire Thunderbolt USB Fonts 51 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports 'com.autodesk.AutoCad com.evenflow.dropbox com.google.GoogleDrive' DYLD_INSERT_LIBRARIES\ DYLD_LIBRARY_PATH -86 ` route -n get default|awk '/e:/{print $2}' ` 25 N\\/A down up 102400 25600 recvfrom sendto CFBundleIdentifier 25 25 25 1000 MB );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^$[0-9]+$ /,"");n=$0;getline;} $NF=="'${p[26]}')" { sub(/.$/,"",$NF);print n;exit;} ' `;f=('\n%s: %s\n' '\n%s\n\n%s\n' '\nRAM details\n%s\n' %s\ %s '%s\n\t(%s)\n' );S0() { echo ' { q=$NF+0;$NF="";u=$(NF-1);$(NF-1)="";gsub(/^ +| +$/,"");if(q>='${p[$1]}') printf("%s (UID %s) is using %s '${p[$2]}'",$0,u,q);} ';};s=(' /^ *$|CSConfigDot/d;s/^ */ /;s/[-0-9A-Fa-f]{22,}/UUID/g;s/(ochat)\.[^.]+(\..+)/\1\2/;/Shared/!s/\/Users\/[^/]+/~/g ' ' s/^ +//;5p;6p;8p;12p;' ' {sub(/^ +/,"")};NR==6;NR==13&&$2<'${p[10]} ' 1s/://;3,6d;/[my].+:/d;s/^ {4}//;H;${ g;s/\n$//;/s: [^EO]|x([^08]|02[^F]|8[^0])/p;} ' ' 5h;6{ H;g;/P/!p;} ' ' ($1~/^Cy/&&$3>'${p[11]}')||($1~/^Cond/&&$2!~/^N/) ' ' /:$/{ N;/:.+:/d;s/ *://;b0'$'\n'' };/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;};$b0'$'\n'' d;:0'$'\n'' x;s/\n\n//;/Apple[ ,]|Intel|SMSC/d;s/\n.*//;/\)$/p;' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/ / { n++;print;} END { if(n<200) print "com.apple.";} ' ' $3~/[0-9]:[0-9]{2}$/ { gsub(/:[0-9:a-f]{14}/,"");} { print|"tail -n'${p[12]}'";} ' ' NR==2&&$4<='${p[13]}' { print $4;} ' ' END { $2/=256;if($2>='${p[15]}') print int($2) } ' ' NR!=13{next};{sub(/[+-]$/,"",$NF)};'"`S0 21 22`" 'NR!=2{next}'"`S0 37 17`" ' NR!=5||$8!~/[RW]/{next};{ $(NF-1)=$1;$NF=int($NF/10000000);for(i=1;i<=3;i++){$i="";$(NF-1-i)="";};};'"`S0 19 20`" 's:^:/:p' '/\.kext\/(Contents\/)?Info\.plist$/p' 's/^.{52}(.+) <.+/\1/p' ' /Launch[AD].+\.plist$/ { n++;print;} END { if(n<200) print "/System/";} ' '/\.xpc\/(Contents\/)?Info\.plist$/p' ' NR>1&&!/0x|\.[0-9]+$|com\.apple\.launchctl\.(Aqua|Background|System)$/ { print $3;} ' ' /\.(framew|lproj)|\):/d;/plist:|:.+(Mach|scrip)/s/:[^:]+//p ' '/root/p' ' !/\/Contents\/.+\/Contents|Applic|Autom|Frameworks/&&/Lib.+\/Info.plist$/ { n++;print;} END { if(n<1000) print "/System/";} ' '/^\/usr\/lib\/.+dylib$/p' ' /Temp|emac/d;/(etc|Preferences)\//s/^\.\/[^/]+//p;' ' /\/(Contents\/.+\/Contents|Frameworks)\/|\.wdgt\/.+\.[bw]/d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| ","||kMDItem'${p[35]}'=");sub("^.."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[9]}'{$2=$2-1;print}' ' BEGIN { i="'${p[26]}'";M1='${p[16]}';M2='${p[18]}';M3='${p[31]}';M4='${p[32]}';} !/^A/ { next;} /%/ { getline;if($5<M1) a="user "$2"%, system "$4"%";} /disk0/&&$4>M2 { b=$3" ops/s, "$4" blocks/s";} $2==i { if(c) { d=$3+$4+$5+$6;next;};if($4>M3||$6>M4) c=int($4/1024)" in, "int($6/1024)" out";} END { if(a) print "CPU: "a;if(b) print "I/O: "b;if(c) print "Net: "c" (KiB/s)";if(d) print "Net errors: "d" packets/s";} ' ' /r\[0\] /&&$NF!~/^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./ { print $NF;exit;} ' ' !/^T/ { printf "(static)";exit;} ' '/apsd|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' $1~"lR"&&$2<='${p[25]}';$1~"li"&&$3!~"wpa2";' ' BEGIN { FS=":";} { n=split($3,a,".");sub(/_2[01].+/,"",$3);print $2" "$3" "a[n]" "$1;b=b$1;} END { if(b) print("\n\t* Code injection");} ' ' NR!=4{next} {$NF/=10240} '"`S0 27 14`" ' END { if($3~/[0-9]/)print$3;} ' ' BEGIN { L='${p[36]}';} !/^[[:space:]]*(#.*)?$/ { l++;if(l<=L) f=f"\n "$0;} END { F=FILENAME;if(!F) exit;if(!f) f="\n [N/A]";"file -b "F|getline T;if(T!~/^(AS.+ (En.+ )?text$|POSIX sh.+ text ex)/) F=F" ("T")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n ...and %s more line(s)\n",l-L);} ' ' BEGIN{FS="= "} /Path/{print $2} ' ' /^ +B/{ s/.+= |(-[0-9]+)?\.s.+//g;p;} ' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' / /{$0="'"${p[28]}"'"};1;' '/ en/!s/\.//p' ' NR!=13{next};{sub(/[+-M]$/,"",$NF)};'"`S0 39 40`" ' $10~/$L/&&$9!~"localhost" { sub(/.+:/,"",$9);print $1": "$9;} ' '/^ +r/s/.+"(.+)".+/\1/p' 's/(.+\.wdgt)\/(Contents\/)?Info\.plist$/\1/p' 's/^.+\/(.+)\.wdgt$/\1/p' );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps sudo\ crontab sudo\ iotop top pkgutil PlistBuddy whoami cksum kextstat launchctl sudo\ launchctl crontab 'sudo defaults read' stat lsbom mdfind ' for i in ${p[24]};do ${c1[18]} ${c2[27]} $i;done;' defaults\ read scutil sudo\ dtrace sudo\ profiles sed\ -En awk /S*/*/P*/*/*/C*/*/airport networksetup mdutil sudo\ lsof test );c2=(com.apple.loginwindow\ LoginHook '-c Print /L*/P*/loginw*' '-c Print L*/P*/*loginit*' '-c Print L*/Saf*/*/E*.plist' '~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' '-c Print\ :'${p[35]}' 2>&1' '-c Print\ :Label 2>&1' '{/,}L*/{Con,Pref}* -type f ! -size 0 -name *.plist -exec plutil -s {} \;' "-f'%N: %l' Desktop L*/Keyc*" therm sysload boot-args status " -F '\$Time \$Message' -k Sender kernel -k Message Req 'Beac|caug|dead[^bl]|FAIL|GPU |hfs: Ru|inval|jnl:|last value [1-9]|n Cause: -|NVDA$|pagin|proc: t|Roamed|rror|ssert|Thrott|tim(ed? ?|ing )o|WARN' -k Message Rne 'Goog|ksadm|SMC:' -o -k Sender fseventsd -k Message Req 'SL' " '-du -n DEV -n EDEV 1 10' 'acrx -o comm,ruid,%cpu' '-t1 10 1' '-f -pfc /var/db/r*/com.apple.*.{BS,Bas,Es,OSXU,Rem,up}*.bom' '{/,}L*/Lo*/Diag* -type f -regex .\*[cgh] ! -name *ag \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true $ -execdir stat -f:%Sc:%N -t%F {} \;|sort -t: -k2 |tail -n'${p[38]} '-L {/{S*/,},}L*/Lau* -type f' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,E}* {/,}L*/{A*d,Ca*/*/Ex,Compon,Ex,In,iTu,Keyb,Mail/B,P*P,Qu*T,Scripti,Sec,Servi,Spo,Widg}* -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto,{cron,fs}tab,hosts,[lps]*.conf,pam.d,ssh{,d}_config,*.local} {,/usr/local}/etc/periodic/*/* /L*/P*{,/*}/com.a*.{Bo,sec*.ap}* .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers -getinfo\ "${p[N5]}" -P -m\ / '' -n1 '-R -l1 -n1 -o prt -stats command,uid,prt' '--regexp --only-files --files com.apple.pkg.*|sort|uniq' -kl -l -s\ / '-R -l1 -n1 -o mem -stats command,uid,mem' -i4TCP:0-1023 com.apple.dashboard\ layer-gadgets '-d /L*/Mana*/$USER&&echo On' );N1=${#c2[@]};for j in {0..8};do c2[N1+j]=SP${p[j]}DataType;done;N2=${#c2[@]};for j in 0 1;do c2[N2+j]="-n ' syscall::'${p[33+j]}':return { @out[execname,uid]=sum(arg0) } tick-10sec { trunc(@out,1);exit(0);} '";done;l=(Restricted\ files Hidden\ apps 'Elapsed time (s)' POST Battery Safari\ extensions Bad\ plists 'High file counts' User Heat System\ load boot\ args FileVault Diagnostic\ reports Log 'Free space (MiB)' 'Swap (MiB)' Activity 'CPU per process' Login\ hook 'I/O per process' Mach\ ports kexts Daemons Agents launchd Startup\ items Admin\ access Root\ access Bundles dylibs Apps Font\ issues Inserted\ dylibs Firewall Proxies DNS TCP/IP Wi-Fi Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' Spotlight Memory Listeners Widgets Parental\ Controls );N3=${#l[@]};for i in 0 1 2;do l[N3+i]=${p[5+i]};done;N4=${#l[@]};for j in 0 1;do l[N4+j]="Current ${p[29+j]}stream data";done;A0() { id -G|grep -qw 80;v[1]=$?;((v[1]==0))&&sudo true;v[2]=$?;v[3]=`date +%s`;clear >&-;date '+Start time: %T %D%n';};for i in 0 1;do eval ' A'$((1+i))'() { v=` eval "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "$v" ]];};A'$((3+i))'() { v=` while read i;do [[ "$i" ]]&&eval "${c1[$1]} ${c2[$2]}" \"$i\"|'${c1[30+i]}' "${s[$3]}";done<<<"${v[$4]}" `;[[ "$v" ]];};A'$((5+i))'() { v=` while read i;do '${c1[30+i]}' "${s[$1]}" "$i";done<<<"${v[$2]}" `;[[ "$v" ]];};';done;A7(){ v=$((`date +%s`-v[3]));};B2(){ v[$1]="$v";};for i in 0 1;do eval ' B'$i'() { v=;((v['$((i+1))']==0))||{ v=No;false;};};B'$((3+i))'() { v[$2]=`'${c1[30+i]}' "${s[$3]}"<<<"${v[$1]}"`;} ';done;B5(){ v[$1]="${v[$1]}"$'\n'"${v[$2]}";};B6() { v=` paste -d: <(printf "${v[$1]}") <(printf "${v[$2]}")|awk -F: ' {printf("'"${f[$3]}"'",$1,$2)} ' `;};B7(){ v=`grep -Fv "${v[$1]}"<<<"$v"`;};C0(){ [[ "$v" ]]&&echo "$v";};C1() { [[ "$v" ]]&&printf "${f[$1]}" "${l[$2]}" "$v";};C2() { v=`echo $v`;[[ "$v" != 0 ]]&&C1 0 $1;};C3() { v=`sed -E "$s"<<<"$v"`&&C1 1 $1;};for i in 1 2;do for j in 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;{ A0;A2 0 $((N1+1)) 2;C0;A1 0 $N1 1;C0;B0;C2 27;B0&&! B1&&C2 28;D12 15 37 25 8;A1 0 $((N1+2)) 3;C0;D13 0 $((N1+3)) 4 3;D23 0 $((N1+4)) 5 4;for i in 0 1 2;do D13 0 $((N1+5+i)) 6 $((N3+i));done;D13 1 10 7 9;D13 1 11 8 10;D22 2 12 9 11;D12 3 13 10 12;D23 4 19 44 13;D23 5 14 12 14;D22 6 36 13 15;D22 7 37 14 16;D23 8 15 38 17;D22 9 16 16 18;B1&&{ D22 11 17 17 20;for i in 0 1;do D22 28 $((N2+i)) 45 $((N4+i));done;};D22 12 44 54 45;D22 12 39 15 21;A1 13 40 18;B2 4;B3 4 0 19;A3 14 6 32 0;B4 0 5 11;A1 17 41 20;B7 5;C3 22;B4 4 6 21;A3 14 7 32 6;B4 0 7 11;B3 4 0 22;A3 14 6 32 0;B4 0 8 11;B5 7 8;B1&&{ A2 19 26 23;B7 7;C3 23;};A2 18 26 23;B7 7;C3 24;A2 4 20 21;B7 6;B2 9;A4 14 7 52 9;B2 10;B6 9 10 4;C3 25;D13 4 21 24 26;B4 4 12 26;B3 4 13 27;A1 4 22 29;B7 12;B2 14;A4 14 6 52 14;B2 15;B6 14 15 4;B3 0 0 30;C3 29;A1 4 23 27;B7 13;C3 30;D13 24 24 32 31;D13 25 37 32 33;A1 23 18 28;B2 16;A2 16 25 33;B7 16;B3 0 0 34;B2 21;A6 47 21&&C0;B1&&{ D13 21 0 32 19;D13 10 42 32 40;D22 29 35 46 39;};D23 14 1 48 42;D12 34 43 53 44;D22 0 $((N1+8)) 51 32;D13 4 8 41 6;D12 26 28 35 34;D13 27 29 36 35;A2 27 32 39&&{ B2 19;A2 33 33 40;B2 20;B6 19 20 3;};C2 36;D23 33 34 42 37;B1&&D23 35 45 55 46;D23 32 31 43 38;D12 36 47 32 48;D13 20 42 32 41;D23 14 2 48 43;D13 4 5 32 1;D22 4 4 50 0;D13 14 3 49 5;B3 4 22 57;A1 26 46 56;B7 22;B3 0 0 58;C3 47;D23 22 9 37 7;A7;C2 2;} 2>/dev/null|pbcopy;exit 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
7. Launch the built-in Terminal 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 Terminal in the icon grid.
Click anywhere in the Terminal window and paste by pressing command-V. The text you pasted should vanish immediately. If it doesn't, press the return key.
8. If you see an error message in the Terminal window such as "syntax error," enter
exec bash
and press return. Then paste the script again.
9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important. If you don't know the password, or if you prefer not to enter it, press the key combination control-C or just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, there will be nothing in the Terminal window and no indication of progress. Wait for the line
[Process completed]
to appear. If you don't see it within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report the results. No harm will be done.
11. When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with "Model Identifier." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
12. When you post the results, you might see the message, "You have included content in your post that is not permitted." It means that the forum software has misidentified something in the post as a violation of the rules. If that happens, please post the test results on Pastebin, then post a link here to the page you created.
Note: This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
Copyright © 2014 by Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Wireless apple keyboard does not connect to new Mac Pro Late 2013

I just got my new Mac Pro 2013 and I can not connect it to my wireless apple keyboard. I am not able to set up and run the system. Any thoughts? Thanks in advance!

How to reset as Apple wireless keyboard, mouse or trackpad(troubleshooting pairing and other common problems):
http://davemeehan.com/technology/how-to-reset-an-apple-wireless-bluetooth-keyboa rd-mouse-or-trackpad

USB keyboard not working on new Mac Pro with Mavericks

I just bought the new Mac Pro and my apple USB keyboard won't work. I have a very old apple USB keyboard that is working but I want to use my newer one. The newer keyboard is a full one also, including the number pad.
Thanks

no difference in ports just troubleshooting, ie if it didn't work on any of the 4 ports, likely a kb issue
if it worked on one of the other 3 ports, you have a broken usb port on the mac pro

I have a brand new Mac Pro Tower that continually kicks me off the internet and sometimes starts up not connecting to the internet?

My brand new Mac Pro Tower that I spent a small fortune on sometimes boots up and does not connect to the internet when every other computer in my office does and other times it just kicks me straight off. My question is, is there a problem with the wi fi on these machines?

Brand new nMP Mac Pro 6,1 Late 2013.... and it is defective - the older silver tower might be easier to find parts but at least it is not 65 lbs and is something that can be taken in - which I think you really need to do.
When you run etrecheck from www.etresoft.com it can show what is installed, drivers and might help point to something on software side.
Grant is the go-to person here I think among others for networking issues.
Airport Express and signal strength, channel it is trying to use, whether the Network control panel settings are "correct" or need to be changed (even the order, what it is trying to look for and use).
If you move it to another spot or put another computer over in that general vicinity...? behaves the same.
I recall reading where the MacBook Pro model in 2012? and switched to a new chipset and some very long (huge) threads in their forum - which means also there was no real solution given.
No, should not be. And other than network tests would be booting into Apple DiagnosticsTest mode - pulls down from Apple servers.
http://support.apple.com/kb/HT5781

New Mac Pro and 9.2 Hangs on Adjustments?? Old G5 Doesn't

Hello
I have what should be a very fast new Mac Pro. 6 core at 3.46Ghz. 48Gb of RAM. Solid state boot drive. Software RAID 0 with 2 Hitachi 3TB drives, hardly anything on them yet. Nvidea Quadro 4000 CUDA card. Everything installed and burned in for the overnight 8 hour test with the MPG workstation program at OWC. Lion 10.7.2.
I had approximately 700 in camera photos combined still in camera between an up-to-16MP Sony NEX 5N camera and up-to-24MP pics on a Sony A77, that have already been loaded into my 6-7 year old 2.4Ghz dual core G5 with 6.5Gb RAM and much older version of iPhoto. OS 10.4.7 I believe.
Last night I loaded all those same pictures into the new machine and 9.2 version iPhoto. And then deleted them from the cards on both cameras. No issues. Smoking fast imports compared to the G5 which wasn't all that bad.
On the G5 with the picture adjust controls I could use the slider to go deeply into those same photos and see the effects of contrast, sharpness and all the other options. Like butter. Make the adjustments while in that deep if desired and then pull back to evaluate the overall picture before saving. Or back in again if desired. No issues.
With the new rig I couldn't wait to try all of this, but once I go deep inside and start to move the adjustment slider controls the system every time starts getting hung with the spinning wheel. Have to wait and wait for them to catch up to the curser on that adjustment. Most of the time the system then will just get stuck and I have to force iPhoto to quit.
Please....does anyone know why all this latest powerfull hardware and software is doing that, compared to the old, much less capable G5? I am really concerned now. Haven't had a chance to get Photoshop and the other production premium software tested yet.
And one last question please. Does anyone know if the "Enhance" feature in the Quick Fixes section adjusts Gamma as well? There seems to be a lot more going on to give the photos depth (what I always really try to do) than the sum of the small slider movements in the Adjust section. With my old system and iPhoto version there was no "Gamma" adjust slider in iPhoto proper......but if I saved a photo first to my Desktop for instance, and then called up the adjustment features, there was a Gamma slider there. Very handy and appreciated.
I see similar vast improvements on some photos now with the "Enhance" feature that looks like maybe Gamma has been optimized as well? There now is no Gamma slider available even if the photo is taken to the desktop first.
Thanks much
Ron

Hello Terence
Thanks for the tip to try. Couldn't get to it until late last night. Seems to still be the same in Library 2.
Also seems to be worse with 27" Cinema Display at full resolution. And with several sliders on adjustment. If I drop the resolution to 1920 x 1080 or 1600 x 900 and move smoothly about it is not as apt to hang up. With as much horsepower as the new Mac Pro has, should resolution of monitor be an issue in these adjustments deep into the pictures?
How about the Enhance button? Is gamma involved? Everything I read about it on searches only talks about boosting saturation of the color and fine tuning with little other slider adjustments. But on a picture where it has made a big difference to the good with depth and overall look, if I look at where the sliders were adjusted and then undo the enhance, and go back and manually put the sliders in the same position it doesn't look the same.
Does anyone know if gamma is being adjusted with this button? Sure seems like it but can't find it mentioned anywhere.
Thanks again!

Why mac pro 2013 not supporting illustrator GPU rendering

Here, all nvidia cards supporting this:
http://helpx.adobe.com/illustrator/kb/gpu-performance-preview-improvements.html
now I'm thinking, that buying the new mac pro 2013 maybe wasn't the best idea... Apple put in AMD GPu's, that is fine by me, but come on, give us some more support for them! Normal windows PC (for 800€) with nvidia GPU is faster at rendering in Illustrator, than my workstation mac (3500+€)! Really? O.o
And story doesn't end here. I was reading one article about GPU usage in this new mac pro and then I tested it myself. Only one GPU is used and the other is barely touched! And this goes for Maya, photoshop, illustrator and other adobe programs. I was shocked, that I discovered I have one GPU to warm up my room and only one actually doing all the work.
Ok I understand, that also software developers needs to support stuff and write their software to actually use GPU's, but adobe creative suite is one of examples, where software is actually capable of using GPU via openCL and in some cases even CUDA from nvidia.
And there is one more thing: new mac pro, has 2 identical AMD GPU's inside, which can work in crossfire configuration under windows in bootcamp, but not in OS X. Sometimes I even play some games on my mac and sometimes I'm testing them (I'm artist, but I also like to develop and test some games in my free time) and it's kinda a shame, that I can run games with better performance under windows in bootcamp.
When I bought this computer I thought this is going to rock and sweep up with all my previous machines. Well in practice it is much of unused potential and great room warmer. It's kinda sad, that on my girlfriend's PC I can play games with better frames and details on GF 660GTX than on my mac pro... I know I know, mac's aren't for gaming, but hey, sometimes it is good to get my mind on rest and blow up some enemies!
I'm not saying mac pro isn't great product, which is (very great). But support to use all computer capabilities is very limited and Apple should kick developers in their back side and push them to start developing things to use GPU's more.
I'm also not expecting Apple to jump on their feet and fix problems overnight. No, just start thinking of adding more support and things that would make our computers much more used and not only good decoration on desk. First would be a good steep adding crossfire support to OS X. That might even help at rendering some 3D scenes?
Next step would probably be better cooperation with software developers, like Adobe , Autodesk,... If adobe made good support for GPU rendering in Illustrator, aim that we get that support soon as well. I'm sometimes having a lot of paths and objects and rendering goes pretty slow then.
I'm also thinking about that AMD choice Apple made wasn't so good when you see that Nvidia puts much more effort into supporting more and more stuff, while AMD is sitting idle not even updating their drivers anymore.
Oh and one more thing: Can we please, please, please, please, preeeeeetty please get 10-bit output support on OS X? It's kinda sad, having good mac workstation with 10-bit capable monitor (dell UP2414Q) and no support for it, while other PC workstations all support it... Photoshop is working much better on OS X and here I have much better integration and everything and I really love working in Photoshop running on OS X, but some basic things are missing and I'm really asking myself sometimes: was that good decision? Photoshop was first written for macs and in 2014 there is much better support for adobe software on windows than on OS X. Where went wrong?
Don't take me wrong and think I'm just ranting here without any good reason, but think: buying very expensive computer that is supposed to make creative work easy and painless is actually just on paper. In reality computer potential is pretty much unused and that makes me thinking if I would be much better buying iMac instead of mac pro...
TL;DR: I wish for some more support from Apple for their new expensive mac pro's 2013. They are great piece of equipment, but equivalent PC's running windows are surpassing them in this department, specially when GPU's are involved. Now I would like to point this out to Apple, so I don't know where to write so they will read so I first wrote that here. I hope someone from Apple reads this and give us some feedback on those missing things or maybe I get direction where to write to Apple so I get maybe some response from them(?):
-not enough GPU support for creative software (adobe suite, autodesk,...) - nvidia + windows offering much more for less money?
-no crossfire support on OS X. Any particular reason for that?
-no 10-bit support for 10-bit displays. Why not? Hardware is capable, why software isn't?
-lack of openCL software out there. Apple isn't doing much to get more support or developers just too lazy to put more effort into this? GPGPU isn't the future as some companies are trying to convince us?

Grant Bennet-Alder wrote:
All displays are supported by one GPU -- the display GPU. The second GPU is reserved for un-interrupted GPU computing and has no Display output Hardware.
Anandtech has a discussion of this in his review of the late 2013 Mac Pro.
Under OS X the situation is a bit more complicated. There is no system-wide CrossFire X equivalent that will automatically split up rendering tasks across both GPUs.
By default, one GPU is setup for display duties while the other is used exclusively for GPU compute workloads. GPUs are notoriously bad at context switching, which can severely limit compute performance if the GPU also has to deal with the rendering workloads associated with display in a modern OS. NVIDIA sought to address a similar problem with their Maximus technology, combining Quadro and Tesla cards into a single system for display and compute.
from section 9:
http://www.anandtech.com/show/7603/mac-pro-review-late-2013/9
Another problem here: on windows bootcamp crossfire IS working, but not in OS X. As I wrote, sometimes it would be better to get more rendering power than computing power (actually at current state of GPU computing software, computing GPU isn't working very much if at all). It would be nice to have an option to switch on and off crossfire so we could use more rendering power when needed.
Also not all people are doing video rendering on their computers. What about 3D modelling and 2D work in photosohp? And maybe people like me are occasionally wish to play some games on their mac?
You linked me GPU usage from one program (probably adobe after effects or premiere pro or apple final cut X?), that is probably one of the only pieces of software that actually uses both GPU's under OS X. I made same experiment with software I use and I even tested some software I don't use but it is advertised it is "optimized" for mac pro like pixelmator.
And guess what? Second GPU is 99% time idle. Even when some stuff is using openCL in Photoshop, stuff is still computed on rendering GPU and not on computing one, which makes computing GPU just a good room warmer as I wrote before. Wouldn't be better to at least use second GPU for something than heating air?

New Mac Pro 2013 late version USB 3.0 hub issue during boot

Similar Messages

Maybe you are looking for