I dont have a sound in my suse 11.3 here is the link about the sound information
http://www.alsa-project.org/db/?f=0c4335d13895ff182b787b49cec39e12d717e22f
note = in ubuntu 64 the sound works
I found the following fix as it seemed to match your problem:
I got a new computer at work, installed Ubuntu 10.10 Maverick Meerkat and the sound didn’t work. The fix was actually quite simple so I thought I’d share it with you in case you have a similar issue.
The computer has an HDA Intel chip (Realtek ALC887) and I couldn’t open alsamixer (this error was displayed: “load hw:0 error: Invalid argument”), although the sound seemed to be working in various applications (no error there) except I couldn’t hear anything.
The fix (I modified this to work in openSUSE in KDE):
Edit /etc/modprobe.d/alsa-base.conf:
kdesu kwrite /etc/modprobe.d/50-sound.conf
And add the following line:
options snd-hda-intel model=generic
Restart your PC and let us know if this makes any difference. I also have a script file called START that might also be helpful with audio problems:
S.T.A.R.T. - SuSE Terminal Audio Reporting Tool
Thank You,
It will be interesting if this works. I checked the HD-Audio-Models.txt file for alsa for 1.0.23 and version 1.0.24 and ‘generic’ is NOT a model option. So if this works it is either an undocumented feature of alsa, or its a case of Ubuntu applying a fix and not sending the documentation upstream. If it does not work in openSUSE but it does work in Ubuntu its a case of Ubuntu not sending the fix upstream so the remainder of Linux can benefit.
I note your PC is a Gigabyte GA-MA78LMT-S2 with 64-bit openSUSE-11.3 and the 2.6.34.7-0.7-desktop with 1.0.22.1/1.0.23 alsa version. The hardware audio codec is identified as a Realtek ALC887. Unfortunately documentation for the ALC887 is slim (not in the HD-Audio-Models.txt file).
I note this error via your mixer:
!!Amixer output
!!-------------
!!-------Mixer controls for card 0 [SB]
amixer: Mixer load hw:0 error: Invalid argument
Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
Mixer name : 'Realtek ALC887'
Components : 'HDA:10ec0887,1458a002,00100302'
Controls : 40
amixer: Mixer hw:0 load error: Invalid argument
and to make an assessment on that I would need more information … ie what is output of:
rpm -q '*alsa*'
rpm -q libasound2
Its possible if you have all the necessary alsa apps installed (alsa, alsa-plugins-32bit, alsa-plugins, alsa-oss, alsa-oss-32bit, alsa-utils, libasound2) that you may also need alsa-firmware. But if adding alsa-firmware does not work, then it is possible that the Ubuntu fix has made it upstream but it is not documented, and possible the alsa-developers have the fix in their latest alsa version.
In which case, we are fortunate on openSUSE that the SuSE-GmbH sound packager is also an alsa developer, and IF the fix was sent upstream by Ubuntu, then one can update alsa to the SuSE-GmbH sound packagers’ cutting edge alsa rpms and the fix may be there.
There is guidance here for how to do that: SDB:Alsa-update - openSUSE (my apologies - that page is out of date and I need to update it - but for now follow the philosophy and install the updates to alsa, alsa-plugins-32bit, alsa-plugins, alsa-oss, alsa-oss-32bit, alsa-utils, libasound2 (and alsa-firmware as appropriate) and also install alsa-driver-kmp-desktop specific to your kernel version. Note a reboot is needed after that update, and you need to be VERY CAREFUL to ensure you updated alsa, alsa-plugins-32bit, alsa-plugins, alsa-oss, alsa-oss-32bit, alsa-utils, libasound2, because many users simply do not understand YaST and they think they did an update when they did not so so. So be very very very very very detailed and careful here.
Whether you get this working or not, a bug report should be raised as this should ‘just work’. So please write a bug report on openSUSE-11.3 component “sound” with guidance here: openSUSE:Submitting bug reports - openSUSE and you can use your openSUSE forum user name and password when logging on to Bugzilla. Please ensure the bug report has all salient information as the SuSE-GmbH packager will NOT read this forum thread. Also please attach to your bug report the latest version from the diagnostic script, and you can create that diagnostic output file by typing:
/usr/sbin/alsa-info.sh --no-upload
and it will be in /tmp/alsa-info.txt.
Thank you for raising the bug report. It is disappointing that the largest distribution (Ubuntu) either fails, or is very late, to pass such fixes upstream, and so the best we can do in openSUSE is to keep trying, and sending fixes upstream quickly so that all Linux versions benefit from our efforts.
A further note to this thread, … I’ve had users a few times remark they have no idea as to where I get the references to HD-Audio-Models.txt nor alsa-configuration.txt files from.
These files SHOULD be on a users’ PC, and are typically associated with the kernel documentation. For example, on the 2.6.34.7-0.7 kernel, one can find the documentation here:
/usr/src/linux-2.6.34.7-0.7/Documentation/sound/alsa
with files in the documentation:
ALSA-Configuration.txt Bt87x.txt emu10k1-jack.txt HD-Audio.txt MIXART.txt Procfile.txt seq_oss.html VIA82xx-mixer.txt
Audigy-mixer.txt CMIPCI.txt hda_codec.txt hdspm.txt OSS-Emulation.txt README.maya44 serial-u16550.txt
Audiophile-Usb.txt ControlNames.txt HD-Audio-Models.txt Joystick.txt powersave.txt SB-Live-mixer.txt
Thanks for all you replay … I been trying everything i could … searching all over the internet … Linux forums etc and it seem a lot of people is having the same problem either 32/64 bits … I just move the the hard-drive to my old computer amd x3 and the sound is working fine.
for now i will use Ubuntu in this new computer i will try to figure out how to send this bug and see if somebody can fix it thanks a lot
Jc
I spent a lot of time typing my response. Did you try any of it before your decision to go to Ubuntu ?
Just wanted to know so I can better judge where to spend my time next time.
Good luck in your efforts on Ubuntu and thankyou for offering to write the bug report. Its not difficult, and as I noted there is guidance here: openSUSE:Submitting bug reports - openSUSE
spent a lot of time typing my response. Did you try any of it before your decision to go to Ubuntu ?
Just wanted to know so I can better judge where to spend my time next time.
t
Sorry not to answer your post … .yes i did everything you ask me to do. for you information I’m still using suse In my post before i say
or now i will use Ubuntu in this new computer
I have not quit suse … i just quit researching for now how to fix the sound on suse … i still have suse in another partition but i just wan to have soundbeside that thank a lot and believe me you are not wasting your time typing and trying to help to the community … i will post any progress ( if i have one ) about the sound in this new computer .
thanks
jc
OK, then that means you attempted to update alsa like I recommended.
Please, so that I can do a quality check to ensure it was done appropriately, can you provide output of:
rpm -qa '*alsa*
rpm -q libasound2
and again run the diagnostic script:
/usr/sbin/alsa-info.sh
and post here the URL/web-address that it provides when you select the share/upload option in that script
I’ve seen MANY cases where users failed in properly updating alsa, and I want to ensure that is not the case here.
Thanks for all you help after Updated to 11.4 the sound is working now by the way this suse 11.4 seem to be faster!
Thanks for all you help after Updated to 11.4 the sound is working now by the way this suse 11.4 seem to be faster!
Well that is one way to fix the problem. Did you do an in place upgrade or a clean install? Do you know if Pulseaudio is running. It would be by default in a clean install. Not sure what you get doing an upgrade. I did a clean install, but maintained my /home area separate. If I run the following command, we can see that PA is running the show:
Command: lsof /dev/dsp* /dev/audio* /dev/mixer* /dev/snd/*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 2350 james 26u CHR 116,9 0t0 5225 /dev/snd/controlC0
pulseaudi 2350 james 32u CHR 116,9 0t0 5225 /dev/snd/controlC0
You can run the same command in a terminal session (don’t include the word Command: ) and see what you get.
Thank You,
I just did update the system , I did not clean install
OpenSUSE-11.4 comes with an alsa-1.0.23/1.0.24 mix, as opposed to openSUSE-11.3 which had an alsa-1.0.21/1.0.22 mix. My suspicion is when you attempted to update alsa with openSUSE-11.3, something went wrong (which is why I asked for the output fo those "rpm -qa 'alsa " and “rpm -q libasound2” commands and the output of the diagnostic script. That would have enabled me to see if the alsa update did not go correctly).
When you update to 11.4, those alsa files are automatically updated correctly by the openSUSE installer.
But no matter. 11.4 is working now for you.
I also find 11.4 marginally faster than 11.3.