Comment 15 for bug 1103236

Also I'm not sure if this is of help, but someone commented on the Ask Ubuntu page where this originally was posted and supposedly the problem was resolved for that person by suspending to ram then resuming which then "initialized" the chip. However, I tried this with no success.