Bug 23263 - mlx5 driver missing
Summary: mlx5 driver missing
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-01 18:52 CEST by Pascal Terjan
Modified: 2018-07-04 17:57 CEST (History)
2 users (show)

See Also:
Source RPM: kernel
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pascal Terjan 2018-07-01 18:52:15 CEST 
When trying to install Mageia on Packet.net c2.medium.x86 which comes with 2 Mellanox 10Gbps adapters the installer failed to find a network adapter both in Mageia 6 and Cauldron.

I ended up installing one of their provided distributions:

# cat /sys/class/net/*/device/uevent 
DRIVER=mlx5_core
PCI_CLASS=20000
PCI_ID=15B3:1015
PCI_SUBSYS_ID=15B3:0016
PCI_SLOT_NAME=0000:01:00.0
MODALIAS=pci:v000015B3d00001015sv000015B3sd00000016bc02sc00i00
DRIVER=mlx5_core
PCI_CLASS=20000
PCI_ID=15B3:1015
PCI_SUBSYS_ID=15B3:0016
PCI_SLOT_NAME=0000:01:00.1
MODALIAS=pci:v000015B3d00001015sv000015B3sd00000016bc02sc00i00

And indeed we don't have MLX5 in our kernel:

[pterjan@mageia kernel]$ grep -r MLX5
PATCHES/configs/i386.config:# CONFIG_MLX5_CORE is not set
PATCHES/configs/x86_64.config:# CONFIG_MLX5_CORE is not set
Marja Van Waes 2018-07-02 07:18:29 CEST

Assignee: bugsquad => kernel
CC: (none) => marja11

Comment 1 Thomas Backlund 2018-07-02 11:50:02 CEST 
Oooh, wonder how I missed that one :/

Anyway, fix queued for next mga6 and Cauldron kernel

CC: (none) => tmb

Comment 2 Thomas Backlund 2018-07-02 14:28:22 CEST 
Cauldron kernel-4.17.3-2.mga7 building
Comment 3 Thomas Backlund 2018-07-02 20:55:46 CEST 
With the now built/uploaded kernel-4.17.3-2.mga7 and drakx-installer-images-2.51-1.mga7 a cauldron install should work
Comment 4 Pascal Terjan 2018-07-04 17:57:52 CEST 
Thanks for the quick update, I tried last night and I can confirm the 2 interfaces are now detected by stage1 and networking is working.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.