Bug 16050 - The ibmcam driver is not working
The ibmcam driver is not working
Status: CLOSED INSUFFICIENT_DATA
Product: Drivers
Classification: Unclassified
Component: USB
All Linux
: P1 normal
Assigned To: Greg Kroah-Hartman
https://bugzilla.redhat.com/show_bug....
:
Depends on:
Blocks: 15310
  Show dependency treegraph
 
Reported: 2010-05-25 23:02 UTC by Bill Davidsen
Modified: 2010-07-23 11:36 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.34
Tree: Mainline
Regression: Yes


Attachments

Description Bill Davidsen 2010-05-25 23:02:22 UTC
This driver has been working, and around the 1st of May I updated my Fedora kernel (FC13-RC) to current. The camera stopped working, so I built the latest 2.6.34-rc version and verified the problem. When 2.6.34 final released I repeated the test and the driver is still not working.

Originally reported against Fedora (not going to be fixed in FC13) the information in the Fedora report may be enough to identify the problem. I can do a bit of test almost any day, but the cams are on a video monitoring system, so I'm not able to do long bisects and such.
Comment 1 Andrew Morton 2010-05-28 22:47:16 UTC
(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Tue, 25 May 2010 23:02:23 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=16050
> 
>                URL: https://bugzilla.redhat.com/show_bug.cgi?id=588900
>            Summary: The ibmcam driver is not working
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.34
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: USB
>         AssignedTo: greg@kroah.com
>         ReportedBy: davidsen@tmr.com
>         Regression: Yes
> 
> 
> This driver has been working, and around the 1st of May I updated my Fedora
> kernel (FC13-RC) to current. The camera stopped working, so I built the latest
> 2.6.34-rc version and verified the problem. When 2.6.34 final released I
> repeated the test and the driver is still not working.
> 
> Originally reported against Fedora (not going to be fixed in FC13) the
> information in the Fedora report may be enough to identify the problem. I can
> do a bit of test almost any day, but the cams are on a video monitoring system,
> so I'm not able to do long bisects and such.
> 

It's a 2.6.33 -> 2.6.34 regression, I think.  I don't know whether it's
a v4l problem or a USB one..
Comment 2 Bill Davidsen 2010-05-29 04:36:11 UTC
Andrew Morton wrote:
> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Tue, 25 May 2010 23:02:23 GMT
> bugzilla-daemon@bugzilla.kernel.org wrote:
>
>   
>> https://bugzilla.kernel.org/show_bug.cgi?id=16050
>>
>>                URL: https://bugzilla.redhat.com/show_bug.cgi?id=588900
>>            Summary: The ibmcam driver is not working
>>            Product: Drivers
>>            Version: 2.5
>>     Kernel Version: 2.6.34
>>           Platform: All
>>         OS/Version: Linux
>>               Tree: Mainline
>>             Status: NEW
>>           Severity: normal
>>           Priority: P1
>>          Component: USB
>>         AssignedTo: greg@kroah.com
>>         ReportedBy: davidsen@tmr.com
>>         Regression: Yes
>>
>>
>> This driver has been working, and around the 1st of May I updated my Fedora
>> kernel (FC13-RC) to current. The camera stopped working, so I built the latest
>> 2.6.34-rc version and verified the problem. When 2.6.34 final released I
>> repeated the test and the driver is still not working.
>>
>> Originally reported against Fedora (not going to be fixed in FC13) the
>> information in the Fedora report may be enough to identify the problem. I can
>> do a bit of test almost any day, but the cams are on a video monitoring system,
>> so I'm not able to do long bisects and such.
>>
>>     
>
> It's a 2.6.33 -> 2.6.34 regression, I think.  I don't know whether it's
> a v4l problem or a USB one..
>
>   
Sounds right, there's quite a bit of version information in the redhat 
BZ entry I noted, and I thought it was a Fedora issue at first. Then 
when Fedora support said it wasn't going to be fixed for FC13 I tried 
the kernel.org source instead. There are some initial comments from 
zaitcev@redhat.com saying there were patches in git to make it work with 
fswebcam (don't use it), but it doesn't seem to with cheese, motion, or 
xawtv, so I'm unsure how "fixed" it is.

I'm ready to try stable releases as they come out, or git releases if 
need be. I have issues getting time on build machine or time of video 
server to do bisect, unfortunately. I looked at the patches all the way 
back to 2.6.27, and ibmcam looks inert, so the changes in v4l would be 
my first guess. Sorry I can't do more.
Comment 3 Bill Davidsen 2010-05-29 13:11:44 UTC
Andrew Morton wrote:
> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Tue, 25 May 2010 23:02:23 GMT
> bugzilla-daemon@bugzilla.kernel.org wrote:
>
>   
>> https://bugzilla.kernel.org/show_bug.cgi?id=16050
>>
>>                URL: https://bugzilla.redhat.com/show_bug.cgi?id=588900
>>            Summary: The ibmcam driver is not working
>>            Product: Drivers
>>            Version: 2.5
>>     Kernel Version: 2.6.34
>>           Platform: All
>>         OS/Version: Linux
>>               Tree: Mainline
>>             Status: NEW
>>           Severity: normal
>>           Priority: P1
>>          Component: USB
>>         AssignedTo: greg@kroah.com
>>         ReportedBy: davidsen@tmr.com
>>         Regression: Yes
>>
>>
>> This driver has been working, and around the 1st of May I updated my Fedora
>> kernel (FC13-RC) to current. The camera stopped working, so I built the latest
>> 2.6.34-rc version and verified the problem. When 2.6.34 final released I
>> repeated the test and the driver is still not working.
>>
>> Originally reported against Fedora (not going to be fixed in FC13) the
>> information in the Fedora report may be enough to identify the problem. I can
>> do a bit of test almost any day, but the cams are on a video monitoring system,
>> so I'm not able to do long bisects and such.
>>
>>     
>
> It's a 2.6.33 -> 2.6.34 regression, I think.  I don't know whether it's
> a v4l problem or a USB one..
>
>   
I noted this problem in Fedora kernels:

2.6.33.2-41.fc13.x86_64 - worked
2.6.33.2-57.fc13.x86_64 - fails

The first was on my video server 4/21 when I left for a trip to the midwest,
and worked perfectly with the "motion" app for the entire ten days. When I
installed the current update on 5/2 or so it stopped working. I did go back
and boot the older kernel and it still works, not some bizarre hardware thing.

After boot I have /dev/video0 as the ibmcam, but after first attempted use
the device is gone. Since it worked in older kernels I rebooted and tried
running it in an older VM (fc9) using USB passthru to KVM. That also didn't
work. Does that tell anyone more than it tells me?
Comment 4 Anonymous Emailer 2010-06-01 09:26:55 UTC
Reply-To: hdegoede@redhat.com

Hi,

On 05/29/2010 12:46 AM, Andrew Morton wrote:
>
> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Tue, 25 May 2010 23:02:23 GMT
> bugzilla-daemon@bugzilla.kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=16050
>>
>>                 URL: https://bugzilla.redhat.com/show_bug.cgi?id=588900
>>             Summary: The ibmcam driver is not working
>>             Product: Drivers
>>             Version: 2.5
>>      Kernel Version: 2.6.34
>>            Platform: All
>>          OS/Version: Linux
>>                Tree: Mainline
>>              Status: NEW
>>            Severity: normal
>>            Priority: P1
>>           Component: USB
>>          AssignedTo: greg@kroah.com
>>          ReportedBy: davidsen@tmr.com
>>          Regression: Yes
>>
>>
>> This driver has been working, and around the 1st of May I updated my Fedora
>> kernel (FC13-RC) to current. The camera stopped working, so I built the latest
>> 2.6.34-rc version and verified the problem. When 2.6.34 final released I
>> repeated the test and the driver is still not working.
>>
>> Originally reported against Fedora (not going to be fixed in FC13) the
>> information in the Fedora report may be enough to identify the problem. I can
>> do a bit of test almost any day, but the cams are on a video monitoring system,
>> so I'm not able to do long bisects and such.
>>
>
> It's a 2.6.33 ->  2.6.34 regression, I think.  I don't know whether it's
> a v4l problem or a USB one..
>

It may very well be a regression, I don't know. But in general the usbvideo drivers
(of which the ibmcam is one) have been unmaintained for a long while, and they are
still v4l1 drivers. I've been slowly working on converting all old v4l1 usb webcam
drivers to the gspca usb webcam driver framework, removing a lot of code duplication
(and other cruft such as controls being controlled through module parameters)
from these drivers and making them v4l2 drivers in the progress.

I really bough 2 ibmcam driver using webcams in the US and had them shipped to the
Netherlands esp. for this purpose. I hope to have a new gspca subdriver to replace
ibmcam soon.

I know this is not really a fix for the problems with the existing ibmcam driver, but
as it is destined to be replaced soon anyways I think this is the best way forward.

Regards,

Hans
Comment 5 Bill Davidsen 2010-06-01 17:19:43 UTC
Hans de Goede wrote:
> Hi,
>
> On 05/29/2010 12:46 AM, Andrew Morton wrote:
>>
>> (switched to email.  Please respond via emailed reply-to-all, not via 
>> the
>> bugzilla web interface).
>>
>> On Tue, 25 May 2010 23:02:23 GMT
>> bugzilla-daemon@bugzilla.kernel.org wrote:
>>
>>> https://bugzilla.kernel.org/show_bug.cgi?id=16050
>>>
>>>                 URL: https://bugzilla.redhat.com/show_bug.cgi?id=588900
>>>             Summary: The ibmcam driver is not working
>>>             Product: Drivers
>>>             Version: 2.5
>>>      Kernel Version: 2.6.34
>>>            Platform: All
>>>          OS/Version: Linux
>>>                Tree: Mainline
>>>              Status: NEW
>>>            Severity: normal
>>>            Priority: P1
>>>           Component: USB
>>>          AssignedTo: greg@kroah.com
>>>          ReportedBy: davidsen@tmr.com
>>>          Regression: Yes
>>>
>>>
>>> This driver has been working, and around the 1st of May I updated my 
>>> Fedora
>>> kernel (FC13-RC) to current. The camera stopped working, so I built 
>>> the latest
>>> 2.6.34-rc version and verified the problem. When 2.6.34 final 
>>> released I
>>> repeated the test and the driver is still not working.
>>>
>>> Originally reported against Fedora (not going to be fixed in FC13) the
>>> information in the Fedora report may be enough to identify the 
>>> problem. I can
>>> do a bit of test almost any day, but the cams are on a video 
>>> monitoring system,
>>> so I'm not able to do long bisects and such.
>>>
>>
>> It's a 2.6.33 ->  2.6.34 regression, I think.  I don't know whether it's
>> a v4l problem or a USB one..
>>
>
> It may very well be a regression, I don't know. But in general the 
> usbvideo drivers
> (of which the ibmcam is one) have been unmaintained for a long while, 
> and they are
> still v4l1 drivers. I've been slowly working on converting all old 
> v4l1 usb webcam
> drivers to the gspca usb webcam driver framework, removing a lot of 
> code duplication
> (and other cruft such as controls being controlled through module 
> parameters)
> from these drivers and making them v4l2 drivers in the progress.
>
> I really bough 2 ibmcam driver using webcams in the US and had them 
> shipped to the
> Netherlands esp. for this purpose. I hope to have a new gspca 
> subdriver to replace
> ibmcam soon.
>
> I know this is not really a fix for the problems with the existing 
> ibmcam driver, but
> as it is destined to be replaced soon anyways I think this is the best 
> way forward.
>
I tried the 2.6.34-11.fc13.x86_64 kernel, and the cameras "sort of" work 
again, I had to change the size being used in the motion.conf file to 
match what I found in the messages log, then I get imaging again, but 
the kernel has multiple OOPS issues, which I have sent off to the 
kerneloops folks. I don't feel comfortable using that kernel, even if it 
doesn't actually die (or hasn't yet).

In case you don't have this information, here is a line from lsusb:
  Bus 003 Device 002: ID 0545:8080 Xirlink, Inc. IBM C-It Webcam

Hopefully the items you have ordered are the same model.
Comment 6 Anonymous Emailer 2010-06-03 13:51:57 UTC
Reply-To: hdegoede@redhat.com

Hi,

On 06/01/2010 07:19 PM, Bill Davidsen wrote:
> Hans de Goede wrote:
 >
> In case you don't have this information, here is a line from lsusb:
> Bus 003 Device 002: ID 0545:8080 Xirlink, Inc. IBM C-It Webcam
>
> Hopefully the items you have ordered are the same model.
>

I have the same usb-id, but I'm working on the driver now and it
seems XirLink distinguishes between different models by bcdversion,
instead of using different usb ids for each product.

Can you send me a mail with the output of "lsusb -v", then I can
see if you have the same version as I have for testing.

Regards,

Hans
Comment 7 Bill Davidsen 2010-06-03 14:59:11 UTC
Hans de Goede wrote:
> Hi,
>
> On 06/01/2010 07:19 PM, Bill Davidsen wrote:
>> Hans de Goede wrote:
> >
>> In case you don't have this information, here is a line from lsusb:
>> Bus 003 Device 002: ID 0545:8080 Xirlink, Inc. IBM C-It Webcam
>>
>> Hopefully the items you have ordered are the same model.
>>
>
> I have the same usb-id, but I'm working on the driver now and it
> seems XirLink distinguishes between different models by bcdversion,
> instead of using different usb ids for each product.
>
> Can you send me a mail with the output of "lsusb -v", then I can
> see if you have the same version as I have for testing.
>

Sure, attached.
Comment 8 Anonymous Emailer 2010-06-03 15:14:21 UTC
Reply-To: hdegoede@redhat.com

Hi,

On 06/03/2010 04:58 PM, Bill Davidsen wrote:
> Hans de Goede wrote:
>> Hi,
>>
>> On 06/01/2010 07:19 PM, Bill Davidsen wrote:
>>> Hans de Goede wrote:
>> >
>>> In case you don't have this information, here is a line from lsusb:
>>> Bus 003 Device 002: ID 0545:8080 Xirlink, Inc. IBM C-It Webcam
>>>
>>> Hopefully the items you have ordered are the same model.
>>>
>>
>> I have the same usb-id, but I'm working on the driver now and it
>> seems XirLink distinguishes between different models by bcdversion,
>> instead of using different usb ids for each product.
>>
>> Can you send me a mail with the output of "lsusb -v", then I can
>> see if you have the same version as I have for testing.
>>
>
> Sure, attached.
>

Thx,

Your device has a revision of 3.0a (the firmware programmers did not
seem to fully grasp the concept of the d in bcd (it stands for decimal),
which is different from mine which is revision 3.01 . Your version is
referred to as a model2 by the old driver, where as mine is a model3.

This is both bad and good news, the bad news is I cannot give you an
already tested driver to fix your issues. The good news is, that this
means that, assuming that you are willing to help out with testing, we
can now also verify that model 2 cams will work with the new driver.

So would you be willing to test the new driver (when it is finished) ?

Regards,

Hans
Comment 9 Bill Davidsen 2010-06-03 16:18:44 UTC
Hans de Goede wrote:
> Hi,
>
> On 06/03/2010 04:58 PM, Bill Davidsen wrote:
>> Hans de Goede wrote:
>>> Hi,
>>>
>>> On 06/01/2010 07:19 PM, Bill Davidsen wrote:
>>>> Hans de Goede wrote:
>>> >
>>>> In case you don't have this information, here is a line from lsusb:
>>>> Bus 003 Device 002: ID 0545:8080 Xirlink, Inc. IBM C-It Webcam
>>>>
>>>> Hopefully the items you have ordered are the same model.
>>>>
>>>
>>> I have the same usb-id, but I'm working on the driver now and it
>>> seems XirLink distinguishes between different models by bcdversion,
>>> instead of using different usb ids for each product.
>>>
>>> Can you send me a mail with the output of "lsusb -v", then I can
>>> see if you have the same version as I have for testing.
>>>
>>
>> Sure, attached.
>>
>
> Thx,
>
> Your device has a revision of 3.0a (the firmware programmers did not
> seem to fully grasp the concept of the d in bcd (it stands for decimal),
> which is different from mine which is revision 3.01 . Your version is
> referred to as a model2 by the old driver, where as mine is a model3.
>
> This is both bad and good news, the bad news is I cannot give you an
> already tested driver to fix your issues. The good news is, that this
> means that, assuming that you are willing to help out with testing, we
> can now also verify that model 2 cams will work with the new driver.
>
> So would you be willing to test the new driver (when it is finished) ?
>
Sure, just let me know what kernel the patch is against. As you say, my 
cams are Model2 in the old nomenclature.

Interesting that the size is set to 352x240 rather than CIF 352x288. And 
while xawtv sort of works with the latest 2.6.33.5-112.fc13.x86_64 koji 
kernel, cheese doesn't, not that I need it, but it worked on the early 
kernels.
Comment 10 Anonymous Emailer 2010-06-09 14:50:18 UTC
Reply-To: hdegoede@redhat.com

Hi,

On 06/03/2010 06:17 PM, Bill Davidsen wrote:
>> So would you be willing to test the new driver (when it is finished) ?
>>
> Sure, just let me know what kernel the patch is against. As you say, my
> cams are Model2 in the old nomenclature.
>
> Interesting that the size is set to 352x240 rather than CIF 352x288. And
> while xawtv sort of works with the latest 2.6.33.5-112.fc13.x86_64 koji
> kernel, cheese doesn't, not that I need it, but it worked on the early
> kernels.
>

Ok, I've a version of the new driver ready for testing.


To test you need the latest libv4l, and my gspca tree:

First update libv4l, do:
git clone git://linuxtv.org/v4l-utils.git
cd v4l-utils/lib
And then follow the instructions here:
http://hansdegoede.livejournal.com/7622.html

Then get my gspca tree, and compile and install it, note
that this is based on the special hg v4l-dvb tree, which
is meant as an overlay to your running kernel, so doing this
will replace the v4l and dvb subsystems of your kernel
while leaving the rest as is:
hg clone http://linuxtv.org/hg/~hgoede/ibmcam
cd ibmcam
make menuconfig
<deselect the ibmcam driver and make any other changes you wish>
make
sudo make install
<reboot, yes really>

Now after the reboot do the following as root:
echo 63 > /sys/module/gspca_main/parameters/debug

And then try using your camera with a v4l app such
as cheese, camorama or some such.

Please collect the output of dmesg and mail it to me.

Also please try running at a resolution of 176x144.

If things don't work (chances are they won't) please try
to describe what exactly is the problem. ie is the
image shifted left / right / up / down with some garbage
or black area being shown on the other side, is there no
image at all is it to dark / light, are the colors wrong etc.

Thanks & Regards,

Hans
Comment 11 Rafael J. Wysocki 2010-07-09 23:24:36 UTC
Handled-By : Hans de Goede <hdegoede@redhat.com>

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