Opened 17 months ago
Last modified 12 months ago
#18495 new bug
Touchpad & Bluetooth don't work on laptop
| Reported by: | eugenia | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Drivers/Input/HID/I2C | Version: | R1/Development |
| Keywords: | bluetooth, touchpad | Cc: | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description (last modified by )
I have this other laptop (DELL 5480) that I tried Haiku-nightly on tonight, and it booted great. Absolutely everything works on it, including wifi, expect for the touchpad and the Bluetooth. The touchpad is obviously the bigger concern between the two.
I connected a USB mouse, and that worked fine. The keyboard also works fine. It's just that the touchpad doesn't register at all.
In case of the Bluetooth, it sees that it's a bluetooth device (it loads the B logo in the bluetooth app), it tries to start the service, but it says that it failed.
I'm attaching here lsusb and lspci from my Kubuntu partition on that machine. The device name for the touchpad is weirdly called under X11's xinput: DLL07D0:01 044E:120B
Attachments (4)
Change History (8)
by , 17 months ago
comment:1 by , 17 months ago
| Description: | modified (diff) |
|---|
comment:2 by , 17 months ago
The touchpad "DLL07D0" appears to be an ALPS I2C device according to https://www.driveridentifier.com/scan/alps-i2c-hid-device/download/1096433241/CD3BCF37E3F44A42AC80142D140A4EFA/ACPI%5CDLL07D0
Our I2C HID driver is incomplete, I don't know if it can discover devices from the ACPI device tree, and also if it needs special handling for ALPS devices or if they follow the HID standard. I think it is also not included in nightly images yet?
If you want to help testing this driver you may have to make some changes to Haiku sources to build a custom disk image including it, are you willing to do this? If so we can provide instructions for it.
Bluetooth is generally unsupported. The best you can get with the current code is pairing with some devices, but there are no drivers to do anything with them once they are paired, so it is quite useless at the moment.
comment:3 by , 17 months ago
Thank you. If the driver is going to be included in future nightlies, I can wait for it to test again. Currently I can't develop, as our home is in disarray due to moving back to Europe.
comment:4 by , 12 months ago
still no luck but slightly different hardware. Adding here since it's most probably related. Also, bluetooth and touchpad seem to be related as they are on the same chip from what I gathered.
My hardware:
Platform
StarLabs StarBook, Intel 11th gen platform
Bluetooth
Bluetooth from Devices app: usb/subclass 0x1 usb/protocol 0x1 device/id 0x26 device/vendor 0x8087 usb/class 0xe0 device/flags 2 usb/id 36 Device name AX201 Bluetooth device/driver bus_managers/usb/device/driver_v1 Manufacturer Intel Corp. Driver used unknown Device paths unknown device/bus usb device/pretty name USB device Class info Wireless (Radio Frequency, Bluetooth)
Touchpad
most probably this one, not recognized:
Class info Human Interface Device (No Subclass, None) Device name Unknown Device paths unknown device/bus usb device/driver bus_managers/usb/device/driver_v1 device/flags 2 device/id 0x2016 device/pretty name USB device device/vendor 0x258a Driver used unknown Manufacturer Unknown usb/class 0x3 usb/id 12 usb/protocol 0 usb/subclass 0
lspci -v