Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: snd_hda_intel alsa have to modprobe remove install each restart. Why?

  1. #1

    Question snd_hda_intel alsa have to modprobe remove install each restart. Why?

    Since a Tumbleweed dup about a month ago I have had problems with sound.

    I have removed all sound installs and configs and started again. Starting with alsa, and then adding pulseaudio thereafter.
    However, I have been plagued by a problem I cannot resolve.
    That is at each restart the sound requires reconfiguring.
    Initially, with only alsa, I would use the Yast2 sound, disable the onboard sound card and then exit and then using yast2 sound config again, re-enable the card using the "normal" option.
    Sound would work again but only for that session.
    Using alsa store did not resolve.

    Since then I have realised that it seems to be a module issue as I can resolve for that session by running as root:
    Code:
    # modprobe -r snd_hda_intel; modprobe snd_hda_intel; systemctl restart sound.target alsa-state.service
    My HDMI unfortunately has the same module.
    So this is quite possibly an underlying reason for the problem.

    I need some help to resolve what is going on and why please so it can be fixed.

    When it is failing (ie after a restart) I get:

    Code:
    # aplay -l
    aplay: device_list:272: no soundcards found...
    
    # cat /proc/asound/cards
      --- no soundcards ---
    After the modprobe remove and install and alsa being restart I get:
    Code:
    #  aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: PCH [HDA Intel PCH], device 0: Generic Analog [Generic Analog]
      Subdevices: 0/1
      Subdevice #0: subdevice #0
    card 0: PCH [HDA Intel PCH], device 1: Generic Digital [Generic Digital]
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    card 0: PCH [HDA Intel PCH], device 3: Generic Digital [Generic 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
    
    # cat /proc/asound/cards
     0 [PCH            ]: HDA-Intel - HDA Intel PCH
                          HDA Intel PCH at 0xdf220000 irq 128
     1 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                          HDA ATI HDMI at 0xdf160000 irq 126
    For background I had an Xonar card in the machine but have removed this as I had even greater problems having Suse install this.
    It is now removed. And because of that history I removed all configurations and conf files for sound that I could, incl alsa, pulseaudio and jack.
    Only alsa, and then later pulseaudio have been reinstalled now.

    I would like to work out how to permanently solve this problem and
    how to also blacklist the Card 1 [HDMI ] "HDA-Intel - HDA ATI HDMI"

    Can anyone please help with resolving this?

    Thankyou

  2. #2

    Default Re: snd_hda_intel alsa have to modprobe remove install each restart. Why?

    I realised I did not include the card pci info and some other install info may be useful. I cannot see an "edit" option for the post so here further info is as a comment:
    (Also can forum administrator please remove my comment above that was only part completed and is contained in this comment. Thanks.)

    Full alsa info from /usr/sbin/alsa-info.sh script is at http://alsa-project.org/db/?f=da2281...4e255da8abc597

    lspci | grep -ie snd -ie audio -ie sound
    Code:
    # lspci | grep -ie snd -ie audio -ie sound
    00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
    01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
    rpm -qa '*alsa*'
    Code:
    # rpm -qa '*alsa*'
    alsa-firmware-1.0.29-2.2.noarch
    alsa-1.1.9-2.1.x86_64
    alsa-utils-1.1.9-2.1.x86_64
    alsa-plugins-pulse-32bit-1.1.9-1.3.x86_64
    alsa-oss-1.1.8-1.4.x86_64
    qemu-audio-alsa-4.0.0-5.1.x86_64
    alsa-plugins-pulse-1.1.9-1.3.x86_64
    alsa-plugins-1.1.9-1.3.x86_64
    rpm -qa '*pulse*'
    Code:
    #rpm -qa '*pulse*'
    pulseaudio-module-zeroconf-12.2-6.1.x86_64
    mpg123-pulse-1.25.10-2.4.x86_64
    xfce4-panel-plugin-pulseaudio-0.4.1-1.5.x86_64
    libpulse0-32bit-12.2-6.1.x86_64
    alsa-plugins-pulse-32bit-1.1.9-1.3.x86_64
    pulseaudio-lang-12.2-6.1.noarch
    alsa-plugins-pulse-1.1.9-1.3.x86_64
    xfce4-volumed-pulse-0.2.3-1.6.x86_64
    pulseaudio-module-bluetooth-12.2-6.1.x86_64
    libpulse0-12.2-6.1.x86_64
    pulseaudio-12.2-6.1.x86_64
    pulseaudio-bash-completion-12.2-6.1.x86_64
    libpulse-mainloop-glib0-12.2-6.1.x86_64
    pulseaudio-utils-12.2-6.1.x86_64
    xfce4-panel-plugin-pulseaudio-lang-0.4.1-1.5.noarch
    rpm -q libasound2
    Code:
    # rpm -q libasound2
    libasound2-1.1.9-2.1.x86_64
    uname -a
    Code:
    # uname -a
    Linux linux-h5nt.suse 5.1.16-1-default #1 SMP Wed Jul 3 12:37:47 UTC 2019 (2af8a22) x86_64 x86_64 x86_64 GNU/Linux
    cat /etc/modprobe.d/50-sound.conf
    Code:
    #cat /etc/modprobe.d/50-sound.conf
    options snd slots=snd-hda-intel index=0 model=generic
    #options snd_hda_codec_hdmi id=HDMI index=1
    # nS1_.aeKjouZo5Y7:100 Series/C230 Series Chipset Family HD Audio Controller
    alias snd-card-0 snd-hda-intel
    #alias snd-card-1 snd_hda_codec_hdmi
    cat /etc/modprobe.d/alsa-base.conf
    Code:
    #cat /etc/modprobe.d/alsa-base.conf
    options snd_hda_intel index=0 model=generic
    #options snd_hda_codec_hdmi id=HDMI index=1

  3. #3
    Join Date
    Oct 2014
    Location
    Italy
    Posts
    1,669

    Default Re: snd_hda_intel alsa have to modprobe remove install each restart. Why?

    Looks similar to this problem: https://lists.opensuse.org/opensuse-.../msg00121.html
    Please see if there is a useful hint there...
    Main: Leap 15 Gnome on i7 4720HQ + Geforce GTX960M
    Test: Leap 42.3 (& others) on Core2Duo + GM965

  4. #4
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,517
    Blog Entries
    37

    Default Re: snd_hda_intel alsa have to modprobe remove install each restart. Why?

    further to OrsoBruno's suggestion ... Takashi (who is an alsa developer) noted:

    https://lists.opensuse.org/opensuse-.../msg00123.html

    and I quote:

    My wild guess is that you've put snd-hda-intel into initrd unnecessarily and incompletely. Maybe YaST did that incorrectly.
    Check and remove the contents of /etc/module-load.d/yast.conf, and recreate initrd.

  5. #5

    Smile Re: snd_hda_intel alsa have to modprobe remove install each restart. Why?

    Thankyou OrsoBruno and oldcpu!

    I will try these in the morning, starting first with oldcpu's suggestion re Takashi as that file does indeed contain the unnecessary and incomplete snd-hda-intel.
    So it sounds most likely that will be the reason.
    Why yast would do this causing this problem is beyond me but the timestamp on that file goes back to April.
    For a certainty I would not have made that change.

    Also do you know if there is a way to blacklist the HDMI audio on the graphics card?

    From my system:
    Code:
    # cat /etc/modules-load.d/yast.conf 
    snd-hda-intel
    
    # ls -laht /etc/modules-load.d/yast.conf 
    -rw-r--r-- 1 root root 14 Apr 28 15:05 /etc/modules-load.d/yast.conf

    Quote Originally Posted by oldcpu View Post
    further to OrsoBruno's suggestion ... Takashi (who is an alsa developer) noted:
    https://lists.opensuse.org/opensuse-.../msg00123.html
    and I quote:
    My wild guess is that you've put snd-hda-intel into initrd
    unnecessarily and incompletely. Maybe YaST did that incorrectly.
    Check and remove the contents of /etc/module-load.d/yast.conf, and
    recreate initrd.

  6. #6

    Default Re: snd_hda_intel alsa have to modprobe remove install each restart. Why?

    Update:
    Suggestions above did not work.
    I would still like to resolve this to enable successful manual configure without yast, as yast seems to create too many problems for me with sound configuring.
    However, after trying the above, there was a LOT (>3000) Tumbleweed updates for my system.
    Since the update, sound works without a restart. Although zypper dup automatically installed modules I had removed, at least
    Code:
    lsa-plugins-pulse-32bit-1.1.9-1.4.x86_64
    pulseaudio-module-bluetooth-12.2-6.2.x86_64
    pulseaudio-module-zeroconf-12.2-6.2.x86_64
    pulseaudio-utils-32bit-12.2-6.2.x86_64
    Back to the manual configuration...
    I tried first just clearing "/etc/modules-load.d/yast.conf" and rebuilding initrd with"grub2-mkconfig". That did not result in sound upon restart.
    Next I tried as per the abovementioned thread of Bjoern Voigt.
    The rmmod removed several dependency modules that required adding back.
    So for me this is the resulting insmod's stack required if someone is using insmod rather than modprobe (which calls insmod for also dependencies) for installation:
    Code:
    insmod /lib/modules/5.1.16-1-default/kernel/sound/soundcore.ko
    insmod /lib/modules/5.1.16-1-default/kernel/sound/core/snd.ko
    insmod /lib/modules/5.1.16-1-default/kernel/sound/core/snd-timer.ko
    insmod /lib/modules/5.1.16-1-default/kernel/sound/core/snd-pcm.ko
    insmod /lib/modules/5.1.16-1-default/kernel/sound/hda/snd-hda-core.ko
    insmod /lib/modules/5.1.16-1-default/kernel/sound/core/snd-hwdep.ko
    insmod /lib/modules/5.1.16-1-default/kernel/sound/pci/hda/snd-hda-codec.ko
    insmod /lib/modules/5.1.16-1-default/kernel/sound/pci/hda/snd-hda-intel.ko
    After installing the modules, removing the contents of "/etc/modules-load.d/yast.conf", and rebuilding init via "grub2-mkconfig", alsa still did not work after reboot with /proc/asound/cards showing "no soundcards".

    Maybe I have missed some required step?

    So I am not really sure what else the zypper dup did that has it now working, but would like to know so I can destroy the sound files and modules and rebuild them by hand rather than rely on yast.

    Any ideas on this?

    Also I would still like to blacklist the radeon graphics HDMI audio that uses the same snd_hda_intel module as the mainboard audio, the later of which is the only one I am using.
    Any ideas on how to blacklist by card/pci/vendor:device etc rather than module name?

    Thanks again

    motiv8d

  7. #7
    Join Date
    Jun 2008
    Location
    Belleville, Ontario, Canada
    Posts
    429

    Default Re: snd_hda_intel alsa have to modprobe remove install each restart. Why?

    Quote Originally Posted by motiv8d View Post
    rebuilding initrd with"grub2-mkconfig"
    I've always used mkinitrd to rebuild intrd. I don't know, maybe that will work for you, too. Worth a try, right?
    "Making rich people richer doesn't make the rest of us richer."
    Ha-Joon Chang

    openSUSE 15.0 4.12.14-lp150.12.45-default x64

  8. #8

    Default Re: snd_hda_intel alsa have to modprobe remove install each restart. Why?

    Thanks Kerijan2003. I had presumed grub2-mkconfig would also use dracut to mkinitrd.
    grub2-mkconfig not doing it would fit with my experience as part of the updates was a new kernel, which would have been built with snd-hda-intel removed already from the yast.conf file.
    I will look at testing it directly.

    Quote Originally Posted by kerijan2003 View Post
    I've always used mkinitrd to rebuild intrd. I don't know, maybe that will work for you, too. Worth a try, right?

  9. #9
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    888

    Default Re: snd_hda_intel alsa have to modprobe remove install each restart. Why?

    Quote Originally Posted by motiv8d View Post
    I realised I did not include the card pci info and some other install info may be useful. I cannot see an "edit" option for the post so here further info is as a comment:
    (Also can forum administrator please remove my comment above that was only part completed and is contained in this comment. Thanks.)

    Full alsa info from /usr/sbin/alsa-info.sh script is at http://alsa-project.org/db/?f=da2281...4e255da8abc597

    lspci | grep -ie snd -ie audio -ie sound
    Code:
    # lspci | grep -ie snd -ie audio -ie sound
    00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
    01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]
    The same on my machine:

    Code:
    erlangen:~ #  lspci | grep -ie snd -ie audio -ie sound
    00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
    erlangen:~ #
    The other device may interfere with built in Intel. As a test turn off AMD using "yast sound":


    ┌───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
    │Sunrise Point-H HD Audio │
    │ │
    │ * Configured as sound card number 0 │
    │ * Driver snd-hda-intel
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  10. #10

    Default Re: snd_hda_intel alsa have to modprobe remove install each restart. Why?

    That is my point karlmistelberger.
    I DON'T WANT to be using yast for sound. Yast has caused too many problems with sound for me.
    So I would like to determine the processes required for sound set up and control on OpenSuse without Yast.

    Yast seems to have been confused by multiple cards that use the same snd_hda_intel module.

    If I was going to use Yast, thus I would like to know how to blacklist by PCI etc rather than module, because of course blacklisting by module is going to stop all sound.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •