[SOLVED] No usb access with VBox

GlennsPref · 08-02-2010, 04:59 AM

Still the same.

Copy log, cat and grep usb

Code:

cat /home/glenn/My_system/vbox-logs/winxpsp2-2010-08-02.log | grep usb
00:00:01.262 [/Devices/usb-ehci/] (level 2)
00:00:01.262 [/Devices/usb-ehci/0/] (level 3)
00:00:01.262 [/Devices/usb-ehci/0/Config/] (level 4)
00:00:01.262 [/Devices/usb-ehci/0/LUN#0/] (level 4)
00:00:01.262 [/Devices/usb-ehci/0/LUN#0/Config/] (level 5)
00:00:01.262 [/Devices/usb-ehci/0/LUN#999/] (level 4)
00:00:01.262 [/Devices/usb-ehci/0/LUN#999/Config/] (level 5)
00:00:01.262 [/Devices/usb-ohci/] (level 2)
00:00:01.262 [/Devices/usb-ohci/0/] (level 3)
00:00:01.262 [/Devices/usb-ohci/0/Config/] (level 4)
00:00:01.262 [/Devices/usb-ohci/0/LUN#0/] (level 4)
00:00:01.262 [/Devices/usb-ohci/0/LUN#0/Config/] (level 5)
00:00:01.262 [/Devices/usb-ohci/0/LUN#999/] (level 4)
00:00:01.262 [/Devices/usb-ohci/0/LUN#999/Config/] (level 5)

lsusb

Code:

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

That's all I got so far.

Regards Glenn

GlennsPref · 08-02-2010, 05:48 AM

lsusb...
Bus 002 Device 006: ID 046d:c215 Logitech, Inc. Extreme 3D Pro

sudo chmod -R 775 /proc/bus/usb/002
sudo chown -hR vboxusers:vboxusers /proc/bus/usb/002

glenn@GamesBox:~$ ls -l /proc/bus/usb (02-08 20:26)
total 0
dr-xr-xr-x 2 root root 0 2010-08-02 20:22 001/
dr-xr-xr-x 2 vboxusers vboxusers 0 2010-08-02 20:22 002/
dr-xr-xr-x 2 root root 0 2010-08-02 20:22 003/
dr-xr-xr-x 2 root root 0 2010-08-02 20:22 004/
-r--r--r-- 1 root root 0 2010-08-02 20:23 devices

glenn@GamesBox:~$ ls -l /proc/bus/usb/002 (02-08 20:39)
total 0
-rwxrwxr-x 1 vboxusers vboxusers 43 2010-08-02 20:22 001*
-rwxrwxr-x 1 vboxusers vboxusers 192 2010-08-02 20:22 002*
-rwxrwxr-x 1 vboxusers vboxusers 251 2010-08-02 20:22 003*
-rwxrwxr-x 1 vboxusers vboxusers 50 2010-08-02 20:22 004*
-rwxrwxr-x 1 vboxusers vboxusers 52 2010-08-02 20:29 006*

glenn@GamesBox:~$ vbox_load (02-08 20:28)
load modules for vbox.
list vbox modules
vboxnetadp 5171 0
vboxnetflt 15181 0
vboxdrv 1791525 2 vboxnetadp,vboxnetflt

It works!

My mistake was (not knowing about) permissions for usb, and in particular /proc/bus/usb.

Yes, thanks skola..., I did misunderstand about the permissions for /proc, I was applying to/dev/bus/usb/...lol!

Still this is new to me, but I thank you, all, for your guidance.

Thanks Heaps.

Regards Glenn

catkin · 08-02-2010, 05:55 AM

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.

unclejed613 · 08-02-2010, 06:08 AM

so what happened after a reboot?

edit: oh, now i see...

not sure that's going to help me, since my USB is managed by HAL, and /etc/fstab hasn't got a usbfs entry as a result...

GlennsPref · 08-02-2010, 06:25 AM

Well what actually happened was, I tried doing far too much.

When all I needed to do was change the permissions for the joystick @ /proc/bus/usb/002 to vboxusers.

I was already a member of the vboxusers group, and the usbfs line in /etc/fstab made no noticable difference, it may save me some trauma later

The reboots were mainly to be sure the system knew what changes I was trying to make to the permissions,

I'm still learning.

all's well, Now.

Slight changes in these systems (to me, anyway) means never stop researching.

Kinda what I wanted GNU/Linux for really. At least we can make it work, with a little collaboration, lol.

Thank you all again.

See you 'round the posts.

Regards Glenn

GlennsPref · 08-03-2010, 05:15 AM

Well, I've come across another problem.

Yesterday the address for the usb joystick was /proc/bus/usb/002/005, but today it is /proc/bus/usb/003/005.

Code:

Bus 003 Device 005: ID 046d:c215 Logitech, Inc. Extreme 3D Pro

I'm wondering how I can make these addresses stick?

It's not too hard to reset it anytime I want to run the vbox and flight sim, but there must be a more efficient way.

Any tips?

Thank you Glenn

unclejed613 · 08-04-2010, 06:14 AM

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:

Code:

KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="root", MODE="0600"
SUBSYSTEM=="usb_device", GROUP="vboxusers", MODE="0664"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", GROUP="vboxusers", MODE="0664"

anybody got any thoughts on this? like, maybe changing or adding another OWNER line?

catkin · 08-04-2010, 09:13 AM

Quote:

Originally Posted by unclejed613

anybody got any thoughts on this? like, maybe changing or adding another OWNER line?

Try renaming /etc/udev/rules.d/10-vboxdrv.rules as /etc/udev/rules.d/90-vboxdrv.rules. More detail in the LQ post I linked earlier in this thread.

unclejed613 · 08-05-2010, 06:15 AM

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

GlennsPref · 02-22-2011, 11:56 PM

To summarise and mark this thread as solved this is what i have and did to it.

Quote:

glenn@GamesBox:~$ uname -a (23-02 15:11)
Linux GamesBox.GlennsPref.net 2.6.37-0.rc5.1mdvtmb-GamesBox #2 SMP PREEMPT Wed Dec 22 16:16:48 EST 2010 x86_64 x86_64 x86_64 GNU/Linux

vbox,4.0.0r69151 AMD64 .run shell package

Make $user a member of the vboxusers group

add usbfs entry to /etc/fstab

Code:

none /proc/bus/usb usbfs devgid=43,devmode=664    0 0

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