Hi Leif, Thank you for your answer.
The eMMC is configured and recognized. I load the grub image from the eMMCs ESP partition. Only after loading and it when edk2 hands over control to the grub application I get an error that no resources are available to open the just used disk partition. The eMMC partition loader does not have any resources to read blocks from the eMMC. Scanning and accessing a USB drive does work though. We did encounter an additional hardware issue with the eMMC so I will wait until that is resolved to dig into the problem again. I might write again at that point. Best Sven From: Leif Lindholm <[email protected]> Date: Monday, 29. October 2018 at 9:03 PM To: Sven Auhagen <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [edk2] Grub Error Marvell Board Hi Sven, On Fri, Oct 26, 2018 at 02:08:16PM +0000, Sven Auhagen wrote: I have a Marvell Board like the MCBin with an Marvell 8040 CPU. A custom board? Is this using one of the platforms from edk2-platforms, or something from Marvell's repositories? EDK2 works fine, a Debian installer runs just fine. The problem comes after the installation. When I try to boot from the eMMC where the files were installed on grub seems not to find the partitions anymore: Tianocore/EDK2 firmware version MARVELL_EFI Press ESCAPE for boot options XhcCheckUrbResult: STALL_ERROR! Completecode = 6 XhcControlTransfer: error - Device Error, transfer - 2 XHCI: Don't support multi-TT feature for Hub now. (force to disable MTT) Well, this bit is USB related, so we can probably ignore it. Installed Fat filesystem on BE649F98 Installed Fat filesystem on BE80FE98 ...[Bds]Booting Debian Loading driver at 0x000B6732000 EntryPoint=0x000B6732400 Loading driver at 0x000B6732000 EntryPoint=0x000B6732400 error: no such partition. Entering rescue mode... grub rescue> grub rescue> ls (hd0) (hd1) (hd2) (hd3) grub rescue> set cmdpath=(hd1)/efi/debian prefix=(hd1,gpt2)/boot/grub root=hd1,gpt2 grub rescue> Has anyone an idea why this is happening or what could be the cause? Does your platform build configuration enable the eMMC? The easiest explanation would be if your EDK2 simply does not support the eMMC. As long as the hardware description tells Linux about it, the kernel can access it even when the firmware does not know how to use it. Best Regards, Leif Beste Grüße/Best Regards Sven Auhagen Dipl. Math. oec., M.Sc. Voleatech GmbH HRB: B 754643 USTID: DE303643180 Grathwohlstr. 5 72762 Reutlingen Tel: +49 7121539550 Fax: +49 7121539551 E-Mail: [email protected] www.voleatech.de<https://www.voleatech.de> Diese Information ist ausschließlich für den Adressaten bestimmt und kann vertraulich oder gesetzlich geschützte Informationen enthalten. Wenn Sie nicht der bestimmungsgemäße Adressat sind, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Anderen als dem bestimmungsgemäßen Adressaten ist es untersagt, diese E-Mail zu lesen, zu speichern, weiterzuleiten oder ihren Inhalt auf welche Weise auch immer zu verwenden. Für den Adressaten sind die Informationen in dieser Mail nur zum persönlichen Gebrauch. Eine Weiterleitung darf nur nach Rücksprache mit dem Absender erfolgen. Wir verwenden aktuelle Virenschutzprogramme. Für Schäden, die dem Empfänger gleichwohl durch von uns zugesandte mit Viren befallene E-Mails entstehen, schließen wir jede Haftung aus. _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
