On Friday 02 February 2001 17:54, Jack Reilly wrote:

After using linux a couple of years I was beginning to feel like I was emerging from the newbie category but this problem with Suse has me right back there. I tried using your config and some variations as well, But all I get is a mouse that keeps returning to the lower left corner of the screen so is not usable. Then I tried another mouse. It's a MS mouse port compatible 2.1A. With the BIOS USB IRQ enabled I got by the correction in the desktop test ok. Then I opened Netscape, got to the Suse site and moved around a bit. But when I tried to enlarge the small window I lost the mouse and the kb. When I turn power off and on to reboot I usually end up with "fsck failed" mess which I don't want to tackle so have to repeat the install. This time the reboot went ok and in "dmesg" I see some lines I haven't noticed before:

usb-uhci.c: Intel USB controller: setting latency timer to zero. usb-uhci.c: USB UHCI at I/O 0xd400, IRQ5 usb-uhci.c: Detected 2 ports usn.c: new USB bus registered, assigned bus number 1 usb.c: USB hub found usb.c: 2 ports detected

In the meantime the Red Hat machine and the mac go along fine and don't care what mouse I use.

Jack Phew....this really sounds spooky and goes way by the few cells I got left in my head. When I was poking around in another SuSE box today I ran into this wheel-mouse README file included in a imwheel package from Freshmeat, in the Installation part it mentions your mouse. I can send you the whole file if you think it can be of any help. Here's the Installation part.

Cheers, ei --- Installation """""""""""" configure --help configure (and any options you want to set) make make install The mouse must be setup in XF86Config to send the mouse buttons 4 and 5 for wheel actions. To do this: [ METHOD #1 : XGrabButton ] 1) edit /etc/XF86Config with your favorite editor (I suggest vim! It's crunchy) a. add the following line to the "Pointer" section. for 1 wheel: ZAxisMapping 4 5 for two wheels or a stick: ZAxisMapping 4 5 6 7 b. Make sure your Protocol is set to either "IMPS/2" for a PS/2 mouse or for serial mice set it to "IntelliMouse" or "Auto". It should work for the following mice, which have wheels, knobs, or buttons that are mappable with ZAxisMapping (according to XFree86 documentation): ASCII (serial, PS/2) Genius NetScroll (PS/2) Genius NetMouse and NetMouse Pro (serial, PS/2) Logitech MouseMan+ and FirstMouse+ (serial, PS/2) Half functionality may be obtained from the following mice that have at least a fourth button capability: ALPS Glide-Point (serial, PS/2) ('Tapping' is button 4) The half functionality will only go up and left, unless you include the -4 option on the command-line. c. Here's my current setup for an example of a PS/2 Intellimouse: Section "Pointer" Protocol "IMPS/2" #change for your mouse type. Device "/dev/psaux" #change for your device. BaudRate 1200 #This is probably not needed! Resolution 100 #And neither is this! ZAxisMapping 4 5 #This is necessary! Buttons 3 #Use this instead of Emulate3 stuff! EndSection d. Restart XWindows if you need to! 2) make 3) make install This will currently install to /usr/local/bin, so edit the Makefile to change this behavior. Don't forget to choose whether you want imwheel to be setuid root. This is required for any users who need to use imwheel and the pidfile stuff to track running imwheels. 4) After XWindows is started run imwheel like this: imwheel -k imwheel will automatically background itself this way. I added the -k to force any old imwheel processes to stop. This will not cause imwheel to die if there are no previous imwheels. XFree86 Settings: Make sure Emulate3 phrases are either deleted or commented out to use the wheel button as the middle button(2), and then the right button is button 3. STUPID FACT: Obviously this method can be used for a real 5(+) button mouse as well...but why?! The 4th and 5th buttons may be used as if they were the wheel rolling up and down, but this will remove the regular functionality of the 4th and 5th buttons, unless you "exclude" the windows in which you need the 4th and 5th buttons. [ METHOD #2 : wheel fifo ] This method is REQUIRED for Accelerated-X or any other server without wheel mouse support built in. It is also the recommended method by me! This method will currently support ONLY the ps/2 Intellipoint Mice, not the serial version, nor any other mice for that fact...unless you want to add support in gpm yourself or send me a mouse so that I can implement it in gpm. To add a new mouse to this method no change to imwheel is required. 1) Edit /etc/XF86Config with your favorite editor (I suggest vim! It's crunchy) OR use XF86Setup. That's easier! b. Make sure your Protocol is set to "MouseSystems" Mouse support is dependent on gpm. Right now I KNOW imps2 works! others that may work for you include mm+ps2, marblefx, pcnps2, and ms3. try others if these don't work or another matches your mouse better. c. Here's my current setup for an example of a PS/2 Intellimouse: Section "Pointer" Protocol "MouseSystems" #gpm -R is MouseSystems! Device "/dev/gpmdata" #this is the gpm -R output BaudRate 1200 #works for me... Resolution 100 #i dunno...works again! Buttons 3 #use this,it's better than Emulate3! #if you set this higher...more #configuration is REQUIRED EndSection d. Restart XWindows if you need to! 2) make 3) make install This will currently install to /usr/local/bin, so edit the Makefile to change this behavior. if you want ALL the gpm stuff enter that directory and "make install" there. The usual install only installs the gpm executable. Don't forget to choose whether you want imwheel to be setuid root. This is required for any users who need to use imwheel and the pidfile stuff to track running imwheels. 4) After XWindows is started run : imwheel -k --wheel-fifo imwheel will automatically background itself this way. I added the -k to force any old imwheel processes to stop. This will not cause imwheel to die if there are no previous imwheels. NOTE: the @Exclude command has no bearing in this method, and is ignored. mainly because by excluding a window in this method there is nothing sent to the window for the wheel, whereas in the other mode exclusion turns off the button grabbing and allows the usual button 4 and 5 events again for those clients that either need to grab all the buttons or want to receive the buttons 4 and/or 5 for their own purposes. --- -- @~~ EagleIce ~ gnu4u@linux.nu ~~@ @~~ Running GNU/Linux & KDE ~~@