Date: Mon, 17 Nov 1997 22:44:22 -0000 (GMT) From: Conrad Sabatier <conrads@neosoft.com> To: Randall Hopper <rhh@ct.picker.com> Cc: multimedia@FreeBSD.ORG Subject: Re: AWE 64 MIDI config -- I'm lost Message-ID: <XFMail.971117224422.conrads@neosoft.com> In-Reply-To: <19971117211344.55386@ct.picker.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18-Nov-97 Randall Hopper wrote: > Conrad Sabatier: > |OK, I'm *finally* getting my system to recognize my AWE 64, thanks to > |Luigi's Pnp patches, and /dev/audio is working fine (Voxware). Even have > |the Real Audio player working (yay!). But... > > Good deal. Yes, indeed! > |MIDI is driving me nuts. I get no sound from playmidi, or it hangs my > |system > |altogether. Installed the awedrv package from Randall Hopper, rebuilt my > |kernel, but still no luck; AWE32 is not found at bootup. Compiled the > > I suspect this might be PnP biting. To my knowledge, all the AWE64s are > PnP. Hardware wise, they're virtually identical to the AWE32. My non-PnP > 32 detects OK. What I'm wondering about is: in the awe_detect* code, I see it looks like we're looking for a certain "signature" at certain addresses, otherwise the awe device is reorted as not found. Could it be that these signatures differ between the AWE32 and 64? I just yetserday downloaded all the docs I could find from Creative's site. Haven't had time to look at it yet, but will. They did describe it as having some info on detection. We'll see. > |Could someone please tell me what I'm doing wrong as far as MIDI? I am *so > |close* to getting this card fully functional (at last), and am anxious to > be > |able to download and play MIDI files. > > Ok, looks like you have some conflicts below: > > |Relevant kernel config section: > | > |options SBC_IRQ=5 > | > |# Controls all sound devices > |controller snd0 > |device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr > |device sbxvi0 at isa? drq 5 > |device sbmidi0 at isa? port 0x330 > |device awe0 at isa? port 0x620 > | > |# For normal case use next line > |device opl0 at isa? port 0x388 > > |device mpu0 at isa? port 0x330 irq 5 conflicts drq 0 > |device uart0 at isa? port 0x330 irq 5 conflicts vector "m6850intr" > ^^^^^^^^^^^^^^^^^^^^^^^^^ > These two lines conflict with sbmidi0. Comment them out. Did that. Still no detection. I've actually thought of just having the detection routines automatically return "true". Would that work? Would the driver then be installed/configured properly? I'm using the default addresses for everything. > As a base starting point, use my kernel lines from below (i.e. comment out > mpu0 and uart0, etc.) > > And if you "do" have another board in your system sitting on port 330, > remove it for now. The Sound Blaster owns this MIDI port--could be the > reason you're locking up your system trying to play MIDIs via the SB FM > synth. I suspect this is what's still causing the problem. My motherboard has a built-in Crystal 4342 chip, and there are no jumpers or BIOS switches to disable it. It *seems* like Luigi's code effectively "turns it off"; I'm using "os disable" on all card 1 devices, and I *am* getting audio from all the other SB devices (which, if the Crystal were enabled, would be causing some major conflicts). > |# Not controlled by `snd' > |device pca0 at isa? port IO_TIMER1 tty > > Should be OK. I've got the same line in mine. > > |OK, good. Yes, timidity works great, and is a fine solution until I > |figure out how to get the AWE wave stuff going. But shouldn't playmidi > |work with my OPL? > > Yes. > > Good luck! > > Randall > > > ----- > > With these lines in your kernel config: > > controller snd0 > device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr > device sbxvi0 at isa? drq 5 > device sbmidi0 at isa? port 0x330 > # Yamaha OPL-2/OPL-3 FM - for SB, SB Pro, SB16, PAS > device opl0 at isa? port 0x388 > device awe0 at isa? port 0x620 Exactly what I have, I'm pretty sure (will check). > You should be able to get cheesy OPL MIDI through opl0 via: > playmidi -4 symphony.mid > > I don't recommend this except as a test though. :-) > > For FM, subst -f for -4. For AWE (with playmidi from the AWE page), subst > -a. But for far-and-away better quality, definitely use drvmidi once you > get the AWE synth part of the card detecting correctly. Thanks for the advice about the switches. Missed the -a somehow. Frankly, I'm about ready to try the solution someone propsed a while back: get out the Exacto knife and kill the fu**ing Crystal! :-) But not until we've exhausted all other possibilities, of course. :-) Oh, one quick question: if I do somehow get everything configured properly, will the AWE driver show up in a cat /dev/sndstat? Thanks so much for your time! -- Conrad Sabatier http://www.neosoft.com/~conrads And the Deep Thought of the Day (tm) is: If you're not part of the solution, you're part of the precipitate.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.971117224422.conrads>