virtualbox.org

Using openSuSE 10.3, everything propery configured.
When I upgraded to Vbox 1.5.4 (from 1.5.2), my Omnikey CardMan 3121 stopped working, which I use for online banking (the only reason I'm using windows also).
I thought it could be something because of win, but fresh reinstall didn't help at all.

When having EHCI controller enabled in VBox settings, device is recognised as unknown and I cannot install drivers in win.
When EHCI option is disabled it is recognized properly, however all lights on device goes off (shouldn't happen) and windows shows and error code 10 (unable to start device). At this point if I try to disconnect device by clicking on VBox USB icon, VBox will freeze.
I tried with different kernels and I get same problem, USB port works, because I did a native win install on spare disk and card reader works there.

EDIT: Downgrading to VBox 1.5.2 fixes the problem. There is definitely something wrong with USB system in VBox.

Well, that seems to be my impression as well. I cant activate any USB-device inside the guest system using vb 1.5.4 - but 1.5.2 was runing well (SuSE 10.3)

Does anyone know where I can get a 1.5.2 for SuSE 10.3?

@DocB: Thanks for confirmation!
Here is 1.5.2 version: http://www.virtualbox.org/download/1.5.2/
I'll stick to 1.5.2 on second computer.

Thanks for the link...maybe we should file a bug with Innotek

.
There is no need to file a trouble ticket, as there is no bug.

USB works with 1.5.4 on an Opensuse 10.3 host, using an XP guest.
.

@constant: not with ALL usb devices. For eg. my camera works, but not my banking card reader.

I'm using Vbox 1.5.4 with Ubuntu 7.10. I have uncommented the 4 lines in mountdevsubfs.sh, and restart it. Still there is no USB available even from the settings.

Any help, please? Should I try to install 1.5.2?

-----
Update:

OK, so I remove 1.5.4, downloaded 1.5.2 and installed it using gdbi. The USBs were automatically detected (I still have the 4 lines uncommented from mountdevsubfs.sh).

So I guess something is broken in 1.5.4, at least with Ubuntu.

.
Something very weird happening here.

Not denying the troubles listed, but I don't have them.

USB is working perfectly with all the devices I have to test with.

I would be most interested to know exactly what it is that causes some problems, but not others.
.

@nightcrawler: your issue is different from that. Please search for a solution (I got USB working under Gutsy in 1.5.4, however same issues as in suse).
Waiting for a response from developers.

Hm..., I was smiling too fast. I don't really know what happened, but out of a suddent I got that famous proxy USB error.

Did you need to do something special with Gutsy and 1.5.4 such that your USBs are recognized?

I remember that problem and I found a solution on an italian blog.
But I don't have it, use gogle with that error. You should be able to get USB working fine on Ubuntu.

Try this: http://gwos.org/doku.php/udsf:virtualbo ... sb_devices

Here's what worked for me with 1.5.2 (all commands as root), taken from various sources:

#gedit /etc/init.d/mountdevsubfs.sh

and uncomment the 4 magic lines:

# Magic to make /proc/bus/usb work
#
mkdir -p /dev/bus/usb/.usbfs
domount usbfs "" /dev/bus/usb/.usbfs -obusmode=0700,devmode=0600,listmode=0644
ln -s .usbfs/devices /dev/bus/usb/devices
mount --rbind /dev/bus/usb /proc/bus/usb

#/etc/init.d/mountdevsubfs.sh start

#gedit /etc/udev/rules.d/40-permissions.rules

and change the following (see http://paulsiu.wordpress.com/2007/11/20 ... irtualbox/):

# USB devices (usbfs replacement)
# original line
#SUBSYSTEM=="usb_device", MODE="0664"
# edited line
SUBSYSTEM==”usb_device”, GROUP=”vboxusers”, MODE=”0664?

Please note the addition of GROUP=”vboxusers” to prevent error (forgot for which error this is, though!).

The following commands to remove the proxy errors, if any (see http://michael-prokop.at/blog/2007/07/1 ... albox-usb/):

#VBOX=$(grep vboxusers /etc/group | sed 's/vboxusers\(.*\):.*/\1/')
and
#mount -t usbfs -o devgid=$VBOX,devmode=664,nodev,noexec,nosuid none /proc/bus/usb

It may be good to reboot.

Now to try with 1.5.4. Or..., hmmm..., perhaps leave it like this, for a while, eh? Don't want to screw it after only 5 minutes.

Hm, I tried both (udev-rules AND fstab), but still dont get it to work AGAIn on SuSE 10.3: vbox 1.5.2 was working, then upgrade to 1.5.4 -> not working, and after downgrade to 1.5.2 I cant get it up and running anymore.
Tried already to delete ~/.Virtualbox , had a new install, but no chance.
USB seems not to be too reliable.....

I've had a working version (till I played around ) by "fstab methode".
Please check your fstab there is another line with "/proc/bus/usb" which you have to delete.