mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bruce Harada <bruce@ask.ne.jp>
To: NyQuist <NyQuist@ntlworld.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nm256_audio.o
Date: Wed, 13 Feb 2002 01:14:05 +0900	[thread overview]
Message-ID: <20020213011405.4f9f3c41.bruce@ask.ne.jp> (raw)
In-Reply-To: <1013529735.9204.23.camel@stinky.pussy>
In-Reply-To: <1013529735.9204.23.camel@stinky.pussy>

On 12 Feb 2002 16:02:15 +0000
NyQuist <NyQuist@ntlworld.com> wrote:

> Hi
> I've a problem with this module. For some reason it locks up my laptop
> when modprobed. I'm running redhat's 2.4.7-10 on an i686 and i'm using
> the neomagic 256 chipset which I believe is a graphics/sound combination
> (with 4 meg or so of mem), the comp is a dell latitude ls.
> The card does work, as it runs under the commercial oss drivers, thing
> is because the machine locks tight running the kernel 256_audio, I can't
> get any debug information, the machine has to be physically
> unplugged/debatteried (lucky I run ext3 :) Not even a messages error. 
> Anyone with any info? I'm gonna have a look and try to debug, but i'm no
> kernel hacker.

A vague memory of when I used to use a neomagic-based laptop tells me that you
might want to try giving lilo (or whatever bootmanager you're using) a
parameter to limit your memory to 1MB less than your actual memory... although
this is from way back in 2.2.[789] days, I think. (For lilo, that would mean
typing mem=xxxM or adding append="mem=xxxM" to /etc/lilo.conf, where xxx is
your total RAM minus 1.)

  reply	other threads:[~2002-02-12 16:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12 16:02 nm256_audio.o NyQuist
2002-02-12 16:14 ` Bruce Harada [this message]
2002-02-12 16:31 ` nm256_audio.o NyQuist
2002-02-12 17:24   ` nm256_audio.o Alan Cox
2002-02-12 20:18     ` nm256_audio.o Pedro M. Rodrigues

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=20020213011405.4f9f3c41.bruce@ask.ne.jp \
    --to=bruce@ask.ne.jp \
    --cc=NyQuist@ntlworld.com \
    --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

all inboxes | Powered by JetHome®