The issue described here does not occur in intrepid and should be marked as fixed. What you're describing is a different bug, which appears to be fixed in the 2.5 branch of the intel driver (I don't know about 2.4.2, though).
The issue described here does not occur in intrepid and should be marked as fixed. What you're describing is a different bug, which appears to be fixed in the 2.5 branch of the intel driver (I don't know about 2.4.2, though).