https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287813

--- Comment #28 from J.R. Oldroyd <f...@opal.com> ---
Well, the case isn't solved at all!

Clearly buying a different device that is known to work is one solution, and I
am probably going to do that to save time.

However, we know that the "pactl exit" hack (with the broken close() code in
the driver) will make this device work perfectly.  So there is a software
solution waiting to be found that would let FreeBSD support this device.

It turns out that I missed something.  I have provided the uaudio info from the
log when this device is connected.  After the Windows test, I happened to be
watching the log as I reconnected the device to FreeBSD.  There is more to this
device than just the uaudio part:

kernel: ugen0.2: <vendor 0x0a12 product 0x4010> at usbus0
kernel: uhub1 on uhub0
kernel: uhub1: <vendor 0x0a12 product 0x4010, class 9/0, rev 2.00/18.65, addr
17> on usbus0
kernel: uhub1: 4 ports with 0 removable, bus powered
kernel: ugen0.3: <vendor 0x0b0e BTV5.2> at usbus0
kernel: uaudio0 on uhub1
kernel: uaudio0: <vendor 0x0b0e BTV5.2, class 0/0, rev 2.00/1.12, addr 18> on
usbus0
kernel: uaudio0: Play[0]: 48000 Hz, 2 ch, 16-bit S-LE PCM format, 2x4ms buffer.
(selected)
kernel: uaudio0: Record[0]: 16000 Hz, 1 ch, 16-bit S-LE PCM format, 2x4ms
buffer. (selected)
kernel: uaudio0: No MIDI sequencer.
kernel: pcm2 on uaudio0
kernel: uaudio0: HID volume keys found.

There is also a 0a12:4010 hub device which turns out to be a "Cambridge Silicon
Radio, Ltd" hub, or possibly a Chinese-made device squatting on this USB ID.

Searching this ID finds various pages saying things like devices with this ID
are known to report wrong parameters or report support for USB commands that
aren't actually supported.  I also find patches for Linux adding some quirks to
work around some of these problems.

I will likely move to the known-working Jabra solution myself.  Debugging this
will be for another day when I have more time.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to