Archive for the ‘Ponderings’ Category

Exit Review: IBM T60p

Saturday, June 28th, 2008

Keeping in line with the exit review series, I’ve written an exit review of my IBM T60p laptop, which was recently retired.

The T60p was purchased back in March 2006, right when the first dual-core mobile chips started shipping. The IBM model number was 2623-DDU, and it featured an Intel T2500 (2GHz), 2GB RAM, 100GB 7200rpm HD, 15″ 1600×1200 LCD, 512MB ATI FireGL V5200, CDRW/DVDRW, Intel 802.11abg wireless, WWAN, Bluetooth/Modem, 1Gb Ethernet, UltraNav, Secure chip, Fingerprint reader, 9 cell Li-Ion batt, and WinXP Pro. Like most of my key gadgets, the T60p followed me everywhere around the world; I spend probably 16 hours a day with it, so it got plenty of wear and tear.

I retired my T60p because Microsoft is retiring Windows XP, and I really don’t want to downgrade to Vista (“congratulations, your new faster hardware now runs slower than ever thanks to Vista!”), so I decided to get the latest, greatest Windows XP laptop available today, and hunker down and hope it lasts me until Microsoft figures out how to get Vista right (or they realize what a terrible mistake they’ve made and bring back XP…sort of like how Intel brought out the Pentium 4 but now all the new designs are Pentium III derivatives). Or maybe before that, Linux support for all of my key apps will get so good, I can finally depart from the Windows ecosystem.

So the reason for getting rid of the T60p isn’t because it had any functional flaw; it’s actually in fair working order, and its performance is still decent.

