To Grate Cheese

IMG_5018This is “Masspot”, a Mac Pro 1,1, upgraded to 12GB of RAM, and replaced disks. It is currently running OS X 10.7.5.

My best guess is that it is over 10 years – probably purchased in 2008 as my main work machine. It survived being shipped via UPS from Japan to Germany. Upon arrival in Hamburg i saw it thrown out of the back of a delivery truck, and very nearly roll into a drainage ditch… it didn’t seem to care. Still runs just fine.

Not sure if it can still grate cheese.

The majority of my image library (Lightroom catalogs) still lives on this machine, backed up to multiple locations, and in the process of transitioning to a RAID6 array Synology NAS.

While i’ve no idea how much it cost at the time, it has undoubtedly paid for itself hundreds (or thousands?!) of times over. My plan is to replace it with… well, that’s the question.

The original Cinema display is now tinged a distinct pink around the edges, and not usable for any image processing. That’s not a huge problem for minor tasks (vnc is good enough with everything cabled) but long-term it’s not viable. The only other monitor, an LG Ultrafine 5K, is now dedicated to my work environment. Not that there is any feasible way to connect it to the current graphics card of the Mac Pro!

Not being a video person all new Apple machines feel like overkill to me. Especially if it’s just image processing. But given the likely lifespan of any new machine that i’m going to buy, maybe it won’t feel that way by the end of it’s life?

In short, i’m thinking about buying a low-end / base model Mac Pro cheese grater. Or an iMac Pro. The latter scares me a little as it’s obviously a non-upgradable route, where the whole thing becomes useless if a component fails. And, i dont really want any more screens in my office.

Ideally, there is a Thunderbolt 3 KVM setup to let me switch between two machine and a single screen. That has to exist… right?

Oh, with a new graphics card and hacked EFi the original Mac Pro can be upgraded to a far more recent macOS release, which would make me less scared about having it on my network!

Sleep Problem

Not me, but my venerable Mac Pro 1,1.

At some point the damn thing stopped sleeping. I’d spend time stopping apps, checking after a clean boot, looking through the output of netstat -an, etc. Nothing. Gave up and just did a lot more shutting down the machine completely. It bugged me but in a way it was good to turn it all off (less checking mail in the middle of the night…)

Today it bugged me again. On the way out to walk around the park i’d tried to sleep the beast, as usual it refused. In a fit of pique i yanked the network connection. Paranoia inspired testing? And, the machine went straight to sleep. Uh huh.

More fiddling around with Privoxy (always a candidate for being the problem in my mind), puzzling through netstat output, closing down apps., etc. More nothing. Bah.

Then, pmset:

$ pmset -g assertions
6/12/13 11:27:34 AM GMT+ 
Assertion status system-wide:
 PreventUserIdleDisplaySleep 0
 CPUBoundAssertion 0
 DisableInflow 0
 ChargeInhibit 0
 PreventSystemSleep 1
 PreventUserIdleSystemSleep 0
 ExternalMedia 0
 DisableLowPowerBatteryWarnings 0
 EnableIdleSleep 1
 NoRealPowerSources_debug 0
 UserIsActive 0
 ApplePushServiceTask 0
Listed by owning process:
 pid 94: [0x0000005e012c0010] PreventSystemSleep named: ""

All this time i’ve had internet sharing turned on… and had no idea that it stopped machines sleeping. Seeing as i don’t actually share internet from this machine it’s a little puzzling. No doubt it was turned on for a reason in the past, all that is lost in the mists of time.

Anyway, pmset -g assertions is the way to debug sleep issues! May Gub (or the ghost of Steve) help you if you ever need to read the manpage. At least i can now sleep my machine again!