On 7/16/22 16:48, Patrick Shanahan wrote:
What confuses me is that the mouse-receiver worked on the red port since beginning (for approx. 3 month), but stopped working a few days ago, and now only works on a blue one... that would suggest a driver change/problem ?? or a hardware failure ...
Agreed, Dating myself, but it took a while for USB3 to catch up to handle all the peripherals on USB2. For a couple of years, mouse hardware specifically recommended staying with USB2 for the problems described. The USB3 driver finally fixed all that. However, it isn't out of the question that there has been some type of regression or new bug introduced in the latest version of the 3.2 driver. Would be worth a couple of searches on "<your mouse type> USB3 problem" and just see if there is any history that may point in the right direction. If it is a new OOPS in the driver, the commit responsible will have to be tracked down. -- David C. Rankin, J.D.,P.E.