CPIA webcam support has sysfs problem

Bug #84470 reported by grendel970
6
Affects Status Importance Assigned to Milestone
Linux
Invalid
Undecided
Unassigned
Ubuntu
Invalid
Undecided
Unassigned
linux (Ubuntu)
Expired
Undecided
Unassigned
linux-source-2.6.15 (Ubuntu)
Won't Fix
Undecided
Chuck Short
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.15-27-686

I have an old intel Qx3 microscope which is treated like a webcam. This did work in the 2.4 kernel series upon research,
but nor I am getting the following errors when plugging in:

Feb 10 19:25:37 localhost kernel: [18467685.216000] usb 4-4.3: new full speed USB device using ehci_hcd and address 13
Feb 10 19:25:37 localhost kernel: [18467685.344000] USB CPiA camera found
Feb 10 19:25:37 localhost kernel: [18467685.344000] videodev: "CPiA Camera" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/
Feb 10 19:25:40 localhost kernel: [18467688.520000] CPiA Version: 1.33 (2.10)
Feb 10 19:25:40 localhost kernel: [18467688.520000] CPiA PnP-ID: 0813:0001:0106
Feb 10 19:25:40 localhost kernel: [18467688.520000] VP-Version: 1.0 0100

It lods up /proc/cpia/video0 and I can even cat that file and get the parameters, as well as turning the toplight on by echoing to this device. Now video0 which is part of v4l will not work, I've tried vidcat, gqcam, streamer, nothing works.

After a while of messing around with it I can get kernel errors like this:
Feb 10 19:12:12 localhost kernel: [18466880.484000] cpia data error: [1] len=0, status=FFFFFFEE
Feb 10 19:12:12 localhost kernel: [18466880.484000] cpia data error: [2] len=0, status=FFFFFFEE
Feb 10 19:12:12 localhost kernel: [18466880.484000] cpia data error: [3] len=0, status=FFFFFFEE
Feb 10 19:12:12 localhost kernel: [18466880.484000] cpia data error: [4] len=0, status=FFFFFFEE
Feb 10 19:12:12 localhost kernel: [18466880.484000] cpia data error: [5] len=0, status=FFFFFFEE
Feb 10 19:12:12 localhost kernel: [18466880.484000] cpia data error: [6] len=0, status=FFFFFFEE
Feb 10 19:12:12 localhost kernel: [18466880.492000] cpia data error: [0] len=0, status=FFFFFFEE
Feb 10 19:13:03 localhost kernel: [18466930.696000] cpia data error: [0] len=0, status=FFFFFFEE
Feb 10 19:13:03 localhost kernel: [18466930.696000] cpia data error: [1] len=0, status=FFFFFFEE

An strace on a vidcat shows it hanging on an ioctl(4, VIDIOMCAPTURE
if that helps..

Here is my v4lconf:
v4l-conf: using X11 display :0.0
dga: version 2.0
X Error of failed request: XF86DGANoDirectVideoMode
  Major opcode of failed request: 137 (XFree86-DGA)
  Minor opcode of failed request: 1 (XF86DGAGetVideoLL)
  Serial number of failed request: 13
  Current serial number in output stream: 13

Please let me know if you need anything else.

Revision history for this message
Chuck Short (zulcss) wrote :

Have this fixed in my git tree for gutsy.

Changed in linux-source-2.6.15:
assignee: nobody → zulcss
Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

This bug has had no activity for a while. This is a check to see if there is still interest in investigating this bug report.
Has this been fixed in Gutsy and/or later?
Can "linux-source-2.6.15" be marked "Won't Fix" or otherwise?

Changed in linux-source-2.6.15:
status: New → Incomplete
Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
DougL (dlarue) wrote :

I just tried my QX3 microscope with both Gutsy and the latest Hardy beta and both worked with gqcam.

I plugged in the USB device, made sure the cpia module is loaded, installed gqcam and then ran "gqcam -v /dev/video0". I also echo'ed "toplight: on" to /proc/cpia/video0 and that turned on the toplight but gqcam has to be running for that to work.

From the kernel output there is no sysfs support yet.
Here is the kernel messages in Gutsy when the device was plugged in and looking at Hardy, it's the same:

[ 7973.144000] Linux video capture interface: v2.00
[ 7973.156000] V4L-Driver for Vision CPiA based cameras v1.2.3
[ 7973.156000] Since in-kernel colorspace conversion is not allowed, it is disabled by default now. Users should fix the applications in case they don't work without conversion reenabled by setting the 'colorspace_conv' module parameter to 1
[ 7973.160000] USB driver for Vision CPiA based cameras v1.2.3
[ 7973.164000] USB CPiA camera found
[ 7973.164000] videodev: "CPiA Camera" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/
[ 7973.904000] CPiA Version: 1.33 (2.10)
[ 7973.904000] CPiA PnP-ID: 0813:0001:0106
[ 7973.904000] VP-Version: 1.0 0100
[ 7973.904000] usbcore: registered new interface driver cpia

Changed in linux-source-2.6.22:
status: Incomplete → Confirmed
Changed in linux-source-2.6.15:
status: Incomplete → Confirmed
Changed in linux-source-2.6.24:
status: New → Confirmed
Changed in linux:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
exactt (giesbert) wrote :

problem still exists on latest hardy...

Revision history for this message
yokurani (yokurani) wrote :

same Problem here with Terratec Terracam USB

lsusb:

Bus 003 Device 005: ID 0553:0002 STMicroelectronics Imaging Division (VLSI Vision) CPiA WebCam

/var/log/messages:

May 30 21:07:05 nb1 kernel: [ 2131.230587] USB driver for Vision CPiA based cameras v1.2.3
May 30 21:07:05 nb1 kernel: [ 2131.230885] USB CPiA camera found
May 30 21:07:05 nb1 kernel: [ 2131.233114] videodev: "CPiA Camera" has no release callback. Please fix your driver for proper sysfs support, see http://lwn.net/Articles/36850/
May 30 21:07:06 nb1 kernel: [ 2132.101595] CPiA Version: 1.30 (2.10)
May 30 21:07:06 nb1 kernel: [ 2132.101603] CPiA PnP-ID: 0553:0002:0100
May 30 21:07:06 nb1 kernel: [ 2132.101608] VP-Version: 1.0 0100
May 30 21:07:06 nb1 kernel: [ 2132.101637] usbcore: registered new interface driver cpia

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Beginning with the Hardy Heron 8.04 development cycle the kernel source package naming convention changed from "linux-source-2.6.xx" to just "linux". Going forward, kernel bugs should now be reported against the "linux" package. I'm removing the linux-source-2.6.24 task since this is already reported against the "linux" package.

Changed in linux-source-2.6.24:
status: New → Invalid
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi All,

This bug has been open for quite a while. Can anyone confirm this issue remains with the latest Jaunty Jackalope 9.04 release - http://www.ubuntu.com/getubuntu/download ?

Additionally against the linux-source-2.6.22 task this is being closed as the 2.6.22 gutsy kernel has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.10-eol. I'm also closing the upstream Linux task as there does not appear to be an upstream bug to link this report to.

Lastly, this is not likely to qualify for a Stable Release Update to dapper so I'm closing the linux-source-2.6.15 task as well.

Again, this will remain open against the actively developed kernel for now if we can get testing and feedback. Thanks.

Changed in linux-source-2.6.22 (Ubuntu):
status: Confirmed → Incomplete
Changed in linux:
status: New → Invalid
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux-source-2.6.15 (Ubuntu):
status: Confirmed → Won't Fix
Changed in linux-source-2.6.22 (Ubuntu):
status: Incomplete → Won't Fix
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.