On Fri, 2021-05-07 at 17:37 +1000, Carl Brewer wrote:
> On 8/01/2021 10:09 pm, Till Wegmueller wrote:
> > Hey Tony
> >
> > Here in the EU I always get myself a USB Gaming Headset for my
> > Audio
> > needs. They are Cheap(ish) and you can get yourself a Wireless
> > Headset
> > that has a dedica
On 8/01/2021 10:09 pm, Till Wegmueller wrote:
Hey Tony
Here in the EU I always get myself a USB Gaming Headset for my Audio
needs. They are Cheap(ish) and you can get yourself a Wireless Headset
that has a dedicated receiver that needs no special driver, other than
Audio. You might also get a
Hey Tony
Here in the EU I always get myself a USB Gaming Headset for my Audio
needs. They are Cheap(ish) and you can get yourself a Wireless Headset
that has a dedicated receiver that needs no special driver, other than
Audio. You might also get away by simply using the Mic, Headset on the
ho
Hi Till,
Thanks a lot for your reply.
Well, it wasn't a kernel driver hogging the device. I could modunload
the usbvc driver easily, but when I tried to attach the device in vbox,
the kernel loaded the usbvc driver automagically again.
But you did actually point me in the right direction, this
Hey Tony
That sounds to me like the a kernel driver is attaching to the device
and thus Virtualbox cannot do that anymore.
There is a blacklisting capability but I have never done that or know
how exactly that works, or if it helps in this situation.
It should be comparable to bhyve passthr
Hi guys,
I'm trying to get my webcam to work in a vbox guest (to use zoom), but
even though it seems to be present in the VM, cheese, zoom and qv4l2
only shows a blank screen. The video device is there though.
On the host I see:
messages:Jan 7 15:46:00 emu usba: [ID 691482 kern.warning] WARNI
