On 25/03/2011 11:42, Andrew O. Shadoura wrote:
Possibly. But somehow this worked fine with 2.6.36.
That's the point. Now i have to use the 2.6.37 because with 2.6.38 i have screen corruption. From what i've understood from Intel developers, 2.6.38 contains changes that require an x driver not yet released or older than the current. Or, as we are doing, to use an older kernel. But i believed this was a problem specific to older chipset, like mine, so my doubts that this bug has a different origins.
Ciao. Cesare.