mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yaroslav Halchenko <yoh@psychology.rutgers.edu>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: Yaroslav Halchenko <yoh@psychology.rutgers.edu>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: alienware hardware - memory problem?
Date: Sat, 26 Jun 2004 11:45:34 -0400	[thread overview]
Message-ID: <20040626154534.GF16916@washoe.rutgers.edu> (raw)
In-Reply-To: <20040626120738.GB14609@hh.idb.hist.no>

On Sat, Jun 26, 2004 at 02:07:38PM +0200, Helge Hafting wrote:
> On Fri, Jun 25, 2004 at 12:20:16PM -0400, Yaroslav Halchenko wrote:
> Glad to be of help.  I hope the /proc/mtrr stuff works out, it is
> nice to use _all_ the memory?.  How much is it?
1GB RAM. I've found somewhere that guy did 'disable=X' with X for all
lines in mtrr (we have 6) and then just overrides first with 1Gb of
write-back and then some amount for video (64M for instance) with
uncachable. I just didn't have time to try yet :-) 

> Don't forget the complaint to the vendor.  The only way to get 
> permanently rid of this sort of problem is when the vendors get
> enough reactions to sloppy bioses.  Don't be silent just because
> you found a solution, you shouldn't really have to in this case.
I'm not sure if vendor would respect such complaint because alienware
supports only windows and Windows doesn't have such problem seems to me.
Anyway how to complain in the right way?

'BIOS errornessly fills Memory Type Range Registers with too many
memory ranges with wrong caching strategies' is it what is happening?

> Also check if there is a newer BIOS around. :-)
that might be usefull :-)

-- 
                                                  Yaroslav Halchenko
                  Research Assistant, Psychology Department, Rutgers
          Office  (973) 353-5440 x263
   Ph.D. Student  CS Dept. NJIT
             Key  http://www.onerussian.com/gpg-yoh.asc
 GPG fingerprint  3BB6 E124 0643 A615 6F00  6854 8D11 4563 75C0 24C8


  reply	other threads:[~2004-06-26 15:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 19:10 alienware hardware Yaroslav Halchenko
     [not found] ` <200406242315.56213.vda@port.imtp.ilyichevsk.odessa.ua>
2004-06-24 20:26   ` Yaroslav Halchenko
     [not found]     ` <200406242358.55782.vda@port.imtp.ilyichevsk.odessa.ua>
2004-06-24 21:09       ` Yaroslav Halchenko
2004-06-24 21:26       ` Yaroslav Halchenko
2004-06-24 21:58         ` Yaroslav Halchenko
2004-06-25  0:01           ` alienware hardware - memory problem? Yaroslav Halchenko
2004-06-25  8:54             ` Helge Hafting
2004-06-25 16:20               ` Yaroslav Halchenko
2004-06-26 12:07                 ` Helge Hafting
2004-06-26 15:45                   ` Yaroslav Halchenko [this message]
2004-06-26 18:41                     ` Helge Hafting

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=20040626154534.GF16916@washoe.rutgers.edu \
    --to=yoh@psychology.rutgers.edu \
    --cc=helgehaf@aitel.hist.no \
    --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®