public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frisch <mfrisch@saturn.tlug.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up
Date: 12 Aug 2001 23:08:38 -0400	[thread overview]
Message-ID: <997672119.956.3.camel@frisch> (raw)
In-Reply-To: <3B772126.F23DB1D7@randomlogic.com>
In-Reply-To: <20010812155520.A935@ulthar.internal.mclure.org> <Pine.LNX.4.33.0108121557060.2102-100000@penguin.transmeta.com> <20010812161544.A947@ulthar.internal.mclure.org>  <3B772126.F23DB1D7@randomlogic.com>

On 12 Aug 2001 17:36:54 -0700, Paul G. Allen wrote:
> Call me dumb, but what was wrong with the SB Live! code in the 2.4.7
> trees? Mine works fine and has since I first installed RH 7.1 on this
> system. The only problem I had was when I compiled it into the kernel
> (instead of compiling as a module), sound would not work and I could not
> configure it with sndconfig.

While the SB Live! code seemed to work flawlessly on my Intel BX board,
since moving to the A7A266 (ALi MaGiK based), I am pretty much convinced
it has been the cause of my intermittent lockup problems.  Without the
emu10k1 driver loaded, I cannot get the machine to lockup and everytime
it has locked up the sound card has been in use.

Right now, I am running the ALSA driver (as somebody else had
mentioned), but not enough yet to know if it's going to cause a problem.

Mike.


  parent reply	other threads:[~2001-08-13  3:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-12  2:52 Hang problem on Tyan K7 Thunder resolved -- SB Live! heads-up Eric S. Raymond
     [not found] ` <997611708.29909.22.camel@DESK-2>
2001-08-12 10:23   ` Jeffrey Ingber
2001-08-12 12:04     ` Alan Cox
2001-08-12 18:31       ` Manuel McLure
2001-08-12 20:15         ` Alan Cox
2001-08-12 20:30           ` Nerijus Baliunas
2001-08-13  3:27             ` Robert Love
2001-08-12 20:35           ` Manuel McLure
2001-08-12 21:59             ` Manuel McLure
2001-08-12 22:24             ` Linus Torvalds
2001-08-12 22:55               ` Manuel McLure
2001-08-12 22:59                 ` Linus Torvalds
2001-08-12 23:15                   ` Manuel McLure
2001-08-13  0:36                     ` Paul G. Allen
2001-08-13  1:39                       ` Justin A
2001-08-13  3:08                       ` Mike Frisch [this message]
2001-08-13  1:00                     ` Linus Torvalds
2001-08-13  1:33                       ` Paul G. Allen
2001-08-13  1:50                         ` Nicholas Knight
2001-08-12 22:10           ` Linus Torvalds
2001-08-12 22:18             ` Alan Cox
2001-08-12 22:21               ` Dax Kelson
2001-08-12 22:31               ` Linus Torvalds
2001-08-16 23:28               ` Pavel Machek
2001-08-17 20:33                 ` Alan Cox
2001-08-13 11:08           ` rui.p.m.sousa
     [not found] <no.id>
2001-08-12 22:30 ` Alan Cox
2001-08-13 12:16 ` Alan Cox
2001-08-13 12:19   ` rui.p.m.sousa
2001-08-13 12:19 ` Alan Cox
2001-08-13 12:35 ` Alan Cox
2001-08-13 12:43   ` Tobias Ringstrom
2001-08-13 12:47 ` Anton Altaparmakov
  -- strict thread matches above, loose matches on Subject: below --
2001-08-13 18:53 Ryan C. Bonham
2001-08-13 18:58 ` Daniel T. Chen
2001-08-13 18:54 Anton Altaparmakov
2001-08-13 19:11 Ryan C. Bonham

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=997672119.956.3.camel@frisch \
    --to=mfrisch@saturn.tlug.org \
    --cc=linux-kernel@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