Thank you very much for all of your help. While nothing you suggested was actually the solution, it lead me in the right direction to discover the answer myself.
The solution was to enable 'Support Legacy USB Devices' in my BIOS (as 'secondary'). In this case I apologize for having troubled the usb mailing list with this problem. However, I do not recall changing this option or anything else in my BIOS since I had Red Hat 8 working before, and so it appeared to me as a mouse problem. I had also looked at this option previously, but I did not think that my MS Intellimouse Explorer was (for practical purposes) a "legacy" device. I changed it just for kicks, to see what would happen, and am happy that I did. So, if anyone else has had a similar problem, this is something to try. If nothing else, we all learned a little bit more.
Cheers!
Aubrey BarnardAllen Martin wrote:
Don't bother trying to get ACPI working, as of 2.4.22 it's still broken for nForce boards, you want the interrupt controller in XT-PIC mode for working interrupts.
I'm not aware of any interrupt related problems with nForce in XT-PIC mode. As a matter of fact I have the same USB mouse as you do running on an nForce3 system with kernel 2.4.22.
I would definitely try removing any other devices you aren't currently using to help narrow down the problem. Also try disabling the second USB controller from the BIOS (Integrated peripherals menu) since it shares the same interrupt.
Does the system hang when you move the mouse if you aren't running X? (init 3)
-Allen
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