Here were some of my favorite features about the T60p:

  • Integrated Verizon EVDO. This was a life-changer; the availability of broadband wireless anywhere in the US in an integrated fashion has literally changed the way I work and live, and it has greatly increased my productivity, especially when traveling. No more searching for free hotspots! Less worry about people sniffing my wireless signal!
  • 1600 x 1200 screen. Can’t live without the pixels!
  • Good horsepower. Plays WoW well, although it struggled a bit with TBC expansion pack. Runs all my design software adequately.
  • Decent battery life. On a 9-cell battery, I get about 3.5 hours a charge. The 6-cell battery gave me about 2 hours, which is long enough for general use; typically I go around with the 6-cell battery as it’s lighter and easier to carry.
  • Nice keyboard. I’ve always liked the Thinkpad keyboards.
  • Fingerprint sensor. There’s something sexy about stroking your laptop to log into it, even if it is a security gimmick.
  • TrackPoint mouse. The TrackPoint is essential for precision CAD work, and one of the reasons I can’t use a whole class of laptops that lack this feature, including Apple laptops.
  • Nice looking. I like the austere black slab look of the Thinkpads — the Dell and HP laptops look so cheesy and plasticky, I feel like I’m carrying around a Fisher-Price toy when I have one of those. I hate to say it, but the Apple notebooks are also getting a bit trite, and from what I’ve seen metal tends to dent, deform and scratch, whereas plastic is more resilient.
  • Good accessories. The AC/DC adapter was the best — compatible with every voltage in the world, auto DC adapters and those funky EmPower adapters found on some airplanes. Also there was a pretty good parallel/serial adapter provided by IBM (as well as one integrated into the minidock), which is key for embedded hardware development.
  • Great thermal management system. The laptop’s fan is whisper quiet, but it pumps out a lot of heat. It’s great to be able to hold your hand about five inches away and feel the heat being quietly pumped out of the laptop — a true sign of good thermal design.
  • Great customer support. Every one of my interactions with warranty service was positive, with the exception of talking to the guy to renew my warranty service. He was pretty clueless, but it was a moot point since I got a new laptop anyways.
  • Solid construction. With the exception of a service-induced crack (more on that later), the T60p is in good condition. The clutch on the screen is still solid, and the hard drive is still in good condition (although it does operate noticeably slower, probably due to the bearings being degraded by years of operation in tough conditions, such as airplanes in turbulence and bumpy car rides in China).
  • Good uptime. My average uptime for my laptop was about two weeks without a reboot — this is through multiple sleep cycles and reconfigurations to my external dual-monitor rig, etc. The chief cause for reboots was actually windows running out of GDI resources due to application leaks.
  • Reasonably light and thin. I wish it were like the ultra-thin laptops, but hey, for the amount of performance I demand and the pixels I require on the LCD, this is probably the best compromise. I do keep a spare ultra-light laptop around for the times when I go on vacations to far-flung regions of the world and I can’t afford the weight of my primary laptop.

    However, I also had many, many problems with the T60p as well. Here are some of the more significant ones:

  • About a year into using the laptop, the ThinkVantage access software blew up on me, rendering my internal WiFi card useless. This was triggered when I once installed an external Wifi card for testing purposes, and the installed drivers broke some internal configuration. I tried just about everything short of wiping the OS to get my WiFi card working again, but alas, I never got it back. It’s tragic, as it’s like I had a hardware failure due to a software error. Fortunately, I have copious quantities of USB Wifi dongles laying around thanks to my work, so I just carried one of those around all the time.
  • The Verizon Access software is flaky. I had a little ritual for getting it to work — turn off the radio, start the app, let the app crash once, turn the radio on, start the app again, and then it works. If you started the app with the radio on it’d never figure out that there was signal. What a weird wart.
  • The case near the trackpad cracked. This was due actually to a flawed repair job by a technician that replaced my LCD. The technician didn’t mate one of the friction-lock connectors on the keyboard bezel exactly, which created a stress point and eventually caused the panel to crack.
  • Speaking of which, the LCD had to be replaced once. The LCD failed by having a set of horizontal lines across the bottom of the panel (I recognized that failure as stress-related failure of the COB drivers on the panel). The replacement LCD had a flaw in it too — there was a spot of blue pixels, about ten pixels on a side, that were always stuck-on, just faintly. It wasn’t annoying enough for another return but still, it’s unfortunate that the replacement LCD had a significant flaw as well.
  • One of the DRAM SO-DIMMs failed about 1.5 years into the laptop’s life. It was manifested by lots of bluescreens, and then I ran some DRAM test software and identified the problem. Spray-cooling the DRAM chips fixed the problem, so I installed some extra heat sinking in the laptop, which got around the problem for another month. Eventually, I had to call in for a replacement of the chips, which was laudably painless. The IBM service rep just sent out the replacement chips right away, no questions asked, and everything worked fine from then on (the laptop was still under its extended warranty at this time). However, it does highlight the fact that there is a thermal design flaw in the DRAM area: there is no heat piping or heat sinking around it. I think that’s because most configurations use less DRAM; I really cranked up the DRAM configuration, which meant I installed the most extreme, power-hungry devices in my laptop, pushing the thermal design margin right to the edge.
  • The trackpoint mouse was flakey sometimes; the drivers would sometimes not load properly or crash, which is annoying.
  • The ThinkVantage system update software, while a nice concept, is a bit annoying to use as it has to update itself typically before updating the system. As a general note, I don’t like vendor-specific extensions to the OS. They are never very well done, and often break: “Dear vendor, please stop trying to ‘add value’. You actually are destroying the value of your brand. Just make your good hardware and don’t get in my way, kthx bai.”
  • The FireGL V5200 graphics chipset, while very powerful, had some serious compatibility limitations. The OpenGL drivers never really worked right, and it was totally unsupported by some games, such as Second Life. Unfortunately, graphics drivers for laptops lag the main branch, since it seems every laptop requires a bit of tweaking to the drivers by the vendor.
  • The UltraBay lithium polymer battery that I purchased failed — twice. The failure was manifested in the battery going to 60% capacity within two months of use. The first time I called it into warranty service and got a replacement, and the second time it failed I just decided it was a design flaw and gave up on replacing it. The UltraBay lithium polymer is handy for situations where you’re on battery power and you want to swap out the main battery without going into hibernation. Fortunately, that situation was rare and the battery life of the main batteries was good enough, so it wasn’t really a problem in practice.
  • This is more my fault than anything else, but 100 GB was too small to live in. It didn’t help that I had multiple VMware images on my machine and my hardware design tools often chew up over 3GB per tool. The 2 GB of DRAM was also tough to live in; Altium DXP eats a gigabyte on its own, so starting and stopping the tool is painful as the page file starts kicking in.
  • Minor nit: the TrackPoint mouse will become uncalibrated if you lean on it lightly for too long, and the mouse will start gliding across the screen on its own. Fortunately, the driver is very intelligent and detects this condition so it’s short-lived.
  • This is a general fault of windows, but the 65k GDI resource limitation just sucks. Running out of GDI resources was the key source of reboots for me; Adobe tools and Altium DXP were notorious for leaking GDI objects, and unfortunately I use both heavily.
  • Bluescreens were rare, typically caused by either pulling out USB devices at inopportune times or problems occurring during standby, but one weirdness really got to me. Toward the end, if I walked around with the laptop, it would blue screen. This was because the hard drive shock detector would pause the drive, which would cause some application fault in windows that wasn’t expecting the pause. If I had to move around, I had to suspend the shock protection, which is sort of defeating the purpose of the protection. This wasn’t the case when I first started using my laptop. Why it developed this problem over time is a mystery to me.
  • Well, that’s my experience with the IBM T60p. I think my experience can be summarized by the fact that my new laptop is an IBM T61p — they won a repeat customer. The T61p is still settling in. I like the extra performance it brings, but it has some quirks of its own that I’m still learning to get used to. It’s funny, but every time I get a new laptop, I have to learn all of its little bugs and find ways to patch my behavior to avoid aggravating them. For example, I’ve trained myself to unplug my webcam before hitting the eject button on the minidock, because failing to do so causes a blue screen without fail. So far, none of the quirks have been so bad that I’ve given up on the machine. In addition to the webcam issue, I did have a spate of blue screens to deal with when I first got the laptop (mostly around minidock ejection and going into and out of standby), and I had to do some digging around in the Minidump logs to figure out exactly what behavior was triggering them. I wonder what other users do when this sort of thing happens to them?

    All Your Bits are Belong to Google?

    Sunday, June 22nd, 2008

    I recently saw a demo of Android booting up in a CoWare environment, and I couldn’t help but notice this line in the Android boot console:

    ...
    Freeing init memory: 96K
    init: HOW ARE YOU GENTLEMEN
    init: reading config file
    ...
    

    That’s a little scary. If you don’t get the reference, it’s the infamous first words of CATS, followed by the immortal phrase “all your base are belong to us“.

    I mean, I love the google search application, but I am a little bit disturbed by the masses of people trusting all their bits to google — their email, their desktops, their photos … soon their phones (no, I don’t use gmail — I must be the last person on earth who doesn’t — but the idea of ads showing up based on what’s in my email is disquieting for a variety of reasons). And I think that surely the Android developers cannot claim ignorance to the context of the phrase: all your base are belong to us // you are on your way to destruction // you have no chance to survive make your time.

    Now, Don’t be Evil!

    Incidentally, CoWare is a really neat tool; one of their other demos is a hardware simulation of the chumby platform. It’s absolutely amazing that they have a cycle-accurate simulation of the chumby hardware platform that boots our code and runs almost real-time. Since it’s a hardware simulation, you can jump in and inspect the state of signals between components, wiggle lines, and set breakpoints based on hardware state (as well as software state). This is one of those cool things that come out of having an open platform; without access to our source code and documentation, creating this demo without the help of chumby would have been much more difficult. And while some consumer electronics companies would go batty over someone emulating their platform, I say to them hats off for such a clever hack and such a powerful product.

    The Chinese think LA is a small city…

    Friday, April 25th, 2008

    I heard the best quote ever on today’s All Things Considered story on easing travel restrictions for Chinese tourists. Rob Schmitz reported that Chinese tour operator Vincent Bao may need to eliminate some destinations on his itinerary:

    The last time he took a Chinese group to downtown LA, for example, Bao says they got off the bus, rolled their eyes, and said it reminded them of any number of small Chinese cities. They then demanded to be taken to Rodeo drive, so they could shop.

    You know, before I went to China, I would have thought this was hyperbole — I grew up in a small town in the American Midwest, surrounded by undeveloped fields, so back then it was hard for me to imagine a place like LA being called small and unimpressive. Now that I’ve been around China, however, I’d have to say their assessment of America’s #2 city (by population) is just about right. Interesting thing is, I never really thought about it that way, until I heard this quote; it’s hard to see your own country through another countryman’s eyes. It’s also interesting to see all those dollars spent by Americans in Wal-Mart flow to China and come back home to Rodeo Drive, to be spent on high-end European luxury goods. I guess the weakening US dollar is good for something.

    Exit Review: Blackberry 8700c

    Thursday, April 17th, 2008

    I think it’s time to start a new kind of gadget review: the exit review.

    Gadgets always seem to arrive on the scene with a lot of splash and hype, but rarely do you find an article telling you how the gadget fared in Real Life. The Exit Review is something I’m going to try doing every time I retire a major gadget of mine; the idea of it is to reflect upon how the gadget performed over its duration of service. Of course, reviews like this are all hindsight, so they don’t drive sales — which probably explains why nobody does them, because there’s no money to be made doing them. However, as a design engineer I think there are lessons to be learned through reflection, and as a consumer I believe that apples don’t fall to far from the tree — a good gadget maker will get my business again, and a bad one will never see another dime from me.

    Recently, my 2-year contract with AT&T wireless expired, so I’m up for a new phone. It’s time to retire my trusty Blackberry 8700c. To set the mood for the exit review, you really must see pictures of how the device looks today.


    Click on the photo above for a much larger version.


    Laser engraving works great on the Blackberry.

    Yes, I’m very hard on my gadgets. I think the cosmetic state of the phone was eloquently summarized by a saleslady in China who blurted, “This looks like shit!”, upon inspecting my phone. Yes, those are in fact two enormous cracks in the front screen protector (they aren’t in the LCD itself — just in the outer protective case), and I’ve been happily using my phone like that for months.

    Those cracks are like badges of honor — a real phone keeps working despite being drop-kicked from four feet or being rattled around inside a suitcase against an electric shaver while being dragged over cobblestone streets in Italy. The cracks don’t interfere with the functionality of the phone; they are thin so they don’t distort the text of emails that I’m reading. It’s a testament to the reliability of the phone. This is in contrast to the Apple iPhone, which is definitely a pretty face with a glass jaw. I’ve seen plenty of iPhones with shattered screens, and most of them after a couple months of use look like a dented and beat up old tin can. That is, unless you put your iPhone into one of those ridiculous iPhone condoms that everyone seems to use. What’s with that, anyways? People pay top dollar for a good-looking phone that’s super-slim, and immediately stick it into a bulky and horrific-looking rubber condom.

    The crazy thing is those obvious battle scars don’t tell half the story. Every one of those little black nicks on the side of the phone (not really visible in the photos above) is made by a drop onto asphalt. I sleep on a lofted bed, six and a half feet up, and many mornings I wake to find that I’ve kicked my phone off the bed onto the ground. So there’s about a hundred drops there. It’s been hurled across the room, drenched in sweat to the point where it’s condensed on the inside of the screen, thrown in the sand, sat on, stepped on and kicked across the asphalt. So it’s durable.

    It’s traveled with me to over a dozen countries in Europe and Asia, and the Quad-Band GSM radio has worked great in every country that uses a GSM standard (I did have to unlock the phone). The data service works overseas as well, too, so I can get my email fix. When I’m in the remote regions of South China I think I grip my Blackberry like a safety blanket, holding on to my final bastion of familiar English text in an overwhelming flood of mandarin characters.

    Significantly, it’s still on its original battery. The amount of charge the battery can hold is definitely reduced, but it still lasts for about a day and a half of regular use without needing a charge. You can see in the photo above that the phone’s still at 3/4 full at the end of the day.

    The most impressive thing about it, however, is how many times the phone has crashed on me since I’ve owned it: zero. There have been about five times in two years where the radio gets confused, and I’ve had to pull the battery — fortunately, that bug happens only when I’m using the phone to browse the web, and the UI is still working so you know something’s wrong. Also, I’ve never had a bad web page crash the phone outright. I’ve had the phone seize for about twenty seconds on some really nasty webpages, but then the Blackberry OS kills the browser thread and the phone is back to normal.

    Thus, even when the phone is struggling, the screen never freezes up: I have never been mislead into thinking the phone is okay when it’s actually just frozen on the home screen. This is the killer failure that plagues users of Treos or Microsoft Mobile powered phones. I hear so many stories of users routinely missing urgent calls and forgetting appointments because their PDA phone crashed on the home screen — so they were fooled into thinking they were lucky and having an unusually quiet day. Maybe you could think of missing calls for a day as an “involuntary vacation mode feature”…I call it bollocks.

    It seems ludicrous to me that anyone would accept using a phone that crashes! First and foremost, a phone…is a phone. It makes and receives calls. It must do that, without fail.

    And because the engineers at Blackberry built a phone that does just that — make and receive calls without fail — and then also has a good email client in it with a full keyboard, my next phone, currently on order, is a Blackberry Curve 8310. I’m a little worried about that fancy trackball in the middle; I can certainly see me writing an unfavorable exit review of that feature in a couple of years, but I’m willing to take that risk for a phone that I can trust to ring when a loved one or a friend is in trouble and needs my help.

    Bacteria Living on Antibiotics

    Sunday, April 13th, 2008

    I like dabbling in bio, so I keep abreast of recent developments by reading Nature and Science. One article in particular caught my eye the other day–George Church’s “Bacteria Subsisting on Antibiotics” in Science (April 4, 2008, Vol 320, p. 100).

    The common wisdom is that “superbugs” — antibiotic resistant bacteria — are being bread inside humans who don’t finish their full course of antibiotics. The theory is that when you don’t finish your full course of antibiotics, you only weaken them, killing off the ones most susceptible to antibiotics: the remaining few were the ones most resistant to antibiotics. If these remaining bacteria cause you to relapse, the new infection will have a greater resistance to antibiotics. Repeat this process a few times, and you are the culture dish for evolving antibiotic resistant bacteria. Clearly, the solution to this problem is to just make sure we all take our antibiotics to the end of its course. Or is it?

    The interesting part about Church’s report is that the bacteria commonly found all around us in the soil has a high chance of being resistant to every known antibiotic; and not only do they resist them, they can use these antibiotics as a food source! They are “ultimate superbugs”. The obvious question is, why haven’t these just taken over and killed every human? [Note: the rest is all my speculation, and not part of Church’s report…] The answer probably lies along several reasons. Typically, soil-based bacteria doesn’t grow well in human hosts; however, it was noted in the article that several strains of resistant bacteria are close relatives to human pathogens. So maybe that’s not the reason. My thought is that antibiotic resistance requires the bacteria to spend extra energy and resources, so when left in a nutrient-rich environment — like the mucous lining of your sinus — they are out-reproduced by the more nimble, but less robust human pathogens. Since bacterial reproduction happens on an exponential curve, even tiny extra metabolic costs add up to a huge disadvantage in the end. Anyone who has financed a mortgage is aware of how a change of a few fractions of a percentage compound interest per year can add up to a lot over many years!

    So, I guess that’s good — the superbugs aren’t winning yet. However, the remaining threat is that bacteria are very promiscuous. They will acquire or exchange DNA under a large number of conditions, including changes in heat, pH, and electric current, as well as viral vectors. My thought is that human pathogens could “acquire” genomes from their resistant soil-based kin when they mix together, and that the slow-growing but long-lived soil based bacteria are acting like a genome archive where useful but expensive bacterial genes are stored. The problem with this theory, of course, is that when the human pathogen acquires the resistance genes, they reproduce slower than those that don’t, so they eventually go extinct, probably before they can infect a human host.

    But there’s one other factor that’s missing. A lot of antibiotics used on humans and animals are excreted through urine, feces, and sweat. These antibiotics are concentrated in sewage and released into the environment — into the soil. The presence of these antibiotics, even in small quantities, combined with the genetic archive stored in soil bacteria, could be enough to bias natural selection to favor the bacteria that have acquired the antibiotic resistance genes, thus providing a natural environmental reservoir for the breeding and storage of superbugs.

    Think about it: the mere prescription of an antibiotic may ultimately lead to environmental bacteria acquiring a resistance to them, and no amount of care or attention on the part of you and me in finishing our antibiotic courses can prevent this.

    That being said, it’s all just speculation on the part of someone who’s really an electronics hacker and not a biologist, so I wouldn’t go sounding any alarms. But it is interesting to think about the role of environmental DNA and the evolution of species; it may be one of those rule-changing disruptive concepts. I’ve been reading about how sea water contains lots of DNA that codes for all kinds of interesting genes, and how our DNA contains lots of “junk” DNA introduced by viruses, etc. Maybe there is more to evolution and genetics than just simple random mutation and how genes are selected from a pool defined by only those found in the parents. With the incorporation of environmental DNA, totally random, unexpected whole genes can be introduced by the environmental library, absent of any parent. Furthermore, genes that fall out of favor (become “extinct”) due to external changes can be archived in this environmental library and brought back into service at a later time, so evolution, at least for simple organisms like bacteria, might not be a simple linear progression.

    Also, in the same issue of Science, there is a snazzy article titled “Single-Molecule DNA Sequencing of a Viral Genome”. Really, really clever stuff going on in there that probably has application beyond just DNA sequencing; if you have an interest in nanotechnology or single-molecule data storage/manipulation/retrieval it’s worth the read.