Always Check the Lowest Common Denominator
Ive been going through some rounds with Asus tech support/customer service the last couple of months. Two RMAs 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 cant believe I missed this fix for so long, I cant believe my older brother who works on computers didnt think of it sooner, but really - Im pissed off that the Asus repair facility didnt 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 dont think I have ever felt so stupid. It appears the recently added backlight code for Enlightenment was simply turning of the T101MTs internal display by default.
This is just a friendly reminder to everyone else out there that when debugging something - dont just skip over the lowest common denominator. It could save you a world of headache.
~Jeff Hoogland
alternative link download