SoundBlaster 16 broken in 7.1?
Hi: I have a Pentium 3 system with ISA-PnP SB16 card. It works fine under Suse 7.0 using ALSA. I have also compiled my own generic kernel 2.2.18 for Suse 7.0, and compiled ALSA 0.9 beta driver source package, and they work fine under 7.0 However, the SB16 card doesn't work under 7.1, using either Suse's attempt at configuring the soundcard under Yast2 or when I compiled my own generic 2.2.18 and ALSA 0.9beta under 7.1 All the drivers appear to load fine. Output of lsmod on the 7.1 system shows a long list of snd-* drivers, although a few items on the lsmod output in the 7.0 system are not in the 7.1 list. I am not sure if this is the issue or not. No error is indicated when modprobe snd-card-sb16. What is wrong is that even though the drivers are present (and yes I turned up the mixer) they simply don't play. Any process that tries to play sound hangs. For example, the aplay process that KDE initiates on startup to play the startum song, it just hangs. ps shows it sitting there an hour after KDE started. Xmms just hangs. It's broken. First I'd like to know if anyone else is aware of SB16 problems on Suse 7.1 and is there an obvious fix? If not, where might I go from here to debug this? Thanks. -- _____________________ Christopher R. Carlen crcarl@inreach.com Suse 7.0 Linux 2.2.18
Chris - I've been having similar problems with a SB32AWE card. I could occasionaly get it to work by configuring it with YAST2, but it would not work after rebooting. I've decided to go back to using kernel support and skip using ALSA. I at least have a working card now, although there are a few things to work out yet. There seems to be up to date documentation in the /usr/src/linux/Documentation directory. Good luck. Harry On Sat, 28 Apr 2001, Chris Carlen wrote:
Hi:
I have a Pentium 3 system with ISA-PnP SB16 card. It works fine under Suse 7.0 using ALSA. I have also compiled my own generic kernel 2.2.18 for Suse 7.0, and compiled ALSA 0.9 beta driver source package, and they work fine under 7.0
However, the SB16 card doesn't work under 7.1, using either Suse's attempt at configuring the soundcard under Yast2 or when I compiled my own generic 2.2.18 and ALSA 0.9beta under 7.1
All the drivers appear to load fine. Output of lsmod on the 7.1 system shows a long list of snd-* drivers, although a few items on the lsmod output in the 7.0 system are not in the 7.1 list. I am not sure if this is the issue or not. No error is indicated when modprobe snd-card-sb16.
What is wrong is that even though the drivers are present (and yes I turned up the mixer) they simply don't play. Any process that tries to play sound hangs. For example, the aplay process that KDE initiates on startup to play the startum song, it just hangs. ps shows it sitting there an hour after KDE started. Xmms just hangs. It's broken.
First I'd like to know if anyone else is aware of SB16 problems on Suse 7.1 and is there an obvious fix? If not, where might I go from here to debug this?
Thanks.
I commented out YAST2's modules.conf entries, and uncommented the default ALSA example entries, including those for the SoundBlaster 16. ALSA now works using Suse's kernel and modules. However, I get strange problems and still no sound when trying to compile ALSA 0.9.0beta3 myself with my compiled generic 2.2.18 kernel. I did the exact same sequence of compiling steps for ALSA on the 7.1 system as on the 7.0 (with compiled generic 2.2.18 on 7.0 also), the compiled ALSA mods load, but there is no sound and /etc/init.d/alsasound reports: alsactl: SND CTL open error: Sound protocol is not compatible I compiled ALSA with full debugging option, and there are no errors reported on detecting the card or getting the drivers into the kernel. Only this problem. kmix shows a blank for CTL1745 (I think) which is where the working mixer channels show up when using the functional ALSA with Suse's kernel. But when I load my ALSA drivers into my kernel, there is another mixer tab "00" which has sliders, but of course that doesn't do any good because aplay or any other sound programs don't play due to the "protocol incompatible" . Any clues? Thanks. _____________________ Christopher R. Carlen crcarl@inreach.com Suse 7.0 Linux 2.2.18
* Chris Carlen [Sun, 29 Apr 2001 10:40:56 -0700]:
alsactl: SND CTL open error: Sound protocol is not compatible
alsactl and all other alsa tools and the library all have to be compatible. So if you compile new ALSA drivers, you also need to fetch the matching library and tools and recompile them. If not, you get the above error. -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390
Philipp Thomas wrote:
alsactl: SND CTL open error: Sound protocol is not compatible alsactl and all other alsa tools and the library all have to be compatible. So if you compile new ALSA drivers, you also need to fetch
* Chris Carlen [Sun, 29 Apr 2001 10:40:56 -0700]: the matching library and tools and recompile them. If not, you get the above error.
Thanks for the reply. Ok, I will try getting the new stuff, or maybe it will be easier to just use the older drivers. But can you explain this: Why is it that when I compiled the alsa-driver-0.9.0beta3 source on the Suse 7.0 system (with generic 2.2.18 kernel), it worked Ok even though I didn't update the other libs/tools? _____________________ Christopher R. Carlen crcarl@inreach.com Suse 7.0 Linux 2.2.18
participants (3)
-
Chris Carlen
-
Harry Reinert
-
Philipp Thomas