HDA Intel; No sound in system. Opensuse 12.1

Done as indicated in post #2 above:
ALSA SOUND information is at link hhttp://www.alsa-project.org/db/?f=44de8994cd15de5673b259a4f3da6b37d723c422, that file is to big to load it here
other information you requested is:

cat /etc/modprobe.d/50-sound.conf

options snd slots=snd-hda-intel

u1Nb.kURRCMIOEo3:82801H (ICH8 Family) HD Audio Controller

alias snd-card-0 snd-hda-intel

NetAngel:/home/ioan/packages

rpm -qa ‘alsa

alsa-oss-32bit-1.0.17-37.1.2.x86_64
alsa-plugins-pulse-32bit-1.0.24-18.1.2.x86_64
alsa-plugins-1.0.24-18.1.2.x86_64
alsa-plugins-pulse-1.0.24-18.1.2.x86_64
alsa-devel-1.0.24.1-23.1.2.x86_64
alsa-plugins-32bit-1.0.24-18.1.2.x86_64
alsa-1.0.24.1-23.1.2.x86_64
alsa-utils-1.0.24.2-12.8.1.x86_64
alsa-oss-1.0.17-37.1.2.x86_64
NetAngel:/home/ioan/packages

rpm -qa ‘pulse

libxine1-pulse-1.1.19-9.7.2.x86_64
alsa-plugins-pulse-32bit-1.0.24-18.1.2.x86_64
pulseaudio-1.1-1.2.x86_64
alsa-plugins-pulse-1.0.24-18.1.2.x86_64
libpulse0-1.1-1.2.x86_64
libpulse0-32bit-1.1-1.2.x86_64
libpulse-mainloop-glib0-1.1-1.2.x86_64

NetAngel:/home/ioan/packages # rpm -q libasound2
libasound2-1.0.24.1-23.1.2.x86_64

cat /etc/modprobe.d/50-sound.conf

options snd slots=snd-hda-intel

u1Nb.kURRCMIOEo3:82801H (ICH8 Family) HD Audio Controller

alias snd-card-0 snd-hda-intel
/home/ioan/packages #

Thanks a lot for your help effort and dedication expecting your feedback, friendly yours SH

I have done what you requested, please look here under…thanks again SH.

I am not familiar with audacity. Does it use pulse ?

You need to run pauvcontrol at the same time as Skype is doing the test call. And look at both Configuration Tab , Input Tab (ensure you select SHOW all input devices) and RECORDING Tab (ensure you select SHOW to ‘all streams’ ).

According to that I note for your recording devices:


ARECORD

**** List of CAPTURE Hardware Devices ****
**card 0**: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
  Subdevices: 2/3
  **Subdevice #0**: subdevice #0
  **Subdevice #1**: subdevice #1
  **Subdevice #2**: subdevice #2

ie your record devices are hw:0,0 , hw:0,1 , hw:0,2 … you need to figure out which one is your external mic jack that you are using.

I also do not understand your mixer settings … I note:


**!!Amixer output**
!!-------------

!!-------Mixer controls for card 0 [Intel]

**Card hw:0 'Intel'/'HDA Intel at 0x50200000 irq 45'**
  Mixer name	: 'SigmaTel STAC9227'
**Simple mixer control 'Line Jack Mode',0**
  Items: 'Mic In' 'Line In' 'Line Out'
  Item0: **'Line Out'**
Simple mixer control 'Capture',0
  Front Left: Capture 12 [86%] [18.00dB] **[on]**
  Front Right: Capture 12 [86%] [18.00dB] **[on]**
**Simple mixer control 'Capture',1**
  Front Left: Capture 14 [100%] [21.00dB] **[off]**
  Front Right: Capture 14 [100%] [21.00dB] **[off]**
**Simple mixer control 'Capture',2**
  Front Left: Capture 14 [100%] [21.00dB] **[off]**
  Front Right: Capture 14 [100%] [21.00dB] **[off]**
**Simple mixer control 'Digital',0**
  Front Left: Capture 120 [100%] [30.00dB]
  Front Right: Capture 120 [100%] [30.00dB]
**Simple mixer control 'Input Source',0**
  Items: 'Mic' 'Line'
  Item0: 'Mic'
**Simple mixer control 'Input Source',1**
  Items: 'Mic' 'Line'
  Item0: **'Line'**
**Simple mixer control 'Input Source',2**
  Items: 'Mic' 'Line'
  Item0: **'Line'**
