sound config with 2.2.10 in slink environment

1999-07-26 Thread Damir J. Naden
Hi, all
I have upgraded my 2.0.36 kernel (home compiled) to a home compiled 2.2.10
(all sources are debianized packages), and all is well (actually, remarkably
faster, it seems) except for sound.
I have enosniq soundscape elite ISA card, which worked under 2.0.36, after I
have made a script at boot-up which initialized the card. Now that same script
gives me error (both manually and at boot-up):

[EMAIL PROTECTED]:/usr/local/bin# ./ssinit
/dev/dsp: Operation not supported by device

My /dev/sndstat is completely empty, since the card is not initializing. i can
supply both /etc/soundconf (which worked under 2.0.36) and my .config options
for sound module (sound is compiled as a module in both old and new kernel) in
2.2.10 sources; if anyone can help. I have read HOWTOs and docs for soundscape
cards at 4front technologies, but I'm afraid I can't decipher the info there
to translate into my config.
Also, once I have it figured out, how do I ( the Good way) insert module
options into /etc/conf.modules (it says not to edit the file...)?
TIA,
damir

P.S. since this may or may not be debian specific, could you reply to my
private address instead of the list if you feel that is more appropriate


Re: sound config with 2.2.10 in slink environment

1999-07-26 Thread Wayne Topa

Subject: sound config with 2.2.10 in slink environment
Date: Mon, Jul 26, 1999 at 12:57:26AM -0400

In reply to:Damir J. Naden

Quoting Damir J. Naden([EMAIL PROTECTED]):
 I have enosniq soundscape elite ISA card, which worked under 2.0.36, after I
 have made a script at boot-up which initialized the card. Now that same script
 gives me error (both manually and at boot-up):
 
 [EMAIL PROTECTED]:/usr/local/bin# ./ssinit
 /dev/dsp: Operation not supported by device

IIRC I have read similar problems and answers reported in the past.
May I suggest that you check the archives for possible solutions to
your problem and come back here if you can't find any solutions that
apply.

-- 
There are two ways to write error-free programs; only the third one
works.
___
Wayne T. Topa [EMAIL PROTECTED]