Kernel 2.6.27.19-3.2-default
KDE 3.5.10 “release 21.9”
Net-Installation, 8 weeks ago
Freeze means keyboard, mouse without function, hd-led is burning permanently, reset is needed.
Sound works well,system sounds and mp3, but freezes occurs when:
-starting x-server with KDE startsound
-playing mp3 with any player (amarok, xmms, smplayer) after several minutes (4-5)
-shutdown from KDE with NO endsound
Freezes can be reproduced at any time.
Without a x-server running i can play mp3 for hours on the command line with for ex. mplayer,
but when starting the x-server it freezes again.
After a freeze, the configured soundcard entry disappears from the yast soundcard menu, but the
modules are still loading and sound works.
So, it looks like there is a problem with the sound kernelmodule snd-sb16 and the x-server.
Any ideas? Thank you very much for your time
If you think it is x-server related, then it could be your graphic driver. Investigate what graphic hardware your PC has. Investigate what graphic driver you are using. If using the proprietary driver, you could try rolling back to an older version of the graphic driver. Alternatively, you could try switching from the proprietary to the openGL graphic driver or to the VESA graphic driver. In all cases, there will be a compromise in terms of lost speed or functionality.
Thanks for the answer.
It is definitely neither the x-server nor the graphic driver that causes the freeze. The buggy part is the Sound Kernelmodul snd-sb16.
Maybe anybody can tell me, how to contact the developers of the kernelmodul? Which packet contains the modul?
I am using Suse since version 5.3 without problems, but with 11.1 the soundblaster 16 dont works any longer.
Did you install alsa-firmware? and then restart and test.
I know you stated it is not graphic driver related, but the fact it does not happen with run level 3 (without an x-server) suggests otherwise, and suggests there is a factor there (although maybe its the KDE desktop as opposed to the graphic driver). Still, to be 100% certain, did you try compatibility with the VESA driver? Does the same problem happen with the VESA driver? With the openGL driver? With the proprietary driver?
Did you try forcing a re-install of just the alsa apps ?
Did you try updating from 1.0.17 / 1.0.18 to 1.0.19 using the wiki page I wrote here: Alsa-update - openSUSE Note if updating to 1.0.19 per that wiki page you need to send six zypper commands. Three commands are associated with updating your alsa apps (you can tell which alsa apps you have installed by typing " rpm -qa | grep alsa " ) and three commands are for adding alsa-driver-kmp-your_kernel_version which you must also add. Restart and test.
Failing that, to contact a dev, you need to write a bug report. There is guidance here: Submitting Bug Reports - openSUSE To ensure a sound developer sees the problem, you need to categorize the problem under sound.
rpm -qa | grep alsa
alsa-utils-1.0.18-6.4
alsa-tools-gui-1.0.18-1.13
alsa-oss-1.0.17-1.37
alsa-1.0.18-8.7
alsa-firmware-1.0.17-1.42
alsa-driver-kmp-default-1.0.19.20090330_2.6.27.19_3.2-1.1
java-1_6_0-sun-alsa-1.6.0.u12-1.2.1
alsa-tools-1.0.18-1.13
alsa-plugins-1.0.18-6.12
I already tested several of the almost daily updated alsa-driver-kmp with no result. I know your wiki page, but i didn’t upgrade alsa until now, because some people from alsa didn’t made me much hope. They suggest, like me, the error occurs not on the alsa layer, but below, directly with the kernel modul. This would explain, why the freeze happens with every sound output plugin like alsa, arts, eSound, OSS. To be sure about that, i am going to install a game with direct access to the soundcard during the next days.
I will also follow your hint and give a try to the alsa upgrade the next days.
The x-server is already tested with VESA and Nvidia graphic drivers. I also upgraded to the newest xorg-x11-server 7.4-17.4.1 all with no result.
Btw, thank you very much for the useful hints and links.
Unfortunately your timing could be bad. There was an update to the kernel to 2.6.27.21 yesterday, which means the alsa applications may update in the next day or two, which means the situation could be confusing for a few days as to the best alsa apps to try.
Reference writing a bug report on openSUSE, note that Novell fund the employment of a full time alsa developer, who also packages the sound drivers (ie alsa) for openSUSE. This means openSUSE tends to be very responsive in providing sound fixes. Hence writing a bug report on openSUSE (being careful to select the “SOUND” category in the bug report) means one gets the attention of a very capable alsa developer.
… In fact my efforts in helping in sound are to a large extent possible and to an equally large extent as an effort try an “leverage” his work in creating on-going alsa development builds (as rpms for openSUSE), by taking his rpm work for openSUSE and making it more easily installable by the average openSUSE user who needs an update beyond the basic “boxed” openSUSE.
Just a note to this. Typically if one installs alsa-driver-kmp-default , but does not install the git version of alsa, alsa-utils, alsa-firmware, alsa-tools, … etc … then one’s sound will be broken.
Note you MUST send six zypper comamnds. 3 commands to update all the alsa apps you have installed, and 3 commands to update your alsa-driver-kmp-your_kernel_version.
However with the kernel update (as of yesterday) things are a bit in flux … you will need to grab the 2.6.27.19 alsa rpms now, before they dissappear when they are replaced with the 2.6.27.21 alsa rpms.
Thats possibly because you only installed the alsa-driver-kmp. Thats NOT enough.
A version mismatch between alsa and alsa-driver-kmp is not possible, because i use zypper to update both as you described it on the wiki page.
Note that sound is working well, but i still got the same freezes as described in the first post.
Looking at the rpm versions I see the versions do not match. It is possible. Whether that is the cause of your problem, I do not know, but the mismatch is there.
I do not know what wiki page you refer to. The wiki page I wrote requires one send 6 zypper commands (3 for general alsa apps updates and 3 for alsa-driver-kmp-ones-kernel version).
Jap i did it as described on this page. I also updated alsa now.
rpm -qa | grep alsa
alsa-utils-1.0.19.git20090410-1.1
alsa-plugins-1.0.19.git20090303-1.14
alsa-oss-1.0.17.git20080715-2.26
alsa-1.0.19.git20090410-1.1
alsa-tools-gui-1.0.19.git20090320-1.4
java-1_6_0-sun-alsa-1.6.0.u13-0.1.1
alsa-firmware-1.0.19.git20090317-1.1
alsa-tools-1.0.19.git20090320-1.4
Alsa-driver-kmp is not available right now for my kernel version.
As expected sound and system sound still works well, but the freezes also works well as described in the first post sigh. No changes at all.
Do you think, there will be a better chance with the new kernel? Thank you for your patience.
IMHO you should write a bug report, being certain to put the problem under the category “sound”. That way you will get the attention of the openSUSE / alsa developer.
Last I looked the openSUSE/alsa developer had only packaged rpms for 2.6.27.19 kernel (on 6-April ) , and not yet for the 2.6.27.21 kernel. Probably on vacation over the Easter time frame … so if you wish to try the new kernel IMHO you should wait until the rpms are built for alsa for the new kernel.
Which graphic driver are you using? The proprietary nVidia driver? If so, what happens with your sound if you try the openGL graphic driver or the Vesa graphic driver?
OK, if you decided you wanted to try the new kernel, I see the updated 1.0.19 versions of alsa are available. Accordingly I updated the wiki: Alsa-update - openSUSE
Thx for the hint. I am going to try the new kernel next week.
The question about the graphic driver i already answered in post #5. I tried the last 2 versions of the x-server with and without the last 3 versions of the nvidia driver. The standard VESA was used, when no nvidia was installed. I also tried 3 players. All with no result.
Sorry.
To be sure, that the freeze isn’t caused by a single multimedia player i tried amarok, xmms and mplayer. All three produces the freeze after 5-8 min playtime.