I have now been using the drm modules from git with 2.6.24, and everything has worked just fine. The native suspend/resume of the intel driver (which was merged in 2.6.25) might be the reason for all I know.
I'm quite certain now that the bug cannot be fixed in intel driver, but rather in the drm modules of the kernel.
I have now been using the drm modules from git with 2.6.24, and everything has worked just fine. The native suspend/resume of the intel driver (which was merged in 2.6.25) might be the reason for all I know.
I'm quite certain now that the bug cannot be fixed in intel driver, but rather in the drm modules of the kernel.