From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Woodhouse Subject: Re: e100/netconsole: Failed to load firmware (Re: linux-next: Tree for November 3) Date: Mon, 03 Nov 2008 16:09:27 +0000 Message-ID: <1225728567.745.13.camel@macbook.infradead.org> References: <1225727806.745.7.camel@macbook.infradead.org> <20081103160057.GA12456@orion> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20081103160057.GA12456@orion> Sender: netdev-owner@vger.kernel.org To: Alexander Beregalov Cc: e1000-devel@lists.sourceforge.net, jaswinder@infradead.org, linux-next@vger.kernel.org, Netdev List-Id: linux-next.vger.kernel.org On Mon, 2008-11-03 at 19:00 +0300, Alexander Beregalov wrote: > # CONFIG_FIRMWARE_IN_KERNEL is not set > CONFIG_EXTRA_FIRMWARE="" OK, so you didn't include the E100 firmware in the kernel, so it only actually manages to bring up the E100 after it's mounted the root file system, not in time for the console? If you set CONFIG_FIRMWARE_IN_KERNEL, does it work? I think that's fairly much expected behaviour. I wonder if there's a way we could make it slightly more intuitive though. -- David Woodhouse Open Source Technology Centre David.Woodhouse@intel.com Intel Corporation