public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] strange system behaviour.
Date: Mon, 21 May 2007 08:08:18 +0100	[thread overview]
Message-ID: <200705210808.36111.michaelkintzios@gmail.com> (raw)
In-Reply-To: <1179703004.14221.1.camel@orpheus>

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

On Monday 21 May 2007 00:16, Iain Buchanan wrote:
> On Mon, 2007-05-21 at 00:30 +0300, Nistor Andrei wrote:
> > On Monday 21 May 2007, Marek Miller wrote:
> > > Yes, it is a RAM defect. Is there a way to define upper limit of RAM,
> > > so I can perform some back-up before
> > > I take my laptop to a warranty service?
> >
> > Try badram-sources. I've never used them, but they should do the trick. I
> > think you can find them in the custom-kernels overlay.
>
> ha! good luck trying to compile the kernel with faulty RAM.  Can you
> remove one stick, or borrow some from a friend / other machine?  That
> might help with your backups...

Or, drop a Knoppix or a different more lightweight LiveCD in, do your back up 
and then take it to the warranty service?
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-21  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 20:20 [gentoo-user] strange system behaviour Marek Miller
2007-05-18  0:05 ` b.n.
2007-05-20 23:01   ` Marek Miller
     [not found]     ` <200705210030.52954.coder.tux@gmail.com>
2007-05-20 23:16       ` Iain Buchanan
2007-05-21  7:08         ` Mick [this message]
2007-05-21  9:50           ` Florian Philipp
2007-05-21 12:18             ` Marek Miller
2007-05-21 13:31               ` Iain Buchanan
2007-05-21 14:53                 ` Dale
2007-05-21  9:24         ` Nistor Andrei

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=200705210808.36111.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.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