netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Fejes József" <fejes@joco.name>
To: netdev@vger.kernel.org
Subject: r8169 misleading firmware error messages
Date: Sat, 16 Apr 2011 10:27:01 +0200	[thread overview]
Message-ID: <4DA952D5.7030805@joco.name> (raw)

Hi,

I'm using Linux 2.6.38.3 with a Realtek 8169 card, ID: 10ec:8168 
(integrated into an Intel D945GSEJT mobo). It never needed any firmware 
files, and when I was using 2.6.37, it never complained about it either. 
Now it does complain (but it still works perfectly):

r8169 0000:01:00.0: eth0: unable to apply firmware patch

Also when I do initramfs stuff:

W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for 
module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for 
module r8169

So then I installed the rtl_nic firmware files, and the error messages 
were gone.

How do I know if it actually tries to load the firmware at all? I see 
there's a condition, if an rtl_readphy returns a wrong value, it doesn't 
even try to load the firmware and just prints the message. Although this 
wouldn't explain why the error message disappeared when the files were 
there.

Clearly, my device works without these firmware files. If my device 
works better with them, or if there are other similar devices which 
require it, I think there should be a configuration option to disable 
this firmware stuff and its benefits altogether so that it doesn't even 
report that it needs it.

Best regards,

-- 
Fejes József
http://joco.name

             reply	other threads:[~2011-04-16  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-16  8:27 Fejes József [this message]
2011-04-16 11:04 ` r8169 misleading firmware error messages François Romieu
2011-04-16 12:06   ` Fejes József
2011-04-16 15:34     ` Ben Hutchings
2011-04-17 14:38     ` François Romieu

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=4DA952D5.7030805@joco.name \
    --to=fejes@joco.name \
    --cc=netdev@vger.kernel.org \
    /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).