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 from 9.2 to 10 and while initailly there was no sound at all and kmix was not initiated e.g. blank I managed to get kmix up by running alsaconf. My sound drive is now SIS 7012 (alsa) and if I run a cdrom (music) its great. However any attempt to run either Amorak or Xine (DVD) produces no sound from these progammes at all.
I ran both Ismod and ispci to see what going on put everything appears OK. The sound hardware listing in YAST also shows SIS 7012 loaded. I am quite sure that under previous versions of Suse my sound card was configured as AC97. This is what is seen on my win98 partition. Below is a copy of the lsmod and lspci files.
If anyone can throw any light on this I would br grateful.
i had a problem like this to(konsole root etc/init.d/alsasound restart) when you boot try and restart the sound that solved my problem. What APU do u have?
I have not solved the problem but I have found out more info.
1. On initial boot the sound card is not indentified and accordingly there is no sound from anywhere.
2. With a bit of fiddling I can get YAST to see the card SIS 7012 (alsa) which gives me sound from the cdrom drive only.
3. I have xine setup to play dvd's but theri is no sound
4. Amarok will crash immediately I try to play a mp3 tune.
5. My hardware report shows two modules of which snd_intel8x0 is loaded as card 0
6. I can also activate module i810_audio but it has no affect.
7. The IRQ 10 and the I/O DC00 and D800 and Windows uses the same resources and the sound is perfect.
There is obviously an incompatibilty somewhere. Does anyone know of diagnostic tools that I may use to try to narrow down the problem?
I have two other minor problems and I am windering whether one of them may be related. Upon boot YAST configures my printer but it does not work.
Only if I add another configuration will it then see the printer. Of course the whole saga is repeated next time I boot. Any suggestions?
Finally as a user everytime I try to activate something a little window pops up (sometimes at least four of them) with the message
"Could not find mime type application/octel-stream". It does not stop the application loading. If I log in as root it does not happen.
Here I am again with the same problem. Incidentally judging by the number of posts with people having problems with Suse 10 Novell have not done themselves any favours.
I am enclosing a copy of part of my dmesg file which appears to highlight the problem with both the sound and the printer.
Can somebody interprete this for me and advice on how I might resolve it. ACPI appears to be having trouble activating both
the sound card and printer.
Incidentally, upon boot if I enter YAST it indentifies my sound card as exactly that "Sound Card" with no number e.g."0". If I try to edit or delete it it throws me out of YAST. If I try to add another card I get an error message.
I'm having problems with sound too. It seems that if I use SKype and then try to use another application that uses Audio it can't access the sound device. Very annoying, Novell should be ashamed of themselves.
Some applications that use sound lock others out while they're running. I'm not sure that's so bad. Since an application can monopolize sound, that means that it may have to release that control upon exit. Is Skype running in the background? Ctrl-Esc will bring up a process list you can check. Perhaps it and not SuSE are your problem.
Additional info after reading up on the problem. It seems there should be at least one dsp file in /dev after the sound card is initiated but I don't any any at all. What is annoying is that according to the OS my sound card SIS 7012 is loaded using snd_intel8x0 driver and yet
there is no sound except from the cdrom.
Your sound card works because the CD cables internally to a sound card input. The Linux default is to install with most sound ports muted. One would think that alsamixer or kmix would both show the problem and allow you to configure to turn off muting. Your error messages on the other would not result from muted inputs. With Linux, there's always an answer -- finding it can be the problem.
I checked and do have a /dev/dsp which is read write to owner (me) and group audio. Permissions are frequently the source of things that don't work. Are you a member of group audio?
A few days ago I had sound on everything and I throught I had cracked it although I didn't know what I had done. Anyway its gone again athough there is some improvement.
1. If I run alsaconf at the end it plays a test tune whch I can now hear.
2. Also with KDE sound enabled I hear all the beeps etc when you open windows etc.
3. If I access the Alsamixer and activate it kills all sound
4. Only the if the Kmixer is activated do I get the limited sound mentioned.
5. If I try to load other sound mixer-desks they abort stating there is no sound card.
6. I have Suse 9.2 installed on another drive and the sound is OK. I have copied the relevant parts of the two dmesg files
for each OS. As you can see Suse 9.2 sees the driver immediately and gets it right whereas Suse 10 has innumerable attempts
before loading it even though it is not working.
The crucial part appears to be the measured usecs seen by Suse 10. They are obviously much too high hence the repeated
attempts to get it right. It eventually loads even though it is still too high.
6. Does anyone know how one can force it to see a usecs measurement of approximately 49000?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.