On Tuesday, October 2, 2018 12:19:14 PM CDT Andreas Färber wrote: > Am 02.10.18 um 04:38 schrieb Mark Petersen: > > On Monday, 1 October 2018 02:19:26 CDT Alexander Graf wrote: > >> On 01.10.18 05:01, Walter M. Peteren wrote: > >>> Has anyone gotten their rock64 to boot opensuse? > >>> > >>> I have ayufan's u-boot installed to SPI. > >>> > >>> The opensuse Tumbleweed JeOS image downloaded from https:// > >>> download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rockchi > >>> p/ > >>> images/ > >>> > >>> I've dd'ed the image to emmc and usb. The boot partition seems to start > >>> at > >>> the correct position 32768, but when the rock64 boots, I'm dropped to > >>> grub shell > >> > >> This is most likely because of a bug in the device path logic in u-boot > >> versions between 2017.09 and 2017.11. > >> > >>> grub> > >>> grub> ls > >>> > >>> yields (hd0) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) > >>> > >>> grub> set prefix=(hd0,gpt1)/efi/boot > >>> grub> set root=(hdo,gpt3) > >>> grub> set btrfs_relative_path=yes < yes or blank yields the same > >>> grub> normal > >>> > >>> yields the grub menu, and whether I chose Tumbleweed or failsafe I > > > > get: > >>> Loading kernel... > >>> Loading initrd... > >>> EFI stub: Booting Linux Kernel... > >>> EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied > >>> EFI stub: ERROR: Could not determine UEFI Secure Boot status. > >>> EFI stub: Using DTB from configuration table > >>> EFI stub: Exiting boot services and installing virtual address > >>> map > >>> > >>> and that's as far as it gets. > >> > >> That means Linux booted. It's a matter of fiddling with DT and kernel > >> command line options to also make it show something. > > > > Thanks for the reply. > > > > I've tried setting earlycon=uart8250,0xff130000 > > Have you tried just "earlycon" without parameters, as Alex suggested? > In your line above I'm missing mmio32. > > Regards, > Andreas
Andreas, Thanks for the reply. I've tried with just earlycon as well as earlycon=uart8250,mmio32,0xff130000 but there is no additional output on the serial console. - I don't believe the board is booting as the network adapter lights don't indicate any activity with and without a cable attached. I've tried using the boot loader from Arch but I end up with the same console ouput after the grub menu. I've also tried a newer JeOS image (2018-9-14-Build4.55) without success. Mark -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
