USB won't recognize sophisticated devices.

[Gary Sams]

I have just replaced my hard drive and motherboard. (ECS GeForce6100SM-M.
AMD Athlon 5000 X2 dual core processor). Windows XP home.

Most things works fine. Cameras, printers, digital dictating machines, 3
button mice and basic keyboards are all recognized as soon as they are
plugged into any USB port, and work well.

When I plug in my Logitech 5 button mouse (MX 510), it doesn't work.
Depending on which USB port I plug it into I am told either that the device
is not recognized, or the device is accurately recognized, but I am told it
is not functioning. I have the same problem with my Microsoft Digital Media
Pro Keyboard.

Both devices work fine if I plug them into an adapter, and connect them to
the keyboard and mouse ports, rather than USB.

I have just bought a new cordless mouse for my laptop - Logitech VX
revolution. I tried this on my desktop and got the same error messages.

I tried upgrading the PSU from 350w (the bare minimum supported by the
motherboard) to a new 600w unit, but to no effect),

Any other ideas?

Gary

 

[Bob Harris]

Do those devices have special drivers that you should install before
connecting them? Check the manufacture's support website for details.

 

[Gary Sams]

Yes they do, and I have installed the latest drivers. As I say, they work
fine, including all bells and whistles, as long as I connect them to the
PS/2 ports, rather than the USB ports,

Gary

 

[Ian D]

Yes they do, and I have installed the latest drivers. As I say, they work
fine, including all bells and whistles, as long as I connect them to the
PS/2 ports, rather than the USB ports,

Gary

Even without drivers, they should be recognized as legacy devices
same as the 3 button mouse you say worked. If they work through
the PS/2 ports use them that way. I have USB keyboard and mouse
and have them connected via PS/2. I find the mouse to be a bit more
responsive, and it saves USB ports for other devices.

Back to your problem, it sounds like a motherboard issue. When you
plug the keyboard and mouse into USB ports, do they show any signs
of life, ie., operating LEDs? It almost looks as if your MB USB ports
can't supply sufficient power for the devices.

 

[Gary Sams]

Even without drivers, they should be recognized as legacy devices
same as the 3 button mouse you say worked. If they work through
the PS/2 ports use them that way. I have USB keyboard and mouse
and have them connected via PS/2. I find the mouse to be a bit more
responsive, and it saves USB ports for other devices.

Back to your problem, it sounds like a motherboard issue. When you
plug the keyboard and mouse into USB ports, do they show any signs
of life, ie., operating LEDs? It almost looks as if your MB USB ports
can't supply sufficient power for the devices.

As for showing signs of life, its variable. The red optical light under the
mouse sometimes lights up and sometimes doesn't - either way it doesn't work
at all. Same with the keyboard, it sometimes shows the lights which should
come on, and sometimes doesn't. In fact on one occasion, after a lot of
unplugging and plugging, I got the keyboard recognized and working. This
produced another problem - windows refused to shut down. When I tried to
shut down it insisted on restarting. I had to disconnect it to turn off the
computer!

As you say, I now have no problems, due to using adapters to the PS/2 ports.
I am just concerned that there is clearly a USB problem, which could cause
difficulties with other devices in the future. I also suspect a power
problem, which is why I upgraded the PSU.

I bought the motherboard from Maplin, and have queried the problem with
them. They have no idea what the problem could be. Do I really need the
hassle of trying to get the motherboard replaced, and then having to fit a
new one?

Gary

 

[Ian D]

As for showing signs of life, its variable. The red optical light under
the mouse sometimes lights up and sometimes doesn't - either way it
doesn't work at all. Same with the keyboard, it sometimes shows the lights
which should come on, and sometimes doesn't. In fact on one occasion,
after a lot of unplugging and plugging, I got the keyboard recognized and
working. This produced another problem - windows refused to shut down.
When I tried to shut down it insisted on restarting. I had to disconnect
it to turn off the computer!

