* Prolific Technology pl2303: unknown device type
[not found] <CAA0uCUZV0Jdc5HJnPg=Rqv06+UVYAudbx5qUNOatE9ZZsP6vsA@mail.gmail.com>
@ 2022-06-18 6:42 ` Giles Roadnight
2022-06-19 9:41 ` Giles Roadnight
2022-06-20 7:05 ` Johan Hovold
0 siblings, 2 replies; 5+ messages in thread
From: Giles Roadnight @ 2022-06-18 6:42 UTC (permalink / raw)
To: linux-usb
Hi
I am trying to connect a Prolific pl2303 to my raspberry pi 4 running
raspberry pi os 64 bit. When I look at dmesg I get the following
output:
[ 31.714397] cam-dummy-reg: disabling
[ 44.046197] usb 1-1.1: USB disconnect, device number 3
[ 47.254348] usb 1-1.1: new full-speed USB device number 4 using xhci_hcd
[ 47.361386] usb 1-1.1: New USB device found, idVendor=067b,
idProduct=23a3, bcdDevice= 6.05
[ 47.361402] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 47.361407] usb 1-1.1: Product: USB-Serial Controller
[ 47.361412] usb 1-1.1: Manufacturer: Prolific Technology Inc.
[ 47.361417] usb 1-1.1: SerialNumber: ALBAb115819
[ 47.364081] pl2303 1-1.1:1.0: pl2303 converter detected
[ 47.364106] pl2303 1-1.1:1.0: unknown device type, please report to
linux-usb@vger.kernel.org
so I followed the example and emailed this address!
and with lsusb:
lsusb -v
Bus 001 Device 004: ID 067b:23a3 Prolific Technology, Inc. USB-Serial Controller
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x067b Prolific Technology, Inc.
idProduct 0x23a3
bcdDevice 6.05
iManufacturer 1 Prolific Technology Inc.
iProduct 2 USB-Serial Controller
iSerial 3 ALBAb115819
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
Any help much appreciated. Thanks
Giles Roadnight
http://giles.roadnight.name
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Prolific Technology pl2303: unknown device type
2022-06-18 6:42 ` Prolific Technology pl2303: unknown device type Giles Roadnight
@ 2022-06-19 9:41 ` Giles Roadnight
2022-06-20 7:05 ` Johan Hovold
1 sibling, 0 replies; 5+ messages in thread
From: Giles Roadnight @ 2022-06-19 9:41 UTC (permalink / raw)
To: linux-usb
I have managed to get this working on an older version of the kernel.
I have tried raspberry pi os buster (debian version 10) and the serial
port was correctly created.
It was Raspberry pi os bullseye (debian 11) that this did not work for.
Giles Roadnight
http://giles.roadnight.name
Giles Roadnight
http://giles.roadnight.name
On Sat, 18 Jun 2022 at 07:42, Giles Roadnight <giles.roadnight@gmail.com> wrote:
>
> Hi
>
> I am trying to connect a Prolific pl2303 to my raspberry pi 4 running
> raspberry pi os 64 bit. When I look at dmesg I get the following
> output:
>
> [ 31.714397] cam-dummy-reg: disabling
> [ 44.046197] usb 1-1.1: USB disconnect, device number 3
> [ 47.254348] usb 1-1.1: new full-speed USB device number 4 using xhci_hcd
> [ 47.361386] usb 1-1.1: New USB device found, idVendor=067b,
> idProduct=23a3, bcdDevice= 6.05
> [ 47.361402] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 47.361407] usb 1-1.1: Product: USB-Serial Controller
> [ 47.361412] usb 1-1.1: Manufacturer: Prolific Technology Inc.
> [ 47.361417] usb 1-1.1: SerialNumber: ALBAb115819
> [ 47.364081] pl2303 1-1.1:1.0: pl2303 converter detected
> [ 47.364106] pl2303 1-1.1:1.0: unknown device type, please report to
> linux-usb@vger.kernel.org
>
> so I followed the example and emailed this address!
>
> and with lsusb:
>
> lsusb -v
> Bus 001 Device 004: ID 067b:23a3 Prolific Technology, Inc. USB-Serial Controller
> Couldn't open device, some information will be missing
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 0
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> idVendor 0x067b Prolific Technology, Inc.
> idProduct 0x23a3
> bcdDevice 6.05
> iManufacturer 1 Prolific Technology Inc.
> iProduct 2 USB-Serial Controller
> iSerial 3 ALBAb115819
> 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
>
> Any help much appreciated. Thanks
>
> Giles Roadnight
> http://giles.roadnight.name
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Prolific Technology pl2303: unknown device type
2022-06-18 6:42 ` Prolific Technology pl2303: unknown device type Giles Roadnight
2022-06-19 9:41 ` Giles Roadnight
@ 2022-06-20 7:05 ` Johan Hovold
2022-06-20 7:10 ` Giles Roadnight
1 sibling, 1 reply; 5+ messages in thread
From: Johan Hovold @ 2022-06-20 7:05 UTC (permalink / raw)
To: Giles Roadnight; +Cc: linux-usb
On Sat, Jun 18, 2022 at 07:42:43AM +0100, Giles Roadnight wrote:
> Hi
>
> I am trying to connect a Prolific pl2303 to my raspberry pi 4 running
> raspberry pi os 64 bit. When I look at dmesg I get the following
> output:
>
> [ 31.714397] cam-dummy-reg: disabling
> [ 44.046197] usb 1-1.1: USB disconnect, device number 3
> [ 47.254348] usb 1-1.1: new full-speed USB device number 4 using xhci_hcd
> [ 47.361386] usb 1-1.1: New USB device found, idVendor=067b,
> idProduct=23a3, bcdDevice= 6.05
> [ 47.361402] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 47.361407] usb 1-1.1: Product: USB-Serial Controller
> [ 47.361412] usb 1-1.1: Manufacturer: Prolific Technology Inc.
> [ 47.361417] usb 1-1.1: SerialNumber: ALBAb115819
> [ 47.364081] pl2303 1-1.1:1.0: pl2303 converter detected
> [ 47.364106] pl2303 1-1.1:1.0: unknown device type, please report to
> linux-usb@vger.kernel.org
>
> so I followed the example and emailed this address!
>
> and with lsusb:
This has been fixed in mainline and backported to the relevant stable
trees (5.17.2, 5.16.19, 5.15.33) at the beginning of April.
You didn't mention which kernel you use, but updating to a more recent
one should fix this.
Johan
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Prolific Technology pl2303: unknown device type
2022-06-20 7:05 ` Johan Hovold
@ 2022-06-20 7:10 ` Giles Roadnight
2022-06-20 7:19 ` Johan Hovold
0 siblings, 1 reply; 5+ messages in thread
From: Giles Roadnight @ 2022-06-20 7:10 UTC (permalink / raw)
To: Johan Hovold; +Cc: linux-usb
Yes thanks. The new kernel has not made it to the default raspberry pi
repos yet so doing apt upgrade does not fix it. I did find a tool that
does update the kernel in an "unsafe" way and that has fixed it for
me.
I know that raspberry pi OS and its versions and repositories are not
your concern as you work on the kernel but as a linux simpleton these
were the issues preventing me from getting the update!
Thanks for your response.
Giles Roadnight
http://giles.roadnight.name
On Mon, 20 Jun 2022 at 08:05, Johan Hovold <johan@kernel.org> wrote:
>
> On Sat, Jun 18, 2022 at 07:42:43AM +0100, Giles Roadnight wrote:
> > Hi
> >
> > I am trying to connect a Prolific pl2303 to my raspberry pi 4 running
> > raspberry pi os 64 bit. When I look at dmesg I get the following
> > output:
> >
> > [ 31.714397] cam-dummy-reg: disabling
> > [ 44.046197] usb 1-1.1: USB disconnect, device number 3
> > [ 47.254348] usb 1-1.1: new full-speed USB device number 4 using xhci_hcd
> > [ 47.361386] usb 1-1.1: New USB device found, idVendor=067b,
> > idProduct=23a3, bcdDevice= 6.05
> > [ 47.361402] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> > [ 47.361407] usb 1-1.1: Product: USB-Serial Controller
> > [ 47.361412] usb 1-1.1: Manufacturer: Prolific Technology Inc.
> > [ 47.361417] usb 1-1.1: SerialNumber: ALBAb115819
> > [ 47.364081] pl2303 1-1.1:1.0: pl2303 converter detected
> > [ 47.364106] pl2303 1-1.1:1.0: unknown device type, please report to
> > linux-usb@vger.kernel.org
> >
> > so I followed the example and emailed this address!
> >
> > and with lsusb:
>
> This has been fixed in mainline and backported to the relevant stable
> trees (5.17.2, 5.16.19, 5.15.33) at the beginning of April.
>
> You didn't mention which kernel you use, but updating to a more recent
> one should fix this.
>
> Johan
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Prolific Technology pl2303: unknown device type
2022-06-20 7:10 ` Giles Roadnight
@ 2022-06-20 7:19 ` Johan Hovold
0 siblings, 0 replies; 5+ messages in thread
From: Johan Hovold @ 2022-06-20 7:19 UTC (permalink / raw)
To: Giles Roadnight; +Cc: linux-usb
On Mon, Jun 20, 2022 at 08:10:22AM +0100, Giles Roadnight wrote:
> Yes thanks. The new kernel has not made it to the default raspberry pi
> repos yet so doing apt upgrade does not fix it. I did find a tool that
> does update the kernel in an "unsafe" way and that has fixed it for
> me.
Good to hear you found a way to resolve this.
Johan
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-06-20 7:19 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CAA0uCUZV0Jdc5HJnPg=Rqv06+UVYAudbx5qUNOatE9ZZsP6vsA@mail.gmail.com>
2022-06-18 6:42 ` Prolific Technology pl2303: unknown device type Giles Roadnight
2022-06-19 9:41 ` Giles Roadnight
2022-06-20 7:05 ` Johan Hovold
2022-06-20 7:10 ` Giles Roadnight
2022-06-20 7:19 ` Johan Hovold
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.