• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
connecting a microphone via USB
#11
There is one thing in addition usually Linux engineers do when there is always a hardware problem. They use the command "dmesg" which gives you back the trace of the system log from the power on of the device.

So please do the following on the two commercial Raspberry Pi and on netPI.

Go in the container and call "dmesg >mylog.txt" on both devices and send it for comparison. Maybe we can detect on the system log level if there is a driver missing on netPI maybe.

Thx
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#12
In the trace I also see a lot of ioctl() commands running. This make me think of enabling even more rights for the container:

When you deploy a container on netPI you have next to the "network" settings and "privileged" setting also a tab called "capabilities". In this tap you find many many switches. So in another try switch all positions of the switches to "enabled". It is just a try. More privileged access rights are not possible to configure on netPI. This is really the last idea I have.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#13
Dear Armin,

I appreciate your detail investigations!

I haven't installed alsa driver tools so that I executed them as as follows:
"apt install -y alsa-oss alsa-tools alsa-tools-gui alsa-utils alsamixergui mpg123"

I rebooted the netPI and check the phenomenon again.
After the reboot, I typed as follows.
The result was the same as before installing alsa driver tools.

root@raspberrypi:/# lsusb
Bus 001 Device 004: ID 0c76:161f JMTek, LLC.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@raspberrypi:/# arecord -l
**** List of CAPTURE Hardware Devices ****
root@raspberrypi:/# apt install -y alsa-oss alsa-tools alsa-tools-gui alsa-utils alsamixergui mpg123
Reading package lists... Done
Building dependency tree
Reading state information... Done
alsa-oss is already the newest version (1.1.8-1).
alsa-tools is already the newest version (1.1.7-1).
alsa-tools-gui is already the newest version (1.1.7-1).
alsa-utils is already the newest version (1.1.8-2).
alsamixergui is already the newest version (0.9.0rc2-1-10).
mpg123 is already the newest version (1.25.10-2).
0 upgraded, 0 newly installed, 0 to remove and 38 not upgraded.
root@raspberrypi:/# arecord -l
**** List of CAPTURE Hardware Devices ****
root@raspberrypi:/#

And, the attached 'mytrace.txt' in my previous post was collected from netPI.
I will come back here when the trace is got from a commercial raspberry pi.

Best regards,
  Reply
#14
but still turn on the capabilities are I told you in the post before and make "dmesg" trace also.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#15
I tested myself with my headset and I see the same result as you see. No microphone is detected on my netPI as well.

I will investigate.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#16
I checked the list of loaded Linux kernel driver on netPI. The following driver is not installed in the netPI Linux kernel: snd_usb_audio

I detected it when I was using my headset on a commercial Raspberry Pi in comparision to netPI using the system message listing command "dmesg".

On netPI I see

Code:
[  772.276924] input: Logitech Logitech G430 Gaming Headset as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:046D:0A4D.0004/input/input3
[  772.344624] hid-generic 0003:046D:0A4D.0004: input,hidraw0: USB HID v1.00 Device [Logitech Logitech G430 Gaming Headset] on usb-3f980000.usb-1.3/input3

On a commercial Raspberry PI I see

Code:
[  772.276924] input: Logitech Logitech G430 Gaming Headset as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:046D:0A4D.0004/input/input3
[  772.344624] hid-generic 0003:046D:0A4D.0004: input,hidraw0: USB HID v1.00 Device [Logitech Logitech G430 Gaming Headset] on usb-3f980000.usb-1.3/input3
[  772.502423] usbcore: registered new interface driver snd-usb-audio

So right now we both have no chance to get the USB microphone operative without driver.

Now my question is, if the request for supporting a microphone is a real customer demand or just needed for tests?
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#17
Dear Armin,

Thank you very much for your information.
I really appreciate your investigations.

Using a microphone is the main technology to use netPI, it's not just a test.
I hope Its drive can be additionally embedded into netPI without security problems in near future.

Best regards,
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Connecting Monitor to netPi paulj19 4 3,366 January-30th-2020, 02:23 PM
Last Post: paulj19

Forum Jump:


Users browsing this thread: 1 Guest(s)