Re: Kernel 2.2.9 and soundblaster module
Brad wrote: On Tue, 15 Jun 1999, Ingo Hohmann wrote: Hi, is there something about soundblaster support that I should have known by now? Seems that my irq, ... settings get lost when I compile soundblaster support as a module. (Sound works when compiled in, but I get device is busy error, when I use modules and try to insmod sb.o) Is there a possibilty to set irq, ... when using modules? Or is it another problem? When you insert the sb module, you have to specify the io, irq, etc on the command line, something like this: insmod sb io=0x220 irq=9 dma=1 dma16=5 mpu_io=0x300 type=6 Same thing when you insmod the adlib_card for midi support: insmod adlib_card io=0x388 On my system, i put a script in /etc/init.d to automatically insert the proper sound modules on boot (after isapnp runs and configures the card) Brad, man modconf - does that for you. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Confession is good for the soul only in the sense that a tweed coat is good for dandruff. --Peter de Vries http://www.skunkpussy.freeserve.co.uk - Drum'n'Bass music, samples and links. ICQ://25576761 begin:vcard n:;Frankie x-mozilla-html:TRUE adr:;; version:2.1 email;internet:[EMAIL PROTECTED] note:Trainee Linux Guru x-mozilla-cpt:;0 fn:Frankie end:vcard smime.p7s Description: S/MIME Cryptographic Signature
Re: Kernel 2.2.9 and soundblaster module
On Fri, 18 Jun 1999, Frankie wrote: Brad wrote: On my system, i put a script in /etc/init.d to automatically insert the proper sound modules on boot (after isapnp runs and configures the card) Brad, man modconf - does that for you. How about man i-don't-have-the-time-to-break-something-that-works-perfectly-fine-for-me-as-is? Besides, the only reason i don't compile sound directly into the kernel is that i have to use isapnp to configure the card. So it's not much of a loss for me to just insert the modules once at boot.
Re: Kernel 2.2.9 and soundblaster module
Brad wrote: [snip] On my system, i put a script in /etc/init.d to automatically insert the proper sound modules on boot (after isapnp runs and configures the card) Brad, would you mind sharing your script? I took a loot at those in init.d (most specifically that of xfstt) and I think I need some guidance before I try to write my own. tia -- __ _ Mark Wagnon Debian GNU/ -o) / / (_)__ __ __ Chula Vista, CA /\\/ /__/ / _ \/ // /\ \/ / [EMAIL PROTECTED] _\_v/_/_//_/\_,_/ /_/\_\ http://www.debian.org
Re: Kernel 2.2.9 and soundblaster module
Brad [EMAIL PROTECTED] writes: On Tue, 15 Jun 1999, Ingo Hohmann wrote: Hi, is there something about soundblaster support that I should have known by now? Seems that my irq, ... settings get lost when I compile soundblaster support as a module. (Sound works when compiled in, but I get device is busy error, when I use modules and try to insmod sb.o) Is there a possibilty to set irq, ... when using modules? Or is it another problem? When you insert the sb module, you have to specify the io, irq, etc on the command line, something like this: insmod sb io=0x220 irq=9 dma=1 dma16=5 mpu_io=0x300 type=6 Same thing when you insmod the adlib_card for midi support: insmod adlib_card io=0x388 On my system, i put a script in /etc/init.d to automatically insert the proper sound modules on boot (after isapnp runs and configures the card) You may also put those informations inside the file /etc/modutils/aliases and have the module automatically loaded when an access to the sound devices is made. Here what I have in my /etc/modutils/aliases for the sound system: alias sound sb options sound dmabuf=1 post-install sb /sbin/modprobe -k adlib_card options sb io=0x220 irq=6 dma=1 dma16=5 mpu_io=0x330 options adlib_card io=0x388 # FM synthesizer Chris -- Looking for a cutting edge | Christophe Broult software validation technology? | mailto:[EMAIL PROTECTED] Check http://www.info.unicaen.fr/lpv | ``Smile, chuckle, giggle''
RE: Kernel 2.2.9 and SoundBlaster module
On Wednesday, June 16, 1999 10:42 PM, Mark Wagnon [SMTP:[EMAIL PROTECTED] wrote: Brad wrote: On my system, i put a script in /etc/init.d to automatically insert the proper sound modules on boot (after isapnp runs and configures the card) would you mind sharing your script? I took a loot at those in init.d (most specifically that of xfstt) and I think I need some guidance before I try to write my own. I hate to poke in like this, and I am not an authoritative source, but isn't this the wrong way to go about it? The following is what I gleaned from the docs- could someone please tell me if I'm doing this in a way that will get hosed when I do Debian updates? /etc/modules: (added these lines to existing file) sound uart401 sb awe_wave /etc/modutils/soundblaster (new file I added) options sound dmabuf=1 options sb io=0x220 irq=5 dma=1 dma16=5 Then run update-modules, which goes through the /etc/modutils directory to build up the /etc/conf.modules file. Thanks! Jonathan
Re: Kernel 2.2.9 and soundblaster module
On Wed, 16 Jun 1999, Mark Wagnon wrote: Brad wrote: [snip] On my system, i put a script in /etc/init.d to automatically insert the proper sound modules on boot (after isapnp runs and configures the card) Brad, would you mind sharing your script? I took a loot at those in init.d (most specifically that of xfstt) and I think I need some guidance before I try to write my own. No problem, although my script probably isn't a model you'll want to follow ;) /etc/init.d/skeleton would be a better model for just about every case you'll need. Also, there's a bit of redundancy here. I call isapnp, but the isapnptools package installs a script (run before this one) that does the same. I could probably then delete that line, i just need to get the time to test it... Ditto for changing some of those insmods to modprobes; when i wrote the script i didn't know how to use modprobe, and after that i didn't want to break something that worked. As a final note, i redirect all error messages to /dev/null. Works ok for me for this script, YMMV. #!/bin/sh case $1 in start) echo -n Setting up sound card... # Plug n Play config isapnp /etc/isapnp.conf 2 /dev/null # Install basic sound modules insmod soundcore 2 /dev/null insmod sound 2 /dev/null # init'ize uart thing, because sb needs it insmod uart401 2 /dev/null # Set up the actual sound card! Pulled numbers out of /etc/isapnp.conf insmod sb io=0x220 irq=9 dma=1 dma16=5 mpu_io=0x300 type=6 2 /dev/null # Midi support. Note that this automatically loads opl3.o as well modprobe adlib_card io=0x388 2 /dev/null echo Done. esac exit 0
RE: Kernel 2.2.9 and SoundBlaster module
On Thu, 17 Jun 1999, Jonathan Lupa wrote: On Wednesday, June 16, 1999 10:42 PM, Mark Wagnon [SMTP:[EMAIL PROTECTED] wrote: Brad wrote: On my system, i put a script in /etc/init.d to automatically insert the proper sound modules on boot (after isapnp runs and configures the card) would you mind sharing your script? I took a loot at those in init.d (most specifically that of xfstt) and I think I need some guidance before I try to write my own. I hate to poke in like this, and I am not an authoritative source, but isn't this the wrong way to go about it? Probably (: The way i did it may not be the Right Thing, but i personally haven't had any troubles. YMMV.
Kernel 2.2.9 and soundblaster module
Hi, is there something about soundblaster support that I should have known by now? Seems that my irq, ... settings get lost when I compile soundblaster support as a module. (Sound works when compiled in, but I get device is busy error, when I use modules and try to insmod sb.o) Is there a possibilty to set irq, ... when using modules? Or is it another problem? Thank you, Ingo Hohmann -- _ _ ingo@)|_ /| _| _ We ARE all ONE www._|_o _ _ ._ _ www./_|_) |o(_|(/_ We ARE all FREE ingo@| |(_|o(_)| (_| _| _|
Re: Kernel 2.2.9 and soundblaster module
Ingo Hohmann wrote: Hi, is there something about soundblaster support that I should have known by now? Seems that my irq, ... settings get lost when I compile soundblaster support as a module. (Sound works when compiled in, but I get device is busy error, when I use modules and try to insmod sb.o) Is there a possibilty to set irq, ... when using modules? Or is it another problem? Did you add some entries to your /etc/modules.conf file? I have the following added to the bottom: alias sound sb alias midi awe_wave post-install awe_wave /usr/bin/sfxload /usr/synthfm.sbk options sb io=0x240 irq=9 dma=1 dma16=7 mpu_io=0x300 and I do a modprobe sb to get sound going. Setting up sound has been extremely frustrating, but I managed to get it going. I've been happily playing CDs since Sunday :) Also, have you looked at AWE32 and README.awe in the Documentation/Sound directory? The info they contained (referring to my addition to /etc/modules.conf) was what I needed to finaly get sound going. I had my isapnp.conf file and my kernel ready to go, but until I added those four lines, I couldn't get sound. hth -- __ _ Mark Wagnon Debian GNU/ -o) / / (_)__ __ __ Chula Vista, CA /\\/ /__/ / _ \/ // /\ \/ / [EMAIL PROTECTED] _\_v/_/_//_/\_,_/ /_/\_\ http://www.debian.org
Re: Kernel 2.2.9 and soundblaster module
On Tue, 15 Jun 1999, Ingo Hohmann wrote: Hi, is there something about soundblaster support that I should have known by now? Seems that my irq, ... settings get lost when I compile soundblaster support as a module. (Sound works when compiled in, but I get device is busy error, when I use modules and try to insmod sb.o) Is there a possibilty to set irq, ... when using modules? Or is it another problem? When you insert the sb module, you have to specify the io, irq, etc on the command line, something like this: insmod sb io=0x220 irq=9 dma=1 dma16=5 mpu_io=0x300 type=6 Same thing when you insmod the adlib_card for midi support: insmod adlib_card io=0x388 On my system, i put a script in /etc/init.d to automatically insert the proper sound modules on boot (after isapnp runs and configures the card)
