Opened 5 years ago

Last modified 5 years ago

#15862 new bug

USB Mouse not working

Reported by: Storm Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Drivers/Input/HID/USB Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by diver)

I am having the same problem i have tried different ports latest nightly and beta mainboard gigabyte H81M-D2V F6 bios rev 1.0.

haiku-master-hrev54026-x86_64-anyboot

~> listusb

13fe:3d00 /dev/bus/usb/0/0 “Kingston Technology Company Inc.” “USB DISK 2.0” ver. 0100
04ca:0095 /dev/bus/usb/0/8 “Lite-On Technology Corp.” “USB Gaming Keyboard” ver. 0153
03f0:1c41 /dev/bus/usb/0/9 “HP, Inc” “HP Gaming Mouse” ver. 0042
0000:0000 /dev/bus/usb/0/hub “HAIKU Inc.” “XHCI RootHub” ver. 0300
2109:3431 /dev/bus/usb/1/0/hub “VIA Labs, Inc.” “Hub” ver. 0420
0000:0000 /dev/bus/usb/1/hub “HAIKU Inc.” “XHCI RootHub” ver. 0300
8087:8008 /dev/bus/usb/2/0/hub “Intel Corp.” “” ver. 0005
0000:0000 /dev/bus/usb/2/hub “HAIKU Inc.” “EHCI RootHub” ver. 0200
8087:8000 /dev/bus/usb/3/0/hub “Intel Corp.” “” ver. 0005
0000:0000 /dev/bus/usb/3/hub “HAIKU Inc.” “EHCI RootHub” ver. 0200

~> listdev

device Serial bus controller (SMBus) [c|5|0]
vendor 8086: Intel Corporation
device 8c22: 8 Series/C220 Series Chipset Family SMBus Controller

device Mass storage controller (SATA controller, AHCI 1.0) [1|6|1]
vendor 8086: Intel Corporation
device 8c02: 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode]

device Bridge (ISA bridge) [6|1|0]
vendor 8086: Intel Corporation
device 8c5c: H81 Express LPC Controller

device Serial bus controller (USB controller, EHCI) [c|3|20]
vendor 8086: Intel Corporation
device 8c26: 8 Series/C220 Series Chipset Family USB EHCI #1

device Serial bus controller (USB controller, XHCI) [c|3|30]
vendor 1106: VIA Technologies, Inc.
device 3483: VL805 USB 3.0 Host Controller

device Bridge (PCI bridge, Normal decode) [6|4|0]
vendor 8086: Intel Corporation
device 8c16: 8 Series/C220 Series Chipset Family PCI Express Root Port #4

device Network controller (Ethernet controller) [2|0|0]
vendor 10ec: Realtek Semiconductor Co., Ltd.
device 8168: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

device Bridge (PCI bridge, Normal decode) [6|4|0]
vendor 8086: Intel Corporation
device 8c14: 8 Series/C220 Series Chipset Family PCI Express Root Port #3

device Bridge (PCI bridge, Normal decode) [6|4|0]
vendor 8086: Intel Corporation
device 8c10: 8 Series/C220 Series Chipset Family PCI Express Root Port #1

device Multimedia controller (Audio device) [4|3|0]
vendor 8086: Intel Corporation
device 8c20: 8 Series/C220 Series Chipset High Definition Audio Controller

device Serial bus controller (USB controller, EHCI) [c|3|20]
vendor 8086: Intel Corporation
device 8c2d: 8 Series/C220 Series Chipset Family USB EHCI #2

device Communication controller [7|80|0]
vendor 8086: Intel Corporation
device 8c3a: 8 Series/C220 Series Chipset Family MEI Controller #1

device Serial bus controller (USB controller, XHCI) [c|3|30]
vendor 8086: Intel Corporation
device 8c31: 8 Series/C220 Series Chipset Family USB xHCI

device Multimedia controller (Audio device) [4|3|0]
vendor 10de: NVIDIA Corporation
device 0e0b: GK106 HDMI Audio Controller

device Display controller (VGA compatible controller, VGA controller) [3|0|0]
vendor 10de: NVIDIA Corporation
device 11c0: GK106 [GeForce GTX 660]

device Bridge (PCI bridge, Normal decode) [6|4|0]
vendor 8086: Intel Corporation
device 0c01: Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller

device Bridge (Host bridge) [6|0|0]
vendor 8086: Intel Corporation
device 0c00: 4th Gen Core Processor DRAM Controller

Attachments (12)

Change History (23)

comment:1 by Storm, 5 years ago

also networking card not working says no link then restart the link.

comment:2 by diver, 5 years ago

Description: modified (diff)
Platform: x86-64All

Please attach your syslog.

comment:3 by Storm, 5 years ago

were is that located?

in reply to:  3 comment:4 by X512, 5 years ago

Replying to Storm:

were is that located?

At /boot/system/var/log/syslog.

by Storm, 5 years ago

Attachment: syslog added

comment:5 by waddlesplash, 5 years ago

KERN: usb_hid: no handlers for hid device

Indeed, it sounds like this is a non-standard mouse that we don't have a driver for.

comment:6 by waddlesplash, 5 years ago

Component: Drivers/USBDrivers/Input/USB-HID
Owner: changed from mmlr to nobody

comment:7 by Storm, 5 years ago

i have found a fix i updated the firmware https://support.hp.com/us-en/drivers/selfservice/omen-by-hp-mouse/16172072/model/16172073 HP omen 600 mouse My network is still constantly restarting though

comment:8 by X512, 5 years ago

  • usb_hid_report_descriptor_03f0_1c41_0

Defines generic mouse so it should work.

Last edited 5 years ago by X512 (previous) (diff)

in reply to:  7 comment:9 by X512, 5 years ago

Replying to Storm:

My network is still constantly restarting though

Create separate ticket for that.

comment:10 by lt_henry, 5 years ago

I join to his issue. I have a usb keyboard and a mice detected but not working. Both are gaming-like peripherals (seems this devices are not very hid friendly).

I am in linux right now, sorry. I will upload report descriptors this evening. Those are the id's:

Bus 003 Device 003: ID 1532:0037 Razer USA, Ltd Bus 003 Device 002: ID 04d9:a096 Holtek Semiconductor, Inc.

I have compiled a custom usb_hid with extra traces, and my keyboard (mice not tested yet) is successfully handled by KeyboardProtocolHandler, at least a pair of its reported configurations.

So, I gone to Linux sources to check usb hid quirks and bingo, the keyboard at least is flagged:

{ HID_USB_DEVICE(USB_VENDOR_ID_HOLTEK_ALT, USB_DEVICE_ID_HOLTEK_ALT_KEYBOARD_A096), HID_QUIRK_NO_INIT_REPORTS },

I dont understand what NO_INIT_REPORTS really does (I am not a hid expert, tbh), It seems that some devices dont like to be requested about input reports, and I get confused at this point :\ It seems that this cannot be done through our Quirks mechanism.

I'll upload descriptors later.

comment:11 by lt_henry, 5 years ago

Ok, I've been digging on Linux sources and seems that they have a custom report descriptor, so maybe I would need to write my own one, as we already do with Xbox and Playstation gamepads.

The mice part: Linux doesnt seems to have a quirk for this mice. At syslog there is no error messages until the mice is moved, then a lot of FIFO overrun happen.

I'm not an expert, but I can do more tests with both devices if you guys guide me a bit. ideas?

by lt_henry, 5 years ago

Attachment: 1532_0037_syslog.txt added
Note: See TracTickets for help on using tickets.