

After replacing the caps, I put all the hardware from the one system into it. I was able to finally test this theory, absolutely, when I got a bad caps Asus nForce 2 board. I ran Ubuntu and noticed the same issue! This proved to me it was not just an issue with Haiku, alone.Īt first I thought it was the USB driver… but other systems I ran Haiku on didn’t have the same problem, so I realized it must be the chipset. And my GLTeapot framerate seemed a bit lacking! I waited a couple THOUSAND revisions, for the USB issue to be fixed and it never was.

This was with it hooked directly to the computer, not through a hub. But within a last year or so, I noticed that my USB mouse would eat up to 50% of my CPU whenever I would move it, in Haiku. I ran BeOS R5 PE and the “WIND” distro version of it, later on. For example, I have a Jetway Via chipset Socket A motherboard and a Asus nForce 2 chipset socket A motherboard.įor several years (at least since 2004, if not before), I have used the Jetway board. That hardware is of prime importance when it comes to Haiku’s functionality/performance.
