Guidance on USB Contoller listing in Device Manager, please



I'm one of the thousands of users who has the dreaded 'USB Device not recognized' error. I don't want to burden this forum (yet) but asking for help on that one. I'm trying to solve it myself by better understanding how USB devices are handled by Windows XP (SP2, that is). I need some guidance on understanding the meaning and significance of the 'USB Controller' section of the Device Manager window.

On my system (ASUS A8V motherboard with 6 out of a possible 8 USB ports installed) the listing shows:

'USB Root Hub' (4 times)
'VIA Universal Host Controller' (3 times)
'VIA USB Enhanced Host Controller' (once)

Loads of newbie Questions:
1. What is a Hub and what is a Root Hub? Are they hardware, microcode or software?
2. What is a USB port and how does it differ to a hub?
3. What is a Host Controller? Is it hardware, microcode or software?
4. I am right in assuming an Enhanced Host Controller is one which provides USB 2.0 support, the others being USB 1.1 only?
5. Why does the output from SiSoft Sandra show no devices attached to any of the 6 ports on the Enhanced Host Controller, but does show the expected devices connected to either Port 1 or Port 2 on one of the three Universal Host Controllers?
6. Why have I got 3 of these host controllers and not just 1 like the Enhanced Host Controller?
7. What is 'Enumeration' and why would a device connected to a USB port fail this process?
8. Is the driver that is listed in the properties for a Hub or Host Controller part of Windows XP, or a specific piece of software supplied with the device?
9. Why do some device have no such driver (for example the Nikon D80 DSLR camera which Windows XP will not recognise - but only on this computer)?


Finally, why do so many people report a 'USB Device Not recognized' error, across such a wide range of systems and devices, across so many years, without a definitive solution being developed by the industry? Microsoft's absence from the this scene is a disgrace. The cost to users must run into 10's of thousands of man hours by now. There are thousands of pages of guidance on the internet which range from the incredible to the insightful - many of them contradicting others. None of them have solved my specific example (but I've only been trying to solve this for 2 weeks ....). If we had this sort of problem with our cars, telephones, TVs, etc, it would have been the subject of incisive media analysis. Why do we let the computer industry get away with this situation? Nikon's technical support response to the problem could form the script for a Broadway comedy; it includes re-installing XP. Who is going to pay for that?
.



Relevant Pages

  • 2.6.10-rc1 & ahci & IHC6R & 925X & raid1
    ... usb modules for console, usb keyboard, network and starting a shell. ... ACPI: PM-Timer IO Port: 0x808 ... PCI: PCI BIOS revision 2.10 entry at 0xfb768, ... usbcore: registered new driver hub ...
    (Linux-Kernel)
  • Re: 2.6.5-rc2-mm4 (and 3) IRQ problem
    ... ACPI: Power Resource ... ata2: SATA port disabled. ... ehci_hcd 0000:00:1d.7: new USB bus registered, ... ehci_hcd 0000:00:1d.7: root hub device address 1 ...
    (Linux-Kernel)
  • hda: dma_timer_expiry: dma status == 0x24
    ... 0000:00:10.0 USB Controller: VIA Technologies, ... usbcore: registered new driver hub ... ACPI: Power Button ... hub 1-0:1.0: individual port over-current protection ...
    (Linux-Kernel)
  • Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793
    ... When the USB reciever is already plugged-in at boot-time and the ... hub 2-2:1.0: USB hub found ... Interface Descriptor: ... Hub Port Status: ...
    (Linux-Kernel)
  • [PROBLEM] 2.6.0-test11: USB freezes after gnome-pilot
    ... and I have a Palm M515 connected thru the USB ... drivers/usb/core/usb.c: registered new driver hub ... hub 1-0:1.0: Port indicators are not supported ... hub 1-0:1.0: power on to power good time: 2ms ...
    (Linux-Kernel)

Loading