ch341 communication problem from kernel.org

[andyb2000]

Issue with esp8266 esptool communications.

This is a bug known at kernel.org
"Bug 214131 - ch341 communication problem"
https://bugzilla.kernel.org/show_bug.cgi?id=214131

It has a resolution, however it appears this has not been pushed out to Ubuntu yet so it is affecting my system.

The issue causes esptool not to be able to communicate with esp8266/esp32 USB chips.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-88-generic 5.4.0-88.99
ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
Uname: Linux 5.4.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: browna 3672 F.... pulseaudio
 /dev/snd/controlC0: browna 3672 F.... pulseaudio
CasperMD5CheckResult: skip
Date: Tue Oct 12 22:33:36 2021
HibernationDevice: # RESUME=UUID=5ec6ef50-65f9-40c2-87ee-3a7a9cd01da7
InstallationDate: Installed on 2015-05-07 (2350 days ago)
InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Acer Aspire VN7-571
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=14353e0d-b4a9-4bfa-b347-cc7a99bdc8bd ro quiet splash i8042.nopnp vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-88-generic N/A
 linux-backports-modules-5.4.0-88-generic N/A
 linux-firmware 1.187.17
SourcePackage: linux
StagingDrivers: ashmem_linux
UpgradeStatus: Upgraded to focal on 2020-11-16 (330 days ago)
dmi.bios.date: 09/12/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire VN7-571
dmi.board.vendor: Acer
dmi.board.version: V1.08
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: V1.08
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd09/12/2014:svnAcer:pnAspireVN7-571:pvrV1.08:rvnAcer:rnAspireVN7-571:rvrV1.08:cvnChassisManufacturer:ct10:cvrV1.08:
dmi.product.family: Sharkbay System
dmi.product.name: Aspire VN7-571
dmi.product.sku: Aspire VN7-571_091B_1.08
dmi.product.version: V1.08
dmi.sys.vendor: Acer

[andyb2000 (andy-thebmwz3)]

Sorry, I realised I didn't have the esp8266 chip connected.

After connecting, here is brief output:

[26645.130953] usb 2-3: new full-speed USB device number 13 using xhci_hcd
[26645.283500] usb 2-3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.54
[26645.283508] usb 2-3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[26645.283513] usb 2-3: Product: USB2.0-Ser!
[26645.285027] ch341 2-3:1.0: ch341-uart converter detected
[26645.285578] usb 2-3: ch341-uart converter now attached to ttyUSB0
root@butterwicks-five:~# lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 002 Device 003: ID 1bcf:2c6e Sunplus Innovation Technology Inc. HD WebCam
Bus 002 Device 005: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth
Bus 002 Device 013: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@butterwicks-five:~#

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[sfromis (sfromis)]

I can confirm this bug blocking me from flashing boards with ESP32 and ESP8266. Not updating other Ubuntu boxes for now. On Discord, I've also been in contact with other people not able to flash similar boards. My setup works with a CP2104 USB/serial adapter chip, different driver, same purpose.

[TomasKovacik (nail-nodomain)]

hello

today I have to roll back to 4.15.0-158-generic on my 18.04 box because of the same bug.
these kernels on 18.04 are affected:
4.15.0-159-generic
4.15.0-161-generic
5.4.0-89-generic

t.

[sfromis (sfromis)]

I'm not seeing this problem anymore after recent software updates.