Page 2 of 3

Re: R8168b/8111b NIC support?

Posted: 2009/07/06 18:53:20
by dk7ue
I am going thru the same problem. Unfortunately, I cannot upgrade to CentOS 5 - I am trying to run a dedicated hardware with drivers working only on CentOS 4. So, as per the discussions in the thread earlier, I need the kmod-r8168 package. Any tips on how can I get/create one?

On my machine uname -rmi gives
2.6.9-78.0.22.ELsmp i686 i386

Re: R8168b/8111b NIC support?

Posted: 2009/09/25 22:48:54
by vidave
Same issue here. I've got some software that only supports RHEL/CentOS 4. As much as I'd personally like to move to 5.x it's just not going to happen.

uname -rmi for me:

2.6.9-78.ELsmp i686 i386

The hardware is an MSI Nettop with an Atom 330 (Dual core 1.6ghz)

Re: R8168b/8111b NIC support?

Posted: 2009/09/27 12:02:38
by AlanBartlett
I have only just come across the later postings to this thread -- I have no idea how I missed [b] dk7ue[/b]'s and [b]vidave[/b]'s requests for help.

I'll see what I can do for you both but, as always, I make no guarantees.

It will be very useful (for me) to see the output returned by the following --

[b]for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1 }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n; done[/b]

Re: R8168b/8111b NIC support?

Posted: 2009/09/30 20:41:18
by w6it
Hi Alan,

I have the same issue. Would appreciate it if you could create the kmod-r8168 package for CentOS 4.

My hardware is the Jetway N92-330-LF with the Intel Atom processor and Realtek RTL8111C PCIe Ethernet with CentOS 4.7.

My uname -rmi is: i686 i386

The lspci output you requested is:
01:00.0 "Ethernet controller" "Realtek Semiconductor Co., Ltd." "RTL8111/8168B PCI Express Gigabit Ethernet controller" "-R02 "Realtek Semiconductor Co., Ltd." "RTL8111/8168B PCI Express Gigabit Ethernet controller"
01:00.0 Class 0200: 10ec:8168 (rev 02)

Thanks for your help.


Re: R8168b/8111b NIC support?

Posted: 2009/10/01 11:40:03
by AlanBartlett
A Vendor:Device ID paring of 10ec:8168 -- that shouldn't be a problem, [b]Greg[/b].

I just need to find the time and remember to think [i]C4[/i], not [i]C5[/i]. :-)

If you haven't heard anything from me within 2 - 3 days, please give this thread a bump.

Re: R8168b/8111b NIC support?

Posted: 2009/10/01 15:39:19
by AlanBartlett
The kABI tracking kmod-r8168 packages (for [i]CentOS-4[/i]) are now available for download from

Please note that the 32-bit (both i586 & i686) & 64-bit packages, along with the source package, md5sum.txt and sha1sum.txt files are all present in that directory. Please ensure that you download the correct version -- architecture and type -- for your system.

Although the packages are signed with the [url=//]ELRepo key[/url] and have the [i].elrepo[/i] tag, they are provided by me as a private service and are not [i]ELRepo[/i] packages.

Now where is my :pint: ?

Re: R8168b/8111b NIC support?

Posted: 2009/10/01 18:18:22
by w6it
Thanks Alan for the fast response.

Just to be sure, for my system I would use: kmod-r8168-8.014.00_NAPI-1.EL.elrepo.i686.rpm is that correct?

I'll let you know how it goes.


R8168b/8111b NIC support?

Posted: 2009/10/02 15:46:10
by toracat
Those kmod packages offered by Alan are currently unavailable. He and I identified an issue relating to the "integrity" of the kmods built for CentOS-[b]4[/b]. This is due to the limited offering of kernel module checking in CentOS-4 as opposed to the real kABI-tracking feature found in CentOS-5.

We will update the thread as we make progress on this subject.

Re: R8168b/8111b NIC support?

Posted: 2009/10/03 13:10:20
by toracat
The wait is over. :-)

[b]Alan[/b] was doing some underground construction and now a reworked version of kmod-r8168 for CentOS-4 is available once again. I took the liberty of making this announcement before he comes out of his cave. :-D

Re: R8168b/8111b NIC support?

Posted: 2009/10/03 15:14:41
by toracat
One additional note about kmods built for CentOS-4. Unlike CentOS-5, CentOS-4 does not offer a full set of RPM packaging macros and the kernels do not have kABI meta information. Therefore, technically, calling CentOS-4 kmods "kABI-tracking" may not be adequate. They are rather "kernel version independent".