From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: BIOS or what
Date: Tue, 1 Mar 2011 15:55:04 +0000 (UTC) [thread overview]
Message-ID: <loom.20110301T165128-702@post.gmane.org> (raw)
In-Reply-To: 1298975033.4d6cc939c344f@imp.free.fr
<alain.didierjean <at> free.fr> writes:
> I'm starting to think about my next development desktop. One
> question haunts me:is the BIOS still a fatality? Is there a
> known and tested alternative available
> UEFI? Open Firmware? coreboot? other? Experience welcome
Well, I've been researching my next mobo too and
I think that GigaByte (some boards) allow
for 2 bios copies to be stored on the mobo.
That would mean a bios failure is not catastrophic?
Surely someone on the list has some experience in this,
maybe playing with Gigabyte's "core unlock" feature
to get a X3 running as a quad core?
James
next prev parent reply other threads:[~2011-03-01 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 10:23 [gentoo-user] BIOS or what alain.didierjean
2011-03-01 13:48 ` Florian Philipp
2011-03-01 15:55 ` James [this message]
2011-03-01 17:28 ` [gentoo-user] " 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=loom.20110301T165128-702@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