From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 0E4801381F3 for ; Fri, 14 Dec 2012 18:26:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D682721C159; Fri, 14 Dec 2012 18:26:41 +0000 (UTC) Received: from crowfix.com (li35-165.members.linode.com [72.14.176.165]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 889E221C104 for ; Fri, 14 Dec 2012 18:24:16 +0000 (UTC) Received: (qmail 22229 invoked by uid 1000); 14 Dec 2012 18:24:10 -0000 Date: Fri, 14 Dec 2012 13:24:10 -0500 From: felix@crowfix.com To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] ~amd64 compatibility with modern cpus Message-ID: <20121214182410.GD19095@crowfix.com> References: <20121214161821.GA19095@crowfix.com> <20121214181646.GL8486@server> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121214181646.GL8486@server> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 05924951-a10b-4ebc-840b-e9d58c9665a2 X-Archives-Hash: 960bed00c1808d73de90b7b18d7b8b96 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