That is exactly what we need to deal -- for Kernel4.18, build initramfs to include pcie and nvme 2 modules inside.
When Kernel is loaded, those modules can be instantiated immediately before re-mounting rootfs which we want to mount nvme device as rootfs.
There is another issue I found, lxde and mate desktop have some conflict with nvme disk.
When I use LXDE release image, after I login, the system hangs when MVMe disk is inserted (the red led on my PCIe -M.2 adapter is turned on, then off).
When I use minimal release image, MVMe disk is recognized (the red led on my PCIe -M.2 adapter is turned on and keeps on)
Based on minimal release image, I installed Ubuntu-Mate-Deskstop and LightDM. The systems works after I log in, but MVMe disk is not recognized (the red led on my PCIe -M.2 adapter is turned on, then off).
I think there are some Memory Address or IRQ conflict between GUI module and nvme module.
Could someone repeat and report the same issue, or it just happened to me?
When Kernel is loaded, those modules can be instantiated immediately before re-mounting rootfs which we want to mount nvme device as rootfs.
There is another issue I found, lxde and mate desktop have some conflict with nvme disk.
When I use LXDE release image, after I login, the system hangs when MVMe disk is inserted (the red led on my PCIe -M.2 adapter is turned on, then off).
When I use minimal release image, MVMe disk is recognized (the red led on my PCIe -M.2 adapter is turned on and keeps on)
Based on minimal release image, I installed Ubuntu-Mate-Deskstop and LightDM. The systems works after I log in, but MVMe disk is not recognized (the red led on my PCIe -M.2 adapter is turned on, then off).
I think there are some Memory Address or IRQ conflict between GUI module and nvme module.
Could someone repeat and report the same issue, or it just happened to me?
