From: Helge Hafting <helgehaf@aitel.hist.no>
To: 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 20:41:59 +0200 [thread overview]
Message-ID: <20040626184159.GA20447@hh.idb.hist.no> (raw)
In-Reply-To: <20040626154534.GF16916@washoe.rutgers.edu>
On Sat, Jun 26, 2004 at 11:45:34AM -0400, Yaroslav Halchenko wrote:
> 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?
>
Remember, you're not the only linux user in the world. :-)
If everybody with trouble complain, then they get enough complaints
that it matters. It doesn't work if everybody thinks the're alone
and do nothing. Note that linux is the fastest growing OS these days.
You can also let them know before you purchase. When getting your next
machine, consider one that claims linux support. They exist - even
laptops. And if you get something else, let them know. If you
inquire about a machine - ask about linux support. Salesmen getting
a lot of that will take note. The linux market isn't the biggest
but cutting off 5%/10% of the market for no reason is bad business.
Linux support is easy - they don't have to do support, just sell
a box that works.
Bring a knoppix CD when looking at machines in shops - then you
can verify that they work without obvious snags like that mtrr bug.
> 'BIOS errornessly fills Memory Type Range Registers with too many
> memory ranges with wrong caching strategies' is it what is happening?
>
About how to complain - be constructive. Tell them that the problem is
serious and makes the machine work much slower than the competition,
but that it is easily fixable by setting the mtrr's up right in the bios.
You may also want to tell them that several other vendor have had
this problem - and fixed it by issuing a bios upgrade.
> > Also check if there is a newer BIOS around. :-)
> that might be usefull :-)
Helge Hafting
prev parent reply other threads:[~2004-06-26 18:39 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
2004-06-26 18:41 ` Helge Hafting [this message]
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=20040626184159.GA20447@hh.idb.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=yoh@psychology.rutgers.edu \
/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®