As you say, I now have no problems, due to using adapters to the PS/2
ports. I am just concerned that there is clearly a USB problem, which
could cause difficulties with other devices in the future. I also suspect
a power problem, which is why I upgraded the PSU.

I bought the motherboard from Maplin, and have queried the problem with
them. They have no idea what the problem could be. Do I really need the
hassle of trying to get the motherboard replaced, and then having to fit a
new one?

Gary

Here's another thought. Can you enter and navigate the BIOS after
bootup with that keyboard plugged into a USB port, and will the
mouse LEDs light at the same time? If not, it's definitely a motherboard
issue, and if they do work at POST, but not after XP starts, it looks like
a motherboard USB driver issue. Also, did you check in Device
Manager to see if the USB2 or Enhanced USB is enabled? I assume you
installed the motherboard drivers.

ID

 

[Gary Sams]

Here's another thought. Can you enter and navigate the BIOS after
bootup with that keyboard plugged into a USB port, and will the
mouse LEDs light at the same time? If not, it's definitely a motherboard
issue, and if they do work at POST, but not after XP starts, it looks like
a motherboard USB driver issue. Also, did you check in Device
Manager to see if the USB2 or Enhanced USB is enabled? I assume you
installed the motherboard drivers.

ID

I can enter and navigate BIOS after bootup with the keyboard plugged into a
USB port, and once XP starts it doesn't work. However, the mouse shows no
lights or other sign of life at either stage.

I can find no reference to USB2 in Device Manager. There is a 'standard
enhanced USB to PCI host controller'. I would not assume the drivers were
properly installed. I paid a local computer ' expert' to install my new
motherboard, but the fact that he kept asking me where I thought the various
connections should go, did not fill me with confidence!

How can I ensure that USB2 and Enhanced USB are enabled, and the drivers are
installed?

Thanks

Gary

 

[Ian D]

I can enter and navigate BIOS after bootup with the keyboard plugged into
a USB port, and once XP starts it doesn't work. However, the mouse shows
no lights or other sign of life at either stage.

I can find no reference to USB2 in Device Manager. There is a 'standard
enhanced USB to PCI host controller'. I would not assume the drivers were
properly installed. I paid a local computer ' expert' to install my new
motherboard, but the fact that he kept asking me where I thought the
various connections should go, did not fill me with confidence!

How can I ensure that USB2 and Enhanced USB are enabled, and the drivers
are installed?

Thanks

Gary

I would say your lack of confidence in your 'expert' is well founded. The
word enhanced indicates USB2 of some sort, but the description is
puzzling, so I have some other questions. Besides the direct motherboard
mounted USB sockets, do you have any mounted on a backplane slot
cover, any case front USB ports, or a separate USB PCI card?

 

[Gary Sams]

I would say your lack of confidence in your 'expert' is well founded. The
word enhanced indicates USB2 of some sort, but the description is
puzzling, so I have some other questions. Besides the direct motherboard
mounted USB sockets, do you have any mounted on a backplane slot
cover, any case front USB ports, or a separate USB PCI card?

The spec for the motherboard says '2 x USB 2.0 headers support additional
4 USB Ports'. I have 4 ports on the front of the case and 4 at the back. My
only PCI card is for firewire,

Thanks

Gary

 

[Paul]

The spec for the motherboard says '2 x USB 2.0 headers support additional
4 USB Ports'. I have 4 ports on the front of the case and 4 at the back. My
only PCI card is for firewire,

Thanks

Gary

"Standard Enhanced" seen in Device Manager, is shorthand for USB2.0 .
It would typically be seen, coming from an Intel Southbridge with USB2.0
capability. In the example here, there is a PCI card with a NEC USB2 chip,
and also an Intel Southbridge with USB2 capabilities, so ports are coming
from two places, complicating the example.

http://www.usbman.com/Guides/checking_for_usb_2.htm

Checking the specific "Enhanced" USB entries, and looking at the driver
list for the specific item, would show a Microsoft USB2 driver or drivers
installed.

A mouse shows lights, according to the light type. My current optical mouse
uses a strong red LED source. The obvious red color is a giveaway. A
laser mouse may use an infrared laser, which is invisible if it is far
enough into the infrared part of the spectrum.

