On 14.08.2018 12:40, Matwey V. Kornilov wrote: > On 09.08.2018 19:14, Frank Kunz wrote: >> Hello, >> >> from JeOS revision log I found: >> >> Dirk Mueller (dirkmueller) committed 5 months ago (revision 602) >> - Drop JeOS-espressobin: use JeOS-efi.aarch64 instead >> - JeOS-rock64: the board now boots, but the image deploying requires >> manual quircks >> >> So I tried >> openSUSE-Tumbleweed-ARM-JeOS-efi.aarch64-2018.05.11-Build1.1.raw.xz and >> it cannot find the boot disk/partition: >> >> Kiwi output: >> ... >> ++ /usr/sbin/hwinfo --disk >> >> >> ++ cut -f2 -d: >> >> >> ++ grep -E 'Device File:|BIOS id' >> >> >> ++ sed '-es@(.*)@@' >> >> >> ++ tr -d ' ' >> >> >> + diskDevices='/dev/ram11 >> >> >> /dev/ram2 >> >> >> /dev/ram0 >> >> >> /dev/ram9 >> >> >> /dev/ram7 >> >> >> /dev/ram14 >> >> >> /dev/ram5 >> >> >> /dev/ram12 >> >> >> /dev/ram3 >> >> >> /dev/ram10 >> >> >> /dev/ram1 >> >> >> /dev/ram8 >> >> >> /dev/ram15 >> >> >> /dev/ram6 >> >> >> /dev/ram13 >> >> >> /dev/ram4' >> + lookupBiosBootDevice >> ... >> >> Maybe a specific mmc driver needs to be loaded, but how to do that for >> the generic JeOS-efi.aarch64 image? > > I did include required modules for EspressoBin. I think that something > wrong with dtb files in your case. Probably, u-boot doesn't find dtb > supplied in the image. >
By the way, could you please tell which u-boot do you use at EspressoBin? > Let me please check how does it work on my EspressoBin. I need some time. > >> >> Br, >> Frank >> > > -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
