The problem seems to be solved in the git-version of the driver (from 2008-02-08, last commit 8c8ca16120927fc2d3cf8bcd5212a4227a280708). I would like do some more testing before closing this bug, but so far everything looks fine.
Regards, Soenke Brice Goglin wrote: > > Do you mean that it didn't happen with the previous intel driver, i.e. > 2:2.2.0 or so ? > If so, it would be great to git-bisest between these releases (on > xf86-video-intel-2.2-branch in the upstream git repo) and find when the > problem appeared (if you need help, let me know). Since you seem to be > able to reproduce quite easy, bisect could be pretty easy. > > Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
