Page 1 of 1
USB adapter lost
Posted: 19. Aug 2008, 19:03
by zkab
I have Ubuntu 8.04 as host and guest is Windows XP Pro and it has worked OK ... but when I launch VBox and connect bluetooth devices in Windows all is OK but when I shutdown Windows & VBox and return to Ubuntu then Bluetooth Manager tells me that there is no bluetooth adapter ... but there was one before launching VBox. It doesn't help if I restart bluetooth ... still no adapter ... only way is to reboot and then the adapter is back
Don't know if there is a connection but xfe (file manager) gives me an error: mount point /proc/bus/usb/.usbfs not responding
Posted: 19. Aug 2008, 23:22
by Sasquatch
I advise you to unmount the BT device prior to shutting down the Guest system. Make sure the BT modules are loaded again, and if they aren't, modprobe them again. You might need to remove the modules and add them again if it doesn't work. Also, you say that a process is not responding, I'm sure you can kill that process

.
Posted: 20. Aug 2008, 09:43
by zkab
What happens is this:
1. BT adapter OK in Ubuntu
2. VB is launched
3. Right-click USB icons in VB and selecting BT adapter
4. Now BT adapter is gone in Ubuntu
5. BT works OK in VB and connects all my devices ...
6. Deselecting BT adapter in VB
7. Shutdown VB
8. BT adapter in Ubuntu is ... gone by the wind
9. /etc/init.d/bluetooth restart ... but it still gone
It seems to me that the moment I select BT adapter in VB somehow Ubuntu unload BT modules ...

Posted: 20. Aug 2008, 10:56
by Sasquatch
I think you have a different problem. The service you need for BT is still running when you remove the BT device. Stop the service first, then run the VM, after you're done with the VM, start the service again. Be sure to unload all modules for BT first too, and load them after the VM use.
Posted: 20. Aug 2008, 13:24
by zkab
I did following:
1) stoped the BT service in Ubuntu
2) started VB ... BT worked OK in VB
3) disabled BT in VB
4) shutdown VB
5) started BT service in Ubuntu
6) still the problem remains ... when starting Blueman it tells me in the status line:
Can't get device list.
Reason: 'module' has no attribute 'adapter'
FYI my BT adapter is a Microsoft USB adapter:
-------------------------------------------------------------------------
UUID: 7903c86b-e1c1-41da-dda3-b3326aaa9830
VendorId: 0x045e (045E)
ProductId: 0x009c (009C)
Revision: 1.0 (0100)
Manufacturer: Microsoft
Product: Wireless Radio for Bluetooth 2.0
SerialNumber: 00125A9ECB95
Address: /proc/bus/usb/002/004
Current State: Available
-------------------------------------------------------------------------
I am lost ...

Posted: 20. Aug 2008, 20:13
by Sasquatch
Well, if it's USB anyway, did you also try to remove it and put it back in the USB port?
Posted: 20. Aug 2008, 22:00
by zkab
No - but there has to be other solutions than to start removing hardware ... or am I wrong

Posted: 20. Aug 2008, 23:11
by Sasquatch
Sometimes that's the only solution if the device stops responding. I don't know with what it was exactly, but I know there was some hardware that needed to be replugged before Linux knew it was there.
Posted: 21. Aug 2008, 13:10
by zkab
OK - I will test it and let you know what happens ...
Posted: 21. Aug 2008, 14:06
by zkab
OK - it worked with unplug/plugin the USB BT adapter.
Is it reasonable that the adapter will be unplugged (from Ubuntu) when BT is activated in VB ... in my limited world I concider it to be a VB bug ...

Posted: 21. Aug 2008, 14:26
by Sasquatch
I would say it's more a Linux bug, as it does not detect the release of the device after VB is done. With a normal USB drive, it is detected again and mounted. This BT device isn't. Ubuntu should probe them. You can check the detection by executing lsusb in a terminal window.
Posted: 21. Aug 2008, 15:17
by zkab
I agree ... Ubuntu should detect it.
Since release 8.10 is on its way I will wait and see if it has been fixed in the coming release ... now I have a temporary solution (hardware unplug/plugin)
Thanks for your support

Posted: 21. Aug 2008, 16:08
by Sasquatch
If you want a fix for it, create a bug report on Launchpad. That way, the know that there is an issue with these kinds of devices and possibly fix it.
Posted: 21. Aug 2008, 17:27
by zkab
Done.
Bug 260106