netdev - Re: e100/netconsole: Failed to load firmware (Re: linux-next: Tree for November 3)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1225728567.745.13.camel@macbook.infradead.org>
Date:	Mon, 03 Nov 2008 16:09:27 +0000
From:	David Woodhouse <dwmw2@...radead.org>
To:	Alexander Beregalov <a.beregalov@...il.com>
Cc:	e1000-devel@...ts.sourceforge.net, jaswinder@...radead.org,
	linux-next@...r.kernel.org, Netdev <netdev@...r.kernel.org>
Subject: Re: e100/netconsole: Failed to load firmware (Re: linux-next: Tree
	for November 3)

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@...el.com                              Intel Corporation

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html