Use UVCView and see whether USB device enumerations are visible, to detect
a device when plugged in. This archived page has a download in the
upper right hand corner. (Don't let the "video" part of the title
fool you - it works for other USB devices as well, and my spare USB
mouse can be seen just fine.) This works best for devices plugged into
connectors directly on the computer.

UVCView – Diagnostic Tool for USB Video Class Hardware
http://web.archive.org/web/20070516...com/whdc/device/stream/vidcap/UVCViewdwn.mspx

If you see your laser mouse in UVCView, it means the USB chip inside
the mouse, is talking to the computer. But it doesn't guarantee that
the rest of the mouse (laser/optical_array) works.

Paul

 

[Gary Sams]

"Standard Enhanced" seen in Device Manager, is shorthand for USB2.0 .
It would typically be seen, coming from an Intel Southbridge with USB2.0
capability. In the example here, there is a PCI card with a NEC USB2 chip,
and also an Intel Southbridge with USB2 capabilities, so ports are coming
from two places, complicating the example.

http://www.usbman.com/Guides/checking_for_usb_2.htm

Checking the specific "Enhanced" USB entries, and looking at the driver
list for the specific item, would show a Microsoft USB2 driver or drivers
installed.

A mouse shows lights, according to the light type. My current optical
mouse
uses a strong red LED source. The obvious red color is a giveaway. A
laser mouse may use an infrared laser, which is invisible if it is far
enough into the infrared part of the spectrum.

Use UVCView and see whether USB device enumerations are visible, to detect
a device when plugged in. This archived page has a download in the
upper right hand corner. (Don't let the "video" part of the title
fool you - it works for other USB devices as well, and my spare USB
mouse can be seen just fine.) This works best for devices plugged into
connectors directly on the computer.

UVCView – Diagnostic Tool for USB Video Class Hardware
http://web.archive.org/web/20070516...com/whdc/device/stream/vidcap/UVCViewdwn.mspx

If you see your laser mouse in UVCView, it means the USB chip inside
the mouse, is talking to the computer. But it doesn't guarantee that
the rest of the mouse (laser/optical_array) works.

Paul

Thanks - I have tried USBView.

