Hi.


This took some time.

On Fri, 2011-11-18 at 08:45 +0100, Stanislaw Gruszka wrote:

quoted

and just from current 3.1?

Yes (I lose your old logs). But I also need verbose log for 2.6.38
(assuming 2.6.38 is the lates version where driver works for you)
to see what we do different regarding communication with firmware.

I went back till 2.6.32, and the problem occurred with all kernels
again.

The logging is basically identical to what I've send before.

So either there is some weird hardware damage,.. or (as I suggested
before) it might be just some different revision or so of the chipset,
behaving different?!


Guess it's pointless to send you the same logging output again, but if
you'd like to I can do so.


Cheers,
Chris.