02-12-2016, 04:07 PM
I have not. I wouldn't think that would help much, either -- the issue is definitively with the driver, and is being pursued in their bugtracker as bug # 91966. (Link) I am working with a fellow named Kevin Brace to solve the issue. Until it is resolved, really the only solution on this hardware is to roll the driver back to the last known good version -- which would be Precise Pangolin's v.0.2.904.