Have you upgraded your kernel? I was ok at first. Got an SB 16pci, ran Yast2 and it found the card, identified it perfectly and set everything up for me. Then I upgraded to 2.4.14 and it all stopped working. The first thing I noticed was that the module names were all different. On the default system there were a number of snd-* modules that got loaded. In my case, snd-card-ens1371 and friends. They also lived under the modules "misc" directory. They don't exist in the new kernel. The equivalent is ens1371.o and it lives in the drivers/sound directory (which seems more sensible to me). I couldn't work out how to get it working using loadable modules (and I did ask for help here but got no reply) so I built the support directly into the kernel. It works now, but KDE's control centre can't see the sound card details and Kmix gets totally confused about what type of card it's dealing with. I also still get the modprobe errors at boot time because something (alsa I think) is still trying to load the snd-* drivers. Running Yast2 again doesn't help either as it senses there is an entry there that isn't active and so just ignores it. There seems to be no way of deleting the original sound entry and starting again from scratch, so I gave up. The 2.4.14 came from SuSE's ftp upload directory, so I don't know why it doesn't build a kernel to the same specifications as the default installation. I suspect the kernel upgrade hasn't been built properly. John On Saturday 17 November 2001 12:27 pm, you wrote:

I have had similar problems to you. I wrote to the Suse Support and got the following reply. I have tried it and it has stopped the messages, but also the startup music has stopped.

Perhaps others can comment on this.

Regards,

David

Reply from Suse below ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Please control the yast2-sound entry in the end of the /etc/modules.conf.

# YaST2: sound cards support # alias char-major-116 snd options snd snd_cards_limit=1 snd_major=116 options snd-card-ens1371 snd_id=card1 snd_index=0

alias snd-card-0 snd-card-ens1371

# YaST2: sound system dependent part # alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-11 snd-mixer-oss alias sound-service-0-12 snd-pcm-oss

KDE-Mixer

You can ignore the message, because it is not an error message or you can change this in the KDE 2.0 control-center under:

-> Sound -> Mixer

Here you'll find the Option "Maximum count of tested devices per mixer" which is on the value "2". Change the value to "1" and confirm with "OK".

At the next KDE-Start the message won't occur anymore.

Kind regards,

Ihr SuSE Support-Team ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

On Fri, 16 Nov 2001 22:53:45 -0200, Jose Thadeu Cavalcante wrote:

...

Hello,

Everytime I start KDE the following four messages are showed in the log console:

XXX YYY modprobe: modprobe: Can't locate module sound-slot-3 XXX YYY modprobe: modprobe: Can't locate module sound-service-3-0 XXX YYY modprobe: modprobe: Can't locate module sound-slot-3 XXX YYY modprobe: modprobe: Can't locate module sound-service-3-0

XXX is the current date and YYY is name of the computer.

Simultaneosly, currently when I run the game xgalaga the sound don't work, only if I go to Yast2 and edit the sound board. This is necessary each time I start the KDE.

How can I solve this problem?

Thanks

-- Jose Thadeu Cavalcante thadeu@cbpf.br Linux user #228006

John Scott -- Thank you, thank you, thank you, thank you, thank you !! Now the world makes so much more sense. I've just re-read SuSE's 7.2 Reference Manual on Alsa again, and it does not make this point clear. Another thought crossed my mind though. In doc/packages/alsa there is a README.SuSE which says: Since SuSE-6.4, the alsa modules come with the kernel rpms specifically compiled for those kernels and the alsa package contains the libs, utils and mixers for alsa. ..and.. You can update the ALSA kernel modules either 1) by updating the kernel package (only if a newer kernel package exists). 2) by installing an alsa-driver package. The alsa-driver package is released usually by ALSA maintainers, and not stored on the official SuSE update directory. So basicly they are saying that they only supply pre-compiled binary modules for Alsa with the binary kernel packages. But they don't supply the source. So what I should have done was to download the pre-compiled 2.4.14 kernel rpm and installed that FIRST, before downloading the 2.4.14 source and attempting to build my own kernel. That would have worked, yes? John On Saturday 17 November 2001 1:29 pm, John Scott wrote:

The reason for this is that SuSE uses ALSA sound by default. Yast only knows how to configure ALSA sound. When you change your kernel config, the alsa modules shipped with your version will no longer work. You have to either switch to kernel modules or download the latest ALSA source and compile new modules for your card. If you do that then the entries in /etc/modules.conf should work unchanged. If you use kernel modules--which are much easier by the way--then you have to comment out all of the entries below and add lines to call the correct kernel modules.

The reason I say kernel modules are easier is that you always download them with your kernel and you can build and install them as part of the same process transparently. Otherwise you will have to recompile your alsa modules every time you upgrade your kernel. The major drawback to switching to kernel modules (with SuSE) is that you can no longer config your card with yast.

If you go to http://www.alsa-project.org/ you can download the source in 3 packages each of which must be installed in order. The alsa install howto on their site gives you step by step.

John

----- Original Message ----- From: "Jose Thadeu Cavalcante" To: Sent: Saturday, November 17, 2001 1:53 AM Subject: [SLE] Sound problems in KDE

...

Hello,

Everytime I start KDE the following four messages are showed in the log console:

XXX YYY modprobe: modprobe: Can't locate module sound-slot-3 XXX YYY modprobe: modprobe: Can't locate module sound-service-3-0 XXX YYY modprobe: modprobe: Can't locate module sound-slot-3 XXX YYY modprobe: modprobe: Can't locate module sound-service-3-0

XXX is the current date and YYY is name of the computer.

Simultaneosly, currently when I run the game xgalaga the sound don't work, only if I go to Yast2 and edit the sound board. This is necessary each

time I

...

start the KDE.

How can I solve this problem?

Thanks

-- Jose Thadeu Cavalcante thadeu@cbpf.br Linux user #228006

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com