From: Chris <chris@cyber-anlage.de>
To: linux-usb@vger.kernel.org
Subject: pl2303 : unknown device type
Date: Tue, 27 Jul 2021 14:37:23 +0200 [thread overview]
Message-ID: <2560053.x2KRyp2eMa@cyber-bucket> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 185 bytes --]
This problem was introduced with 5.13 and still persists in 5.13.5
After downgrading to 5.12.x, everything works like expected. Tested on
archlinux. The device is an "ICP-DAS I-7561"
[-- Attachment #1.2: dmsg --]
[-- Type: text/plain, Size: 530 bytes --]
dmesg -w
[ 1999.689678] usb 2-4: new full-speed USB device number 3 using ohci-pci
[ 1999.919763] usb 2-4: New USB device found, idVendor=067b, idProduct=2303, bcdDevice=5d.ca
[ 1999.919772] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1999.919775] usb 2-4: Product: USB-Serial Controller
[ 1999.919777] usb 2-4: Manufacturer: Prolific Technology Inc.
[ 1999.923348] pl2303 2-4:1.0: pl2303 converter detected
[ 1999.923365] pl2303 2-4:1.0: unknown device type, please report to linux-usb@vger.kernel.org
[-- Attachment #1.3: lsusb --]
[-- Type: text/plain, Size: 2468 bytes --]
lsusb -v
Bus 002 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Action MA-8910P
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x067b Prolific Technology, Inc.
idProduct 0x2303 PL2303 Serial Port / Mobile Action MA-8910P
bcdDevice 5d.ca
iManufacturer 1 Prolific Technology Inc.
iProduct 2 USB-Serial Controller
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0027
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-07-27 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 12:37 Chris [this message]
2021-07-27 13:24 ` pl2303 : unknown device type Oliver Neukum
2021-07-29 10:15 ` Johan Hovold
2021-07-29 10:10 ` Johan Hovold
2021-07-29 13:55 ` Chris
2021-07-30 7:32 ` Johan Hovold
2021-07-30 12:11 ` Johan Hovold
2021-07-30 12:21 ` [PATCH] USB: serial: pl2303: fix HX type detection Johan Hovold
2021-07-30 12:29 ` Greg KH
2021-07-30 15:11 ` Johan Hovold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2560053.x2KRyp2eMa@cyber-bucket \
--to=chris@cyber-anlage.de \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).