I recently bought the Voyo Vbook 3 (CherryTrail Edition) which employs the same 
touchpad.
I have emailed Voyo but didn't receive an answer yet. But judging from some 
screenshots I found the touchpad might very well be a Synaptics device.

As I am not an experienced developer, especially in regard to the Linux
Kernel, I didn't try to assign the synaptics driver. Instead I went for
hid-generic which offers basic functionality.

The problem is, that this device gets matched by hid-multitouch. An easy kernel 
patch is to add the line
#define USB_VENDOR_ID_RIPOFF    0x1018
to drivers/hid/hid-ids.h in the kernel source and then modify 
drivers/hid/hid-core.c to contain
    case USB_VENDOR_ID_RIPOFF:
        hid->group = HID_GROUP_GENERIC;
        break;
within the function hid_scan_report under vendor specific handlings.

I didn't have the time to recompile the whole kernel (4.13.0, Ubuntu
17.10), so I compiled and installed everything in "drivers/hid" as
external modules. After reloading the hid module, the touchpad works.

Curiously, it wouldn't work directly after start up even though the right .ko 
file had been loaded (as reported by modinfo), so i put the lines
hid
usbhid
hid-generic
in \etc\initramfs-tools\modules and did an "update-initramfs -u"
Now it works on the login screen.

I hope someone with more experience can propose an appropriate kernel patch or 
something?
In the meantime I plan to soonish publish a more extensive description of my 
little hack and more tricks to also get other hardware of the voyo (such as 
wifi) working.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1685937

Title:
  HID 1018:1006 Touchpad does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad does not work. hid_multitouch interprets gestures as weird stuff 
-> opens search, types letters. If I didnt overlook anything the touchpad 
position does not show in any of the /dev/input files.. Any help would be 
appreciated.
  edit:  its on a trekstor surfbook w2.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 24 23:05:18 2017
  MachineType: TrekStor SurfBook W2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=78342794-9ef5-4a63-9b1e-040a63fd644b ro i8042.nopnp quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware                             1.164
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2016
  dmi.bios.version: SB14464-2_BIOS_V2.1.1
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: CherryTrail CR
  dmi.board.vendor: TS_I-Net
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvn:bvrSB14464-2_BIOS_V2.1.1:bd11/22/2016:svnTrekStor:pnSurfBookW2:pvrType1-TBDbyOEM:rvnTS_I-Net:rnCherryTrailCR:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: SurfBook W2
  dmi.product.version: Type1 - TBD by OEM
  dmi.sys.vendor: TrekStor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685937/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to