Ticket #574 (closed defect: obsolete)

Opened 10 years ago

Last modified 21 months ago

Problems w/ MP3 Player being recognized.

Reported by: gumbyx Owned by:
Priority: major Component: USB
Version: VirtualBox 2.1.0 Keywords: MP3 Player
Cc: Guest type: other
Host type: other

Description (last modified by frank) (diff)

This problem has been reported by another user for ver. 1.3.8, and I am re-reporting it for 1.4.0. For some reason, I cannot get windows XP SP2 to recognize my MP3 player. It will mount as a USB Mass Storage Device, but will not allow me to connect to it. The following error message comes up when I view the device in Device Manager:

This device cannot start. (Code 10)

It is recognized as a Sansa e250r, but it just stops there.

Change History

comment:1 Changed 10 years ago by scotte

Same problem here with a sansa e280r. Works great on the linux (kubuntu) host, or if I boot into winxp, but a winxp guest is not able to mount it. The device shows disconnected, and winxp shows it with the code 10 error.

Would be great to get this resolved so I don't have to reboot into winxp to use rhapsody.

comment:2 Changed 10 years ago by scotte

BTW, in my case I'm seeing this on VirtualBox 1.5.0 with the 1.5.0 guest addition, if that helps...

comment:3 Changed 9 years ago by xiojason

This problem is due to the interaction between the device and the host OS, before VirtualBox's USB proxy grabs the device.

Upon plugging in the device, it is recognized by the USB subsystem on Linux and the usb-storage kernel module is loaded, and the HAL (on Ubuntu) sees the device attach as well. This causes the device to move to "Connected" state (as seen on the display). VirtualBox then sees the device and removes it from the host to attach the USB proxy. This process moves the device from "Connected" to "Disconnected" state. When it shows up in the guest, it's "Disconnected" and not (properly?) reinitialized to return to "Connected" state. This appears to cause the "Code 10" error.

By killing all of the HAL processes under Ubuntu and removing my usb-storage.ko module (and rerunning depmod -a) before starting VirtualBox, I was able to attach my Sansa e260 and e280R and have them properly recognized in the guest OS -- the host didn't spoil the device's "Connected" state before it was made available to the guest.

Unfortunately, I still can't utilize it -- when attempting to manage the device in Rhapsody, some action within the guest/proxy kicks the device into "Disconnected" state and it doesn't come back.

comment:4 Changed 9 years ago by jckdnk111

I have a creative zen vision m and have the exact same issue. A workaround for this issue would be very nice.

comment:5 Changed 9 years ago by jckdnk111

after trying every possible combination I could think I finally found one that works ... empty usb filter with no usb 2.0 support. It works great now! (version 1.6 by the way)

comment:6 Changed 9 years ago by frank

  • Component changed from other to USB

comment:7 in reply to: ↑ description Changed 8 years ago by caasland

Re-reporting this with Ubuntu 8.10, Sansa e280, and VirtualBox 2.1.0 PUEL.

comment:8 Changed 8 years ago by sandervl73

  • Version changed from VirtualBox 1.4.0 to VirtualBox 2.1.0

comment:9 Changed 21 months ago by frank

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use