On Thu, 2 Oct 2003, Branden Robinson wrote: > Unfortunately, I can't see any evidence that dexconf tried to set your > mouse protocol to NetScrollPS/2. > > In fact, I can't find any evidence, even in your original report, that > either mouse device was ever described as using the NetScrollPS/2 > protocol. On what basis did you come to believe it had?
After I upgraded and rebooted the mouse stopped working. When I switched to another virtual console and diffed the XF86Config-4 file with the backup I saw the PS/2 had been switched to NetScrollPS/2. I configured it back to PS/2 and that fixed things. I just assumed it was dexconf that switched it, since I hadn't done it. Does dexconf or something else know how to probe the mouse to find out what it is? Under 2.6.0-testX having the mouse set at PS/2 worked fine, even with the wheel. But I switched back to 2.4.22 today, and the wheel stopped working until I changed the config to ImPS/2. I've only had the "new" mouse about a month, it was being thrown out at work, so this is the first time I've used it under 2.4. This makes me think the 2.6 kernels handle mice somewhat differently than the 2.4 kernels. Probably an entirely unrelated issue. Thanks for your help on this. --Andre