Always Check the Lowest Common Denominator

I've been going through some rounds with Asus tech support/customer service the last couple of months. Two RMA's and a brand new unit later, I have resolved the issue. I must admit it is a slightly embarrassing fix. It is a true example of making a mountain out of a mole hill in the technology industry.

I can't believe I missed this fix for so long, I can't believe my older brother who works on computers didn't think of it sooner, but really - I'm pissed off that the Asus repair facility didn't think of this before replacing the motherboard and screen in the netbook.

This morning I had the bright idea to boot up the T101mt again, but this time after I hit the power button I press function+f6 to toggle the brightness setting on the screen up. Sure enough the screen clicked right back on.

I don't think I have ever felt so stupid. It appears the recently added backlight code for Enlightenment was simply turning of the T101MT's internal display by default.

This is just a friendly reminder to everyone else out there that when debugging something - don't just skip over the lowest common denominator. It could save you a world of headache.

~Jeff Hoogland