Jump to content

Network adaptor acting weird on Gigabyte Aorus Extreme x399


amelius

Recommended Posts

So, I just switched motherboards to a Gigabyte Aorus Extreme x399 from an ROG Zenith Extreme. One of the things I like about this new board is that instead of having a PCI expansion board for 10gbe, it has it built into the motherboard.

 

Both of these boards use Aquantia for the 10 gigabit port.

 

On the new board, plugging into the 10gbe slot doesn't seem to do anything, while using either of the two 1gbe slots works fine.

When checking from terminal, I observed the following:

root@Atlas:~# lshw -class network
  *-network                 
       description: Ethernet interface
       product: I210 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: eth0
       version: 03
       serial: e0:d5:5e:e0:dc:42
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.4.0-k duplex=full firmware=3.11, 0x80000469 ip=192.168.2.107 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:39 memory:c0e00000-c0efffff ioport:2000(size=32) memory:c0f00000-c0f03fff memory:c0d00000-c0dfffff
  *-network UNCLAIMED
       description: Network controller
       product: Wireless 8265 / 8275
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:04:00.0
       version: 78
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress cap_list
       configuration: latency=0
       resources: memory:c1100000-c1101fff
  *-network DISABLED
       description: Ethernet interface
       product: I210 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:05:00.0
       logical name: eth1
       version: 03
       serial: e0:d5:5e:e0:dc:44
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.4.0-k firmware=3.11, 0x80000469 ip=192.168.2.87 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:24 memory:c0b00000-c0bfffff ioport:1000(size=32) memory:c0c00000-c0c03fff memory:c0a00000-c0afffff
  *-network UNCLAIMED
       description: Ethernet controller
       product: AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion]
       vendor: Aquantia Corp.
       physical id: 0
       bus info: pci@0000:07:00.0
       version: 02
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress pm msix msi vpd bus_master cap_list
       configuration: latency=0
       resources: memory:c0840000-c084ffff memory:c0850000-c0850fff memory:c0400000-c07fffff memory:c0800000-c083ffff
  *-network:0 DISABLED
       description: Ethernet interface
       physical id: 1
       logical name: gretap0
       capabilities: ethernet physical
       configuration: broadcast=yes multicast=yes
  *-network:1 DISABLED
       description: Ethernet interface
       physical id: 2
       logical name: erspan0
       capabilities: ethernet physical
       configuration: broadcast=yes multicast=yes
  *-network:2 DISABLED
       description: Ethernet interface
       physical id: 3
       logical name: bond0
       serial: 9e:ed:8b:10:af:a8
       capabilities: ethernet physical
       configuration: autonegotiation=off broadcast=yes driver=bonding driverversion=3.7.1 firmware=2 link=no master=yes multicast=yes

So it looks like the adapter in question is "*-network UNCLAIMED". I'm not entirely sure how to fix this, forum posts for linux in general have suggested that some driver is missing, and to fix it by sudo apt-get install linux-backports-modules-jaunty however, that wouldn't work on UnRaid because it's not a debian based distribution. What's odd to me is that a very similar card, just one that's external worked fine, it was even the same brand.

 

I'd like to figure out how to get this card to be claimed/working properly. I'm suspecting some sort of driver issue, but that's where I'm stuck, not sure where to go from here.

 

Thank you, appreciate the help!

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...