wireless mouse not working with terminal

Basically, I have the 20150508 version of Tumbleweed with breeze blocked with ‘zypper al breeze’, blocking the Plasma 5.3 update from the following week. I am shooting for the stability of KDE4 coupled with the new kernel 4. I didn’t like the look of breeze, I didn’t like the new fonts, both kwrite and konsole were broken with the initial update to 15.04. I am trusting zypper to keep all dependencies stable. The greatness of zypper absolutely confirms my choice in using openSUSE as my linux distro. The only thing I did not like about openSUSE was the slowness to update to the newest kernel. Hence my choice of Tumbleweed. If there ever is an official release of openSUSE 13.3, I’d probably switch to that.

My problem probably does not have anything to do with the above; it is with my wireless mouse. It works perfectly with the desktop. I have had trouble with the keyboard freezing on me during command line sessions in the main terminal (ctrl+alt_F1). I finally noticed that it happens everytime I bump my mouse. It seems that it confuses the system when the mouse data has no relevant context to work from. Instead of ignoring the mouse, it seems that the mouse is allowed to clog up the buffer. Obviously mentioning the ‘buffer’ is kind of silly; I don’t know enough about the system to know whether that is really how it works. But I did test it: bumping the mouse always leads to turning off the computer with the hardware power button.

Of course I haven’t tested the mouse with a terminal program that uses the mouse. EMACS?

Tumbelweed has it own forum since the problem could very well be a tumbleweed problem or ist also sounds like youare pushing the kernel version also it could be any combination.Also to make thing more complicated the mouse and key board are both channelled through xorg. thus the video driver has some say in the matter.

Remember that when you ride the cutting edge expect to bleed. :open_mouth:

My advise take this to the tumbleweed section and mention all drivers and hardware video related.

A normal 13.2 install does not appear to have this weird problem

Hi
Temporarily closed and moving to correct forum.

Hi
Moved and re-opened…enjoy.

Which parts of the forum am I allowed to post to?

Can I be pushing the kernel if I only use openSUSE repositories with zypper and install all dependencies? I want a more up-to-date kernel than is standard in 13.2. That doesn’'t mean I have installed a kernel beyond the Tumbleweed oss if that is what is what you think.

I have bash 4.3 and kernel-desktop 4.0.4. This is on an HP ENVY 23. What is xorg and how is it related to bash? I don’t know which drivers to mention, but this is a start:

linux-lo2y:~ # lspci -nnk | grep -A4 VGA          
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)
        DeviceName:  Onboard IGD
        Subsystem: Hewlett-Packard Company Device [103c:2b1b]
        Kernel driver in use: i915
        Kernel modules: i915


OK, so obviously this is a hardware issue and has nothing whatsoever to do with the fact I am using Tumbleweed. The kind of person who can help me is more likely to visit the Hardware part of the forum. I am in the wrong place. So does anyone know how the system intercepts mouse messages while using the terminal?

Hard to tell with the information provided so far. You could test with a live distro to eliminate kernel differences for example.

The kind of person who can help me is more likely to visit the Hardware part of the forum.

Well, I check ‘Today’ Posts’ and ‘New Posts’ (as i suspect many others do), so see all sub-forums.

I am in the wrong place.

You need to demonstrate to us that this is not TW-specific. TW uses bleeding-edge Xorg libraries and kernel versions. It’s really a testing ground, and it doesn’t always play nice with certain hardware.

So does anyone know how the system intercepts mouse messages while using the terminal?

How about telling us more info about the mouse and keyboard? Are the mouse and keyboard both wireless? And if so connected via same dongle? Or Bluetooth?

/usr/sbin/hwinfo --mouse
usb-devices
xinput list

If you compare it to other rolling distros, I don’t think TW is bleeding edge. I don’t think I should have been moved until people asked me for more relevant info. I can’t demonstrate anything without knowing what the problem is. Being criticized for posting in the wrong place is not help. And yes I immediately felt that I had been taken away from the place were I could get the best information. I don’t think I am the only person who should be expected to demonstrate that they are right. Is xorg really a word? I’ll answer your question after I’ve gotten some rest.

I’m not getting into an argument about that, but you need to accept that it was a moderator decision, and that we prefer to use use the TW forum for such posts.

Is xorg really a word? I’ll answer your question after I’ve gotten some rest.

