public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  SOLVED  Re: installing an amd k6
Date: Thu, 14 Sep 2006 00:47:38 +0000 (UTC)	[thread overview]
Message-ID: <loom.20060914T024005-246@post.gmane.org> (raw)
In-Reply-To: 200609130755.25586.ext-dirk.heinrichs@nokia.com

Dirk Heinrichs <ext-dirk.heinrichs <at> nokia.com> writes:
>
Hello Dirk,

I posted a resonse early today, but, it never made it..

> > Are you suggesting I use this in my make.conf file?
> > CFLAGS="-O2 -march=i586 -pipe"

> -march=k6 (or even k6-2) is OK, as listed above.

I used this:
CFLAGS="-O2 -march=i586 -pipe"

Because when I untarred the i586 file it was
what was written by default into the make.conf file by:
 stage3-i586-2006.0.tar.bz2 

When booting I gave these options
gentoo-nofb  acpi=no nosmp


> For this type of machine, I'd go with the stage 3. It might recompile some 
> of the packages, depending on your use flags upon next "emerge -DNuvp 
> world/system", baut that's still faster than bootstrapping from stage 1.


I did use the latest portage I could find:
portage-latest.tar.bz2         

The K6 is now compiling a hardened kernel.

Thanks to all, as it was a lot of little things that helped!


James


-- 
gentoo-user@gentoo.org mailing list



      parent reply	other threads:[~2006-09-14  0:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 19:29 [gentoo-user] installing an amd k6 James
     [not found] ` <342e1090609121248x5416adb2uc7fa84ab9951c886@mail.gmail.com>
2006-09-12 20:07   ` [gentoo-user] " James
2006-09-12 20:58     ` Steve McGrath
2006-09-12 22:21   ` James
2006-09-13  0:52     ` darren kirby
2006-09-13  2:34       ` james
     [not found]         ` <200609130755.25586.ext-dirk.heinrichs@nokia.com>
2006-09-14  0:47           ` James [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=loom.20060914T024005-246@post.gmane.org \
    --to=wireless@tampabay.rr.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