[opensuse-arm] nanopi neo air ?
Has anyone been playing with one of these? I'm not making much progress myself - eventually I'd like to get openSUSE running of course, but for starters, I'm just trying with the ubuntu core from http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air The device seems to be booting (blue light flashing), but it's not picking up an IP-address from dhcp. -- Per Jessen, Zürich (6.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 24.02.2017 um 17:47 schrieb Per Jessen:
Has anyone been playing with one of these? I'm not making much progress myself - eventually I'd like to get openSUSE running of course, but for starters, I'm just trying with the ubuntu core from http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air
The device seems to be booting (blue light flashing), but it's not picking up an IP-address from dhcp.
Have you looked at my JeOS-nanopineo? Should be fairly similar. Upstream kernel did not have some drivers yet, there's a bug open where David is tracking those. https://en.opensuse.org/HCL:NanoPi_Neo 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+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Freitag, 24. Februar 2017 17:47:24 CET Per Jessen wrote:
Has anyone been playing with one of these? I'm not making much progress myself - eventually I'd like to get openSUSE running of course, but for starters, I'm just trying with the ubuntu core from http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air
The device seems to be booting (blue light flashing), but it's not picking up an IP-address from dhcp.
Have you tried using the image linked from: https://en.opensuse.org/HCL:NanoPi_Neo Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 work: +49 2405 49936-424 -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Fri, 24 Feb 2017 18:07:37 +0100, Andreas Färber wrote:
Am 24.02.2017 um 17:47 schrieb Per Jessen:
Has anyone been playing with one of these? I'm not making much progress myself - eventually I'd like to get openSUSE running of course, but for starters, I'm just trying with the ubuntu core from http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air
The device seems to be booting (blue light flashing), but it's not picking up an IP-address from dhcp.
Have you looked at my JeOS-nanopineo? Should be fairly similar. Upstream kernel did not have some drivers yet, there's a bug open where David is tracking those.
The Air doesn't include the on-board EMAC, so you should be fine with mainline kernel once the DT changes make it into mainline: https://groups.google.com/forum/#!msg/linux-sunxi/40476sMfqpQ/t_R7S-_5AwAJ https://groups.google.com/forum/#!msg/linux-sunxi/DtE7gpL7ITw/nqmRrY7oBwAJ https://groups.google.com/forum/#!msg/linux-sunxi/DcZWcD-9398/obO-7OzEBQAJ Cheers, David -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Andreas Fc3a4rber wrote:
Am 24.02.2017 um 17:47 schrieb Per Jessen:
Has anyone been playing with one of these? I'm not making much progress myself - eventually I'd like to get openSUSE running of course, but for starters, I'm just trying with the ubuntu core from http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air
The device seems to be booting (blue light flashing), but it's not picking up an IP-address from dhcp.
Have you looked at my JeOS-nanopineo? Should be fairly similar.
I'll try that - it can't be too difficult to add in a wlan interface. Thanks Per -- Per Jessen, Zürich (6.3°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Andreas Fc3a4rber wrote:
Am 24.02.2017 um 17:47 schrieb Per Jessen:
Has anyone been playing with one of these? I'm not making much progress myself - eventually I'd like to get openSUSE running of course, but for starters, I'm just trying with the ubuntu core from http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air
The device seems to be booting (blue light flashing), but it's not picking up an IP-address from dhcp.
Have you looked at my JeOS-nanopineo? Should be fairly similar. Upstream kernel did not have some drivers yet, there's a bug open where David is tracking those.
Yes, I did try that initially (before Sportferien). I've just now downloaded openSUSE-Tumbleweed-ARM-JeOS-nanopineo.armv7l-2017.01.17-Build5.2.raw.xz copied it to the SD card, and added /etc/sysconfig/network/ifcfg-wlan0 Boot-up - the green LED comes on at low intensity, then goes high after a little while. The blue LED never lights up and it doesn't request an IP-address. That's why I switched to the Ubuntu core from friendlyarm. I must be missing something essential, I just can't put my finger on it. -- Per Jessen, Zürich (5.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 24.02.2017 um 18:23 schrieb David Disseldorp:
On Fri, 24 Feb 2017 18:07:37 +0100, Andreas Färber wrote:
Have you looked at my JeOS-nanopineo? Should be fairly similar. Upstream kernel did not have some drivers yet, there's a bug open where David is tracking those.
The Air doesn't include the on-board EMAC, so you should be fine with mainline kernel once the DT changes make it into mainline: https://groups.google.com/forum/#!msg/linux-sunxi/40476sMfqpQ/t_R7S-_5AwAJ https://groups.google.com/forum/#!msg/linux-sunxi/DtE7gpL7ITw/nqmRrY7oBwAJ https://groups.google.com/forum/#!msg/linux-sunxi/DcZWcD-9398/obO-7OzEBQAJ
FYI I've just enabled JeOS-nanopineo in Factory - we'll need to update the Wiki once it's built and published. 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+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Per Jessen wrote:
Andreas Fc3a4rber wrote:
Am 24.02.2017 um 17:47 schrieb Per Jessen:
Has anyone been playing with one of these? I'm not making much progress myself - eventually I'd like to get openSUSE running of course, but for starters, I'm just trying with the ubuntu core from http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air
The device seems to be booting (blue light flashing), but it's not picking up an IP-address from dhcp.
Have you looked at my JeOS-nanopineo? Should be fairly similar.
I'll try that - it can't be too difficult to add in a wlan interface.
Quick follow-up - it was a little tricky, but at least the nanopi neo air is now running with the ubuntu core image as provided by friendlyarm. For the wifi interface, it's using a "bcmdhd" module from wireless/bcm4336/bcmdhd.ko - afaict, that is not included in the openSUSE JeOS image? For my purposes, I can no doubt make it work with Ubuntu, but I'd much rather be running openSUSE :-) -- Per Jessen, Zürich (7.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 26.02.2017 um 19:00 schrieb Per Jessen:
Per Jessen wrote:
Andreas Fc3a4rber wrote:
Am 24.02.2017 um 17:47 schrieb Per Jessen:
Has anyone been playing with one of these? I'm not making much progress myself - eventually I'd like to get openSUSE running of course, but for starters, I'm just trying with the ubuntu core from http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air
The device seems to be booting (blue light flashing), but it's not picking up an IP-address from dhcp.
Have you looked at my JeOS-nanopineo? Should be fairly similar.
I'll try that - it can't be too difficult to add in a wlan interface.
Just to be clear, this is not just about adding a wlan interface. Since you're the one with the board, I pointed you to look at JeOS-nanopineo as template to create a JeOS-nanopineoair image - don't expect the image for another board to just work for you. LEDs are one of the most common things to differ between boards, compared to serial ports.
Quick follow-up -
it was a little tricky, but at least the nanopi neo air is now running with the ubuntu core image as provided by friendlyarm. For the wifi interface, it's using a "bcmdhd" module from wireless/bcm4336/bcmdhd.ko - afaict, that is not included in the openSUSE JeOS image? For my purposes, I can no doubt make it work with Ubuntu, but I'd much rather be running openSUSE :-)
The upstream driver is called brcmfmac - you may need to extend our bcm43xx-firmware package with the NVRAM config file for your board. As usual, each board will need its own u-boot-* package (if it's in mainline, it's trivial to enable as package; but apparently it isn't), a .dtb file in a dtb-* package for our kernel version (again nope) and then the JeOS additions to install those packages into an image. In the meantime you should create an HCL:Nano_Pi_Neo_Air Wiki page to track any package or upstream dependencies for creating that image. 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+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Andreas Fc3a4rber wrote:
Am 26.02.2017 um 19:00 schrieb Per Jessen:
Per Jessen wrote:
Andreas Fc3a4rber wrote:
Am 24.02.2017 um 17:47 schrieb Per Jessen:
Has anyone been playing with one of these? I'm not making much progress myself - eventually I'd like to get openSUSE running of course, but for starters, I'm just trying with the ubuntu core from http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air
The device seems to be booting (blue light flashing), but it's not picking up an IP-address from dhcp.
Have you looked at my JeOS-nanopineo? Should be fairly similar.
I'll try that - it can't be too difficult to add in a wlan interface.
Just to be clear, this is not just about adding a wlan interface. Since you're the one with the board, I pointed you to look at JeOS-nanopineo as template to create a JeOS-nanopineoair image
Ah, I misunderstood. Is there a howto for me to study somewhere, this is brand new territory for me.
LEDs are one of the most common things to differ between boards, compared to serial ports.
Okay.
In the meantime you should create an HCL:Nano_Pi_Neo_Air Wiki page to track any package or upstream dependencies for creating that image.
I tried that, I'm not sure if it worked. -- Per Jessen, Zürich (4.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 27.02.2017 um 08:55 schrieb Per Jessen:
Andreas Fc3a4rber wrote:
Am 26.02.2017 um 19:00 schrieb Per Jessen:
Per Jessen wrote:
Andreas Fc3a4rber wrote:
Am 24.02.2017 um 17:47 schrieb Per Jessen:
Has anyone been playing with one of these? I'm not making much progress myself - eventually I'd like to get openSUSE running of course, but for starters, I'm just trying with the ubuntu core from http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air
The device seems to be booting (blue light flashing), but it's not picking up an IP-address from dhcp.
Have you looked at my JeOS-nanopineo? Should be fairly similar.
I'll try that - it can't be too difficult to add in a wlan interface.
Just to be clear, this is not just about adding a wlan interface. Since you're the one with the board, I pointed you to look at JeOS-nanopineo as template to create a JeOS-nanopineoair image
Ah, I misunderstood. Is there a howto for me to study somewhere, this is brand new territory for me.
I'm not aware (but it's a Wiki...), that's why I pointed to an existing example. pre_checkin.* is always the first file to look at, and inside the JeOS package Images.kiwi.in.
In the meantime you should create an HCL:Nano_Pi_Neo_Air Wiki page to track any package or upstream dependencies for creating that image.
I tried that, I'm not sure if it worked.
Apparently not under that name, and I realize HCL:NanoPi_Neo_Air would've been more consistent anyway. If you chose a different name, it doesn't show up here: https://en.opensuse.org/Category:ARM_devices But maybe you just forgot to tag the category? 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+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Andreas Fc3a4rber wrote:
In the meantime you should create an HCL:Nano_Pi_Neo_Air Wiki page to track any package or upstream dependencies for creating that image.
I tried that, I'm not sure if it worked.
Apparently not under that name, and I realize HCL:NanoPi_Neo_Air would've been more consistent anyway. If you chose a different name, it doesn't show up here: https://en.opensuse.org/Category:ARM_devices But maybe you just forgot to tag the category?
Not sure what happened to the page yesterday, but I've created a new one. -- Per Jessen, Zürich (4.4°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Andreas Fc3a4rber wrote:
Just to be clear, this is not just about adding a wlan interface. Since you're the one with the board, I pointed you to look at JeOS-nanopineo as template to create a JeOS-nanopineoair image - don't expect the image for another board to just work for you. LEDs are one of the most common things to differ between boards, compared to serial ports.
I've been trying to do this more or less from scratch - I figure that'll give me a better overall understanding of what's involved. I'll try to sum up where I am at the moment, I would much appreciate someone correcting my mistakes/misunderstandings. I started out here: https://en.opensuse.org/openSUSE:OpenSUSE_on_your_ARM_board, "Bootstrapping a kernel using openSUSE chroot". I figured from there it couldn't be too difficult getting u-boot installed, and ROOT+BOOT partitions updated and maybe have a somewhat working system. I'm still waiting for the ttl serial interfaces to arrive :-) u-boot - this is installed in a known place in the beginning of the SD card, and the board BIOS knows where to look for it. Is that correct? u-boot - does not seem to be platform specific? I've looked at u-boot in OBS, all the variations link to u-boot, where the spec file has a few platform-specific customizations. It seems to me that nanopi-neo ought to work with nanopi-neo-air too? dtb file - this is a hardware description needed because embedded platforms typically don't offer the interfaces for the OS to discover the hardware itself. The dtb file is part of the kernel tree. I've found a kernel patch for adding a dtb for the nanopi-neo-air. It applied cleanly to 4.10.1. When booting, how is the correct dtb file loaded? thanks Per -- Per Jessen, Zürich (4.4°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Per Jessen wrote:
Andreas Fc3a4rber wrote:
Just to be clear, this is not just about adding a wlan interface. Since you're the one with the board, I pointed you to look at JeOS-nanopineo as template to create a JeOS-nanopineoair image - don't expect the image for another board to just work for you. LEDs are one of the most common things to differ between boards, compared to serial ports.
I've been trying to do this more or less from scratch - I figure that'll give me a better overall understanding of what's involved. I'll try to sum up where I am at the moment, I would much appreciate someone correcting my mistakes/misunderstandings.
I started out here:
https://en.opensuse.org/openSUSE:OpenSUSE_on_your_ARM_board, "Bootstrapping a kernel using openSUSE chroot".
I figured from there it couldn't be too difficult getting u-boot installed, and ROOT+BOOT partitions updated and maybe have a somewhat working system. I'm still waiting for the ttl serial interfaces to arrive :-)
They arrived From China this morning - the board is booting: https://files.jessen.ch/nanopi-neo-air-console.txt -- Per Jessen, Zürich (6.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
Andreas Fc3a4rber wrote:
Just to be clear, this is not just about adding a wlan interface. Since you're the one with the board, I pointed you to look at JeOS-nanopineo as template to create a JeOS-nanopineoair image - don't expect the image for another board to just work for you. LEDs are one of the most common things to differ between boards, compared to serial ports.
I've been trying to do this more or less from scratch - I figure that'll give me a better overall understanding of what's involved. I'll try to sum up where I am at the moment, I would much appreciate someone correcting my mistakes/misunderstandings.
I started out here:
https://en.opensuse.org/openSUSE:OpenSUSE_on_your_ARM_board, "Bootstrapping a kernel using openSUSE chroot".
I figured from there it couldn't be too difficult getting u-boot installed, and ROOT+BOOT partitions updated and maybe have a somewhat working system. I'm still waiting for the ttl serial interfaces to arrive :-)
They arrived From China this morning - the board is booting:
After amending boot.script and removing "size=100%" from rootflags, and adding "root=/dev/mmcblk0p2" to the kernel arguments, the system actually completed boot-up and offered me a login. I don't have a network yet, and there were a few things that failed during startup (due to root being read-only), but I'm running openSUSE TW on the nanopi-neo-air and even have a brightly lit green LED. -- Per Jessen, Zürich (7.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Per Jessen wrote:
I figured from there it couldn't be too difficult getting u-boot installed, and ROOT+BOOT partitions updated and maybe have a somewhat working system. I'm still waiting for the ttl serial interfaces to arrive :-)
They arrived From China this morning - the board is booting:
After amending boot.script and
removing "size=100%" from rootflags, and adding "root=/dev/mmcblk0p2" to the kernel arguments, the system actually completed boot-up and offered me a login. I don't have a network yet, and there were a few things that failed during startup (due to root being read-only), but I'm running openSUSE TW on the nanopi-neo-air and even have a brightly lit green LED.
After finally finding wifi firmware and NVRAM defs at http://vps.vdwaa.nl/~jelle/brcm/ adding crda and wireless-regedb, I now have a wifi connection, although I cannot login over ssh yet. (it just hangs). -- Per Jessen, Zürich (10.9°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
I figured from there it couldn't be too difficult getting u-boot installed, and ROOT+BOOT partitions updated and maybe have a somewhat working system. I'm still waiting for the ttl serial interfaces to arrive :-)
They arrived From China this morning - the board is booting:
After amending boot.script and
removing "size=100%" from rootflags, and adding "root=/dev/mmcblk0p2" to the kernel arguments, the system actually completed boot-up and offered me a login. I don't have a network yet, and there were a few things that failed during startup (due to root being read-only), but I'm running openSUSE TW on the nanopi-neo-air and even have a brightly lit green LED.
After finally finding wifi firmware and NVRAM defs at http://vps.vdwaa.nl/~jelle/brcm/
adding crda and wireless-regedb, I now have a wifi connection, although I cannot login over ssh yet. (it just hangs).
Some sort of ipv4/ipv6 problem - logging in over ipv6 works fine. -- Per Jessen, Zürich (12.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 27.02.2017 um 14:23 schrieb Andreas Färber:
Am 27.02.2017 um 08:55 schrieb Per Jessen:
Andreas Fc3a4rber wrote:
Am 26.02.2017 um 19:00 schrieb Per Jessen:
Per Jessen wrote:
Andreas Fc3a4rber wrote:
Am 24.02.2017 um 17:47 schrieb Per Jessen: > Has anyone been playing with one of these? I'm not making much > progress myself - eventually I'd like to get openSUSE running of > course, but for starters, I'm just trying with the ubuntu core > from http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Air > > The device seems to be booting (blue light flashing), but it's not > picking up an IP-address from dhcp.
Have you looked at my JeOS-nanopineo? Should be fairly similar.
I'll try that - it can't be too difficult to add in a wlan interface.
Just to be clear, this is not just about adding a wlan interface. Since you're the one with the board, I pointed you to look at JeOS-nanopineo as template to create a JeOS-nanopineoair image
Ah, I misunderstood. Is there a howto for me to study somewhere, this is brand new territory for me.
I'm not aware (but it's a Wiki...), that's why I pointed to an existing example. pre_checkin.* is always the first file to look at, and inside the JeOS package Images.kiwi.in.
With today's update to v2017.05-rc2, there now is a u-boot-nanopineoair package in Base:System:Staging for you to test. If you interrupt it on serial and type "printenv fdtfile", I would expect that you see a different .dtb filename than for -nanopineo. The sun8i-h3-nanopi-neo-air.dtb file is however not part of kernel 4.11 (i.e., not in Kernel:HEAD), so you would need to try kernel-vanilla and dtb-sun8i from Kernel:linux-next. Or try just the .dtb file from there, with a Factory or Kernel:HEAD kernel-lpae. To use the partially-working sun8i-h3-nanopi-neo.dtb as before with the new u-boot-nanopineoair, you could use a symlink. Small steps... 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+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Per, Am 18.04.2017 um 18:51 schrieb Andreas Färber:
With today's update to v2017.05-rc2, there now is a u-boot-nanopineoair package in Base:System:Staging for you to test.
If you interrupt it on serial and type "printenv fdtfile", I would expect that you see a different .dtb filename than for -nanopineo.
The sun8i-h3-nanopi-neo-air.dtb file is however not part of kernel 4.11 (i.e., not in Kernel:HEAD), so you would need to try kernel-vanilla and dtb-sun8i from Kernel:linux-next. Or try just the .dtb file from there, with a Factory or Kernel:HEAD kernel-lpae.
To use the partially-working sun8i-h3-nanopi-neo.dtb as before with the new u-boot-nanopineoair, you could use a symlink.
Small steps...
Haven't heard back here yet. Note that I've recently (when touching it) prepared a JeOS image with the above bootloader: https://en.opensuse.org/HCL:NanoPi_Neo_Air It still requires the above workarounds for the .dtb, thus in a Contrib. Some feedback before oSC17 would be appreciated, as I don't have one. Thanks, 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+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Andreas Färber wrote:
Hi Per,
Am 18.04.2017 um 18:51 schrieb Andreas Färber:
With today's update to v2017.05-rc2, there now is a u-boot-nanopineoair package in Base:System:Staging for you to test.
If you interrupt it on serial and type "printenv fdtfile", I would expect that you see a different .dtb filename than for -nanopineo.
The sun8i-h3-nanopi-neo-air.dtb file is however not part of kernel 4.11 (i.e., not in Kernel:HEAD), so you would need to try kernel-vanilla and dtb-sun8i from Kernel:linux-next. Or try just the .dtb file from there, with a Factory or Kernel:HEAD kernel-lpae.
To use the partially-working sun8i-h3-nanopi-neo.dtb as before with the new u-boot-nanopineoair, you could use a symlink.
Small steps...
Haven't heard back here yet. Note that I've recently (when touching it) prepared a JeOS image with the above bootloader:
https://en.opensuse.org/HCL:NanoPi_Neo_Air
It still requires the above workarounds for the .dtb, thus in a Contrib.
Some feedback before oSC17 would be appreciated, as I don't have one.
Hi Andreas I have a working system, it's been running for a while measuring electricity consumption. https://www.jessen.ch/electricity I am currently missing two things - I want to boot from the built-in eMMC flash and I would prefer to run a clean Leap422. The latter isn't so important though. I started with your TW JeOS image for the nanopi neo: openSUSE-Tumbleweed-ARM-JeOS-nanopineo.armv7l-2017.01.17-Build5.2.raw.xz I updated the dtb with some patches from a Dutch guy, I rebuilt the kernel, got new firmware and nvram for the wifi. It was a great learning exercise. Gruss Per -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (4)
-
Andreas Färber -
David Disseldorp -
Per Jessen -
Stefan Bruens