From: Greg KH <gregkh@linuxfoundation.org>
To: Augusto Ciuffoletti <augusto.ciuffoletti@unipi.it>
Cc: linux-usb@vger.kernel.org
Subject: Re: Problem with the CH341 driver in Ubuntu 20.04
Date: Tue, 5 Jan 2021 17:11:59 +0100 [thread overview]
Message-ID: <X/SPz9Xw7QTM7pVx@kroah.com> (raw)
In-Reply-To: <CAOefePCJzObfprvXHsruzO7sRn4ZkPO2PD_LJae+BhwgyDOytw@mail.gmail.com>
On Tue, Jan 05, 2021 at 04:55:41PM +0100, Augusto Ciuffoletti wrote:
> Hi Greg,
>
> thank you for your reply.
>
> The kernel version I am using is the one currently shipped with the
> latest release of Ubuntu 20.04 (LTS). They will certainly upgrade the
> kernel in the future: if you tell me that the problem does not exist
> in a successive kernel release, I will post the info and close the
> issue.
You will have to work with them, we have no clue what they put in their
kernels.
> You ask me "Where is your usb-to-serial device here?". The point is
> that nothing appears in the lsusb related to the device, although it
> is plugged in (the device receives power). Plugin/unplugging the
> device does not result in any output in syslog/dmesg. I tried to
> manually insert the driver, with no result. The device is not
> discovered at all, but it was (and worked perfectly) in the previous
> Ubuntu release (19.10), and I just guess the kernel was
> 5.3.0-64-generic. So I have no clue..., and it would be helpful to
> have a way to obtain any sort of.
That seems like the root problem here. Work with the Ubuntu developers
to solve that please, once the device is seen then the driver can be
properly bound to the device. Good luck!
greg k-h
prev parent reply other threads:[~2021-01-05 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 15:14 Problem with the CH341 driver in Ubuntu 20.04 Augusto Ciuffoletti
2021-01-05 15:27 ` Greg KH
2021-01-05 15:55 ` Augusto Ciuffoletti
2021-01-05 16:11 ` Greg KH [this message]
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=X/SPz9Xw7QTM7pVx@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=augusto.ciuffoletti@unipi.it \
--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 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.