It shows a Standard OpenHCD USB Host Controller (I'll call this 1) and a
Standard Enhanced PCI to USB Host Controller (2), each with 10 ports.

Plugging the mouse into different ports gives different results.
A rear port - it appears under 1. It is recognized as Logitech USB MX510
Optical Mouse. There is a yellow exclamation mark and the mouse does not
light up. Device information says at the top - ERROR no string descriptor
for index 2, and further down: ERROR- No open pipes. Further down under
'device descriptor' there are 2 further ERRORs - no string descriptor for
index 1 iProduct, and index 2 iSerial Number.

A different rear port - it appears under 1. It is correctly recognized.
There is no yellow error. It lights up but doesn't work. Under detail the
following messages could be problems.
Current Config Value 0x01 (arrow) Device Bus Speed: Low
wMaxPacket size 0x0007 = Invalid bus speed for USB Video Class
CAUTION: This may be an invalid bInterfaceProtocol iInterface:
0x00
(note that plugging in a three button optical cordless mouse produces the
same messages, but it works).

Front ports mainly produce the same result as the first described above. On
one occasion, which I can't now reproduce, it appeared under Controller 2,
but showed no lights and the same yellow errors.
Sometimes it shows a yellow error under controller 1 and is not recognized.
No lights, and the main description says Failed Enumeration: Unknown Device.

Does any of this help?

Gary

 

[Paul]

Thanks - I have tried USBView.

It shows a Standard OpenHCD USB Host Controller (I'll call this 1) and a
Standard Enhanced PCI to USB Host Controller (2), each with 10 ports.

Plugging the mouse into different ports gives different results.
A rear port - it appears under 1. It is recognized as Logitech USB MX510
Optical Mouse. There is a yellow exclamation mark and the mouse does not
light up. Device information says at the top - ERROR no string descriptor
for index 2, and further down: ERROR- No open pipes. Further down under
'device descriptor' there are 2 further ERRORs - no string descriptor for
index 1 iProduct, and index 2 iSerial Number.

A different rear port - it appears under 1. It is correctly recognized.
There is no yellow error. It lights up but doesn't work. Under detail the
following messages could be problems.
Current Config Value 0x01 (arrow) Device Bus Speed: Low
wMaxPacket size 0x0007 = Invalid bus speed for USB Video Class
CAUTION: This may be an invalid bInterfaceProtocol iInterface:
0x00
(note that plugging in a three button optical cordless mouse produces the
same messages, but it works).

Front ports mainly produce the same result as the first described above. On
one occasion, which I can't now reproduce, it appeared under Controller 2,
but showed no lights and the same yellow errors.
Sometimes it shows a yellow error under controller 1 and is not recognized.
No lights, and the main description says Failed Enumeration: Unknown Device.

Does any of this help?

Gary

I couldn't find a picture of the UVCView window, but a very similar program
USBView here, has the same displayed information.

http://www.die.de/blog/content/binary/usbview.png

Basically, how it works, is USB ports can support two standards. USB 1.1 and
USB 2.0. There are two kinds of logic blocks inside the Southbridge, and they
are connected via a multiplexer, to the physical USB port.

A USB 1.1 logic block, typically controls two USB ports. You may have noticed
a habit of putting USB ports in "stacks of two", and the stack of two may be
tied to the same USB 1.1 controller.

The USB 2.0 controller, tends to be shared over more ports.

In that USBView window, you're seeing the ports listed twice. During negotiation,
a plugged in device may end up operating at 2.0 speeds, or at 1.1 speeds. It
will either be "bound" to its USB 1.1 controller, or to the more widely shared
USB 2.0 controller. But it shouldn't show up on both at the same time. So
12 places may show in USBView/UVCView, but only 6 could be used at any one
time.

For a mouse, what I would expect to see, is the mouse show up on the "pair
of two" blocks, and not on the USB2 6, 8, or 10 shared block.

Note that, on some of the latest Intel chipsets, they have finally introduced
a second USB2 controller block, breaking the pattern seen on the screen. This
was done, to offer more USB2 bandwidth to the ports. But it doesn't change the
multiplexing thing, or the "either/or" nature of which block a plugged device
is bound to.

In the USBView picture above, the "Root Hub" at the top of the display, has
not been clicked to expose the two entries it contains. Otherwise, you'd be
looking at "three pairs of two" and the "six port" near the bottom. That is
typical of a range of Intel Southbridges for example. (The 82801 number is
what is pointing me at Intel, as that is an Intel number.)

I think this value, is supposed to be used for the control endpoint.

bMaxPacketSize0 Number Maximum packet size for endpoint zero
(only 8, 16, 32, or 64 are valid)

wMaxPacketSize is two bytes, and appears to support arbitrary lengths
(for data transfers).

Maybe the mouse is declaring itself to be a USB2 device, but that seems a
bit strange. Or maybe the computer and mouse are not communicating
error free.

http://www.beyondlogic.org/usbnutshell/usb5.htm

"The bcdUSB field reports the highest version of USB the device supports"
"USB 2.0 is reported as 0x0200, USB 1.1 as 0x0110 and USB 1.0 as 0x0100."

If a device cannot be fully enumerated (less well than the example in the
picture above), then it is pretty hard for Windows to either apply a default
driver or associate the device with a separately provided driver.
There are classes of devices, and some of them have built-in
drivers in Windows. For a pointing device, I would have
expected to at least be able to move the cursor, even without
installing a driver. I thought (but could be wrong), that third party
drivers for pointing devices, allowed handling extended numbers
of buttons, or binding them to commands and the like. At
least, my cheesy little test mouse I use here, for testing
UVCView, doesn't need any driver to behave like a mouse,
and is immediately recognized and works.

"HID Compliant Mouse" - my cheesy two button mouse, a freeby at a tech show

*******
---===>Device Information<===---
English product name: "HID-compliant Mouse (USB)"

ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: Low
Device Address: 0x02
Open Pipes: 1

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0003 = Invalid bus speed for USB Video Class
bInterval: 0x10

===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0100
bDeviceClass: 0x00 -> This is an Interface Class Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 = (8) Bytes
idVendor: 0x03EE = Mitsumi
idProduct: 0x6407
bcdDevice: 0x0110
iManufacturer: 0x01
English (United States) "Mitsumi"
iProduct: 0x02
English (United States) "HID-compliant Mouse (USB)"
iSerialNumber: 0x00
bNumConfigurations: 0x01

===>Configuration Descriptor<===
bLength: 0x09
bDescriptorType: 0x02
wTotalLength: 0x0022 -> Validated
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0xA0 -> Bus Powered
MaxPower: 0x32 = 100 mA

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x03 -> HID Interface Class
bInterfaceSubClass: 0x01
bInterfaceProtocol: 0x02
CAUTION: This may be an invalid bInterfaceProtocol
iInterface: 0x00

===>HID Descriptor<===
bLength: 0x09
bDescriptorType: 0x21
bcdHID: 0x0100
bCountryCode: 0x00
bNumDescriptors: 0x01
bDescriptorType: 0x22
wDescriptorLength: 0x0032

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0003 = Invalid bus speed for USB Video Class
bInterval: 0x10
*******

You can get the 650 page USB2 standard here (top of the page, link to ZIP).
The "usb_20.pdf" document inside, almost 6MB, is the spec. It will
help a bit interpreting the fields.

http://www.usb.org/developers/docs/

In my mouse example above, the 0x03EE and 0x6407 information, would be
how a third-party driver would get loaded, in response to that USB
device being plugged in. So if you installed some mouse software,
the mouse software would load in response to matching on the idVendor
and idProduct. If those values were corrupted in transmission, then
there is no reason for the third-party driver to be consulted.

The "Caution" messages are probably a feature of UVCView, because the
program was intended for debugging USB Video Class devices (webcams?).
So things that don't look like video devices, or support typical
video device characteristics, may be the reason for some of the Caution
messages. Perhaps a copy of USBView would not have those messages.

Paul

 

[Gary Sams]

I couldn't find a picture of the UVCView window, but a very similar
program
USBView here, has the same displayed information.

http://www.die.de/blog/content/binary/usbview.png

Basically, how it works, is USB ports can support two standards. USB 1.1
and
USB 2.0. There are two kinds of logic blocks inside the Southbridge, and
they
are connected via a multiplexer, to the physical USB port.

A USB 1.1 logic block, typically controls two USB ports. You may have
noticed
a habit of putting USB ports in "stacks of two", and the stack of two may
be
tied to the same USB 1.1 controller.

The USB 2.0 controller, tends to be shared over more ports.

In that USBView window, you're seeing the ports listed twice. During
negotiation,
a plugged in device may end up operating at 2.0 speeds, or at 1.1 speeds.
It
will either be "bound" to its USB 1.1 controller, or to the more widely
shared
USB 2.0 controller. But it shouldn't show up on both at the same time. So
12 places may show in USBView/UVCView, but only 6 could be used at any one
time.

For a mouse, what I would expect to see, is the mouse show up on the "pair
of two" blocks, and not on the USB2 6, 8, or 10 shared block.

Note that, on some of the latest Intel chipsets, they have finally
introduced
a second USB2 controller block, breaking the pattern seen on the screen.
This
was done, to offer more USB2 bandwidth to the ports. But it doesn't change
the
multiplexing thing, or the "either/or" nature of which block a plugged
device
is bound to.

In the USBView picture above, the "Root Hub" at the top of the display,
has
not been clicked to expose the two entries it contains. Otherwise, you'd
be
looking at "three pairs of two" and the "six port" near the bottom. That
is
typical of a range of Intel Southbridges for example. (The 82801 number is
what is pointing me at Intel, as that is an Intel number.)

I think this value, is supposed to be used for the control endpoint.

bMaxPacketSize0 Number Maximum packet size for endpoint zero
(only 8, 16, 32, or 64 are valid)

wMaxPacketSize is two bytes, and appears to support arbitrary lengths
(for data transfers).

Maybe the mouse is declaring itself to be a USB2 device, but that seems a
bit strange. Or maybe the computer and mouse are not communicating
error free.

http://www.beyondlogic.org/usbnutshell/usb5.htm

"The bcdUSB field reports the highest version of USB the device
supports"
"USB 2.0 is reported as 0x0200, USB 1.1 as 0x0110 and USB 1.0 as
0x0100."

If a device cannot be fully enumerated (less well than the example in the
picture above), then it is pretty hard for Windows to either apply a
default
driver or associate the device with a separately provided driver.
There are classes of devices, and some of them have built-in
drivers in Windows. For a pointing device, I would have
expected to at least be able to move the cursor, even without
installing a driver. I thought (but could be wrong), that third party
drivers for pointing devices, allowed handling extended numbers
of buttons, or binding them to commands and the like. At
least, my cheesy little test mouse I use here, for testing
UVCView, doesn't need any driver to behave like a mouse,
and is immediately recognized and works.

"HID Compliant Mouse" - my cheesy two button mouse, a freeby at a tech
show

*******
---===>Device Information<===---
English product name: "HID-compliant Mouse (USB)"

ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: Low
Device Address: 0x02
Open Pipes: 1

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0003 = Invalid bus speed for USB Video
Class
bInterval: 0x10

===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0100
bDeviceClass: 0x00 -> This is an Interface Class
Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 = (8) Bytes
idVendor: 0x03EE = Mitsumi
idProduct: 0x6407
bcdDevice: 0x0110
iManufacturer: 0x01
English (United States) "Mitsumi"
iProduct: 0x02
English (United States) "HID-compliant Mouse (USB)"
iSerialNumber: 0x00
bNumConfigurations: 0x01

===>Configuration Descriptor<===
bLength: 0x09
bDescriptorType: 0x02
wTotalLength: 0x0022 -> Validated
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0xA0 -> Bus Powered
MaxPower: 0x32 = 100 mA

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x03 -> HID Interface Class
bInterfaceSubClass: 0x01
bInterfaceProtocol: 0x02
CAUTION: This may be an invalid bInterfaceProtocol
iInterface: 0x00

===>HID Descriptor<===
bLength: 0x09
bDescriptorType: 0x21
bcdHID: 0x0100
bCountryCode: 0x00
bNumDescriptors: 0x01
bDescriptorType: 0x22
wDescriptorLength: 0x0032

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0003 = Invalid bus speed for USB Video
Class
bInterval: 0x10
*******

You can get the 650 page USB2 standard here (top of the page, link to
ZIP).
The "usb_20.pdf" document inside, almost 6MB, is the spec. It will
help a bit interpreting the fields.

http://www.usb.org/developers/docs/

In my mouse example above, the 0x03EE and 0x6407 information, would be
how a third-party driver would get loaded, in response to that USB
device being plugged in. So if you installed some mouse software,
the mouse software would load in response to matching on the idVendor
and idProduct. If those values were corrupted in transmission, then
there is no reason for the third-party driver to be consulted.

The "Caution" messages are probably a feature of UVCView, because the
program was intended for debugging USB Video Class devices (webcams?).
So things that don't look like video devices, or support typical
video device characteristics, may be the reason for some of the Caution
messages. Perhaps a copy of USBView would not have those messages.

Paul

Sorry, but this is way over my head. Are we any closer to knowing why ny
mouse doesn't work?

Thanks

Gary

 

[Paul]

Sorry, but this is way over my head. Are we any closer to knowing why ny
mouse doesn't work?

Thanks

Gary

When the computer is not able to set up the necessary "endpoints",
for communications, that is a communications problem. It doesn't
get any more fine grained than that. Either the motherboard is
at fault, or the device is at fault, or some cabling is bad
and so on.

About the only other thing I can suggest, is the use of a USB
hub as a "cleaner" of USB signals. There were isolated cases in
the past, where a USB peripheral had high "jitter" in data signals.
(A certain music player was involved I think.) That means the 1's
and 0's didn't arrive at exactly regular intervals. Some motherboard
USB ports (Nforce2 Southbridge) couldn't "see" those devices with
high jitter. The workaround was to use a *USB2* hub, because USB2
hubs reclock and regenerate the data on the way through. As long
as the hub can deal with the jitter, the signal passed back to the
computer is clean. And if the hub is self-powered, with a wall wart,
then you know it has a good source of power for the peripheral.

That test is worthwhile, if you already have a USB2 hub on hand,
to try it. It might turn out to be a waste of money, if you
have to go out and buy one for the test.

While I have seen one USB device, intended for testing USB ports,
I don't know if owning such a thing would leave a user further
ahead in the long run (say, test passes, but real device still
doesn't work). You would almost need a USB protocol
analyzer, to get to the bottom of an unknown communications
problem.

http://www.lecroy.com/tm/products/ProtocolAnalyzers/images/PTP_Session_Decode.jpg
http://www.lecroy.com/tm/products/ProtocolAnalyzers/PDF/USB_high.pdf

One test I like to use on my computers, is booting an alternate
OS when things have "gone South" on me. For example, lspci,
lsusb, and dmesg in Linux, can give some enumeration info on
various bus interfaces. If you can see and use the hardware in
an alternate environment, that tells you the OS or drivers are
implicated, back in Windows. The distros I have on hand, are
Knoppix (knopper.net) and Ubuntu (ubuntu.com). The distro is a
700MB download, and is a ISO9660 file. A program like Nero, can
be used to burn a 700MB CD, based on the download (converts ISO9660
into a CD). There are smaller distros (puppylinux ~100MB), if you
aren't on broadband, and needed something smaller. But I haven't
tested that one, so cannot comment on quality. A lot of the
700MB is crap, and doesn't really help make a good test environment,
but I cannot say how small a distro could get, and still have
useful functionality. The very smallest Linux environments, have
been booted from a floppy.

Paul

 

[Gary Sams]

When the computer is not able to set up the necessary "endpoints",
for communications, that is a communications problem. It doesn't
get any more fine grained than that. Either the motherboard is
at fault, or the device is at fault, or some cabling is bad
and so on.

About the only other thing I can suggest, is the use of a USB
hub as a "cleaner" of USB signals. There were isolated cases in
the past, where a USB peripheral had high "jitter" in data signals.
(A certain music player was involved I think.) That means the 1's
and 0's didn't arrive at exactly regular intervals. Some motherboard
USB ports (Nforce2 Southbridge) couldn't "see" those devices with
high jitter. The workaround was to use a *USB2* hub, because USB2
hubs reclock and regenerate the data on the way through. As long
as the hub can deal with the jitter, the signal passed back to the
computer is clean. And if the hub is self-powered, with a wall wart,
then you know it has a good source of power for the peripheral.

That test is worthwhile, if you already have a USB2 hub on hand,
to try it. It might turn out to be a waste of money, if you
have to go out and buy one for the test.

While I have seen one USB device, intended for testing USB ports,
I don't know if owning such a thing would leave a user further
ahead in the long run (say, test passes, but real device still
doesn't work). You would almost need a USB protocol
analyzer, to get to the bottom of an unknown communications
problem.

http://www.lecroy.com/tm/products/ProtocolAnalyzers/images/PTP_Session_Decode.jpg
http://www.lecroy.com/tm/products/ProtocolAnalyzers/PDF/USB_high.pdf

One test I like to use on my computers, is booting an alternate
OS when things have "gone South" on me. For example, lspci,
lsusb, and dmesg in Linux, can give some enumeration info on
various bus interfaces. If you can see and use the hardware in
an alternate environment, that tells you the OS or drivers are
implicated, back in Windows. The distros I have on hand, are
Knoppix (knopper.net) and Ubuntu (ubuntu.com). The distro is a
700MB download, and is a ISO9660 file. A program like Nero, can
be used to burn a 700MB CD, based on the download (converts ISO9660
into a CD). There are smaller distros (puppylinux ~100MB), if you
aren't on broadband, and needed something smaller. But I haven't
tested that one, so cannot comment on quality. A lot of the
700MB is crap, and doesn't really help make a good test environment,
but I cannot say how small a distro could get, and still have
useful functionality. The very smallest Linux environments, have
been booted from a floppy.

Paul

Thanks, I understood that one. Given that this is effectively a new
computer, I think a fault with the motherboard is the most likely cause. I
will take it up with the manufacturer, but I don't expect to get much
response - I think they are in Taiwan, and even if I do I am not sure what I
expect them to do - I don't fancy replacing the motherboard for a problem I
am able to work round at the moment,

Gary

 

[vij kap]

I was very interested to see the coversation.

I bought one USB gamepad it works on my old laptop which is around 10yrs old, however, it does not work with my new laptop. Please help.

I am also getting the same error.

---===>Device Information<===---
English product name: "USB Joystick"

ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: Low
Device Address: 0x01
Open Pipes: 1

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0008 = Invalid bus speed for USB Video Class
bInterval: 0x10

===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0110
bDeviceClass: 0x00 -> This is an Interface Class Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 = (8) Bytes
idVendor: 0x1345 = Sino Lite Technology Corp.
idProduct: 0x0001
bcdDevice: 0x0311
iManufacturer: 0x01
English (United States) "LuenKeung Co.,Ltd"
iProduct: 0x02
English (United States) "USB Joystick"
iSerialNumber: 0x00
bNumConfigurations: 0x01

===>Configuration Descriptor<===
bLength: 0x09
bDescriptorType: 0x02
wTotalLength: 0x0022 -> Validated
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0x80 -> Bus Powered
MaxPower: 0xFA = 500 mA

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x03 -> HID Interface Class
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
CAUTION: This may be an invalid bInterfaceProtocol
iInterface: 0x00

===>HID Descriptor<===
bLength: 0x09
bDescriptorType: 0x21
bcdHID: 0x0110
bCountryCode: 0x33
bNumDescriptors: 0x01
bDescriptorType: 0x22
wDescriptorLength: 0x0041

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0008 = Invalid bus speed for USB Video Class
bInterval: 0x10

 

[vij kap]

I was very interested to see the coversation.

I bought one USB gamepad it works on my old laptop which is around 10yrs old, however, it does not work with my new laptop. Please help.

I am also getting the same error.

---===>Device Information<===---
English product name: "USB Joystick"

ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: Low
Device Address: 0x01
Open Pipes: 1

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0008 = Invalid bus speed for USB Video Class
bInterval: 0x10

===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0110
bDeviceClass: 0x00 -> This is an Interface Class Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 = (8) Bytes
idVendor: 0x1345 = Sino Lite Technology Corp.
idProduct: 0x0001
bcdDevice: 0x0311
iManufacturer: 0x01
English (United States) "LuenKeung Co.,Ltd"
iProduct: 0x02
English (United States) "USB Joystick"
iSerialNumber: 0x00
bNumConfigurations: 0x01

===>Configuration Descriptor<===
bLength: 0x09
bDescriptorType: 0x02
wTotalLength: 0x0022 -> Validated
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0x80 -> Bus Powered
MaxPower: 0xFA = 500 mA

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x03 -> HID Interface Class
bInterfaceSubClass: 0x00
bInterfaceProtocol: 0x00
CAUTION: This may be an invalid bInterfaceProtocol
iInterface: 0x00

===>HID Descriptor<===
bLength: 0x09
bDescriptorType: 0x21
bcdHID: 0x0110
bCountryCode: 0x33
bNumDescriptors: 0x01
bDescriptorType: 0x22
wDescriptorLength: 0x0041

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0008 = Invalid bus speed for USB Video Class
bInterval: 0x10