* Re: [Bugme-new] [Bug 16050] New: The ibmcam driver is not working
2010-05-28 22:46 ` [Bugme-new] [Bug 16050] New: The ibmcam driver is not working Andrew Morton
@ 2010-05-29 3:19 ` Bill Davidsen
2010-05-29 13:11 ` Bill Davidsen
2010-06-01 8:48 ` Hans de Goede
2 siblings, 0 replies; 10+ messages in thread
From: Bill Davidsen @ 2010-05-29 3:19 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-usb, linux-media, bugzilla-daemon, bugme-daemon
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.
--
Bill Davidsen <davidsen@tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Bugme-new] [Bug 16050] New: The ibmcam driver is not working
2010-05-28 22:46 ` [Bugme-new] [Bug 16050] New: The ibmcam driver is not working Andrew Morton
2010-05-29 3:19 ` Bill Davidsen
@ 2010-05-29 13:11 ` Bill Davidsen
2010-06-01 8:48 ` Hans de Goede
2 siblings, 0 replies; 10+ messages in thread
From: Bill Davidsen @ 2010-05-29 13:11 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-usb, linux-media, bugzilla-daemon, bugme-daemon
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?
--
Bill Davidsen <davidsen@tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Bugme-new] [Bug 16050] New: The ibmcam driver is not working
2010-05-28 22:46 ` [Bugme-new] [Bug 16050] New: The ibmcam driver is not working Andrew Morton
2010-05-29 3:19 ` Bill Davidsen
2010-05-29 13:11 ` Bill Davidsen
@ 2010-06-01 8:48 ` Hans de Goede
2010-06-01 17:19 ` Bill Davidsen
2 siblings, 1 reply; 10+ messages in thread
From: Hans de Goede @ 2010-06-01 8:48 UTC (permalink / raw)
To: Andrew Morton
Cc: linux-usb, linux-media, bugzilla-daemon, bugme-daemon, davidsen
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Bugme-new] [Bug 16050] New: The ibmcam driver is not working
2010-06-01 8:48 ` Hans de Goede
@ 2010-06-01 17:19 ` Bill Davidsen
2010-06-03 13:53 ` Hans de Goede
0 siblings, 1 reply; 10+ messages in thread
From: Bill Davidsen @ 2010-06-01 17:19 UTC (permalink / raw)
To: Hans de Goede
Cc: Andrew Morton, linux-usb, linux-media, bugzilla-daemon,
bugme-daemon
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.
--
Bill Davidsen <davidsen@tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Bugme-new] [Bug 16050] New: The ibmcam driver is not working
2010-06-01 17:19 ` Bill Davidsen
@ 2010-06-03 13:53 ` Hans de Goede
2010-06-03 14:58 ` Bill Davidsen
0 siblings, 1 reply; 10+ messages in thread
From: Hans de Goede @ 2010-06-03 13:53 UTC (permalink / raw)
To: Bill Davidsen
Cc: Andrew Morton, linux-usb, linux-media, bugzilla-daemon,
bugme-daemon
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Bugme-new] [Bug 16050] New: The ibmcam driver is not working
2010-06-03 13:53 ` Hans de Goede
@ 2010-06-03 14:58 ` Bill Davidsen
2010-06-03 15:15 ` Hans de Goede
0 siblings, 1 reply; 10+ messages in thread
From: Bill Davidsen @ 2010-06-03 14:58 UTC (permalink / raw)
To: Hans de Goede
Cc: Andrew Morton, linux-usb, linux-media, bugzilla-daemon,
bugme-daemon
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
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.
--
Bill Davidsen <davidsen@tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
[-- Attachment #2: u.tmp --]
[-- Type: text/plain, Size: 21128 bytes --]
Bus 004 Device 002: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x058f Alcor Micro Corp.
idProduct 0x6362 Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
bcdDevice 1.29
iManufacturer 1 Generic
iProduct 2 Mass Storage Device
iSerial 3 058F312D81B
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 250mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 2.06
iManufacturer 3 Linux 2.6.33.5-112.fc13.x86_64 uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0103 power enable connect
Port 2: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
Bus 003 Device 002: ID 0545:8080 Xirlink, Inc. IBM C-It Webcam
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.01
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 8
idVendor 0x0545 Xirlink, Inc.
idProduct 0x8080 IBM C-It Webcam
bcdDevice 3.0a
iManufacturer 0
iProduct 1 USB IMAGING DEVICE
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 73
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03fe 1x 1022 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x03fe 1x 1022 bytes
bInterval 1
Device Status: 0x0000
(Bus Powered)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 2.06
iManufacturer 3 Linux 2.6.33.5-112.fc13.x86_64 uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.2
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0103 power enable connect
Port 2: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 2.06
iManufacturer 3 Linux 2.6.33.5-112.fc13.x86_64 uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
Bus 001 Device 003: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0764 Cyber Power System, Inc.
idProduct 0x0501 CP1500 AVR UPS
bcdDevice 0.01
iManufacturer 3 CPS
iProduct 1 UPS BF700
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 50mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 374
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Device Status: 0x0001
Self Powered
Bus 001 Device 002: ID 03f0:1d17 Hewlett-Packard LaserJet 1320
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x03f0 Hewlett-Packard
idProduct 0x1d17 LaserJet 1320
bcdDevice 1.00
iManufacturer 1 Hewlett-Packard
iProduct 2 hp LaserJet 1320 series
iSerial 3 00CNFC5383JM
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 78
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 7 Printer
bInterfaceSubClass 1 Printer
bInterfaceProtocol 3 IEEE 1284.4 compatible bidirectional
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 255
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 7 Printer
bInterfaceSubClass 1 Printer
bInterfaceProtocol 2 Bidirectional
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 1
bInterfaceClass 7 Printer
bInterfaceSubClass 1 Printer
bInterfaceProtocol 1 Unidirectional
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0001
Self Powered
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 2.06
iManufacturer 3 Linux 2.6.33.5-112.fc13.x86_64 uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
bPwrOn2PwrGood 1 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0103 power enable connect
Port 2: 0000.0303 lowspeed power enable connect
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [Bugme-new] [Bug 16050] New: The ibmcam driver is not working
2010-06-03 14:58 ` Bill Davidsen
@ 2010-06-03 15:15 ` Hans de Goede
2010-06-03 16:17 ` Bill Davidsen
0 siblings, 1 reply; 10+ messages in thread
From: Hans de Goede @ 2010-06-03 15:15 UTC (permalink / raw)
To: Bill Davidsen
Cc: Andrew Morton, linux-usb, linux-media, bugzilla-daemon,
bugme-daemon
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Bugme-new] [Bug 16050] New: The ibmcam driver is not working
2010-06-03 15:15 ` Hans de Goede
@ 2010-06-03 16:17 ` Bill Davidsen
2010-06-09 14:51 ` Hans de Goede
0 siblings, 1 reply; 10+ messages in thread
From: Bill Davidsen @ 2010-06-03 16:17 UTC (permalink / raw)
To: Hans de Goede
Cc: Andrew Morton, linux-usb, linux-media, bugzilla-daemon,
bugme-daemon
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.
--
Bill Davidsen <davidsen@tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Bugme-new] [Bug 16050] New: The ibmcam driver is not working
2010-06-03 16:17 ` Bill Davidsen
@ 2010-06-09 14:51 ` Hans de Goede
0 siblings, 0 replies; 10+ messages in thread
From: Hans de Goede @ 2010-06-09 14:51 UTC (permalink / raw)
To: Bill Davidsen
Cc: Andrew Morton, linux-usb, linux-media, bugzilla-daemon,
bugme-daemon
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
^ permalink raw reply [flat|nested] 10+ messages in thread