Posts: 20
Threads: 3
Joined: Dec 2020
Reputation:
0
01-02-2021, 03:55 PM
(This post was last modified: 01-13-2021, 02:28 AM by radiooff.)
01/12/2021:
I marked this as solved, since I will wait for moOde 7.1.0 to be released.
Thanks for everyone's help.
radiooff
Hi all,
I've been lurking here for a bit of time. I am having trouble with moOde detecting my USB DAC (SMSL M100).
I have RPi 4 (2GB) and an official RPi 7" touchscreen display. It's powered by an official RPi 4 power supply (Vilros). The M100 is powered by an external battery or a 5V wall wart. I also have a USB WD Passport (4GB) internally powered by the RPi 4.
I have tried time and time again to get moOde going with my setup for the past month. At first, with 6.7.1 and 7.0, they really did not work for me. Each time I do a project with an RPi-- I have to relearn what Linux I do know! Anyways, 7.0.1 works. I've had it recognize my USB drive and the files on it. moOde generates a library and I can even try to test the audio or play a radio station-- which is when everything takes a turn for the worse.
I get no audio out. I have owned the M100 for close to a year-- it seems to be operational. I've set the I2S to 'none' and tried to detect my USB Audio (inline 1 connected to USB on RPi). But no dice.
Right at this time I have my M100 connected to my RPi4. So here's some code:
Code: pi@moode:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Code: pi@moode:~ $ moodeutl -l
20210102 101925 worker: -- Start
20210102 101925 worker: Successfully daemonized
20210102 101925 worker: Integrity check (passed)
20210102 101926 worker: File check (OK)
20210102 101926 worker: Session loaded
20210102 101926 worker: Debug logging (OFF)
20210102 101926 worker: -- Device
20210102 101926 worker: ALSA cards: (0:Headphones | 1:empty | 2:empty | 3:empty
20210102 101926 worker: Configured: (0:Pi Headphone jack | mixer:(Headphone) | alsavol:0)
20210102 101926 worker: ALSA mixer actual (Headphone)
20210102 101926 worker: ALSA Headphone volume set to (0%)
20210102 101926 worker: -- System
20210102 101927 worker: Host (moode)
20210102 101927 worker: moOde (7.0.1 2020-12-23)
20210102 101927 worker: RaspiOS (10.6)
20210102 101927 worker: Kernel (5.4.77-v7l+ #1371)
20210102 101927 worker: Platform (Unknown Pi-model)
20210102 101927 worker: ARM arch (armv7l, 32-bit kernel)
20210102 101927 worker: MPD ver (0.22.3_p0x3)
20210102 101927 worker: CPU gov (performance)
20210102 101927 worker: USB boot not available
20210102 101927 worker: File system expanded
20210102 101927 worker: HDMI port off
20210102 101927 worker: -- Network
20210102 101927 worker: eth0 exists
20210102 101927 worker: eth0 address not assigned
20210102 101927 worker: wlan0 exists
20210102 101927 worker: wifi country (US)
20210102 101927 worker: wlan0 trying SSID (Fios-ZWkC8)
20210102 101927 worker: IP addr (192.168.1.179)
20210102 101927 worker: Netmask (255.255.255.0)
20210102 101927 worker: Gateway (192.168.1.1)
20210102 101927 worker: Pri DNS (192.168.1.1)
20210102 101927 worker: Domain (myfiosgateway.com)
20210102 101927 worker: -- Audio
20210102 101928 worker: MPD conf updated
20210102 101928 worker: ALSA outputs unmuted
20210102 101928 worker: ALSA card number (0)
20210102 101928 worker: Audio output (Pi Headphone jack)
20210102 101928 worker: Audio formats (U8, S16_LE)
20210102 101928 worker: ALSA mixer name (Headphone)
20210102 101928 worker: MPD volume control (software)
20210102 101928 worker: Hdwr volume controller exists
20210102 101928 worker: Max ALSA volume (100%)
20210102 101928 worker: Reset renderer active flags
20210102 101928 worker: -- MPD
20210102 101928 worker: MPD started
20210102 101929 worker: MPD accepting connections
20210102 101929 worker: Configure MPD outputs
20210102 101929 worker: MPD output 1 ALSA default (on)
20210102 101929 worker: MPD output 2 ALSA crossfeed (off)
20210102 101929 worker: MPD output 3 ALSA parametric eq (off)
20210102 101929 worker: MPD output 4 ALSA graphic eq (off)
20210102 101929 worker: MPD output 5 ALSA polarity inversion (off)
20210102 101929 worker: MPD output 6 ALSA bluetooth (off)
20210102 101929 worker: MPD output 7 HTTP stream (off)
20210102 101929 worker: MPD crossfade (off)
20210102 101929 worker: -- Feature availability
20210102 101929 worker: Source select (available)
20210102 101929 worker: Source select (source: MPD)
20210102 101929 worker: Source select (output: Pi Headphone jack)
20210102 101929 worker: Bluetooth (available)
20210102 101929 worker: Airplay renderer (available)
20210102 101929 worker: Spotify renderer (available)
20210102 101929 worker: Squeezelite renderer (available)
20210102 101929 worker: UPnP renderer (available)
20210102 101929 worker: DLNA server (available)
20210102 101929 worker: UPnP browser (available)
20210102 101929 worker: GPIO button handler (available)
20210102 101929 worker: Stream recorder (n/a)
20210102 101929 worker: -- Music sources
20210102 101929 worker: USB sources (none attached)
20210102 101929 worker: NAS and UPnP sources (none configured)
20210102 101929 worker: -- Miscellaneous
20210102 101929 worker: USB volume knob (Off)
20210102 101929 worker: USB auto-mounter (udisks-glue)
20210102 101929 worker: LED0 (On)
20210102 101929 worker: LED1 (On)
20210102 101929 worker: Saved MPD vol level (0)
20210102 101929 worker: Preamp volume level (0)
20210102 101929 worker: MPD volume level (0) restored
20210102 101929 worker: ALSA Headphone volume (100%)
20210102 101929 worker: Auto-play (Off)
20210102 101929 worker: Maintenance interval (3 hrs)
20210102 101929 worker: Screen saver activation (Never)
20210102 101929 worker: Session permissions (OK)
20210102 101929 worker: Watchdog started
20210102 101929 worker: Ready
20210102 101932 worker: Job i2sdevice
The only audio I can choose is 'RPi Headphones'. So, I may be missing something obvious or perhaps the M100 does not work in this case (or perhaps at all.) I'm not above buying a new DAC if that has to happen. I'd prefer a USB DAC, but a hat-config will do too...
But does it need to come to that?
Thank you.
Posts: 13,450
Threads: 305
Joined: Mar 2018
Reputation:
545
The output from lsusb shows nothing connected.
To troubleshoot start with just a bare Pi and your USB dac (to rule out some sort of power issue). If lsusb still shows nothing connected then swap in a different Pi for example a 3B+.
Posts: 20
Threads: 3
Joined: Dec 2020
Reputation:
0
(01-02-2021, 04:18 PM)Tim Curtis Wrote: The output from lsusb shows nothing connected.
To troubleshoot start with just a bare Pi and your USB dac (to rule out some sort of power issue). If lsusb still shows nothing connected then swap in a different Pi for example a 3B+.
Do you suspect a power issue because of the touchscreen?
I have tried each of the 4 USB ports on the RPi 4 with the M100 (externally powered) but using the touch screen. Would it be different if I turned on the HDMI and used my monitor instead?
I think I do have a 3B+ kicking around and a spare microSD, maybe I'll hook that up to my monitor...
Posts: 20
Threads: 3
Joined: Dec 2020
Reputation:
0
Ok.
I found an RPi 3B+ and a 128GB microSD card. I have that with 7.0.1., wi-fi On, ethernet on and my USB DAC connected. No keyboard, mouse or monitor connected.
Here's some code:
Code: pi@moode:~ $ lsusb
Bus 001 Device 004: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and some more:
Code: pi@moode:~ $ moodeutl -l
20210102 123146 worker: -- Start
20210102 123146 worker: Successfully daemonized
20210102 123147 worker: Integrity check (passed)
20210102 123147 worker: File check (OK)
20210102 123147 worker: Session loaded
20210102 123147 worker: Debug logging (OFF)
20210102 123147 worker: -- Device
20210102 123147 worker: ALSA cards: (0:empty | 1:empty | 2:empty | 3:empty
20210102 123147 worker: Configured: (0: | mixer:(Invalid card number.) | alsavol:Invalid card number.)
20210102 123147 worker: WARNING: No device found at configured MPD card0
20210102 123147 worker: UPDATE: Reconfigured MPD card number to 0
20210102 123147 worker: ALSA mixer actual (Invalid card number.)
20210102 123148 worker: ALSA Invalid card number. volume set to (Invalid card number.)
20210102 123148 worker: -- System
20210102 123149 worker: Host (moode)
20210102 123149 worker: moOde (7.0.1 2020-12-23)
20210102 123149 worker: RaspiOS (10.6)
20210102 123149 worker: Kernel (5.4.77-v8+ #1371)
20210102 123149 worker: Platform (Pi-3B+ 1GB v1.3)
20210102 123149 worker: ARM arch (aarch64, 64-bit kernel)
20210102 123149 worker: MPD ver (0.22.3_p0x3)
20210102 123149 worker: CPU gov (performance)
20210102 123149 worker: USB boot enabled
20210102 123149 worker: File system not expanded yet
20210102 123149 worker: HDMI port on
20210102 123149 worker: -- Network
20210102 123149 worker: eth0 exists
20210102 123149 worker: IP addr (192.168.1.183)
20210102 123149 worker: Netmask (255.255.255.0)
20210102 123149 worker: Gateway (192.168.1.1)
20210102 123149 worker: Pri DNS (192.168.1.1)
20210102 123149 worker: Domain (myfiosgateway.com)
20210102 123149 worker: wlan0 exists
20210102 123149 worker: wifi country (US)
20210102 123149 worker: wlan0 trying SSID (Fios-ZWkC8)
20210102 123150 worker: IP addr (192.168.1.184)
20210102 123150 worker: Netmask (255.255.255.0)
20210102 123150 worker: Gateway (192.168.1.1)
20210102 123150 worker: Pri DNS (192.168.1.1)
20210102 123150 worker: Domain (myfiosgateway.com)
20210102 123150 worker: -- Audio
20210102 123150 worker: MPD conf updated
20210102 123150 worker: ALSA outputs unmuted
20210102 123150 worker: ALSA card number (0)
20210102 123150 worker: Audio output ()
20210102 123150 worker: Audio formats (cat: /proc/asound/card0/pcm0p/sub0/hw_params: No such file or directory)
20210102 123151 worker: ALSA mixer name (Invalid card number.)
20210102 123151 worker: MPD volume control (software)
20210102 123151 worker: Hdwr volume controller exists
20210102 123151 worker: Max ALSA volume (100%)
20210102 123151 worker: Reset renderer active flags
20210102 123151 worker: -- MPD
20210102 123151 worker: MPD started
20210102 123151 worker: MPD accepting connections
20210102 123151 worker: Configure MPD outputs
20210102 123151 worker: MPD output 1 ALSA default (on)
20210102 123151 worker: MPD output 2 ALSA crossfeed (off)
20210102 123151 worker: MPD output 3 ALSA parametric eq (off)
20210102 123151 worker: MPD output 4 ALSA graphic eq (off)
20210102 123151 worker: MPD output 5 ALSA polarity inversion (off)
20210102 123151 worker: MPD output 6 ALSA bluetooth (off)
20210102 123151 worker: MPD output 7 HTTP stream (off)
20210102 123151 worker: MPD crossfade (off)
20210102 123151 worker: -- Feature availability
20210102 123151 worker: Source select (available)
20210102 123151 worker: Source select (source: MPD)
20210102 123151 worker: Source select (output: )
20210102 123151 worker: Bluetooth (available)
20210102 123151 worker: Airplay renderer (available)
20210102 123151 worker: Spotify renderer (available)
20210102 123151 worker: Squeezelite renderer (available)
20210102 123151 worker: UPnP renderer (available)
20210102 123151 worker: DLNA server (available)
20210102 123151 worker: UPnP browser (available)
20210102 123151 worker: GPIO button handler (available)
20210102 123151 worker: Stream recorder (n/a)
20210102 123151 worker: -- Music sources
20210102 123151 worker: USB sources (none attached)
20210102 123151 worker: NAS and UPnP sources (none configured)
20210102 123151 worker: -- Miscellaneous
20210102 123151 worker: USB volume knob (Off)
20210102 123151 worker: USB auto-mounter (udisks-glue)
20210102 123152 worker: LED0 (On)
20210102 123152 worker: LED1 (On)
20210102 123152 worker: Saved MPD vol level (0)
20210102 123152 worker: Preamp volume level (0)
20210102 123152 worker: MPD volume level (0) restored
20210102 123152 worker: ALSA Invalid card number. volume (Invalid card number.)
20210102 123152 worker: Auto-play (Off)
20210102 123152 worker: Maintenance interval (3 hrs)
20210102 123152 worker: Screen saver activation (Never)
20210102 123152 worker: Session permissions (OK)
20210102 123152 worker: Watchdog started
20210102 123152 worker: Ready
20210102 123155 worker: Job i2sdevice
20210102 123257 worker: Job mpdrestart
20210102 123631 watchdog: Info: Reducing PHP fpm worker pool
Now, at least I am getting an invalid ALSA code?
Anyways, the card I am using is faster than the one in my RPi 4. I am also getting more options. So, I think I'll switch out the cards at the very least.
The question is the M100 compatible? I have the Touchscreen stand, and I just want to run a localUI on the touchscreen with the 4GB (unpowered) drive as a moOde jukebox. Or will I not be able to do all those things?
Would it be a good idea to just try to replicate what I did with the faster microSD on the RPi 4 bare?
Posts: 6,029
Threads: 177
Joined: Apr 2018
Reputation:
235
@ radiooff
I don't think your issue has anything to do with the RPi model or the nature of the uSD card.
In both posts where you've shown lsusb output, there's no indication that the SMSL M100's USB port has been detected by Raspberry Pi OS. In effect, you're done before you start since there's nothing for moOde to work with.
I tried and failed to find a manual for this DAC (but didn't look very hard).
I do notice in the ads that this DAC has more than one input. Is there some selection process you have to go through to select the USB input? Does this DAC work with any other computer? If so, what did you have to do to make it so?
Regards,
Kent
Posts: 20
Threads: 3
Joined: Dec 2020
Reputation:
0
Hi Kent,
I have the PDF manual of the M100, it's not helpful in the least. There is a selection button. It has optical, coaxial and USB in and when using it with moOde I have always selected the correct inline. But the M100 is a bit odd, it has 2 USB in for 5V, but only one is marked as an input.
So, I did what you asked. I hooked the M100 up to the external power supply and to a different output, specifically optical from a Chromecast Audio powered by a backup-battery. Which is then in turn hooked up to my powered computer speakers. I set up the CCA, and everything worked. So, it looks like it is a bum USB input on the M100. I may have broken it somehow, because this is actually the first time I have used it.
The CCA DAC is no slouch. But I need RCA out because my receiver and CD don't have coaxial or optical in. I also have a about 1TB of FLAC files, and nothing on Android will handle that library efficiently or responsively. I found moOde.
I did try the bare RPi 4 with the M100 and still got:
Code: pi@moode:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I don't think I am wrong in assuming I need a new DAC, at least for the purposes I need.
It's looks like a Topping D50 with my RPi 4 would fit the bill.
Any insights?
Posts: 5
Threads: 0
Joined: Jul 2018
Reputation:
0
I think your USB DAC is using a VIA-USB controller, so it's visible already (and usuable I assume). I use a Audio-GD DAC and it shows like this in the lsusb output:
....
Bus 001 Device 004: ID 040d:3410 VIA Technologies, Inc.
....
when I installed Moode at first I did not have sound, but for some reason my DAC was not present when I checked with "aplay -l". What I did was the following:
- I changed the /boot/config.txt:
disable_splash=1
disable_overscan=1
hdmi_drive=2
hdmi_blanking=1
hdmi_force_edid_audio=1
hdmi_force_hotplug=1
hdmi_group=0
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=audio=on
dtparam=audio=off
after a reboot the internal audio (and i2s overlay for HATs) willl be disabled and my USB DAC showed up then (check this with "aplay -l")
now you should be able to see/select your DAC in the MPD config page in the Moode-browser page as output device. Now before you go on: I had one more issue: when I checked with "aplay -l" my DAC was reported as "card 1" for some reason. This will give a problem when you would like to see the "Audio Info" (in the browser-screen - click on the "M" in the upper right corner and select that option). I solved this as follows:
- I created the file /etc/asound.conf and added this:
pcm.!default {
type hw
card 0
}
ctl.!default {
type hw
card 0
}
reboot the system once more and check with "aplay -l" if your DAC is seen on "card 0", see my output:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Audiogd [Audio-gd], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
now you should be able to see/configure your DAC in the MPD settings page. In theory you should be able to get sound from your DAC, however, in some cases you might run into the UAC2 issue, which means that your music skips or stutters. In the System Config page there is a "USB (UAC2) fix" setting which should do the trick, but this did not work for me (may be a bug, but it can also be an issue with my setup). For me to get it working I added the following to the first line in the /boot/cmdline.txt for this:
dwc_otg.lpm_enable=0 dwc_otg.fiq_fsm_mask=0x3
be sure to add it at the beginning or at the end without a newline (so one long line of text).
you need to reboot in order to get this working.
I hope this will help you 
Posts: 6,029
Threads: 177
Joined: Apr 2018
Reputation:
235
(01-02-2021, 07:09 PM)radiooff Wrote: Hi Kent,
...
I did try the bare RPi 4 with the M100 and still got:
Code: pi@moode:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
...
In keeping with the recent reply by ImInTheMoOdeForAudio, you can confirm if this Via Labs device is indeed your DAC interface, by looking to see if it offers audio-related endpoints.
Here's an example using my Khadas Tone Board which implements its USB interface using a XMOS Ltd chip
Code: pi@moodelr:~ $ lsusb
Bus 002 Device 002: ID 152d:1561 JMicron Technology Corp. / JMicron USA Technology Corp. JMS561U two ports SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 20b1:000a XMOS Ltd
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So device ID 20b1:000a
Using lsusb -v to get detail and grep to look just for Audio
Code: pi@moodelr:~ $ lsusb -v -d 20b1:000a|grep Audio
Couldn't open device, some information will be missing
bFunctionClass 1 Audio
bInterfaceClass 1 Audio
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
bInterfaceClass 1 Audio
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
bFunctionClass 1 Audio
bInterfaceClass 1 Audio
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
bInterfaceClass 1 Audio
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
In your case, you'd try
Code: lsusb -v -d 2109:3431
You can leave off the grep'ping to see all the gory details.
Regards,
Kent
Posts: 20
Threads: 3
Joined: Dec 2020
Reputation:
0
(01-04-2021, 07:11 PM)ImInTheMoOdeForAudio Wrote: I think your USB DAC is using a VIA-USB controller, so it's visible already (and usuable I assume). I use a Audio-GD DAC and it shows like this in the lsusb output:
....
Bus 001 Device 004: ID 040d:3410 VIA Technologies, Inc.
....
when I installed Moode at first I did not have sound, but for some reason my DAC was not present when I checked with "aplay -l". What I did was the following:
- I changed the /boot/config.txt:
disable_splash=1
disable_overscan=1
hdmi_drive=2
hdmi_blanking=1
hdmi_force_edid_audio=1
hdmi_force_hotplug=1
hdmi_group=0
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=audio=on
dtparam=audio=off
after a reboot the internal audio (and i2s overlay for HATs) willl be disabled and my USB DAC showed up then (check this with "aplay -l")
now you should be able to see/select your DAC in the MPD config page in the Moode-browser page as output device. Now before you go on: I had one more issue: when I checked with "aplay -l" my DAC was reported as "card 1" for some reason. This will give a problem when you would like to see the "Audio Info" (in the browser-screen - click on the "M" in the upper right corner and select that option). I solved this as follows:
- I created the file /etc/asound.conf and added this:
pcm.!default {
type hw
card 0
}
ctl.!default {
type hw
card 0
}
reboot the system once more and check with "aplay -l" if your DAC is seen on "card 0", see my output:
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Audiogd [Audio-gd], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
now you should be able to see/configure your DAC in the MPD settings page. In theory you should be able to get sound from your DAC, however, in some cases you might run into the UAC2 issue, which means that your music skips or stutters. In the System Config page there is a "USB (UAC2) fix" setting which should do the trick, but this did not work for me (may be a bug, but it can also be an issue with my setup). For me to get it working I added the following to the first line in the /boot/cmdline.txt for this:
dwc_otg.lpm_enable=0 dwc_otg.fiq_fsm_mask=0x3
be sure to add it at the beginning or at the end without a newline (so one long line of text).
you need to reboot in order to get this working.
I hope this will help you
Thank you!
I will keep this under advisement. I have tried to find the card with aplay -l command. My RPi 4 would report 'Pi Headphones' at card 0. I also tried my RPi 3B+ and that would yield an invalid card number error and an ALSA error.
Posts: 20
Threads: 3
Joined: Dec 2020
Reputation:
0
(01-04-2021, 07:38 PM)TheOldPresbyope Wrote: (01-02-2021, 07:09 PM)radiooff Wrote: Hi Kent,
...
I did try the bare RPi 4 with the M100 and still got:
Code: pi@moode:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
...
In keeping with the recent reply by ImInTheMoOdeForAudio, you can confirm if this Via Labs device is indeed your DAC interface, by looking to see if it offers audio-related endpoints.
Here's an example using my Khadas Tone Board which implements its USB interface using a XMOS Ltd chip
Code: pi@moodelr:~ $ lsusb
Bus 002 Device 002: ID 152d:1561 JMicron Technology Corp. / JMicron USA Technology Corp. JMS561U two ports SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 20b1:000a XMOS Ltd
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So device ID 20b1:000a
Using lsusb -v to get detail and grep to look just for Audio
Code: pi@moodelr:~ $ lsusb -v -d 20b1:000a|grep Audio
Couldn't open device, some information will be missing
bFunctionClass 1 Audio
bInterfaceClass 1 Audio
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
bInterfaceClass 1 Audio
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
bFunctionClass 1 Audio
bInterfaceClass 1 Audio
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
AudioControl Interface Descriptor:
bInterfaceClass 1 Audio
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
bInterfaceClass 1 Audio
AudioStreaming Interface Descriptor:
AudioStreaming Interface Descriptor:
AudioStreaming Endpoint Descriptor:
In your case, you'd try
Code: lsusb -v -d 2109:3431
You can leave off the grep'ping to see all the gory details.
Regards,
Kent
Thank you Kent.
I did try the verbose (-v option) on a couple lsusb commands. I could not find any reference to any audio device. Just recognition that something was there. I am on the more novice end for Linux use; but I have put together a MythBox, a few RetroPies and a couple of PiHoles over the years. So, I did not expect to have this much difficulty.
I'll find some other use for the M100. But I did order a Topping D50s and a power supply for it. I'll have those in a few days.
|
