Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This seems a mighty strange device. ~It's a usb microphone on a tripod with ever changing led colours, but it also identifies as a disk! It's brand name is BLOW. The label is in Polish, and gives the website: https://www.protech.com.pl/
It's not in yesterday's usb.ids. Here's what I can find on it.
Code:
dec@Ebony:~$sudo lsusb |grep Jieli
Bus 003 Device 003: ID 4c4a:4155 Jieli Technology UACDemoV1.0
Zoom actually gives the fullest description:"UACDemoV1.0 Audio-Default Audio Device"
dec@Ebony:~$lsblk |grep sdb
sdb 8:16 1 0B 0 disk
[sdb only appeared when I plugged it in. the '0B' size is also somewhat odd.]
dec@Ebony:~$ls -l /dev/disk/by-id |grep usb-BR25
lrwxrwxrwx 1 root root 9 Feb 23 09:09 usb-BR25_UDISK_4150325431313106-0:0 -> ../../sdb
dec@Ebony:~$ls -l /dev/disk/by-path
total 0
lrwxrwxrwx 1 root root 9 Feb 23 09:09 pci-0000:0a:00.3-usb-0:2.1:1.0-scsi-0:0:0:0 -> ../../sdb
It doesn't feature in the UUID directories. Now my fstab has /dev/nvme0n1* & /dev/sda*, but a UUIID for the external disk, so it isn't a disk crisis.
But on the PC is a failed webcam/mic that I'm replacing. The mic works only if you yell at it from 3 inches. The camera turns my pale sickly-looking self into a face painted red LED, with all background colours appropriately shaded. Now when I replace that camera, whether the usb microphone module continues to load for this split-personality device is a very open question.
What I'd like is some clever tricks or options to make sure the microphone works, and to nobble it as a disk.
at first you can cut that ebay link at the first question mark. https://www.ebay.ie/itm/125922022158? (use without that)
Otherwise you ought to create an udev rule for that device.
start somewhere here: https://unix.stackexchange.com/quest...ux-environment
That stackexchange link quickly deteriorates into nagging and corrections. I dislike stackexchange. You go to the trouble of answering a problem. Nobody says 'thanks' but they go correcting you on the way you answered it.
I get the idea, though. One rule to disable everything on that usb.id, and another to allow the one specific usage you want.
I'll have a go at that when I feel able for a cryptic crossword puzzle. I never made friends with udev, so this will be a first.
Last edited by business_kid; 02-23-2024 at 11:24 AM.
at first you can cut that ebay link at the first question mark. https://www.ebay.ie/itm/125922022158? (use without that)
Otherwise you ought to create an udev rule for that device.
start somewhere here: https://unix.stackexchange.com/quest...ux-environment
I've been through this stackexchange link. This seems to disallow all devices, then enable approved ones. Fine on servers. That's not acceptable for me, as a great variety of usb devices are used here. I can't go cobbling up some udev rule any time I want to allow a device. I have this one device that thinks it's a disk, or excites that reaction. Is there another way to do this? Edit usb.ids perhaps? Associate a module with it? Anything?
I guess you need to disable the non-existent disk only.
Exactly. How do I do that? It's loading the usb-storage and seems to think it's a disk with the storage removed . I even saw a comment to that effect. This is from /var/log/messages:
Code:
Feb 22 09:42:06 Ebony kernel: usb 3-2.1: new full-speed USB device number 5 using xhci_hcd
Feb 22 09:42:06 Ebony kernel: usb 3-2.1: New USB device found, idVendor=4c4a, idProduct=4155, bcdDevice= 1.00
Feb 22 09:42:06 Ebony kernel: usb 3-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 22 09:42:06 Ebony kernel: usb 3-2.1: Product: UACDemoV1.0
Feb 22 09:42:06 Ebony kernel: usb 3-2.1: Manufacturer: Jieli Technology
Feb 22 09:42:06 Ebony kernel: usb 3-2.1: SerialNumber: 4150325431313106
Feb 22 09:42:06 Ebony mtp-probe: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:08.1/0000:0a:00.3/usb3/3-2/3-2.1"
Feb 22 09:42:06 Ebony mtp-probe: bus: 3, device: 5 was not an MTP device
Feb 22 09:42:06 Ebony kernel: usb-storage 3-2.1:1.0: USB Mass Storage device detected
Feb 22 09:42:06 Ebony kernel: scsi host6: usb-storage 3-2.1:1.0
Feb 22 09:42:06 Ebony kernel: usbcore: registered new interface driver usb-storage
Feb 22 09:42:06 Ebony kernel: usbcore: registered new interface driver uas
Feb 22 09:42:07 Ebony kernel: scsi 6:0:0:0: Direct-Access BR25 UDISK 1.00 PQ: 0 ANSI: 2
Feb 22 09:42:07 Ebony kernel: sd 6:0:0:0: [sdb] Media removed, stopped polling
Feb 22 09:42:07 Ebony kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
BTW, MTP = Media Transfer Protocol. I've a thing about unknown acronyms. Is there some way I can say "Actually, that 4c4a:4155 device you might meet isn't a disk, but a microphone?"
I tried zoom today, and the microphone couldn't be heard on zoom. OTOH, when I used (spit!) windows 11, it worked fine, and is not recognized as a disk . I have to report this thing to linux-usb.org, which has a bot reading it's email. How does that work?
What's more, I couldn't change volume. I boosted it to 150% and it got no louder Is there anything I can pull to stop the kernel assigning usb-storage.ko to a microphone? As it's a usb device, I have the usb id.
For the record, it's alone in it's usb port, no hubs or anything and no usb storage devices are in the pc at all. I can see it's clearly saying it's a mass storage device, and then saying it's a microphone. So that diagnostic hit the nail on the head.
It seems clear that linux is reading the first Interface Descriptor, and windows the second one.
It is also not purely a microphone, from your lsusb it appears to be an entire (simple) sound card, with sub-devices for 2 sound channels and an onboard mixer, and onboard audio compression to offload some of the work of streaming. A web search suggests it may also have bluetooth receiving capability.
The "mass storage" descriptor appears possibly related to it transferring compressed audio in frames.
It is also not purely a microphone, from your lsusb it appears to be an entire (simple) sound card, with sub-devices for 2 sound channels and an onboard mixer, and onboard audio compression to offload some of the work of streaming. A web search suggests it may also have bluetooth receiving capability.
The "mass storage" descriptor appears possibly related to it transferring compressed audio in frames.
Thanks for your reply. I saw it there in your link. I don't know if we're talking about the same device. It doesn't seem to have support from alsa+pulse of 2024! It adds an unnecessary disk. The sales ad boasts none of the features you describe. If definitely doesn't provide a mixer. I can't even adjust the insufficient volume under pulse.
My model may be a cut down version. Mind you, if I met a microphone with all those bells & whistles, I wouldn't buy it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.