public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tamer Higazi <th982a@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kernel panick after time while compiling....
Date: Wed, 29 May 2013 00:50:40 +0200	[thread overview]
Message-ID: <51A534C0.2030203@googlemail.com> (raw)
In-Reply-To: <51A52EBF.9020107@gmail.com>

Dale!
I am getting now myself a Mac OSX Mini Server with 8GB or 16GB RAM, and
get OSX, Windows and Gentoo there on a disk to run. That's it!

Proper screen with a very high resolution, and I am happy, and I am back
coding.


For future travels, My CPU makes with me the journey all the time....

:) :) :)


Tamer



Am 29.05.2013 00:25, schrieb Dale:

> On a really really old system many years ago, I had random reboots, lock
> ups and such.  I swapped P/S, memory and other components that I could
> but it still did it.  I finally figured it had to be something hard
> wired on the motherboard and just replaced the whole thing.  I figure a
> controller chip or something was the problem. 
> 
> One thing about puters and random problems, they are hard to nail down. 
> P/S and memory are a common problem but something bad on the mobo can
> give the same symptoms.  Basically, you have to replace stuff until it
> stops doing whatever it shouldn't be doing.  I have seen people have
> enough parts to build a second rig short the case of course.  As always,
> it is the last thing you replace and sometimes it can be the last thing
> you CAN replace.  ;-)
> 
> Personally, I'd prefer one that doesn't work at all.  Tends to narrow it
> down a lot.  If replacing the P/S don't fix it, time for a new build. 
> It is dead.  For a 6 year old puter, I'd just have to try fixing it
> tho.  I usually get at least 8 years out of a build. 
> 
> Dale
> 
> :-)  :-) 
> 



  parent reply	other threads:[~2013-05-28 22:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-26 23:15 [gentoo-user] kernel panick after time while compiling Tamer Higazi
2013-05-26 23:36 ` Dale
2013-05-27 15:38   ` Fast Turtle
2013-05-27 20:11     ` Tamer Higazi
2013-05-28  5:38       ` Mick
2013-05-28 21:34         ` Stroller
2013-05-28 21:41           ` Tamer Higazi
2013-05-28 22:25             ` Dale
2013-05-28 22:44               ` Alan McKinnon
2013-05-28 23:03                 ` Dale
2013-05-28 22:50               ` Tamer Higazi [this message]
2013-05-29  7:51             ` Thanasis
2013-05-26 23:39 ` [gentoo-user] " Nikos Chantziaras
2013-05-27  0:12   ` Zhu Sha Zang
2013-05-27 15:35 ` [gentoo-user] " Fast Turtle

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=51A534C0.2030203@googlemail.com \
    --to=th982a@googlemail.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