NanoPi R4s, enp1s0 ethernet device not showed up after reboot

[3735943886]

Hello,

After NanoPi R4S reboot, ethernet interface `enp1s0` disappeared. I tried soft reboot for several times but failed. 

 

If I shutdown the board and power plug out/in again, then `enp1s0` appears. I tested it several times and 100% same results.

Any idea please?

 

wg* is for vpn. please ignore them.

[Werner]

Providing logs with 

armbianmonitor -u

 helps with troubleshooting and significantly raises chances that issue gets addressed.

[3735943886]

 

9 hours ago, Werner said:

Providing logs with 

armbianmonitor -u

 helps with troubleshooting and significantly raises chances that issue gets addressed.

Thank you for prompt reply.

 

I uploaded armbianmonitor -u

 

http://ix.io/3WJi

is for working state (power off and on)

 

http://ix.io/3WJk

is for non-working state (soft reboot)

 

Thank you

[3735943886]

I found a similar question here.

And I don't think it's a hardware problem but may be a kernel issue or something, because it was OK for long time and the problem suddenly occurs after upgrade to bullseye.

[Werner]

If the device works normally on cold boot I strongly assume it is an uboot/kernel bug. Hard to tell though where it comes from. If you have time and want to help us tracking down try older images and check when reboot breaks (or even wasn't working at all, no idea).

[3735943886]

50 minutes ago, Werner said:

If the device works normally on cold boot I strongly assume it is an uboot/kernel bug. Hard to tell though where it comes from. If you have time and want to help us tracking down try older images and check when reboot breaks (or even wasn't working at all, no idea).

Thank you for reply.

I'll try older images and post again later when I have time.

[3735943886]

6 hours ago, 3735943886 said:

Thank you for reply.

I'll try older images and post again later when I have time.

I tested with 4 archived images today.

GOOD is enp1s0 works fine with warm reboot.

BAD is enp1s0 works only after cold boot.

 

Armbian_20.11.10_Nanopi-r4s_focal_current_5.9.14.img.xz :GOOD
Armbian_21.08.1_Nanopi-r4s_bullseye_current_5.10.60.img.xz :GOOD
Armbian_21.08.1_Nanopi-r4s_hirsute_edge_5.13.12.img.xz :BAD
Armbian_22.02.1_Nanopi-r4s_jammy_edge_5.16.11.img.xz :BAD

and current my system is Armbian 22.02.1 with bullseye 5.15.25 :BAD

 

So I think,

Armbian version does not matter.

Debian (or ubuntu) version does not matter, either.

Kernel version (5.13 and above) may cause something.

 

Now I downgraded my system's kernel to 5.10.63 with via armbian-config.

And enp1s0 normally works after warm reboot again.

 

If you need more information that I can provide for this issue, please let me know.

Thank you.

[3735943886]

I found another post which is the same problem, I guess.

[annabelle]

It might be a hardware issue, I had to get a replacement from the seller as my secondary port didn't work no matter what

[elyograg]

I was having a similar issue, but can't remember if I tried fully powering it down.  I think I've always done the soft reboot.

 

As I said in that topic, the new version of the armbian-firmware-full package seems to have fixed the problem.  I did "reboot" via ssh.  The kernel was not updated.

[elyograg]

Update:  I haven't had that port working for a while now.  For a brief time after I installed the full firmware, it was working, and now it doesn't any more.  Cold boot does not seem to help.  I did a complete reinstall with the jammy build and it still doesn't work.

[David Manouchehri]

@elyograg: New builds should work after https://github.com/armbian/build/pull/4308. Let me know if this works for you or not.

[elyograg]

I upgraded my kernel again today and now the LAN port shows up in the OS.

It works with both a cold boot and a warm reboot.

 

elyograg@legolas:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 54:10:ec:69:2a:04 brd ff:ff:ff:ff:ff:ff
    inet 192.168.217.165/24 brd 192.168.217.255 scope global dynamic noprefixroute eth0
       valid_lft 10776sec preferred_lft 10776sec
    inet6 fe80::e711:cec1:6580:b9c9/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether be:4f:ec:fc:14:a2 brd ff:ff:ff:ff:ff:ff
elyograg@legolas:~$ uname -a
Linux legolas 6.0.5-rockchip64 #22.08.8 SMP PREEMPT Fri Oct 28 15:15:06 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
elyograg@legolas:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy

 

[David Manouchehri]

Nice, glad I seemed to have fixed it for you!

 

Could you post dmesg as well? I want to see how many times training failed. 

[Igor]

FYI. I pushed update to CURRENT kernel too - today / tomorrow.