[solved] Missing firmware for network adapter

[wvxvw]

Hi, I believe that I understood this message correctly:

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

I've tried to install firmware-linux package, but the warning is still there (right after install). I'm not familiar with the problem or even with its nature, so, please be patient and explain in more details if you answer

I've found this problem by looking the messages log, where there was the line:

r8169 0000:07:00.0: eth0: unable to load firmware patch rtl_nic/rtl8168e-1.fw (-2)

Then I read in another place that the firmware-linux package is meant to contain the said patch, but it looks like it's not there. Where is it?

[4D696B65]

You will need firmware-realtek from backports or upgrade to wheezy.
http://packages.debian.org/squeeze-back ... re-realtek

[wvxvw]

Thanks, this fixes it!

[rbeldua]

Thanks, this fixes it!

Hi..am new to linux, could you post pls how to fix this error. thanks in advance

[darmach]

Hello,
same for me. I get :

Code: Select all

[   18.245462] r8169 0000:03:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168g-2.fw (-2)

On jessie.

How to solve that one on jessie?

[stevepusser]

By doing the same thing--enable nonfree and installing firmware-realtek, or directly downloading and installing the deb package. https://packages.debian.org/jessie/firmware-realtek

[re00k]

Hi,
It's years later and i got bitten right now by the same scenario:
In a new Debian stable (Bookworm) installation i had updated to the latest and fixed Kernel 6.1.85-1.
Afterwards, i tried suspend and resume, and the network didn't come up again.
Same after a reboot.
In the syslogs i found

r8169: ... firmware ... rtl8168g-2.fw failed to load

And right you were, the package firmware-realtek was missing.
Got it elsewhere from the repository and transferred by USBstick,
copied to /var/cache/apt/archives and aptitude got it directly on the next try.
On the next reboot, i still read in the logs

... r8169_apply_firmware failed: -110
... PHY r8169-0-700:00: phy_poll_reset failed: -110

On the next reboot, i tried a live Distro from USB stick, which failed to boot, also citing error -110 about the stick.
On the third reboot i was prepared to go back to the Kernel 6.1.76-1 from before, via USBstick.
But now, both firmware load and PHY reset worked without a hitch and the net came up.
The ONE thing i had changed was to install firmware-realtek,
Possibly saved the day with your information, you did, sir!

[Aki]

In the syslogs i found

Code: Select all

r8169: ... firmware ... rtl8168g-2.fw failed to load

In a new Debian stable (Bookworm) installation
[..]
And right you were, the package firmware-realtek was missing.
Got it elsewhere from the repository and transferred by USBstick,
copied to /var/cache/apt/archives and aptitude got it directly on the next try.

This is a rather unconventional way of installing packages. This is not the way to do it. You need to download it from the Debian repositories and then install it; a possible shortcut could be:

Code: Select all

wget http://ftp.us.debian.org/debian/pool/non-free-firmware/f/firmware-nonfree/firmware-realtek_20230210-5_all.deb
sudo dpkg -i firmware-realtek_20230210-5_all.deb

Code: Select all

r8169: ... firmware ... rtl8168g-2.fw failed to load

On the next reboot, i still read in the logs

Code: Select all

... r8169_apply_firmware failed: -110
... PHY r8169-0-700:00: phy_poll_reset failed: -110

Is it possible that you have installed the wrong firmware?

On the next reboot, i tried a live Distro from USB stick, which failed to boot, also citing error -110 about the stick.

What Live Distribution?

On the third reboot i was prepared to go back to the Kernel 6.1.76-1 from before, via USBstick.
But now, both firmware load and PHY reset worked without a hitch and the net came up.
The ONE thing i had changed was to install firmware-realtek,
Possibly saved the day with your information, you did, sir!

Yes, it is possible that you have the wrong firmware installed. Open a new topic if you think you have a kernel problem.

[re00k]

This is a rather unconventional way of installing packages. This is not the way to do it. You need to download it from the Debian repositories and then install it; a possible shortcut could be:

Actually, i did.
My other machine doesn't have realtek LAN.
Therefore i got the package from the bookworm repository file

http://ftp.es.debian.org/debian/pool/no ... -5_all.deb

and transferred that to the disconnected machine into /var/cache/apt/archives,
so that aptitude had it available. Installed then without a hitch.

Is it possible that you have installed the wrong firmware?

Well, the log specifically complained about

r8169: ... firmware ... rtl8168g-2.fw failed to load

and this is listed in the mentioned firmware-realtek's information page as pertaining to RTL8168G.
This seemed like a close relative and maybe a solution, also, this package up to now was not installed.

On the next reboot, i tried a live Distro from USB stick, which failed to boot, also citing error -110 about the stick.

What Live Distribution?

SparkyLinux stable AMD64, a Debian stable Bookworm modification.

https://sourceforge.net/projects/sparky ... o/download

the one i used to install the afflicted machine.
Sparky is based on Debian and uses Debian's repo's preferentially, adding their own repo's.
Sadly, USBsticks i bought in the last 2 years appear to suck.
regards, rec00k

[sunrat]

Sparky is a Debian derivative. Derivative topics are handled in Off-topic subforum.
You should post issues in Sparky forums - https://forum.sparkylinux.org/

Topic moved.

[re00k]

Hi,
in principle you're right.
I was contributing to an existing thread, though, what i hoped would be an additional case description.
After my initial post, i was answering questions by @Aki
Thus not asking, but telling.
Best regards.

[sunrat]

Hi,
in principle you're right.
I was contributing to an existing thread, though, what i hoped would be an additional case description.
After my initial post, i was answering questions by @Aki
Thus not asking, but telling.
Best regards.

Oops, my bad. Moved back to "Hardware".