![]() ![]() ![]() Are you able to load the UEFI Shell using boot6? If the problem only is access to disks, cloud you please provide screenshots for drivers, devices and read your posts in this thread, and it seems to me that you are turning in circles. Could you please try boot6 again with Clover 5146 and describe what the problem is with boot6. ![]() boot6 should not have this issue as it does not have BiosBlockIoDxe. The difference between boot6 and boot7 seems to be that boot6 is using UEFI drivers for hardware access while boot7 is using BIOS interrupts for hardware access. This was the line in your last attachment (handle might change on reboot):ĥA B - 1 1 128 PcieRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)Ĭonnect the device to the driver using the handles found above: This time please don’t change to fs0: either just stay on the default path to avoid using the disk drives.įind the handle for device “PcieRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)” near the top of the output of “devices -b”. Note that this should result in you losing access to both the USB and the SATA drive until you reboot, so only screenshot will be available. Note that in the previous attempt I choose the wrong device, but lspci shows that PcieRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) is the NVMe controller.Ĭould you please try disconnecting it and then connecting it to the NVMe driver. This is different from the hardware layout and is just the internal UEFI representation, but prevents the NVMe driver from attaching as it sees the device already having a driver. If the NVMe device is still not showing up in the output of map, could you please provide me a screenshot of the last connect commands so that I can see if anything failed and the output of “devices” and “drivers” without a reboot so that I can see if anything was changed by the above commands.Ĭould you please also try Clover 5146 using BDU v.028b from, I think that the problem is that all your disk drives are attached to the NVMe controller, probably by BiosBlockIoDxe. ![]() Note: Both the device and the driver should be near the end of the output, but you can change to paged output if you want to read the entire output:Ĭonnect the device to the driver using the handles found above (and connect the sub items, map -r is assigning fsX: numbers too): This was the line in your last attachment (handle might change on reboot):ġ02 00000010 ? - NVM Express Driver \EFI\CLOVER\drivers\BIOS\NvmExpressDxe_5.efi This was the line in your last attachment (handle might change on reboot):įind the handle for the “NVM Express Driver” in the output of “drivers”. If the NVMe device is not showing up in the output of map, please proceed with the next steps:įind the handle for device “PciRoot(0x1)/Pci(0x0,0x0)” in the output of “devices”. This could help making sure the Clover is seeing the same hardware as Linux, could you please try manually connecting the NVMe device to the NVMe driver. Linux has support for a lot of hardware and file systems, so should be possible to save the output, but a screenshot is fine too. iso can be made to a bootable USB using Rufus for example. In case you cannot make the USB drive work, could you please provide the output of just the new commands after the a clean reboot:Ĭould you also please provide the output of lspci from Linux on the same machine. If the USB drive disappears, you can try loading the driver first, but then devices need to be connected manually and you might not be able to save the output either: If successful, could you please capture the output of all of these: Unload BiosBlockIoDxe using the correct handle (4C in the example): Look for the handle of BiosBlockIoDxe (was 4C in the attached output, but might change on each boot): This should not disconnect access to the USB drive, but if it disappears you can just reboot the system to start over. Please try unloading it before loading the NVMe driver. I think that a lot of noise is because of BiosBlockIoDxe. Since the system has no UEFI firmware, there is no need for a bootable UEFI Shell, you can continue using the one that Clover has built in. Have you tried other methods of making it work? For example using DUET?Ĭould you please provide a link for the guide for installing Clover on a legacy BIOS system, I would like to try it in a virtual machine. Sorry, I did not realize previously that this is a legacy BIOS system. , thank you for the details and for being able to capture the output. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |