Linux Sound subsystem development
 help / color / mirror / Atom feed
From: benoit.rouits@lemel.fr (Benoit Rouits)
To: linux-sound@vger.kernel.org
Subject: GUS MAX problem
Date: Sun, 06 Dec 1998 02:19:33 +0000	[thread overview]
Message-ID: <marc-linux-sound-91295518418565@msgid-missing> (raw)

Hello,
(I'm not subscribed, please use reply)

I've got a problem with my 2.0.31 kernel
 and standard driver for GUS that is :

-When i use MIDI player first time, i get a segmentation fault. At the 
second time, the /dev/sequencer is said BUSY.But when i CAT foo.bar in /dev/
sequencer
, I can "hear" some midi message.(unsynchrnised of course) What's the 
problem?

- Secondly, wave sound works well but sometimes i get a big BUZZ when 
playing some file. I'm forced to reboot to get good sound again.

Any suggestion?

Thank's a lot .

P.S: My GUS MAX is an ISA one and works
 well under Micro$oft and I'm sure to not have any irq or dma conflicts.

Benoit Rouits

             reply	other threads:[~1998-12-06  2:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-06  2:19 Benoit Rouits [this message]
1998-12-07 15:35 ` GUS MAX problem Tuukka Toivonen
1998-12-07 21:38 ` Benoit Rouits
1998-12-07 21:56 ` Tuukka Toivonen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-sound-91295518418565@msgid-missing \
    --to=benoit.rouits@lemel.fr \
    --cc=linux-sound@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox