From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: e1000-devel@lists.soutceforge.net,
"Rafael J. Wysocki" <rjw@sisk.pl>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.29-rc2 regression] e100: netconsole not functional because of missing firmware
Date: Mon, 19 Jan 2009 21:43:00 +0300 [thread overview]
Message-ID: <200901192143.02853.arvidjaar@mail.ru> (raw)
In-Reply-To: <4807377b0901191030g27efac79rbd39501eb2eea4cb@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On 19 января 2009 21:30:01 Jesse Brandeburg wrote:
> On Sat, Jan 17, 2009 at 8:08 AM, Andrey Borzenkov <arvidjaar@mail.ru>
wrote:
> > [ 2.008509] e100: eth0: e100_request_firmware: Failed to load
> > firmware "e100/d101m_ucode.bin": -22
> > [ 2.010461] netconsole: failed to open eth0
> > [ 2.010996] netconsole: cleaning up
> >
> > This has been working all the time without requiring any external
> > firmware to be present. Why it suddenly refuses to work now?
>
> to use netconsole you probably need to set config option
> CONFIG_FIRMWARE_IN_KERNEL=y
>
Yes, I already figured that much :) Unfortunately, there seems to be a
bug that prevents compiling firmware if src != obj. At least it does not
work for me.
> Hm, I wonder if we couldn't have netconsole=y select
> CONFIG_FIRMWARE_IN_KERNEL in Kconfig
>
That probably is overkill; unfortunately I am afraid there is no way to
make kconfig automatically select correct firmware in case e100 is built
in.
Thank you!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-19 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 16:08 [2.6.29-rc2 regression] e100: netconsole not functional because of missing firmware Andrey Borzenkov
2009-01-19 18:30 ` Jesse Brandeburg
2009-01-19 18:43 ` Andrey Borzenkov [this message]
2009-01-19 19:20 ` Rafael J. Wysocki
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=200901192143.02853.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=e1000-devel@lists.soutceforge.net \
--cc=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).