No sound, need help

Just did a clean install of Tumbleweed.
Installed the multimedia packages.

There is no sound.
Sound settings, test produces nothing.
The sound card (SB Live! Audigy SB0570) is configured through Yast

Neither external speaker and internal work.

Where do I go from here?
Thank for the help.

Rebooted, deleted and then re-did the sound cards.
Now it works. Not sure what was wrong.

Thanks, but all working now.

Yes, not an unknown situation – at least on the (AMD) hardware I use …

  • It’s been this way for ages …
  • The golden rule seems to be – install
    rebootconfigure the sound cardsreboot

LOL, tks
It’s working now and that’s what counts.

hello guys, i tried all day to get this working, but no effort.

i tried rebooting the fresh install, then setting with yast and rebooting, still no sound/ no output card detected.

i tried the troubleshooting guide, everything of it. nothing helped.

i have onboard audio on a Gigabyte X570 Gaming, graphics is Powercolor RX550 (HDMI).

i have plugged in headphones in the front and a receiver in the rear audio-jack.
but its not getting recognized. the tray icon says no outpout device found.
pavucontrol only sees the graphics hdmi, but the profiles are all unavailable.
the mainboard audio is not listed at all.

this is the output of the alsa script:

https://pastebin.com/miX0M1ry

Please help me :disapointed::disapointed:

BIOS/UEFI settings?

UEFI, encrypted LVM…
or what do you mean?

or do you mean the motherboard setup at boot?

if i disable HD Onboard Audio in the Mainboard setup, then it disappears from yast.
re enabled, reconfigured, rebooted, still no sound.

Green connectors?
Check connection between front panel and motherboard (F_AUDIO).

Realtek ALC887 codec

yes green connectors.
the connections are good. the green jack on the back (soldered connector on mb) also is not working.

when you look at the alsafile, the folder of the onboard card is empty. also alsa lists only hdmi output devices.

F_AUDIO (Front Panel Audio Header)
The front panel audio header supports High Definition audio (HD). You may connect your chassis front panel audio module to this header. Make sure the wire assignments of the module connector match the pin assignments of the motherboard header. Incorrect connection between the module connector and the motherboard header will make the device unable to work or even damage it.

You need “HD audio” connector, not old-styled AC97.

Detach front panel connectors (when system is powered off) and try again.

yea it was connected to f-audio (left connector at the bottom of the mainboard)
disconnected it, started , no sound at backpanel, no volume knob in tray, no output device visible.

For user hanswurstt …

The script you posted indicated to me the alsa driver (?) may have issues with your hardware. This was the script link you posted: https://pastebin.com/miX0M1ry

I note two alsa modules loaded:


!!Loaded ALSA modules 

!!------------------- 

 

snd_hda_intel (card 0) 

snd_hda_intel (card 1)

Later its clear that one is for HDMI (card-0) and the other (card-1) is for analogue audio:


!!Soundcards recognised by ALSA 
!!----------------------------- 
 
 0 [HDMI           ]: HDA-Intel - HDA ATI HDMI 
                      HDA ATI HDMI at 0xfce60000 irq 113 
 1 [Generic        ]: HDA-Intel - HD-Audio Generic 
                      HD-Audio Generic at 0xfcd00000 irq 115

However “aplay” only recognizes card-0 and does not pickup card-1:


!!Aplay/Arecord output 
!!-------------------- 
 
APLAY 
 
**** List of PLAYBACK Hardware Devices **** 
card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] 
  Subdevices: 1/1 
  Subdevice #0: subdevice #0 
card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1] 
  Subdevices: 1/1 
  Subdevice #0: subdevice #0 
card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2] 
  Subdevices: 1/1 
  Subdevice #0: subdevice #0 
card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3] 
  Subdevices: 1/1 
  Subdevice #0: subdevice #0 
card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4] 
  Subdevices: 1/1 
  Subdevice #0: subdevice #0

Amixer pickups up what could be your analog audio, but it calls it ‘generic’ … and I don’t know if that an issue:


!!-------Mixer controls for card Generic 

 

Card hw:1 'Generic'/'HD-Audio Generic at 0xfcd00000 irq 115' 

  Mixer name    : '' 

  Components    : '' 

  Controls      : 0 

  Simple ctrls  : 0

Further, dmesg indicates a ‘no codec found’ problem;


   51.858937] snd_hda_intel 0000:08:00.1: Force to non-snoop mode 
   51.859137] snd_hda_intel 0000:0a:00.4: enabling device (0000 -> 0002) 
**   51.863336] snd_hda_intel 0000:0a:00.4: no codecs found!**

Typically, by default, sound in openSUSE is sent to card-0, which is HDMI. If you are not using HDMI (card-0) but are using analog sound (card-1), then sound by default will go to a device (HMDI) that you are not using and you will hear nothing. In such a case, the easiet way to address such, is to install ‘pulse audio volume control’ (pavucontrol) and use that to direct sound to card-1. However given Tumbleweed now uses PipeWire in addition to Pulse Audio (where I have not yet learned about Pipewire), and given the Codec error, and given the absence of information about card-1 in aplay, its possible there is an issue with the alsa driver or some other aspect, beyond my skill to help.

If you can not get sound working with pavucontrol app, I recommend you write a bug report on the Tumbleweed kernel. Writing a bug report will get the attention of an openSUSE packager who is also an alsa driver developer, and you will get the best help there, available in the GNU/Linux community.

P.S. - In future, please start a new thread. It is VERY confusing in a thread with two simultaneous helps going on.

Thanks for your reply,
i also noted the things you mentioned, but my knowledge is too far awawy from understanding all this :smiley:

pavucontrol doesnt see the generic soundcard, it sees only the hdmi card.

i dont wanted to start a new thread as i thought maybe im a bit too dumb and the issue could be fixed easily, and the OP seemed to have the same issue.
but i will write a bug report, thank you all for trying to help
:kiss:

 :kiss: