Macmini after EFI 1.7 and kvm, no display

New Macmini, late 2012, updated EFI firmware 1.7, GEFEN KVM 2x1 switch, Apple Cinema display 21' :
When directly connected to Apple Cinema Display = OK
When connected through KVM switch (+HDMI to DVI adapter) = black screen on cinema display, mouse & keyboard seem (?) to switch succesfully (flicker on mouse after switching).
No problems previously with older Macmini's and Macbook ...
Any suggestions ???
Thanks

KVM switches are either compatible with Macs or they are problematic at best.
I had a KVM here that when I switched to another screen/keyboard, the screen would stay black, until I disconnected and reconnected the Mac video cable. It was a PITA. Threw it in the trash eventually.
I now have a mini and a nettop Linux box, both connected to the same monitor with DVI and VGA respectively. The screens are switched with a button on the monitor. If I need a keyboard on the Linux box, I attach one, otherwise I ssh into it and use the Apple keyboard. There is a separate wireless USB mouse on the Linux box, as needed.

Similar Messages

Slow MacMini after upgrading to Maverick and later Yosemite.

Gents,
I have had nothing than trouble with my MacMini (late 2009) since i installed Maverick and I hoped some things would improve with Yosemite. That did not happen. I have been through all possible "solutions" but no luck. I hope someone can help me. My MacMini was working like a charm until I installed Maverick.
(PS: My back-up drive is not connected as shown below)
This is my Etrecheck:
Problem description:
MacMini (late 2009) Sluggish after installation Maverick and later Yosemite
EtreCheck version: 2.1.2 (105)
Report generated December 15, 2014 at 7:17:37 PM GMT-2
Hardware Information: ℹ️
Mac mini (Late 2009) (Verified)
Mac mini - model: Macmini3,1
1 2.53 GHz Intel Core 2 Duo CPU: 2-core
4 GB RAM Upgradeable
BANK 0/DIMM0
2 GB DDR3 1067 MHz ok
BANK 1/DIMM0
2 GB DDR3 1067 MHz ok
Bluetooth: Old - Handoff/Airdrop2 not supported
Wireless: en1: 802.11 a/b/g/n
Video Information: ℹ️
NVIDIA GeForce 9400 - VRAM: 256 MB
SyncMaster 1920 x 1080 @ 60 Hz
System Software: ℹ️
OS X 10.10.1 (14B25) - Uptime: 0:5:40
Disk Information: ℹ️
Hitachi HTS543232L9SA02 disk0 : (320.07 GB)
S.M.A.R.T. Status: Verified
EFI (disk0s1) <not mounted> : 210 MB
Macintosh HD (disk0s2) / : 319.21 GB (67.50 GB free)
Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
OPTIARC DVD RW AD-5670S
USB Information: ℹ️
Apple Computer, Inc. IR Receiver
Apple Inc. BRCM2046 Hub
Apple Inc. Bluetooth USB Host Controller
Gatekeeper: ℹ️
Mac App Store and identified developers
Kernel Extensions: ℹ️
/Applications/Elgato Video Capture.app
[not loaded] com.elgato.driver.Pluto2 (1.1) [Support]
/Applications/Toast 10 Titanium/Toast Titanium.app
[not loaded] com.roxio.BluRaySupport (1.1.6) [Support]
/System/Library/Extensions
[not loaded] com.HGST.driver.GDOCKDriver (1.0.3 - SDK 10.7) [Support]
[not loaded] com.avira.kext.FileAccessControl (1.0.0d1 - SDK 10.9) [Support]
[not loaded] com.hzsystems.driver.CDSDAudioCaptureSupport (1.5) [Support]
[not loaded] com.jmicron.driver.jmPeripheralDevice (2.0.2 - SDK 10.5) [Support]
[not loaded] com.sony.driver.dsccamFirmwareUpdaterType00 (1 - SDK 10.6) [Support]
/Users/[redacted]/Library/Services/ToastIt.service/Contents/MacOS
[not loaded] com.roxio.TDIXController (2.0) [Support]
Launch Agents: ℹ️
[not loaded] com.adobe.AAM.Updater-1.0.plist [Support]
[loaded] com.divx.dms.agent.plist [Support]
[loaded] com.divx.update.agent.plist [Support]
[loaded] com.google.keystone.agent.plist [Support]
Launch Daemons: ℹ️
[loaded] com.adobe.fpsaud.plist [Support]
[loaded] com.google.keystone.daemon.plist [Support]
[loaded] com.oracle.java.JavaUpdateHelper.plist [Support]
User Launch Agents: ℹ️
[loaded] com.adobe.ARM.[...].plist [Support]
[invalid?] com.jdibackup.JustCloud.autostart.plist [Support]
[invalid?] com.macupdate.desktop5.scanner.plist [Support]
[invalid?] com.yahoo.YahooContactSyncAgent.plist [Support]
User Login Items: ℹ️
Caffeine ApplicationHidden (/Applications/Caffeine.app)
AdobeResourceSynchronizer Application (/Applications/Adobe Acrobat 8 Professional/Adobe Acrobat Professional.app/Contents/Support/AdobeResourceSynchronizer.app)
G-Technology Assistant ApplicationHidden (/Applications/G-Technology Assistant.app)
Internet Plug-ins: ℹ️
o1dbrowserplugin: Version: 5.38.6.0 - SDK 10.8 [Support]
Google Earth Web Plug-in: Version: 6.1 [Support]
Default Browser: Version: 600 - SDK 10.10
OVSHelper: Version: 1.1 [Support]
AdobeAAMDetect: Version: AdobeAAMDetect 1.0.0.0 - SDK 10.6 [Support]
FlashPlayer-10.6: Version: 16.0.0.235 - SDK 10.6 [Support]
DivX Web Player: Version: 3.2.4.1250 - SDK 10.6 [Support]
AdobePDFViewerNPAPI: Version: 11.0.07 - SDK 10.6 [Support]
Flash Player: Version: 16.0.0.235 - SDK 10.6 [Support]
iPhotoPhotocast: Version: 7.0
googletalkbrowserplugin: Version: 5.38.6.0 - SDK 10.8 [Support]
QuickTime Plugin: Version: 7.7.3
AdobePDFViewer: Version: 8.0.0 [Support]
GarminGpsControl: Version: 4.2.0.0 - SDK 10.8 [Support]
Silverlight: Version: 4.0.51204.0 [Support]
JavaAppletPlugin: Version: Java 7 Update 67 Check version
User internet Plug-ins: ℹ️
BrowserPlus_2.9.8: Version: 2.9.8 [Support]
Google Earth Web Plug-in: Version: 7.0 [Support]
Safari Extensions: ℹ️
ASCPowerTools
Audio Plug-ins: ℹ️
DVCPROHDAudio: Version: 1.2
3rd Party Preference Panes: ℹ️
BrowserPlus [Support]
Flash Player [Support]
Perian [Support]
Time Machine: ℹ️
Skip System Files: NO
Mobile backups: OFF
Auto backup: NO - Auto backup turned off
Volumes being backed up:
Macintosh HD: Disk size: 319.21 GB Disk used: 251.71 GB
Destinations:
MacMini Backup [Local]
Total size: 402.92 GB
Total number of backups: 15
Oldest backup: 2014-10-12 15:52:07 +0000
Last backup: 2014-12-09 00:11:21 +0000
Size of backup disk: Too small
Backup size 402.92 GB < (Disk used 251.71 GB X 3)
Top Processes by CPU: ℹ️
      6% WindowServer
      3% JustCloud
      0% launchd
      0% AppleSpell
      0% SystemUIServer
Top Processes by Memory: ℹ️
137 MB Dock
82 MB CalendarAgent
77 MB Spotlight
73 MB com.apple.internetaccounts
73 MB NotificationCenter
Virtual Memory Information: ℹ️
62 MB Free RAM
1.71 GB Active RAM
1.70 GB Inactive RAM
554 MB Wired RAM
1.16 GB Page-ins
471 KB Page-outs
Diagnostics Information: ℹ️
Dec 15, 2014, 07:12:36 PM Self test - passed
Dec 15, 2014, 10:34:27 AM com.apple.AmbientDisplayAgent_2014-12-15...crash

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.
Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
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. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.
You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.
In this case, however, there are a couple of ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone with the necessary skill can verify what it does.
You may not be able to understand the script yourself. But variations of the script have been posted on this website thousands of times over a period of years. The site is hosted by Apple, which does not allow it to be used to distribute harmful software. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message.
Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.
4. 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.
5. 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.
6. 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.
7. 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 SerialATA 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports ' com.clark.\* \*dropbox \*genieo\* \*GoogleDr\* \*k.AutoCAD\* \*k.Maya\* vidinst\* ' 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 ' com.adobe.AAM.Updater-1.0 com.adobe.AAM.Updater-1.0 com.adobe.AdobeCreativeCloud com.adobe.CS4ServiceManager com.adobe.CS5ServiceManager com.adobe.fpsaud com.adobe.SwitchBoard com.adobe.SwitchBoard com.apple.aelwriter com.apple.AirPortBaseStationAgent com.apple.FolderActions.enabled com.apple.installer.osmessagetracing com.apple.mrt.uiagent com.apple.ReportCrash.Self com.apple.rpmuxd com.apple.SafariNotificationAgent com.apple.usbmuxd com.citrixonline.GoToMeeting.G2MUpdate com.google.keystone.agent com.google.keystone.daemon com.microsoft.office.licensing.helper com.oracle.java.Helper-Tool com.oracle.java.JavaUpdateHelper com.oracle.java.JavaUpdateHelper org.macosforge.xquartz.privileged_startx org.macosforge.xquartz.privileged_startx org.macosforge.xquartz.startx ' ' 879294308 4071182229 461455494 3627668074 1083382502 1274181950 1855907737 2758863019 1848501757 464843899 3694147963 1233118628 2456546649 2806998573 2778718105 2636415542 842973933 2051385900 3301885676 891055588 998894468 695903914 1443423563 4136085286 523110921 2883943871 3873345487 ' 51 5120 files );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=(' s/[0-9A-Za-z._]+@[0-9A-Za-z.]+\.[0-9A-Za-z]{2,4}/EMAIL/g;/faceb/s/(at\.)[^.]+/\1NAME/g;/\/Shared/!s/(\/Users\/)[^ /]+/\1USER/g;s/[-0-9A-Fa-f]{22,}/UUID/g;' ' s/^ +//;/de: S|[nst]:/p;' ' {sub(/^ +/,"")};/er:/;/y:/&&$2<'${p[10]} ' 1s/://;3,6d;/[my].+:/d;s/^ {4}//;H;${ g;s/\n$//;/s: (E[^m]|[^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[ ,]|Genesy|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<10) print "com.apple.";} ' ' { sub(/ :/,"");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<1100) print "/System/";} ' '/^\/usr\/lib\/.+dylib$/p' ' /Temp|emac/{next};/(etc|Preferences|Launch[AD].+)\// { sub(".(/private)?","");n++;print;} END { split("'"${p[41]}"'",b);split("'"${p[42]}"'",c);for(i in b) print b[i]".plist\t"c[i];if(n<500) print "Launch";} ' ' /\/(Contents\/.+\/Contents|Frameworks)\/|\.wdgt\/.+\.([bw]|plu)/d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| |\n","\\|\\|kMDItem'${p[35]}'=");sub("^...."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[43]}'{$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|BKAg|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' $1~"lR"&&$2<='${p[25]}';$1~"li"&&$3!~"wpa2";' ' BEGIN { FS=":";p="uniq -c|sed -E '"'s/ +\$[0-9]+\$\$.+\$/\\\2 x\\\1/;s/x1$//'"'";} { n=split($3,a,".");sub(/_2[01].+/,"",$3);print $2" "$3" "a[n]$1|p;b=b$1;} END { close(p);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]";"cksum "F|getline C;split(C, A);C="checksum "A[1];"file -b "F|getline T;if(T!~/^(AS.+ (En.+ )?text(, with v.+)?$|(Bo|PO).+ sh.+ text ex|XM)/) F=F" ("T", "C")";else F=F" ("C")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n   ...and %s more line(s)\n",l-L);} ' ' s/^ ?n...://p;s/^ ?p...:/-'$'\t''/p;' 's/0/Off/p' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' / / { print "'"${p[28]}"'";exit;};1;' '/ en/!s/\.//p' ' NR!=13{next};{sub(/[+-M]$/,"",$NF)};'"`S0 39 40`" ' $10~/$L/&&$9!~"localhost" { sub(/.+:/,"",$9);print $1": "$9|"sort|uniq";} ' '/^ +r/s/.+"(.+)".+/\1/p' 's/(.+\.wdgt)\/(Contents\/)?Info\.plist$/\1/p' 's/^.+\/(.+)\.wdgt$/\1/p' ' /l: /{ /DVD/d;s/.+: //;b0'$'\n'' };/s: /{ /V/d;s/^ */- /;H;};$b0'$'\n'' d;:0'$'\n'' x;/APPLE [^:]+$/d;p;' ' /^find: /d;p;' "`S0 44 45`" ' BEGIN{FS="= "} /Path/{print $2} ' ' /^ *$/d;s/^ */   /;' ' s/^.+ |\(.+$$//g;p ' '/\.(appex|pluginkit)\/Contents\/Info\.plist$/p' ' /2/{print "WARN"};/4/{print "CRITICAL"};' ' /EVHF|MACR|^s/d;s/^.+: //p;' ' $3~/\./ { i++;n=n"\n"$1"\t"$3;} END { if(i>1) print n;} ' );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps crontab iotop top pkgutil 'PlistBuddy 2>&1 -c "Print' whoami cksum kextstat launchctl smcDiagnose sysctl\ -n defaults\ read stat lsbom mdfind ' for i in ${p[24]};do ${c1[18]} ${c2[27]} $i;done;' pluginkit scutil dtrace profiles sed\ -En awk /S*/*/P*/*/*/C*/*/airport networksetup mdutil lsof test osascript\ -e netstat );c2=(com.apple.loginwindow\ LoginHook '" /L*/P*/loginw*' "'tell app \"System Events\" to get properties of login items'|tr , \\\n" 'L*/Ca*/com.ap*.Saf*/E*/* -d 1 -name In*t -exec '"${c1[14]}"' :CFBundleDisplayName" {} \;|sort|uniq' '~ $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' :${p[35]}\" :Label\" '{/,}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 \$(RefProc): \$Message' -k Sender Req 'fsev|kern|launchd' -k RefProc Rne 'Aq|WebK' -k Message Rne 'Goog|ksadm|probe|Roame|SMC:|smcD|sserti|suhel| VALI|ver-r|xpma' -k Message Req 'abn|bad |Beac|caug|corru|dead[^bl]|FAIL|fail|GPU |hfs: Ru|inval|jnl:|last value [1-9]|NVDA$|pagin|pci pa|proc: t|Roamed|rror|SL|TCON|Throttli|tim(ed? ?|ing )o|WARN' " '-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,J,OSXU,Rem,up}*.bom' '{/,}L*/Lo*/Diag* -type f -regex .\*[cght] ! -name .?\* ! -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]} '/S*/*/Ca*/*xpc* >&- ||echo No' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,Ex}* {/,}L*/{A*d,Ca*/*/Ex,Co{mpon,reM},Ex,In{p,ter},iTu*/*P,Keyb,Mail/B,Pr*P,Qu*T,Scripti,Sec,Servi,Spo,Widg}* -path \\*s/Resources -prune -o -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto,{cron,fs}tab,hosts,{[lp],sy}*.conf,mach_i*/*,pam.d/*,ssh{,d}_config,*.local} {,/usr/local}/etc/periodic/*/* /L*/P*{,/*}/com.a*.{Bo,sec*.ap}*t {/S*/,/,}L*/Lau*/*t .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers\ "${p[N5]}" -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' '+c0 -i4TCP:0-1023' com.apple.dashboard\ layer-gadgets '-d /L*/Mana*/$USER&&echo On' '-app Safari WebKitDNSPrefetchingEnabled' "+c0 -l|awk '{print(\$1,\$3)}'|sort|uniq -c|sort -n|tail -1|awk '{print(\$2,\$3,\$1)}'" -m 'L*/{Con*/*/Data/L*/,}Pref* -type f -size 0c -name *.plist.???????|wc -l' kern.memorystatus_vm_pressure_level '3>&1 >&- 2>&3' " -F '\$Time \$Message' -k Sender kernel -k Message CSeq 'n Cause: -' " -i );N1=${#c2[@]};for j in {0..9};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 XPC\ cache 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 Prefetching SATA Descriptors App\ extensions Lockfiles Memory\ pressure SMC Shutdowns Nets );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" ]];};A'$((7+i))'() { v=` eval sudo "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "$v" ]];};';done;A9(){ 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" ]]&&sed -E "$s"<<<"$v";};C1() { [[ "$v" ]]&&printf "${f[$1]}" "${l[$2]}" "$v"|sed -E "$s";};C2() { v=`echo $v`;[[ "$v" != 0 ]]&&C1 0 $1;};C3() { v=`sed -E "${s[63]}"<<<"$v"`&&C1 1 $1;};for i in 1 2 7 8;do for j in 0 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;{ A0;D20 0 $((N1+1)) 2;D10 0 $N1 1;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;D13 0 $((N1+9)) 59 50;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;B1&&D73 19 53 67 55;D22 2 12 9 11;D12 3 13 10 12;D23 4 19 44 13;D23 5 54 12 56;D23 5 14 12 14;D22 6 36 13 15;D22 20 52 66 54;D22 7 37 14 16;D23 8 15 38 17;D22 9 16 16 18;B1&&{ D82 35 49 61 51;D82 11 17 17 20;for i in 0 1;do D82 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&&{ A8 18 26 23;B7 7;C3 23;};A2 18 26 23;B7 7;C3 24;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;B3 4 0 65;A3 14 6 32 0;B4 0 16 11;A1 26 50 64;B7 16;C3 52;D13 24 24 32 31;D13 25 37 32 33;A2 23 18 28;B2 16;A2 16 25 33;B7 16;B3 0 0 34;B2 21;A6 47 21&&C0;B1&&{ D73 21 0 32 19;D73 10 42 32 40;D82 29 35 46 39;};D23 14 1 62 42;D12 34 43 53 44;D12 22 20 32 25;D22 0 $((N1+8)) 51 32;D13 4 8 41 6;D12 21 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 38 55 68 57;D23 33 34 42 37;B1&&D83 35 45 55 46;D23 32 31 43 38;D12 36 47 32 48;D13 10 42 32 41;D13 37 2 48 43;D13 4 5 32 1;D13 4 3 60 5;D12 21 48 49 49;B3 4 22 57;A1 21 46 56;B7 22;B3 0 0 58;C3 47;D22 4 4 50 0;D12 4 51 32 53;D23 22 9 37 7;A9;C2 2;} 2>/dev/null|pbcopy;exit 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
8. 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 and start typing the name.
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.
9. If you see an error message in the Terminal window such as "Syntax error" or "Event not found," enter
exec bash
and press return. Then paste the script again.
10. 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.
11. 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 what happened. No harm will be done.
12. 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 the words "Start time." 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.
13. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "You are not authorized to post." That's a bug in the forum software. Please post the test results on Pastebin, then post a link here to the page you created.
14. 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.

Mavericks and MacMini - after sleep mode windows resized and glued to left upper corner

Hi!
I have MacMini and HDMI monitor. When I go to bed, I use sleep mode and off monitor using power button (I don't like standby light). When I woke up, I press on my touchpad to wake up my MacMini, after that I stand up and turning on monitor. All works fine, until I installed Mavericks. Now, after turning on, all windows changed size to very small and glued to left upper corner. I can't resize or move window. Only shutdown app can help. But, I can't shutdown Finder, I need reboot MacMini. It's very annoying.
As I understand, this problem appear, when I wake up MacMini before turning monitor on. When I turned on monitor and after that woke up MacMini, windows don't change his sizes.
What can I do to solve this problem?

This issue is driving me insane. I lock my computer a couple of times a day as I go to meeting and what not. Everytime either Outlook or VMWare or Chrome will be screwed up when I awake it from sleep. I have to kill the app and start it back up again or I can't get it out of its weird "docked" mode. Basically the application window will be nearly off the screen. I can move it on the screen but the caption will be off screen still and I will not be able to size the window at all. It really messes VMWare's mind up when this happens.
I wanted Mavericks as it was supposed to fix multiple monitor issues but it has made it worse. Very sorry I upgraded. I hope they fix it in the next bug patch. I just cuss at the stupid thing when I wake it.
MacBook Pro 16g of memory with external 24" monitor via HDMI -> DVI connector. Laptop is primary monitor on the left, external monitor is on the right. Mavericks is in the doghouse just below both of them.

After 10.8.2 and efi upgrade apple thunderbolt monitor is black

After the upgrade when I boot with the display connected (thunderbolt) both the macbook and external apple display remain black with the cursor in outline. When the display is disconnected the macbook screen returns. What about it apple this is a premium computer and screen and its all designed by you guys?

My display is working great - and I've been through the 10.82 update, the 10.8.2 update, etc., but no firmware update (your's was likely Retina-specific).
Your ATB should just be pug-and-play. Since you're still under warranty, I would contact AppleCare and possibly setup and appointment with the Genius Bar folks at your local Apple Store: something's not right - whether it's you display or your notebook.
Clinton

No internal speakers after EFI- and thunderbolt updates

i got no sound in my internal speakers after the updates.
rebooted and repaired permissions, problem persists

Is there a red light shining in the headphone port ?
If so, some solutions to be found in this threadhttps://discussions.apple.com/message/10384803#10384803
Stefan

IMac (Late 2006) Stalls with EFI 1.2 and Leopard

A few days ago, I installed both the iMac 1.2 EFI Firmware update and Leopard on my late 2006 20" iMac. Since then, I've seen random momentary stalls throughout the system.
It sometimes happens while scrolling a web page, displaying a sheet, opening a stack, browsing CoverFlow, and so on. I don't know how to intentionally recreate it, it just seems to happen. It often (always?) seems to coincide with some disk activity.
I don't remember this behavior on the same hardware in the past, so either it's something with the firmware update or Leopard. Has anyone seen anything else like this?
Thanks in advance.

Some people reported various bugs after installing the firmware update. Shutting it off and turning it back was all that was needed to fix the bugs.

Macmini can't wake up and I Get a Black Screen

Hi all, this is my first post in this community. Please do help me.
I purchased a Mac mini (2012 late model, OS was originally Mavericks 10.9.1 when the machine arrives at my home. ) in January 2014. I used a “miniDP to DP adapter” to connect the Macmini with my Asus PB278Q Display (the original DP cable that comes with PB278Q is connected to the adapter. The adapter is plugged into the Thunderbolt socket on the back of Macmini). It supports the maximum resolution on my display (2560x1440), but if I use a HDMI cable instead, it only supports up to 1920x1080P. Everything was fine until last week when I attempted to wake up macmini after it had slept for 8 hours or so (I used it in the morning, put it to sleep mode before going to work, and then came back at 5:40 pm hoping to use it again). The Macmini light was on, and I could hear noise. But the screen is black with its power light yellow. When I kept hitting the keyboard, I could hear a “Ding” from Macmini each time, and the PB278Q power light sometimes turned blue, but soon a prompt "No Signal” appeared on the screen, followed by a totally black screen with power led turning back to yellow.
I tried to unplug the adapter from the thunderbolt port, plugging it back in, connecting a HDMI cable with macmini (PB278Q supports both DP and HDMI), nothing helped. Pressing and holding the power button for 6 secs, and pressing it again to let Macmini reboot surely helps each time. I have not done a thorough experiment to tell within how many hours the wakeup has no issues. But I am sure that there is no issues at least within one hour. I.e. if I walk away from my macmini, and it sleeps (set to 10 mins sleep), come backs after not a long while, and hit the keyboard or the trackpad. The screen comes back to life immediately, and I see the “login” dialog.
I called Mac techsupport for three times and talked with their higher level engineers for a long time. They suggested me to do “Command+Option+R+P”. Now I know that is “Resetting NVRAM / PRAM”. But the problem stays.
Does Re-installing help? I just reinstalled last night and won’t be able to judge until tomorrow. At this point, I have the following suspicions, which I hope someone can help:
1. The miniDP to DP adapter might have caused this problem. Replacing one adapter or using a good miniDP-DP cable might be the solution. But I can’t find such a cable or adapter on Apple’s online store. Note it should be Mini-DP to DP or thunderbolt to DP cable. Please suggest where I can get one
2. I doubt that my suspicion 1 is valid, as in my question – why is everything ok when the macmini does not sleep or sleeps a short time? When I work on the macmini, no problem happens. The display works fine, and the resolution is the maximum that the display is capable of. Therefore, why should my suspicion one hold any water?
3. Since the display power led turns blue when macmini detects keyboard hits, does that prove that macmini is innocent, as it successfully sends out a signal to my display, but somehow my display persistently says “no signal”. In this light, can we shrink the problem identification scope to the display, the DP cable and the adapter?
Thank you very much for any help or hint/tips I can get from any of you.
God bless.
Bluebird,
Chengdu, China

Hello Bluebird,
See if it's related to this...
It also seems to be related to later OSX versions, like 10.8.x & 10.9.x
The 2012 macs (and later apparently) (also later OSX versions on earlier Macs can do it also), not waking normally from sleep after hours being in sleep. (noted here ...
http://www.xlr8yourmac.com/archives/feb13/022813.html#2012macswontwake
"Why 2012 iMac/2012 Mac Mini won't Wake After Hours of Sleep (Hibernates/Powers Off)")
The sleepimage file still reappears even if never slept. Delete it (hibernate off, etc) - within minutes its back.
A note on that here - http://www.xlr8yourmac.com/feedback/Chameleon_SSD_Optimizer.html
About iMac sleep...
http://forums.macrumors.com/showthread.php?t=1529750
Try this: "sudo pmset autopoweroff 0" and "sudo pmset standby 0"
http://xlr8yourmac.com/archives/sep13/091313.html#10.8.5SleepEjectTip
One user reported that the opposite worked...
Try this: "sudo pmset autopoweroff 1" and "sudo pmset standby 1"

Macbook pro mid 2012 no retina performance drop after efi

Hi, mi macbook pro mid 2012 no retina after efi update the performance are too slow, thats is the same problem with retina, please fix it, in osx mountain lyon the aplications that used every daywith video is poor, in bootcamp with games is the same problem, the cpu clock drops from3.3 ghz to 1.2 ghz or more. Waiting for a mew efi update bescause my mac is the same that a macbook air

No Apple hasn't officially stated anything about this issue. After I updated to EFI Update 2.0 I noticed the issues and started doing my research and found people in the Macrumors forums having the same problems and eventually I was reading that users that didn't update yet weren't seeing the update in their updates meaning Apple pulled the update from the servers. Other users reported after calling Applecare that they were aware of the issue.

Mac Book fails to boot properly after EFI Firmware 27 update

hi
I have a strange boot issue having (tried) to install EFI 2.7 update.
When I restart the laptop, it 'chimes', displays a grey screen ... then chimes, displays a grey screen , ... for ever
I hit the bower (off) button for 5 secs or thereabouts, and restart ... same thing
I do this 4 times and finally it reboots.
But the EFI update still appears as needing to be installed (software update tells me it is not installed). Update history shows however that it IS installed.
I can go through this process any number of times ... I now have Software Update history showing quite a few installs opf the EFI 2.7 update.
If I just do a restart WITHOUT installing, I also go through the same fail to restart / fail to start / ... / eventually restart sequence.
So it seems now that the laptop will only start after 4 failed restarts and finally it starts ...
After starting it all appears to be perfectly fine.
Nothing strange in the console logs that I can see. The failed reboots don't seem to register in the console logs - I suspect that the failure to restart is pretty early on in the boot sequence, well before it tries to load any semblance of the OSX kernel. It is almost as if it is trying to boot from someplace other than the disk ... until eventually it gives up and tries the disk. (I have tried booting with and without network cable - no difference) I don't know enough about mac bootup sequences to know if there is some config/setting that is screwed up causing this odd behaviour. I sirt of feel it must be setup/software related, but could be wrong.
Odd.
Any ideas?
- chris

I have a MC721LL/A early 2011 15.4" MacBook Pro i7. After I installed this firmware update my Mail would not load saying the version I was trying to start was not compatible with the OSX version (not sure whether this was an OSX update issue which I think I did at the same time). But the biggest problem I have is that I cannot boot my machine. It boots to the Apple logo and then emits 3 beeps repeatedly. I am on vacation in Osaka, Japan and the Apple Store here told me after running some analytics that the logic board is not seeing the RAM. After reseating the RAM multiple times (both original and replacement DIMMS), it still won't boot. The Genius Bar guy said very nicely that it is out of warranty and needs a new logic board, costing over $500 and taking a week at the factory. He recommended spending the money on a new MacBook instead. Since my machine is 15 months old, I am not very happy about this. The machine was absolutely fine before the firmware upgrade. I will wait till I get back to the US and get a second opinion from my local Apple Store. I can't accept that a 15 month old MacBook Pro very lightly used can develop such a catastrophic failure.

DC Offset problem with Peak 4.14 on MacMini after new hard drive upgrade

Tiger 10.4.11
Bias Peak 4.14 (24-bit 44.1 AIFF files)
USBPre 1.5
The reason for this new topic is a problem that developed with Bias Peak 4.14 on my MacMini. Suddenly, when I apply the "Remove DC Offset" DSP process to a recording, the Bias Peak meters may stop displaying correctly.
About 50% of the time, only one meter will respond to the sound, or neither will (the meters work fine on the raw file before I apply the DSP function). The rest of the time, they work normally after DC Offset. I'm still waiting to hear from Bias about this via their forum, but no-one has responded yet. I don't know if this is just a GUI bug or an indication of a recording problem. The really spooky thing is that the problem only shows up part of the time.
This is happening on a new installation of OS X on a new drive that I installed. See a note at the bottom of this post for a hardware issue that may or may not play a role.
I've been recording vinyl successfully for a long time now on my MacMini (24-bit 44.1 AIFF), using a USBPre external A/D converter and Bias Peak (currently v4.14). But recently Peak froze as it was saving a file. I had to do a hard shut down which led to a corrupted system. I'd been meaning to upgrade to a larger drive anyway, so I put a 120 gig drive in.
After first installing/updating OS X on the new drive, and installing/upgrading Bias Peak, I had no problems. But then the control panel for the USBPre froze as I was getting ready to shut down. This worried me, so I ran diagnostics with TechTool and installed eDrive. The meter problem began showing up after this change. I wiped out the partition and reinstalled from scratch again, hoping that this would get things back to normal. But I still have the meter problem after applying DC Offset. Note, I created two partitions on the drive, and put Tiger on the first partition.
The makers of the USBPRe (Sound Devices) say there is nothing about the USBPre or drivers that should be causing this.
So I'm stuck, and faced with the following ideas for what might be wrong:
1. Peak has a bug that I've somehow triggered. This may or may not be affecting the recording.
2. Something about my recording hardware/driver has changed that is "corrupting" my recordings sometimes, and this is causing Peak to have trouble metering the sound.
3. I screwed up my computer hardware and this is screwing up the recordings part of the time. See my upgrade note* about the hardware.
4. The new drive seems to be a little slower to display folder contents. I wonder if this apparent latency could be causing the DC Offset problem in the original recorded file.
* Upgrade note: When I tried to put the cover of the Mini back on after upgrading my drive and testing it out, I discovered that I hadn't screwed the drive/fan/DVD setup in correctly. The screws had fallen out and disappeared (my tiny screw driver made it very hard to tighten the screws I guess. I thought I’d done it correctly).
I turned the Mini upside down a couple of times before I discovered the screws missing.. My first attempts to put the cover on with the Mini sitting upright were not successful, so I turned it upside down to take the cover back off. The screws probably fell out then. When I tried putting the cover top down on the table and lowering the Mini into the cover I discovered that the drive/fan/DVD assembly was loose!
The drive is now secured completely except for the screws, and it is working. The slowness I mentioned above is something I noticed before the screws fell out, but obviously the assembly was not secured 100% even before I lost the screws.
I apologize for this convoluted post and hope it is clear enough. Please help if you can, I'm under pressure to finish my recording project.
Vinyl_Man

Hello, DaddyPaycheck,
The USBPre is powered by the USB bus, and it is plugged directly into the MacMini.
The screws remain in hiding. I'm amazed that I didn't find them on the motherboard or something like that. If they don't turn up fairly soon, I'll try to get replacements from an Apple service center. And I'll make sure I have a better small screwdriver.
I just did a test with Audacity for OS X and Cool Edit for Windows. I opened files that give me the meter problem in Peak and removed the DC Offset. When I opened the files I had modified in Audacity and Cool Edit, Peak metered the sound correctly. Somehow Peak is sensitive to something in the file that does not bother the other apps, and when the other apps have adjusted the DC Offset, Peak is happy. Peculiar.
I'm thinking about recording with Audacity now instead of Peak. I'm still concerned that something is wrong, though, since I don't understand the problem.
-Vinyl_Man

Second display via Thunderbolt "flashes" after EFI 1.7

I have a second display (Samsung SyncMaster 245BW) connected to my 27" iMac via Thunderbolt and a miniDisplay -> DVI connector. I just recently got the 1.7 EFI software update and noticed that the second display will flash every 2 - 3 minutes. Anyone else seeing this? Should I revert back to the previous EFI?

KVM switches are either compatible with Macs or they are problematic at best.
I had a KVM here that when I switched to another screen/keyboard, the screen would stay black, until I disconnected and reconnected the Mac video cable. It was a PITA. Threw it in the trash eventually.
I now have a mini and a nettop Linux box, both connected to the same monitor with DVI and VGA respectively. The screens are switched with a button on the monitor. If I need a keyboard on the Linux box, I attach one, otherwise I ssh into it and use the Apple keyboard. There is a separate wireless USB mouse on the Linux box, as needed.

AE only recognized by Macmini after hard reset, not by my Macbook

I did a hard reset on my AE after some network issues (couldn't access the internet) and after that only my Macmini could see the AE and do the admin settings. My Macbook still couldn't see my network so I changed the channel to 10 and suddenly my Macbook was able to recognize my network. Why is that? I should be able to do the install from my Mybook too, if I didn't had my Mini what would be my solution then. Is it some firmware or anything that the Macbook missing? Please help!
Thx
MacBook Core2Duo/ Mac mini intel core duo Mac OS X (10.4.8)
MacBook Core2Duo/ Mac mini intel core duo Mac OS X (10.4.8)

Machines manufactured in Europe can see channels 1-13.
Machines manufactured in America can see channels 1-11.
Airport when initially set up defaults at channel 13.
If your airport base station is broadcasting on channel 13 and your macbook has been made or is using hardware made in america it will be unable to recognize channel 13.
Changing the default channel to something lower than 11 usually works.
If you didnt have your mac mini then you would run a direct ethernet cable between you express and your mac, and airport admin utility will be able to see the base station.
Hope this helps.

Shortcut to connect and disconnect 'Airplay Display' on MacMini?

Is there a shortcut to connect and disconnect 'Airplay Display' on my MacMini so I dont have to use the drop menu?
Running Mavericks 10.9.2

Hi, I have a similar problem and reported it to the Apple hotline. They currently have no solution. The same in several online discussions. Currently you only can disconnect or switch off you modem to cut the connection to the internet. When I do that I must use the AirPort utility to reload the AirPort Extreme base station after the connection has been re-established.
I'm not sure if the people in the States can imagine that there are other regions in the worlds were individuals live which don't have a flatrate ...

Macbook 2008 4,1 serious problems after 10.6.8 and 1.4 firmware update

I'm having a problem with my 2008 2.4Ghz Macbook. After doing a fresh install of 10.6.0 with a Retail DVD, the MB was working perfectly, absolutely no problems at all. I then ran Software Update and installed all the recommended updates to 10.6.8, and I only noticed in passing that there was a Firmware update to do too, as reported by Software Update. I ran that as well and, IIRC, it was applied after fully updating to 10.6.8 and after rebooting twice. The MB rebooted, ran the Firmware update (which seemed to complete fine, as the progress bar completed normally against the grey screen), then rebooted. Again, IIRC, after running the Firmware update, and I'm now at 10.6.8, I started a Repair Permissions and left the MB for a while. It was the next day, maybe 15 hours later, when I went back to the MB and it was in Sleep. I pressed a key to wake it and this is when the weirdness started.
The screen was "fuzzy", sort of out of focus, though I could see the desktop, and what I could see was: the Disk Utility window open on Repair Permissions (which had completed normally) and several Vertical Segmented Bars running across the bottom part of the screen, at about the height where the Firmware Update progress bar was. These bars were filling in from left to right. IIRC, it may have looked a little like when you wake from Deep Sleep (or Hibernate, or whatever it was called). Like when you Wake from Sleep after the battery has run out and then you plug the AC adapter in.
Anyway, before the Vertical Segmented Bars progress was completed, the screen went black. Pressing keys didn't bring the desktop back.
I did a forced shutdown, reset the SMC, then rebooted. No startup chime. The Superdrive, hard drive and fans spun up, but the screen remained black. After a few reboots, I got a desktop back, and tried to reinstall from both an external HD (with Restored disk image) and the Retail Snow Leo DVD. Both times, the MB booted to the startup screen: with the external HD, I held down Option and chose the Snow Leo install; with the DVD, the MB started normally while I held down the C key. The boot started from the HD and the DVD, but after about 60 seconds, with Apple logo and the spinning "cog wheel", the screen went black. And seemed to shut down. With the external FW hard drive, the drive made a loud click, its LED went off, then it came back on after a few seconds, as if it had lost all power to it, then the LED lit up when power returned to it from the shut down MB. Anyway, the installs failed.
I then attached the 2.4 MB to another MB (2.1) in Target Disk Mode and it booted fine into TDM. It showed up on the 2.1's desktop, I ran Check Disk and it checked out okay. I then looked under Startup Disk and the 2.4's disk was listed there, with 10.6.8.
I then booted the 2.1 from the 2.4's disk and it booted fine. I ran check Permissions, and a huge list of permissions to repair came out. At this point, I've left things as they are. The 2.1 is booted from the 2.4, the latter used as external boot HD.
I then replaced hard drive and RAM. Tried to boot from DVD and install, got to Apple logo and spinning cog wheel, but after about 2 minutes the screen went black.
I then connected an external monitor and rebooted from the DVD. The external display received a video signal and I got to the Snow Leopard install screen. All this time the Macbook display has remained BLACK.
I went to Disk Utility and reformatted the new drive, then started the installation, which completed fine. The Macbook runs normally connected to the external display.
Any thoughts?
Why would the Macbook display work fine at boot (Apple logo, etc.), but then cut out after about 2-3 minutes?
Why would the Macbook screen remain black while I got a video signal on an external monitor?
Does this sound heat-related in some way? I should note that while booting from the DVD and now installing Snow Leopard, the fans are going pretty fast.
I just want to point out that this was an absolutely pristine, impeccable Macbook until these recent problems. It is in fantastic condition, none of the usual chips out of the top case and trackpad area. After the latest fresh install of 10.6.0 it was perfect upon reboot. Fast, perfect Airport and Bluetooth, FW and USB worked perfectly with a FW drive and USB mouse I hooked up. The update to 10.6.8 via Software Update seemed to complete fine.
Then all the problems started AFTER THE FIRMWARE UPDATE.
I don't know how much stock can be put in the firmware update being the cause of the problems, but the sequence here would bear that out. These are also somewhat unusual problems, at least in my experience.
One of the odd things was when I first went to wake the Macbook after the firmware update: the "fuzzy", out-of-focus screen and the segmented progress bars. And it was just before the segmented bars completed progress from left to right that the display cut out and went black. And from that time on, I've had the aforementioned problems.
Any ideas or links to similar problems would be greatly appreciated, e.g. possibly firmware related, or where the Macbook screen works but goes black after a couple minutes. And now that I've been able to connect to an external monitor, it would seem that the video signal is okay too.
Thanks.

Just to update.
After leaving the Macbook unplugged and without battery for a few days. I reset the SMC and, with no battery installed, I've just now rebooted and:
1) the first time, it booted, but no chime, and when the display turned on, once again I got the "out of focus" desktop AND the segmented vertical bars on the desktop (and the bars were filling in from right to left); the display went black after about 10-15 seconds;
2) I shut down and swapped some different RAM, then reset the SMC again and booted without battery. This time I got the boot chime and the Macbook booted to the Apple logo screen and spinning cogwheel. After about 2 minutes, the cogwheel stopped spinning, as if to boot to the desktop, but then the display went black. The front light started to pulse after about 10 seconds, and the Macbook appeared to be in Sleep.
3) I woke the Macbook from sleep by hitting a few keys and this time it went to the desktop. This is the first time it's gone to the desktop since the problem started.
I had enough time to see that everything appeared normally on the desktop, such as the time and date, Airport was connected, etc. And then the display went black again, after about 10 seconds.
At this point, I can now always get to the desktop, but the display goes black after about 10 seconds. I have just enough time to press a few keys and the Macbook does respond.
4) I shut down and reinserted the battery. Here's where new problems show up.
With the battery inserted, and the Macbook in sleep, if I hit a key, the DVD spins up as the Macbook is waking, BUT now the front sleep indicator light FLASHES (blinks) 5 TIMES. No beeps.
The Macbook still gets to the desktop, like before, and the screen goes black after 10 seconds.
I found some info on the Apple site re. 5 flashes (Article 21502):
If you don’t hear beeps, but the sleep indicator light flashes five times when you start it up or wake it from sleep, its battery may need service. Take the battery to an Apple Authorized Service Provider, such as an Apple Retail Store.
For more information, see the Apple Support article below.
You can continue using your computer before you service the battery. Use a different battery, or connect the computer’s power adapter and plug it into a power source.
Note:If you use your computer without a battery or with a faulty battery, you could lose all unsaved changes if it’s unplugged while it’s on.
BUT, the battery is not defective, as it works okay in another Macbook.
I should also point out that the problem with the 5 indicator light flashes or with the battery did not exist before the 10.6.8 and the Firmware 1.4 updates.
Any ideas?

Adobe Creative Cloud because I do not get After Effects among others but I try to install software from the page but I give After Effects download shareware and says downloading but nothing comes give him retrying but nothing even leave the application of

if you can help me please alguin
Adobe Creative Cloud because I do not get After Effects among others but I try to install software from the page but I give After Effects download shareware and says downloading but nothing comes give him retrying but nothing even leave the application of Adobe Creative but nothing help

Without proper system info and otehr technical details nobody can tell you anything.
Mylenium

Macmini after EFI 1.7 and kvm, no display

Similar Messages

Maybe you are looking for