Mailinglist Archive: opensuse (2974 mails)
| < Previous | Next > |
Re:[SLE] losing mouse and keyboard
- From: Jack Reilly <aa6vn@xxxxxxxxxxx>
- Date: Fri, 02 Feb 2001 11:25:04 -0800
- Message-id: <01020211273109.00818@va>
On Thu, 01 Feb 2001, you wrote:
> On Wednesday 31 January 2001 18:19, Jack Reilly wrote:
> > The mouse is a three button Logitech Mouseman. The keyboard is VA LInux
> > oem that appears to be standard. Yast identifies it as type PC 104. The
> > connectors go to PS/2 ports. I neglect to mention that I have two PCs and
> > a mac connected to a Belkin OmniCube for common use of keyboard, mouse, and
> > monitor. The monitor is a NECMultiSync FP950. Both PCs have been running
> > RedHat without any problem.
> >
> It often happens that when the mouse isn't properly configured the x-server
> flips out and kills the keyboard too (sometimes it doesn't even start at all
> 'cos of the mouse), so your keyboard is probably configured properly.
> I don't know the 3-button LM mouse but I know that some of them run the
> config as the MS Intellimouse (mine is that). IMPS/2 protocol and PS/2 mouse
> should have the device configured; /dev/psaux. This is my mouse in the
> /etc/XF86Config file:
> --
> Section "Pointer"
> Protocol "IMPS/2"
> Device "/dev/psaux"
> SampleRate 60
> BaudRate 1200
> ZAxisMapping 4 5
> EndSection
> --
> If you are a Linux newbie and you don't know how to boot up in text mode, or
> change into another virtual desktop to edit your /etc/XF86Config file with
> emacs or vi then let us know.
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
> On Wednesday 31 January 2001 18:19, Jack Reilly wrote:
> > The mouse is a three button Logitech Mouseman. The keyboard is VA LInux
> > oem that appears to be standard. Yast identifies it as type PC 104. The
> > connectors go to PS/2 ports. I neglect to mention that I have two PCs and
> > a mac connected to a Belkin OmniCube for common use of keyboard, mouse, and
> > monitor. The monitor is a NECMultiSync FP950. Both PCs have been running
> > RedHat without any problem.
> >
> It often happens that when the mouse isn't properly configured the x-server
> flips out and kills the keyboard too (sometimes it doesn't even start at all
> 'cos of the mouse), so your keyboard is probably configured properly.
> I don't know the 3-button LM mouse but I know that some of them run the
> config as the MS Intellimouse (mine is that). IMPS/2 protocol and PS/2 mouse
> should have the device configured; /dev/psaux. This is my mouse in the
> /etc/XF86Config file:
> --
> Section "Pointer"
> Protocol "IMPS/2"
> Device "/dev/psaux"
> SampleRate 60
> BaudRate 1200
> ZAxisMapping 4 5
> EndSection
> --
> If you are a Linux newbie and you don't know how to boot up in text mode, or
> change into another virtual desktop to edit your /etc/XF86Config file with
> emacs or vi then let us know.
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
| < Previous | Next > |