From: felix@crowfix.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ~amd64 compatibility with modern cpus
Date: Fri, 14 Dec 2012 13:24:10 -0500 [thread overview]
Message-ID: <20121214182410.GD19095@crowfix.com> (raw)
In-Reply-To: <20121214181646.GL8486@server>
On Fri, Dec 14, 2012 at 12:16:46PM -0600, Bruce Hill wrote:
> On Fri, Dec 14, 2012 at 11:18:21AM -0500, felix@crowfix.com wrote:
> >
> > I will try some more desperate tricks today, like reconnecting the USB pile to see if it at least boots the disks again - is my choice between disks and keyboard? I will find out. My best guess right now is that booting 3.7.0 is what clobbered things; whether I added a option which loaded bad firmware, or 3.7.0 is broken, I have no idea. It could well be something unrelated to 3.7.0. My goal for today is to try to get keyboard and disk working, then boot with 3.6.8.
>
> Whatever you think of logic, it is entirely illogical that a kernel could kill
> your BIOS, or any hardware ... at least, just booting into it.
>
> The southbridge is a good thing to look at, esp for a burned spot/pit.
>
> My suggestion is http://www.sysresccd.org/SystemRescueCd_Homepage
That's what I've been using.
But the hardware failure is illogical too; why would USB and SATA fail at the same time? Or why would southbridge fail when it had been running perfectly fine?
I don't really think it was 3.7.0, but who knows, did I answer some config question incorrectly and tell it to load some firmware? Without access to the disk, I can't tell. I don't remember any question about loading BIOS firmware, and can't see why the kernel would even care about that.
The whole mess makes no sense.
--
Felix Finch, a la mode
next prev parent reply other threads:[~2012-12-14 18:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 16:18 [gentoo-user] ~amd64 compatibility with modern cpus felix
2012-12-14 16:28 ` Michael Mol
2012-12-14 16:33 ` felix
2012-12-14 16:47 ` Florian Philipp
2012-12-14 17:22 ` Volker Armin Hemmann
2012-12-14 17:35 ` felix
2012-12-14 18:16 ` Bruce Hill
2012-12-14 18:24 ` felix [this message]
2012-12-14 18:34 ` Bruce Hill
2012-12-14 18:43 ` felix
2012-12-14 18:48 ` Michael Mol
2012-12-14 18:52 ` Bruce Hill
2012-12-16 1:55 ` [gentoo-user] " Grant Edwards
2012-12-14 18:38 ` [gentoo-user] " Volker Armin Hemmann
2012-12-14 19:51 ` [gentoo-user] ~amd64 compatibility with modern cpus -- REBOOT OK THIS A.M felix
2012-12-14 20:00 ` Michael Mol
2012-12-14 21:19 ` Dale
2012-12-14 22:03 ` felix
2012-12-17 22:10 ` Robert Walker
2012-12-18 4:41 ` felix
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=20121214182410.GD19095@crowfix.com \
--to=felix@crowfix.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