From: Sean Young <sean@mess.org>
To: Wade Berrier <wberrier@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: mceusb xhci issue?
Date: Mon, 25 Apr 2016 18:15:06 +0100 [thread overview]
Message-ID: <20160425171506.GA25277@gofer.mess.org> (raw)
In-Reply-To: <20160425040632.GD15140@berrier.lan>
On Sun, Apr 24, 2016 at 10:06:33PM -0600, Wade Berrier wrote:
> Hello,
>
> I have a mceusb compatible transceiver that only seems to work with
> certain computers. I'm testing this on centos7 (3.10.0) and fedora23
> (4.4.7).
>
> The only difference I can see is that the working computer shows
> "using uhci_hcd" and the non working shows "using xhci_hcd".
>
> Here's the dmesg output of the non-working version:
>
> ---------------------
>
> [ 217.951079] usb 1-5: new full-speed USB device number 10 using xhci_hcd
> [ 218.104087] usb 1-5: device descriptor read/64, error -71
> [ 218.371010] usb 1-5: config 1 interface 0 altsetting 0 endpoint 0x1 has an invalid bInterval 0, changing to 32
> [ 218.371019] usb 1-5: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 0, changing to 32
That's odd. Can you post a "lsusb -vvv" of the device please?
Thanks,
Sean
next prev parent reply other threads:[~2016-04-25 17:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 4:06 mceusb xhci issue? Wade Berrier
2016-04-25 17:15 ` Sean Young [this message]
2016-04-26 3:16 ` Wade Berrier
2016-04-27 20:07 ` Sean Young
2016-05-15 2:29 ` Wade Berrier
2016-05-18 14:52 ` Wade Berrier
2016-07-09 14:59 ` Mauro Carvalho Chehab
2016-07-12 15:52 ` Alan Stern
2016-08-11 20:18 ` Alan Stern
2016-09-10 19:58 ` Wade Berrier
2016-09-15 19:13 ` Alan Stern
2016-09-15 22:48 ` Wade Berrier
2016-09-16 14:24 ` [PATCH] USB: change bInterval default to 10 ms Alan Stern
2016-09-16 15:02 ` Mauro Carvalho Chehab
2016-09-16 14:25 ` mceusb xhci issue? Alan Stern
2016-09-16 15:03 ` Mauro Carvalho Chehab
2016-09-15 19:37 ` Alan Stern
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=20160425171506.GA25277@gofer.mess.org \
--to=sean@mess.org \
--cc=linux-media@vger.kernel.org \
--cc=wberrier@gmail.com \
/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.