Re: [SLE] ESS Maestro 3 & SuSE 7.0
I have SuSE 7.0 installed on a laptop with an ES1980 PCI audio controller, which is not recognized by the kernel (2.2.16). From ftp://ftp.suse.com/pub/people/tiwai I downloaded the relevant alsa-rpms and installed them according to the instructions there, but it still didn't work. I hope that someone here can help me. Here are the details:
I have a Maestro 3 card, and found I needed to use the code from the alsa homepage to get it to work under SuSE7.0 Installation from their code is easy enough, and there is good documentation should you have a problem. They're at: http://www.alsa-project.org Have Fun, Jim. -- James McBoyle /"\ james.mcboyle@sun.com \ / ASCII Ribbon Campaign Software Engineer X Against HTML Mail Integrated Software QED / \
I wrote:
I have SuSE 7.0 installed on a laptop with an ES1980 PCI audio controller, which is not recognized by the kernel (2.2.16). From ftp://ftp.suse.com/pub/people/tiwai I downloaded the relevant alsa-rpms and installed them according to the instructions there, but it still didn't work. I hope that someone here can help me. Here are the details:
james.mcboyle@ireland.sun.com writes:
I have a Maestro 3 card, and found I needed to use the code from the alsa homepage to get it to work under SuSE7.0 Installation from their code is easy enough, and there is good documentation should you have a problem. They're at:
In fact, I had previously tried to compile and install Alsa 0.5.11 from their source code, without success. Perhaps you can tell me exactly what steps you did? For reference, here's part of the output of my attempt: root@steve:/home/steve/computer/alsa/alsa-driver-0.5.11 > ./configure --with-debug=detect loading cache ./config.cache checking for gcc... (cached) gcc checking whether the C compiler (gcc ) works... yes .... checking for kernel version... 2.2.16 checking for kernel module symbol versions... no checking for PCI support in kernel... yes checking for SGI/MIPS (HAL2) architecture... no checking for directory to store kernel modules... /lib/modules/2.2.16/misc checking for debug level... detect checking for processor type... i686 checking for SMP... no checking for ISA PnP driver in kernel... no checking for ISA PnP support... yes checking for driver version... 0.5.11 checking for sequencer support... yes checking for OSS/Free emulation... yes checking for which soundcards to compile driver for... all creating ./config.status creating Makefile.conf creating snddevices creating utils/alsa-driver.spec creating cards.config creating include/config.h creating include/config1.h include/config1.h is unchanged creating include/version.h include/version.h is unchanged root@steve:/home/steve/computer/alsa/alsa-driver-0.5.11 > make clean rm -f `find . -name ".depend"` ... root@steve:/home/steve/computer/alsa/alsa-driver-0.5.11 > make make dep make[1]: Entering directory `/home/steve/computer/alsa/alsa-driver-0.5.11' make[2]: Entering directory `/home/steve/computer/alsa/alsa-driver-0.5.11/support' ... sound_oss.c:27: #error "Enable the OSS soundcore multiplexer (CONFIG_SOUND) in the kernel." make[2]: *** [.depend] Error 1 make[2]: Leaving directory `/home/steve/computer/alsa/alsa-driver-0.5.11/kernel' make[1]: *** [dep] Error 1 make[1]: Leaving directory `/home/steve/computer/alsa/alsa-driver-0.5.11' make: *** [include/sndversions.h] Error 2 root@steve:/home/steve/computer/alsa/alsa-driver-0.5.11 > make install make[1]: Entering directory `/home/steve/computer/alsa/alsa-driver-0.5.11/support' ... sound_oss.c:27: #error "Enable the OSS soundcore multiplexer (CONFIG_SOUND) in the kernel." make[1]: *** [sound_oss.o] Error 1 make[1]: Leaving directory `/home/steve/computer/alsa/alsa-driver-0.5.11/kernel' make: *** [compile] Error 1 root@steve:/home/steve/computer/alsa/alsa-driver-0.5.11 > ./snddevices Creating /dev/mixer?... done Creating /dev/sequencer... done Creating /dev/midi?... done ... root@steve:/home/steve/computer/alsa/alsa-driver-0.5.11 > modprobe snd-card-maestro3 modprobe: Can't locate module snd-card-maestro3 I couldn't figure out why it didn't work, but thought it might be due to SuSE-specific features, that's why I decided to try SuSE-specific rpm's. But so far, no luck there either. Someone else said it looked like I had PnP set to yes in the BIOS and I should try setting it to no; unfortunately, there is, as far as I can tell, no mention of PnP whatsoever in my BIOS (Phoenix Version 4.0 R6 04UE), so I don't know what alternative I have.... --Steve Berman
* Stephen Berman [19 Oct 2001 17:13:31 +0200]:
sound_oss.c:27: #error "Enable the OSS soundcore multiplexer (CONFIG_SOUND) in the kernel." make[2]: *** [.depend] Error 1
Very, very easy ;-) You have to configure your kernel source code. If you're using the sources for the SuSE kernels *and* you're running a standard SuSE kernel, just do cd /usr/src/linux make cloneconfig If you're using a vanilla kernel, configure the kernel via menuconfig, config or xconfig and set sound support to 'm', i.e a modular soundcore. Philipp -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390
philippt@t-online.de (Philipp Thomas) writes:
* Stephen Berman [19 Oct 2001 17:13:31 +0200]:
sound_oss.c:27: #error "Enable the OSS soundcore multiplexer (CONFIG_SOUND) in the kernel." make[2]: *** [.depend] Error 1
Very, very easy ;-) You have to configure your kernel source code. If you're using the sources for the SuSE kernels *and* you're running a standard SuSE kernel, just do
cd /usr/src/linux make cloneconfig
If you're using a vanilla kernel, configure the kernel via menuconfig, config or xconfig and set sound support to 'm', i.e a modular soundcore.
Well, I have the standard laptop configuration for 2.2.16 with SuSE 7.0 and haven't recompiled the kernel since the initial installation; the following lines are in /usr/src/linux/.config: CONFIG_SOUND=m CONFIG_SOUND_OSS=m Isn't this what you're suggesting? Yet it didn't work. However, I've now got a solution, which is to deactivate the Windows ACPI and APM BIOS settings. This (for reasons I don't understand, though I'd like to) has permitted the PCI sound card to be assigned an IRQ on booting, and that's what Alsa needed. (This was suggested to me in the German SuSE-Linux list -- this alone has made it worth subscribing to both lists, even though it means slogging through more than 500 mails a day :-) .) What's more, I still can use suspend-to-disk under Linux without a problem (at least till now...). (However, suspend-to-disk is now not working properly under Windows, but since I work primarily under Linux, the trade-off is worth it to me.) --Steve Berman
participants (3)
-
james.mcboyle＠ireland.sun.com -
philippt＠t-online.de -
Stephen Berman