Re: OPL3SAX SOUND BOARD
On Sun, Jun 20, 1999 at 11:39:18AM +0200, Peter Makholm wrote: > "People" <[EMAIL PROTECTED]> writes: > > > PLEASE > > GIVE-ME OPL3SAX SOUND BOARD > > Sorry but it seems like you caps lock i broken. > > OPL3-SAx works almost perfect with the new 2.2.x kernels. Grab a > kernel source read the Documentation/sound/OPL3SAx, compile and be > happy. I've got this eXtensa 390 (Acer/TI) with OPL3-SAx chipset, and I'm not yet able to make it work with Linux. I've used isapnp with the same parameters as the Windows95 driver, but every time I use MS Sound System (i.e. playing or recording a sample) the kernel freezes. The mixer works (I can listen to the CD and modify the mixer settings) but nothing else... There seems to be no IRQ, DMA or IO ports conflict, so I haven't got a clue. Ciao, Illo. -- Ilario Nardinocchi, [EMAIL PROTECTED] - Computer Science Adept since 1982 [EMAIL PROTECTED] Know-nothing-bozo rule: The views expressed above are entirely mine and do not represent the views, policy or understanding of any other person or official body.
Re: OPL3SAX SOUND BOARD
"People" <[EMAIL PROTECTED]> writes: > PLEASE > GIVE-ME OPL3SAX SOUND BOARD Sorry but it seems like you caps lock i broken. OPL3-SAx works almost perfect with the new 2.2.x kernels. Grab a kernel source read the Documentation/sound/OPL3SAx, compile and be happy. I think you need the isapnp package. > --=_NextPart_000_0004_01BEB9B1.B1A9D580 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable Please don't do that. -- I congratulate you. Happy goldfish bowl to you, to me, to everyone, and may each of you fry in hell forever. -- Isaac Asimov, "The Dead Past"
OPL3SAX SOUND BOARD
PLEASE GIVE-ME OPL3SAX SOUND BOARD ALL DRIVERS TO [EMAIL PROTECTED] THANK YOU
Re: Sound Board
Hamori Andras wrote: > > On Mon, 22 Mar 1999, Ed Cogburn wrote: > > > > > With 2.2, the config of sound drivers occurs outside the kernel > > config. You can no longer build the sound modules into the > > kernel, they must be built as modules. With sb16, for example I > > need a config line like: > > > > options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 > > > > in /etc/modules.conf. > > The above doesn't apply to 2.0 kernels, so your problem might not > > be related to configuration of the sound module. If you are using > > a 2.2 kernel then see /usr/src/linux/Documentation/Introduction. > > > > Isn't it just the opposite? Under 2.0, I've always configured and compiled > the sound module separately, but when I used Slackware 3.0, the kernel > (v2.0.27) shipped with it had the SB driver compiled in, although I never > succeeded in configuring the sound driver in the kernel config. Under 2.2, > there's no opportunity for configuring and/or compiling the sound module > on its own, it's just like any other standard kernel driver. Too bad that > I couldn't get it working with my AD1848-based Aztech card, nor could I > compile the old driver for 2.2, so I'm still back on 2.0.37. > > Andras First of all, if anyone noticed, the Intro file I referred to above is actually in /usr/src/linux/Documentation/sound/Introduction. ^ Now, Hamori, you can still compile sound as a module or into the kernel with 2.2. What's changed is that, *if you compile as a module*, you can't configure the module in the kernel config (make menuconfig). The module must be configured either at the time its loaded (insmod sb ) or in /etc/modules.conf. Under the sound section of the kernel config, I can select 'Sound Card Support' as a module (sound.o), followed by 'OSS sound modules' as a module (soundcore.o?), followed by '100% Sound Blaster compatibles', again as a module (sb.o). You just can't *configure* them at this time (as explained above - this is whats changed since 2.0). I know nothing about the Aztech cards, sorry. HTH -- Ed C.
Re: Sound Board
Bob Nielsen wrote: > > On Mon, 22 Mar 1999, steven walsh wrote: > > > On Mon, 22 Mar 1999, Ed Cogburn wrote: > > > > > > With 2.2, the config of sound drivers occurs outside the kernel > > > config. You can no longer build the sound modules into the > > > kernel, they must be built as modules. With sb16, for example I > > > need a config line like: > > > > > > options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 > > > > It does? I did it all in "make menuconfig" and it worked fine. > > Yes, using 2.2.x > > The configuration of sound AS A MODULE has changed. It is still valid to > compile sound support into the kernel (except possibly for PnP sound > cards). > > Bob I went back and looked at menuconfig, and Bob's right. I don't know how I got it so screwed up. Anyway, when building the drivers as *modules* you don't get the opportunity to set the config options (irq,dma,etc). The config stuff is either put in 'modules.conf' or provided on the command line that loads the module, ie, "insmod sb ". When compiling into the kernel, nothing has changed. Sorry about the mistake. -- Ed C.
Re: Sound Board
On Mon, 22 Mar 1999, Ed Cogburn wrote: > > With 2.2, the config of sound drivers occurs outside the kernel > config. You can no longer build the sound modules into the > kernel, they must be built as modules. With sb16, for example I > need a config line like: > > options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 > > in /etc/modules.conf. > The above doesn't apply to 2.0 kernels, so your problem might not > be related to configuration of the sound module. If you are using > a 2.2 kernel then see /usr/src/linux/Documentation/Introduction. > Isn't it just the opposite? Under 2.0, I've always configured and compiled the sound module separately, but when I used Slackware 3.0, the kernel (v2.0.27) shipped with it had the SB driver compiled in, although I never succeeded in configuring the sound driver in the kernel config. Under 2.2, there's no opportunity for configuring and/or compiling the sound module on its own, it's just like any other standard kernel driver. Too bad that I couldn't get it working with my AD1848-based Aztech card, nor could I compile the old driver for 2.2, so I'm still back on 2.0.37. Andras
Re: Sound Board
On Mon, 22 Mar 1999, Bob Nielsen wrote: > The configuration of sound AS A MODULE has changed. It is still valid to > compile sound support into the kernel (except possibly for PnP sound > cards). > Indeed. If you specific PNP support I haven't had any problems, though the default IRQ in the config menu for the sb16 pnp was wrong. Easily fixed.
Re: Sound Board
On Mon, 22 Mar 1999, steven walsh wrote: > On Mon, 22 Mar 1999, Ed Cogburn wrote: > > > > With 2.2, the config of sound drivers occurs outside the kernel > > config. You can no longer build the sound modules into the > > kernel, they must be built as modules. With sb16, for example I > > need a config line like: > > > > options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 > > It does? I did it all in "make menuconfig" and it worked fine. > Yes, using 2.2.x The configuration of sound AS A MODULE has changed. It is still valid to compile sound support into the kernel (except possibly for PnP sound cards). Bob Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen
Re: Sound Board
On Mon, 22 Mar 1999, Ed Cogburn wrote: > > With 2.2, the config of sound drivers occurs outside the kernel > config. You can no longer build the sound modules into the > kernel, they must be built as modules. With sb16, for example I > need a config line like: > > options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 It does? I did it all in "make menuconfig" and it worked fine. Yes, using 2.2.x "See you on the flip side" - Steve Walsh (EfNet:#Babylon5:KnaraKat) ([EMAIL PROTECTED])
Re: Sound Board
Petru NOTINGHER wrote: > > -- > > Subject: Re: Sound Board > Date: Mon, 22 Mar 1999 16:44:34 +0100 > From: Petru NOTINGHER <[EMAIL PROTECTED]> > Organization: LEM /UM 2 > To: [EMAIL PROTECTED] > References: <[EMAIL PROTECTED]> > > [EMAIL PROTECTED] wrote: > > > What sound driver are you using? OSS (comes with kernel) or ALSA? > > I'm using OSS. What's ALSA ? Is that the manufacturer's driver ? ALSA = Advanced Linux Sound Architexture. Take a look at "http://alsa.jcu.cz/intro.html";. ALSA will become a replacement for OSS in the future at some point. > > > Also, do > > you have sound compiled in, or as module? Kernel version would help too. > > I tried both, but none worked. Now I'm using the compiled version. > I tried on 2.00.36 and now on 2.2.1. With 2.2, the config of sound drivers occurs outside the kernel config. You can no longer build the sound modules into the kernel, they must be built as modules. With sb16, for example I need a config line like: options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 in /etc/modules.conf. The above doesn't apply to 2.0 kernels, so your problem might not be related to configuration of the sound module. If you are using a 2.2 kernel then see /usr/src/linux/Documentation/Introduction. > > Thank you for your help. > > Petru -- Ed C.
Re: Sound Board
--- Begin Message --- [EMAIL PROTECTED] wrote: > What sound driver are you using? OSS (comes with kernel) or ALSA? I'm using OSS. What's ALSA ? Is that the manufacturer's driver ? > Also, do > you have sound compiled in, or as module? Kernel version would help too. I tried both, but none worked. Now I'm using the compiled version. I tried on 2.00.36 and now on 2.2.1. Thank you for your help. Petru --- End Message ---
Sound Board
Hello. I'm trying to make an ALS 100 Sound Device to work on a Linux machine. Apparently, the card is recognized as a full-compatible SoundBlaster 16 card at the boot time, and that is what it is. The proc/dma and /proc/interrupts show it, but the /dev/sndstat and the/dev/tkmixer are not created. Consequently, I can't play audio files. I can only use the card to play Audio CDs. Can anybody help me ? Thanks.
