I think it was the 2.6.35-23 update that resolved it (whether intentionally or otherwise) - try that one.
I think it was the 2.6.35-23 update that resolved it (whether intentionally or otherwise) - try that one.