Hello people,
first to explain why i start another thread on the topic - no USB working in VirtualBox. Devices recognized but not available. So i have read most of the threads on the topic here and even on other places on the net. But i still do not have solution to the problem. My configuration is - Slackware13_64 plus VirtualBox and Slackware13_32 in it.

What i did until now:

1.Added myself to groups:vboxusers,plugdev - Not working

2.Edit rc.S - Not working.
Adding "-o devgid=83,devmode=0644" to the mount command changes the mode of /proc/bus/usb to root,plugdev. But when i start VBox and inside LILO loads the mouse and keyboard die and i cant do anything except reboot. When i remove devgid from the mount command the mouse and keyboard are ok but then usb is not accessible again.

3.Edit fstab - Not working.
Basically the same story as with rc.S.devgid halts my input. Whatever i put in devgid is the same result.

4.No need to edit the udev rules they dont change the mode to other than 664.i saw that on some systems some of the udev rules change the mode to 646 but slackware is not of them

I do not know what else i might try.
Please help

Since this is a new thread you should not assume that people have read the old thread, at the very least you need to supply a link to it. Your post does not even say what your problem is.
What is not working?

Evo2.

Hello again,
i am sorry. I am frustrated
The problem is that USB in VirtualBox is not working. It shows the devices but they are not available. As i understood the problem is the permissions of /proc/bus/usb. There are several solutions posted on this site (http://www.linuxquestions.org/questi...virtualbox+usb).
But they are not working for me as explained in my previous post.

Ohh, I see. Sorry I can't help, I only use the free version of VirtualBox, which last time I checked does not provide usb access.

Evo2.

The post which helped me get USB devices working in VirtualBox was this one. I was lazy and just re-booted rather than trying to remount anything (that way I could get more coffee while I was waiting). But when I started VirtualBox again after the re-boot I could access my memory sticks and my iPhone.

Hello gilead,
im glad you solved the problem. But what exactly did you do? I have read the thread and tried many things but nothing seems to work. When i use the DEVGID in mount or FSTAB the mouse and keyboard die in host and in guest.
Thanks

It was the /etc/fstab entries that did it for me:
Are there any errors in /var/log/messages or /var/log/syslog about your keyboard/mouse?

Hi gilead,
Ok i tried and this approach with both lines in fstab. No luck. First there was a complain that i shouldnt have mounted that way and then the same. Mouse and keyboard die. No complains in /var/log/messages or syslog
Im getting really annoyed by that thing. I think is something in the udev rule for Vbox. But i dont know much about that.
But obviously is some permission thing.

Hears what worked for me using Slack64-C host / WinXP 32 client

Add to /etc/rc.d/rc.S:
" /sbin/mount -v usbfs /proc/bus/usb -t usbfs -o devgid=10,devmode=0664 "

Add yourself in the groups:
wheel
vboxusers

In VirtualBox Control

Set Network to
" Bridged Adaptor "

Check both boxes in the USB section.

Have you tried running the script posted in this LQ post?

To catkin,
yes i did in fact It gave me all test ok with one exception which i couldnt get. Here is the outcome:
VirtualBox PUEL version found. OK.
WARNING: VirtualBox non-PUEL version also found. ???
Name of user used to run VirtualBox: domine
This computer has udev rules file for VirtualBox, /etc/udev/rules.d/10-vboxdrv.rules. OK.
No fstab usbfs line found. udev rules are effective.
Group name used for VirtualBox USB access is vboxusers.
Group vboxusers found in /etc/group. OK.
Here is the group line from /etc/group:
vboxusers:x:102:domine
User domine is in group vboxusers/102. OK.
Access mode used for VirtualBox USB access is 0664.
Access mode (0664) includes 'group write'. OK.
Kernel module vboxdrv loaded. OK.
All tests passed. OK. :-)

The output is strange as i didnt install other versions of VB.

Im reading now about udev rules. Maybe if i make a special device node for my webcam on which im the owner it will solve the problem.
If any ideas i will be happy to try out
Thanks for the help

If there is a non-PUEL version of VirtualBox and that is the one that is being run then it would be enough to explain why you cannot access USB devices. Suggest you investigate why the script is generating that warning.

Ok. I did "slocate -u" and then search with "slocate -i virtualbox". But no additional VB to the one in /opt. Any other idea of how can i search?
Btw some idea why the mouse and keyboard die when i use the devgid?
Thanks

Hello again,
i checked the script code of this link http://www.linuxquestions.org/questi...39#post3727439. The check for RPM gives the error flag=YES. But rpm is not working on my system. I dont use rpm. But i did the check manually "rpm -qi VirtualBox" gives error that some libnss3 not found. Hence error in the logic of the script and not correct findings.
So that is not my problem. The problem is why my mouse and keyboard die when i use devgid in fstab or mount. I just cant figure that out. It doesnt matter which GID i give 102(vboxusers) or 83(plugdev). Its wired dont you think. I never saw somebody else system to have that kind of problem.

I am searching the web for days but no such info found.

Plaese any idea will be appreciated.

As far as i know, installing 'Virtualbox Guest Additions' in guest OS is also required for usb to work.