Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 81871 - USB Audio not detected on Logitech QuickCam Pro 4000
USB Audio not detected on Logitech QuickCam Pro 4000
Product: Red Hat Linux
Classification: Retired
Component: kudzu (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-01-14 15:04 EST by Hetz Ben Hamo
Modified: 2014-03-16 22:33 EDT (History)
1 user (show)

See Also:
Fixed In Version: FC4
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-23 15:58:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Hetz Ben Hamo 2003-01-14 15:04:46 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
I have Logitech QuickCam Pro 4000.

Cam is working OK with phoebe, but the Audio section shows as "unknown" in
Kudzu, and it comes in an endless loop (when booting)..

The module for this cam for sound is simply "audio" module - USB Audio sound,
which is part of the kernel.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. connect the cam
2. see results as described above

Actual Results:  endless loop in kudzu with this cam (unless selecting either Do
nothing or Ignore, but it's not always helping...

Expected Results:  to load the module ;)

Additional info:

If you look at testers mailing list - someone at redhat has the exact cam. 

my lsusb output can be taken from:

Comment 1 Bill Nottingham 2005-09-23 15:58:35 EDT
This should be more or less handled with current kudzu. Note that as of FC4,
there is no UI that pops up, and the modules should be loaded automatically via

Note You need to log in before you can comment on or make changes to this bug.