Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#68704 - [mkinitcpio] unable to boot intel nvme after install due to missing vmd module

Attached to Project: Arch Linux
Opened by Vinay S Shastry (shastry) - Sunday, 22 November 2020, 03:42 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 21 April 2021, 11:29 GMT
Task Type Bug Report
Category Packages: Core
Status Assigned
Assigned To Giancarlo Razzolini (grazzolini)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 9
Private No


A fresh install is unable to boot from intel nvme due to missing module "vmd".

The nvme device doesn't show up during initrd due to this. The missing root device causes boot failure.

mkinitcpio should include vmd in block hook by default.

Add vmd to mkinitcpio.conf MODULES array.

Additional info:
* mkinitcpio 29-1
* HOOKS=(base systemd keyboard autodetect modconf block sd-encrypt sd-lvm2 filesystems fsck)
* dracut included the module in:
* Related:

$ hwinfo --storage
24: PCI 0e.0: 0104 RAID bus controller
[Created at pci.386]
Unique ID: vuMS.gpb2qBSjMtD
SysFS ID: /devices/pci0000:00/0000:00:0e.0
SysFS BusID: 0000:00:0e.0
Hardware Class: storage
Device Name: "Onboard - Other"
Model: "Intel Volume Management Device NVMe RAID Controller"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x9a0b "Volume Management Device NVMe RAID Controller"
SubVendor: pci 0x8086 "Intel Corporation"
SubDevice: pci 0x0000
Driver: "vmd"
Driver Modules: "vmd"
Memory Range: 0x603c000000-0x603dffffff (rw,non-prefetchable)
Memory Range: 0x50000000-0x51ffffff (rw,non-prefetchable)
Memory Range: 0x603f100000-0x603f1fffff (rw,non-prefetchable)
Module Alias: "pci:v00008086d00009A0Bsv00008086sd00000000bc01sc04i00"
Driver Info #0:
Driver Status: vmd is active
Driver Activation Cmd: "modprobe vmd"
Config Status: cfg=new, avail=yes, need=no, active=unknown

28: PCI e100.0: 0108 Non-Volatile memory controller (NVM Express)
[Created at pci.386]
Unique ID: bGtE.DDz_x3DkYn0
Parent ID: 7KSl.T0Q3BSb1PJ9
SysFS ID: /devices/pci0000:00/0000:00:0e.0/pci10000:e0/10000:e0:1d.0/10000:e1:00.0
SysFS BusID: 10000:e1:00.0
Hardware Class: storage
Model: "Intel SSD 660P Series"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0xf1a8 "SSD 660P Series"
SubVendor: pci 0x8086 "Intel Corporation"
SubDevice: pci 0x390d
Revision: 0x03
Driver: "nvme"
Driver Modules: "nvme"
Memory Range: 0x50000000-0x50003fff (rw,non-prefetchable)
IRQ: 2147483648 (no events)
Module Alias: "pci:v00008086d0000F1A8sv00008086sd0000390Dbc01sc08i02"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (PCI bridge)
This task depends upon

Comment by Alexander Epaneshnikov (erik_pro) - Sunday, 14 March 2021, 00:27 GMT
ran into this issue on HP Pavilion Laptop 15-eg0xxx
Comment by David Rosenstrauch (darose) - Wednesday, 21 April 2021, 12:45 GMT
Me as well, on a Dell Inspiron 5406. Seems like a number of newer laptops use Intel VMD.
Comment by Brian Clausen (Sparereach) - Sunday, 06 June 2021, 18:22 GMT
Experienced this as well on the Asus Zenbook UX325.
Comment by Ramdip Gill (ekzyis) - Tuesday, 06 July 2021, 08:36 GMT
Also experienced this on a Dell XPS 13 9310
Comment by Panayotis (teras) - Saturday, 11 September 2021, 14:07 GMT
This is a "me too" message -- Dell 9710. Please please add it as default :)
Comment by Vlatko B (vlatkoB) - Sunday, 03 October 2021, 06:19 GMT
"me too" on Asus TUF F17
Comment by nl6720 (nl6720) - Sunday, 03 October 2021, 06:29 GMT Comment by Sergey Kvachonok (ravenexp) - Tuesday, 05 October 2021, 18:47 GMT
"me too" on Asus VivoBook S435E