|
Bugzilla – Full Text Bug Listing |
| Summary: | Laptop additional mice not found/used | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Jonathon Robison <jrobiso2> |
| Component: | SaX2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED WORKSFORME | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jonathon Robison
2005-08-17 14:37:09 UTC
please call from runlevel as user root with all mice connected: sax2 -r 1) are all mice working ? 2) what are the contents of /var/log/SaX.log 3) what does hwinfo --mouse tell you ? Here is what hwinfo --mouse shows: (it's 100% correct, by the way)
Jons:~ # hwinfo --mouse
15: USB 00.0: 10503 USB Mouse
[Created at usb.122]
Unique ID: ADDn.R9wUZ167351
Parent ID: k4bc.f9i7qR3Y7n3
SysFS ID: /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0
SysFS BusID: 1-1:1.0
Hardware Class: mouse
Model: "Logitech Optical USB Mouse"
Hotplug: USB
Vendor: usb 0x046d "Logitech Inc."
Device: usb 0xc016 "Optical USB Mouse"
Revision: "3.40"
Compatible to: int 0x0210 0x0013
Driver: "usbhid"
Device File: /dev/input/mice (/dev/input/mouse2)
Device Number: char 13:63 (char 13:34)
Speed: 1.5 Mbps
Driver Info #0:
Buttons: 3
Wheels: 1
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #14 (Hub)
20: PS/2 00.0: 10500 PS/2 Mouse
[Created at input.140]
Unique ID: AH6Q.fU1aO9YHBB4
Hardware Class: mouse
Model: "DualPoint Stick"
Vendor: int 0x0212
Device: int 0x0002 "DualPoint Stick"
Compatible to: int 0x0210 0x0003
Device File: /dev/input/mice (/dev/input/mouse0)
Device Number: char 13:63 (char 13:32)
Driver Info #0:
Buttons: 3
Wheels: 0
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
21: PS/2 00.0: 10500 PS/2 Mouse
[Created at input.140]
Unique ID: AH6Q.fU1aO9YHBB4
Hardware Class: mouse
Model: "AlpsPS/2 ALPS DualPoint TouchPad"
Vendor: int 0x0212
Device: int 0x0002 "AlpsPS/2 ALPS DualPoint TouchPad"
Compatible to: int 0x0210 0x0003
Device File: /dev/input/mice (/dev/input/mouse1)
Device Number: char 13:63 (char 13:33)
Driver Info #0:
Buttons: 3
Wheels: 0
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Jons:~ #
However, as it stands, none of these are on the lists that YaST2 shows me, the
Glidepoint won't work, and neither does the Dell Optical USB mouse. Lastly, the
touchpad is so sensative I cannot get anything much done.
/var/log/Sax.log is small and only has info from first boot, apparantly.
I'll try the sax2 -r and get back to here.
Doing Sax2 -r in runlevel 3 seems to have worked. I now have all 3 possbilities available to me - touchpad (which I would still like to kill), glidepoint, and USB optical wheel mouse. Any idea why this did not get configured correctly during installation? Hmm I did a test installation on my Notebook here with a touchpad and a external USB mouse which is very much the same setup as you have I think. It works for me as it should. Some words to explain that: 1) calling sax2 -r means "start from scratch" which is the same as the suggestion made in YaST while installing so in the later installed system the configuration should be the same. The fact that the SaX.log is small points out that you have called sax2 again within the installed system which makes it not easy to see what happened during installation 2) the touchpad is not fully supported during installation, it is used in failsafe mode to not influence the installation in a negative way. This is because the touchpad drivers may under certain condition prevent the X-Server from setting up a core pointer which is very bad. As result while installing all connected USB and PS/2 devices should work in 3Button + Wheel mode which they did in my test 3) the configuration in full featured mode for the touchpad will be included using a SaX2 profile. This profile has been provided by our laptop guys and defines a setup "most" like to use. I'm sorry that this default setup doesn't fit your needs but currently there is no special touchpad dialog to configure this special device. |