0
trimen

NanoPi Fire3 - ethernet not working and other issues

Recommended Posts

Hello,

I'm trying to get working my NanoPi Fire3 with HD702 screen and I found out some issues.
I'm running Armbian_20.02.7_Nanopifire3_bionic_legacy_4.14.174 image on it.
--
First and most significant is that the ethernet port isn't working properly. I cannot ping anything and if I try to deactivate and activate ethernet connection in Network Manager it says:


 

Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <warn>  [1585663445.9567] dhcp4 (eth0): request timed out
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info>  [1585663445.9569] dhcp4 (eth0): state changed unknown -> timeout
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info>  [1585663445.9738] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 4459
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info>  [1585663445.9739] dhcp4 (eth0): state changed timeout -> done
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info>  [1585663445.9761] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <warn>  [1585663445.9800] device (eth0): Activation: failed for connection 'Wired connection 1'
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info>  [1585663445.9845] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0045] policy: auto-activating connection 'Wired connection 1'
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0147] device (eth0): Activation: starting connection 'Wired connection 1' (cf44b283-2a76-371d-9d8a-84fccecce8ea)
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0166] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0202] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0241] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0268] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)

After reboot, it's connected via eth, but if I try to ping something is also fails

root@nanopifire3:~# ping 8.8.8.8
PING 8.8.88 (8.8.0.88) 56(84) bytes of data.
From 10.42.0.72 icmp_seq=1 Destination Host Unreachable
From 10.42.0.72 icmp_seq=2 Destination Host Unreachable
From 10.42.0.72 icmp_seq=3 Destination Host Unreachable
From 10.42.0.72 icmp_seq=4 Destination Host Unreachable
From 10.42.0.72 icmp_seq=5 Destination Host Unreachable
From 10.42.0.72 icmp_seq=6 Destination Host Unreachable
From 10.42.0.72 icmp_seq=7 Destination Host Unreachable
From 10.42.0.72 icmp_seq=8 Destination Host Unreachable
From 10.42.0.72 icmp_seq=9 Destination Host Unreachable
From 10.42.0.72 icmp_seq=10 Destination Host Unreachable
From 10.42.0.72 icmp_seq=11 Destination Host Unreachable
From 10.42.0.72 icmp_seq=12 Destination Host Unreachable
From 10.42.0.72 icmp_seq=13 Destination Host Unreachable
From 10.42.0.72 icmp_seq=14 Destination Host Unreachable
From 10.42.0.72 icmp_seq=15 Destination Host Unreachable
From 10.42.0.72 icmp_seq=16 Destination Host Unreachable
From 10.42.0.72 icmp_seq=17 Destination Host Unreachable
From 10.42.0.72 icmp_seq=18 Destination Host Unreachable
From 10.42.0.72 icmp_seq=19 Destination Host Unreachable
From 10.42.0.72 icmp_seq=20 Destination Host Unreachable
From 10.42.0.72 icmp_seq=21 Destination Host Unreachable
From 10.42.0.72 icmp_seq=22 Destination Host Unreachable
From 10.42.0.72 icmp_seq=23 Destination Host Unreachable
From 10.42.0.72 icmp_seq=24 Destination Host Unreachable
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available

--

I connected my HD702 screen to board and if I install xubuntu-core/desktop... it works, but It's running via fb, thus it's slow and FriendlyArm OneWire touchscreen isn't working. I wasn't able to find information if is OneWire touchscreen supported in your kernel, or how to get it working.
I wasn't able to find any information if is GPU in S5P6818 supported or if it's possible to have accelerated desktop environment on it.
--
My last question is if SPI on this board works.

Thanks in advance.

Share this post


Link to post
Share on other sites
Armbian is a community driven open source project. Do you like to contribute your code?
1 hour ago, trimen said:

First and most significant is that the ethernet port isn't working properly.


Known problem, no solution yet, but its probably some init timings. Sometimes driver fails to properly initialise the driver. 

 

1 hour ago, trimen said:

I connected my HD702 screen to board and if I install xubuntu-core/desktop... it works, but It's running via fb, thus it's slow and FriendlyArm OneWire touchscreen isn't working.


I do have this screen somewhere, but was never tested. Check device tree - perhaps/probably it only needs to be enabled.

 

1 hour ago, trimen said:

I wasn't able to find any information if is GPU in S5P6818 supported or if it's possible to have accelerated desktop environment on it.


We ported this work: https://github.com/rafaello7/debian-installer-nanopi-m3 More or less it works what is written there and more.

Share this post


Link to post
Share on other sites

Thanks for fast reply.

I poked around DTB and i try to enable SPI, which was set to disabled, I changed it to okay, but after recompiling DTB and rebooting nothing happend.
There is also entry onewire-touch, but I don't know what to do with it.

spi@c005b000 {
                        compatible = "nexell,s5p6818-spi";
                        reg = <0xc005b000 0x100>;
                        interrupts = <0x0 0xc 0x0>;
                        dmas = <0x39 0x6 0x0 0x39 0x7 0x0>;
                        dma-names = "tx", "rx";
                        resets = <0x12 0x2c 0x12 0x2d>;
                        reset-names = "pre-reset", "spi-reset";
                        #address-cells = <0x1>;
                        #size-cells = <0x0>;
                        samsung,spi-src-clk = <0x0>;
                        num-cs = <0x1>;
                        clocks = <0x48 0x48>;
                        clock-names = "spi", "spi_busclk0";
                        pinctrl-names = "default";
                        pinctrl-0 = <0x49>;
                        status = "okay";
                };
//------

onewire-touch {
                compatible = "friendlyarm,onewire-touch";
                interrupt-parent = <0x2e>;
                interrupts = <0x10 0x0>;
                i2c-bus = <0x6e>;
                pinctrl-names = "default";
                pinctrl-0 = <0x6f>;
        };


In modules I found module onewire-touch, but nothing after loading.
--

About DTB editing, I was able to find very little information about modifying. Can I be pointed to somewhere, where I can get info about it?


 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
0