mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Chris White <chriswhite@gentoo.org>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: Logitech Quickcam Express USB Address Aquisition Issues
Date: Sun, 7 Aug 2005 00:36:39 -0700	[thread overview]
Message-ID: <20050807003639.0aa1d9b3.akpm@osdl.org> (raw)
In-Reply-To: <20050807160222.0c4ee412@localhost>

Chris White <chriswhite@gentoo.org> wrote:
>
> [Pre Note: please CC me all responses, thanks]
> 
> Currently, I have a Logitech Quickcam Express webcamera.  Unfortunately, it
> seems to have issues getting assigned an address.  I quote the following
> from dmesg:
> 
> usb 1-1.1: new full speed USB device using ehci_hcd and address 11
> usb 1-1.1: device descriptor read/64, error -32
> usb 1-1.1: device descriptor read/64, error -32
> usb 1-1.1: new full speed USB device using ehci_hcd and address 12
> usb 1-1.1: device descriptor read/64, error -32
> usb 1-1.1: device descriptor read/64, error -32
> usb 1-1.1: new full speed USB device using ehci_hcd and address 13
> usb 1-1.1: device not accepting address 13, error -32
> usb 1-1.1: new full speed USB device using ehci_hcd and address 14
> usb 1-1.1: device not accepting address 14, error -32
> 
> As far as the host goes, I have the following USB hosts:
> 
> 0000:00:11.0 USB Controller: NEC Corporation USB (rev 43)
> 0000:00:11.1 USB Controller: NEC Corporation USB (rev 43)
> 0000:00:11.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
> 
> The first is my builtin Intel USB controller, the second is one belkin
> USB 1.0 card, and another 2.0 card.  I've tried it in all three just to
> verify one of my hosts wasn't broken.  Considering my printer works with
> it, as well as my scanner, I'm sort of thinking that's not an issue.
> 
> I searched up google a bit and recieved some warnings about acpi causing
> problems, so I disabled that, but was still unsucessful in getting that to
> work.  Please let me know if any other information is required.  Thanks
> ahead of time.
> 

(Added linux-usb-devel)

Which kernel version?

Did it work OK under a previous kernel version?  If so, which?


  reply	other threads:[~2005-08-07  7:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07  7:02 Chris White
2005-08-07  7:36 ` Andrew Morton [this message]
2005-08-07  7:11   ` Chris White
     [not found]   ` <mailman.1123400700.14696.linux-kernel2news@redhat.com>
2005-08-07  8:40     ` Pete Zaitcev
2005-08-08  8:57       ` Chris White
2005-08-07  9:23 ` Ondrej Zary
2005-08-07 11:36 ` christos gentsis
2005-08-07 18:54   ` Alistair John Strachan
2005-08-07 18:58     ` Alistair John Strachan
2005-08-08  2:38       ` Chris White
2005-08-08  8:27         ` Hugo Mills
2005-08-08  9:02         ` christos gentsis

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=20050807003639.0aa1d9b3.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=chriswhite@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®