[SOLVED] 5.15.80 sees 2nd nvme ssd, 6.12.21 doesn't

[bammbamm808]

2 nvme m2 drives, one with Gentoo, one with Win10. My old kernel, 5.15.80, Sees the Win10 drive, which is where the Win bootloader is in the EFISP. lsblk and blkid both see it. I can mount the ESP and manipulate files there. My newer kernel is not aware of the Win10 drive at all. It doesn't even show in dmesg has causing an error or warning. Could I get some ideas on what kernel options need enabling in the the 6x kernel to acknowledge the second drive?

[pingtoo]

What is "EFISP"? I cannot find any reference for the term.

[GDH-gentoo]

What is "EFISP"? I cannot find any reference for the term.

OP probably meant the ESP of the Windows 10 drive.

[keekkenen]

Could I get some ideas on what kernel options need enabling in the the 6x kernel to acknowledge the second drive?

I think you need to check your kernel options (not only about nvme) by wikis form Pietinger

[pingtoo]

What is "EFISP"? I cannot find any reference for the term.

OP probably meant the ESP of the Windows 10 drive.

GDH-gentoo, Thanks

Let's assume that,

nvme m2 drives, one with Gentoo, one with Win10. My old kernel, 5.15.80, Sees the Win10 drive, which is where the Win bootloader is in the EFISP. lsblk and blkid both see it. I can mount the ESP and manipulate files there. My newer kernel is not aware of the Win10 drive at all. It doesn't even show in dmesg has causing an error or warning. Could I get some ideas on what kernel options need enabling in the the 6x kernel to acknowledge the second drive?

bammbamm808, from your signature, you noted that you have "Samsung m.2 NVME pcie-3.0" does the second NVMe is same brand/model?

I suspect you mean you you are not able to mount the NTFS file system for "Win10 drive" for your newer kernel.

can you share lsblk -f to verify if a device/partition detected by the newer kernel.
and lsmod to confirm no dynamic ntfs module loaded
and the newer kernel .config? to verify if any ntfs module configured

[bammbamm808]

What is "EFISP"? I cannot find any reference for the term.

Apologies efi system partition.

[bammbamm808]

I suspect you mean you you are not able to mount the NTFS file system for "Win10 drive" for your newer kernel.

can you share lsblk -f to verify if a device/partition detected by the newer kernel.
and lsmod to confirm no dynamic ntfs module loaded
and the newer kernel .config? to verify if any ntfs module configured

I mean, that the newer kernel does not detect the drive at all: no dmesg about it. It's not there in any sense under 6.12.22. That would make it difficult to mount, so technically correct.

[pingtoo]

I suspect you mean you you are not able to mount the NTFS file system for "Win10 drive" for your newer kernel.

can you share lsblk -f to verify if a device/partition detected by the newer kernel.
and lsmod to confirm no dynamic ntfs module loaded
and the newer kernel .config? to verify if any ntfs module configured

I mean, that the newer kernel does not detect the drive at all: no dmesg about it. It's not there in any sense under 6.12.22. That would make it difficult to mount, so technically correct.

In this case you need to share lspci -nnk to see under the new kernel configuration provide driver support.

[bammbamm808]

I suspect you mean you you are not able to mount the NTFS file system for "Win10 drive" for your newer kernel.

can you share lsblk -f to verify if a device/partition detected by the newer kernel.
and lsmod to confirm no dynamic ntfs module loaded
and the newer kernel .config? to verify if any ntfs module configured

I mean, that the newer kernel does not detect the drive at all: no dmesg about it. It's not there in any sense under 6.12.22. That would make it difficult to mount, so technically correct.

In this case you need to share lspci -nnk to see under the new kernel configuration provide driver support.

Will do.

[bammbamm808]

I suspect you mean you you are not able to mount the NTFS file system for "Win10 drive" for your newer kernel.

can you share lsblk -f to verify if a device/partition detected by the newer kernel.
and lsmod to confirm no dynamic ntfs module loaded
and the newer kernel .config? to verify if any ntfs module configured

I mean, that the newer kernel does not detect the drive at all: no dmesg about it. It's not there in any sense under 6.12.22. That would make it difficult to mount, so technically correct.

In this case you need to share lspci -nnk to see under the new kernel configuration provide driver support.

Thanks for the nudge. I had somehow ommited ahci, which is needed for my SECOND ATA controller, on which resides the nvme containing Windows.

[bammbamm808]

Seems the fix was intermittent. Sometimes kernel panic on trying, I guess to load the ahci driver for 2nd chipset, sometimes it works. I'm trying different kernels to see if there's something newer than 5.15.80 (which works perfectly). If not I can fall back to that. So far, 6.12.23 seems to be working. Still failing most boots. Back to 5x with full functionality. will poke around some more in menuconfig, but my eyes are crossing after hours spent doing that.

EDIT: Seems that the nvme I have on m.2_2 can be problematic for some folks. I have updated the firmware for the device and so far, seems to be working, even with 6.x kernels. More time needed to be sure, but it has worked for more cold boots consecutively than it ever did before.