public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Please suggest settings and flags in  /etc/make.conf?
Date: Fri, 22 Jan 2010 05:25:46 -0800	[thread overview]
Message-ID: <5bdc1c8b1001220525k72fd4f11g76210dcb20143e45@mail.gmail.com> (raw)
In-Reply-To: <4B58E805.40007@gmail.com>

On Thu, Jan 21, 2010 at 3:49 PM, Juan Fco. Giordana
<juangiordana@gmail.com> wrote:
> On 01/22/2010 12:44 AM, Mark Knecht wrote:
>>
>> I'm just installing Gentoo on my first new machine in years. Can
>> anyone suggest which of the CPU flags below might best be added to
>> make.conf? The machine will be a standard desktop running rt-sources
>> and stable Gentoo.
>>
>> This processor is 2 physical cores with hyperthreading enabled in each
>> core.
>>
>> Currently make.conf has only the standard stuff other than me adding
>> the MAKEOPTS line:
>>
>> # These settings were set by the catalyst build script that automatically
>> # built this stage.
>> # Please consult /usr/share/portage/config/make.conf.example for a more
>> # detailed example.
>>
>> ...
>
> See http://en.gentoo-wiki.com/wiki/Safe_Cflags
>
> Also, take a look to what they say about -march=native.
>
> Regards
>

Hi all,
   OK, thanks to everyone for your responses. It's 5AM and I'm going
to try and answer as much as I can to get more info. Things are very
hosed up with this machine after whatever instructions I gave grub
didn't work. At the point where I'm supposed to get a grub splash
screen I get a blinking cursor, then it flashes for less than a second
some of the rootnoverify part from grub.conf so it's finding
something, and then I get a message about windows not starting because
<Windows root>\system32\hal.dll is missing.

   I have not yet this morning booted again from the install CD and
chrooted into the new 64-bit install. As I said, it's 5AM.

   OK, specific to this response there's nothing on the Safe_Cflags
page about this specific processor. (i5-661) I'll continue to study
that and take a very conservative path.

   Today all I want is to boot Gentoo with nothing but @system. I'm
happy to build that 10 times over with new CFLAGS if necessary before
going on to ANYTHING in @world. I don't NEED Gentoo just yet - I want
it but don't need it. What I need is to get grub working and be able
to boot into Windows first so I'm going to focus on that.

Thanks,
Mark



  reply	other threads:[~2010-01-22 13:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22  0:44 [gentoo-amd64] Please suggest settings and flags in /etc/make.conf? Mark Knecht
2010-01-21 23:49 ` Juan Fco. Giordana
2010-01-22 13:25   ` Mark Knecht [this message]
2010-01-22  3:05 ` Lie Ryan
2010-01-22  4:01   ` Mark Knecht
2010-01-22  8:02     ` Lie Ryan
2010-01-22 11:45       ` [gentoo-amd64] " Duncan
2010-01-22  5:26   ` [gentoo-amd64] " Peter Humphrey
2010-01-22  7:52     ` Lie Ryan
2010-01-22 13:27       ` Mark Knecht
2010-01-22 12:49   ` [gentoo-amd64] " Duncan
2010-01-22 13:39     ` Frank Peters
2010-01-22 19:05   ` [gentoo-amd64] " Mark Knecht

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=5bdc1c8b1001220525k72fd4f11g76210dcb20143e45@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-amd64@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