Bug 5634

Summary:	ALSA fails with SB16 value
Product:	Drivers	Reporter:	Ralf Neubauer (ralf)
Component:	Sound(ALSA)	Assignee:	Alexey Dobriyan (adobriyan)
Status:	CLOSED CODE_FIX
Severity:	normal	CC:	horms, tiwai
Priority:	P2
Hardware:	i386
OS:	Linux
Kernel Version:	2.6.14-2	Subsystem:
Regression:	---	Bisected commit-id:

Description Ralf Neubauer 2005-11-20 23:33:08 UTC

Hello,

my friendly Debian maintainer told me to put 340108@bugs.debian.org upstream.


Most recent kernel where this bug did not occur: --
Distribution: Debian testing


Hardware Environment:

"SB16 value" card,
OSS says (in dmesg) about this card (using the parameters from below):

sb: Init: Starting Probe...
sb: Probing legacy card with io=220, irq=5, dma=1, dma16=5
SB 4.12 detected OK (220)
sb: Turning on MPU
sb: Init: Done
YM3812 and OPL-3 driver Copyright (C) by Hannu Savolainen, Rob Hooft
1993-1996

The other card I have is detected as SB 4.13 (i think, at least a small
difference in the version number) and is jumpered to IRQ7 instead of
IRQ5.

machine a) K6-III/450 Asus Board, ALi Chipset, e100, GeForce2-MX, Dawicontrol
Scsi (AMD chipset)
machine b) 5x86/133 VLB/PCI combi board, 3c509, S3 trio

sorry I don't know the hardware by heart, but the single constant is the SB16
value, the rest has variations everywhere. of course they are standing at the
same global coordinates and the sysop is the same as well (and may be at fault ..).

Software Environment:
debian kernel linux-image-2.6.14-2-386
or linux-image-2.6.12-1-386
or kernel-image-2.4.27-2-386 with alsa-modules

no binary nvidia driver loaded

Problem Description:
My "SB16 value" cards (ISA, afaik no PNP) don't work with ALSA.
The words "SB16 value" are litererally printed on the card. As I found
out, these seem to be SB16's without a MIDI interface (but with OPL3).

The OSS modules work perfectly with the /etc/modules entries

        sb irq=5 io=0x220 mpu_io=0x330 dma=1 dma16=5
        opl3 io=0x388

The corresponding ALSA line

        snd-sb16 irq=5 port=0x220 mpu_port=0x330 dma8=1 dma16=5 isapnp=0

simply says

FATAL: Error inserting snd_sb16
(/lib/modules/2.6.14-2-386/kernel/sound/isa/sb/snd-sb16.ko): No such
device
FATAL: Error running install command for snd_sb16

and puts

Sound Blaster 16 soundcard not found or device busy
In case, if you have AWE card, try snd-sbawe module

into dmesg. As there may be no MPU I tried with mpu_port=0 and various
other variations (isapnp=1 etc).

alsaconf simply tries to use
        alias snd-card-0 snd-sb16
        options snd-sb16 index=0 isapnp=0
which fails as well.


Steps to reproduce:

reboot, load module with above mentioned parameters.

Comment 1 Ralf Neubauer 2006-01-13 12:43:42 UTC

Debian unstable's linux-image-2.6.15-1-486 improved the situation somewhat.

Now

modprobe snd-sb16 isapnp=0

works and appending the whole irq/port/dma list works too. I can play a test mp3
with mpg123 (via /dev/dsp) and alsaplayer. alsamixer works.

Only the snd-opl3-synth module doesn't really work, I never managed to get more
than 0 or 1 note of a midi file played, depending on midi player (playmidi -f,
tse3play, pmidi) and input file. stracing shows that the players stuff lots of
data into the appropriate device and then hang, while nothing is played. Some
times playmidi even hung unkillable, had to reboot for further experiments.

This may have to do with missing/wrong irq/port/dma/other parameters, just I
can't think of more things to fiddle with; I compared them with the working OSS
settings and the Windows configuration data.

Comment 2 Lee Revell 2006-01-20 19:22:32 UTC

For future reference "upstream" for ALSA bugs is the ALSA bug tracker, not this
bugzilla:

https://bugtrack.alsa-project.org/alsa-bug/main_page.php

Anyway I think this should be considered resolved - can you open a new bug
report for the OPL synth issue?

Comment 3 Alexey Dobriyan 2006-09-07 10:17:05 UTC

OK, original issue resolved, snd-opl3-synth-not-working is separate story and
ALSA developers use their own bugzilla. Reopen there.