public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roger Mason <rmason@mun.ca>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] x86 boot failure
Date: Fri, 07 May 2010 07:33:15 -0230	[thread overview]
Message-ID: <y65633081wc.fsf@perthite.esd.mun.ca> (raw)
In-Reply-To: <4BE3BC4D.3000400@alyf.net> (Andrea Conti's message of "Fri, 07 May 2010 09:07:57 +0200")

Hello Andrea,

Andrea Conti <alyf@alyf.net> writes:

> I would check the processor type setting (A 3GHz Celeron should be
> P4-based) and/or muck around with ACPI. Also try disabling framebuffer
> drivers and using a plain VGA console.
>
> Leave all advanced settings in your bios to their defaults.
>
> And no, EM64T just means it *can* run amd64 -- i686 is fine and IMO a
> lot better for that kind of hardware if you do not absolutely need to
> run 64-bit code for some reason.

That is what I thought.

I looked into the BIOS: no AHCI support.  I edited the genkernel .config
and set the various SATA drivers as built-in.  There seemed to be
nothing wrong with grub or its configuration (I rebuilt it anyway, just
in case).  In the end I gave up and installed the machine as an amd64.
I may know today how that turned out: my install script shuts the
machine down at the end and I'll need to get someone to re-boot it for
me as I'm not in the office.

I'll let you know what happened.

Thanks Andrea and everyone else for your help.

Roger



  reply	other threads:[~2010-05-07 10:04 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  8:37 [gentoo-user] x86 boot failure Roger Mason
2010-05-06 11:52 ` Mick
2010-05-06 12:38   ` Roger Mason
2010-05-06 12:51     ` Mick
2010-05-06 13:03     ` Neil Bothwick
2010-05-06 13:34       ` Dale
2010-05-06 14:06         ` Neil Bothwick
2010-05-06 15:03           ` Dale
2010-05-06 15:25             ` Neil Bothwick
2010-05-06 16:03               ` Dale
2010-05-07  6:28                 ` Mick
2010-05-07  8:22                   ` Neil Bothwick
2010-05-06 14:19     ` Roger Mason
2010-05-09 21:46       ` Walter Dnes
2010-05-10 15:18         ` [gentoo-user] x86 boot failure [solved] Roger Mason
2010-05-07  8:51   ` [gentoo-user] x86 boot failure Peter Humphrey
2010-05-06 14:25 ` Stroller
2010-05-06 15:37   ` Roger Mason
2010-05-06 16:03     ` Helmut Jarausch
2010-05-06 16:48     ` Neil Bothwick
2010-05-07  7:07   ` Andrea Conti
2010-05-07 10:03     ` Roger Mason [this message]
2010-05-07 11:30       ` Helmut Jarausch
2010-05-07 13:33         ` Roger Mason
2010-05-08 14:16           ` [gentoo-user] Boot gentoo with GTP Disk label claude angéloz
2010-05-08 19:30             ` Mick
2010-05-10 16:01             ` Paul Hartman
2010-05-12 20:00               ` Mick
2010-05-12 20:47                 ` Paul Hartman
2010-05-12 21:47                   ` Mick
2010-05-12 21:59                     ` Paul Hartman
2010-05-12 22:22             ` [gentoo-user] " walt
2010-05-13 21:08               ` Stroller
2010-05-13 22:12                 ` Mick
2010-05-13 23:21                   ` walt
2010-05-14 11:34                     ` Tanstaafl
2010-05-14 12:23                       ` Neil Bothwick
2010-05-14 14:45                         ` Tanstaafl
2010-05-15 14:58                           ` walt

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=y65633081wc.fsf@perthite.esd.mun.ca \
    --to=rmason@mun.ca \
    --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