Message-ID: <4B43C169.3040601@tmr.com>
Date: Tue, 05 Jan 2010 17:47:05 -0500
From: Bill Davidsen <davidsen@tmr.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090507 Fedora/1.1.16-1.fc9 NOT Firefox/3.0.11 SeaMonkey/1.1.16
MIME-Version: 1.0
To: Gene Heskett <gene.heskett@verizon.net>
CC: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.33 fails to find cpu firmware
References: <201001050128.12202.gene.heskett@verizon.net>
In-Reply-To: <201001050128.12202.gene.heskett@verizon.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1217
Lines: 28

Gene Heskett wrote:
> Greetings a;;
> 
> 2.6.33-rc2 isn't terribly stable here, but the first problem is .6 seconds 
> into the boot, it hangs for 1 minute waiting on the amd cpu firmware, which I 
> don't believe it ever finds, it just times out and goes on.  This machine 
> runs fairly well without that even for a cold boot.
> 
> I assume this is because the root filesystem with /lib/firmware is not yet 
> available, and that if this file was supplied in the initrd file, this would 
> go away.
> 
> I've studied the manpage for mkinitrd, but the precise option to do this 
> preload escapes me.
> 
But the root should be mounted before firmware, I'm looking at my messages log 
and everything including swap seems to be there before the firmware loader is 
called. That's on a 2.6.31 kernel, but still...

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/