[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem with an Awe64 sound card on potato



Berthold Cogel wrote:
> 
> "Brian J. Dumont" wrote:
> >
> > Hi,
> >
> > I have a PII-333 machine with a Soundblaster Awe64 Gold installed.  I had
> > been running Redhat 6.1 for a couple years with the soundcard functioning
> > properly (so I think the hardware is OK).  I recently wiped the drive and
> > have installed Debian 2.2 instead, but I cannot seem to get the soundcard
> > to run.  I am using Debian's default 2.2.17 kernel.
> >
> > I have looked through the kernel config to verify:
> > CONFIG_SOUND_SB=m
> > CONFIG_SOUND=m
> > CONFIG_LOWLEVEL_SOUND=y
> > CONFIG_AWE32_SYNTH=m
> >
> > I have set up isapnp to work properly, giving these results:
> >
> > Board 1 has Identity f1 05 78 ee 7e b2 00 8c 0e:  CTL00b2 Serial No 91811454 [checksum f1]
> > CTL00b2/91811454[0]{Audio               }: Ports 0x220 0x330 0x388; IRQ5 DMA1 DMA5 --- Enabled OK
> > CTL00b2/91811454[1]{Game                }: Port 0x200; --- Enabled OK
> > CTL00b2/91811454[2]{WaveTable           }: Port 0x640; --- Enabled OK
> >
> > either at boot time or if I run isapnp from the shell.
> >
> > I have also appended the line:
> > sound
> > to my /etc/modules file.  After boot, I can run lsmod and see the
> > soundcore, soundlow, and sound modules, but if I cat /dev/sndstat
> > I see:
> >
> > OSS/Free:3.8s2++-971130
> > Load type: Driver loaded as a module
> > Kernel: Linux tim 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i686
> > Config options: 0
> >
> > Installed drivers:
> >
> > Card config:
> >
> > Audio devices:
> >
> > Synth devices:
> >
> > Midi devices:
> >
> > Timers:
> > 0: System clock
> >
> > Mixers:
> >
> > I can also find:
> >  14 sound
> > in my /proc/devices
> >
> > I then tried modprobe -a sb from my /lib/modules/2.2.17/misc
> > directory.  At this point, my /dev/sndstat looks like:
> >
> > OSS/Free:3.8s2++-971130
> > Load type: Driver loaded as a module
> > Kernel: Linux tim 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i686
> > Config options: 0
> >
> > Installed drivers:
> >
> > Card config:
> >
> > Audio devices:
> > 0: Sound Blaster 16 (4.16) (DUPLEX)
> >
> > Synth devices:
> >
> > Midi devices:
> > 0: Sound Blaster 16
> >
> > Timers:
> > 0: System clock
> >
> > Mixers:
> > 0: Sound Blaster
> >
> > with an lsmod of:
> > Module                  Size  Used by
> > sb                     33396   0  (unused)
> > uart401                 6128   0  [sb]
> > sound                  57592   0  [sb uart401]
> > soundlow                 416   0  [sound]
> > soundcore               2628   6  [sb sound]
> > lockd                  31112   1  (autoclean)
> > sunrpc                 52420   1  (autoclean) [lockd]
> > unix                   10212  96  (autoclean)
> >
> > which looks like it worked; but when I play a sound, I get every
> > other bit of the sound.  In other words, it plays for about 1/2 second,
> > then is silent for about 1/2 second, then plays for 1/2 second, and so on.
> >
> > It sounds to me like an IRQ conflict, but the only other ISA device
> > that's in the machine is a modem on ttyS1 IRQ3 (not PnP, set by jumpers);
> > and it doesn't seem like that should be the case anyway, since I haven't
> > switched any jumpers since I had Red Hat.
> >
> > I can't seem to figure out what I'm missing.  Any ideas?
> > Thanks very much,
> > Brian
> >
> > -------------------------------------------------------------------------------
> > Brian J. Dumont - bdumont@airflowsciences.com
> >
> > --
> > Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
> 
> I don't know what is wrong. I have the same problem since I updated from
> Slink to Potato. Somehow the module sb tries to use IRQ7 even if I try
> to set IRQ5. The same kernel (2.2.14) and the same configuration worked
> well with Slink. Perhaps there's a bug in one of the packages (isapnp,
> modutils ???).
> 
> Berthold Cogel

Perhaps a work-around would be to configure isapnp such that the sound card
uses IRQ7 instead of IRQ5.  Has anyone solved and/or found a workaround to 
this type of problem?

Thanks,
Brian


-------------------------------------------------------------------------------
Brian J. Dumont - bdumont@airflowsciences.com



Reply to: