From: Mike Dresser <mdresser@windsormachine.com>
To: Joel Franco Guzmán <joel@gds-corp.com>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble
Date: Thu, 18 Jan 2001 09:40:56 -0500 [thread overview]
Message-ID: <3A670078.E8DF3229@windsormachine.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0101172037310.1309-100000@thor.gds-corp.com>
Sorry if this has been asked of you before, but what happens if you put just
the 64 meg module in?
> Bug Report
> ----------
> 1. 128M memory OK, but with 192M the sound card generate a noise while
> use the DSP.
> 2. i got the problem when I just put more 64M memory to the my machine.
> With 128M the problem is not present, but with 192M it is. The only
> difference is the memory quantity, or in other words, the additional slot
> occupied by the new memory card.
My instinct is the pc100 ram being run at 133. Sometimes you get away with
it(my pre-ratings, but supposed to be pc66 - hyundai ram runs at 100 just
fine, but won't go any higher), and maybe your new 64 megger can't do it.
Mike Dresser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-18 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 23:11 PROBLEM: 128M memory OK, but with 192M sound card es1391 trouble Joel Franco Guzmán
2001-01-17 23:25 ` J . A . Magallon
2001-01-17 10:36 ` Josh Myer
2001-01-18 11:15 ` J . A . Magallon
2001-01-18 14:31 ` Joel Franco Guzmán
2001-01-18 10:02 ` Stefan Ring
2001-01-18 15:34 ` Joel Franco Guzmán
2001-01-18 15:58 ` Stefan Ring
2001-01-18 18:14 ` Mike Galbraith
2001-01-18 14:40 ` Mike Dresser [this message]
2001-01-18 15:30 ` Joel Franco Guzmán
2001-01-21 20:17 ` Gregory McLean
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=3A670078.E8DF3229@windsormachine.com \
--to=mdresser@windsormachine.com \
--cc=joel@gds-corp.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