Still no luck. No signal at video, no text in console after EFI stub. Any ideas why?
2017-09-04 14:25 GMT+03:00 Matwey V. Kornilov <matwey.korni...@gmail.com>: > After some time, the ethernet leds begin to blink, but no requests to > dhcp. something is alive inside still... > > 2017-09-04 11:17 GMT+03:00 Matwey V. Kornilov <matwey.korni...@gmail.com>: >> Hm, console=ttyS2,1500000 supposed to work, but it doesnt... >> >> 2017-09-04 11:00 GMT+03:00 Matwey V. Kornilov <matwey.korni...@gmail.com>: >>> Booting a command list >>> >>> Loading linux.vmx... >>> Loading initrd.vmx... >>> 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... >>> >>> Hm... Seems to be no consoie from the kernel >>> >>> 2017-09-02 13:29 GMT+03:00 Matwey V. Kornilov <matwey.korni...@gmail.com>: >>>> 2017-09-02 13:25 GMT+03:00 Andreas Färber <afaer...@suse.de>: >>>>> Hi, >>>>> >>>>> Am 02.09.2017 um 12:06 schrieb Matwey V. Kornilov: >>>>>> 1. Tools from https://github.com/rockchip-linux/rkbin are required to >>>>>> prepare u-boot binary to be deployed into sd-card. The tools are >>>>>> permitted to be redistributed, but they are x86_64-only binary blobs. >>>>>> I think we could package them in RPM package and wrap them using >>>>>> qemu-linux-x86_64 to execute them at JeOS building phase (at aarch64 >>>>>> architecture). >>>>> >>>>> Negative. Same topic came up for Amlogic, and I had to develop the >>>>> native Open Source meson-tools instead. >>>>> >>>>> For creating a JeOS image we need to use U-Boot SPL, which as I already >>>>> pointed out should avoid all those binary-only x86 tools. >>>>> >>>>> If that is not working yet (you did not say), then we can just document >>>>> the x86-only steps to keep them out of OBS. >>>>> >>>> >>>> Well, I didn't find any U-Boot SPL implementation for RK3328 in any >>>> u-boot trees. That is the issue currently. >>>> >>>>>> 2. bootloader are required to be placed at +16MB offset from the >>>>>> beginning of SD card. We have to find a way to specify KIWI to place >>>>>> EFI partition not at 2048sector as default. >>>>> >>>>> Yousaf gave a presentation on how to accomplish that for RK3399. >>>>> >>>>> If this reservation is implemented, then similar to my JeOS-nanopik2 >>>>> image we could just leave out U-Boot and give users Wiki instructions on >>>>> how to place U-Boot there themselves. >>>>> >>>>> You had forgotten to create an HCL Wiki page - I stubbed one out: >>>>> >>>>> https://en.opensuse.org/HCL:Rock64 >>>>> >>>>> Regards, >>>>> Andreas >>>>> >>>>> -- >>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany >>>>> GF: Felix Imendörffer, Jane Smithard, Graham Norton >>>>> HRB 21284 (AG Nürnberg) >>>> >>>> >>>> >>>> -- >>>> With best regards, >>>> Matwey V. Kornilov >>> >>> >>> >>> -- >>> With best regards, >>> Matwey V. Kornilov >> >> >> >> -- >> With best regards, >> Matwey V. Kornilov > > > > -- > With best regards, > Matwey V. Kornilov -- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
