Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

USB device configuration causes error during system boot: Initializing USB controller (usb-ohci): failed

Details

Why do I see this error message regarding my USB device when I boot up my ESX Server system?

vmserver1 rc.sysinit: Initializing USB controller (usb-uhci): succeeded
vmserver1 modprobe: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
vmserver1 modprobe: /lib/modules/2.4.9-vmnix2/kernel/drivers/usb/usb-ohci.o: init_module: No such device
vmserver1 modprobe: /lib/modules/2.4.9-vmnix2/kernel/drivers/usb/usb-ohci.o: insmod /lib/modules/2.4.9-vmnix2/kernel/drivers/usb/usb ohci.o failed
vmserver1 modprobe: /lib/modules/2.4.9-vmnix2/kernel/drivers/usb/usb-ohci.o: insmod usb-ohci failed
vmserver1 rc.sysinit: Initializing USB controller (usb-ohci): failed

Solution

Systems using the USB-UHCI device driver with the USB 2.0 interface cause ESX Server to show a false warning message during the boot sequence. It is safe to ignore this message.

To configure your system so that this warning does not appear the next time you boot your ESX Server machine:

  1. Log onto the service console as root.
  2. Edit /etc/modules.conf.
  3. Look for a line similar to:

    alias usb-controller1 usb-ohci

  4. Comment out that line.

    Example: #alias usb-controller1 usb-ohci

  5. Save your changes to /etc/modules.conf and exit.

Keywords

1659; esx; insmod; errors; incorrect; module; parameters; params; modprobe; usb-ohci; failed; usb-ohci.o

Update History

02/07/2012 - Updated title to include error

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
Actions
KB: