Asus Xonar SE in Ubuntu 19.04 - no sound

Asked by Daniel on 2019-08-16

Hi all,

Recently I have bought the Asus Xonar SE in order to use S/PDIF devices for playback. It was the newest and best I could find for the price, and people on Amazon commented it worked in Ubuntu for them (read about 12.04 & 14.04 being OK).
Now, I don't know how they did it, but I can't get it to work. I have tried many things told about for troubleshooting and solving audio-related problems similair to mine on Ubuntu/Linux, but nothing so far.
I would like to use the S/PDIF output, but also by trying with the analog output on the card had no luck: I have seen no playback.
The card itself is a bit weird. It uses a USB (yes, even though it's PCIe) audio processor from C-Media (the CM6620A), a host controller for USB from AsMedia (ASM1042A) and the S1220A from Realtek as a DAC.

Now software (steps):
I already worked with Alsamixer in the terminal and tried solving the issue with changing volume, but no luck there. This is what it looks like: https://imgur.com/a/fLIotEY
To me it mainly looks odd that none of the outputs are correctly labelled, as they are with working (normal) cards in Alsamixer. It's all PCM ...

Another thing I tried was doing a search on the codecs on the machine, and there it returned this:

==> /proc/asound/card0/codec#0 <==
Codec: Realtek ALC892

==> /proc/asound/card0/codec#2 <==
Codec: Intel Kabylake HDMI

From the return of aplay -l I can see that the Xonar SE is card#1 , but for that there are no codecs available via the command I ran like above (head -n 1 /proc/asound/card*/codec#*).

aplay-l output:

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: SoundCard [Xonar SoundCard], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: SoundCard [Xonar SoundCard], device 1: USB Audio [USB Audio #1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: SoundCard [Xonar SoundCard], device 2: USB Audio [USB Audio #2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: SoundCard [Xonar SoundCard], device 3: USB Audio [USB Audio #3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

The Alsa information output seems fairly complicated to me. I find it difficult to get information from there, but I have the output here: http://alsa-project.org/db/?f=2a945544a53708b95cd185596fd636a60f1c1e62

Btw: I also tried it with a different Ubuntu version (18.04 LTS from USB) and also Mint 19.2. No luck with that either, same result like all of the above information.

Is there anyone who knows what steps I can take to make this work? Or how to diagnose a problem?
Thanks already

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu alsa-driver Edit question
Assignee:
No assignee Edit question
Last query:
2019-08-17
Last reply:
2019-09-01
Daniel (danielboven) said : #1

I forgot to tell that:
1. The card works perfectly in Windows 10 (my PC is dualbooted with REFInd), after having installed the software from the CD Asus provided (so there's no hardware problem there)
2. I have set the output device correctly in the Ubuntu settings panel for sound (it looks like this: https://imgur.com/a/AfJN7ls ). I have also tried changing to different digital profiles in a PulseAudio tool, but no luck with that either.

Launchpad Janitor (janitor) said : #2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Daniel (danielboven) said : #3

This issue got solved with the help of someone on the AskUbuntu.com forum. I have closed that question, the full answer can be found there: https://askubuntu.com/a/1170038/986260