Hello everyone, I'm facing a weird problem. I've recently rented a PC - ASUS G21CX, which comes with 2 disks:
- NVME SSD Intel 660p 512Gi - SATA HDD Toshiba 1Ti
Obviously it arrived with Windows 10 installed and want to install Fedora on it, however Fedora Live image does not recognize NVME drive, like it's not even there. HDD is available as /dev/sda as expected. dmesg and journalctl does not show any errors except some usb-related failures, but I don't think it's related in any way.
Windows and BIOS both recognize the disk. I've disabled the Secure Boot feature but that had no effect.
I've tried both Workstation image and KDE image (which I intent to use). I was hoping to see something else on other distros, but no other live image managed to boot on this machine. I've tried Ubunut 20.04 LTS, Manjaro KDE, PopOS with nVidia drivers all are getting stuck at boot.
The rest of the hardware:
- Motherboard Chipset: Intel Z390 (Cannon Lake-H) - Core i7-9700K - ASUS RTX 2070
BIOS settings are almost as limited as a laptop, but nothing unusual from what I can tell.
Do you have any pointers or ideas what could it be and how to fix it? --- Best regards, Alex
On Thu, 13 Aug 2020 at 07:16, Alex Gurenko via users < users@lists.fedoraproject.org> wrote:
Hello everyone, I'm facing a weird problem. I've recently rented a PC - ASUS G21CX, which comes with 2 disks:
- NVME SSD Intel 660p 512Gi
- SATA HDD Toshiba 1Ti
Obviously it arrived with Windows 10 installed and want to install Fedora on it, however Fedora Live image does not recognize NVME drive, like it's not even there. HDD is available as /dev/sda as expected. *dmesg* and *journalctl* does not show any errors except some usb-related failures, but I don't think it's related in any way.
Windows and BIOS both recognize the disk. I've disabled the Secure Boot feature but that had no effect.
Intel has a publication for you:
https://www.intel.com/content/dam/support/us/en/documents/memory-and-storage...
On Thu, 13 Aug 2020 10:16:26 +0000 Alex Gurenko via users wrote:
Do you have any pointers or ideas what could it be and how to fix it?
I can say that the fedora 32 live image had no problem installing on my new desktop system which only has NVME storage, so there isn't a general problem with fedora and NVME, must be something specific to that system.
You could turn the process inside out - use the windows virtualization code to install fedora in a windows virtual machine, then run that in full screen :-).
On Thu, 2020-08-13 at 08:48 -0400, Tom Horsley wrote:
On Thu, 13 Aug 2020 10:16:26 +0000 Alex Gurenko via users wrote:
Do you have any pointers or ideas what could it be and how to fix it?
I can say that the fedora 32 live image had no problem installing on my new desktop system which only has NVME storage, so there isn't a general problem with fedora and NVME, must be something specific to that system.
You could turn the process inside out - use the windows virtualization code to install fedora in a windows virtual machine, then run that in full screen :-). _______________________________________________
It might be worth checking:
If the UEFI does not "see" the SSD then check the status of the Protective MBR boot flag using gdisk/fdisk To CLEAR the flag gdisk /dev/sda p ; v ; x ; n ; w ; To SET/CLEAR the flag fdisk /dev/sda M ; i ; a ; i ; w ; q ;
John
I recently had a lenovo laptop with windows 10 preinstalled, and the nvme did not show up. If you go into bios and turn off the raid setting, then it showed up. Of course, no more windows if you do this.
On Thu, Aug 13, 2020 at 9:02 AM ja ja@jaa.org.uk wrote:
On Thu, 2020-08-13 at 08:48 -0400, Tom Horsley wrote:
On Thu, 13 Aug 2020 10:16:26 +0000 Alex Gurenko via users wrote:
Do you have any pointers or ideas what could it be and how to fix it?
I can say that the fedora 32 live image had no problem installing on my new desktop system which only has NVME storage, so there isn't a general problem with fedora and NVME, must be something specific to that system.
You could turn the process inside out - use the windows virtualization code to install fedora in a windows virtual machine, then run that in full screen :-). _______________________________________________
It might be worth checking:
If the UEFI does not "see" the SSD then check the status of the Protective MBR boot flag using gdisk/fdisk To CLEAR the flag gdisk /dev/sda p ; v ; x ; n ; w ; To SET/CLEAR the flag fdisk /dev/sda M ; i ; a ; i ; w ; q ;
John
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
You can fix your Windows install to work with AHCI. I did this on my Dell XPS 13 and the only issue I had was it triggered a bitlocker recovery. After entering the recovery key it's been all good. https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-id... On Thu, 2020-08-13 at 11:02 -0400, Neal Becker wrote:
I recently had a lenovo laptop with windows 10 preinstalled, and the nvme did not show up. If you go into bios andturn off the raid setting, then it showed up. Of course, no more windows if you do this.
On Thu, Aug 13, 2020 at 9:02 AM ja ja@jaa.org.uk wrote:
On Thu, 2020-08-13 at 08:48 -0400, Tom Horsley wrote:
On Thu, 13 Aug 2020 10:16:26 +0000
Alex Gurenko via users wrote:
Do you have any pointers or ideas what could it be and how to
fix it?
I can say that the fedora 32 live image had no problem installing
on my new desktop system which only has NVME storage, so there
isn't a general problem with fedora and NVME, must be something
specific to that system.
You could turn the process inside out - use the windows
virtualization
code to install fedora in a windows virtual machine, then run
that
in full screen :-).
It might be worth checking:
If the UEFI does not "see" the SSD then check
the status of the Protective MBR boot flag using gdisk/fdisk
To CLEAR the flag gdisk /dev/sda p ; v ; x ; n ; w ;
To SET/CLEAR the flag fdisk /dev/sda M ; i ; a ; i ; w ; q ;
John
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
_______________________________________________users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 8/13/2020 11:06 AM, Kevin Becker wrote:
You can fix your Windows install to work with AHCI. I did this on my Dell XPS 13 and the only issue I had was it triggered a bitlocker recovery. After entering the recovery key it's been all good.
https://support.thinkcritical.com/kb/articles/switch-windows-10-from-raid-id...
On Thu, 2020-08-13 at 11:02 -0400, Neal Becker wrote:
I recently had a lenovo laptop with windows 10 preinstalled, and the nvme did not show up. If you go into bios and turn off the raid setting, then it showed up. Of course, no more windows if you do this.
On Thu, Aug 13, 2020 at 9:02 AM ja <ja@jaa.org.uk mailto:ja@jaa.org.uk> wrote:
On Thu, 2020-08-13 at 08:48 -0400, Tom Horsley wrote:
On Thu, 13 Aug 2020 10:16:26 +0000 Alex Gurenko via users wrote:
Do you have any pointers or ideas what could it be and how to
fix it?
I have a Del XPS 8930 that Fedora did not see the NVME SSD when I tried to install on it. All I had to do to get it to be visible was to change the BIOS from RAID to AHCI. On my machine, Windows didn't seem to care which it was, but that made it visible to Fedora.