From: 12345@whatismyemailaddress.xyz   
      
   On Mon, 30 May 2022 05:06:43 +0200, Aragorn wrote:   
      
   > On 30.05.2022 at 02:01, John Smith scribbled:   
   >   
   >> 	The system comes with a 500GB SSD storage device. Actually,   
   >> it is a device plugged into the motherboard directly - like a RAM   
   >> module - and identified at the Lenovo setup as an M2 Samsung device. We   
   >> added an old SATA hard drive as well, for that's where my wife's data   
   >> live - the idea is to use the M2 device for the OS, and the SATA drive   
   >> for her home directory. In the Lenovo setup, I made sure to disable the   
   >> Secure Boot feature, plus changed the boot order settings so I can boot   
   >> off the Slackware64 15.0 install USB stick.   
   >>   
   >> 	After doing all this, the system indeed boots off the USB   
   >> stick without any problems - without disabling Secure Boot the only   
   >> thing that boots is the preinstalled Windows.   
   >>   
   >> 	Everything seems to work fine, in that the kernel encounters   
   >> no problems with the hardware, and I can log in at the command line as   
   >> root in order to start launching the install.   
   >>   
   >> 	The problem arises when I try to identify the hard drives   
   >> available. When I do   
   >>   
   >> 	fdisk /dev/sda   
   >>   
   >> the hard drive identified is the SATA hard drive that we installed.   
   >> When I try with /dev/sdb, this is the Slackware64 15.0 USB stick. And   
   >> that's it. Much to my dismay, the M2 drive is not detected at all.   
   >> Anybody know why such is the case, and, more importantly, how to get   
   >> around it?   
   >   
   > M.2 drives and PCIe-mounted NVMe drives do not identify to userland as   
   > /dev/sd? device nodes.  Instead, you should look for /dev/nvme* nodes,   
   > e.g. /dev/nvme0n1p1 — the "-p1" at the end indicates the partition,   
   > while the characters in front of it indicate the drive.   
      
   	Very much appreciated for that piece of information - the   
   installation kernel indeed detects the M.2 drive at /dev/nvme0n1. The   
   installation seems to be proceeding without any issues.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)