Orange Pi Plus 2 - new kernel, no network


piknew
 Share

1 1
Go to solution Solved by Igor,

Recommended Posts

Remark: on my Orange Pi PC and Orange Pi Plus 2e - everything is OK. Problem occurred on Orange Pi Plus 2 and Orange Pi Zero

 

After upgrading to:

 

[root@PKTEST ~]# uname -a
Linux PKTEST 5.10.4-sunxi #20.11.6 SMP Sun Jan 3 21:28:45 CET 2021 armv7l GNU/Linux

 

My "headless" Orange Pi Plus 2 "disappeared from network. I switch it off and connected via serial. I was able to login. Device runs successfully, it is assigning IP to network interface (static assignment) but... there is no connectivity at all (both egress and ingress).

 

[root@PKTEST ~]# ifconfig
enx0281cbcd0fcf: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.250  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::81:cbff:fecd:fcf  prefixlen 64  scopeid 0x20<link>
        ether 02:81:cb:cd:0f:cf  txqueuelen 1000  (Ethernet)
        RX packets 71  bytes 4397 (4.2 KiB)
        RX errors 0  dropped 38  overruns 0  frame 0
        TX packets 44  bytes 2484 (2.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 41

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 80  bytes 12802 (12.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 80  bytes 12802 (12.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@PKTEST ~]# ping localhost
PING localhost(localhost (::1)) 56 data bytes
64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.129 ms
64 bytes from localhost (::1): icmp_seq=2 ttl=64 time=0.166 ms
64 bytes from localhost (::1): icmp_seq=3 ttl=64 time=0.154 ms
^C
--- localhost ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 52ms
rtt min/avg/max/mdev = 0.129/0.149/0.166/0.020 ms
[root@PKTEST ~]# ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.107 ms
^C
--- 127.0.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.107/0.107/0.107/0.000 ms
[root@PKTEST ~]# ping 192.168.10.1
PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
From 192.168.10.250 icmp_seq=1 Destination Host Unreachable
From 192.168.10.250 icmp_seq=2 Destination Host Unreachable
From 192.168.10.250 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.10.1 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 78ms

 

Link to post
Share on other sites

Donate and support the project!

12 minutes ago, piknew said:

My "headless" Orange Pi Plus 2 "disappeared from network. I switch it off and connected via serial. I was able to login. Device runs successfully, it is assigning IP to network interface (static assignment) but... there is no connectivity at all (both egress and ingress).


My test devices works without a problem on 5.10.4, this is my Opi Zero: http://ix.io/2KRg

 

Its either hardware quality where we can't do much with a manual single device testing and WIP testing facility where we also receive little to no help:

https://github.com/armbian/autotests

https://github.com/armbian/mpads

Link to post
Share on other sites

I have reflashed SD card for OPI Zero with previous kernel (5.9.14-sunxi) - it works. So, next step will be apt update && apt upgrade to see if problem occurs again.

This is currently working version: http://ix.io/2KRL

Edit: it works. So, problem with Opi Zero was related to some "unknown unknown" :).

 

Also now I am flashing other SD card with previous kernel (5.9.14-sunxi) for OPI+2 and I will check the same as above.

 

BTW. When I am referring "previous kernel" - I mean my own images of configured system (which is kept with every upgrade since legacy 3.14), not original image from Armbian website.

 

Link to post
Share on other sites

Orange Pi + 2 - still issue with network.

 

I do not know if this is important, but other board has upgraded 6 packages (which 1 is Debian's), for example Opi Zero:

 

[root@PKCHECKER /var/log]# cat dpkg.log | grep upgrade
2021-01-04 20:24:19 upgrade libp11-kit0:armhf 0.23.15-2 0.23.15-2+deb10u1
2021-01-04 20:24:22 upgrade armbian-config:all 20.11.4 20.11.6
2021-01-04 20:24:24 upgrade linux-buster-root-current-orangepizero:armhf 20.11.3 20.11.6
2021-01-04 20:24:30 upgrade linux-dtb-current-sunxi:armhf 20.11.3 20.11.6
2021-01-04 20:24:45 upgrade linux-image-current-sunxi:armhf 20.11.3 20.11.6
2021-01-04 20:27:01 upgrade linux-u-boot-orangepizero-current:armhf 20.11.3 20.11.6

 

I noticed this when was about to reboot. Please note last lines - package "u-boot" is still in version 20.11.3:

 

[root@PKTEST ~]# apt update
Hit:1 http://deb.debian.org/debian buster InRelease
Get:2 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:3 http://deb.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:4 http://deb.debian.org/debian buster-proposed-updates InRelease [54.5 kB]
Get:5 https://armbian.systemonachip.net/apt buster InRelease [18.3 kB]
Get:6 http://deb.debian.org/debian-security buster/updates/main armhf Packages [319 kB]
Get:7 http://deb.debian.org/debian buster-proposed-updates/main armhf Packages.diff/Index [27.8 kB]
Get:8 http://deb.debian.org/debian buster-proposed-updates/main armhf Packages 2020-12-28-1401.36.pdiff [5,356 B]
Get:9 http://deb.debian.org/debian buster-proposed-updates/main armhf Packages 2020-12-29-2000.40.pdiff [2,130 B]
Get:9 http://deb.debian.org/debian buster-proposed-updates/main armhf Packages 2020-12-29-2000.40.pdiff [2,130 B]
Get:10 https://armbian.systemonachip.net/apt buster/main armhf Packages [669 kB]
Get:11 https://armbian.systemonachip.net/apt buster/buster-desktop armhf Packages [28.2 kB]
Fetched 1,241 kB in 5s (270 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
[root@PKTEST ~]# apt list --upgradable
Listing... Done
armbian-config/buster 20.11.6 all [upgradable from: 20.11.4]
libp11-kit0/stable 0.23.15-2+deb10u1 armhf [upgradable from: 0.23.15-2]
linux-buster-root-current-orangepiplus/buster 20.11.6 armhf [upgradable from: 20.11.3]
linux-dtb-current-sunxi/buster 20.11.6 armhf [upgradable from: 20.11.3]
linux-image-current-sunxi/buster 20.11.6 armhf [upgradable from: 20.11.3]
[root@PKTEST ~]# apt upgrade -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  armbian-config libp11-kit0 linux-buster-root-current-orangepiplus linux-dtb-current-sunxi linux-image-current-sunxi
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 36.3 MB of archives.
After this operation, 72.7 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian-security buster/updates/main armhf libp11-kit0 armhf 0.23.15-2+deb10u1 [292 kB]
Get:2 https://mirrors.dotsrc.org/armbian-apt buster/main armhf armbian-config all 20.11.6 [44.5 kB]
Get:3 https://minio.k-space.ee/armbian/apt buster/main armhf linux-buster-root-current-orangepiplus armhf 20.11.6 [415 kB]
Get:5 https://mirrors.netix.net/armbian/apt buster/main armhf linux-image-current-sunxi armhf 20.11.6 [35.3 MB]
Get:4 https://armbian.systemonachip.net/apt buster/main armhf linux-dtb-current-sunxi armhf 20.11.6 [193 kB]
Fetched 36.3 MB in 13s (2,785 kB/s)
(Reading database ... 51412 files and directories currently installed.)
Preparing to unpack .../libp11-kit0_0.23.15-2+deb10u1_armhf.deb ...
Unpacking libp11-kit0:armhf (0.23.15-2+deb10u1) over (0.23.15-2) ...
Setting up libp11-kit0:armhf (0.23.15-2+deb10u1) ...
(Reading database ... 51412 files and directories currently installed.)
Preparing to unpack .../armbian-config_20.11.6_all.deb ...
Unpacking armbian-config (20.11.6) over (20.11.4) ...
Preparing to unpack .../linux-buster-root-current-orangepiplus_20.11.6_armhf.deb ...
Unpacking linux-buster-root-current-orangepiplus (20.11.6) over (20.11.3) ...
Preparing to unpack .../linux-dtb-current-sunxi_20.11.6_armhf.deb ...
Unpacking linux-dtb-current-sunxi (20.11.6) over (20.11.3) ...
Preparing to unpack .../linux-image-current-sunxi_20.11.6_armhf.deb ...
update-initramfs: Deleting /boot/initrd.img-5.9.14-sunxi
Removing obsolete file uInitrd-5.9.14-sunxi
Unpacking linux-image-current-sunxi (20.11.6) over (20.11.3) ...
Setting up linux-image-current-sunxi (20.11.6) ...
update-initramfs: Generating /boot/initrd.img-5.10.4-sunxi
update-initramfs: Converting to u-boot format
Setting up linux-dtb-current-sunxi (20.11.6) ...
Setting up armbian-config (20.11.6) ...
Setting up linux-buster-root-current-orangepiplus (20.11.6) ...
Failed to enable unit: Unit file /etc/systemd/system/armbian-ramlog.service is masked.
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.10.4-sunxi
update-initramfs: Converting to u-boot format
[root@PKTEST ~]# apt list --installed | grep u-boot

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

linux-u-boot-orangepiplus-current/buster,now 20.11.3 armhf [installed]
u-boot-tools/stable,now 2019.01+dfsg-7 armhf [installed]
[root@PKTEST ~]#

 

Link to post
Share on other sites

This is full log from Serial connection:

 


U-Boot SPL 2018.05-armbian (Sep 19 2018 - 13:00:01 +0200)
DRAM: 2048 MiB
Trying to boot from MMC2


U-Boot 2018.05-armbian (Sep 19 2018 - 13:00:01 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus / Plus 2
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
Loading Environment from EXT4... MMC: no card present
** Bad device mmc 0 **
Failed (-5)
In:    serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c30000
MMC: no card present
** Bad device mmc 0 **
MMC: no card present
** Bad device mmc 0 **
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
   Request Sense returned 02 3A 00
2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3708 bytes read in 5 ms (723.6 KiB/s)
## Executing script at 43100000
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
212 bytes read in 4 ms (51.8 KiB/s)
MMC: no card present
** Bad device mmc 0 **
12396787 bytes read in 598 ms (19.8 MiB/s)
7932912 bytes read in 387 ms (19.5 MiB/s)
Found mainline kernel configuration
33456 bytes read in 35 ms (932.6 KiB/s)
374 bytes read in 21 ms (16.6 KiB/s)
Applying kernel provided DT overlay sun8i-h3-i2c0.dtbo
393 bytes read in 5 ms (76.2 KiB/s)
Applying user provided DT overlay ds1307.dtbo
4185 bytes read in 21 ms (194.3 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    12396723 Bytes = 11.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Ramdisk to 4942d000, end 49fff8b3 ... OK
   reserving fdt memory region: addr=43000000 size=6e000
   Loading Device Tree to 493bc000, end 4942cfff ... OK

Starting kernel ...

Loading, please wait...
Starting version 241
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk2p1] fsck.ext4 -a -C0 /dev/mmcblk2p1
/dev/mmcblk2p1: recovering journal
/dev/mmcblk2p1: clean, 58384/901600 files, 510156/3753728 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Armbian 20.11.6 Buster!

[  OK  ] Listening on Device-mapper event daemon FIFOs.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Started Forward Password R…uests to Wall Directory Watch.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Listening on LVM2 poll daemon socket.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Reached target Swap.
[  OK  ] Set up automount Arbitrary…s File System Automount Point.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Listening on RPCbind Server Activation Socket.
[  OK  ] Started Dispatch Password …ts to Console Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Paths.
[  OK  ] Listening on Journal Socket.
         Starting Monitoring of LVM…meventd or progress polling...
         Starting Journal Service...
         Mounting POSIX Message Queue File System...
         Starting Remount Root and Kernel File Systems...
         Starting Load Kernel Modules...
         Mounting Kernel Debug File System...
         Mounting RPC Pipe File System...
         Starting Set the console keyboard layout...
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on initctl Compatibility Named Pipe.
         Starting udev Coldplug all Devices...
         Mounting Temporary Directory (/tmp)...
         Starting Create list of re…odes for the current kernel...
         Starting Availability of block devices...
[  OK  ] Started Monitoring of LVM2… dmeventd or progress polling.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Journal Service.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted RPC Pipe File System.
[  OK  ] Mounted Temporary Directory (/tmp).
[  OK  ] Started Create list of req… nodes for the current kernel.
[  OK  ] Started Availability of block devices.
         Starting Apply Kernel Variables...
         Mounting FUSE Control File System...
         Mounting Kernel Configuration File System...
         Starting RTC-I2C device driver...
         Starting Load/Save Random Seed...
         Starting Create System Users...
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started Set the console keyboard layout.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Create System Users.
[  OK  ] Started udev Coldplug all Devices.
         Starting Helper to synchronize boot up for ifupdown...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Reached target Local File Systems.
         Starting Set console font and keymap...
         Starting Load AppArmor profiles...
         Starting Create Volatile Files and Directories...
         Starting Preprocess NFS configuration...
[  OK  ] Started Set console font and keymap.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Preprocess NFS configuration.
[  OK  ] Reached target NFS client services.
[  OK  ] Started Create Volatile Files and Directories.
         Starting Update UTMP about System Boot/Shutdown...
         Starting Network Name Resolution...
         Starting RPC bind portmap service...
[  OK  ] Started Load AppArmor profiles.
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
[  OK  ] Started RPC bind portmap service.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Started Network Name Resolution.
[  OK  ] Started Helper to synchronize boot up for ifupdown.
[  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
         Starting Raise network interfaces...
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Discard unused blocks once a week.
[  OK  ] Started Clean PHP session files every 30 mins.
[  OK  ] Started Daily man-db regeneration.
[  OK  ] Started Daily rotation of log files.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
[  OK  ] Started Manage Sound Card State (restore and store).
         Starting Login Service...
         Starting System Logger Daemon...
         Starting Save/Restore Sound Card State...
[  OK  ] Started D-Bus System Message Bus.
         Starting WPA supplicant...
         Starting Resets System Activity Data Collector...
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
         Starting LSB: Load kernel …d to enable cpufreq scaling...
[  OK  ] Started Regular background program processing daemon.
         Starting LSB: saslauthd startup script...
         Starting Deferred execution scheduler...
[  OK  ] Reached target RPC Port Mapper.
[  OK  ] Started Save/Restore Sound Card State.
[  OK  ] Started Resets System Activity Data Collector.
[  OK  ] Started Deferred execution scheduler.
         Starting Load/Save RF Kill Switch Status...
[  OK  ] Reached target Sound Card.
[  OK  ] Started LSB: saslauthd startup script.
[  OK  ] Started RTC-I2C device driver.
[  OK  ] Started Load/Save RF Kill Switch Status.
[  OK  ] Started Login Service.
[  OK  ] Started WPA supplicant.
[  OK  ] Started LSB: Load kernel m…ded to enable cpufreq scaling.
         Starting LSB: set CPUFreq kernel parameters...
[  OK  ] Started LSB: set CPUFreq kernel parameters.
         Starting LSB: Set sysfs variables from /etc/sysfs.conf...
[  OK  ] Started System Logger Daemon.
[  OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
[  OK  ] Started Raise network interfaces.
[  OK  ] Reached target Network.
         Starting Permit User Sessions...
[  OK  ] Started Unattended Upgrades Shutdown.
         Starting OpenVPN service...
         Starting Network Time Service...
         Starting OpenBSD Secure Shell server...
         Starting The PHP 7.3 FastCGI Process Manager...
[  OK  ] Reached target Network is Online.
         Starting Automounts filesystems on demand...
         Starting LSB: disk temperature monitoring daemon...
         Starting /etc/rc.local Compatibility...
[  OK  ] Started Permit User Sessions.
[  OK  ] Started OpenVPN service.
[  OK  ] Started Network Time Service.
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Started The PHP 7.3 FastCGI Process Manager.
[  OK  ] Created slice User Slice of UID 0.
         Starting User Runtime Directory /run/user/0...
[  OK  ] Started User Runtime Directory /run/user/0.
         Starting User Manager for UID 0...
[  OK  ] Started User Manager for UID 0.
[  OK  ] Started Session 2 of user root.

Armbian 20.11.6 Buster ttyS0

PKTEST login: root
Password:
Last login: Mon Jan  4 20:57:51 CET 2021 from 192.168.10.126 on pts/0
Device "bonding_masters" does not exist.
  ___  ____  _
 / _ \|  _ \(_)  _
| | | | |_) | |_| |_
| |_| |  __/| |_   _|
 \___/|_|   |_| |_|

Welcome to Armbian 20.11.6 Buster with Linux 5.10.4-sunxi

System load:   18%              Up time:       0 min
Memory usage:  4% of 1.97G      IP:            192.168.10.250
CPU temp:      48°C             Usage of /:    13% of 15G

HXproc_run_async: pmvarrun: No such file or directory
[root@PKTEST ~]# ifconfig
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500
        inet 192.168.10.250  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::81:cbff:fecd:fcf  prefixlen 64  scopeid 0x20<link>
        ether 02:81:cb:cd:0f:cf  txqueuelen 1000  (Ethernet)
        RX packets 61  bytes 3797 (3.7 KiB)
        RX errors 0  dropped 37  overruns 0  frame 0
        TX packets 39  bytes 2568 (2.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enx0281cbcd0fcf: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
        ether 02:81:cb:cd:0f:cf  txqueuelen 1000  (Ethernet)
        RX packets 61  bytes 3797 (3.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 39  bytes 2568 (2.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 41

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 74  bytes 12232 (11.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 74  bytes 12232 (11.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlxd84710fed46b: flags=6147<UP,BROADCAST,SLAVE,MULTICAST>  mtu 1500
        ether d8:47:10:fe:d4:6b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@PKTEST ~]# ping 192.168.10.1
PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
From 192.168.10.250 icmp_seq=1 Destination Host Unreachable
From 192.168.10.250 icmp_seq=2 Destination Host Unreachable
From 192.168.10.250 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.10.1 ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 79ms
pipe 4
[root@PKTEST ~]#

 

Link to post
Share on other sites

Done, U-Boot is updated:

 

U-Boot SPL 2020.10-armbian (Dec 12 2020 - 00:52:34 +0100)
DRAM: 2048 MiB
Trying to boot from MMC2


U-Boot 2020.10-armbian (Dec 12 2020 - 00:52:34 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Plus / Plus 2
DRAM:  2 GiB
MMC:   mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:1... In:    serial@1c28000
Out:   serial@1c28000
Err:   serial@1c28000
Net:   phy interface7
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1d000: USB EHCI 1.00
scanning bus usb@1c1b000 for devices... 2 USB Device(s) found
scanning bus usb@1c1d000 for devices... Device NOT ready
   Request Sense returned 02 3A 00
2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK

 

However, it doesn't helped with network. All interfaces are up, activity LEDs are blinking, switch is reporting connection 1Gbit/s but no traffic goes in/out. The same board but with previous kernel - everything is ok.

 

Maybe anybody else with Orange Pi + 2 can verify if this problem occurs as for my board?

Link to post
Share on other sites

I can verify that I have the same issue after upgrading my Orange Pi 2+. with the latest kernel upgrade.  WiFi works but hardwired ethernet does not.  I have the same symptoms as you. Both ends report connection and there is no traffic.  Let me know if I can help by reporting anything, but I think I'm just confirming the same issue.

 

Eric

Link to post
Share on other sites

I've moved the samba server over to the wireless, not the fastest solution, but I suspect this may not take too long to fix.  If it does, I will revert to an older kernel version as you suggest.

 

Eric

Link to post
Share on other sites

12 hours ago, ejs said:

I can verify that I have the same issue after upgrading my Orange Pi 2+. with the latest kernel upgrade.

 

 

Thank you for confirmation. It seems that this board is affected.

 

11 hours ago, Werner said:

As a temporary fix for now is use WiFi to provide connection and armbian-config to revert to an older kernel version.

 

Thanks, however, I will use "chroot" method when fixed kernel / packages will be available. For now I have just restored system from my backup image with previous kernel.

 

I am able to help with any other diagnostics. First step I would suggest to check if code for driver has been changed: 8189es - which I guess is used only by OPI+2. "OPI+2e" version which I also own is using 8189fs - and there is no problem there.

Link to post
Share on other sites

2 hours ago, Igor said:

I assume its this problem, but since I have no hardware to test, someone will need to build from sources to confirm:
https://github.com/armbian/build/commit/535650da96bb585a7dad47237f283a780189f0fb

 

It works! Thank you.

 

Screenshot_1.png.cabedd984774914661180e03c1ae51f4.png

 

Attached are:

  • decompiled source (command: dtc -I dtb -O dts sun8i-h3-orangepi-plus.dtb >sun8i-h3-orangepi-plus.dts ) with modified line 540 to be phy-mode = "rgmii-id"; (as given in patch): sun8i-h3-orangepi-plus.dts
  • compiled dtb (command: dtc -O dtb -o sun8i-h3-orangepi-plus.dtb sun8i-h3-orangepi-plus.dts ), to be placed in /boot/dtb-5.10.4-sunxi (then I have executed command: update-initramfs -u just in case): sun8i-h3-orangepi-plus.dtb

 

Link to post
Share on other sites

  • piknew changed the title to Orange Pi Plus 2 - new kernel, no network
 Share

1 1