Re: moused problems, not related to acpi
Please type boot -v at the loader prompt and send me dmesg's output after the system has started. I would also like to know more about your mouse: manufacturer, product name, model No, a URL which lists this mouse, etc. Thank you, Kazu -current as of yesterday. I've got a new mouse, but it isn't compatible with moused: I get psmintr: out of sync (00c0 != ). and any cursor movement moves the cursor to the upper right edge of the screen. Further mouse movement results in virtual button presses. Attached is the output of moused -p /dev/psm0 -d -f. The output shows in this order: - move to the left - move to the right - move forward - move backward - push left button - push right button - push middle button - scroll wheel forward - scroll wheel backward - push the second left button (yes, there's a second button behind the left button) - push the second right button The mouse is labeled as a 600dpi mouse (-r 600 didn't changes the behavior). Win2k has no problems with it, unset acpi_load at the loader prompt didn't changes the behavior. Bye, Alexander. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: moused problems, not related to acpi
On 25 Sep, Kazutaka YOKOTA wrote: Please type boot -v at the loader prompt and send me dmesg's output after the system has started. Omitted in the mail to -current. I would also like to know more about your mouse: manufacturer, product name, model No, a URL which lists this mouse, etc. NoName 4D Browser Mouse ??? (FCC ID:10WCM-B700) ^^ either '1' or 'I' and '0' or 'O' ??? (got it in a local store for DEM 20 (~$10?)) Additional info: - made in china - 5 buttons + wheel - 600 dpi - tracking speed: 250mm/sec - it's also available as a serial or USB mouse and with 400 dpi My old mouse died either while unplugging it from a running system or by plugging it into another running system (yes I know, PS/2 isn't hot-pluggable). The new mouse works with W2K in the first system, the second system refuses to boot if the new mouse is plugged in. I try it with another mouse later, to determine if the second system (Asus P2L97-S) is damaged or not. And I try the new mouse with a 3rd system. Bye, Alexander. -- The best things in life are free, but the expensive ones are still worth a look. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: moused problems, not related to acpi
On 25 Sep, Kazutaka YOKOTA wrote: Please type boot -v at the loader prompt and send me dmesg's output after the system has started. Omitted in the mail to -current. Thank you. Hmmm, the output doesn't show anything suspicious. It looks like that the mouse is just an ordinary one... psm0: current command byte:0047 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:, flags:, packet size:3 psm0: syncmask:c0, syncbits:00 We need some more tests. Would you add the following lines to your kernel configuration file, rebuild the kernel, and do 'boot -v' again? options KBDIO_DEBUG=2 options PSM_DEBUG=2 Kazu I would also like to know more about your mouse: manufacturer, product name, model No, a URL which lists this mouse, etc. NoName 4D Browser Mouse ??? (FCC ID:10WCM-B700) ^^ either '1' or 'I' and '0' or 'O' ??? (got it in a local store for DEM 20 (~$10?)) Additional info: - made in china - 5 buttons + wheel - 600 dpi - tracking speed: 250mm/sec - it's also available as a serial or USB mouse and with 400 dpi My old mouse died either while unplugging it from a running system or by plugging it into another running system (yes I know, PS/2 isn't hot-pluggable). The new mouse works with W2K in the first system, the second system refuses to boot if the new mouse is plugged in. I try it with another mouse later, to determine if the second system (Asus P2L97-S) is damaged or not. And I try the new mouse with a 3rd system. Bye, Alexander. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
