From: Greg KH <gregkh@linuxfoundation.org>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: linux-usb@vger.kernel.org
Subject: Re: USB hub problem
Date: Sun, 15 Aug 2021 08:28:48 +0200 [thread overview]
Message-ID: <YRi0ICEZM+1eAyNu@kroah.com> (raw)
In-Reply-To: <3481f401-1d52-d5a1-d983-4b5f7046704b@eyal.emu.id.au>
On Sun, Aug 15, 2021 at 09:32:06AM +1000, Eyal Lebedinsky wrote:
> I have an external 4-way USB3.0 hub (I actually have two of them) That do not behave as expected.
> It is an XCD XCDESSUSBH4BK. It is unpowered. I am on fedora 34, kernel 5.13.8-200.fc34.x86_64
>
> For starters, I found that attaching a USB SSD does not allow booting from it.
That is up to your BIOS, not Linux.
> I then found that when attaching my phone it is not recognized.
In what way?
> I searched the hub model and IDs but did not find relevant information.
> Is there an official list of supported hubs (or devices)?
No, as any list would instantly be out of date.
> Here is what it looks like.
>
> When the hub is attached (no phone) I see
> Bus 001 Device 048: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
> and
> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
> |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
> |__ Port 2: Dev 48, If 0, Class=Hub, Driver=hub/4p, 480M
> Attaching the phone does not add a device.
>
> Detaching/attaching the hub (with the phone already plugged in) I get
> Bus 001 Device 052: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy A5 (MTP)
> Bus 001 Device 051: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
> and
> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
> |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
> |__ Port 2: Dev 51, If 0, Class=Hub, Driver=hub/4p, 480M
> |__ Port 1: Dev 52, If 1, Class=Communications, Driver=cdc_acm, 480M
> |__ Port 1: Dev 52, If 2, Class=CDC Data, Driver=cdc_acm, 480M
> |__ Port 1: Dev 52, If 0, Class=Imaging, Driver=, 480M
> |__ Port 1: Dev 52, If 3, Class=Vendor Specific Class, Driver=, 480M
> and the phone is recognized and accessible as MTP device.
Great, so when does this not work? This shows a successful device
found.
thanks,
greg k-h
next prev parent reply other threads:[~2021-08-15 6:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 23:32 USB hub problem Eyal Lebedinsky
2021-08-15 6:28 ` Greg KH [this message]
2021-08-15 7:47 ` Eyal Lebedinsky
2021-08-15 8:54 ` Felipe Balbi
2021-08-15 10:35 ` Eyal Lebedinsky
2021-08-16 10:30 ` Oliver Neukum
2021-08-16 12:25 ` Eyal Lebedinsky
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=YRi0ICEZM+1eAyNu@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=eyal@eyal.emu.id.au \
--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