Always Stay On Brand.™
In this entry from a few years ago, I wrote about putting an SSD in an iBook from 2001. I got another iBook because I like them and they play Starcraft and if I didn’t who would, and I thought that it’d be fun to revisit that and see what a new IDE SSD did against that one from 2011.
Unfortunately, that was a short-lived plan. KingSpec (and others) do still make IDE SSDs, but almost all of them use the SM2236 controller, instead of the older SM2231, which seems to demand a couple more channels than the iBook knows what to do with. It can’t start up from a preformatted SM2236 drive, and it can’t install from a CD onto the drive either. Since clamshell iBooks are one of the trickier computers to do a drive swap on, I found this realization very amusing (although, truth be told, it’s not a terrible job at about 40-50 minutes; it’s just a fuss).
So that was out. But then I figured, in that last article I made reference to my CompactFlash-bedrivulated iBook — what if I revisited that? I made that thing in 2008 or so, surely CF has gotten faster. I also sold it in 2011 without having benchmarked it, lending an air of pointlessness to this whole thing, which was perfect.
So, I got a neat Syba IDE-CF bridge in 2.5″ drive format. Pretty nice; it has two CF slots. I used a Lexar 16 GB 800x card, since I had a spare one; presumably a 64 GB 1066x card would be faster. I also added a 512 MB stick of RAM and a new “CWK” battery to the iBook — which must be made using decade-old NewerTech tooling or something, but it works shockingly well.
Installation was the usual pain in the ass.
I also lost my Air’s disc burner and had to resort to, err, backup measures. I didn’t realize this iMac only had 10.1 on it, but it burned the Panther CDs fine, so that’s alright.
Anyway, long story short, it works great. On the left, here is the SM2231 KingSpec SSD in the other iBook. On the right, that iBook’s original Travelstar HDD.
Now, here’s the iBook with 800x 16 GB CompactFlash:
A nice improvement! Slower small random writes than the KingSpec, but everything else is a decent little bit faster. Again, I think you could address that by going with a faster CF card if you were so inclined. The CF and CF-IDE bridge is also slightly cheaper than the 16 GB KingSpec was (in 2011) and the 16 GB KingSpec (with SM2236 controller) is now. The computer is fast for a 2000 laptop, silent, and gets pretty good battery life even by modern standards. The only downside is that the first-generation AirPort cannot use WPA2.
Obviously it’s sort of pointless. When I was little, the three computers I really wanted in 2000 were the Indigo/Key Lime iBook and the Cube, as well as the “Lamp” G4 iMac when it first came out in 2001. I couldn’t afford any of them at the time (although I eventually did have a 1.25 GHz 20″ iMac G4, bought slightly used in 2004, which lasted me until the Intel switch), and made do with a PM7100/80 upgraded to G3. But I guess buying now-useless things you couldn’t afford when you were small is part of being a grown-up or whatever. I have the iMac and a couple iBooks, and I had a Cube upgraded to a 1.33 G4 in 2007-2008, but sold it. That was real dumb since Cubes cost insane monies now. Ah, well. The point is, I don’t really use any of them and it’s pointless. But if you like pointless old nonsense, I guess I recommend shoving CF cards all up ins it. Sometimes you just gots to have a Starcraft 1 LAN party.
I returned the EVGA because it just wasn’t worth the fuss, but then Nvidia started releasing their own OS X drivers, so I thought I’d give it another shot. I got another 670, an Asus DirectCU II, and tried it again.
Update from 2017: This post is five years old now, but lots of people still find it through Google. So I thought I’d update it just to say that I sold the Mac Pro with an Nvidia card to my dad, and it has been working fine through the various OS upgrades. Googling around suggests that the 10×0 cards work fine in Mac Pros too. I replaced my Pro with a MacBook Air and a custom gaming PC, but I think the 4,1/5,1 Pro remains a really good computer.
I thought I’d try dropping a GeForce GTX 670 into my Mac Pro, since apparently 10.8 can drive it (you just won’t get the EFI boot screens). I bought the 2GB EVGA 670 FTW, mostly since that has two six-pin power plugs. The top OEM card for the Mac Pro is the Radeon 5870, which is a good card but also pretty old, so — on paper — the 670 is a nice upgrade. The 670 is actually a little cheaper, too. The drivers in Mac OS are still pretty immature, so my goal was to get equal-or-slightly-better performance for now, and way better performance in Windows.
Installing it is pretty straight-forward, if you’ve ever done computer stuff at all. Here’s my Mac Pro as it sat, with the 5870.
The 670 is a little smaller.
The 670 dropped right into the 5870’s spot, and hooked up to its power plugs. These are standard parts, of course, so if it didn’t that would mean I’m really dumb. You can see that I also put in a little PCI fan (powered from the spare optical drive SATA port, and a SATA-to-Molex adapter). This pushed a lot of air, but it was really noisy, and it didn’t seem to make much difference; the only thing making much heat in the PCI bay is the GPU (the rear hard drives being idle most of the time), and both the 5870 and 670 keep their heat fairly contained in those plastic shrouds, and push it out the back. Maybe the fan did a little something, but it wasn’t worth the noise. So, the little PCI fan is gone now.
So I did that, and it booted. That was nice. You don’t get the grey boot screen (the video drivers loads when the OS does, so it appears to boot straight to the desktop). With the fast SSD booting, it was just, like, “push button, wait 20 seconds, be at desktop”. The obvious problem is that if you find yourself looking at the startup manager a lot, this is a bad solution — you no longer get that. In that case, it’s worth keeping things OEM or finding a flashed Nvidia card that gives you the boot screen.
Anyhow, it worked just fine. I went to run benchmarks, and LuxMark couldn’t load. No OpenCL. So I found a fix from Netkas, installed it, and hey, liftoff. So, here are benchmarks and observations.
Here’s LuxMark doing Sala. That’s a pretty solid improvement. I would have hoped for a bit more, but I’m not complaining. Of course, the real strength of an Nvidia card over ATI is CUDA; the 670 is probably about six million times faster in After Effects.
Wait, crap. Check the GFX details; the 5870 is the first result, and the 670 is the second result. That’s annoying. Cinebench is pretty dated these days, but the numbers went down! My precious numbers! Well, Kepler drivers are immature. Hopefully this changes over time.
Now, games. Everything was tested at 2560×1440 at the highest detail settings.
Starcraft 2 gained about 10 FPS (61 vs 50, average) on the 670, tested playing a Bly v. Tarson replay. So that was cool; you can see that Barefeats got the biggest improvement on a 570/580 from SC2 at those settings. Then I tried Civ 5; not only was it slower on the 670, it was kind of glitchy. Source games don’t really tax the 5870, so it’s hard to see much improvement in practical play, but the 670 was about 15% faster across Portal 2 and L4D2. L4D2 did have a weird bit of stutter when levels started. Dirt 2 ran great on both cards, although it remains a super-annoying game. Cities in Motion was, I think, slightly slower on the 670, but played fine. It gets jumpy with a huge map and the fastest game speed. The Sims 3 was just about as fast, too. Weirdly, Diablo 3 didn’t improve at all — you’d think whatever worked for SC2 would work for D3, but no.
My wrapped version of Skyrim was the only game here that wasn’t really playable on the 5870 at 2560/Ultra, so I was excited to see what the 670 did. It did nothing, actually; the game was still jumpy. If I had to cork sniff, I’d say the 5870 was more consistent — the 670 seemed to do a little better as long as you were standing still, and a little worse when you turned. This isn’t really a reflection on either card.
Everything else worked fine. I’d heard people saying that Steam didn’t work with PC GPUs — it did. All my non-game programs worked as well as before. Temperatures were about the same as before, and the 670 managed its fan just fine (it’s quieter than the 5870, which made me nervous). Restarting in Windows showed off what the 670 could actually do, of course, although I found the difference marginally underwhelming in stuff like New Vegas and World of Tanks. But then, they’re not taxing anyway, and the only tricky stuff for the 670 to add is anti-aliasing. Anyhow, the 670 in Mac OS is pretty much as fast as the 5870 except if you like Civ 5.
I ended up a little conflicted. The 670 is better than the 5870, depending on what you’re doing, but not by that much in most cases except for CUDA. It’s unsupported, and there were a couple glitches. The 5870, in comparison, is an OEM card that developers (presumably) test against, so you won’t see much in the way of issues, and it’s still the fastest OEM Mac GPU by a comfortable margin (over the iMac’s 6970M). However, the 670 is definitely faster in Windows, and there’s a lot of potential for the Mac drivers to improve and let the 670 really go nuts.
I got a bunch of questions regarding the 3.33 six-core swap in my Mac Pro, so here are answers:
So I just finished the W3680 swap. Really easy, and no troubles with the software side of things. I have the base 2009 Mac Pro, with the W3520, and it’s okay. But because the Pro is a sensible computer, you can put a newer processor in. And I got a great deal on the 3.33 six-core, which is what has come in the top single-processor Mac Pro since 2010. All this also applies to putting a W3670 in the 2009 Pro. That’s the six-core 3.2, which is pretty much as fast and about $100 cheaper.
The only things you need are the W3680, some Arctic Silver thermal compound and thermal compound remover (Amazon or NewEgg has the ArctiClean kit that comes with remover and “purifier”), a long 3mm Allen key, and the Mac Pro Firmware Upgrade Utility (you have to register to download).
The first thing to do is to use the firmware upgrade utility to make your Mac Pro think it’s a 2010. That’s one click. It’ll still identify itself as a 2009 in the System Information panel, but I believe that pulls its information from the serial number; the computer itself behaves as a 2010, and you’re clear to install the newer processor with B1 stepping. It’s worth pointing out that the W3680 is the same chip used in the 2010+ Mac Pro, as is the firmware, so this is all OEM — no weirdness.
Once the software is done, it’s just like swapping the processor on any other computer. Actually, it’s easier, since the processor lives on a daughterboard. Pull that out:
As a result of the shitsville Mac Pro “update”, I got a 2009 Mac Pro, which is pretty easy to upgrade to the current spec. You just need a newer Xeon and one of Apple’s insanely overpriced and outdated GPUs. A quick firmware bebop, and yer done.
I have a few of the old colorful iBooks (a Tangerine and a Blueberry), which I like because they’re indestructible, and have a much more naïve design than modern Macs, which are quite Germanic and boring. The Tangerine is overclocked by 133mhz, has CompactFlash instead of a hard drive, and I re-celled the battery so it can get about 12 hours of life. It makes a great simplistic writing machine.
Of course, the essence of technological simplicity is needlessly complicating and overthinking it, then rationalizing more nonsense purchases. I like the FireWire iBooks because the colors are nicer (it’s less translucent and more white), and I also wanted to try a shady Chinese SSD instead of CompactFlash. So I got a preposterous KingSpec 16gb IDE SSD, and another iBook, a 366 Indigo. Here’s the procedure and a little test of the KingSpec.
Here’s the SSD. The mark of quality… must be around here somewhere…
There’s the computer with its keyboard off. In a nice world you could get to the hard drive from here, but the Clamshell iBooks (and every other iBook) are actually among the more notorious Macs to re-hard drive.
There’s the removal of the top case. Surely one can now get to the drive….
…oh. Then the EMI shield comes off. There’s the 60gb 7200RPM drive that I transplanted from a P4 2.8 Toshiba. I was going to overclock this computer to 433mhz like the older one, but Apple moved the resistors that you re-solder to do so in these second-generation clamshells, and I have no idea where they went.
At this point, I became paranoid that the Chinese SSD was playing cards, or nothing, so I took it apart.
There was actually real memory inside there. And it’s from Hynix, a brand I have heard of! I didn’t take the sticker off the controller to see who made that (I thought it might let the ghosts out). It isn’t JMicron, though.
There, now it’s in. I got this down to about 50 minutes from start to finish, so it doesn’t seem that hard. Putting the display back on is kind of annoying because the clutch cover has to go over some tabs, but it’s not bad.
Anyway, then I tried it out. It starts reasonably quicker—49 seconds from power-on to opening a browser, compared to 1:35 on the hard drive. The battery meter on the OEM battery jumped from 3:55 to 6:20, 13 hours on my custom battery, and of course it’s also silent. Here’s the XBench score; SSD on the left, HDD on the right.
You can see the SSD is a lil’ faster with small sequential writes, slightly slower with sequential reads and big seq. writes, and way, way quicker with random reads. That’s nice, because random reads are what a computer spends most of its time doing. For modern comparison, here’s my MacBook Pro’s 500gb 7200RPM SATA HDD (on a much faster bus, of course):
So the cheap Chinese SSD may have an awful controller, but it overpowers a modern HDD by a factor of 10 in small random reads, and that’s handy for making a computer feel quick. Although this one’s pretty CPU-limited. It’s a lot quicker than the CF “SSD”. So I’m pretty happy with this experiment. It runs OS 10.4 and WriteRoom just fine. My rationalization for keeping the other iBooks around will be “emergency Starcraft 1 LAN party laptops”. That actually happens sort of frequently around here, so I am being prudent.