public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] r8169 unable to apply firmware patch
Date: Mon, 1 Aug 2011 09:47:21 +1000	[thread overview]
Message-ID: <CAC=wYCGghOV-GO9pWsVV8jmQkYV_E3QtrFZ2a7FsgPnQyPjX5A@mail.gmail.com> (raw)
In-Reply-To: <CAN0CFw0z7aBrSwND1-S6ssx06_oB7P1iyoXCHnpBZz=RwO-Rxw@mail.gmail.com>

>> Maybe you have an older firmware installed from a different package?
>> Run emerge -p linux-firmware on that box to see if there's a blocker.
>
> linux-firmware is blocked by radeon-ucode and rt61-firmware,

I'm guessing that radeon-ucode and rt61-firmware and all the others
are being deprecated in favour of linux-firmware, but i don't recall
seeing an elog on it.

> but now
> that I look closer I realize that ifconfig doesn't show an eth0
> interface at all even though lspci -v shows:
>
> Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
> Express Gigabit Ethernet controller
> ...
> Kernel driver in use: r8169
>
> Shouldn't the eth0 interface appear in ifconfig once the r8169 driver
> is loaded?  dmesg has no mention of eth0 or r8169.

That's odd. Does that box still have the failed loading firmware
error? Perhaps missing firmware stops eth0 from being created. I'd try
installing linux-fireware and trying again (assuming you havent
already).

>>> I guess linux-firmware is a package released by the kernel folks
>>> containing certain firmware blobs?  It looks like rt73 is in there but
>>> not b43.
>>
>> Maybe these?
>> /lib/firmware/brcm/bcm4329-fullmac-4.bin
>> /lib/firmware/brcm/bcm4329-fullmac-4.txt
>> /lib/firmware/brcm/bcm43xx-0.fw
>> /lib/firmware/brcm/bcm43xx_hdr-0.fw
>> /lib/firmware/LICENCE.broadcom_bcm43xx
>
> Right again.  The contents of /lib/firmware/b43 and /lib/firmware/brcm
> are completely different, but you think either one will work with a
> b43 device?

The driver will know which one it wants. You could grep the source for
the firmware file names to see which it pulls in.



  reply	other threads:[~2011-07-31 23:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30  0:05 [gentoo-user] r8169 unable to apply firmware patch Grant
2011-07-30  8:20 ` Adam Carter
2011-07-30  8:42   ` Adam Carter
2011-07-31  0:05     ` Grant
2011-07-31  5:11       ` Adam Carter
2011-07-31 19:17         ` Grant
2011-07-31 23:47           ` Adam Carter [this message]
2011-08-01 18:35             ` Grant
2011-08-01 18:45               ` Michael Mol
2011-08-01 19:04                 ` Grant
2011-08-01 19:21                   ` Michael Mol
2011-08-01 20:13                     ` Grant
2011-08-01 20:30                       ` Michael Mol
2011-08-02  3:29                         ` Adam Carter
2011-08-02 14:48                           ` Grant
2011-08-02 23:36                             ` Adam Carter
2011-08-03 16:39                               ` Grant
2011-08-03 17:32                                 ` Mick
2011-08-03 17:55                                   ` Grant
2011-08-02 14:43                         ` Grant
2011-08-02  9:37               ` pk
2011-08-01 16:10       ` Paul Hartman

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='CAC=wYCGghOV-GO9pWsVV8jmQkYV_E3QtrFZ2a7FsgPnQyPjX5A@mail.gmail.com' \
    --to=adamcarter3@gmail.com \
    --cc=gentoo-user@lists.gentoo.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