Custom Query (16363 matches)
Results (124 - 126 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10155 | obsolete | "firmware upload failed (-110) when attempting to connect USB Wireless device (Atheros carl9170) | ||
| Description |
Host: Ubuntu 10.10 x64
Guest: BackTrack 5 R1 / 2.6.39.4
Device: NetGear WN111v2 (Atheros carl9170)
When booting this OS on bare metal I am able to attach the device without any issues. If you boot the OS in VirtualBox, you get a "firmware upload failed (-110)" error. Things I've tried:
I've also tried playing with the compat-wireless drivers from linuxwireless.org but still no go. I really think it is limited to a Linux host/linux guest issue. Outputs: dmesg [ 139.774350] usb 1-1: USB disconnect, device number 2 [ 142.980070] usb 1-1: new high speed USB device number 3 using ehci_hcd [ 143.308076] usb 1-1: reset high speed USB device number 3 using ehci_hcd [ 143.524060] usb 1-1: driver API: 1.9.2 2011-01-22 [1-1] [ 143.524062] usb 1-1: firmware API: 1.9.2 2010-12-25 [ 143.624148] usb 1-1: firmware upload failed (-110). lsusb Bus 001 Device 003: ID 0846:9001 NetGear, Inc. WN111(v2) RangeMax Next Wireless [Atheros AR9170+AR9101] |
|||
| #3521 | worksforme | "framedyn.dll not found" after XP install on MacOS | ||
| Description |
After installing XP SP3 on a MacOS, I get this error message. This is the second error message I get in the whole process (the first being about not being able to run "Windows Media Player" because of registry issues, or something like that). After dismissing this error, the system is mostly usable, but it has some quirks. After googling a bit, I found this article: http://support.microsoft.com/kb/319114 but there is no dllcache folder under system32 for me. The same Windows XP CD was recently installed in a real computer and works fine, btw. |
|||
| #11765 | fixed | "guestproperty set" toggles value with Powered Off vm => Fixed in SVN | ||
| Description |
When the VM is Powered Off, VBoxManage guestproperty set VMName TestProperty will set TestProperty with an empty value if TestProperty does not exist. If TestProperty does exist, it will delete the property. This means running the command multiple times will toggle the TestProperty value between set and deleted. In the past, running guestproperty set would make sure the value was deleted, no matter its previous state. This is used to clear values that might be set from a previous run. This is only when the VM is powered off. It works as expected if the VM is running. This might be related to Ticket #11719. |
|||

