I’ve just installed 11.2 on my Fujitsu Siemens Amilo Pi 1505 and sound recording does not work. That means skype & sound recorder do not capture any sound. If I adjust the “Mic” control in KMix, then I can hear my own voice in the speaker, but there isn’t any “Capture” control at all.
Previously I’ve used 11.1 and it worked perfectly. The capture control in KMix (Alsamixer, etc) was present.
The laptop has a hda-intel ALC861 sound card and I use it with exactly the same settings on 11.2 as on 11.1 (sound.conf options: model=3stack)
Note, you can add extra mixer controls (channels) in KDE’s kmix via kmix’s menus.
Please provide more information so we can assess this. With your mixer set up EXACTLY how you think it should be setup for the recording to work, please in a terminal, with your PC connected to the Internet run the following diagnostic script (it won’t fix/change anything - its a diagnostic): /usr/sbin/alsa-info.sh
select to UPLOAD/SHARE and when it is complete, it will give you a URL. Please post here the URL. Just the URL.
Please also post here the output of running in a terminal: rpm -qa ‘alsa’
rpm -qa ‘pulse’
rpm -q libasound2
uname -a
cat /etc/modprobe.d/50-sound.conf
Note 11.2 will ignore an /etc/modprobe.d/sound file, and instead it uses an /etc/modprobe.d/50-sound.conf file.
As you can see I use 64 bit SUSE.
I’ve tried all possible 'model’s in 50-sound.conf described in ALSA-models.txt file. In some cases I had ‘Capture’ control, but in that cases sound didn’t work at all. I’ve tried other options as well (position_fix=1, power_safe=10, etc) proposed in different ALSA bug reports, but Capture didn’t appear.
As I mentioned 11.1 (resp. Ubuntu Jaunty) worked on this laptop properly.
BTW:
I think yast has a bug in the sound configuration module. If I change the configuraton (e.g. differnet module) it saves the previous version of the 50-sound.conf into the /etc/modprobe.d directory as well (50-sound.conf.YaST2save). As far as I know all of the files in this directory are read by modprobe, and therefore the backup file mess up the configuration of the sound module.
Thankyou for that. That confirms a FUJITSU SIEMENS AMILO Pi 1505 running a 64-bit openSUSE-11.2 with the 2.6.31.5-0.1-desktop kernel, and 1.0.20/21 of alsa, with an ALC861 hardware audio codec.
**Is this an INTERNAL or EXTERNAL mic you are trying to use? **It makes a difference in what mixer settings we need to consider !!
I note there IS a digital capture in your mixer. Is this a digital internal mic?
Your /etc/cat/modprobe.d/50-sound.conf looks really messed up. I recommend you do NOT put all those settings in, unless specifically advised to do so by an alsa developer. Just keep it simple instead.
I recommend you FIRST try with NO “options snd-hda-intel model=3stack” line, and reboot with that. ONLY if that does not give you the needed options, could you try to force things. The autoprobe on 11.2 is VERY good and you may just be making it far worse.
But if you wish to try with an option, then try this for “3stack”:
in the /etc/modprobe.d/50-sound.conf file:
options snd-hda-intel model=3stack
options snd slots=snd-hda-intel
u1Nb.4iaEZqA1QJD:82801G (ICH7 Family) High Definition Audio Controller
alias snd-card-0 snd-hda-intelThen save that, and restart your alsa sound driver with su -c ‘rcalsasound restart’ and enter root password when prompted, restart your mixer, and test your audio and mic.
Then if “3stack” does not work, try a different setting, … say “3stack-dig”. To do that replace “3stack” with “3stack-dig” in the file, and then save that, and restart your alsa sound driver with su -c ‘rcalsasound restart’ and enter root password when prompted, restart your mixer, and test your audio and mic.
Do that for each item in the list below, ONE at a time.
ALC861/660
==========
3stack 3-jack
3stack-dig 3-jack with SPDIF I/O
6stack-dig 6-jack with SPDIF I/O
3stack-660 3-jack (for ALC660)
uniwill-m31 Uniwill M31 laptop
toshiba Toshiba laptop support
asus Asus laptop support
asus-laptop ASUS F2/F3 laptops
auto auto-config reading BIOS (default)
hmmm … what were you using for a sound test? Did you check both Master and PCM and Speaker volume controls?
What are you using for a test of your mic? I recommend for testing you look at this: Microphone - openSUSE and specifically test with:
arecord -vv -fdat foo.wav
where foo.wav is an arbitrary name of the file to be created.
ONLY try these if alsa developer recommends.
that was the case for 11.1 but not for 11.2. The behaviour has been changed in 11.2. In 11.2 other files simply give an error message but are not loaded. Hence there is no bug in the 50-sound.conf.YaST2save creation.
If you have no luck, then write a bug report where there is guidance here: Submitting Bug Reports - openSUSE and select component “sound” in the report. Note that by writing a bug report (and selecting component “sound” ) on openSUSE, you get the immediate attention of the openSUSE packager for sound, who is also an alsa developer. Hence the suggestions/advice one gets is first rate from them. And if they produce a fix, the fix is typically sent up stream immediately so all distributions can benefit.
openSUSE-11.2 is very good for sound and its possibly one of the understated features of 11.2 in that sound mostly “just works”.
11.2 includes the 2.6.31 kernel that has 1.0.21 of alsa with the kernel, where 1.0.21 of alsa is VERY good for sound features
1.0.21 of alsa includes Xfi support
1.0.21 of alsa has significantly improved autoprobe of hardware
11.2 has a different implementation for the /etc/modprobe.d directory, where only files with the number-function.conf will be loaded and others will give an error. Hence the 50-sound.conf file for the sound config. This also means alsaconf, which creates an /etc/modprobe.d/sound file, is now depreciated for 11.2 and should not be used in 11.2.
11.2 has pulse disabled automatically upon install on my PCs thus far (although its still present) (this pulse enable/disable on install may be PC dependent ? I’m not sure).
the long and short of it is sound is mostly easier to get working in 11.2 as opposed to earlier openSUSE releases.
The Ubuntu releases with the 2.6.31 kernel should work ok. My “gripe” with Ubuntu is their slow implementation of sending Ubuntu fixes upstream. IMHO both Fedora and Novell do a far superior job of sharing their fixes with the remainder of the Linux community.
Well, unfortunately I have a problem with the default settings as well. Sound works only if something is plugged into the front output jack (only output jack on the laptop).
That means I can hear the sound if I plug my headset, but If I pull it out no sound is comming from the laptop’s speaker.
There is no “speaker” or similar control in the mixer.
I’ve tried with all possible “model” options (3stack, etc) as well. In the most cases laptop’s speaker works, but sound recording not.
That means I haven’t found a configuration were both (recording & laptop speaker) work.
If you are confident you followed the above recommendations as best possible, and that the model options you tried do not provide the capability that is correct, then IMHO you should write a bug report. There is guidance here for writing a bug report: Submitting Bug Reports - openSUSE
Please note that by writing a bug report, you get the immediate attention of the Novell/SuSE-GmbH packager who packages sound for openSUSE, and who is also an alsa driver developer. Hence if they manage to solve the problem, and if it involves an update to alsa, they are very good at passing the fixes upstream, and all Linux distributions will benefit from your bug report.
Be certain to raise the bug report against component “sound” in openSUSE-11.2.
