Mark Hindley wrote:
> I am trying to setup my ALS 110 soundcard under my build of kernel
> 2.4.0-test10.
>
> I have built in isapnp support and also the sb and opl3 drivers.
>
> However, even though I pass opl3=0x388 on the Kernel command line all
> I get is an isapnp panic.
I'm experiencing what superficially appears to be a related problem
with an AWE64 card. I'm building the drivers non-modular (because
I've yet to find any description of how to configure modular sound
drivers for 2.4.0). I believe I'm making the appropriate configuration
settings - from my .config:
CONFIG_SOUND=y
CONFIG_SOUND_OSS=y
CONFIG_SOUND_TRACEINIT=y
CONFIG_SOUND_DMAP=y
CONFIG_SOUND_ADLIB=y
CONFIG_SOUND_VMIDI=y
CONFIG_SOUND_SB=y
CONFIG_SOUND_AWE32_SYNTH=y
CONFIG_SOUND_YM3812=y
and I'm passing "opl3=0x388" to the driver. However, if I query
what synth devices the driver supports, it only reports an
AWE32-0.4.4 (RAM512k) sample device. I expect it report an FM synth
device, too. I get the same (lack of) effect if I go via the
adlib_card code, by saying "adlib=0x388". My investigations so
far have shown that when opl3_detect() first tries to get the
signature of the OPL3 device, it gets 0xff from the inb() (line
195 of drivers/sound/opl3.c in test11pre1), while the corresponding
code in 2.2.18pre19 gets 0x00.
Stephen Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Nov 15 2000 - 21:00:20 EST