RTL8111 series LAN chips

[Tuftec]

I am trying to get TC to work on a new version of the DMP eBox PC family (EB333x series).
This series has 2 x LAN ports. The first is detected by TC but the second is not.

I believe the second port is based on an RTL8111F device and runs at 1G.

Has anyone had experience with getting TC to work with this Ethernet chip family?

Cheers

Peter.

[curaga]

Please post the relevant parts from "lspci -vvnn".

[Tuftec]

I have this reported from DMESG so far

eth1: RTL8168b/8111b at 0xf808a000, 44:4d:50:54:ae:47, XID 0c900800 IRQ 16


More later.

[coreplayer2]

I've noticed it's quite common on motherboards with two Ethernet  ports that only the primary Ethernet port is usable. Have never really investigated why exactly this is, though am thinking it's a limitation of the driver ?

[Tuftec]

Here is the relevant information reported by lspci:

02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 07)
   Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
   Latency: 0, Cache Line Size: 128 bytes
   Interrupt: pin A routed to IRQ 16
   Region 0: I/O ports at c800 [size=256]
   Region 2: Memory at fc9ff000 (64-bit, prefetchable) [size=4K]
   Region 4: Memory at fc9f8000 (64-bit, prefetchable) [size=16K]
   Capabilities: <access denied>
   Kernel driver in use: r8169
   Kernel modules: r8169


The driver being used appears not to work.

Peter.

[coreplayer2]

If you're using tc-4.7.7 then you'll probably need the Realtek r8168 driver.  On the other hand tc-5.1 appears to be using the correct fixed driver.  Again I've had no reason to use the secondary eth port so can't tell you if it works or not in either case, but is just a thought since there were detection issues with the older r8169 driver.  Your chip appears to be 8168 but is using the r8169 driver, am surprised it works at all!

[curaga]

What do you mean by "appears not to work"? It does not show in ifconfig? Lights not blinking if you do ifconfig up? Etc.

[tinypoodle]

If you're using tc-4.7.7 then you'll probably need the Realtek r8168 driver.  On the other hand tc-5.1 appears to be using the correct fixed driver.  Again I've had no reason to use the secondary eth port so can't tell you if it works or not in either case, but is just a thought since there were detection issues with the older r8169 driver.  Your chip appears to be 8168 but is using the r8169 driver, am surprised it works at all!

Looks like correct driver for device ID:
http://cateee.net/lkddb/web-lkddb/R8169.html

[coreplayer2]

You my be right, I therefore stand corrected

Maybe this means little, but I fired up a notebook which uses the same eth. chip (single port) only to find it uses r8169 driver.  lspci -knn reports 8168B chip, same ID, however dmesg claims 8168c version which apparently is the rev2 chip

Code: [Select]

lspci -knn
08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02)
        Subsystem: CLEVO/KAPOK Computer Device [1558:0860]
        Kernel driver in use: r8169
        Kernel modules: r8169

Code: [Select]

tc@box:~$ dmesg | grep r816
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:08:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
r8169 0000:08:00.0: setting latency timer to 64
r8169 0000:08:00.0: irq 47 for MSI/MSI-X
r8169 0000:08:00.0: eth0: RTL8168c/8111c at 0xf8036000, 00:90:f5:80:3d:de, XID 1c4000c0 IRQ 47
r8169 0000:08:00.0: eth0: link down
r8169 0000:08:00.0: eth0: link up
I have a couple more pc's which use the same/similar  dual port Ethernet chip, will verify when I return home tomorrow
 
I'd like to know which kernel the OP is using and see his dmesg results.

[Tuftec]

Thanks for all the ideas.

Just to clarify.

The second port does not work.

The primary port is based on a different device and it works fine, but is only a 100M port.
We need to get the second port going to get a true 1G connection.

Here is the full details reported by lspci for both ports:


00:08.0 Ethernet controller [0200]: RDC Semiconductor, Inc. R6040 MAC Controller [17f3:6040]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
   Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
   Latency: 64 (750ns min, 2000ns max)
   Interrupt: pin A routed to IRQ 11
   Region 0: I/O ports at d800 [size=256]
   Region 1: Memory at febdfc00 (32-bit, non-prefetchable) [size=256]
   Expansion ROM at febc0000 [disabled] [size=64K]
   Kernel driver in use: r6040
   Kernel modules: r6040


02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 07)
   Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
   Latency: 0, Cache Line Size: 128 bytes
   Interrupt: pin A routed to IRQ 16
   Region 0: I/O ports at c800 [size=256]
   Region 2: Memory at fc9ff000 (64-bit, prefetchable) [size=4K]
   Region 4: Memory at fc9f8000 (64-bit, prefetchable) [size=16K]
   Capabilities: <access denied>
   Kernel driver in use: r8169
   Kernel modules: r8169

I have been directed to this driver
http://driverscollection.com/?H=RTL8111F&By=RealTek&SS=Linux

But I do not have clue how to possibly include this in TC.

All advice welcome.

Cheers

Peter.

[curaga]

You still didn't say what you mean with "doesn't work".

[Tuftec]

The ebox units do not have any blinkin lights to blink!!!

[Rich]

Hi Tuftec
If you run  ifconfig  does it list eth0 and eth1?

[Tuftec]

Here is what ipconfig reports

[Rich]

Hi Tuftec
Looks like you just need to assign an IP address.