Detection of exasound e38 over USB?

Audio Gear Talk RoPieee
1

Just installed the most recent RoPieee on a Pi 3 B, connected to exasound e38 over USB. The kernel picks up the device in dmesg, but aplay -l shows “no sound cards found”.
Here’s a snippet from dmesg when connecting the sound card:
[ 141.160670] usb 1-1.5: new high-speed USB device number 5 using dwc_otg
[ 141.294261] usb 1-1.5: New USB device found, idVendor=0403, idProduct=6010, bcdDevice= 7.00
[ 141.294369] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 141.294457] usb 1-1.5: Product: exaSound-e38-1.0
[ 141.294516] usb 1-1.5: Manufacturer: FTDI
[ 141.294569] usb 1-1.5: SerialNumber: FT17NNKQ
[ 141.299070] snd-rpi-justboom-dac soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 141.319299] usbcore: registered new interface driver usbserial_generic
[ 141.320070] usbserial: USB Serial support registered for generic
[ 141.330335] usbcore: registered new interface driver ftdi_sio
[ 141.333284] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 141.336148] ftdi_sio 1-1.5:1.0: FTDI USB Serial Device converter detected
[ 141.338852] usb 1-1.5: Detected FT2232H
[ 141.341802] usb 1-1.5: FTDI USB Serial Device converter now attached to ttyUSB0
[ 141.344832] snd-rpi-justboom-dac soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 141.346155] ftdi_sio 1-1.5:1.1: FTDI USB Serial Device converter detected
[ 141.350711] snd-rpi-justboom-dac soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 141.355784] usb 1-1.5: Detected FT2232H
[ 141.364238] usb 1-1.5: FTDI USB Serial Device converter now attached to ttyUSB1
[ 141.367604] snd-rpi-justboom-dac soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 141.376390] snd-rpi-justboom-dac soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry

I tried connecting a Pioneer USB DAC and that works (with the exception of DoP not locking, but that’s a different story that I may create a topic for later).

Any advice on how to troubleshoot further, @spockfish ?

2

Created a feedback item for this problem. (Ignore the first one - cd14846c9e8fab64 - that was taken before plugging in the DAC…) Proper feedback ID is 5ff76da12824a3db.
Thanks

Edit:
Just rememberd that I had tried enabling a random HAT output, but that didn’t help. The feedback was created with the HAT enabled. Let me know if you need me to produce another feedback item with just USB audio or if what you have is enough.

3

In case you have not heard, exaSound does not provide drivers for Linux and, afaik, their DACs won’t work without them.

4

Ah, good point… Thanks, I didn’t think of that. Meaning that to use the e38 with Roon I’d either have to keep using the exasound “Playpoint” (that I was hoping I could sell and replace with RoPieee and the touch display) or roll a Windows or Mac computer so I could use the drivers…
I guess I could upgrade my Audiophile Optimizer license and set up w10 plus roon core on the Intel NUC that I’m currently running ROCK on (connected to my stereo rig) and move it to the exasound and then setup the RoPieee for the stereo rig instead.

5

Or sell it and replace it with a less expensive Sigma Streamer.

6

Thanks for the advice and troubleshooting help. I was able to get a good solution by adding Roon and the Exasound drivers to a W10 PC that was already in the multichannel rig that I normally use to run Kodi for watching movies. It can easily cope with both duties.