Mailinglist Archive: opensuse (958 mails)

< Previous Next >
Re: [opensuse] Jelly Comb touchpad not working
05.05.2019 4:20, Marc Chamberlin пишет:

cat /proc/bus/input/devices


I: Bus=0003 Vendor=258a Product=6a88 Version=0110
P: Phys=usb-0000:00:14.0-5.1.5/input1

U: Uniq=
H: Handlers=kbd mouse0 event12
B: EV=17
B: KEY=2a000000000 0 1f0000 1000302000000 3838d801d001 1e000000000000 0
B: REL=143
B: MSC=10

shows that is the event assigned to the kbd mouse0  AFAIK

evtest --grab /dev/input/event12
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x258a product 0x6a88 version 0x110
Input device name: "SINO WEALTH USB KEYBOARD"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 113 (KEY_MUTE)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 116 (KEY_POWER)
    Event code 128 (KEY_STOP)
    Event code 140 (KEY_CALC)
    Event code 142 (KEY_SLEEP)
    Event code 143 (KEY_WAKEUP)
    Event code 144 (KEY_FILE)
    Event code 155 (KEY_MAIL)
    Event code 156 (KEY_BOOKMARKS)
    Event code 158 (KEY_BACK)
    Event code 159 (KEY_FORWARD)
    Event code 163 (KEY_NEXTSONG)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 165 (KEY_PREVIOUSSONG)
    Event code 171 (KEY_CONFIG)
    Event code 172 (KEY_HOMEPAGE)
    Event code 173 (KEY_REFRESH)
    Event code 217 (KEY_SEARCH)
    Event code 224 (KEY_BRIGHTNESSDOWN)
    Event code 225 (KEY_BRIGHTNESSUP)
    Event code 240 (KEY_UNKNOWN)
    Event code 272 (BTN_LEFT)
    Event code 273 (BTN_RIGHT)
    Event code 274 (BTN_MIDDLE)
    Event code 275 (BTN_SIDE)
    Event code 276 (BTN_EXTRA)
    Event code 421 (KEY_WORDPROCESSOR)
    Event code 423 (KEY_SPREADSHEET)
    Event code 425 (KEY_PRESENTATION)
  Event type 2 (EV_REL)
    Event code 0 (REL_X)
    Event code 1 (REL_Y)
    Event code 6 (REL_HWHEEL)
    Event code 8 (REL_WHEEL)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Testing ... (interrupt to exit)

Moving my finger on the touchpad or pressing the mouse keys did not
produce any further output...

So this is kernel issue. To be absolutely sure you may try evtest on
another evdev, that corresponds to your keyboard - do not use "--grab"
parameter, you will be unable to use keyboard then (or prepare remote
login where you can kill evtest).

Otherwise you need to look at low level kernel tools to see what
happens. You may try hid-record
( or usbmon as last resort.

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups