byd touchpad no longer detected

Bug #1687256 reported by Daveh
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

When running on kernel 4.8.0-34 my Lafite byd touchpad is recognised correctly and shows with xinput --list as BYDPS/2 BYD Touchpad.
If I use any higher upgrade, eg 4.8.0-46 in 16.10 then touchpad is only identified as ImPS/2 Generic Wheel Mouse. The same applies if I try 17.04 from an external drive, touchpad does not work and cursor remains in top rh corner of screen.
This could be related to the changelog https://launchpad.net/ubuntu/+source/linux/+changelog

4.8.0-36.38 in yakkety-proposed

  * Yakkety update to v4.8.13 stable release (LP: #1650581)
...
    - Input: psmouse - disable automatic probing of BYD touchpads

https://patchwork.kernel.org/patch/9424421/

---
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dave 3590 F.... pulseaudio
 /dev/snd/controlC1: dave 3590 F.... pulseaudio
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=0b7a1f56-4391-4d9d-90ed-d0f5f5d76c90
InstallationDate: Installed on 2015-05-17 (714 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Intel Corporation SharkBay Platform
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-34-generic N/A
 linux-backports-modules-4.8.0-34-generic N/A
 linux-firmware 1.161.1
Tags: yakkety
Uname: Linux 4.8.0-34-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 03/27/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.6.5
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: WhiteTip Mountain1 Fab2
dmi.board.vendor: Topstar
dmi.board.version: Fab2
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/27/2015:svnIntelCorporation:pnSharkBayPlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrFab2:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
dmi.product.name: SharkBay Platform
dmi.product.version: 0.1
dmi.sys.vendor: Intel Corporation

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1687256/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Daveh (hatton-d) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected yakkety
description: updated
Revision history for this message
Daveh (hatton-d) wrote : CRDA.txt

apport information

Revision history for this message
Daveh (hatton-d) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Daveh (hatton-d) wrote : IwConfig.txt

apport information

Revision history for this message
Daveh (hatton-d) wrote : JournalErrors.txt

apport information

Revision history for this message
Daveh (hatton-d) wrote : Lspci.txt

apport information

Revision history for this message
Daveh (hatton-d) wrote : Lsusb.txt

apport information

Revision history for this message
Daveh (hatton-d) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Daveh (hatton-d) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Daveh (hatton-d) wrote : ProcModules.txt

apport information

Revision history for this message
Daveh (hatton-d) wrote : RfKill.txt

apport information

Revision history for this message
Daveh (hatton-d) wrote : UdevDb.txt

apport information

Revision history for this message
Daveh (hatton-d) wrote : WifiSyslog.txt

apport information

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.11 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
tags: added: kernel-da-key
Daveh (hatton-d)
description: updated
Revision history for this message
Daveh (hatton-d) wrote :

kernel-bug-exists-upstream

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Did you try this command, as commit log suggested?
echo -n "byd" > /sys/bus/serio/devices/serio1/drvctl

Revision history for this message
Daveh (hatton-d) wrote : Re: [Bug 1687256] Re: byd touchpad no longer detected

I have just tried that and get "Permission denied"

On 04/05/2017 06:47, Kai-Heng Feng wrote:
> Did you try this command, as commit log suggested?
> echo -n "byd" > /sys/bus/serio/devices/serio1/drvctl
>

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Use "sudo -s" to get root permission first.

Revision history for this message
Daveh (hatton-d) wrote :

Thanks for the help and advice so far. Before making an upstream bug report I would like to be sure that is necessary, as I believe the problem relates to the patch referred to in bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424293.
What has actually happened is that my touchpad has reverted to the condition prior to BYD patch implementation described in this bug report.

Revision history for this message
Daveh (hatton-d) wrote :

I have tried this: echo -n "byd" > /sys/bus/serio/devices/serio1/drvctl

and get: bash: echo: write error: Invalid argument

On 05/05/17 08:17, Kai-Heng Feng wrote:
> Use "sudo -s" to get root permission first.
>

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Maybe it's not exactly serio1? Maybe it's 0 or 2 or something.

penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-4.11-rc8 needs-upstream-testing
tags: added: needs-bisect regression-update
tags: added: zesty
description: updated
tags: removed: needs-bisect
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Okay, it's a type in the commit log. Use this instead:
echo -n "byd" > /sys/bus/serio/devices/serio1/protocol

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

type -> typo ...

Revision history for this message
Daveh (hatton-d) wrote :

Thanks for your patience, the touchpad is then recognised.

On 11/05/17 09:28, Kai-Heng Feng wrote:
> Okay, it's a type in the commit log. Use this instead:
> echo -n "byd" > /sys/bus/serio/devices/serio1/protocol
>

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you share your laptop's vendor name and product name?
The dmi string isn't really helpful.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

4.8 has reached EOL.
Please give the supported version (19.04 Disco / 18.04.3 Bionic) a try.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
status: Incomplete → Won't Fix
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

I'm closing this with Won't fix.
If the issue still exist, please file a new bug.
Thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.