On 05/13/2007 12:17 PM, ramkromberg@mail.com wrote:

> EPPROM OFF (SOFTWARE ON):
> 
> in dos: diagnose works,
> reboot and back to lin: sudo modprobe snd-sb8 port=0x220 irq=5 dma8=1
> 
> no error, no mention in dmesg, but xmms gives the usual error...

Yep. The DSP is there but the IRQ isn't firing.

I now understand what the difference between our boards is; we both have a 
jumper that can be set to EEPROM, but only I actually have an EEPROM...

It's amazing the things some manufacturers choose to save a penny on but 
both your and my (formerly) non-working AZT2316A boards do not have an 
actual EEPROM. It should be on that spot marked UX2 close to the clock (the 
shiny metal thing in the lower left corner).

This also means your board is simply not supported by any driver currently 
available in the tree. The driver needs to "play EEPROM" and upload the 
configuration values to the AZT2316 before the card will work and current 
drivers don't do this (under DOS, it's the job of that EEPROM.SYS DOS device 
driver that's executed from CONFIG.SYS).

Attached is a new snd-galaxy driver that _does_  do the enabling. It's not 
final yet, but works nicely for my EEPROM-less boards. It took quite a bit 
of grovveling around but it's completely documented now.

I want to test it with more cards first, with and without EEPROMS and with 
the JMPCFG jumper set to either position, need to figure out full-duplex on 
cards with a CS4231 (as opposed to a half-duplex CS4248), want to see if 
there are any cards among them that allow _both_ the SB and the WSS part to 
be active, and will finally merge in snd-azt2320 as well for one unified 
snd-galaxy driver.

Thought I'd post it now though. You already said you can't compile new 
drivers for that machine anyhow so consider this just for educational 
purposes. In the next message I'll post a small userspace program to do the 
enabling from userspace so that you can use that for now and then just use 
either snd-sb8 or snd-sgalaxy to drive the card.

Rene.