Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 May 1996 18:22:13 +0200
From:      "Christoph P. Kukulies" <kuku@gilberto.physik.rwth-aachen.de>
To:        multimedia@freebsd.org
Subject:   snd in -current, vmix, misc
Message-ID:  <199605121622.SAA27809@gilberto.physik.rwth-aachen.de>

next in thread | raw e-mail | index | archive | help

I compiled a -current kernel with snd01041996-2.2-current.tgz:

VoxWare Sound Driver:3.5-alpha7-951119 (Thu Jan  4 01:09:01 PST 1996 Amancio Hasty@rah.star-gate.com)
Config options: 188090a

Installed drivers: 
Type 4: Gravis Ultrasound


Card config: 
Gravis Ultrasound at 0x220 irq 12 drq 1,3

Audio devices:
0: Gravis UltraSound (DUPLEX)

Synth devices:
0: Gravis UltraSound 3.7 (512k)

Midi devices:
0: Gravis UltraSound Midi

Timers:
0: System clock
1: GUS

Mixers:
0: ICS2101 Multimedia Mixer

When I do a 

cat some.au >/dev/audio
I'm getting:

May 12 18:06:42 isdn-kukulies /kernel: isa_dmastart: channel 1 busy
and continously the message 'isa_dmastart: channel 1 busy' on the screen.

What's the cause of this?

What is the 'standard' way to control the volume of mic and speaker?
Is it still vmix or are there other tools. The vmix I have uses
/tmp/vatsock btw which might not be appropriate.

Starting vat 4.0a8 gives the same above message for channel 3:
May 12 18:15:38 isdn-kukulies /kernel: isa_dmastart: channel 3 busy
May 12 18:15:38 isdn-kukulies /kernel: isa_dmastart: channel 3 busy

Can someone enlighten me? thanks.


--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de







Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605121622.SAA27809>