Mike Sunderland wrote:
> I have RH5.1 with an AWE32pnp and midi working fine. Exactly what problems
> are you seeing?
>
> On 28-Aug-98 Neal Sanche wrote:
>
> > On Thu, 27 Aug 1998, Kyle Davenport wrote:
> >
> >> I had awe32 working thru all upgrades of Takashi Iwai's driver on
> >> Slackware, then tried Redhat 5.0 on a new system which irrepairably
> >> broke
> >> it._ I can not forgive Redhat for messing with the linux kernel!_
> >> Specifically, they added "modularization" to the sound drivers which
> >> broke Takashi's awe32 driver (It's been awhile, but I tried
> everything!)_
> >>(snip)
> > No. It's the same with RH5.1, but the modularized sound system have been
> > in linux-2.1.x for quite a while now, so you have to live with it
> > (assuming 2.2 will be out soon).
> >
> > I have an AWE32pnp and cant get midi to work, but it works nicely as a
> > SB16. I use this script for loading sound modules:
> >
> >#!/bin/sh
> >
> > /sbin/modprobe sound
> > /sbin/insmod uart401
> > /sbin/insmod sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
> > /sbin/insmod awe_wave
> >
> > The last line fails, but the rest works. Maybe it can be fixed with
> > isapnptools -- suggestions are welcome.
OK. Clarification for Tim Wright: we were talking only about the wave table
functions. In fact I have an original non-pnp awe32. The problems I had
were getting the sound part of the kernel to compile as a whole (a single
sound.o) or loading "modularized" sound which gave my symbol errors. Under
Slackware I had all kernel versions working up thru 2.0.33. It was
definitely RH's changes in 5.0 which broke it.
Neal - is it working for you as a single module or a bunch of sub-modules?
