Announcement

Collapse
No announcement yet.

Audio output devices not correctly detected

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Audio output devices not correctly detected

    Updated neon 20.04 (upgraded from 18.04 because the new installer does not allow legacy installation)

    Either the last update (this morning, about a weeks worth up updates) or removing kscreen and using an xrandr script to set my monitors correctly (because kscreen will not keep it's settings) has resulted in no longer being able to use my monitor speakers.
    It appears pulseaudio is no longer correctly identifying my audio outputs correctly.

    Here's the out put of aplay -l:
    Code:
    [FONT=monospace][COLOR=#54FF54][B]stuart@office[/B][/COLOR][COLOR=#000000]:[/COLOR][COLOR=#54FFFF][B]~[/B][/COLOR][COLOR=#000000]$ aplay -l[/COLOR]
    **** List of PLAYBACK Hardware Devices ****
    card 0: PCH [HDA Intel PCH], device 0: ALC1220 Analog [ALC1220 Analog]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    card 0: PCH [HDA Intel PCH], device 1: ALC1220 Digital [ALC1220 Digital]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    card 1: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    card 1: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    card 1: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    card 1: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    card 1: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    [/FONT]
    Here's the connected monitors:
    Code:
    [FONT=monospace][COLOR=#54FF54][B]stuart@office[/B][/COLOR][COLOR=#000000]:[/COLOR][COLOR=#54FFFF][B]~[/B][/COLOR][COLOR=#000000]$ xrandr[/COLOR]
    Screen 0: minimum 320 x 200, current 4920 x 1920, maximum 16384 x 16384
    DisplayPort-0 disconnected (normal left inverted right x axis y axis)
    DisplayPort-1 disconnected (normal left inverted right x axis y axis)
    DisplayPort-2 disconnected (normal left inverted right x axis y axis)
    HDMI-A-0 connected 1080x1920+3840+0 right (normal left inverted right x axis y axis) 527mm x 296mm
    DVI-D-0 disconnected (normal left inverted right x axis y axis)
    DisplayPort-3 connected primary 3840x1600+0+0 (normal left inverted right x axis y axis) 880mm x 367mm
    DisplayPort-4 disconnected (normal left inverted right x axis y axis)
    [/FONT]
    Here's what system settings shows:
    Click image for larger version

Name:	Screenshot_20201023_104738.jpg
Views:	1
Size:	95.8 KB
ID:	649673

    You can see two devices that are NOT connected show connected and the two ACTUALLY connected show unconnected.

    And ideas where to start?

    Please Read Me

    #2
    UPDATE: Ok, weird but working; I switched to HDMI-5 in System Settings and it started working. I'm not sure why the devices do not correspond with xrandr but I can live with that.

    Please Read Me

    Comment


      #3
      This solution worked for me:
      Open the alsa configuration file: kate /etc/modprobe.d/alsa-base.conf

      Add the following line to the end of this file: options snd-hda-intel dmic_detect=0

      Reboot.

      Comment


        #4
        Originally posted by Avi512 View Post
        This solution worked for me:
        Open the alsa configuration file: kate /etc/modprobe.d/alsa-base.conf

        Add the following line to the end of this file: options snd-hda-intel dmic_detect=0

        Reboot.
        I appreciate the suggestion, but what does it do and why?

        Please Read Me

        Comment


          #5
          This is (iirc) specific to the common Realtek ALC892 (and porb others), which uses the snd_hda_intel kerenl module.
          It seems the option dmic_detect in the 5.4 kernel is set to 'on' , or this option was added to the module, not sure. Still haven't discovered what the option actually does. Lots of folks lost their sound cards, and disabling the option seems to be the fix in 5.4.
          Of course no one testing Ubuntu with this kernel ever noticed this problem, somehow?

          https://bugs.archlinux.org/task/64720
          Gotta love them arch users/hackers
          Last edited by claydoh; Oct 24, 2020, 08:46 AM.

          Comment

          Working...
          X