SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have just upgraded to Suse 10.2. The new system works fine with the exception of sound.
I have no sound at all. KMix appears with a red cross through it and opening it shows no mixer controls and a drop down menu with nothing on it. Launching Amarok produces an error message along the lines of "Xine was unable to initiate any audio drivers" Other programs which use sound advise that no sound is available.
However if I log in as root then everything works as it should which suggests to me that my normal User does not have the right permissions to access the audio files drivers etc and that this is why nothing works.
The sound system was working previously under Suse 10.1.
Is this likely to be the case and how can I resolve the problem
The problem was that the user wasn't part of the audio group and got rid of the 00 in alsamixer, having corrected that I now have sound although for some reason only out of the two front speakers not the rear center or side speakers, any suggestions of how to solve that would be appreciated
My audio card is a Creative Soundblaster Audigy SE
I had the same problem (no sound for users) and appreciate the solution PaleViper. I would never have suspected that the normal users would have been denied audio in a normal installation.
For those who are not familiar working their way around SUSE, to do this in YaST, select: Security and Users --> User Management. Select the user and click Edit. Click on the Details tab. Click on the Audio group. Click Accept and then Finish.
I have successfully installed 10.2 onto my laptop and everything works fine except that although the sound card is found and identified as (sis962) AC'97, yast is unable to configure it. It says the kernel module could not be loaded.
I have tried using alsaconf, which locates the card and appears to be successful, but in fact it is not.
I have same problem. No sound. There was no sound in 10.0 either. My user account wasn't in the audio -group. But it is. No sound. YaST gives this kind of information:
82801G (ICH7 Family) High Definition Audio Controller
Configured as sound card number 0
Driver snd-hda-intel
Machine thinks that sound is coming, but I don't hear anything. This is little bit annoying.
I have same problem. No sound. There was no sound in 10.0 either. My user account wasn't in the audio -group. But it is. No sound. YaST gives this kind of information:
82801G (ICH7 Family) High Definition Audio Controller
Configured as sound card number 0
Driver snd-hda-intel
Machine thinks that sound is coming, but I don't hear anything. This is little bit annoying.
Search the forum for "82801G" (if you haven't already), since there may be something unexpected regarding setting up or detecting that hardware. Also try logging in as root and see if things change. Another more drastic measure would be to delete the sound card profile from the machine, reboot, and see if it does a better job detecting and installing it this time. (I think I had that work once on SUSE 10.0. I do not know to this day what the real problem was, since I never had a problem like that on another machine.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.