Re: to enable nvme
Samuel Thibault <[email protected]>
| Newsgroups | gmane.linux.debian.ports.hurd |
|---|---|
| Organization | I am not organized |
| Message-ID | <anUHBZamYIxM4mmZ@end> |
Hello, [email protected], le jeu. 06 août 2026 22:04:38 +0000, a ecrit: > On 7/24/26 03:35, Samuel Thibault wrote: > > [email protected], le ven. 24 juil. 2026 04:26:50 +0000, a ecrit: > > > I attached this quilt patch which modified a Makefile which I hoped would > > > enable nvme. Is this what I have to do prior to compiling rumpkernel to > > > enable nvme? > > Trying is the best of knowing if there are still issues. > > > > Samuel > > I think we can test it with qemu nvme driver. I modified the patch to > include only ld, ld_nvme, and nvme. > > Isn't nvmectl necessary? I seem not able to find it compiled anywhere. Probably only to manage namespaces and whatnot of nvme devices, but not really required to access the disk. Linux itself doesn't have nvmectl when booting off nvme. > So I get into grub and I can see the device as (hd0,msdos2), but changing > the root device from wd0 to nvme0ns1, ld_nvme0ns1 or something leads to boot > error "ext2fs: part:2:device:wd0: no such device or address". What is the > correct root device name for nvme? I don't know, but doesn't the boot log show what the rumpdisk kernel detected as disks? > It also says (Flash mass storage, NVMe I/O, revision 0x02) at pci0 dev 4 > function 0 not configured. There are similar messages for ethernet, vga > display, and miscellaneous bridge. Perhaps there is more to it than just add the files mentioned above, to enable the actual use of the driver. > Is it appropriate to send screenshot attachments in this list? Sure! Samuel