Logitech Quickcam Express USB Address Aquisition Issues
[Pre Note: please CC me all responses, thanks]
Currently, I have a Logitech Quickcam Express webcamera. Unfortunately, it seems to have issues getting assigned an address. I quote the following from dmesg:
usb 1-1.1: new full speed USB device using ehci_hcd and address 11 usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: new full speed USB device using ehci_hcd and address 12 usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: new full speed USB device using ehci_hcd and address 13 usb 1-1.1: device not accepting address 13, error -32 usb 1-1.1: new full speed USB device using ehci_hcd and address 14 usb 1-1.1: device not accepting address 14, error -32
As far as the host goes, I have the following USB hosts:
0000:00:11.0 USB Controller: NEC Corporation USB (rev 43) 0000:00:11.1 USB Controller: NEC Corporation USB (rev 43) 0000:00:11.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
The first is my builtin Intel USB controller, the second is one belkin USB 1.0 card, and another 2.0 card. I've tried it in all three just to verify one of my hosts wasn't broken. Considering my printer works with it, as well as my scanner, I'm sort of thinking that's not an issue.
I searched up google a bit and recieved some warnings about acpi causing problems, so I disabled that, but was still unsucessful in getting that to work. Please let me know if any other information is required. Thanks ahead of time.
Chris White
Quoted 29 lines · Chris White
[Pre Note: please CC me all responses, thanks]
Currently, I have a Logitech Quickcam Express webcamera. Unfortunately, it seems to have issues getting assigned an address. I quote the following from dmesg:
usb 1-1.1: new full speed USB device using
ehci_hcdand address 11 usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: new full speed USB device usingehci_hcdand address 12 usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: new full speed USB device usingehci_hcdand address 13 usb 1-1.1: device not accepting address 13, error -32 usb 1-1.1: new full speed USB device usingehci_hcdand address 14 usb 1-1.1: device not accepting address 14, error -32As far as the host goes, I have the following USB hosts:
0000:00:11.0 USB Controller: NEC Corporation USB (rev 43) 0000:00:11.1 USB Controller: NEC Corporation USB (rev 43) 0000:00:11.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
The first is my builtin Intel USB controller, the second is one belkin USB 1.0 card, and another 2.0 card. I've tried it in all three just to verify one of my hosts wasn't broken. Considering my printer works with it, as well as my scanner, I'm sort of thinking that's not an issue.
Quoted 5 lines
I searched up google a bit and recieved some warnings about acpi causing problems, so I disabled that, but was still unsucessful in getting that to work. Please let me know if any other information is required. Thanks ahead of time.
(Added linux-usb-devel)
Which kernel version?
Did it work OK under a previous kernel version? If so, which?
Quoted 1 line
Which kernel version?
Yes, I was just about to slap myself for fogetting that, it's under greg-kh's 2.6.12.13 git repository sources.
Quoted 1 line
Did it work OK under a previous kernel version? If so, which?
I haven't attempted that, but I'll probably give a 2.6.9/2.4 series kernel a shot later on tommorow night.
Chris White
Quoted 4 lines · Chris White
Quoted 1 line
Did it work OK under a previous kernel version? If so, which?
I haven't attempted that, but I'll probably give a 2.6.9/2.4 series kernel a shot later on tommorow night.
Does that thing work with Windows?
I strongly suspect that it's simply broken at this point.
-- Pete
Quoted 7 lines · Chris White
As far as the host goes, I have the following USB hosts:
0000:00:11.0 USB Controller: NEC Corporation USB (rev 43) 0000:00:11.1 USB Controller: NEC Corporation USB (rev 43) 0000:00:11.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
The first is my builtin Intel USB controller, the second is one belkin USB 1.0 card, and another 2.0 card. I've tried it in all three just to verify one of my hosts wasn't broken. Considering my printer works with it, as well as my scanner, I'm sort of thinking that's not an issue.
It looks like one add-on USB 2.0 card with NEC chip which is backward compatible with USB 1.0. No Intel here.
Signature · 1 line
Ondrej Zary
Quoted 21 lines · Chris White
[Pre Note: please CC me all responses, thanks]
Currently, I have a Logitech Quickcam Express webcamera. Unfortunately, it seems to have issues getting assigned an address. I quote the following from dmesg:
usb 1-1.1: new full speed USB device using
ehci_hcdand address 11 usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: new full speed USB device usingehci_hcdand address 12 usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: device descriptor read/64, error -32
usb 1-1.1: new full speed USB device usingehci_hcdand address 13 usb 1-1.1: device not accepting address 13, error -32 usb 1-1.1: new full speed USB device usingehci_hcdand address 14 usb 1-1.1: device not accepting address 14, error -32As far as the host goes, I have the following USB hosts:
0000:00:11.0 USB Controller: NEC Corporation USB (rev 43) 0000:00:11.1 USB Controller: NEC Corporation USB (rev 43) 0000:00:11.2 USB Controller: NEC Corporation USB 2.0 (rev 04)
Quoted 5 lines
The first is my builtin Intel USB controller, the second is one belkin USB 1.0 card, and another 2.0 card. I've tried it in all three just to verify one of my hosts wasn't broken. Considering my printer works with it, as well as my scanner, I'm sort of thinking that's not an issue.
I searched up google a bit and recieved some warnings about acpi causing problems, so I disabled that, but was still unsucessful in getting that to work. Please let me know if any other information is required. Thanks ahead of time.
Chris White
does the drivers for the Phillips web cams come back to the kernel? because i thought that it was taken out...
http://www.smcc.demon.nl/webcam/
check this site and see if your cam was one of the cams that supported from the driver that discontinue... so if is supported by this driver, download and install it... it works i try it with my cam ;)
On Sunday 07 Aug 2005 12:36, christos gentsis wrote:
[snip]
Quoted 8 lines
Quoted 7 lines
I searched up google a bit and recieved some warnings about acpi causing problems, so I disabled that, but was still unsucessful in getting that to work. Please let me know if any other information is required. Thanks ahead of time.
Chris White
Quoted 9 lines
does the drivers for the Phillips web cams come back to the kernel? because i thought that it was taken out...
http://www.smcc.demon.nl/webcam/
check this site and see if your cam was one of the cams that supported from the driver that discontinue... so if is supported by this driver, download and install it... it works i try it with my cam ;)
The in-kernel pwc driver doesn't work for me either. I highly recommend you try the above if this turns out to not be a hardware fault.
Signature · 6 lines
Cheers, Alistair. 'No sense being pessimistic, it probably wouldn't work anyway.' Third year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK.
Quoted 13 lines · Alistair John Strachan
On Sunday 07 Aug 2005 12:36, christos gentsis wrote:
[snip]Quoted 10 lines
Quoted 6 lines
I searched up google a bit and recieved some warnings about acpi causing problems, so I disabled that, but was still unsucessful in getting that to work. Please let me know if any other information is required. Thanks ahead of time.
Chris White
does the drivers for the Phillips web cams come back to the kernel? because i thought that it was taken out...
Quoted 8 lines
Quoted 5 lines
http://www.smcc.demon.nl/webcam/
check this site and see if your cam was one of the cams that supported from the driver that discontinue... so if is supported by this driver, download and install it... it works i try it with my cam ;)
The in-kernel pwc driver doesn't work for me either. I highly recommend you try the above if this turns out to not be a hardware fault.
Sorry, I didn't even check the link. Try the driver from:
http://www.saillard.org/linux/pwc/
Which seems to work better.
Signature · 6 lines
Cheers, Alistair. 'No sense being pessimistic, it probably wouldn't work anyway.' Third year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK.
Quoted 9 lines
Sorry, I didn't even check the link. Try the driver from:
http://www.saillard.org/linux/pwc/
Which seems to work better.
Signature · 2 lines
Cheers, Alistair.
Err, mine's a logitech camera, why is everyone recommending philips drivers :P?
Chris White
Quoted 8 lines · Chris White
Quoted 5 lines
Sorry, I didn't even check the link. Try the driver from:
http://www.saillard.org/linux/pwc/
Which seems to work better.
Err, mine's a logitech camera, why is everyone recommending philips drivers :P?
Because many of the Logitech cameras are based on the Philips
chipset.
Hugo.
Signature · 3 lines
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 1C335860 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- All hope abandon, Ye who press Enter here. --- Quoted 4 lines · Chris White
Err, mine's a logitech camera, why is everyone recommending philips drivers :P?
Chris White
what happens with the most of the computer peripherals the company that sell it is different with the company that produce it... in this case philips sell the ship for the cameras to other companies and logitech use that chip. in the website say which cameras are based to the philips chip
Quoted 6 lines
Does that thing work with Windows?
I strongly suspect that it's simply broken at this point.
-- Pete
And that is the final answer for $14,000. Looks like I got Yet Another Large Paperweight(tm) to deal with. Yup, this thing is broken. I tried it on my dad's machine today, and Windows chucked the thing out as invalid format right away. Oh well, maybe I should enroll in an electronics class and fix it myself.
Chris White