hey,
after todays security update, i rebooted the system as requested and the sound has disappeared.
the volume icon has gone from the system tray and when i try to enter the volume controls through yast i get this message:
YaST got signal 11 at YCP file Wizard.ycp:743
/sbin/yast2: line 437: 5008 Segmentation fault $ybindir/y2base $module “$@” “$SELECTED_GUI” $Y2_GEOMETRY $Y2UI_ARGS
It’s complete nonsense to me so i’m hoping someone knows what it means and what has happened.
thanks.
I note there was a 2.6.27.29 kernel released, … that could have broken your sound.
What is the output of typing:
uname -a
Is it the 2.6.27.29 kernel?
If you have updated to the 2.6.27.29 kernel, you could try sending six zypper commands (not 3, … 6 !! ) per this guide:
Alsa-update - openSUSE
I just checked and I see rpms for the 2.6.27.29 kernel.
Be certain to reboot after doing the update.
However the daily snapshot, when I looked a few minutes ago, was still for the 2.6.27.25 kernel … so do NOT apply the daily snapshots (just yet).
thanks for replying
so answer to first question:
derek@linux-5fdn:~> uname -a
Linux linux-5fdn 2.6.27.29-0.1-pae #1 SMP 2009-08-15 17:53:59 +0200 i686 i686 i386 GNU/Linux
will let you know in a sec if the zypper thing worked. just rebooting now.
so it appears i’ve had no luck.
i’m hoping i didn’t choose the wrong kernel version in the 2nd set of zypper commands.
i chose: kernel 2.6.27.29-0.1.1-pae i386 GNU/Linux (openSUSE-11.1)
as i’m running the 32-bit version, i figured this one was that considering the other had x86_64 which i assumed meant it was for the 64bit version.
i had a quick luck at the snapshots and it appears they have uploaded the latest versions for my kernel. however i’m a little reticent to do anything in case what i have done so far has been wrong.
Yes, I also noticed this morning when I got up that the alsa rpms for the daily snapshots were updated to the 2.6.27.29 kernel.
I think you could try either one of two approaches next:
In any event, to provide more information, what I typically ask is that you run an audio diagnostic script first as root (to update the script) and then as a regular user run the script again. The script does NOT fix anything. Rather it provides information.
To run the script, with your PC connected to the internet, type:
/usr/sbin/alsa-info.sh
run it the first time as root, and say YES to the update. Run it a second time as a regular user, and select to share your diagnostic information. That will post the information on an alsa specific paste site, and it will give you a URL. Please post the URL here. Just the URL.
Then also in a konsole/terminal, copy and paste the following (and provide the output):
rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
uname -a
cat /etc/modprobe.d/sound
Typically, once I have that information, I can make a better recommendation.
alsa url:
http://www.alsa-project.org/db/?f=56ccd0f95521359b963008c4c8e294530e556e92
derek@linux-5fdn:~> rpm -qa | grep alsa
alsa-oss-1.0.17-1.37
alsa-utils-1.0.18-6.4
alsa-driver-kmp-pae-1.0.20.20090821_2.6.27.29_0.1-1.1
alsa-plugins-pulse-1.0.18-6.12
alsa-plugins-1.0.18-6.12
alsa-docs-1.0.20-44.1
alsa-1.0.20-44.1
derek@linux-5fdn:~> rpm -qa | grep pulse
pulseaudio-utils-0.9.14-2.2.1
pulseaudio-module-lirc-0.9.14-2.2.1
libxine1-pulse-1.1.16.3-0.pm.3
pulseaudio-module-x11-0.9.14-2.2.1
alsa-plugins-pulse-1.0.18-6.12
libpulse-browse0-0.9.14-2.2.1
pulseaudio-esound-compat-0.9.14-2.2.1
libpulse-mainloop-glib0-0.9.14-2.2.1
pulseaudio-0.9.14-2.2.1
pulseaudio-module-gconf-0.9.14-2.2.1
pulseaudio-lang-0.9.14-2.2.1
pulseaudio-module-bluetooth-0.9.14-2.2.1
libpulse0-0.9.14-2.2.1
pulseaudio-module-zeroconf-0.9.14-2.2.1
vlc-aout-pulse-1.0.1-2.2
derek@linux-5fdn:~> rpm -q libasound2
libasound2-1.0.20-44.1
derek@linux-5fdn:~> uname -a
Linux linux-5fdn 2.6.27.29-0.1-pae #1 SMP 2009-08-15 17:53:59 +0200 i686 i686 i386 GNU/Linux
derek@linux-5fdn:~> cat /etc/modprobe.d/soundoptions snd slots=snd-hda-intel
u1Nb.avucAs_JlT2:82801H (ICH8 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
ok thats everything i think!
Yes, I note a stac9227 on a 32-bit openSUSE-11.1 with the 2.6.27.29 pae kernel.
I was looking at your mixer settings:
Simple mixer control ‘Speaker’,0
Capabilities: pvolume pswitch
Front Left: Playback 36 [56%] -21.00dB] [on]
Front Right: Playback 36 [56%] -21.00dB] [on]
Simple mixer control ‘Speaker’,1
Capabilities: pvolume pswitch
Front Left: Playback 64 [100%] [0.00dB] [off]
Front Right: Playback 64 [100%] [0.00dB] [off]
Simple mixer control ‘Speaker’,3
Capabilities: pvolume pswitch
Front Left: Playback 64 [100%] [0.00dB] [off]
Front Right: Playback 64 [100%] [0.00dB] **[off]**I can’t tell what sort of setup you have but I do note you have 2 speaker settings muted, which may not be relevant.
You could try updating now to the latest daily snapshot, now that it is here:
Alsa-update-snapshot - openSUSE
… again, note you MUST send six zypper commands. Reboot after the successful installation
If the alsa update does not work, we can try forcing a model option configuration into your openSUSE using one selection at a time from this list from the HD-Audio-Models.txt file for 1.0.20 of alsa:
STAC9227/9228/9229/927x
=======================
ref Reference board
ref-no-jd Reference board without HP/Mic jack detection
3stack D965 3stack
5stack D965 5stack + SPDIF
dell-3stack Dell Dimension E520
dell-bios Fixes with Dell BIOS setup
auto BIOS setup (default)
I can provide the syntax necessary for that if we suspect that is necessary.
ok. i installed the daily snapshot but i’m no further forward i’m afraid.
with reference to the mixer settings, i’m almost certain this is the issue. the problem being i cannot access the mixer either through the normal speaker icon or through the sound section of the yast. when i try to go through yast i get an error message and i’m still getting it.
YaST got signal 11 at YCP file Wizard.ycp:743
/sbin/yast2: line 437: 5008 Segmentation fault $ybindir/y2base $module “$@” “$SELECTED_GUI” $Y2_GEOMETRY $Y2UI_ARGS
i think for some reason this mixer interface is crashing, i don’t if any of that stuff you’ve asked me to install is an update of that mixer interface.
my speaker setup is just normal stereo computer speakers. there are couple of other outputs but it’s just basically your average off the shelf dell computer sound card.
i hope some that helps and isn’t just babbling.
What desktop? KDE-3.5.10 ? KDE-4.1.3 ? KDE-4.2.x ? KDE-4.3.x ? Gnome?
What mixer is crashing? kmix ? alsamixer? amixer?
gnome and in default mixer tracks for device it says “HDA Intel (alsa mixer)” so i reckon it’s alsa mixer. but i haven’t knowingly installed anything else, it’s the default for gnome.
If you type “alsamixer” in a terminal, do you get alsamixer?
You can also type “man amixer” and learn how to use “amixer”.
What happens if you restart the alsasound driver with:
**su -c ‘rcalsasound restart’**and enter root password when prompted for a password, and then test your audio? Can you also give me the output of:
rpm -qa | grep alsa
Did you try testing your audio with root permissions?
Did you try check to see if there is any sound in your headphones?
You could try forcing a model option. ie try each of those model options, one at a time.
Lets say you decide to start with “3stack”. You could do so by editing your /etc/modprobe.d/sound file such that it looks like (I added a line at the start of the file):
options snd-hda-intel model=3stack
options snd slots=snd-hda-intel
# u1Nb.avucAs_JlT2:82801H (ICH8 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
Note in gnome to edit that file you need to type:
gnomesu ‘gedit /etc/modprobe.d/sound’ and enter root password when asked for a password.
Once the edit is done, save, it, and then restart alsa sound driver with:
su -c 'rcalsasound restart’and enter root password when prompted for a password, then restart alsamixer (or amixer) and adjust your audio levels and test your sound.
If “3stack” does not work, replace it in the /etc/modprobe.d/sound file with the next item in the list (5stack) and save the change , restart alsa, restart mixer, and test the sound.
Do that every EVERY item in the list until sound works (or until you test them all).
i got alsa mixer going and unmuted those two muted channels. but it doesn’t seemed to have resolved my problems.
i know it sounds completed retarded and i’m exposing my complete noobness here but all i can think is that little speaker icon that is normally there in the system try thing on bottom right hand corner of my screen is gone.
like occasionally on my other comp, which i use for recording, i have to fiddle with sound card configurations, when i switch the primary sound card, i get a little message that says volume control has crashed unexpectedly (no those exact words) reload? so i do and it’s all fine.
But here, i’ve had no such message and the volume control icon is gone.
btw i really appreciate you helping me here. i realise this must be very frustrating having to try and help me, i wish i knew more and could be clearer with my problem.
Does that not come back when you run alsamixer? I do not know gnome, so I can not help much wrt that.
Please take a look at post#13 in this thread … I asked some questions, and provided some suggestions in that post.
results of that first command:
derek@linux-5fdn:~> rpm -qa | grep alsa
alsa-plugins-pulse-1.0.20.git20090805-1.4
alsa-driver-kmp-pae-1.0.20.20090821_2.6.27.29_0.1-1.1
alsa-oss-1.0.17.git20080715-2.5
alsa-tools-1.0.20.git20090702-2.5
alsa-docs-1.0.20-44.1
alsa-firmware-1.0.20.git20090507-3.1
alsa-plugins-1.0.20.git20090805-1.4
alsa-1.0.20.git20090811-1.1
alsa-utils-1.0.20.git20090818-1.1
That looks ok … when testing your sound, also try this test as both a regular user and as root:
aplay -vv somefile.wav
where “somefile.wav” is a wav file that you select that you know to be a good file.
I take it that “rcalsasound restart” did not restore your sound ?
this is a little bit confusing to me. i’m not sure how to start doing this. is there a guide somewhere i can go through step by step?
on a separate note, i’m getting no sound through headphones and i don’t know how to test the sound as root user.
sorry, forgot to say, that didn’t work for me. i had a bit of a system hang before and i decided to have a break and completely forgot to tell you the result of that one.