**Simple mixer control 'Mux',0**
  Front Left: Capture 4 [100%] [40.00dB]
  Front Right: Capture 4 [100%] [40.00dB]
**Simple mixer control 'Mux',1**
  Front Left: Capture 4 [100%] [40.00dB]
  Front Right: Capture 4 [100%] [40.00dB]
**Simple mixer control 'Mux',2**
  Front Left: Capture 4 [100%] [40.00dB]
  Front Right: Capture 4 [100%] [40.00dB]
**Simple mixer control 'Rear Mic Jack Mode',0**
  Items: 'Mic In' 'Line In'
  Item0: **'Line In'**

You have rear jack mic set to Line-in … ie NOT to a mic. So I assume you are not using a rear mic. You have ‘input source 2’ and ‘input source 1’ set to Line In. Are you certain neither of those controls correspond to the input jack you are using for your external mic ? And you have 'Simple mixer control ‘Line Jack Mode’ set to Line-In. Is that correct ? Should it be ‘mic’ ?

Reference your record devices are hw:0,0 , hw:0,1 , hw:0,2, I recommend you test with arecord command. For example, for hw:0,0


arecord -v -f S16_LE -c 2 -D hw:0,0 new.wav

where the audio is saved to file new.wav. The recording is stopped by pressing . One MUST pay attention to the arecord errors. I have assumed 2 channels ( -c 2 ) but maybe it should be one channel ( -c 1 ). I have assumed format S16_LE but I could be wrong.

similar for hw:0,1


arecord -v -f S16_LE -c 2 -D hw:0,1 new.wav

similar for hw:0,2


arecord -v -f S16_LE -c 2 -D hw:0,2 new.wav

I think only you can do that. … But we can provide suggestions to test. I note an AD1988B on a 64-bit openSUSE-12.1 with the stock alsa version.

If you look at the HD-Audio-Models.txt file (that is on your PC) or simply google it, you will note this list for the AD1988B:


AD1988/AD1988B/AD1989A/AD1989B
==============================
  6stack	6-jack
  6stack-dig	ditto with SPDIF
  3stack	3-jack
  3stack-dig	ditto with SPDIF
  laptop	3-jack with hp-jack automute
  laptop-dig	ditto with SPDIF
  auto		auto-config reading BIOS (default)

thats only one option of many that need be tried, with a restart of the alsa sound driver needed inbetween (and a restart of the mixer).

I also recommend you install pavucontrol and use that to tune your audio.

Hi oldcpu,
Thanks for your answer. I put in post #21 all information required by you in post #2. You recommend to use some information but I am afraid I do NOT understand which value you recommend for which options. Please be more precise, I am far from a sound card expert…
thanks friendly yours SH

Hi OldCPU,
I am not sure how valuable this information might be. I am a SUSE user since probably before version 9, probably even older. I regularly update and I do not remember , since 3-4 years I am using this PC, that I ever had to do ANYTHING in terms of sound driver configuration. All worked in SUSE 11.1–>11.4 like a charm. This explains my ignorance in this matter. I asked if someone can explain me what values are required for what options in the YAST sound card configuration, but I must say that do not understand how the information you indicate should be used.
When I do the test of sound card the test is not always working: I hear regular noise in the head set, the sound test is either mute or played but partially, sometimes completely. I installed the program you mentioned (pavucontrol) but it does not start, it crashes and says it can not connect to the audio. On the other hand remember that the PC is in dual boot and in when XP is booted, all works like a charm…thanks a lot for all your efforts, expecting your feedback, friendly yours SH.

If you have had no success thus far, then maybe you should write a bug report and get the attention of THE SuSE-GmbH packager for sound, who is also an alsa sound driver developer. There is guidance here for bug reports: openSUSE:Submitting bug reports - openSUSE you can use your openSUSE forum username and password when logging on to bugzilla. Attach to the bug report the /tmp/alsa-info.txt text file that you get from running:


/usr/sbin/alsa-info.sh --no-upload

and monitor the bug report , checking every day or so. Watch for a ‘need info’ flag, which the SuSE-GmbH packager (alsa developer) will set when asking for information. Provide the information, and then clear the flag after providing it. The SuSE-GmbH packager for sound is very good at solving sound problems and when they come up with a fix, they pass it upstream so that all GNU/Linux distributions can benefit.

You can mention that in the bug report. I note:

NetAngel:/home/ioan/packages # rpm -qa '*pulse*'
libxine1-pulse-1.1.19-9.7.2.x86_64
alsa-plugins-pulse-32bit-1.0.24-18.1.2.x86_64
pulseaudio-1.1-1.2.x86_64
alsa-plugins-pulse-1.0.24-18.1.2.x86_64
libpulse0-1.1-1.2.x86_64
libpulse0-32bit-1.1-1.2.x86_64
libpulse-mainloop-glib0-1.1-1.2.x86_64

hence you do have pulse audio installed so pavucontrol should work.

I would just like to add my experience to this thread, as I was having exactly the same problem after upgrading from 11.4 to 12.1

I tried everything, and then it occurred to me to check my user permissions. For some reason, I had been removed from the Audio group during the upgrade process. One reboot later, and I had sound again.

Hi all of you!!
I am running SUSE 12.1 64bits KDE and though I have flash installed and no sound problems when booting XP (my PC is dual boot) I DO HAVE problems with Firefox and chrome when getting going to YouTube: in Youtube NO SOUND AT ALL, while YAST sound test worked perfectly well.
I opened a bug with Bugzilla (732872) and while looking at other bugs e.g. 725701 I found out that sound works when you enter as root. Even in you KDE session, just open a terminal, enter SU and start Firefox from there: for me that worked and sound came back like in a charm.
Since in fact I did an upgrade to SUSE 12.1, I did not change anything in my home directory and it seems to me problem comes from there: some of my old settings disturb sound when using chrome or Firefox 8.0, because both have sound once lunched from root.
I dare suspect that this has nothing to do with root privileged, it might work for any “new user”.
SO FORGET sound driver issues or ALSA problems: when you have sound problems with Chrome or Firefox 8.0 products, change user…e.g; go to root and problem might be solved. It was for me at least!!

                                                                         have fun.

YES YES YES…this is the way to solve this. Just go to YAST, manage user-groups and ensure you user name is in AUDIO group. Forget my previous post, it’s not wrong, but “root” is in any group and thus in AUDIO group and this is why it worked. THE REAL way to correct this bug is the way puzzeled pinguin suggested: he is right!! I did it and it worked for me…thanks to him, friendly yours SH.

ОК, now I have repaired also a microphone. :slight_smile:
Thanks, oldcpu!!

Can I ask more?
Tell, where this information is available? There is a table of conformity? How did you know?

Great news.

Its on your computer (and mine) under the sound documentation that comes with the kernel delivery. As you may or may not know, with the kernel comes the alsa sound driver. So accordingly the documentation for the sound driver also is provided with the kernel. Hence, one can look under the documentation for their kernel version. Now I am using an openSUSE-11.4 PC with the 2.6.37.6-0.9 kernel, so on my PC if I look under:


/usr/src/linux-2.6.37.6-0.9/Documentation/sound/alsa/

I will find the alsa sound driver documentation for that kernel version. Your PC will be similar (but your kernel version different). The model options will be in the HD-Audio-Models.txt file.

