Regression #14534
closed
Cavium ``qlnxe`` / ``if_qlnxe`` driver is not present
Added by Nikolaos Astyrakakis over 1 year ago.
Updated about 1 year ago.
Category:
Hardware / Drivers
Plus Target Version:
23.09
Affected Architecture:
amd64
Description
Interfaces using qlnxe driver are not appearing in 2.7.0 version.
I added if_qlnxe_load="YES" but the interfaces are not appearing.
Nikolaos Astyrakakis wrote:
Interfaces using qlnxe driver are not appearing in 2.7.0 version.
I added if_qlnxe_load="YES" but the interfaces are not appearing.
Was this working on a previous release and broke in 2.7.0? Or has this never worked?
Kris Phillips wrote in #note-1:
Nikolaos Astyrakakis wrote:
Interfaces using qlnxe driver are not appearing in 2.7.0 version.
I added if_qlnxe_load="YES" but the interfaces are not appearing.
Was this working on a previous release and broke in 2.7.0? Or has this never worked?
It was working on 2.6.0.
Actually, functionality was added on 2.6.0
Check Feature #11750
- Tracker changed from Bug to Regression
- Subject changed from Qlnxe driver is not working. to Cavium ``qlnxe`` / ``if_qlnxe`` driver is not present
- Priority changed from Very High to Normal
- Target version set to 2.8.0
- Plus Target Version set to 23.09
I don't see the module in the builds or in the kernel configuration, but the string for it is still in MODULES_OVERRIDE
as though it should be included. It's possible something in that driver changed upstream.
- Related to Feature #11750: Support for network interfaces using the ``qlnxe`` driver added
Jim Pingle wrote in #note-3:
I don't see the module in the builds or in the kernel configuration, but the string for it is still in MODULES_OVERRIDE
as though it should be included. It's possible something in that driver changed upstream.
Well, then we cannot update to 2.7.0 from 2.6.0 unless the driver is included in 2.7.x.
We are using Synology E10G21-F2 network card with 2 x 10G SFP+ ports that is based on Marvell FastLinQ 41000 Series network card. The card works fine in 2.6.0 version, for connection with WAN and LAN switches.
Is there any work-around to resolve this issue in 2.7.0?
- Assignee set to Christian McDonald
I see the problem. I'm running a test build now to confirm. This will be resolved in the next release.
- Status changed from New to Feedback
- Status changed from Feedback to Resolved
- Target version changed from 2.8.0 to 2.7.1
Also available in: Atom
PDF