mhh, strange, now it doesnt work at all. No audio on any of the speakers
mhh, strange, now it doesnt work at all. No audio on any of the speakers
openSUSE:Submitting bug reports - openSUSE Write the bug report on openSUSE-11.4 component sound. Title something like "ALC888 misidentified as ALC887-VD and surround sound does not work". Use your openSUSE forum username and password when logging on to Bugzilla. Attach to the bug report the file '/tmp/alsa-info.txt' which you get from running:
No valid SSID suggests to me alsa can not determine the model option to apply. I also note in a Debian thread for the H55M-S2V hardware that you have a similar problem. Now in that Debian thread, instead of applying '3stack-6ch' model option they applied 'generic'. I have no idea as to where 'generic' comes from, as that is not even in the HD-Audio-Models.txt file which lists all the model options. I think your '3stack-6ch' effort makes more sense.Code:[ 5.913104] hda_codec: ALC887-VD: BIOS auto-probing. [ 5.913111] ALSA hda_codec.c:4633: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) [ 5.913113] ALSA hda_codec.c:4637: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 5.913115] ALSA hda_codec.c:4641: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [ 5.913117] ALSA hda_codec.c:4642: mono: mono_out=0x0 [ 5.913118] ALSA hda_codec.c:4646: inputs: [ 5.913119] ALSA hda_codec.c:4652: [ 5.914724] ALSA patch_realtek.c:1579: realtek: No valid SSID, checking pincfg 0x4005c603 for NID 0x1d [ 5.914726] ALSA patch_realtek.c:1595: realtek: Enabling init ASM_ID=0xc603 CODEC_ID=10ec0887
I provided a list above (in post#17 of this thread) of all the possible model options for your hardware. My recommendation is to keep trying each, one at a time, restarting your alsa sound driver between each attempt, until you find one that works best for surround sound.
tried all the possible values. No success
i submitted the bug report (Bug 706280 Submitted).
I will now attempt to do the same i did with my customer's PC (see posts 1 & 2) to see if i can fix it like i did then.
Will report back
After much tweaking, reading and even more head scratching, i finally solved the problem.
the only solution i found, was to do exactly what i wrote in post 2 in this thread!
After installing the driver as mentioned in that post (and having pulseaudio enabled), i tested the system, and the following issues occured...
1.- pavucontrol does have the proper sliders for all channels now, and 5.1 audio is selected by default, however, the subwoofer slider does absolutely nothing. And i get no audio out of my subwoofer.
2.- Opened Banshee (witch dint output any sound on my subwoofer, other channels were fine), and also opened pavucontrol, and every time i tried to move one of the output sliders in pavucontrol (any of them), banshee crashed, it just exited without any error.
3.- Opened the default volume control on the notification area, and tried to adjust the sliders there, but they are completely useless and incorrect. for example, moving the "subwoofer" slider up or down, caused ALL audio volume (all channels) to change, the other sliders moved themeselves as "by magic". The only audio level that dint changed, was the subwoofer itself.
Also, the sliders for "front-rear" balance, do not work.
4.- Overall sound was "weird", like slightly muffled.
So i did exactly what i did to my customer's PC. Went to yast->audio, and used the "Others"->Pulse audio configuration dialog to DISABLE pulseaudio.
After i rebooted, the volume control in my notification area was gone, I tried to open alsamixer via terminal (as standard user), and got:
However when i opened as root it worked.ALSA lib pulse.c:229pulse_connect) PulseAudio: Unable to connect: Conection refused
so the only way i have to control the volume for all channels (system wide) si to use both the "Volume..." option in yast->sound, or open alsamixer as root.
But at least now, all channel sliders and controls (including subwoofer) work perfectly both in yast->sound->volume, and alsamixer.
The "strange, muffled sound" issue is also gone, sound is perfect (after i disabled pulseaudio!)
Tested the audio with banshee (normal, stereo mp3 files) and it worked perfectly, got audio in all channels.
Also used totem to play a 5.1 audio test video i have, and it too worked perfectly.
So my final conclusions are, to make this card work properly i have to...
1.- to compile and install the driver from the realtek site.
2.- Disable pulse audio
3.- use either alsamixer or yast->sound->volume dialog to adjust systemwide volume for all channels.
4.- use the volume control on your applications (or the phisical one on the speakers) to quickly adjust the volume.
I wonder if this whole bad audio issue is caused by 2 bugs and not just one.
on one side we have the fact that i have to install the stuff from the realtek page, and on the other, even after doing that, pulse audio does not work. i have to disable it.
So maybe theres the bug about the driver, and the pulseaudio not working even after installing the driver is another issue?
In any case, im submitting a mini "how to" for evaluation in the howto section, so that untill these issues are fixed, others wont have to spend so much time working arround them.
Its unfortunate that you encountered a bug here.
The openSUSE packager for sound is also an alsa sound developer. Assuming he is not on vacation (or busy with openSUSE 11.4 packaging) he is normally very good at addressing bug reports and coming up with fixes. Typically such fixes are an iterative process, and he will update alsa and ask the users to update their openSUSE with his updates to test if they work. I wrote a guide how to apply his updates here: SDB:Alsa-update - openSUSE
In fact there are already some update present now you could have applied, but to see if the bug fix for your ALC888 is available, but you have gone and adopted another approach, so I don't think we will find out. ... I posted a LOT of information above, and recommending to try that alsa update would have been my next step.
Anyway, glad to read you found a method that works.
One caution - my experience is 90% of the time users who compile the driver from the RealTek site totally fail in their effort, and they often end up re-installing to clean up the mess they created. I note you succeeded and thats great, but updating from Realtek is not a solution I would recommend myself. The next kernel update could break the sound, and once again one has to recompile, etc ... IMHO its far better to work with the openSUSE packager for sound, for at least that way one has an rpm and repository one can use for their updates.
Thanks again for all your advice & help
I must admit i am not too pleased with the solution i found, i know that when the kernel gets updated, ill have to compile and install the driver again (and pray it still works). But at the time it was the only effective solution i could find.
Now that i have installed this driver, is it "too late" to take the approach you mention on that link (update alsa)?
And, (i haven’t read all that page yet, just took a quick look) is that alsa version a stable one or is it beta / testing?
Do you know if there is a "normal" alsa update for 11.4 coming soon? i mean an update that you do by "zypper update" without aditional steps.
Typically there are two parts to it, ... one part updates the actual driver (kernel modules) which is the alsa-driver-kmp-<some-kernel-version> which replaces the modules that come with the kernel. A new kernel update will break this, and one needs to install the new rpm (which the openSUSE packager for sound always creates anywhere from a day to a week after a kernel update).
The second part is the update to all the rpms that typically come with the alsa driver (in the kernel) such as libasound2, alsa, alsa-oss, alsa-utils, alsa-plugins, etc ...
I've read of cases where users who had a realtek driver install then install both the alsa-driver-kmp-<somekernel-version> with the extra alsa apps and claim it replaced the realtek, and I've read of cases where they claim it did not replace the realtek. I don't know the truth here, as I have never installed the realtek myself. Its difficult to know the real story unless one does such an install ones self with a reasonable level of (non-trivial) knowledge. My 'guess' is an install of the rpms should replace the realtek but in all due honesty I do not know for certain.
My guess is if he thinks he has a fix to the ALC888 he will update first his repository, and ask you to test the update (by installing alsa-driver-kmp-<somekernel> ' and maybe some of the libasound2, alsa, alsa-utils, alsa-plugins, ... etc cutting edge versions). If they work he may then depending on the severity of the bug push it for openSUSE-11.4 as a nominal update. If he feels it not so important he will wait until openSUSE-12.1.
Typically he is very good at pushing immediate fixes. ... In many respects on openSUSE we are fortunate that one of the SuSE-GmbH packagers is an alsa driver developer. Not all GNU/Linux distributions are that fortunate.
You know, i just realized something...
I tought that the driver i downloaded from the realtek site, was some sort of "propietary" driver made by realtek for their chipsets. But just now, i took a closer look at the readme file in the tar (im pasting it here)...
If i understand correctly, isnt this just an updated version of the general alsa modules? i mean, i dont think its a propietary driver made by realtek for their chips, but it seems to me like its just a standard, recent module pack from the alsa site. am i correct? and if so, wouldnt applying this driver pack be more or less the same as installing alsa-driver-kmp-<somekernel>?The source code copy from Main Page - AlsaProject. ver:5.15
Linux Source Code for ALC audio codec
Support Codec list:
====HD Audio codec ====
This Source Code is from Main Page - AlsaProject.
For OS installation, please remember add the Development tool kit.
For driver installation, please follow below steps.
Note: Please check Development tool kit on your OS.
Step 1. unzip source code
tar xfvj alsa-driver-1.0.xx.tar.bz2
Step 2. Complied source code
a. cd alsa-driver-1.0.xx
b. ./configure --with-cards=hda-intel
d. make install
Step 3. reboot your machine
Step 4. Use the alsamixer the disable mute (All audio line default is mute)
Must to compile and to install the ALSA library and utility. (Use automatic install is already install)
Note: 1. The most detail information, can refer the alsa-kernel/Documenttation/ALSA-Configuration.txt in the azx-021705.tar.bz2.
2. Kernel Version must be 2.6 or later.
3. All mixer channels are muted by default. You must use a native
or OSS mixer program to unmute appropriate channels.
4. If can not compile the source code, try to rename the /usr/src/linux-2.x -> /usr/src/linux.
5. The driver added to support the SPDIF functoin.
6. a. You can download the alsa-lib-1.0.x and alsa-utils-1.0.x form the Main Page - AlsaProject, then unzip and install them.
b. Suggest use "alsamixer" to control mixer function.
c. Used "alsaconf" can autodetect which drive you need to install (step 4).
7. SUSE Distribution must install the ncurses package.
I cant belive i read this readme file before, and dint actually "noticed" this.
I forgot to mention, im editing the bug report i submitted earlier, to mention this solution, maybe it will help the devs fix the issue.