From: Greg KH <greg@kroah.com>
To: Will Newton <will@misconception.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.18 and VIA USB
Date: Mon, 20 May 2002 13:49:14 -0700 [thread overview]
Message-ID: <20020520204914.GD25182@kroah.com> (raw)
In-Reply-To: <E179T0J-0002gQ-00.2002-05-19-16-53-53@mail6.svr.pol.co.uk> <20020520175353.GB24443@kroah.com> <E179tpB-0000D2-00.2002-05-20-21-32-09@cmailg4.svr.pol.co.uk>
On Mon, May 20, 2002 at 09:34:42PM +0100, Will Newton wrote:
> On Monday 20 May 2002 6:53 pm, you wrote:
>
> > > hub.c: USB new device connect on bus1/2, assigned device number 7
> > > usb.c: USB device not accepting new address=7 (error=-110)
> > > hub.c: Cannot enable port 2 of hub 1, disabling port.
> > > hub.c: Maybe the USB cable is bad?
> >
> > Which USB host controller driver are you using?
>
> usb-uhci.c: $Revision: 1.275 $ time 11:55:11 Apr 14 2002
> usb-uhci.c: High bandwidth mode enabled
> usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
When trying out 2.4.19-pre, also try the uhci.c driver.
> > And are you sure your cable isn't bad? :)
>
> No, and it isn't feasible for me to test this right now, as it's a custom (I
> think) cable and I have only one cable and one USB capable machine.
Ah, custom cable, not good :(
> Also a google search for "Maybe the USB cable is bad?" seems to turn up only
> VIA users.
Yes, there are a lot of odd VIA problems, but then again, there are a
lot of USB cables out there in the wild that are not compliant with the
USB spec :)
greg k-h
next prev parent reply other threads:[~2002-05-20 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-19 15:56 Kernel 2.4.18 and VIA USB Will Newton
2002-05-20 17:53 ` Greg KH
[not found] ` <E179tpB-0000D2-00.2002-05-20-21-32-09@cmailg4.svr.pol.co.uk>
2002-05-20 20:49 ` Greg KH [this message]
2002-05-20 21:16 ` Kristofer T. Karas
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=20020520204914.GD25182@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=will@misconception.org.uk \
/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