Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
glenn@GamesBox:~$ lsusb (02-08 19:55)
Bus 004 Device 005: ID 043d:007b Lexmark International, Inc. InkJet Color Printer
Bus 004 Device 004: ID 043d:007c Lexmark International, Inc. Lexmark X1110/X1130/X1140/X1150/X1170/X1180/X1185
Bus 004 Device 003: ID 0b05:1715 ASUSTek Computer, Inc. 2045 Bluetooth 2.0 Device with trace filter
Bus 004 Device 002: ID 043d:007a Lexmark International, Inc. Generic Hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005: ID 046d:c215 Logitech, Inc. Extreme 3D Pro
Bus 002 Device 004: ID 0aec:3260 Neodio Technologies Corp. 7-in-1 Card Reader
Bus 002 Device 003: ID 046d:092f Logitech, Inc. QuickCam Express Plus
Bus 002 Device 002: ID 0582:00e7 Roland Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Sorry not to be able to help in what must be a frustrating saga (because my versions are too different) but have you tried a) attaching USB devices from the command line (to see any error messages) and b) re-ordering the VirtualBox udev rule? Earlier in the thread a usbfs line in fstab was mentioned and that has obviated any need for a udev rule adjustment in my experience -- but it may be worth trying. More in this LQ thread.
EDIT: was posting while solution was being posted. Glad you found a solution.
ok, so last night i tried it as root, with no other modifications made. usb works when running vbox as root. after doing some further searching, i am not sure, but the file /etc/udev/rules.d/10-vboxdrv.rules may hold the key to fixing this:
i've tried that, but since there's no conflicting rules elsewhere, it had no effect, neither did changing the mode and owner information in the rules file
Now what I do is anytime I want to run vbox I find the joystick address, it changes from time to time.
Code:
lsusb | grep "3D Pro" (23-02 15:49)
Bus 003 Device 003: ID 046d:c215 Logitech, Inc. Extreme 3D Pro
then edit this file and run it.
my script,
Code:
#!/bin/zsh
# /home/glenn/bin/vbox_load
echo "load modules for vbox."
sudo modprobe -f vboxdrv
sudo modprobe -f vboxnetadp
sudo modprobe -f vboxnetflt
echo "list vbox modules"
sudo lsmod | grep vbox
ls -l /proc/bus/usb/003 #edit this line
sudo chown -hR vboxusers:vboxusers /proc/bus/usb/003/003 #edit this line
sudo chmod -R 775 /proc/bus/usb/003/003 #edit this line
ls -l /dev/input/js0
# ID 046d:c215 Logitech, Inc. Extreme 3D Pro
final output...(dates and user rem. for clarity)
Code:
echo "load modules for vbox."
load modules for vbox.
sudo modprobe -f vboxdrv
sudo modprobe -f vboxnetadp
sudo modprobe -f vboxnetflt
echo "list vbox modules"
list vbox modules
sudo lsmod | grep vbox
vboxnetadp 5147 0
vboxnetflt 18777 0
vboxdrv 1809667 2 vboxnetadp,vboxnetflt
ls -l /proc/bus/usb/003 #edit this line
sudo chown -hR vboxusers:vboxusers /proc/bus
/usb/003/003 #edit this line
sudo chmod -R 775 /proc/bus/usb/003/003 #edit this line
ls -l /dev/input/js0
crw-rw-r--+ 1 root root 13, 0 2011-02-23 09:45 /dev/input/js0
Cheers Glenn
Last edited by GlennsPref; 02-23-2011 at 12:04 AM.
Reason: clarity
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.