Your message dated Wed, 23 May 2007 04:19:56 -0300
with message-id <[EMAIL PROTECTED]>
and subject line closing old bug
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: qc-usb-source
Version: 0.6.2-2
Package builds module 'quickcam' successfully. But after installing and
loading module camera doesn't work. The problem appeared after I
upgraded from 2.6.8-1-k7 to 2.6.8-2-k7. I'm able to use camera only if I
switch back to previous kernel 2.6.8-1-k7 or if I build sources found
at http://home.mag.cx/messenger/source/qc-usb-messenger-0.8.tar.gz (its
date is 2005.01.04)
Here is the dmesg output - just 2 (two) lines for kernel 2.6.8-2-k7:
Linux video capture interface: v1.00
usbcore: registered new driver quickcam
Here is what demsg say when module built and used with 2.6.8-1-k7 kernel:
$ dmesg | grep quick
quickcam [16.551305]: ----------LOADING QUICKCAM MODULE------------
quickcam [16.551315]: struct quickcam size: 2192
usbcore: registered new driver quickcam
quickcam: QuickCam USB camera found (driver version QuickCam
Messenger/Communicate USB $Date: 2004/12/21 10:00:00 $)
quickcam: Kernel:2.6.8-1-k7 bus:1 class:FF subclass:FF vendor:046D
product:08F0
quickcam [16.572717]: poisoning qc in qc_usb_init
quickcam [16.580687]: E00A contains 08F0
quickcam: Sensor VV6450 detected
quickcam: Registered device: /dev/video1
My opinion is that package in Debian "testing" is based on old version
of the driver. Could this be a problem?
I'm using Debian "Sarge", kernel 2.6.8-2-k7, on AMD Barton 2600+, nVidia
nForce 2 chipset. I have correct kernel-headers installed on my PC.
There are not other issues with USB devices that I noticed.
--- End Message ---
--- Begin Message ---
Hi,
from what can be seen in the logs provided, this is a mistake, as this
driver doesn't support this usb id:
P: Vendor=046d ProdID=08f0 Rev= 1.00
I think the reporter was using the messenger driver, as can be seen in
one of the dmesg outputs.
Closing this now, reopen if necessary.
--
MartÃn Ferrari
--- End Message ---
