http://bugzilla.opensuse.org/show_bug.cgi?id=1079924 Bug ID: 1079924 Summary: Kernel initrd is missing vmd.ko kernel module during and after installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: valurolafsson@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- I tried installing Leap 42.3 on a new Dell Precision 7820 with a 1TB PCIe NVMe Class 40 SSD, connected through a Front Flexbay system. During install, the drive was not recognized/detected, which made it impossible for me to install Leap 42.3 on to the system. After looking into this, I found that the NVMe drive was connected through an "Intel RAID bus controller". This controller required the vmd.ko kernel module to function correctly during install. After getting help from the forums on how to load vmd.ko during install (https://forums.opensuse.org/showthread.php/528994-Unable-to-install-openSUSE...), I made a Driver Update Disk with the vmd.ko kernel module. I was able to get it to load before Yast installation was launched, so that I was able to see the NVMe drive during install and the installation process for Leap 42.3 worked perfectly. However, after install I rebooted, and the system was not able to detect the NVMe drive. I then booted into rescue mode (using my Driver Update Disk), mounted the NVMe drive, made a '01-dist.conf' file in /etc/dracut.conf.d containing the single line 'force_drivers+="vmd"', ran 'mkinitrd', and rebooted. The system was then able to find the NVMe drive and booted correctly into the freshly installed Leap 42.3. I'm guessing that these types of PCIe controllers will become more common, as more systems use PCIe NVMe drives. To avoid future complication installing openSUSE on such systems, it would be advisable to include vmd.ko into the initrd file (for both Leap 42.3 if possible, and any future Leap versions), both for the installation media and after the system has been installed. The controller in question has the following information after running 'hwinfo --storage' on Leap 42.3 running on my system: 103: PCI 1705.5: 0104 RAID bus controller [Created at pci.378] Unique ID: 0siH.saXLQ4XDZNB SysFS ID: /devices/pci0000:17/0000:17:05.5 SysFS BusID: 0000:17:05.5 Hardware Class: storage Model: "Intel RAID bus controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x201d SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x0000 Revision: 0x04 Driver: "vmd" Driver Modules: "vmd" Memory Range: 0x38007c000000-0x38007dffffff (ro,non-prefetchable) Memory Range: 0x92000000-0x93ffffff (rw,non-prefetchable) Memory Range: 0x38007ff00000-0x38007fffffff (rw,non-prefetchable) Module Alias: "pci:v00008086d0000201Dsv00008086sd00000000bc01sc04i00" Driver Info #0: Driver Status: vmd is active Driver Activation Cmd: "modprobe vmd" Config Status: cfg=no, avail=yes, need=no, active=unknown As can be seen above, the controller needs the 'vmd' kernel module to function. -- You are receiving this mail because: You are on the CC list for the bug.