On Thu, Apr 20, 2017 at 5:21 AM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > [Not sure what happens but when I try to Reply TB hangs; sorry for > broken thread] > > 19.04.2017 21:45, Manuel Lauss пишет: >> Hi Andrei, >> >> On Wed, Apr 19, 2017 at 8:09 PM, Andrei Borzenkov > <arvidj...@gmail.com> wrote: >>> 19.04.2017 20:31, Manuel Lauss пишет: >>>> Hi Andrei, >>>> >>>> On Wed, Apr 19, 2017 at 7:15 PM, Andrei Borzenkov > <arvidj...@gmail.com> wrote: >>>>> 19.04.2017 14:47, Manuel Lauss пишет: >>>>>> Hello, >>>>>> >>>>>> I'm trying to get grub running on an EFI system which only has a > NVMe disk. >>>>>> My problem is that when grub is launched by EFI (from the ESP), it >>>>>> does not see any disks at all, >>>>>> 'ls' just prints "(proc)" and nothing more. Is there a way to get >>>>>> grub to recognize the disk >>>>>> the firmware has loaded it from? >>>>>> >>>>>> It's installed this way, /boot/efi is /dev/nvme0n1p2, which is the >>>>>> ESP. Version is 2.02_rc2 >>>>>> grub-install --efi-directory=/boot/efi --no-nvram --target=x86_64-efi >>>>>> --compress=xz --themes="breeze" /dev/nvme0n1p2 >>>>>> >>>>> >>>>> GRUB relies on EFI for disk access and needs BlockIO protocol on device >>>>> so it can work with it. It may be that EFI NVMe driver on your system >>>>> does not implement it. Can you boot EFI shell on your system? This > could >>>>> be used to verify what protocols are present for which device. >>>> >>>> Yes EFI Shell is available, and can be used to e.g. start the grub > efi binary >>>> on the nvme device just fine. >>> >>> Could you run >>> >>> dh -d >>> >>> in EFI shell and send me result? You can redirect output to file on ESP >>> using standard syntax >>> >>> dh -d > dh.out >> >> It is attached. I guess entry 0x60 is the relevant NVMe one. >> > > > No, this is likely > > 179: DevPath (..0x1,25-07-B0-71-C2-38-25-00))DiskIo BlkIo > Controller Name : SAMSUNG MZVKW1T0HMLH-00000 > Device Path : > PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,25-07-B0-71-C2-38-25-00) > Controller Type : BUS > Configuration : NO > Diagnostics : NO > Managed by : > Drv[117] : Generic Disk I/O Driver > Drv[118] : Partition Driver(MBR/GPT/El Torito) > Parent Controllers : > Parent[149] : NVMe Mass Storage Controller > Child Controllers : > Child[17A] : NTFS File System [449MB] > Child[17B] : FAT File System > Child[17C] : > PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,25-07-B0-71-C2-38-25-00)/HD(3,GPT,CD3F6DDD-2517-43DD-8474-B00C1AF9E700,0x113000,0x8000) > Child[17D] : NTFS File System [74GB] > Child[17E] : > PciRoot(0x0)/Pci(0x1,0x1)/Pci(0x0,0x0)/NVMe(0x1,25-07-B0-71-C2-38-25-00)/HD(5,GPT,539BD179-6BB4-453A-AAB6-E9E254B55F82,0x95ED000,0x6DDD028F) > > and it looks entirely OK. Could you test current GRUB GIT or at least > 2.02~rc2? If problem still persists, please open bug report on > https://savannah.gnu.org/projects/grub
I've patched 2.02-rc2 to match git head, installed it, but no disks visible. Do I have to add a special module to grub (i.e. one of the files in /usr/lib/grub/x86_64-efi/) or is this enabled in the core with a special configure switch? Thanks! Manuel _______________________________________________ Help-grub mailing list Help-grub@gnu.org https://lists.gnu.org/mailman/listinfo/help-grub