Results 1 to 2 of 2
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 07-17-2013 #1
- Join Date
- Jul 2013
lspci incorrectly identifies RTL8111/8168 ethernet card
I am currently running Debian Squeeze Linux 2.6.32-5-amd64. When I try to upgrade to Debian Wheezy or Ubuntu 12.04 or later I can no longer connect to the router. The interface comes up just fine and the green light turns on showing that the port is receiving power, but the yellow data light never blinks. So the ethernet port gets turned on, but can't send or receive data. I have tried using the r8168 drivers from Realtek which produced no changes as well as using r8169 drivers from older kernels. I have checked to make sure that the network is configured properly and will attach some of the outputs from meaningful sources. The only difference I see between the two installs is the kernel version and the lspci output. On older kernel versions (<= 2.6) it displays the controller as RTL8111/8168B whereas on newer versions it is shown as RTL8111/8168. However, they both display the same device code. My current theory on what is happening here is that the r8168/9 kernel module is getting the wrong device name from the system. Has anyone seen an issue like this/ possible workaround?
lspci (newer kernel):
03:00.0 Ethernet controller : Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06) Subsystem: Gigabyte Technology Co., Ltd Motherboard [1458:e000] Flags: bus master, fast devsel, latency 0, IRQ 73 I/O ports at d000 [size=256] Memory at da104000 (64-bit, prefetchable) [size=4K] Memory at da100000 (64-bit, prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: r8168
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard Flags: bus master, fast devsel, latency 0, IRQ 59 I/O ports at d000 [size=256] Memory at da104000 (64-bit, prefetchable) [size=4K] Memory at da100000 (64-bit, prefetchable) [size=16K] Capabilities:  Power Management version 3 Capabilities:  MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities:  Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities:  Advanced Error Reporting Capabilities:  Virtual Channel Capabilities:  Device Serial Number 01-00-00-00-68-4c-e0-00 Kernel driver in use: r8169
r8168 260963 0
eth0 Link encap:Ethernet HWaddr 94:de:80:71:0a:29 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:73 Base address:0xc000
- 07-18-2013 #2
- Join Date
- May 2011
hello and welcome, jpulman!
could it be that the r8169 module is loading first, and preventing the r8168 module from binding to the device? see this thread.
as to the lspci output, the verbose output from lspci comes from a text file that contains all that info, and that file is updated regularly. so different versions of distros will have varying info for the same device. you can find that file here usually: