(Solved) Strange problem with Touchscreen - Teclast F6 Plus

[JannerOyibo]

Hello,

I am trying to see if Mint will install correctly on an old Teclast F6 plus laptop.

So I can boot into Mint using a bootable USB drive and everything works except Wifi. Touchscreen works ok.

So to correct the wifi issue, i found on a thread that issuing the following commnad fixes wifi :-

echo 1 | sudo tee /sys/bus/pci/rescan

And this allows the wifi to work However this also causes the touchscreen to stop working.

I am a little lost so does anyone have a fix for this ?

Thanks in advance for your help.........

[SMG]

Hello,

I am trying to see if Mint will install correctly on an old Teclast F6 plus laptop.

So I can boot into Mint using a bootable USB drive and everything works except Wifi. Touchscreen works ok.

So to correct the wifi issue, i found on a thread that issuing the following commnad fixes wifi :-

echo 1 | sudo tee /sys/bus/pci/rescan

And this allows the wifi to work However this also causes the touchscreen to stop working.

Welcome to the forum, JannerOyibo.

After you get the wifi working, please post your system information here. Open the System Reports app and click the System Information tab on the left. Your computer's information should come up in the right pane. Then click the Copy button in the lower right and paste the results into a reply window here so we can see how Linux Mint views your hardware.

[JannerOyibo]

Code: Select all

System:
  Kernel: 5.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
    tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
    base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: TECLAST product: F6 Plus v: N/A serial: <superuser required> Chassis:
    type: 10 serial: <superuser required>
  Mobo: TECLAST model: F6 Plus v: 1.0 serial: <superuser required> UEFI: American Megatrends
    v: tPAD 3.12 date: 12/26/2019
Battery:
  ID-1: BAT0 charge: 36.9 Wh (98.9%) condition: 37.3/37.0 Wh (100.8%) volts: 7.6 min: N/A
    model: N/A type: Unknown serial: <filter> status: Charging
CPU:
  Info: quad core model: Intel Celeron N4100 bits: 64 type: MCP smt: <unsupported>
    arch: Goldmont Plus rev: 1 cache: L1: 224 KiB L2: 4 MiB
  Speed (MHz): avg: 2299 high: 2333 min/max: 800/2400 cores: 1: 2288 2: 2288 3: 2288 4: 2333
    bogomips: 8755
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel GeminiLake [UHD Graphics 600] driver: i915 v: kernel ports: active: eDP-1
    empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3185 class-ID: 0300
  Device-2: Mustek Systems USB 2.0 PC Camera type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-6:8 chip-ID: 055f:3843 class-ID: 0102
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3072x1728 s-dpi: 120 s-size: 650x366mm (25.6x14.4") s-diag: 746mm (29.4")
  Monitor-1: eDP-1 model: LM133LF5L01 res: 3072x1728 hz: 60 dpi: 265 size: 294x165mm (11.6x6.5")
    diag: 337mm (13.3") modes: 1920x1080
  OpenGL: renderer: Mesa Intel UHD Graphics 600 (GLK 2) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1
    direct render: Yes
Audio:
  Device-1: Intel Celeron/Pentium Silver Processor High Definition Audio vendor: Realtek
    driver: snd_hda_intel v: kernel bus-ID: 00:0e.0 chip-ID: 8086:3198 class-ID: 0403
  Device-2: Mustek Systems USB 2.0 PC Camera type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-6:8 chip-ID: 055f:3843 class-ID: 0102
  Sound Server-1: ALSA v: k5.15.0-91-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 8086:3165 class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-4:5
    chip-ID: 8087:0a2a class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
    sub-v: 1000 hci-v: 4.2 rev: 1000
Drives:
  Local Storage: total: 536.42 GiB used: 0 KiB (0.0%)
  ID-1: /dev/sda model: BW-SA3 MX size: 476.94 GiB speed: 6.0 Gb/s type: SSD serial: <filter>
    rev: 612 scheme: GPT
  ID-2: /dev/sdb type: USB vendor: SanDisk model: SDDR-113 size: 59.48 GiB type: N/A
    serial: <filter> rev: 1.00 scheme: MBR
Partition:
  ID-1: / size: 3.79 GiB used: 85.3 MiB (2.2%) fs: overlay source: ERR-102
Swap:
  Alert: No swap data was found.
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 9 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 1-2:2 info: USB2.0 HUB ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
    chip-ID: 2148:7022 class-ID: 0900
  Device-1: 1-2.1:9 info: Maxxter Wireless Receiver type: Mouse,Keyboard
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 50mA chip-ID: 248a:8514
    class-ID: 0301
  Device-2: 1-2.2:6 info: China Resource Semico Keyboard type: Keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 98mA chip-ID: 1a2c:2124
    class-ID: 0300
  Device-3: 1-3:3 info: Realtek RTS5129 Card Reader Controller type: <vendor specific>
    driver: rtsx_usb,rtsx_usb_ms,rtsx_usb_sdmmc interfaces: 1 rev: 2.0 speed: 480 Mb/s power: 500mA
    chip-ID: 0bda:0129 class-ID: ff00 serial: <filter>
  Device-4: 1-4:5 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0a2a class-ID: e001
  Device-5: 1-5:7 info: SanDisk SDDR-113 type: Mass Storage driver: usb-storage interfaces: 1
    rev: 2.0 speed: 480 Mb/s power: 250mA chip-ID: 0781:a7a8 class-ID: 0806 serial: <filter>
  Device-6: 1-6:8 info: Mustek Systems USB 2.0 PC Camera type: Video,Audio
    driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s power: 500mA
    chip-ID: 055f:3843 class-ID: 0102
  Hub-3: 2-0:1 info: Super-speed hub ports: 7 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 53.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: apt: 2120
  Active apt repos in: /etc/apt/sources.list
    1: deb cdrom:[Linux Mint 21.3 _Virginia_ - Release amd64 20240109]/ jammy contrib main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com virginia main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 238 Uptime: 2h 3m wakeups: 1 Memory: 7.57 GiB used: 2.17 GiB (28.7%) Init: systemd
  v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
  inxi: 3.3.13

[JannerOyibo]

Code: Select all

mint@mint:~$ xinput
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SEM USB Keyboard Consumer Control       	id=13	[slave  pointer  (2)]
⎜   ↳ Goodix Capacitive TouchScreen           	id=16	[slave  pointer  (2)]
⎜   ↳ HTIX5288:00 0911:5288 Mouse             	id=17	[slave  pointer  (2)]
⎜   ↳ HTIX5288:00 0911:5288 Touchpad          	id=18	[slave  pointer  (2)]
⎜   ↳ Telink Wireless Receiver Consumer Control	id=8	[slave  pointer  (2)]
⎜   ↳ Telink Wireless Receiver Mouse          	id=23	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Video Bus                               	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ SEM USB Keyboard                        	id=12	[slave  keyboard (3)]
    ↳ SEM USB Keyboard System Control         	id=14	[slave  keyboard (3)]
    ↳ USB 2.0 PC Camera: PC Camera            	id=15	[slave  keyboard (3)]
    ↳ HTIX5288:00 0911:5288 Keyboard          	id=19	[slave  keyboard (3)]
    ↳ Intel HID events                        	id=20	[slave  keyboard (3)]
    ↳ Intel HID 5 button array                	id=21	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=22	[slave  keyboard (3)]
    ↳ SEM USB Keyboard Consumer Control       	id=24	[slave  keyboard (3)]
    ↳ Goodix Capacitive TouchScreen           	id=25	[slave  keyboard (3)]
    ↳ Telink Wireless Receiver Consumer Control	id=9	[slave  keyboard (3)]
    ↳ Telink Wireless Receiver System Control 	id=10	[slave  keyboard (3)]
    ↳ Telink Wireless Receiver                	id=11	[slave  keyboard (3)]

[SMG]

So to correct the wifi issue, i found on a thread that issuing the following commnad fixes wifi :-

echo 1 | sudo tee /sys/bus/pci/rescan

And this allows the wifi to work

I am not familiar with that as a fix for wifi. Where did you find it?

Did you try finding a different solution for wifi rather than the one you are using? I did a search on Intel Wireless 3165 and didn't see others having problems.

However this also causes the touchscreen to stop working.

If you send a command to all PCI buses then you should expect it affect more than just the wifi.

The Goodix touchscreen is showing in the output you posted.

Code: Select all

mint@mint:~$ xinput
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Goodix Capacitive TouchScreen           	id=16	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Goodix Capacitive TouchScreen           	id=25	[slave  keyboard (3)]

[JannerOyibo]

I found the link concerning WiFi adapter at :

https://askubuntu.com/questions/1266523 ... oesnt-work

I'm a bit of a newbie as far as Linux is concerned so just blindly followed commands in that thread. I'd appreciate any ideas to get both wifi and touchscreen working at same time...

[SMG]

I found the link concerning WiFi adapter at :

https://askubuntu.com/questions/1266523 ... oesnt-work

Did you check to see if wireless was showing before you ran that command? You would check the following location in the System Information.

Code: Select all

Network:
  Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 8086:3165 class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>

Additionally, this topic Intel 3165 not working on Ubuntu 19.10 indicates there was output in dmesg to indicate the port was not powered.

Did you make the changes indicated in the BIOS of the link you provided?

[JannerOyibo]

Prior to issuing command, No network card seen in system information and also no output from dmesg | | grep iwl command :-
Network:
Message: No device data found.


mint@mint:~$ dmesg | grep iwl
mint@mint:~$

After issuing scan command previously mentioned , system information does see the wifi card and I get the following from dmesg | grep iwl command :-

mint@mint:~$ dmesg | grep iwl
[ 392.016086] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[ 392.064712] iwlwifi 0000:02:00.0: Found debug destination: EXTERNAL_DRAM
[ 392.064720] iwlwifi 0000:02:00.0: Found debug configuration: 0
[ 392.065233] iwlwifi 0000:02:00.0: loaded firmware version 29.4063824552.0 7265D-29.ucode op_mode iwlmvm
[ 392.238246] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210
[ 392.252680] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
[ 392.253999] iwlwifi 0000:02:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 392.259031] iwlwifi 0000:02:00.0: base HW address: 5c:80:b6:d4:cf:ba
[ 392.320784] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 392.342880] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
[ 392.417559] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
[ 392.497247] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
[ 392.498741] iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring

I did make bios settings changes mentioned in link.

I have noticed that I was slightly off when I mentioned that touchscreen did work prior to sending the rescan command. I can now say that the touchscreen does work on booting the system then stops after a couple of minutes even before sending that rescan command. So basically I think that I should be looking more at the problem of the touchscreen being seen by the system but not not actually working with or without wifi issue......

Any thoughts ?

[SMG]

I have noticed that I was slightly off when I mentioned that touchscreen did work prior to sending the rescan command. I can now say that the touchscreen does work on booting the system then stops after a couple of minutes even before sending that rescan command. So basically I think that I should be looking more at the problem of the touchscreen being seen by the system but not not actually working with or without wifi issue......

Any thoughts ?

When specifically does it seem to stop working? Is it before or after you log in?

Some others with Goodix touchscreens have discovered the rotation of the screen is off (sometimes 90 or 180 degrees) so check to see if it might be working in a different location than the location you are expecting it to work.

What is the output of

Code: Select all

dmesg -T | grep 'Goodix'

[JannerOyibo]

When specifically does it seem to stop working? Is it before or after you log in?
Since I'm loading Mint from bootable USB drive, no login required as it boots directly into desktop

Some others with Goodix touchscreens have discovered the rotation of the screen is off (sometimes 90 or 180 degrees) so check to see if it might be working in a different location than the location you are expecting it to work.
I have tried setting laptop set at 90, 180 and 270 deg - doesn't work in any of these angles

What is the output of
mint@mint:~$ dmesg -T | grep 'Goodix'
[Mon Apr 1 07:10:08 2024] Goodix-TS i2c-GDIX1002:00: supply AVDD28 not found, using dummy regulator
[Mon Apr 1 07:10:08 2024] Goodix-TS i2c-GDIX1002:00: supply VDDIO not found, using dummy regulator
[Mon Apr 1 07:10:08 2024] Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121
[Mon Apr 1 07:10:08 2024] Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121
[Mon Apr 1 07:10:08 2024] Goodix-TS i2c-GDIX1002:00: ID 9111, version: 8030
[Mon Apr 1 07:10:08 2024] input: Goodix Capacitive TouchScreen as /devices/pci0000:00/0000:00:17.0/i2c_designware.4/i2c-4/i2c-GDIX1002:00/input/input16

