I've posted this issue in the Hardware and the Mulitmedia forums with no response. Google, emailing module authors, and other mailing lists have all failed to solve my problem.

Here's the URL to one of the forum posts:
http://forums.gentoo.org/viewtopic.php?t=99012

Here's the text from it with some minor edits, in case you don't feel like messing with the web:
--------
I'm running a PnP SB AWE64. The BIOS on boot reports an IRQ of 5 and DMAs of 3 and 6. dmesg reports that ISAPnP finds an IRQ of 5 and DMAs of 1 and 5. Not surprisingly, most sound doesn't play complaining of improper IRQ or DMA settings. The occasional sound I get out of it is fine, but very infrequent.


I've compiled in ISAPnP, and built OSS and the sb driver as modules. Here are relavent lines from my module files:

First, my initial configuration:
/etc/modules.autoload.d/kernel-2.4:
sb
awe_wave

/etc/modules.d/aliases:
alias sound-slot-0 sb
alias sound-service-0-1 awe_wave
post-install awe_wave /usr/bin/sfxload

I've emerge awefx and whatnot. I've done my best to follow the instructions found in /usr/src/linux/Documentation/sound/AWE32. When I noticed that ISAPnP and my BIOS didn't agree, I double checked to make sure Plug and Play OS was disabled in my BIOS, and that everything else in there was groovy. It seemed OK.

So, in an attempt to get things to agree, I added

irq=5 dma=3 dma16=6 io=0x220 mpu_io=0x330 isapnp=0

to the sb lines in both files listed above. In other words, my autoload file had the line:

sb irq=5 dma=3 dma16=6 io=0x220 mpu_io=0x330 isapnp=0

The aliases file was similar. I also ran modules-update whenever I changed things. I double checked in /proc/ioports that the mpu_io and io settings were as above. This seemed to have no effect other than to cause a module failure report at boot. Strange thing is that the module still loaded by the time I logged in, with the old 1 and 5 DMA settings.

If anybody can help me override ISAPnP so I can get the proper DMA settings in there, I'd really appreciate it.
--------


Any help or suggestions would be truly appreciated. I'm really getting frustrated here. This card worked with no hardware changes under RedHat 9, so I know this is a software problem.

Chad Martin


-- [EMAIL PROTECTED] mailing list



Reply via email to