grub4efi - request uefi drivers list utility

[steve6375]

Would it be possible to list UEFI drivers that are currently loaded? Specifically, it would be nice to be able check if the UEFI BIOS already contains an NTFS driver and so can access NTFS partitions as well as FAT partitions. P.S. Does grub4efi add drivers and so would affect this list, or does grub4efi use its own code to access filesystems?

[a1ive]

Would it be possible to list UEFI drivers that are currently loaded? Specifically, it would be nice to be able check if the UEFI BIOS already contains an NTFS driver and so can access NTFS partitions as well as FAT partitions.

Yes it's possible. But I won't have time for the next few months.

P.S. Does grub4efi add drivers and so would affect this list, or does grub4efi use its own code to access filesystems?

G4E is NOT a UEFI driver. A "UEFI application" cannot be a "UEFI driver". "UEFI driver" is a special type of executable that has a different entry point and is loaded in a different way to a normal "UEFI application".

does grub4efi use its own code to access filesystems?

Yes. G4E and GRUB2 uses Block I/O Protocol to read and write to disk, while rEFInd uses Simple Filesystem Protocol to access files, so these drivers can be used for rEFInd/Shell, but not for G4E/GRUB2.

[yaya2007]

可以使用uuid，vol，map --status函数获得有关驱动器的信息。 具体还想知道什么?

[steve6375]

I want to know if the UEFI environment contains an NTFS (and exFAT) driver. All UEFI BIOSes support FAT, but some UEFI BIOSes also have extra filesystem drivers such as NTFS or exFAT. When you directly boot to an OS on an NTFS volume (or VHD on NTFS), it will need to use the UEFI drivers to access the files on the NTFS filesystem If the UEFI BIOS does not include any NTFS diver, then we could load an NTFS UEFI driver using the grub4efi load command. However, if the UEFI BIOS already has an NTFS driver, it would be safer to not load another NTFS driver as it is not needed.

The UEFI Shell 'drivers' command lists drivers, but we need the same command in grub4efi so we can determine if an NTFS driver is already present or not.

[a1ive]

可以使用uuid，vol，map --status函数获得有关驱动器的信息。 具体还想知道什么?

不是 ”驱动器”。 他是想列出所有 UEFI 驱动，或者查找包含指定名字的 UEFI 驱动是否存在。

[yaya2007]

嗷，明白了。搞笑了。

[a1ive]

嗷，明白了。搞笑了。

比如他想判断uefi固件是否支持从exfat分区启动，就要列出所有已安装的驱动，查找驱动名字里面有没有带"exfat"的。 可以参考 https://github.com/a1ive/grub/blob/259a9e8ce51a0fb81f3f656024ab6ec78401507a/grub-core/map/efi/vdisk.c#L73

[yaya2007]

是不是你想要的. BOOTX64.rar.txt

[steve6375]

Thanks! great work! :-) Just a few small issues:

1. Help not displaying properly

2. Redirect to file formatting

This makes it difficult to parse maybe better as single column (e.g. uefidriver --list) for example, how would you get just the full name of an NTFS driver from the list by parsing? Why do you use comma . and not period . ???

3. line feed after command?

4. name and help description 'uefidriver' 'get uefi driver' is not good description - better as 'uefidrivers - list uefi drivers' shell equivalent command is 'drivers' not 'driver'

Query: If I add a driver using 'load' it does not appear in list. Is this expected? If so, maybe uefidrivers help should say 'list inbuilt BIOS UEFI drivers' ?

[a1ive]

@yaya2007 你列出的是 COMPONENT_NAME2_PROTOCOL 还是 COMPONENT_NAME_PROTOCOL ？

[yaya2007]

是name2

[steve6375]

Shell (grubfm shell) loads same driver and shows it in list

[a1ive]

是name2

我好像误导你了，应该用 EfiDriverBindingProtocol https://github.com/tianocore/edk2/blob/0ecdcb6142037dd1cdd08660a2349960bcf0270a/MdePkg/Include/Protocol/DriverBinding.h 枚举 DriverBindingProtocol，再从每个 handle 上打开 ComponentName2Protocol，再获取名称

[yaya2007]

在我的惠普笔记本上，无论是是 COMPONENT_NAME2_PROTOCOL 还是 COMPONENT_NAME_PROTOCOL，都不支持。不知道EfiDriverBindingProtocol 是否会普遍支持（如果仍然要打开ComponentName2Protocol，估计够呛）。 使用 COMPONENT_NAME2_PROTOCOL 或者 COMPONENT_NAME_PROTOCOL，返回的列表信息已经可以判断 UEFI 是否支持 NTFS 或者 exFAT 启动，继而加载相关缺失的驱动。

上一版本是为了充分利用屏幕，一行显示2项内容。但是保存到内存，丢失排版信息，所以显示混乱。 这一版是一行显示一项内容。

如果觉得使用EfiDriverBindingProtocol比较妥当，那就等a1ive有时间再打补丁，我不想费神了。 BOOTX64.rar.txt

[a1ive]

好吧，等我有时间了再改一下。

[steve6375]

thanks. I prefer uefidrivers as the command rather than uefidriver