From owner-freebsd-multimedia Sat Apr 20 1:58: 3 2002 Delivered-To: freebsd-multimedia@freebsd.org Received: from mk-smarthost-3.mail.uk.tiscali.com (mk-smarthost-3.mail.uk.tiscali.com [212.74.112.73]) by hub.freebsd.org (Postfix) with ESMTP id 8FE3D37B405; Sat, 20 Apr 2002 01:57:49 -0700 (PDT) Received: from [80.225.35.127] (helo=lineone.net) by mk-smarthost-3.mail.uk.tiscali.com with esmtp (Exim 3.35 #1) id 16yqbY-0009fC-00; Sat, 20 Apr 2002 09:52:25 +0100 Message-ID: <3CC12D6B.DFACE1A@lineone.net> Date: Sat, 20 Apr 2002 09:57:15 +0100 From: Jean-Mark Dupoux X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: questions@freebsd.org, multimedia@freebsd.org Subject: Re: Kernel config parameters for soundcard - 4.4 rel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I really should have mentioned that I had to go back to the old device snd build to get full use out of this Aztech Sound Galaxy in the end, for the benefit of anyone setting up similar hardware. It beats me exactly why, but when I compiled with: device pcm device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x10 the card was recognised easily enough and loaded up as a soundblaster pro, but would only play .AU files reliably. Wav's were still thowing up errors with: sb_dspwr(0x40) timed out and so on So after switching back to this build: device snd device sb0 at isa? port 0x220 irq 5 drq 1 flags 0x10 device opl3 at isa? port 0x388 device joy0 at isa? port 0x200 wav files and au files played equally well. I still have no mixer to set volumes and so forth, and the same still holds true though about having to boot DOS first and reset with ctrl-alt-del just to get the card running at all. I may look into running DOS commands somehow directly from inside freebsd to see if using the original utilities is an option for command line mixer settings jmdupoux_@_lineone.net --------------- Original Message ------------------- Ok, this one is solved - it was a hardware issue, in as much as the card only works after a boot into DOS and then a soft-reset. I think otherwise the EEPROM chip on the card doesn't get initialized (module in config.sys) and it's as good as dead. Works fine and loads up like a SB pro after all, 16-bit on this card only works with MSS mode Thanks for all the input, I'll look out for the additions to the new driver jmdupoux_@_lineone.net John Utz wrote: > > Hi; > > On Fri, 19 Apr 2002 jmdupoux@lineone.net wrote: > > > ok, when I looked at man and the handbook the impression was that sbc > > was typically suited for some specific compatible chipsets, while sb or > > csa for example targeted others. > > not quite. the man page is a tad out of date. so you shouldnt take it to > be a full list. sbc is a bridge driver for things that know how to act > like an SB16. > > > But anyhow, now I've tried a build with sbc there still seems to be one > > or two problems > > > > it still looks like no mixer is being created, only one device created > > pcm0: at io 0x220 irq 5 drq 1 (1p, 1w, 1v channels) > > only gonna be one device. you have succeeded. so far :-) > recall that the other things midi, opl, etc dont work yet. > > > and the response from trying to play a file is not a sound output: > > > > sb_dspwr(0x40) timed out. > > sb_dspwr(0x40) timed out. > > sb_dspwr(0x40) timed out. > > sb_dspwr(0x40) timed out. > > > > before returing to the prompt, in complete silence > > oh. that's looking broken. :-( > > and upon reflection, the device string isnt looking good either. i'll ssh > into my box at home later, but i think that the SB dsp 3.01 isnt what i > would expect to see for the string, i'd expect a manufacturer's name. > > did you try just using pcm *without* sbc? we may be working too hard...pcm > may already know how to attach to your hardware already. > > > entering mixer by itself at the prompt gives me a list of current > > settings, all at zero, but any attempt to run for example mixer vol 10 > > returns mixer: MIXER_WRITE: Device not configured > > did you do a MAKEDEV? > > su to root, cd /dev and do an > > sh MAKEDEV snd0 > > and go back to being a normal user > > then do a > > cat /dev/sndstat > > and see what you get. then try mixer and see what you get. > > > still stumped > > were making progress tho..... > > > jmdupoux_@_lineone.net > > > > > > On 19 Apr 2002 at 10:43, John Utz wrote: > > > > > yup. > > > > > > jean, you need to add a c. > > > > > > you want sbc, not sb > > > > > > the sbc device is the pcm bridge driver for soundblaster compats. > > > > > > sb is the old voxware driver for sounblaster compats. > > > > > > subtle, but crucial :-) > > > > > > On Fri, 19 Apr 2002, Andy Sparrow wrote: > > > > > > > > Ok, here's the file - I havnt changed much from generic yet since the > > > > > soundcard was pretty much the only sticking point > > > > > > > > > # Multimedia support > > > > > # Sound card - aztech audio galaxy pro II cs4231 > > > > > > > > > > device pcm > > > > ^^^^^^^^^^ > > > > > > > > Non-VOXWARE > > > > > > > > > device sb0 at isa? port 0x220 irq 5 drq 0 flags 0x11 > > > > ^^^^^^^^^^ > > > > > > > > VOXWARE. Incompatible with above (requires 'device snd'). > > > > > > > > > > > > > > > > > > > # commented trash .... > > > > > # device snd0 > > > > > # device sbmidi0 at isa? port 0x330 irq 9 > > > > > # device mss0 at isa? port 0x530 irq 7 drq 5 > > > > > # flags 0x11 > > > > > # device sbmidi0 at isa? port 0x330 irq 9 > > > > > # device opl0 at isa? port 0x388 > > > > > # device joy0 at isa? port 0x200 > > > > > # options CONFIG_SBPRO > > > > > # options __SGNXPRO__ > > > > > > > > > > > > > > -- > > > > > > John L. Utz III > > > john@utzweb.net > > > > > > Idiocy is the Impulse Function in the Convolution of Life > > > > > > > > > -- > > John L. Utz III > john@utzweb.net > > Idiocy is the Impulse Function in the Convolution of Life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message