Thanks for testing the patch; since the video came up, that suggests we're on the right track, and that your issue is likely indeed to be fdo 12490.
It looks like overnight alex took care of the remaining issues people had reported, and the bug is now closed as fixed. If he puts out a new release soonish, we may be able to pull that into Gutsy, else we can try putting in via an update. I'm reluctant to put this single patch in, since it sounds like it's incomplete by itself due to the gamma issues you're reporting.
Offhand I'd think the mouse issues are coincidental; as far as I know, video driver code and input driver code is isolated. I would suspect KVM quirkiness before the driver. With my avocent kvm I've noticed the mouse gets lost in certain circumstances, requiring the kvm to be reset and sometimes the computer system to also be restarted. So my guess would be that it's an unrelated issue. However if you can determine it's definitely due to this driver, let me know so we can get that reported.
Hi Nick,
Thanks for testing the patch; since the video came up, that suggests we're on the right track, and that your issue is likely indeed to be fdo 12490.
It looks like overnight alex took care of the remaining issues people had reported, and the bug is now closed as fixed. If he puts out a new release soonish, we may be able to pull that into Gutsy, else we can try putting in via an update. I'm reluctant to put this single patch in, since it sounds like it's incomplete by itself due to the gamma issues you're reporting.
Offhand I'd think the mouse issues are coincidental; as far as I know, video driver code and input driver code is isolated. I would suspect KVM quirkiness before the driver. With my avocent kvm I've noticed the mouse gets lost in certain circumstances, requiring the kvm to be reset and sometimes the computer system to also be restarted. So my guess would be that it's an unrelated issue. However if you can determine it's definitely due to this driver, let me know so we can get that reported.