For the record, the e6410 problem mentioned in comment #3 has now been identified as a different issue (bug #595604).
For the record, the e6410 problem mentioned in comment #3 has now been identified as a different issue (bug #595604).