From: Greg KH <gregkh@linuxfoundation.org>
To: Eduard-Bogdan Budai <eduard.budai@rcs-rds.ro>
Cc: linux-usb@vger.kernel.org
Subject: Re: Bug report for pl2303 converter (ATEN USB to serial Bridge, idVendor=067b, idProduct=23a3, bcdDevice= 1.05)
Date: Wed, 9 Feb 2022 12:39:16 +0100 [thread overview]
Message-ID: <YgOn5PIQWOrcv146@kroah.com> (raw)
In-Reply-To: <35338b26-41db-e772-235a-502caa30e00f@rcs-rds.ro>
On Wed, Feb 09, 2022 at 12:13:28PM +0200, Eduard-Bogdan Budai wrote:
> Thank you very much for your answer.
>
> The newest kernel that is in the standard Ubuntu 20.04 repositories is
> today Linux 5.13.0-28-generic #31~20.04.1-Ubuntu SMP Wed Jan 19 14:08:10
> UTC 2022 x86_64). After moving from 5.13.0-27-generic #29~20.04.1-Ubuntu
> to the newest 5.13.0-28-generic #31~20.04.1-Ubuntu, the dmesg showed:
>
> [Wed Feb 9 11:38:51 2022] usb 3-2: new full-speed USB device number 4
> using xhci_hcd
> [Wed Feb 9 11:38:51 2022] usb 3-2: New USB device found, idVendor=067b,
> idProduct=23a3, bcdDevice= 1.05
> [Wed Feb 9 11:38:51 2022] usb 3-2: New USB device strings: Mfr=1,
> Product=2, SerialNumber=0
> [Wed Feb 9 11:38:51 2022] usb 3-2: Product: ATEN USB to Serial Bridge
> [Wed Feb 9 11:38:51 2022] usb 3-2: Manufacturer: Prolific Technology
> Inc.
> [Wed Feb 9 11:38:51 2022] usbcore: registered new interface driver
> usbserial_generic
> [Wed Feb 9 11:38:51 2022] usbserial: USB Serial support registered for
> generic
> [Wed Feb 9 11:38:51 2022] usbcore: registered new interface driver
> pl2303
> [Wed Feb 9 11:38:51 2022] usbserial: USB Serial support registered for
> pl2303
> [Wed Feb 9 11:38:51 2022] pl2303 3-2:1.0: unknown device type, please
> report to linux-usb@vger.kernel.org
>
> A 5.4.0-99-generic #112~18.04.1-Ubuntu SMP Thu Feb 3 14:09:57 UTC 2022
> x86_64 from a Ubuntu 18.04 recognizes the same adapter as a ttyUSB0
> (which is what is needed to be used).
>
> Unfortunately, the environment in which happened what I described below
> has certain restrictions that don't allow me to try a newer kernel than
> the newest that is in the standard Ubuntu repositories...
I would suggest going and getting support from those that are imposing
those odd restrictions on you, as they are not allowing you to use the
hardware you need to use :(
Good luck!
greg k-h
next prev parent reply other threads:[~2022-02-09 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <10d4dbe9-4b17-aeb5-0abe-bf0829173c1d@rcs-rds.ro>
2022-01-20 15:08 ` Bug report for pl2303 converter (ATEN USB to serial Bridge, idVendor=067b, idProduct=23a3, bcdDevice= 1.05) Eduard-Bogdan Budai
2022-02-08 10:15 ` Greg KH
2022-02-09 10:13 ` Eduard-Bogdan Budai
2022-02-09 11:39 ` Greg KH [this message]
2022-02-09 14:08 ` 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=YgOn5PIQWOrcv146@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=eduard.budai@rcs-rds.ro \
--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