I thought I’d contribute a separate post regarding sound trouble on M7 (in addition to someone elses on M6)
I haven’t run the diagnostic script from the troubleshooting sight yet, but I did notice the following. Any suggestions, or do I need to run the script to provide further details?
dmesg |grep ALSA
51.098194] ALSA /usr/src/packages/BUILD/kernel-desktop-2.6.31/linux-2.6.30/sound/pci/hda/hda_intel.c:1186: Too big adjustment 32
51.111798] ALSA /usr/src/packages/BUILD/kernel-desktop-2.6.31/linux-2.6.30/sound/pci/hda/hda_intel.c:1186: Too big adjustment 32
51.205383] ALSA /usr/src/packages/BUILD/kernel-desktop-2.6.31/linux-2.6.30/sound/pci/hda/hda_intel.c:1186: Too big adjustment 32
when I check to see whats there, the BUILD directory is empty
I notice that both kernels 2.6.31 and 2.6.30 are mentioned above. Is this just a case of a bad update from M6 to M7?
Thanks. Exactly what was your sound trouble? Low sound? No sound?
I took a look at the script. I note openSUSE-11.2 milestone7 with the 2.6.31-rc9-7-desktop kernel and an ALC660-VD hardware audio codec in an Asus A7K with a mix of alsa-1.0.20/1.0.21.
Your PCs mixer settings for “Master” strike me as somewhat strange:
!!------------- !!-------Mixer controls for card 0 [SB]
Card hw:0 ‘SB’/‘HDA ATI SB at 0xfebf4000 irq 16’
Mixer name : ‘Realtek ALC660-VD’ Simple mixer control ‘Master’,0
Mono: Playback 5 [8%] -59.00dB] [on] Simple mixer control ‘PCM’,0
Front Left: Playback 252 [99%] [0.60dB]
Front Right: Playback 252 [99%] [0.60dB] Simple mixer control ‘Front’,0
Front Left: Playback 64 [100%] [0.00dB] [on]
Front Right: Playback 64 [100%] [0.00dB] [on]
Try moving that setting up from 8% to 95%. Typically one uses kmix in kde or alsamixer in gnome for such adjustments.
no sound. When I log in I get a pop up in KDE 4 telling me there is no analogue sound, so its defaulting to pulse audio.
I’ve opened KDE4s mixing controls and everything there is full. Haven’t tried headphones yet (which I should have I already).
This is a laptop for which it was found (in 11.1) under 1.0.19 that HDa verb was required with some special settings (as I recall you were in that thread somewhere). I was hoping that this would be fixed in 1.0.20.
Trying the headphones is essential. I was told by one of the alsa developers that getting sound to work in a headphone is much easier than getting it to work in speakers.
Now for some generic advice, and my apologies if this is too simple for you, but I have difficulty guessing the knowledge level of users (and some users get upset at me for over estimating their knowledge, or in other cases under estimating their knowledge - no matter how one cuts it, it is difficult to guess correctly).
Do NOT use the startup system sound as your criteria for stating sound does not work. Also be certain to check your mixer. Its not uncommon for a mixer setting (master, pcm or speaker) to be muted upon boot. In KDE your mixer is “kmix” (the small speaker in right hand corner). In Gnome your mixer is “alsamixer”.
Note, when testing if you have sound, please copy and paste the following speaker-test into a Gnome terminal or a kde konsole:
speaker-test -Dplug:front -c2 -l5 -twav
Note Linux is case sensitive, and “D” is not the same as “d”. To stop the above test, while the konsole/xterm has the mouse focus, press <CTRL><C> on the keyboard. Note you should check your mixer settings (kmix if using KDE, and alsamixer if using Gnome) to ensure that PCM and Master Volume are set around 95%. Once you have basic sound established you can back off to lower volume levels. Note the test for surround sound is different.
If that test yields errors (and its not uncommon to get errors there), try instead this more simple test: speaker-test -c2 -l5 -twavYou should hear a female voice saying ‘FRONT LEFT’, ‘FRONT RIGHT’ five times. Its quite common that one of those speaker tests will work and one will NOT work, so don’t be distressed if that is the case. IF that test gives sound, stop now, post that the sound test gives sound, and we will look at other possible causes for your applications not giving you the sound you want (such as missing codecs, using the wrong packaged version … etc … ).
Or alternatively, for testing the simple playback, use aplay program. Prepare a WAV file and simply run like:
aplay -vv somefile.wav
With the option -vv, aplay shows the verbose information of the PCM device, and a VU-peak meter during playing the file.
Try those speaker-tests as both a regular user, and also with root permissions. If you have a headset, try with your headset plugged in, and also with your headset not plugged in (for speakers).
Assuming no sound, can you provide more very detailed information so a good recommendation can be given? For openSUSE-11.1, you can do that, with your laptop connected to the internet, by opening a gnome-terminal or a kde konsole and twice copy and paste the following into that terminal/konsole
Run it the 1st time with root permissions. It will ask if you wish to do an update of the script. Select YES.
Then run it again (as either a regular user or as root). This time it will diagnose your PC’s hardware and software configuration for audio, and it will post its output on the Internet/web. It will give you the URL of the web site. Please post that URL here. JUST the URL.
Also, please copy and paste the following commands one line at a time into a gnome-terminal or a konsole and post here the output: rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
cat /etc/modprobe.d/sound… with that information I may be able to make a recommendation.
Also, do NOT waste too much time on this. Simply post on our forum if you get stumped, and continue to look for help that way.
Hi old cpu
I can confirm that no sound happens for headphone use either. I did confirm kmixer settings. all tests were run as root and user with and without headphones. No sound resulted. the below was done as root with and without headphones
speaker-test -c2 -l5 -twav
Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
ALSA lib conf.c:4626:(snd_config_expand) Expand error (walk): File exists
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.488574
0 - Front Left
1 - Front Right
I don’t have 11.1 working anylonger (overwrote it with the M7 version). I did the script update, but didn’t get what I wanted:
-rwxr-xr-x 1 root root 0 Sep 22 22:45 /usr/sbin/alsa-info.sh
so nothing got uploaded to the network
Somewhat surprised at the alsa 1.0.20 and 21 mix. Did 1.0.21 come in M7? Otherwise not sure how I got it there…vlcplayer?
I really need the script output posted to a web site, such as a paste bin site. So can you run the script with the no-upload option, and post its output to a pastebin site such as pastebin - Type, paste, share. ?
You can run the script to have its output saved to /tmp/alsa-info.txt by typing:
Where do I find an updated script? I wasn’t clear in my last posting as to what had happened.
When I ran the script and accepted the option to dowload an updated script, it downloaded a script of size 0 bytes. I can’t update running the script in /usr/sbin anymore as the script is a zero sized file as i listed below
Is the output from the script I ran awhile ago not sufficient or different from what you were needing
Can you post here the output of:
Once we have that, I will be able to recommend some edits to that file that you can try, using this list forthe ALC660VD:
3stack-dig 3-jack with SPDIF OUT
6stack-dig 6-jack with SPDIF OUT
3stack-660 3-jack (for ALC660VD)
3stack-660-digout 3-jack with SPDIF OUT (for ALC660VD)
lenovo Lenovo 3000 C200
dallas Dallas laptops
hp HP TX1000
asus-v1s ASUS V1Sn
auto auto-config reading BIOS (default)
Lets try a model option. For example, from the list in an above post, lets try 3stack-660.
To test that, add a line to the start of your /etc/modprobe.d/50-sound.conf file such that it reads:
options snd-hda-intel model=3stack-660
options snd slots=snd-hda-intel,snd-hda-intel
# 5Dex.IOFetRyhSn6:SBx00 Azalia (Intel HDA)
alias snd-card-0 snd-hda-intel
# NXNs.JPS6WT8bfU4:RV630/M76 audio device [Radeon HD 2600 Series]
alias snd-card-1 snd-hda-intel
then restart your alsa sound driver with su -c ‘rcalsasound restart’ and enter root password when prompted and then restart your mixer and test your sound.
If 3stack-660 does not work, then replace it in the /etc/modprobe.d/50-sound.conf file with another item from the list ( say for example asus-v1s ), restart alsa as above, restart, your mixer, and test your sound. Do this for each item in the list, stopping if sound works. Don’t forget to use sound test noted above in previous post, and test with speaker and headphones, and as a regular user (and in terminal as root if regular user does not work).
OK, note that Takashi Iwai is looking for info from a user with the associated hardware in that thread … (he wants a user with that sound device to run the “/usr/sbin/alsa-info.sh --no-upload” script and then go to /tmp/alsa-info.txt file and upload that text file to the bug report).