Good idea. We all need rest. I’ll leave you to learn more about X.Org (colloquy xorg and other variations)

BTW, you haven’t’ supplied the requested information (ref post #7). You’re unlikely to get the help you need if you don’t answer peoples requests. Keep the posts constructive, otherwise you’re at risk of driving away those that may be able to advise further.

32: USB 00.2: 10503 USB Mouse
  [Created at usb.122]
  Unique ID: 634B.FOweNqV8oSF
  Parent ID: uIhY.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2
  SysFS BusID: 3-3:1.2
  Hardware Class: mouse
  Model: "Jing-Mold Enterprise HP Wireless Keyboard Kit"
  Hotplug: USB
  Vendor: usb 0x05af "Jing-Mold Enterprise Co., Ltd"
  Device: usb 0x0702 "HP Wireless Keyboard Kit"
  Revision: "1.04"
  Compatible to: int 0x0200 0x0001 "Generic USB Mouse"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Speed: 12 Mbps
  Module Alias: "usb:v05AFp0702d0104dc00dsc00dp00ic03isc01ip02in02"
  Driver Info #0:
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #29 (Hub)


OK, the thing that jumps out for me is ‘Enterprise HP Wireless Keyboard Kit’. As little as I understand any of that, it means that the keyboard and the mouse share the same driver? And there I see ‘GPM Protocol: exps2’ and gpm is a program that is supposed to allow the mouse to be used in the terminal. Sorry I gotta go. I’ll have to run xinput and usb devices much later.

OK, the thing that jumps out for me is ‘Enterprise HP Wireless Keyboard Kit’. As little as I understand any of that, it means that the keyboard and the mouse share the same driver?

Yes, you have a single receiver dongle (sometimes referred to as a ‘unfying receiver’) supported by the usbhid driver, but there are other drivers involved that specifically handle the keyboard and mouse operation within Xorg.

What does the following report?

/usr/sbin/hwinfo --keyboard

It would be useful to know whether an older openSUSE version operates correctly with this hardware, in case a regression is evident. It might be the case that a bug report is warranted.

This is not a bad problem to me. If I am on the terminal side of things and I accidentally bump the mouse, which I am not using and don’t need at that point anyway, the keyboard stops responding so I can’t ctrl+alt+f7 and get back to the desktop, so I have no recourse but to press the power button. At which point I marvel once again at how smoothly and quickly openSUSE can reboot.:stuck_out_tongue:

The mouse does probably continue to send signals to the computer even when one is using the terminal. This problem begs the question: 'How does the operating system normally handle those signals silently behind the scenes even while we are just using the terminal and don’t even need the mouse. I am wondering if someone may have thought I was talking about when I am using the console. No, no problems while running any programs on the desktop. There the mouse has a function and it functions normally.

15: USB 00.0: 10800 Keyboard
  [Created at usb.122]
  Unique ID: CiZ2.KkrEjjM9ExA
  Parent ID: uIhY.2DFUsyrieMD
  SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0
  SysFS BusID: 3-3:1.0
  Hardware Class: keyboard
  Model: "Jing-Mold Enterprise HP Wireless Keyboard Kit"
  Hotplug: USB
  Vendor: usb 0x05af "Jing-Mold Enterprise Co., Ltd"
  Device: usb 0x0702 "HP Wireless Keyboard Kit"
  Revision: "1.04"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Speed: 12 Mbps
  Module Alias: "usb:v05AFp0702d0104dc00dsc00dp00ic03isc01ip01in00"
  Driver Info #0:
    XkbRules: xfree86
    XkbModel: pc104
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #14 (Hub)

31: PS/2 00.0: 10800 Keyboard
  [Created at input.226]
  Unique ID: nLyy.+49ps10DtUF
  Hardware Class: keyboard
  Model: "AT Translated Set 2 keyboard"
  Vendor: 0x0001 
  Device: 0x0001 "AT Translated Set 2 keyboard"
  Compatible to: int 0x0211 0x0001
  Device File: /dev/input/event0
  Device Files: /dev/input/event0, /dev/input/by-path/platform-i8042-serio-0-event-kbd
  Device Number: char 13:64
  Driver Info #0:
    XkbRules: xfree86
    XkbModel: pc104
  Config Status: cfg=no, avail=yes, need=no, active=unknown


The only thing I see is the confirmation that both use Jing Mold Enterprise HP Wireless Keyboard Kit and that the keyboard gets 15 and 31 and the mouse gets 32.

‘xinput list’ responds with ‘unable to connect to X server’.

linux-lo2y:~ # usb-devices | egrep -i -B3 -A4 'hewlett|broadcom|ilitek'
T:  Bus=03 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#=  7 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=222a ProdID=006a Rev=00.01
S:  Manufacturer=ILITEK
S:  Product=ILITEK Multi-Touch
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=200mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

T:  Bus=03 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=32 #Cfgs=  1
P:  Vendor=05af ProdID=0702 Rev=01.04
S:  Manufacturer=Hewlett Packard
S:  Product=HP Wireless Keyboard Kit                                                                                                   
C:  #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=100mA                                                                                                 
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid                                                                   
I:  If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid                                                                   
--
T:  Bus=03 Lev=01 Prnt=01 Port=05 Cnt=04 Dev#=  4 Spd=480 MxCh= 0                                                                      
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1                                                                           
P:  Vendor=0e8d ProdID=1887 Rev=00.00                                                                                                  
S:  Manufacturer=Hewlett-Packard Company
S:  Product=HP External USB Optical Drive                                                                                              
S:  SerialNumber=KZ2E4S90826                                                                                                           
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA                                                                                                 
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=02 Prot=50 Driver=usb-storage
--
T:  Bus=03 Lev=01 Prnt=01 Port=07 Cnt=05 Dev#=  5 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0a5c ProdID=21f1 Rev=01.12
S:  Manufacturer=Broadcom Corp
S:  Product=BCM20702A0
S:  SerialNumber=18CF5EAFB91F
C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
linux-lo2y:~ # 


That is most of the manufacturers except for the webcam, pny usb-stick, and Linux 4.0.4-2 desktop xhci-hcd

I just notice that everything relevant is on Bus 03, so this is all of Bus 03:

linux-lo2y:~ # usb-devices | egrep -i -A8 Bus=03
T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh=14
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=04.00
S:  Manufacturer=Linux 4.0.4-2-desktop xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=0000:00:14.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=03 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#=  7 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=222a ProdID=006a Rev=00.01
S:  Manufacturer=ILITEK
S:  Product=ILITEK Multi-Touch
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=200mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid

T:  Bus=03 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=32 #Cfgs=  1
P:  Vendor=05af ProdID=0702 Rev=01.04
S:  Manufacturer=Hewlett Packard
S:  Product=HP Wireless Keyboard Kit
C:  #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
I:  If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
I:  If#= 2 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
--
T:  Bus=03 Lev=01 Prnt=01 Port=04 Cnt=03 Dev#=  3 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=154b ProdID=007a Rev=11.00
S:  Manufacturer=PNY Technologies
S:  Product=USB 2.0 FD
S:  SerialNumber=AEC10H09YE11002205
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=200mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

T:  Bus=03 Lev=01 Prnt=01 Port=05 Cnt=04 Dev#=  4 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0e8d ProdID=1887 Rev=00.00
S:  Manufacturer=Hewlett-Packard Company
S:  Product=HP External USB Optical Drive
S:  SerialNumber=KZ2E4S90826         
C:  #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=02 Prot=50 Driver=usb-storage

T:  Bus=03 Lev=01 Prnt=01 Port=07 Cnt=05 Dev#=  5 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=0a5c ProdID=21f1 Rev=01.12
S:  Manufacturer=Broadcom Corp
S:  Product=BCM20702A0
S:  SerialNumber=18CF5EAFB91F
C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
--
T:  Bus=03 Lev=01 Prnt=01 Port=08 Cnt=06 Dev#=  6 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=04f2 ProdID=b454 Rev=69.40
S:  Manufacturer=Chicony Electronics Co., Ltd.
S:  Product=HP High Definition 1MP Webcam
C:  #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
I:  If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo

linux-lo2y:~ # 


Simply removing the dongle and re-plugging doesn’t help in that situation?

I’ve just noticed something unusual about your hwinfo output. Normally, I’d expect to see unique device files for attached input devices. Your wireless keyboard and mouse devices don’t seem to have that. Mis-handled by the usbhid driver I suspect.

For reference, I’ve just attached a Logitech wireless keyboard and mouse attached via a single ‘unifying’ receiver (Logitech USB Receiver).

The keyboard is reported like this

# hwinfo --keyboard
21: USB 00.0: 10800 Keyboard                                    
  [Created at usb.122]
  Unique ID: ZmS7.Ze5SG2POyjB
  Parent ID: 7eqy.gkSaZmjGyhD
  SysFS ID: /devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0
  SysFS BusID: 6-1:1.0
  Hardware Class: keyboard
  Model: "Logitech USB Receiver"
  Hotplug: USB
  Vendor: usb 0x046d "Logitech, Inc."
  Device: usb 0xc52e "USB Receiver"
  Revision: "15.00"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Device File: /dev/input/event10
  Device Files: /dev/input/event10, /dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd, /dev/input/by-path/pci-0000:00:1d.1-usb-0:1:1.0-event-kbd
  Device Number: char 13:74
  Speed: 12 Mbps
  Module Alias: "usb:v046DpC52Ed1500dc00dsc00dp00ic03isc01ip01in00"
  Driver Info #0:
    XkbRules: xfree86
    XkbModel: pc104
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #20 (Hub)

The mouse is reported like this

# hwinfo --mouse
42: USB 00.1: 10503 USB Mouse                                   
  [Created at usb.122]
  Unique ID: 0yiB.b0ZOFsTpR64
  Parent ID: 7eqy.gkSaZmjGyhD
  SysFS ID: /devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.1
  SysFS BusID: 6-1:1.1
  Hardware Class: mouse
  Model: "Logitech USB Receiver"
  Hotplug: USB
  Vendor: usb 0x046d "Logitech, Inc."
  Device: usb 0xc52e "USB Receiver"
  Revision: "15.00"
  Compatible to: int 0x0210 0x0038
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Device File: /dev/input/mice (/dev/input/mouse1)
  Device Files: /dev/input/mice, /dev/input/mouse1, /dev/input/event11, /dev/input/by-id/usb-Logitech_USB_Receiver-if01-event-mouse, /dev/input/by-path/pci-0000:00:1d.1-usb-0:1:1.1-event-mouse, /dev/input/by-id/usb-Logitech_USB_Receiver-if01-mouse, /dev/input/by-path/pci-0000:00:1d.1-usb-0:1:1.1-mouse
  Device Number: char 13:63 (char 13:33)
  Speed: 12 Mbps
  Module Alias: "usb:v046DpC52Ed1500dc00dsc00dp00ic03isc01ip02in01"
  Driver Info #0:
    Buttons: 8
    Wheels: 3
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #40 (Hub)

They have separate device files.

So, I’m defintely inclined to lean towards a driver bug here.

There is no dongle, like the webcam, it is internal to the computer. HP Envy 23 all-in-one. I don’t know if this is typical of all-in-ones instead of desktops, but although it is usb wireless as opposed to bluetooth or wifi, there is nothing plugged into a usb jack. My pny usb drive which contains my original TW dvd distro and my optical drive are using usb jacks, but the wireless keyboard is hardwired into usb internally. No doubt it is meant to be transparent to the user and would have been if nothing went wrong. But if it had been wifi or bluetooth, I probably would not have been able to install openSUSE on my computer. Broadcom was the biggest challenge. The wifi drivers did not work at first.

On 2015-06-09 15:36, susedevfan wrote:

> OK, the thing that jumps out for me is ‘Enterprise HP Wireless Keyboard
> Kit’. As little as I understand any of that, it means that the keyboard
> and the mouse share the same driver? And there I see ‘GPM Protocol:
> exps2’ and gpm is a program that is supposed to allow the mouse to be
> used in the terminal. Sorry I gotta go. I’ll have to run xinput and usb
> devices much later.

Stop the gpm service, then find out if moving the mouse crashes the system.

Some mouse drivers convert mouse movements to keypresses (or emulate
them). If this is so, disabling ‘gpm’ would stop the conversion. If it
works, my guess is that you are using the wrong mouse type in the gpm
config.


Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))

You’re gettting hung up on the terminology. A proprietary wireless receiver is involved, and it is connected to the USB bus, just as the Logitech device I attached was. Internal, external is irrelevant. The usbhid driver is almost certainly mishandling this device. It is the device driver. The X-server uses evdev as a device handler, while the kernel has other keyboard and mouse drivers (event handlers) for console communication.

This will tell us a bit more about the event handler(s) tied to the hardware

cat /proc/bus/input/devices