yesterday i wrote about my trouble getting the sgalaxy module to
work. i've spent some time debugging, and still haven't gotten
much further, but thought i should ask a basic question:
is anyone successfully using the snd-card-sgalaxy module with an
aztech sgalaxy card?
(i always assume that the code must work for everyone else, but of course,
that's not _always_ the case. :-)
my alsa and kernel version numbers appear below.
my card(s) came from an old packard bell 486 machines. these cards
have been working fine with the OSS drivers, and i haven't touched their
config. my devices and sndstat output look like:
$ cat /proc/asound/devices
0: [0] : control
1: : sequencer
6: [0- 0]: mixer
16: [0- 0]: digital audio playback
24: [0- 0]: digital audio capture
33: : timer
$ cat /proc/asound/sndstat
Sound Driver:3.8.2-980706 (ALSA v0.5.12 emulation code)
Kernel: Linux moss 2.2.16-22 #9 Sat Nov 17 14:28:52 EST 2001 i586
Config options: 0
Installed drivers:
Type 10: ALSA emulation
Card config:
Sound Galaxy at 0x530, irq 7, dma 1
Audio devices:
0: CS4248
Synth devices: NOT ENABLED IN CONFIG
Midi devices: NOT ENABLED IN CONFIG
Timers:
7: system timer
Mixers:
0: CS4248
again, the symptom is that output hangs, or in some cases times out
with EIO, after some number of writes to /dev/audio (for oss-aware
programs). alsamixer seems to work fine. when using aplay, strace
shows an early ioctl failing after a brief timeout, with EIO. the log
shows the following:
Nov 30 09:19:00 moss kernel: snd: ad1848_mce_down - auto calibration time out (1)
Nov 30 09:19:10 moss kernel: snd: playback flush error (DMA or IRQ trouble?)
i'd be happy with any suggestions someone can offer...
paul
> hi --
>
> i recently upgraded to alsa drivers on the 4 or 5 machines that
> i maintain (all running 2.2.16), primarily to get better support for
> my GUS Max cards. sure enough, they now work flawlessly (i couldn't
> get recording to work with the free OSS drivers), and so does my one
> creative labs' soundblaster. however, a couple of cards that used to
> work fine now almost work, but not quite.
>
> the cards in question were shipped with some relatively ancient
> Packard Bell 486 boxes, and were called "Sound 144 Sound Card".
> i was able to use them with the OSS drivers, using the sgalaxy
> module:
> options sgalaxy io=0x530 irq=7 dma=1 sgbase=0x220
> but when i put in what i think is the equivalent for alsa:
> options snd-card-sgalaxy snd_sbport=0x220 snd_wssport=0x530 \
> snd_irq=7 snd_dma1=1
> (line broken for clarity) the module will load, and data can be
> written (at first), but then it hangs, and no output is forthcoming.
>
> it seems like this must be a missing interrupt (or interrupt conflict)
> problem, but since the new driver was the only change, and i sort of
> thought i'd configured them the same, i'm stumped.
>
> the one thing that sort of tickles at my memory is that i think i was
> running these cards in MSS (?) mode to get them to work the first time
> around -- but i'm not sure what that means, or meant, or what it
> implies... and i may even be mis-remembering.
>
> i'm kind of hoping for a been-there-done-that response from someone,
> or a pointer to what i should check next... thanks!
>
> paul
> =---------------------
> paul fox, [EMAIL PROTECTED] (arlington, ma, where it's 37.9 degrees)
>
> _______________________________________________
> Alsa-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/alsa-user
=---------------------
paul fox, [EMAIL PROTECTED] (arlington, ma, where it's 45.0 degrees)
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
