[Kernel-packages] [Bug 2002353] Re: Problem with Goodix i2c touch screen
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/2002353 Title: Problem with Goodix i2c touch screen Status in linux package in Ubuntu: Confirmed Bug description: I have no-name tablet with goodix touch screen which not work in any version of Ubuntu. Currently I work with 20.04 LTS and kernel 5.15.0-56-lowlatency. It reports into dmesg: Goodix-TS i2c-GDIX1002:00: acpi_dev_get_resources returned: 1, ts->gpio_count: 2, ts->gpio_int_idx: -1 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121 After reviewing driver's source code I found that such parameters are very close to code path which is used for bay trail, but my system is not bay trail. When I comment out check for bay trail driver started to work: 776c776 < } else if (/*is_byt() &&*/ ts->gpio_count == 2 && ts->gpio_int_idx == -1) { --- > } else if (is_byt() && ts->gpio_count == 2 && ts->gpio_int_idx == -1) { Maybe this is not correct fix and I may fix something in my system so it will start to work with 'normal' driver? Or maybe driver need to be modified as that checking for bay trail is not needed? Thanks. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kioskset 4197 F...m alsa_dmixd /dev/snd/controlC0: kioskset 4197 F alsa_dmixd /dev/snd/timer: kioskset 4197 f alsa_dmixd CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 MachineType: Default string Default string Package: linux (not installed) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/appliance-vmlinuz root=UUID=bfe1498f-1f0d-48fe-b456-bfeebe528053 ro quiet splash nvidia-drm.modeset=1 net.ifnames=0 brd.rd_nr=0 usbcore.autosuspend=-1 elevator=noop vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-lowlatency 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-lowlatency N/A linux-backports-modules-5.15.0-56-lowlatency N/A linux-firmware1.187.33 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-56-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/26/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S101UJSR200_8GB_R02 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS101UJSR200_8GB_R02:bd09/26/2019:br5.11:efr1.13:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Tablet dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002353] Re: Problem with Goodix i2c touch screen
apport information ** Tags added: apport-collected focal ** Description changed: I have no-name tablet with goodix touch screen which not work in any version of Ubuntu. Currently I work with 20.04 LTS and kernel 5.15.0-56-lowlatency. It reports into dmesg: Goodix-TS i2c-GDIX1002:00: acpi_dev_get_resources returned: 1, ts->gpio_count: 2, ts->gpio_int_idx: -1 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121 After reviewing driver's source code I found that such parameters are very close to code path which is used for bay trail, but my system is not bay trail. When I comment out check for bay trail driver started to work: 776c776 < } else if (/*is_byt() &&*/ ts->gpio_count == 2 && ts->gpio_int_idx == -1) { --- > } else if (is_byt() && ts->gpio_count == 2 && ts->gpio_int_idx == -1) { Maybe this is not correct fix and I may fix something in my system so it will start to work with 'normal' driver? Or maybe driver need to be modified as that checking for bay trail is not needed? Thanks. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.25 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0p: kioskset 4197 F...m alsa_dmixd + /dev/snd/controlC0: kioskset 4197 F alsa_dmixd + /dev/snd/timer: kioskset 4197 f alsa_dmixd + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + MachineType: Default string Default string + Package: linux (not installed) + ProcEnviron: + SHELL=/bin/bash + LANG=en_US.UTF-8 + TERM=xterm + XDG_RUNTIME_DIR= + PATH=(custom, no user) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/appliance-vmlinuz root=UUID=bfe1498f-1f0d-48fe-b456-bfeebe528053 ro quiet splash nvidia-drm.modeset=1 net.ifnames=0 brd.rd_nr=0 usbcore.autosuspend=-1 elevator=noop vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-lowlatency 5.15.64 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-56-lowlatency N/A + linux-backports-modules-5.15.0-56-lowlatency N/A + linux-firmware1.187.33 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal + Uname: Linux 5.15.0-56-lowlatency x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 09/26/2019 + dmi.bios.release: 5.11 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: S101UJSR200_8GB_R02 + dmi.board.asset.tag: Default string + dmi.board.name: Default string + dmi.board.vendor: Default string + dmi.board.version: Default string + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 10 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.ec.firmware.release: 1.13 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS101UJSR200_8GB_R02:bd09/26/2019:br5.11:efr1.13:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: + dmi.product.family: Tablet + dmi.product.name: Default string + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Default string ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2002353/+attachment/5640991/+files/AlsaInfo.txt -- 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/2002353 Title: Problem with Goodix i2c touch screen Status in linux package in Ubuntu: Incomplete Bug description: I have no-name tablet with goodix touch screen which not work in any version of Ubuntu. Currently I work with 20.04 LTS and kernel 5.15.0-56-lowlatency. It reports into dmesg: Goodix-TS i2c-GDIX1002:00: acpi_dev_get_resources returned: 1, ts->gpio_count: 2, ts->gpio_int_idx: -1 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121 After reviewing driver's source code I found that such parameters are very close to code path which is used for bay trail, but my system is not bay trail. When I comment out check for bay trail driver started to work: 776c776 < } else if (/*is_byt() &&*/ ts->gpio_count == 2 && ts->gpio_int_idx == -1) { --- > } else if (is_byt() && ts->gpio_count == 2 && ts->gpio_int_idx == -1) { Maybe this is not correct fix and I may fix something in my system so it will start to work with 'normal' driver? Or maybe driver need to be modified as that checking for bay trail is not needed? Thanks. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kioskset 4197 F...m alsa_dmixd /dev/snd/controlC0: kioskset 4197 F alsa_dmixd /dev/snd/t
[Kernel-packages] [Bug 2002353] Re: Problem with Goodix i2c touch screen
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002353/+attachment/5640275/+files/version.log -- 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/2002353 Title: Problem with Goodix i2c touch screen Status in linux package in Ubuntu: New Bug description: I have no-name tablet with goodix touch screen which not work in any version of Ubuntu. Currently I work with 20.04 LTS and kernel 5.15.0-56-lowlatency. It reports into dmesg: Goodix-TS i2c-GDIX1002:00: acpi_dev_get_resources returned: 1, ts->gpio_count: 2, ts->gpio_int_idx: -1 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121 Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121 After reviewing driver's source code I found that such parameters are very close to code path which is used for bay trail, but my system is not bay trail. When I comment out check for bay trail driver started to work: 776c776 < } else if (/*is_byt() &&*/ ts->gpio_count == 2 && ts->gpio_int_idx == -1) { --- > } else if (is_byt() && ts->gpio_count == 2 && ts->gpio_int_idx == -1) { Maybe this is not correct fix and I may fix something in my system so it will start to work with 'normal' driver? Or maybe driver need to be modified as that checking for bay trail is not needed? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp