[SOLVED] need realtek r8168 binary for intel I5 (AMD_64) for fedora 16

dsahnen · 05-26-2012, 05:26 PM

I just installed fedora 16 on my PC (64 bit I5). I had previously installed Fedora 12, and from what I read, it was easier/better to do a full install of 16 rather then try to upgrade. I took this advice, but now I am stuck. I have no network connection. I have a gigabyte motherboard (P55A) that has a realtek NIC. I downloaded the driver source for my configuration, but I cannot compile it because I do not have a compiler installed. Of course, I cannot install the compiler via yum, because I have no network connection. I tried downloading an rpm product (gcc) and installing via rpm, but although I get no errors, it does not appear to install gcc. Therefore, I cannot compile the driver.

Could someone with a similar system please send the r8168 binary to me at dsahnen@gmail.com. If I can install this binary and get my NIC working, I believe I can get everything else working from that point. But the source does not do me any good. I need the correct binary (for 3.1.0-7.fc16.x86_64)

Thanks,
Dave

jhwilliams · 05-26-2012, 09:03 PM

Just build in from source.

Quote:

I cannot install the compiler via yum, because I have no network connection

Use a CD to get gcc

Here are outdated instructions for Ubuntu -- there will be a few changes for Redhat.

http://nosemaj.org/hardy-r8168

jschiwal · 05-27-2012, 01:05 AM

I believe you want to use the rtl8169 kernel module instead. From the r8169.c file:

Code:

 * r8169.c: RealTek 8169/8168/8101 ethernet driver.

Code:

 sudo /sbin/modinfo r8169
filename:       /lib/modules/3.1.10-1.9-desktop/kernel/drivers/net/r8169.ko
firmware:       rtl_nic/rtl8105e-1.fw
firmware:       rtl_nic/rtl8168e-3.fw
firmware:       rtl_nic/rtl8168e-2.fw
firmware:       rtl_nic/rtl8168e-1.fw
firmware:       rtl_nic/rtl8168d-2.fw
firmware:       rtl_nic/rtl8168d-1.fw
version:        2.3LK-NAPI
license:        GPL
description:    RealTek RTL-8169 Gigabit Ethernet driver
author:         Realtek and the Linux r8169 crew <netdev@vger.kernel.org>
srcversion:     3E842CC3B34475192563328
alias:          pci:v00000001d00008168sv*sd00002410bc*sc*i*
alias:          pci:v00001737d00001032sv*sd00000024bc*sc*i*
alias:          pci:v000016ECd00000116sv*sd*bc*sc*i*
alias:          pci:v00001259d0000C107sv*sd*bc*sc*i*
alias:          pci:v00001186d00004302sv*sd*bc*sc*i*
alias:          pci:v00001186d00004300sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008169sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008168sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008167sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008136sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008129sv*sd*bc*sc*i*
depends:        
vermagic:       3.1.10-1.9-desktop SMP preempt mod_unload modversions 
parm:           use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int)
parm:           debug:Debug verbosity level (0=none, ..., 16=all) (int)

Run "lspci -v" and then "lspci -n". The "lspci -v" command may indicate the driver you need. The "lscpi -n" command will provide the manufactures ID code. Note how it matches the line from the "modinfo" command. The firmware was supplied with my kernel. In your case, if it isn't, look for a package that supplies the files.

Code:

sudo /sbin/lspci -v | sed -n '/Ethernet/,/^$/p'
0e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
        Subsystem: Toshiba America Info Systems Device ff00
        Flags: bus master, fast devsel, latency 0, IRQ 46
        I/O ports at 4000 [size=256]
        Memory at f2010000 (64-bit, prefetchable) [size=4K]
        Memory at f2000000 (64-bit, prefetchable) [size=64K]
        [virtual] Expansion ROM at f2020000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable- Count=2 Masked-
        Capabilities: [d0] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 36-38-32-35-33-34-33-33
        Kernel driver in use: r8169

> /sbin/lspci -n | grep 0e:00.0
0e:00.0 0200: 10ec:8168 (rev 02)

I highlighted the lines that match up so you can see how this information ties together.

dsahnen · 05-27-2012, 08:27 AM

Quote:

Originally Posted by jhwilliams

Just build in from source.

Use a CD to get gcc

Here are outdated instructions for Ubuntu -- there will be a few changes for Redhat.

http://nosemaj.org/hardy-r8168

Thank you for this information and your scripts. It was quite informative. I have now installed gcc, but I cannot get a clean compile. There are several header files included in the .c's that just don't exists on my machine. Most of these are <linux/*.h> files. These files are simply not in /usr/include/linux. It seems that this version of the driver file was written for linux kernel version 2.4 or 2.6. Since I wonder if the difference is that I have 3.1.0 installed. Anyone have any experience with this?

Unfortunately, the binaries that were included in your tar did not work for me. (insmod failed). Not surprising, I guess, since these were compiled for Ubuntu (I assume). So I'm still looking for a solution. I will post here when I get it working with the solution that worked for me. In the meantime, I'm still looking for the binary if anyone has it.
Thanks

jschiwal · 05-27-2012, 10:22 PM

You want the r8169 kernel module. See the post above. It turned out I have the same nic on my laptop.

jhwilliams · 05-27-2012, 11:04 PM

Quote:

Originally Posted by jschiwal

You want the r8169 kernel module. See the post above. It turned out I have the same nic on my laptop.

At the time I wrote that blog post, r8169 didn't have support for 8168/8111, and that was the whole point.

I did notice (around 2010 maybe?) that 8169 in the common distro Linux releases was supporting it, though.

So, I am curious why any relatively recent distro needs to be messed with anymore at all?

dsahnen · 05-30-2012, 05:47 PM

Quote:

Originally Posted by jhwilliams

At the time I wrote that blog post, r8169 didn't have support for 8168/8111, and that was the whole point.

I did notice (around 2010 maybe?) that 8169 in the common distro Linux releases was supporting it, though.

So, I am curious why any relatively recent distro needs to be messed with anymore at all?

I solved the problem by purchasing a NIC. I just couldn't get the one on the MB to work.