View previous topic :: View next topic |
Author |
Message |
bammbamm808 Guru


Joined: 08 Dec 2002 Posts: 557 Location: Hawaii
|
Posted: Thu Apr 10, 2025 10:28 pm Post subject: [SOLVED] 5.15.80 sees 2nd nvme ssd, 6.12.21 doesn't |
|
|
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? _________________ MSI MAG B550 Tomahawk
Ryzen 3900x
32Gb Samsung B-die (16GB dual rank x2) DDR4 @ 3200MHz, cl14
Geforce RTX 4070S 8GB
Samsung m.2 NVME pcie-3.0
Etc....
Last edited by bammbamm808 on Wed Apr 16, 2025 3:05 am; edited 3 times in total |
|
Back to top |
|
 |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1684 Location: Richmond Hill, Canada
|
Posted: Thu Apr 10, 2025 10:31 pm Post subject: |
|
|
What is "EFISP"? I cannot find any reference for the term. |
|
Back to top |
|
 |
GDH-gentoo Veteran


Joined: 20 Jul 2019 Posts: 1902 Location: South America
|
Posted: Thu Apr 10, 2025 10:51 pm Post subject: |
|
|
pingtoo wrote: | What is "EFISP"? I cannot find any reference for the term. |
OP probably meant the ESP of the Windows 10 drive. _________________
NeddySeagoon wrote: | I'm not a witch, I'm a retired electronics engineer  |
Ionen wrote: | As a packager I just don't want things to get messier with weird build systems and multiple toolchains requirements though  |
|
|
Back to top |
|
 |
keekkenen n00b

Joined: 05 Oct 2024 Posts: 71
|
Posted: Thu Apr 10, 2025 10:53 pm Post subject: Re: 5.15.80 sees 2nd nvme ssd, 6.12.21 doesn't |
|
|
bammbamm808 wrote: | 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 _________________ 7950x3d / x670e MSI Tomagawk / Sapphire RX 7800XT 16Gb / G.Skill 64Gb 5600 / A-Data Legend 960 2Tb (x2), A-Data SX8200PNP 256Gb |
|
Back to top |
|
 |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1684 Location: Richmond Hill, Canada
|
Posted: Thu Apr 10, 2025 11:07 pm Post subject: |
|
|
GDH-gentoo wrote: | pingtoo wrote: | 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,
bammbamm808 wrote: | 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 |
|
Back to top |
|
 |
bammbamm808 Guru


Joined: 08 Dec 2002 Posts: 557 Location: Hawaii
|
Posted: Fri Apr 11, 2025 12:17 am Post subject: |
|
|
pingtoo wrote: | What is "EFISP"? I cannot find any reference for the term. |
Apologies efi system partition. _________________ MSI MAG B550 Tomahawk
Ryzen 3900x
32Gb Samsung B-die (16GB dual rank x2) DDR4 @ 3200MHz, cl14
Geforce RTX 4070S 8GB
Samsung m.2 NVME pcie-3.0
Etc.... |
|
Back to top |
|
 |
bammbamm808 Guru


Joined: 08 Dec 2002 Posts: 557 Location: Hawaii
|
Posted: Fri Apr 11, 2025 12:19 am Post subject: |
|
|
pingtoo wrote: | 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. _________________ MSI MAG B550 Tomahawk
Ryzen 3900x
32Gb Samsung B-die (16GB dual rank x2) DDR4 @ 3200MHz, cl14
Geforce RTX 4070S 8GB
Samsung m.2 NVME pcie-3.0
Etc.... |
|
Back to top |
|
 |
pingtoo Veteran


Joined: 10 Sep 2021 Posts: 1684 Location: Richmond Hill, Canada
|
Posted: Fri Apr 11, 2025 12:36 am Post subject: |
|
|
bammbamm808 wrote: | pingtoo wrote: | 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. |
|
Back to top |
|
 |
bammbamm808 Guru


Joined: 08 Dec 2002 Posts: 557 Location: Hawaii
|
Posted: Fri Apr 11, 2025 1:12 am Post subject: |
|
|
pingtoo wrote: | bammbamm808 wrote: | pingtoo wrote: | 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. _________________ MSI MAG B550 Tomahawk
Ryzen 3900x
32Gb Samsung B-die (16GB dual rank x2) DDR4 @ 3200MHz, cl14
Geforce RTX 4070S 8GB
Samsung m.2 NVME pcie-3.0
Etc.... |
|
Back to top |
|
 |
bammbamm808 Guru


Joined: 08 Dec 2002 Posts: 557 Location: Hawaii
|
Posted: Fri Apr 11, 2025 1:55 am Post subject: |
|
|
pingtoo wrote: | bammbamm808 wrote: | pingtoo wrote: | 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. _________________ MSI MAG B550 Tomahawk
Ryzen 3900x
32Gb Samsung B-die (16GB dual rank x2) DDR4 @ 3200MHz, cl14
Geforce RTX 4070S 8GB
Samsung m.2 NVME pcie-3.0
Etc.... |
|
Back to top |
|
 |
bammbamm808 Guru


Joined: 08 Dec 2002 Posts: 557 Location: Hawaii
|
Posted: Fri Apr 11, 2025 8:19 am Post subject: |
|
|
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. _________________ MSI MAG B550 Tomahawk
Ryzen 3900x
32Gb Samsung B-die (16GB dual rank x2) DDR4 @ 3200MHz, cl14
Geforce RTX 4070S 8GB
Samsung m.2 NVME pcie-3.0
Etc.... |
|
Back to top |
|
 |
|