Andreas Fc3a4rber wrote: > Am 26.01.19 um 23:15 schrieb Per Jessen: >> Per Jessen wrote: >> >>> I've just booted a nanopi neo air with >>> >>> >> http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/NanoPiNeo/images/openSUSE-Tumbleweed-ARM-JeOS-nanopineoair.armv7l-2019.01.08-Build6.14.raw.xz >>> >>> and I am greeted with: >>> >>> Ubuntu 15.10 FriendlyARM ttyS0 >>> FriendlyARM login: >>> >>> ??? >> >> Having also tried with nanopineo Leap15 from ports (which worked >> fine), it appears the problem is in in the lack of a boot.scr file >> (in the above). > > As a reminder, I prepared that image about two years ago, and this is > the first real test feedback we're getting - that's why it's not in > Factory:ARM:Live but in Contrib:NanoPiNeo. So you'll need to > investigate any problems at your own, as no one else here seems to > have that board.
I've had two for about two years, when I started with them, I had to do most of the work by hand :-) I'm repeating it now because the SD card started failing. > It sounds to me as if it's booting from eMMC and doesn't support UEFI > yet. Afaict, it's simply because the image above does not have the boot.scr. Today I switched to using the leap15 nanopineo appliance from ports/ - http://download.opensuse.org/ports/armv7hl/distribution/leap/15.0/appliances/ That's working a lot better, but I'm having trouble getting the wifi to work. > Then instead of adding an older boot method to our image, you > should upgrade your U-Boot on eMMC - extract the > /boot/u-boot-sunxi-with-spl.bin from our rpm u-boot-nanopineoair and > dd it to its expected location of seek=8k on the eMMC's mmcblkX - > compare other boards' HCL Wiki pages, e.g., Pine64. > Depending on how the Neo Air's boot flow is, erasing U-Boot on eMMC > might also make it fall back to SD, but having it on SPI or eMMC would > seem preferable, as you can then have a "normal" GPT on SD. Thanks, I'll check this out. -- Per Jessen, Zürich (4.4°C) member, openSUSE Heroes -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
