[RESOLVED] my sayodevice is being recognized as mouse(?)

Nikorasu82 · 2025-07-21 20:40:10

So after some updates i was doing without checking for more than a week, I started noticing that my keypad wasnt working anymore, when i use lsusb they show up and i assume theres no error message there

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 30fa:0400 USB Optical Mouse
Bus 001 Device 064: ID 8089:0009 SayoDevice Nikorasu's devi
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 256c:006e HUION 420
Bus 005 Device 003: ID 320f:50dc USB Keyboard
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

but when i use journalctl -p 3 -b this shows up

[ 780.496319] usb 1-2: USB disconnect, device number 41
[ 780.976743] usb 1-2: new high-speed USB device number 42 using xhci_hcd
[ 781.592870] usb 1-2: unable to read config index 0 descriptor/all
[ 781.592878] usb 1-2: can't read configurations, error -71
[ 781.976090] usb 1-2: new high-speed USB device number 43 using xhci_hcd
[ 782.359039] usb 1-2: device descriptor read/64, error -71
[ 782.871599] usb 1-2: New USB device found, idVendor=8089, idProduct=0009, bcdDevice= 0.76
[ 782.871606] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 782.871609] usb 1-2: Product: Nikorasu's devi
[ 782.871611] usb 1-2: Manufacturer: SayoDevice
[ 782.871614] usb 1-2: SerialNumber: 03E61333A714542D0F39E339E300
[ 782.893832] input: SayoDevice Nikorasu's devi as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/usb1/1-2/1-2:1.0/0003:8089:0009.00FB/input/input731
[ 782.980175] hid-generic 0003:8089:0009.00FB: input,hidraw5: USB HID v1.10 Keyboard [SayoDevice Nikorasu's devi] on usb-0000:02:00.0-2/input0
[ 782.989942] input: SayoDevice Nikorasu's devi as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/usb1/1-2/1-2:1.1/0003:8089:0009.00FC/input/input733
[ 782.990077] input: SayoDevice Nikorasu's devi as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/usb1/1-2/1-2:1.1/0003:8089:0009.00FC/input/input734
[ 782.990210] input: SayoDevice Nikorasu's devi Keyboard as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/usb1/1-2/1-2:1.1/0003:8089:0009.00FC/input/input735
[ 783.041137] input: SayoDevice Nikorasu's devi Mouse as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/usb1/1-2/1-2:1.1/0003:8089:0009.00FC/input/input736
[ 783.041453] hid-generic 0003:8089:0009.00FC: input,hiddev98,hidraw6: USB HID v1.11 Keyboard [SayoDevice Nikorasu's devi] on usb-0000:02:00.0-2/input

I just started using linux a month ago, I hope I can fix that
Linux 6.15.7-arch1-1 x86_64
Hyprland 0.50.1

Last edited by Nikorasu82 (2025-07-22 06:34:33)

gromit · 2025-07-21 20:42:25

Since when is this the case? Do you also see this behavior when using the linux-lts kernel?

Nikorasu82 · 2025-07-21 21:01:27

gromit wrote:

Since when is this the case? Do you also see this behavior when using the linux-lts kernel?

Im not entirely sure since i wasnt using my keypad for a week or so, but I believe it started after 17th
and I don't know about lts

gromit · 2025-07-21 21:06:52

Which packages did you upgrade around the 17th? Please post the relevant snippet from your pacman.log

seth · 2025-07-21 21:14:07

Just to be clear, the device shows up as keyboard AND mouse (which isn't uncommon and at least https://www.amazon.de/BTXETUEL-OSU-Tast … 4YGD9?th=1 seems to have a dial)
That's however after some initial protocol errors and google has no hits for "Nikorasu's devi" - is this the result of some botched OCR or is that actually how the device registers?
Do you still have access to older journals when the device worked as expected ("sudo journalctl -b 10" for ten boots ago)

Is this a built-in device or cable wired, does it start to respond when re-attaching it after the boot?
Also about the "not works" part: does it still generate input in "sudo evtest"?

Nikorasu82 · 2025-07-21 21:21:10

seth wrote:

Just to be clear, the device shows up as keyboard AND mouse (which isn't uncommon and at least https://www.amazon.de/BTXETUEL-OSU-Tast … 4YGD9?th=1 seems to have a dial)
That's however after some initial protocol errors and google has no hits for "Nikorasu's devi" - is this the result of some botched OCR or is that actually how the device registers?
Do you still have access to older journals when the device worked as expected ("sudo journalctl -b 10" for ten boots ago)
Is this a built-in device or cable wired, does it start to respond when re-attaching it after the boot?
Also about the "not works" part: does it still generate input in "sudo evtest"?

Nikorasu's devi is the way i called it before I got to linux

i should have it i dont usually clear my logs

and its cable wired and it doesnt work as it should (only thing it does is mess up with my cam in some games :v)

Edit:journalctl 10 shows this

Jul 06 19:47:33 Tetosupremacy kernel: irq 7: nobody cared (try booting with the "irqpoll" option)
Jul 06 19:47:33 Tetosupremacy kernel: CPU: 5 UID: 0 PID: 0 Comm: swapper/5 Not tainted 6.15.4-arch2-1 #1 PREEMPT(full) bf56011d6043294f437da1888a30a6d02e6dd116
Jul 06 19:47:33 Tetosupremacy kernel: Hardware name: MANCER MCR-A520M-DXV4/MCR-A520M-DXV4, BIOS 5.17 08/08/2024
Jul 06 19:47:33 Tetosupremacy kernel: Call Trace:
Jul 06 19:47:33 Tetosupremacy kernel: <IRQ>
Jul 06 19:47:33 Tetosupremacy kernel: dump_stack_lvl+0x5d/0x80
Jul 06 19:47:33 Tetosupremacy kernel: __report_bad_irq+0x35/0xa7
Jul 06 19:47:33 Tetosupremacy kernel: note_interrupt.cold+0x28/0x66
Jul 06 19:47:33 Tetosupremacy kernel: handle_irq_event+0x72/0x80
Jul 06 19:47:33 Tetosupremacy kernel: handle_fasteoi_irq+0x7a/0x220
Jul 06 19:47:33 Tetosupremacy kernel: __common_interrupt+0x41/0xa0
Jul 06 19:47:33 Tetosupremacy kernel: common_interrupt+0x80/0xa0
Jul 06 19:47:33 Tetosupremacy kernel: </IRQ>
Jul 06 19:47:33 Tetosupremacy kernel: <TASK>
Jul 06 19:47:33 Tetosupremacy kernel: asm_common_interrupt+0x26/0x40
Jul 06 19:47:33 Tetosupremacy kernel: RIP: 0010:cpuidle_enter_state+0xbb/0x410
Jul 06 19:47:33 Tetosupremacy kernel: Code: 00 00 e8 f8 d6 0c ff e8 83 f1 ff ff 48 89 c5 0f 1f 44 00 00 31 ff e8 a4 48 0b ff 45 84 ff 0f 85 33 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 7c 01 00 00 49 63 ce 48 2b 2c 24 48 6b d1 68 48 89
Jul 06 19:47:33 Tetosupremacy kernel: RSP: 0018:ffffce42801afe78 EFLAGS: 00000246
Jul 06 19:47:33 Tetosupremacy kernel: RAX: ffff8a0a9c06f000 RBX: 0000000000000003 RCX: 0000000000000000
Jul 06 19:47:33 Tetosupremacy kernel: RDX: 0000000051f3c944 RSI: fffffffd41c083b5 RDI: 0000000000000000
Jul 06 19:47:33 Tetosupremacy kernel: RBP: 0000000051f3c944 R08: 0000000000000000 R09: 000000000000000f
Jul 06 19:47:33 Tetosupremacy kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8a0700f3f000
Jul 06 19:47:33 Tetosupremacy kernel: R13: ffffffff913faa80 R14: 0000000000000002 R15: 0000000000000000
Jul 06 19:47:33 Tetosupremacy kernel: ? cpuidle_enter_state+0xac/0x410
Jul 06 19:47:33 Tetosupremacy kernel: cpuidle_enter+0x31/0x50
Jul 06 19:47:33 Tetosupremacy kernel: do_idle+0x1b1/0x210
Jul 06 19:47:33 Tetosupremacy kernel: cpu_startup_entry+0x29/0x30
Jul 06 19:47:33 Tetosupremacy kernel: start_secondary+0x119/0x140
Jul 06 19:47:33 Tetosupremacy kernel: common_startup_64+0x13e/0x141
Jul 06 19:47:33 Tetosupremacy kernel: </TASK>
Jul 06 19:47:33 Tetosupremacy kernel: handlers:
Jul 06 19:47:33 Tetosupremacy kernel: [<0000000044cbee21>] amd_gpio_irq_handler
Jul 06 19:47:33 Tetosupremacy kernel: Disabling IRQ #7
Jul 06 19:47:33 Tetosupremacy kernel: input: SayoDevice Nikorasu's devi Mouse as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/usb1/1-2/1-2:1.1/0003:8089:0009.0005/input/input14
Jul 06 19:47:33 Tetosupremacy kernel: hid-generic 0003:8089:0009.0005: input,hiddev97,hidraw4: USB HID v1.11 Keyboard [SayoDevice Nikorasu's devi] on usb-0000:02:00.0-2/input1

which is weird it started on the 6th, cause i remember playing with Sayo

Last edited by Nikorasu82 (2025-07-21 21:28:41)

Nikorasu82 · 2025-07-21 21:21:57

gromit wrote:

Which packages did you upgrade around the 17th? Please post the relevant snippet from your pacman.log

is there any way other than copying it by vim? i cant copy the logs there

seth · 2025-07-21 21:36:01

sudo journalctl -b -10 | curl -F 'file=@-' 0x0.st

The error concerns your CPU idling, it's probably not related to the input device.

Did you try to re-attach it after the system has booted and checked whether it still produces evtest input?

Nikorasu's devi is the way i called it before I got to linux

Should have checked your nick
Sanity check: is there a parallel windows installation?

Nikorasu82 · 2025-07-21 21:39:46

seth wrote:

sudo journalctl -b -10 | curl -F 'file=@-' 0x0.st
The error concerns your CPU idling, it's probably not related to the input device.
Did you try to re-attach it after the system has booted and checked whether it still produces evtest input?
Nikorasu's devi is the way i called it before I got to linux
Should have checked your nick
Sanity check: is there a parallel windows installation?

about the evtest input, when i tried running sudo evtest in terminal it says command not found
And I dont have a parallel windows installation, I fully changed to arch (well atleast it doesnt show up on bootloader)

Edit: forgot to mention im trying to fix that before coming here for around 15 hours or so, i noticed it on 2 am ;-;

Last edited by Nikorasu82 (2025-07-21 21:44:32)

seth · 2025-07-21 21:44:50

https://archlinux.org/packages/extra/x86_64/evtest/

seth, couple of times wrote:

Did you try to re-attach it after the system has booted

Nikorasu82 · 2025-07-21 21:54:47

seth wrote:

https://archlinux.org/packages/extra/x86_64/evtest/
thanks
seth, couple of times wrote:
Did you try to re-attach it after the system has booted

after testing evtest dont know if this changes something but before restarting it was listed as device 13 and now it became 28
evtest result: Testing ... (interrupt to exit)
expected 24 bytes, got -1

evtest: error reading: No such device
Edit: sometimes it dissapears from evtest, but when i use lsusb it shows up again (still not working tho)

and just to be sure:
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x8089 product 0x9 version 0x110
Input device name: "SayoDevice Nikorasu's devi"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 1 (KEY_ESC)
Event code 2 (KEY_1)
Event code 3 (KEY_2)
Event code 4 (KEY_3)
Event code 5 (KEY_4)
Event code 6 (KEY_5)
Event code 7 (KEY_6)
Event code 8 (KEY_7)
Event code 9 (KEY_8)
Event code 10 (KEY_9)
Event code 11 (KEY_0)
Event code 12 (KEY_MINUS)
Event code 13 (KEY_EQUAL)
Event code 14 (KEY_BACKSPACE)
Event code 15 (KEY_TAB)
Event code 16 (KEY_Q)
Event code 17 (KEY_W)
Event code 18 (KEY_E)
Event code 19 (KEY_R)
Event code 20 (KEY_T)
Event code 21 (KEY_Y)
Event code 22 (KEY_U)
Event code 23 (KEY_I)
Event code 24 (KEY_O)
Event code 25 (KEY_P)
Event code 26 (KEY_LEFTBRACE)
Event code 27 (KEY_RIGHTBRACE)
Event code 28 (KEY_ENTER)
Event code 29 (KEY_LEFTCTRL)
Event code 30 (KEY_A)
Event code 31 (KEY_S)
Event code 32 (KEY_D)
Event code 33 (KEY_F)
Event code 34 (KEY_G)
Event code 35 (KEY_H)
Event code 36 (KEY_J)
Event code 37 (KEY_K)
Event code 38 (KEY_L)
Event code 39 (KEY_SEMICOLON)
Event code 40 (KEY_APOSTROPHE)
Event code 41 (KEY_GRAVE)
Event code 42 (KEY_LEFTSHIFT)
Event code 43 (KEY_BACKSLASH)
Event code 44 (KEY_Z)
Event code 45 (KEY_X)
Event code 46 (KEY_C)
Event code 47 (KEY_V)
Event code 48 (KEY_B)
Event code 49 (KEY_N)
Event code 50 (KEY_M)
Event code 51 (KEY_COMMA)
Event code 52 (KEY_DOT)
Event code 53 (KEY_SLASH)
Event code 54 (KEY_RIGHTSHIFT)
Event code 55 (KEY_KPASTERISK)
Event code 56 (KEY_LEFTALT)
Event code 57 (KEY_SPACE)
Event code 58 (KEY_CAPSLOCK)
Event code 59 (KEY_F1)
Event code 60 (KEY_F2)
Event code 61 (KEY_F3)
Event code 62 (KEY_F4)
Event code 63 (KEY_F5)
Event code 64 (KEY_F6)
Event code 65 (KEY_F7)
Event code 66 (KEY_F8)
Event code 67 (KEY_F9)
Event code 68 (KEY_F10)
Event code 69 (KEY_NUMLOCK)
Event code 70 (KEY_SCROLLLOCK)
Event code 71 (KEY_KP7)
Event code 72 (KEY_KP8)
Event code 73 (KEY_KP9)
Event code 74 (KEY_KPMINUS)
Event code 75 (KEY_KP4)
Event code 76 (KEY_KP5)
Event code 77 (KEY_KP6)
Event code 78 (KEY_KPPLUS)
Event code 79 (KEY_KP1)
Event code 80 (KEY_KP2)
Event code 81 (KEY_KP3)
Event code 82 (KEY_KP0)
Event code 83 (KEY_KPDOT)
Event code 85 (KEY_ZENKAKUHANKAKU)
Event code 86 (KEY_102ND)
Event code 87 (KEY_F11)
Event code 88 (KEY_F12)
Event code 89 (KEY_RO)
Event code 90 (KEY_KATAKANA)
Event code 91 (KEY_HIRAGANA)
Event code 92 (KEY_HENKAN)
Event code 93 (KEY_KATAKANAHIRAGANA)
Event code 94 (KEY_MUHENKAN)
Event code 95 (KEY_KPJPCOMMA)
Event code 96 (KEY_KPENTER)
Event code 97 (KEY_RIGHTCTRL)
Event code 98 (KEY_KPSLASH)
Event code 99 (KEY_SYSRQ)
Event code 100 (KEY_RIGHTALT)
Event code 102 (KEY_HOME)
Event code 103 (KEY_UP)
Event code 104 (KEY_PAGEUP)
Event code 105 (KEY_LEFT)
Event code 106 (KEY_RIGHT)
Event code 107 (KEY_END)
Event code 108 (KEY_DOWN)
Event code 109 (KEY_PAGEDOWN)
Event code 110 (KEY_INSERT)
Event code 111 (KEY_DELETE)
Event code 113 (KEY_MUTE)
Event code 114 (KEY_VOLUMEDOWN)
Event code 115 (KEY_VOLUMEUP)
Event code 116 (KEY_POWER)
Event code 117 (KEY_KPEQUAL)
Event code 119 (KEY_PAUSE)
Event code 121 (KEY_KPCOMMA)
Event code 122 (KEY_HANGUEL)
Event code 123 (KEY_HANJA)
Event code 124 (KEY_YEN)
Event code 125 (KEY_LEFTMETA)
Event code 126 (KEY_RIGHTMETA)
Event code 127 (KEY_COMPOSE)
Event code 128 (KEY_STOP)
Event code 129 (KEY_AGAIN)
Event code 130 (KEY_PROPS)
Event code 131 (KEY_UNDO)
Event code 132 (KEY_FRONT)
Event code 133 (KEY_COPY)
Event code 134 (KEY_OPEN)
Event code 135 (KEY_PASTE)
Event code 136 (KEY_FIND)
Event code 137 (KEY_CUT)
Event code 138 (KEY_HELP)
Event code 140 (KEY_CALC)
Event code 142 (KEY_SLEEP)
Event code 150 (KEY_WWW)
Event code 152 (KEY_SCREENLOCK)
Event code 158 (KEY_BACK)
Event code 159 (KEY_FORWARD)
Event code 161 (KEY_EJECTCD)
Event code 163 (KEY_NEXTSONG)
Event code 164 (KEY_PLAYPAUSE)
Event code 165 (KEY_PREVIOUSSONG)
Event code 166 (KEY_STOPCD)
Event code 173 (KEY_REFRESH)
Event code 176 (KEY_EDIT)
Event code 177 (KEY_SCROLLUP)
Event code 178 (KEY_SCROLLDOWN)
Event code 179 (KEY_KPLEFTPAREN)
Event code 180 (KEY_KPRIGHTPAREN)
Event code 183 (KEY_F13)
Event code 184 (KEY_F14)
Event code 185 (KEY_F15)
Event code 186 (KEY_F16)
Event code 187 (KEY_F17)
Event code 188 (KEY_F18)
Event code 189 (KEY_F19)
Event code 190 (KEY_F20)
Event code 191 (KEY_F21)
Event code 192 (KEY_F22)
Event code 193 (KEY_F23)
Event code 194 (KEY_F24)
Event code 240 (KEY_UNKNOWN)
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Event type 17 (EV_LED)
Event code 0 (LED_NUML) state 0
Event code 1 (LED_CAPSL) state 0
Event code 2 (LED_SCROLLL) state 0
Event code 3 (LED_COMPOSE) state 0
Event code 4 (LED_KANA) state 0
Key repeat handling:
Repeat type 20 (EV_REP)
Repeat code 0 (REP_DELAY)
Value 250
Repeat code 1 (REP_PERIOD)
Value 33

Last edited by Nikorasu82 (2025-07-21 22:04:14)

seth · 2025-07-21 22:27:48

Please use [code][/code] tags. Edit your posts in this regard.

Then collect some data:
1. The older journals
2. pacman log (around 17th)
3. behavior w/ the LTS kernel
4. re-attach the device, try a different usb slot.

after testing evtest dont know if this changes something but before restarting it was listed as device 13 and now it became 28
evtest result: Testing ... (interrupt to exit)
expected 24 bytes, got -1
evtest: error reading: No such device
Edit: sometimes it dissapears from evtest, but when i use lsusb it shows up again (still not working tho)

This will likely go along errors in dmesg, the device flickers on the bus.

Nikorasu82 · 2025-07-21 22:49:27

seth wrote:

Please use [code][/code] tags. Edit your posts in this regard.
Then collect some data:
1. The older journals
2. pacman log (around 17th)
3. behavior w/ the LTS kernel
4. re-attach the device, try a different usb slot.
after testing evtest dont know if this changes something but before restarting it was listed as device 13 and now it became 28
evtest result: Testing ... (interrupt to exit)
expected 24 bytes, got -1
evtest: error reading: No such device
Edit: sometimes it dissapears from evtest, but when i use lsusb it shows up again (still not working tho)
This will likely go along errors in dmesg, the device flickers on the bus.

sometimes I look back on decisions I take on my life, and then I notice that I never try enough...
it was the slot
I feel so dumb for not trying this before this...
thanks for the help and sorry for the trouble

seth · 2025-07-22 05:19:51

I feel so dumb for not trying this before this...

Or insufficiently frustrated by questionable engineering - you might as well feel lucky

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2025-07-21 20:40:10

[RESOLVED] my sayodevice is being recognized as mouse(?)

#2 2025-07-21 20:42:25

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#3 2025-07-21 21:01:27

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#4 2025-07-21 21:06:52

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#5 2025-07-21 21:14:07

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#6 2025-07-21 21:21:10

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#7 2025-07-21 21:21:57

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#8 2025-07-21 21:36:01

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#9 2025-07-21 21:39:46

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#10 2025-07-21 21:44:50

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#11 2025-07-21 21:54:47

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#12 2025-07-21 22:27:48

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#13 2025-07-21 22:49:27

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

#14 2025-07-22 05:19:51

Re: [RESOLVED] my sayodevice is being recognized as mouse(?)

Board footer