Hi all.
I just upgraded to 12.1 from 11.4 and am having sound issues (again:(). In 11.3 I had both mic and output working. In 11.4 I never got the mic to work, but at least I could watch videos and listen to music. Now in 12.1 I have no sound input or output whatsoever. So here is the out put of the commands listed in the guidlines:

http://www.alsa-project.org/db/?f=2830c4716f97dd2f23f24528fabef3a5d7de6b68

#rpm -qa ‘alsa

alsa-firmware-1.0.24.1-7.1.1.noarch
alsa-utils-1.0.24.2-12.8.1.x86_64
alsa-plugins-pulse-32bit-1.0.24-18.1.2.x86_64
alsa-plugins-32bit-1.0.24-18.1.2.x86_64
alsa-plugins-jack-1.0.24-18.1.2.x86_64
java-1_6_0-sun-alsa-1.6.0.u29-0.2.1.x86_64
pyalsa-1.0.22-9.1.2.x86_64
alsa-devel-1.0.24.1-23.1.2.x86_64
alsa-plugins-jack-32bit-1.0.24-18.1.2.x86_64
alsa-oss-1.0.17-37.1.2.x86_64
alsamixergui-0.9.0rc1-755.1.2.x86_64
alsa-1.0.24.1-23.1.2.x86_64
alsa-tools-gui-1.0.24.1-12.1.2.x86_64
alsa-plugins-pulse-1.0.24-18.1.2.x86_64
alsa-oss-32bit-1.0.17-37.1.2.x86_64
alsa-plugins-1.0.24-18.1.2.x86_64

#rpm -qa ‘pulse
pulseaudio-utils-1.1-1.2.x86_64
alsa-plugins-pulse-32bit-1.0.24-18.1.2.x86_64
pulseaudio-equalizer-2.7rev4-1.2.noarch
libpulse0-32bit-1.1-1.2.x86_64
alsa-plugins-pulse-1.0.24-18.1.2.x86_64
libpulse0-1.1-1.2.x86_64
libpulse-mainloop-glib0-1.1-1.2.x86_64
pulseaudio-1.1-1.2.x86_64

rpm -q libasound2

libasound2-1.0.24.1-23.1.2.x86_64

uname -a

Linux homepc 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3 14:45:45 UTC 2011 (187dde0) x86_64 x86_64 x86_64 GNU/Linux

cat /etc/modprobe.d/50-sound.conf

options snd slots=snd-hda-intel,snd-hda-intel

u1Nb.ZbI9NHBokA7:5 Series/3400 Series Chipset High Definition Audio

alias snd-card-0 snd-hda-intel

NXNs.TTZRWxxfTa1:nVidia Corporation

alias snd-card-1 snd-hda-intel

Reading through this thread gives me hope so I’m looking forward to getting some advice on this.
Thanks in advance.

I am hopeful that we should be able to get your sound working … I note a 64-bit opeSUSE-12.1 with the 3.1.0-1.2-desktop kernel with the alsa sound driver version 1.0.24, the alsa sound library version 1.0.24.1 and the alsa utilities version: 1.0.24.2. Your PC has a VIA VT1708S hardware audio codec.

The first thing I recommend you do is install the application pulse audio volume control (pavucontrol) and use that to tune the audio for each multimedia application. In pavucontrol ensure that you have the VT1708S Analog device selected (or the VT1708S Digital device) and not the HDMI devices. Run pavucontrol the 1st time you run each multimedia application and when trying to play back audio ensure the Output Devices tab has SHOW to all Output devices and that they are not muted and the Playback tab has the correct output device selected.

Now for additional sound testing, I note this for your hardware for sound playback:


**!!Aplay/Arecord output**
!!------------

APLAY
**
**** List of PLAYBACK Hardware Devices ******
**card 0:** Intel [HDA Intel], **device 0:** VT1708S Analog [VT1708S Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
**card 0**: Intel [HDA Intel], **device 1**: VT1708S Digital [VT1708S Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
**card 0**: Intel [HDA Intel], **device 2:** VT1708S HP [VT1708S HP]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
**card 1**: NVidia [HDA NVidia], **device 3**: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
**card 1**: NVidia [HDA NVidia], **device 7**: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
**card 1**: NVidia [HDA NVidia], **device 8**: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
**card 1**: NVidia [HDA NVidia], **device 9**: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

From that I can see you have 7 audio devices on this PC: hw:0,0 (analog audio), hw:0,1 (digital audio) , hw:0,2 (HP audio - I have no idea what that is) , hw:1,3 (HDMI audio output), hw:1,7 (HDMI audio output), hw:1,8 (HDMI audio output), hw:1,9 (HDMI audio output) . Now you did not state which device in your PC you are attempting to use for audio. I assume it is hw:0,0 (most likely) with only a very unlikely possibility it is hw:0,1 or hw:0,2 and most unlikely it is the HDMI (at this stage).

So for hw:0,0 (your PC analog audio) you could try a simply sound test for the audio using the application ‘aplay’ , assuming you have a .wav file on your computer (lets assume you have a file called ‘new.wav’ - you need to provide such a file) :


aplay -D hw:0,0 -c 2 test.wav

run that as a regular user in a terminal, and if that fails try root permissions in that terminal (only). Note I assumed 2 channel sound in this example with ’ -c 2 '. Its possible you might need something other than ‘2’ for 2 channel sound. If you were trying digital or hp audio, you would use hw:0,1 or hw:0,2 instead of hw:0,0 as appropriate.

Another command for testing audio as a regular user in a terminal (and also if that fails as root in ONLY a terminal) is


speaker-test -D hw:0,0 -c2 -l5 -twav

where I am assuming a 2 channel system using device hw:0,0 (if it were device hw:0,1 or hw:0,2 you would need to use that instead). If this was a 5.1 surround sound system you could try:


speaker-test -D hw:0,0 -c6 -l5 -twav

Lets assume none of that works, and further lets wildly speculate that the alsa sound driver needs configuring upon booting (but I see no evidence from the dmesg in the diagnostic script output that you provided that that is the case - I am just adding this for completeness). In that case I would look to see if there are any model options that can be forced for your VIA VT1708s. To do that we look at the documentation that is on your PC, in the location /usr/src/your-kernel/Documentation/sound/alsa/ in the file HD-Audio-Models.txt file that you must know about since it is noted in this thread and you elected to post your problem on this same thread. In that file that is on your pc, you will note the section:


VIA VT17xx/VT18xx/VT20xx
========================
  auto		BIOS setup (default)

which suggests for your VIA 1708s there is only one alsa option that can be forced, where that is ‘auto’.

So if the above tests failed to produce sound, you could then with root permissions edit your PC’s /etc/modprobe.d/50-sound.conf file and add this line to the START of that file:


options snd-hda-intel model=auto

so that that file looks like:


options snd-hda-intel model=auto
options snd slots=snd-hda-intel,snd-hda-intel
# u1Nb.ZbI9NHBokA7:5 Series/3400 Series Chipset High Definition Audio
alias snd-card-0 snd-hda-intel
# NXNs.TTZRWxxfTa1:nVidia Corporation
alias snd-card-1 snd-hda-intel 

save the change, restart your PC and test the sound.

Glad to read that, … but from my view your posting on this solved thread just confuses me as I can not see the relationship between this thread and your problem. How much time must I spend studying someone else’s problem that appears to me to have no relationship to yours ?

Please next time start a new thread. Daily I search for ‘sound’ and ‘mic’ and ‘audio’ and look for sound issues, so if you are trying to get the attention for a sound problem, tagging on to a different users problem, where that user has different hardware, is not the best way to do this.

Good luck and I hope we succeed here.

Here is what I get:

speaker-test -D hw:0,0 -c2 -l5 -twav

speaker-test 1.0.24.2

Playback device is hw:0,0
Stream parameters are 48000Hz, S16_LE, 2 channels
WAV file(s)
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 64 to 262144
Period size range from 32 to 131072
Using max buffer size 262144
Periods = 4
was set period_size = 65536
was set buffer_size = 262144
0 - Front Left
1 - Front Right
Time per period = 5.463046
0 - Front Left
1 - Front Right
Time per period = 5.464977
0 - Front Left
1 - Front Right
Time per period = 5.464361
0 - Front Left
1 - Front Right
Time per period = 5.465523
0 - Front Left
1 - Front Right
Time per period = 5.464197

I hear no sound though…

Lets assume none of that works, and further lets wildly speculate that the alsa sound driver needs configuring upon booting (but I see no evidence from the dmesg in the diagnostic script output that you provided that that is the case - I am just adding this for completeness). In that case I would look to see if there are any model options that can be forced for your VIA VT1708s. To do that we look at the documentation that is on your PC, in the location /usr/src/your-kernel/Documentation/sound/alsa/ in the file HD-Audio-Models.txt file that you must know about since it is noted in this thread and you elected to post your problem on this same thread. In that file that is on your pc, you will note the section:
options snd-hda-intel model=auto
options snd slots=snd-hda-intel,snd-hda-intel

u1Nb.ZbI9NHBokA7:5 Series/3400 Series Chipset High Definition Audio

alias snd-card-0 snd-hda-intel

NXNs.TTZRWxxfTa1:nVidia Corporation

alias snd-card-1 snd-hda-intel


save the change, restart your PC and test the sound. 

This didn’t help…
Here is some more info that may or may not be helpful:
my pavucontrol settings
http://s18.postimage.org/ebrv4qbc9/off1.png
http://s14.postimage.org/6gqihegg1/off2.png
This is what I get when I click the Test button in KDE sound settings (next screenshot). The volume level bar is changing so that it seems that something is being played back, but I hear no sound…
http://s15.postimage.org/mootracp7/off3.png
http://s17.postimage.org/edxymcau7/off4.png

On a side note, I installed Fedora 16 yesterday just to see if my sound would work in there. And it does. No tweaking required - “it just works”. I know it’s mostly irrelevant, but there must be something fundamentally wrong with the way sound configuration works in the latest OpenSuse versions.

Glad to read that, … but from my view your posting on this solved thread just confuses me as I can not see the relationship between this thread and your problem. How much time must I spend studying someone else’s problem that appears to me to have no relationship to yours ?

Please next time start a new thread. Daily I search for ‘sound’ and ‘mic’ and ‘audio’ and look for sound issues, so if you are trying to get the attention for a sound problem, tagging on to a different users problem, where that user has different hardware, is not the best way to do this.

Sorry about the confusion. The topic appeared to be very related to my problem and it isn’t marked as [Solved] so I thought I’d just post here. Next time I will start a new thread.

OK, it was worth trying.

Still, rather than dismiss that as not working, can you help me a bit understand why it did not work. i.e how about after rebooting with that edit in place, try running the diagnostic script (alsa-info.sh) and post the URL so that non-functional configuration could be examined.

Why is GF104 High Definition Audio Controller set to OFF ? What other options are there under Internal audio.

Which of the aplay and speaker-test options that I provided did you try ? Did you try in a terminal as a regular user, and also with root permissions in a terminal ?

Its not irrelevant. It is important information. The sound driver typically comes with the kernel. So, what kernel version does Fedora 16 have? I don’t run Fedora 16, but you just did. So you know the kernel version.

Thanks, in future it will stop me wasting time sifting back and forth through a solved thread, scratching my head as to the relevance I had thought you had in mind.

What to try now ?

I recommend now that you update alsa. Please follow the guide here that I wrote: SDB:Alsa-update - openSUSE … apologies for any difficulty you may have in following that guide. It is intended for many openSUSE versions. Please be careful when updating alsa. Do NOT install more than one kmp package (install the correct one) and ensure you update the alsa apps (as > 50% users fail to update alsa as they ignore the guide and update their own way which does not work for them).

Thanks and good luck.

After banging my head against the wall (figuratively), I discovered that I probably had the sound all this time… I just don’t have it in the front headphone jack on my computer which is where I actually want it to be. But when connected to the back, it works… Oh, well.
Now I’m trying SDB:Intel-HDA sound problems - openSUSE it’s not working yet, so I might come back here.

No, it’s not working. alsamixer shows 0 volume level for the headphones and I can’t change it - I tried. Here is my 50-sound… file:

options snd-hda-intel position_fix=1
options snd slots=snd-hda-intel

u1Nb.ZbI9NHBokA7:5 Series/3400 Series Chipset High Definition Audio

alias snd-card-0 snd-hda-intel

Indeed, having cables appropriately plugged in is important.

Is this a home made PC ? If so, is the front headphone jack actually wired ? I assume it is wired, as I believe you note this front headphone jack works in Fedora. What kernel version was that version of Fedora ?

Do you find that modified file, with the line deleted, and ‘position_fix=1’ improves things ? Do you get better mixer settings with that ? If not, I recommend you go back to the old:


options snd slots=snd-hda-intel,snd-hda-intel
# u1Nb.ZbI9NHBokA7:5 Series/3400 Series Chipset High Definition Audio
alias snd-card-0 snd-hda-intel
# NXNs.TTZRWxxfTa1:nVidia Corporation
alias snd-card-1 snd-hda-intel

… ie if not essential, lets not add unneeded complications/changes.

Also, now that you know the issue is the front head phone jack, maybe again try:


options snd-hda-intel model=auto
options snd slots=snd-hda-intel,snd-hda-intel
# u1Nb.ZbI9NHBokA7:5 Series/3400 Series Chipset High Definition Audio
alias snd-card-0 snd-hda-intel
# NXNs.TTZRWxxfTa1:nVidia Corporation
alias snd-card-1 snd-hda-intel

restart, and and see if it adds a control to the mixer for the front headphone jack.

My understanding is that you have not yet updated alsa ?

Hi oldcpu. I’m pretty new to using Linux and I’ve tried everything I am able to with the limited knowledge I have.
I have tried disabling pulse audio, but my sound didn’t come on. When I play a file, the system definitely picks up the sound, but I don’t hear anything.
I tried to add the lines you said to the 50-sound.conf file but it won’t allow me to save due to it being read only.
http://www.alsa-project.org/db/?f=4a7727cbd33a7647481275be275e60275b04322f
Hopefully this will be of some use. I really want to get my sound working as I am really liking openSuse so far, makes a nice change to clunky Windows.
Thanks in advance.