Mailinglist Archive: opensuse (3637 mails)

< Previous Next >
Re: [SLE] Suse 7.1, ALSA, and SB16 issues
Hi
One thing I see, is in your modules.conf , you didn't delete all the alsa related stuff .
just comment out ##
the following to start with.

## YaST2: sound cards support
> #
> alias char-major-116 snd
> options snd snd_cards_limit=1 snd_major=116
>
> #
> # 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

Now , if you want to use oss for sound , get rid of alsa boot script - /sbin/init.d/alsasound
see if you can use Yast to 'delete files , and choose to delete anything ALSA.
yast should delete all installed alsa stuff .

Looks like you have some kernel problems too , maybe someone on the list here
can jump in to help you with that if you don't solve it yourself.

one thing at a time I guess .

Hope this helps
cheers
John



On Wed, 02 May 2001, Ron Sinclair wrote:
> I finally have Suse 7.1 on my system. I used the default installation with
> the 2.4 and 2.2.18 kernels and ReiserFS. The installation went fine and I'm
> dualbooting it with W98 using BootMagic.
>
> I'm having problems getting the sound to work. I have an ISA soundcard, a
> Soundblaster16. I've always had problems getting Suse 6.4 to automatically
> detect it. When installing Suse, it always tries to use ALSA and I have to
> remove ALSA in order to get my card functional. I'd thought ALSA supported
> Creative soundcards, especially a SB16, but everytime I try to install Suse,
> Suse has issues with my soundcard....even version 7.1. This is what Yast2
> looks like after trying to configure my modem:
> http://members.fortunecity.com/wigglit/ronpics/snapshot3.png
>
> I removed the ALSA package and anyting associated with it from my box today,
> expecting things to be ok. NOT.
>
> Somehow, my box is still trying to use ALSA. The manual states to use OSS
> (package opso) in place of ALSA when problems occur with ALSA, but when I did
> a search for this package, Suse couldn't find it. It also states that SAX2
> can only configured soundcards using the ALSA package. After I removed ALSA,
> I checked Yast2 under 'Sound'. This is what I found:
> http://members.fortunecity.com/wigglit/ronpics/snapshot4.png
>
> I've tried hacking modules.conf to configure my card to no avail, even after
> removing ALSA altogether. Here's what my current modules.conf looks like.
> I've cut out the irrelevant parts:
>
> _________________
> #*****************************************************************************
> # module : sb.o Soundblaster 16, SB Pro + Clones
> # Also needed for AWE32/64
> #
> # Dcoumentation available in
> /usr/src/linux/Documentation/sound/Soundblaster
> # and in /usr/src/linux/drivers/sound/sb.c .
> #
> # Possible configuration :
> #
> alias char-major-14 sb
> alias sound on
> alias midi on
> post-install sb /sbin/modprobe "-k" "adlib_card"
> options sb dma=3 dma16=7 io=0x220 irq=5 mpu_io=0x330
> options adlib_card io=0x388
> #
> ..
> ...
> ...
> ...
> ...
> ...
> ...
> ## YaST2: sound cards support
> #
> alias char-major-116 snd
> options snd snd_cards_limit=1 snd_major=116
>
> #
> # 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
> _______________
>
> I also get error messages in the console log (only with the out-of-the-box
> 2.4 kernel):
>
> _______________
> Console log for 500mhz
> May 2 12:01:59 500mhz kernel: PCI: Found IRQ 9 for device 00:09.0
> May 2 12:01:59 500mhz kernel: usb-uhci.c: Detected 2 ports
> May 2 12:01:59 500mhz kernel: usb.c: USB device 3 (vend/prod 0x46d/0x840) is
> not claimed by any active driver.
> May 2 12:01:59 500mhz kernel: usb.c: USB device 4 (vend/prod 0x4a9/0x2204)
> is not claimed by any active driver.
> May 2 12:02:09 500mhz modprobe: modprobe: Can't locate module char-major-145
> May 2 12:02:09 500mhz modprobe: modprobe: Can't locate module char-major-145
> May 2 12:02:42 500mhz kernel: isapnp: Scanning for Pnp cards...
> May 2 12:02:42 500mhz kernel: isapnp: No Plug & Play device found
> May 2 12:02:43 500mhz kernel: <Sound Blaster 16 (4.13)> at 0x220 irq 5 dma
> 1,5
> May 2 12:02:43 500mhz kernel: <Sound Blaster 16> at 0x330 irq 5 dma 0,0
> May 2 12:02:43 500mhz insmod:
> /lib/modules/2.4.0-4GB/kernel/drivers/sound/sb.o: post-install sb failed
> May 2 12:02:43 500mhz insmod:
> /lib/modules/2.4.0-4GB/kernel/drivers/sound/sb.o: insmod char-major-14 failed
> _______________
>
> This is getting frustrating. At least with Suse 6.4, I could eventually get
> the sound working. Suse 7.1 is so damn different that I may go six months
> without sound. What's worse is the fact that when KDE2 boots up, it plays
> that funky music, and I CAN hear that, just not music CDs. If I turn up the
> speakers to max, I can hear the music faintly.
>
> I get errors in the console window when I boot up with the 2.2.18 kernel, but
> the sound is still playing when KDE2 boots up and not playing when I put in a
> music CD:
>
> May 2 21:32:58 500mhz kernel: ATAPI device hdc:
> May 2 21:32:58 500mhz kernel: Error: Illegal request -- (Sense key=0x05)
> May 2 21:32:58 500mhz kernel: Logical block address out of range --
> (asc=0x21, ascq=0x00)
> May 2 21:32:58 500mhz kernel: The failed "Read Track Rzone Info" packet
> command was:
> May 2 21:32:58 500mhz kernel: "52 01 00 00 00 00 00 00 08 00 00 00 "
> _______________
>
> Seems to be USB related and not sound related errors.
>
> I'm at a total loss here. This is a fresh install. ISAPNP won't detect the
> soundcard or ISA modem that I have, but the modem works fine.
>
> I'm gonna leave it alone for a few days and see if I can clear my head and
> retry to fix this. Ugh....
>
> Update: Another nagging problem I just found out about ALSA is that after I
> removed it, when I went back later to install other software, I found that
> ALSA automatically reinstalls. I did this 3 times. WTF!?
>
>
> --
> To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
> For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the FAQ at http://www.suse.com/support/faq and the
> archives at http://lists.suse.com
--

God does not play dice" -- Einstein
"Not only does God play dice, he sometimes throws
them where they can't be seen." -- Stephen Hawking



< Previous Next >
This Thread
References