cms wrote:
Hello all,
Just received my copy of SuSE 9.2 Pro and completed a clean install on my Toshiba Satellite 2435 laptop. For whatever reason, the laptop's touchpad was not detected/installed correctly. Using the laptop has become extremely difficult. The mouse opens *almost* every window and app that it trails over and hardware clicking/tapping doesn't work. I don't recall what driver I've used in the past with SuSE and this laptop--truth is, I never looked. Currently I'm using the generic PS/2 Mouse (Aux-Port) driver as indicated in the Hardware section of YaST's Control Center and the touchpad is somewhat functional, albeit with irritating side effects. With previous versions of SuSE the touchpad was detected/configured correctly and without my intervention. Anyone using SuSE 9.2 with a similar machine?
Searches on SuSE's Support Portal turned up zero articles related to ALPS Touchpad devices.
This is a snippet of dmesg, related to the mouse/touchpad:
------- SNIP ------- mice: PS/2 mouse device common for all mice input: AT Translated Set 2 keyboard on isa0060/serio0 alps.c: E6 report: 00 00 64 alps.c: E7 report: 73 02 0a alps.c: E6 report: 00 00 64 alps.c: E7 report: 73 02 0a alps.c: Status: 15 01 0a ALPS Touchpad (Glidepoint) detected Disabling hardware tapping alps.c: Status: 11 01 0a input: AlpsPS/2 ALPS TouchPad on isa0060/serio4 input: PC Speaker md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 ------- SNIP -------
Any help or suggestions would be greatly appreciated.
TIA
Chris Shanahan
Ok, some of the bytes alps.c reports are different for me, but the effect is substantially the same. Moving over a button does not *always* auto-click it (or maybe I moved around the button), but my attempts to position to a button using the external mouse and then click on it using the other one often cause the driver to lose it's sync and re-position to the middle of the screen. SuSE call the ALPS driver both for laptops and for desktops, the difference being that the driver decides that it is not responsible for desktops and returns a status of -1. This leaves other modules free to do things correctly. An obvious fix would be to rape the driver (which is not in the standard kernel - it is one of SuSE's patches) to always return -1, but I almost always get compile errors when recompiling the SuSE kernel. Vanilla kernels almost always compile fine. I found a desktop boot log diff at http://www.linux-club.de/viewtopic.php?p=106393 (search for alps.c and go up 10 lines; 9.1 is green and 9.2 is red) and it shows that alps is new. For the record: No-Name laptop, years old running an Intel Tillamook 266 processor. Upgrading it was a total bitch and I ended up having to do it as a new install (after rescuing /etc in the /home tree) and reformatting my /, /usr, /var and /opt partitions. Amusingly, the install process did not bother activating my swap partition and tried to perform an installation with 96MB. The installation process only kick-started after a 'swapon /dev/hda3' performed from screen 2 :-) -- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html