Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!pumpkin.pangea.ca!eru.mt.luth.se!solace!nntp.uio.no!newsfeeds.sol.net!europa.clark.net!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!rill.news.pipex.net!pipex!tank.news.pipex.net!pipex!news.utell.co.uk!usenet
From: brian@shift.utell.net (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Of Mice And Multimedia
Date: 8 Apr 1997 09:38:48 GMT
Organization: Awfulhak Ltd.
Lines: 79
Message-ID: <5id3n8$8md@ui-gate.utell.co.uk>
References: <hrrbi5.ov1.ln@dolphin.neosoft.com>
Reply-To: brian@awfulhak.org, brian@utell.co.uk
NNTP-Posting-Host: shift.utell.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:38777
In article <hrrbi5.ov1.ln@dolphin.neosoft.com>,
conrads@neosoft.com (Conrad Sabatier) writes:
> I've been running up against a rather intriguing set of problems in trying
> to get a Soundblaster AWE 64 to work under FreeBSD (2.2.1). Much to my
> chagrin, I didn't realize the card was PnP when I bought it (I still have
> time to return it, and am *this close* to doing so).
>
> To be as concise as possible, it seems the only way to get FreeBSD to
> recognize it is to compile a kernel with all the sound-related IRQs, DMAs,
> etc. configured to the card's default settings:
>
> options SBC_IRQ=5
>
> 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 opl0 at isa? port 0x388
>
> Only problem is, when I do this, my PS/2-style mouse no longer works under
> X. If I use the sound defaults in LINT, the card isn't recognized.
>
> I've gone over and over this and can't figure out where the conflict is
> arising between the soundcard and mouse. Arggh!
>
I take it the mouse doesn't work at all (have you tried moused ?).
This may be a hardware thing. My machine at home should be using
*all* of the IRQs. However, the SMC 21040 PCI NIC seems not to
be able to use IRQ 15 (and I can't get the 1542c to either). The
result is that the NIC grabs, on a random basis, either IRQ 5 or
9. These IRQs are assigned to COM3 & COM4, so depending on the time
of day, I lose one of the two COM ports :(
Try examining your dmesg output - maybe one of your PCI cards
(I assume it's a PCI board) is grabbing IRQ 12 - but only if the
soundcard is around.
> I've also noticed that "cat /dev/sndstat" shows bogus IRQ and port for the
> sbxvi0, sbmidi0 and opl0 devices (65535 and <some huge number> --
> obviously, -1 in 16 and 32 bits, respectively). Should I explicitly
> declare this stuff in the config or not?
I've always put all of the SBC_ variables in my config file (it's easy
to change things without figuring out what the variable is from LINT
when you change something). I don't know if this is fixed these days
(so that it uses the stuff specified on the device line) - I havn't
looked at the code in ages, but it shouldn't do any harm.
> Any ideas would be greatly appreciated. I'd really *much* rather get this
> thing working than have to return it and get something else. It's a
> fabulous card, really.
If it's of any use, my laptop has a soundcard and a ps/2 mouse. The
sound is sb16 compat and didn't work at 0x220 - I found it at 0x240.
It probably doesn't help - I don't know how PnP it is, but here are
the config lines I use:
controller snd0
options "SBC_BASE=0x240"
options "SBC_IRQ=5"
options "SBC_DMA=1"
options "SB16_DMA=5"
options "SB16MIDI_BASE=0x330"
device sb0 at isa? port 0x240 conflicts irq 5 conflicts drq 1 vector sbintr
device sbxvi0 at isa? port 0x240 conflicts irq 5 conflicts drq 5 vector sbintr
device sbmidi0 at isa? port 0x330
> By the way, no luck at all with OSS, either.
>
> Damn Plug-and-Play! I *hate* it!
^^^^
That's "Pray"
--
Brian <brian@awfulhak.org> <brian@freebsd.org>
<http://www.awfulhak.demon.co.uk>
Don't _EVER_ lose your sense of humour !