On 10/11/15(Tue) 23:51, Paco Willers wrote: > Hi, > > > I reinstalled OpenBSD 5.8 and updated to stable again, so I now have a > clean install. The only thing I configured manually is: I added > 'apmd_flags="-A"' in /etc/rc.conf.local to do CPU frequency scaling while > I'm not sure my system supports it. > > It seems a randomly occuring problem. My mouse: "vendor 0x0000 USB OPTICAL > MOUSE". It's wholesale cheap stuff. Other OSes don't show the problem, and > that makes me believe the mouse is doing alright. I happen to have two of > them, so to be certain I'll swap it and test this new configuration in a > few days. I'll keep you informed. I wouldn't be surprised if this cheap > piece of hardware would have some minor incompatibility that only a correct > OS's (OpenBSD) driver would crash upon. :-) (That doesn't explain Maurice's > identical problem using a Logitech mouse. Also, to my knowledge a crashed > driver would raise an error message which I didn't see.) > > Here are my dmesg outputs that might help. Of course if you want to see > more files, I'd be happy to provide them. Also if you come up with some > ideas I could test, let me know. (I won't be available for a few days > however.) > > My dmesg detecting the mouse:
Could you play with lsusb(1), from the usbutils package? "lsusb -v" will report the hub status for each hub port. I'd suggest running "lsusb -v" when your mouse plugged in but not recognized, then unplug it an run it again. Compare the outputs. Also compare them to an output when the mouse is recognized. If you can send me these tree output (you can limit them to the corresponding hub) it could help figuring out what's wrong.
