1 |
>>>> My system seems to have 2 USB controllers, one 1.1 controller (OHCI) |
2 |
>>>> and one 2.0 controller (EHCI): |
3 |
>>>> |
4 |
>>>> 00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev |
5 |
>>>> a3) (prog-if 10 [OHCI]) |
6 |
>>>> Subsystem: Micro-Star International Co., Ltd. Device 7309 |
7 |
>>>> Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21 |
8 |
>>>> Memory at dfe7f000 (32-bit, non-prefetchable) [size=4K] |
9 |
>>>> Capabilities: [44] Power Management version 2 |
10 |
>>>> Kernel driver in use: ohci_hcd |
11 |
>>>> |
12 |
>>>> 00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev |
13 |
>>>> a3) (prog-if 20 [EHCI]) |
14 |
>>>> Subsystem: Micro-Star International Co., Ltd. Device 7309 |
15 |
>>>> Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22 |
16 |
>>>> Memory at dfe7ec00 (32-bit, non-prefetchable) [size=256] |
17 |
>>>> Capabilities: [44] Debug port: BAR=1 offset=0098 |
18 |
>>>> Capabilities: [80] Power Management version 2 |
19 |
>>>> Kernel driver in use: ehci_hcd |
20 |
>>>> |
21 |
>>>> I have 2 Philips USB webcams attached to this system and controlled by |
22 |
>>>> media-video/motion. One of the webcams is not functioning, and I'm |
23 |
>>>> supposed to make sure I don't have both of them attached to the USB |
24 |
>>>> 1.1 controller. How can I do that? I have: |
25 |
>>>> |
26 |
>>>> # lsusb |
27 |
>>>> Bus 001 Device 003: ID 04f9:002a Brother Industries, Ltd |
28 |
>>>> Bus 001 Device 001: ID 1d6b:0002 |
29 |
>>>> Bus 002 Device 003: ID 0471:0329 Philips |
30 |
>>>> Bus 002 Device 002: ID 0471:0329 Philips |
31 |
>>>> Bus 002 Device 001: ID 1d6b:0001 |
32 |
>>>> |
33 |
>>>> Is there any way to find out? |
34 |
>>>> |
35 |
>>>> - Grant |
36 |
>>>> |
37 |
>>>> |
38 |
>>>> |
39 |
>>>> |
40 |
>>> I !think! mine has that too. This is the usb part of my config: |
41 |
>>> |
42 |
>>> root@smoker / # cat /usr/src/linux/.config | grep USB | grep =y |
43 |
>>> CONFIG_USB_HID=y |
44 |
>>> CONFIG_USB_SUPPORT=y |
45 |
>>> CONFIG_USB_ARCH_HAS_HCD=y |
46 |
>>> CONFIG_USB_ARCH_HAS_OHCI=y |
47 |
>>> CONFIG_USB_ARCH_HAS_EHCI=y |
48 |
>>> CONFIG_USB=y |
49 |
>>> CONFIG_USB_DEVICEFS=y |
50 |
>>> CONFIG_USB_OHCI_HCD=y |
51 |
>>> CONFIG_USB_OHCI_LITTLE_ENDIAN=y |
52 |
>>> CONFIG_USB_ACM=y |
53 |
>>> CONFIG_USB_PRINTER=y |
54 |
>>> CONFIG_USB_STORAGE=y |
55 |
>>> root@smoker / # |
56 |
>>> |
57 |
>>> With mine, it tries 2.0 first then goes to the first version. My |
58 |
>>> printer is 2.0 but my camera is the old version, or maybe it is the |
59 |
>>> other way around. I got a memory stick that connects 2.0 to. Anyway, |
60 |
>>> that works here and it may work for you. |
61 |
>>> |
62 |
>>> Dale |
63 |
>>> |
64 |
>> |
65 |
>> So it doesn't matter which slots the webcams are plugged into? |
66 |
>> |
67 |
>> - Grant |
68 |
>> |
69 |
>> |
70 |
>> |
71 |
> |
72 |
> I'm not 100% sure of this but I think it will try to connect sort of |
73 |
> like a IDE drive or even a old dial-up modem does. It just tries to use |
74 |
> the fastest speed it can get a stable connect at. It appears to try the |
75 |
> new faster version first but if that doesn't work it switches to the |
76 |
> slower speed and tries that. Because of my hardware, I have to use both |
77 |
> on mine since some can only use the slow speed and some can use the high |
78 |
> speed. |
79 |
> |
80 |
> As far as the actual connector itself, I'm pretty sure it doesn't matter |
81 |
> at all. It's one chip that controls it all anyway. Just like the PCI |
82 |
> bus, it has one chip and that's it. I know I have switched my printer |
83 |
> and camera around several times and it works the same no matter how I |
84 |
> connect it. |
85 |
> |
86 |
> Now if you have the new version USB with everything hardware wise, you |
87 |
> may be able to disable the old version so that it has no option but to |
88 |
> use the new fast one. That way you can get the fast speed or a error |
89 |
> message that it isn't working. Keep in mind tho, if you have a junky |
90 |
> cable, it will limit the speed a LOT. My printer would not use the new |
91 |
> fast version with a older cable. It does with the new cable tho. My |
92 |
> camera just plain don't work with the new version no matter what. You |
93 |
> may want to get a good quality cable to test with too. |
94 |
> |
95 |
> Someone correct me if I am off base here. |
96 |
> |
97 |
> Dale |
98 |
|
99 |
You seem to be right on here Dale. usbview showed my printer |
100 |
connected to the 2.0 controller and a webcam connected to the 1.1 |
101 |
controller, so I unplugged the printer and plugged the webcam into |
102 |
it's slot and it still showed up under 1.1. So there doesn't appear |
103 |
to be any slot/controller correlation. |
104 |
|
105 |
This is a problem for me though. My webcams can't both operate on the |
106 |
1.1 controller at the same time due to the bandwidth limitation of the |
107 |
1.1 controller. I need them both on 2.0 or one on each controller, |
108 |
but they are always grabbed by the 1.1 controller. Even worse, I |
109 |
disabled support for 1.1 in the kernel so only 2.0 was supported and |
110 |
the webcams didn't show up at all. Could they be USB 1.1 only? |
111 |
Shouldn't a 1.1 device operate on a 2.0 controller? |
112 |
|
113 |
- Grant |