Re: [opensuse-arm] trying out Jeos for nanopi neo air
Andreas Fc3a4rber wrote: > Am 27.01.19 um 14:57 schrieb Per Jessen: >> 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: > > ??? > [...] >>> 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. > > After checking for boot.scr it should check for efi/boot/bootarm.efi. > So as I said, if it doesn't do that, your U-Boot is too old or > misconfigured and needs to be replaced. Okay, that makes sense. > Our image surely does not contain Ubuntu, so that must be coming from > somewhere other than our image! Yes, this seems to be what FriendlyARM supplies by default. I've made quite a bit of progress now, Leap15 is running from SD. I almost have wireless working, just now getting crda and wireless-regdb installed. -- Per Jessen, Zürich (4.7°C) member, openSUSE heroes. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] trying out Jeos for nanopi neo air
Am 27.01.19 um 14:57 schrieb Per Jessen: > 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: ??? [...] >> 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. After checking for boot.scr it should check for efi/boot/bootarm.efi. So as I said, if it doesn't do that, your U-Boot is too old or misconfigured and needs to be replaced. Our image surely does not contain Ubuntu, so that must be coming from somewhere other than our image! Either it's on an internal boot medium, or you're having difficulties writing our image to SD card and have leftovers on that card. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] trying out Jeos for nanopi neo air
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: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] trying out Jeos for nanopi neo air
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. It sounds to me as if it's booting from eMMC and doesn't support UEFI yet. 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. If the Neo Air does come with eMMC pre-populated, then we can drop this JeOS-nanopineoair image and instead use JeOS-efi after upgrading U-Boot. We may need to add another dtb package to JeOS-efi then. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] trying out Jeos for nanopi neo air
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). -- Per Jessen, Zürich (3.8°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] trying out Jeos for nanopi neo air
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: ??? The default login as per https://en.opensuse.org/HCL:NanoPi_Neo_Air doesn't work either. -- Per Jessen, Zürich (3.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