[SMG]

Since I'm loading Mint from bootable USB drive, no login required as it boots directly into desktop

I forgot you hadn't actually installed Linux Mint and thus are not working with the most recent updates.

mint@mint:~$ dmesg -T | grep 'Goodix'
[Mon Apr 1 07:10:08 2024] Goodix-TS i2c-GDIX1002:00: supply AVDD28 not found, using dummy regulator
[Mon Apr 1 07:10:08 2024] Goodix-TS i2c-GDIX1002:00: supply VDDIO not found, using dummy regulator
[Mon Apr 1 07:10:08 2024] Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 1: -121
[Mon Apr 1 07:10:08 2024] Goodix-TS i2c-GDIX1002:00: i2c test failed attempt 2: -121
[Mon Apr 1 07:10:08 2024] Goodix-TS i2c-GDIX1002:00: ID 9111, version: 8030
[Mon Apr 1 07:10:08 2024] input: Goodix Capacitive TouchScreen as /devices/pci0000:00/0000:00:17.0/i2c_designware.4/i2c-4/i2c-GDIX1002:00/input/input16

I searched and found this bug report Goodix touchscreen no longer working since kernel 5.7.

Based on what I see in it, I suggest trying one of the Edge ISOs (Linux Mint 21.2 Cinnamon (Edge) Edition ISO or Linux Mint 21.3 Cinnamon (Edge) Edition ISO) which have the 6.2 or 6.5 kernels respectively or the LM20.3 ISO which has the 5.4 kernel. LM20.3 has one more year of support.

There are apparently a number of different Goodix model touchscreens so it is hard to guess what might work for you.

[JannerOyibo]

Since I'm loading Mint from bootable USB drive, no login required as it boots directly into desktop

I forgot you hadn't actually installed Linux Mint and thus are not working with the most recent updates.

I am actually booting to 21.3 Cinnamon and kernel is pre 5.7......

mint@mint:~$ hostnamectl
Static hostname: mint
Icon name: computer-laptop
Chassis: laptop
Machine ID: 909eee248e3644248df7834e7e24c550
Boot ID: 7ed4cd912f3040a8bd8e97d19e065350
Operating System: Linux Mint 21.3
Kernel: Linux 5.15.0-91-generic
Architecture: x86-64
Hardware Vendor: TECLAST
Hardware Model: F6 Plus

I will try to download iso again and retry. Will get back to you.

[JannerOyibo]

Since I'm loading Mint from bootable USB drive, no login required as it boots directly into desktop

I forgot you hadn't actually installed Linux Mint and thus are not working with the most recent updates.

I am actually booting to 21.3 Cinnamon and kernel is pre 5.7......

mint@mint:~$ hostnamectl
Static hostname: mint
Icon name: computer-laptop
Chassis: laptop
Machine ID: 909eee248e3644248df7834e7e24c550
Boot ID: 7ed4cd912f3040a8bd8e97d19e065350
Operating System: Linux Mint 21.3
Kernel: Linux 5.15.0-91-generic
Architecture: x86-64
Hardware Vendor: TECLAST
Hardware Model: F6 Plus

I will try to download iso again and retry. Will get back to you.

So I downloaded the latest ISO from the link provided above..........

And after booting from it on a external USB drive, wifi worked immediately without having to use the rescan command as before AND touchscreen is now working as expected !!
mint@mint:~$ hostnamectl
Static hostname: mint
Icon name: computer-laptop
Chassis: laptop
Machine ID: 8e275cbb688f4652a352b2ae40ceff1d
Boot ID: c5967258231a496cba7f233c9c965faa
Operating System: Linux Mint 21.3
Kernel: Linux 6.5.0-14-generic
Architecture: x86-64
Hardware Vendor: TECLAST
Hardware Model: F6 Plus

That newest kernel (6.5.0-14-generic) seems to have resolved both issues previously seen with original kernel (5.15.0-91-generic).
Just goes to show that sometimes we try to make things more complicated than they actually are !

Thanks for your assistance.

[SMG]

I am actually booting to 21.3 Cinnamon and kernel is pre 5.7......

Actually, you were not. The numbers to the right of the period increase sequentially and 15 is a larger number than 7 so you were booting with a kernel that was released after 5.7.

Glad to hear it is working for you.