11-22-2015, 02:04 PM
Found this post saying problem likely caused by UEFI/(Bios) settings -- possibly solved by updating the firmware, if an update is available. Sounds like these types of systems are meant to boot in UEFI mode and the firmware is not set-up to properly handle Legacy/Bios mode booting. As you can read in rest of that thread, I had the OP run through various things to try getting it to work all to no avail.
Unfortunately, (assuming you don't find another solution), you may end up having to re-install everything (Windows and LL) in UEFI mode to get it working right.
P.s. Just for heck of it, run sudo blkid from terminal in live LL to see if UUID of LL on nvme disk matches that shown in your grub.conf output. If not, try editing it and see if that works. Other than that I'm afraid I have no idea how to get around the problem other than doing a UEFI-mode install.
Unfortunately, (assuming you don't find another solution), you may end up having to re-install everything (Windows and LL) in UEFI mode to get it working right.
P.s. Just for heck of it, run sudo blkid from terminal in live LL to see if UUID of LL on nvme disk matches that shown in your grub.conf output. If not, try editing it and see if that works. Other than that I'm afraid I have no idea how to get around the problem other than doing a UEFI-mode install.
Try Linux Beginner Search Engine for answers to Linux questions.