@Lionel: I asked because Clay mentioned three posts above yours that the problem was fixed. And it was a new 2.6.22-8 kernel.
@Lionel: I asked because Clay mentioned three posts above yours that the problem was fixed. And it was a new 2.6.22-8 kernel.