2018-07-30 14:23 GMT+03:00 Alexander Graf <[email protected]>: > Hi Matwey, > > On 07/29/2018 01:19 PM, Matwey V. Kornilov wrote: >> >> Hello, >> >> I am (stilL) trying to boot openSUSE on Rock64. I use JeOS image from >> Contrib:Rockchip and manually built bootloader (with >> 0001-XXX-openSUSE-XXX-Prepend-partition-.patch). And currently I see the >> following new issue: >> >> mmc1 is current device >> Scanning mmc 1:2... >> 52462 bytes read in 43 ms (1.2 MiB/s) >> Failed to mount ext2 filesystem... >> ** Unrecognized filesystem type ** >> Scanning mmc 1:1... >> Found EFI removable media binary efi/boot/bootaa64.efi >> reading efi/boot/bootaa64.efi >> 1247744 bytes read in 58 ms (20.5 MiB/s) >> ## Starting EFI application at 02000000 ... >> Card did not respond to voltage select! >> mmc_init: -95, time 10 >> Scanning disk [email protected]... >> Scanning disk [email protected]... >> Found 2 disks >> Welcome to GRUB! >> >> ethernet@ff540000 Waiting for PHY auto negotiation to complete......... >> TIMEOUT ! >> Could not initialize PHY ethernet@ff540000 >> GNU GRUB version 2.02 >> >> Minimal BASH-like line editing is supported. For the first word, TAB >> lists possible command completions. Anywhere else TAB lists possible >> device or file completions. >> >> >> >> grub> >> >> >> I see that both dtb file and EFI GRUB executable are loaded. But instead >> of GRUB menu I see GRUB command line. I suppose it means that grub >> failed to fetch GRUB configuration. How could I debug further what is >> wrong? > > > Correct. Grub failed to fetch the configuration because it failed to > initialize the prefix correctly. If you run "set" on the command line, you > should be able to see that the prefix is wrong. You can as interim step set > it manually using the set command and then run "normal". That should get you > a working grub menu. >
Indeed, the prefix is (hd0)/efi/boot, instead of (hd0,gpt1)/efi/boot. > The really important question is why grub could not determine its prefix > correctly though. What U-Boot version are you basing on? There were a few > bugs with the device path exposure in 2018.05 IIRC. I am running downstream u-boot with rock64 support: https://github.com/ayufan-rock64/linux-u-boot It is based on 2017.09 > > > Alex > -- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
