Interfaces won't detect PCI Gigabit NIC

johndoe86x · 5. Januar 2016

Hey, guys, I just added a PCI Gigabit NIC for a second interface to my box, but I'm not sure why it's not detected.

I've seen several reviews speaking about full compatibility with their Linux boxes.
http://www.amazon.com/gp/produ…=oh_aui_search_detailpage
Any advice on this? Thanks!

ryecoaaron · 5. Januar 2016

If you aren't using the backports 3.16 kernel, you will have to wait for OMV 3 and the backports 4.3 kernel -OR- compile the driver yourself.

What is the output of: lspci

If the command doesn't exist, apt-get install pciutils

johndoe86x · 6. Januar 2016

I am using the backports kernel, and here is the output of lspci

Code

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation Z68 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
02:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
06:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)

Alles anzeigen

ryecoaaron · 6. Januar 2016

That should be easily detected. What is the output of: ifconfig -a

johndoe86x · 6. Januar 2016

The output of ifconfig -a

Code

docker0   Link encap:Ethernet  HWaddr 02:42:2f:35:1c:26  
          inet addr:172.17.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
          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:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


eth0      Link encap:Ethernet  HWaddr bc:5f:f4:1d:69:6b  
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1263327 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6123212 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:391185001 (373.0 MiB)  TX bytes:8416567549 (7.8 GiB)


lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:60168 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60168 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:6362675 (6.0 MiB)  TX bytes:6362675 (6.0 MiB)

Alles anzeigen

ryecoaaron · 6. Januar 2016

Post the output of dmesg | grep r8169

If lsmod | grep r8169 returns nothing, try modprobe r8169.

johndoe86x · 6. Januar 2016

dmesg | grep r8169

Code

[    0.745985] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    0.746219] r8169 0000:04:00.0: irq 45 for MSI/MSI-X
[    0.746379] r8169 0000:04:00.0 eth0: RTL8168evl/8111evl at 0xffffc900018ea000, bc:5f:f4:1d:69:6b, XID 0c900800 IRQ 45
[    0.746381] r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[   20.780298] r8169 0000:04:00.0: firmware: direct-loading firmware rtl_nic/rtl8168e-3.fw
[   20.881601] r8169 0000:04:00.0 eth0: link down
[   20.881621] r8169 0000:04:00.0 eth0: link down
[   23.204230] r8169 0000:04:00.0 eth0: link up

lsmod | grep r8169

Code

r8169                  68527  0 
mii                    12675  1 r8169

ryecoaaron · 6. Januar 2016

That must be the onboard adapter. I just looked at lspci again and it only shows one adapter. Even if it didn't have drivers, the card should show up in lspci. Try reseating the card or putting it in a different slot.

johndoe86x · 8. Januar 2016

Sorry to be MIA for a bit, I'm a bit wary of opening the box as I've had one of the drives not properly reconnect and lost an array when I had a bad drive. It's a fault of the drive bay. Anyways, I don't have anything plugged in right now, but when I do... there seems to be at least a notification light that it's connected. Still think I should re-seat?

ryecoaaron · 8. Januar 2016

Reseat it or replace it with an Intel adapter. It needs to show up in lspci for it to work.

johndoe86x · 8. Januar 2016

When in the world did these things get so expensive?

@ryecoaaron, would you suggest using this?
http://www.amazon.com/Intel-EX…s_browse-bin%3A3896216011

ryecoaaron · 8. Januar 2016

So expensive?? That is a good quality Intel pci-e dual port. That is less than I paid for my single port So, yes, that would work well if you have an open pci-e 4x or bigger slot.

Interfaces won't detect PCI Gigabit NIC

Jetzt mitmachen!

Tags