Bug 1572625
| Summary: | Accupoint (keyboard built-in mouse pointer) does not work | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tom <tom.mannerhagen> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 28 | CC: | airlied, bskeggs, dchen, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, peter.hutterer, sam, steved, tom.mannerhagen | ||||||
| Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-08-29 15:05:10 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Tom
2018-04-27 12:51:36 UTC
This is the correct link to the bug report on the user-forum: https://forum.toshiba.eu/showthread.php?97938-Portege-X30-D-Accupoint-and-fingerprint-scanner-not-working /Tom I'm assuming the "Toshiba input device" is the accupoint? What's the sudo evemu-record output for that device? Created attachment 1429798 [details]
evemu-record dump from Accupoint
evemu-record dump from Accupoint
No events shown when moving the accupoint
Created attachment 1429799 [details]
evemu-record dump from Touchpad
Adding the evemu-record dump from the touchpad if of any use.
Is there another input device that may be the trackpoint? The "Toshiba input device" is definitely not it, it's a collection of multimedia keys. No buttons, no axes that would be required by a relative input device like a trackpoint. Hi Right, the "Toshiba input device" was actually the hotkeys. I looked at the Windows driver and it seems the accupoint is connected with the touchpad and activated via the driver. Can you guide me how to provide relevant information back to you? Is the INF useful here? BR Tom Punting to the kernel, looks like the device is never initialized correctly, so libinput doesn't get to see it. Needs to be fixed in the kernel. Hi It could be that this device is found at acpi/TOS0213 /sys/bus/acpi/devices/TOS0213:00 The path matches the details found in the Windows INF-file. Would it be possible to use an existing standard driver for this device? If so, can you tell me how to test? BR Tom *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.17.7-200.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. This is still an issue in Fedora 31. I have filed a bug upstream: https://bugzilla.kernel.org/show_bug.cgi?id=205817 |