Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#3710 - atlantic.ko (Marvell/Aqtion/Aqantia AQC107/108) 10Gbit 802.3bz Ethernet Driver not being built #8727

Open
openwrt-bot opened this issue Mar 29, 2021 · 1 comment
Labels

Comments

@openwrt-bot
Copy link

aenertia:

I have Several ASUS branded PCIe 10Gbit Cards based on the Aquantia Gen2 silicon, Some AQC107 based SFP+ modules and several ipq8074 boards with them. These work fine with the atlantic kernel driver which has been in mainline for some time.

Test build is x86_64 against the 21.02 tagged branch.

The 21.02 tagged branch (and the master, and 19.07) menuconfig for these cards do not appear despite the driver being present in the kernel source tree.

The lspci ID output of the card:

04:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:d107] (rev 02) Subsystem: ASUSTeK Computer Inc. XG-C100C [1043:8741] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [180 v1] Secondary PCI Express LnkCtl3: LnkEquIntrruptEn- PerformEqu- LaneErrStat: 0 Kernel driver in use: atlantic Kernel modules: atlantic

[aenertia@fedora build]$ lsmod |grep atlantic
atlantic 229376 0
macsec 61440 1 atlantic

Within the make kernel_menuconfig selection it is shown as a Y default, tristate flag when the x86_64 target is selected but never appears to get built into the resultant image.

On my comparison systems running RHEL8.3 and Fedora Rawhide - the atlantic kernel module has a dependency on the macsec kernel module - this is mentioned the 5.4 kernel source in the openwrt build tree for 21.02 tag - but seems to be silently dropped/skipped.

I tried several manual .config edits in the kernel build tree to force inclusion of the atlantic and macsec modules without success in the resultant images.
I note that there is a main kmod-macsec config entry in the primary .config buildroot ; but enabling that results in an architecture invalid for target error during kernel compilation. Is there perhaps a double up of the macsec name inside the build tree?

tl;dr Summary of required actions:

*Expose the Atlantic module/option in the main menuconfig buildroot
*Confirm why the atlantic module is set to Y by default, but not resulting in a usable driver in the kernel
*Check that the macsec module which appears to be a dependency for the atlantic driver does not have a naming conflict and/or why selecting it in the main buildroot results in an invalid arch error for x86_64 build target.

--

Severity ; the atlantic module is increasingly commonly deployed both in server, enthusiast and OEM embedded appliances (ipq80xx is a common pairing) as well as NBaseT SFP+ modules (rebadged by several vendors i.e Mikrotik) to supply NBaseT 10Gbit functionality. It has not been working in the last 2 openwrt releases and should be fixed before 21.02 goes out the door.

@jean1880
Copy link

Bumping, would be great if this could be resolved, bought the hardware and it is supported by the kernel source, just not the openwrt build for some reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants