Opened 7 years ago

Closed 7 years ago

#124 closed System Defect (invalid)

no working mouse during install

Reported by: mrezny Owned by:
Priority: minor Milestone:
Component: Installer Version: 1.5
Keywords: Cc:

Description

This is actually with the new 1.5.1 installer, but there is no option for that version on the ticket. I have not tried 1.5 as I do not have the ISOs and do not see them easily available as the legacy version is 1.4.1. This is the same hardware as mentioned in ticket #123, but this issue is minor in comparison and a separate issue so it deserves its own ticket.

During boot, psm0 is installed and finds my mouse as an IntelliMouse?. The actually mouse is a basic Logitech optical 2-button + scrollwheel. The system is connected through a good KVM which switches without dropping the PS/2 connection. I'm sure its not a hardware problem as booting Linux gets a working mouse.

When X comes up at the start of install, there is a mouse cursor in the center of the screen, but it won't move. There is no screen corruption, the chosen mode looks decent, and I can still use the keyboard to navigate the installer. So, this is an annoyance but not critical by any means. I have not yet established whether the mouse works once the system is fully installed as I have not yet completed an install, mostly due to the other previously mentioned ticket.

Change History (2)

comment:1 Changed 7 years ago by mrezny

Further testing indicates this is likely a FreeBSD problem and not a PCBSD problem. Booting FreeBSD 7.0-RELEASE and starting the mouse daemon through sysinstall results in a non-moving cursor in the center of the screen. The mouse is detected the same by FreeBSD in all cases, but does not respond to movement. Solution will follow if found, but this is likely not require action by PCBSD team.

comment:2 Changed 7 years ago by mrezny

  • Resolution set to invalid
  • Status changed from new to closed

Works with USB mouse. The mouse really SHOULD work on PS/2, but for some reason just doesn't. This is FreeBSD's problem and not PCBSD's.

Note: See TracTickets for help on using tickets.