http://bugzilla.opensuse.org/show_bug.cgi?id=1205777 http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c1

--- Comment #1 from Johannes Kastl opensuse_buildservice@ojkastl.de --- New day, new errors. I am not sure if grub is somehow confused by the usb stick I have plugged as an external storage device. I'll remove it and see if it helps.

``` scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ** Invalid partition 3 ** Couldn't find partition mmc 0:3 ** Invalid partition 4 ** Couldn't find partition mmc 0:4 Scanning mmc 0:2... ** fs_devread read error - block ** fs_devread read error - block ** fs_devread read error - block bad tree block 2340093952, bytenr mismatch, want=2340093952, have=0 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 No EFI system partition BootOrder not defined EFI boot manager: Cannot load any image ** No partition table - mmc 0 ** Couldn't find partition mmc 0:2 ** No partition table - mmc 0 ** Couldn't find partition mmc 0:1 =>

```

``` error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0xee2aff0 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0xee2af80 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x1 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x87f0 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x8780 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x800 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0xee2aff0 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0xee2af80 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x8800 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0xee2aff0 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0xee2af80 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x1 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x87f0 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x8780 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x800 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0xee2aff0 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0xee2af80 from `hd1'. error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x8800 from `hd1'. error: ../../grub-core/commands/search.c:296:no such device: e590f1c9-3c90-4d9e-a0df-ff6e17559cf8. Loading Linux 6.0.8-1-default ... error: ../../grub-core/disk/efi/efidisk.c:602:failure reading sector 0x8880 from `hd1'. Loading initial ramdisk ... error: ../../grub-core/loader/arm64/efi/linux.c:300:you need to load the kernel first.

Press any key to continue... ```

http://bugzilla.opensuse.org/show_bug.cgi?id=1205777 http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c3

--- Comment #3 from Michal Suchanek msuchanek@suse.com --- Right, there is some bug in the rk3399 mmc driver in u-boot.

https://marc.info/?l=u-boot&m=165684945826950&w=2

No solution is known.

http://bugzilla.opensuse.org/show_bug.cgi?id=1205777 http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c5

--- Comment #5 from Michal Suchanek msuchanek@suse.com --- No I got sidetracked because I found a problem with i2c bus which happens even earlier in the boot sequence.

http://bugzilla.opensuse.org/show_bug.cgi?id=1205777 http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c6

--- Comment #6 from Stefan Seyfried seife@novell.slipkontur.de --- Johannes' machine is an allwinner sun50i, not a rk3399, but the problem might be similar.

http://bugzilla.opensuse.org/show_bug.cgi?id=1205777 http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c8

--- Comment #8 from Johannes Kastl opensuse_buildservice@ojkastl.de --- Sorry Michal for being to vague.

Yes, this is a Pine A64, A64-DB-2G Rev B, date on the board says 2016-03-21.

Kind Regards, Johannes

http://bugzilla.opensuse.org/show_bug.cgi?id=1205777 http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c9

--- Comment #9 from Johannes Kastl opensuse_buildservice@ojkastl.de --- What I fail to understand this far:

The board does not have a SPI flash (as far as I found out, so it needs to read the u-boot code from the sdcard (that for whatever reason is called mmc).

So the steps are: - board resets - board reads from sdcard from some offset - board boots into u-boot - u-boot fails to detect the sdcard OR u-boot is able to start grub, but grub fails to find the root device ("error: ../../grub-core/commands/search.c:296:no such device: e590f1c9-3c90-4d9e-a0df-ff6e17559cf8.") OR grub uses the wrong device ("failure reading sector 0x3786d40 from `hd1'.", which seems to have disappeared now that I removed the USB stick

If u-boot is booted, at least the board itself seems to find the sdcard. But u-boot does not? This would point to a bug in u-boot?

Kind Regards, Johannes

http://bugzilla.opensuse.org/show_bug.cgi?id=1205777 http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c11

--- Comment #11 from Johannes Kastl opensuse_buildservice@ojkastl.de --- Hi Michal,

Indeed, the situation is very much similar on rk3399 - the u-boot driver is likely missing a step in initializing the mmc bus or card.

This means there are two problems: - u-boot failing to detect the sdcard it was booted from - grub2 being loaded but failing to detect the root device or boot device or load the kernel or anything like that.

The latter one is the one, that I cannot solve even if the u-boot watchdog were working. A grub2 hanging with "Press any key to continue" makes the device unreachable and useless.

Any idea how to tackle that?

Kind Regards, Johannes

http://bugzilla.opensuse.org/show_bug.cgi?id=1205777 http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c13

--- Comment #13 from Johannes Kastl opensuse_buildservice@ojkastl.de --- Thanks Seife!

I gave this a try and now I am in a boot loop:

``` Booting /efi\boot\bootaa64.efi Please press 't' to show the boot menu on this console error: ../../grub-core/video/video.c:761:no suitable video mode found. error: ../../grub-core/commands/boot.c:196:you need to load the kernel first. resetting ... ```

Not sure why suddenly it does no longer show the grub2 console but rather asks for pressing 't'. I need to investigate what I did wrong :-)

But at least it seems like the automatic reboot is working.

Unfortunately it errors out after some loops:

``` U-Boot SPL 2022.10 (Oct 04 2022 - 00:00:00 +0000) DRAM: 2048 MiB Trying to boot from MMC1 spl: mmc init failed with error: -110 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### ```

But that might be the other error, the one where u-boot does not boot..

Kind Regards, Johannes

http://bugzilla.opensuse.org/show_bug.cgi?id=1205777 http://bugzilla.opensuse.org/show_bug.cgi?id=1205777#c15

--- Comment #15 from Matthias Brugger mbrugger@suse.com --- (In reply to Johannes Kastl from comment #9)

What I fail to understand this far:

The board does not have a SPI flash (as far as I found out, so it needs to read the u-boot code from the sdcard (that for whatever reason is called mmc).

So the steps are:

• board resets
• board reads from sdcard from some offset
• board boots into u-boot
• u-boot fails to detect the sdcard OR u-boot is able to start grub, but grub fails to find the root device

("error: ../../grub-core/commands/search.c:296:no such device: e590f1c9-3c90-4d9e-a0df-ff6e17559cf8.") OR grub uses the wrong device ("failure reading sector 0x3786d40 from `hd1'.", which seems to have disappeared now that I removed the USB stick

If u-boot is booted, at least the board itself seems to find the sdcard. But u-boot does not? This would point to a bug in u-boot?

Yes, Grub usese the EFI implementation of U-Boot to access the HW. And if U-Boot access to the SD card is buggy, so will be the access from Grub.