Peter,

Thanks for the response and the info about upstream support. I used both the "orangepi_pc" and "nanopi_neo" profiles to get a successful boot, however when I used the "nanopi_neo" profile, neither ethernet port worked, it was only when I used the "orangepi_pc" profile that I was able to get one of the ethernet ports to work. As far as the machine model, it reports "Xunlong Orange Pi PC".

With some testing, I can confirm that everything else is working as it should: USB works, the two onboard serial ports, and the single ethernet port, just not the second ethernet or onboard wifi. I have also attached a txt file with the output from the "lshw" command, for your reference.

Geoff Marr
IRC: coremodule


On Sun, May 26, 2019 at 3:09 AM Peter Robinson <pbrobinson@gmail.com> wrote:
Hi Geoff,

> Forgive my ignorance but I am curious how one would go about making both ethernet ports work on a NanoPi R1? I used an armhfp Fedora 30 Server image to boot into Fedora on the device, but out of the box only one ethernet port works; no wifi and the second ethernet port does not work. The NanoPi recognizes the second ethernet port, but I can't get it to recognize the actual connection. I can bring the second port "up". but it never connects. As far as I can tell, the device does not recognize the wifi at all. Is this something I can configure, and if so, where do I begin?

I don't see support for the NanoPi R1 in the upstream kernel so ATM we
don't actually support it at all, what profile/device are you using
when you write out the image? What does the "Machine Model" report in
the first few lines of dmesg output report?

Peter