I am looking to run my root and home directories from my NVMe instead of my eMMC. I have searched the Pine64 website and have found numerous ways to do it but almost all of them involve other distributions. Any help would be greatly appreciated.
For the record, I do not care about being able to boot from my NVMe. I just want to be able to use my 512 GB SSD to run a web server and a database. Any help would be greatly appreciated.
Hello and welcome to the forum.
I think you should flash manjaro image on emmc and nvme
After that erase the ROOT_MNJRO partition from emmc and erase BOOT_MNJRO partition from nvme.
After this you should be able to boot from emmc but start rootfs from nvme.
I hope this method with work on Rockpro64, @Strit correct me if I’m wrong, as I don’t have this device for trying it.
I have already flashed both the eMMC and the NVMe. When I boot, only the eMMC responds. However, NVMe is recognized and mounted already.
Yes rk3399 can only boot from emmc or sd card.
So it will boot from emmc but you can remove ROOT_MNJRO on emmc and keep ROOT_MNJRO on nvme so the kernel should load rootfs from nvme.
That should work in theory.
Maybe you should try this and share the uart log if ur getting stuck.
I removed the ROOT_MNJRO from the eMMC. Then I removed the BOOT_MNJRO from the NVMe. I had to reconfigure the system again (no big deal). It took a little while to boot after setting it up with the NVMe as the root, but it works. Thank you very much for the easy solution.
Now my only problem is I am unable to get the ethernet connection to work. Do you have a suggestion? I created a new ethernet connection and still nothing.
Plus I just realized that my 10mm heatsink with fan is not running.
No idea about these as Ive never seen it tested RockPro64. Maybe @Strit can help.
I don’t have a fan for my RockPro64.
But the Ethernet should work out of the box on all new installs of Manjaro ARM.
You haven’t mentioned what Image you have downloaded and installed.
I created the issue. I should have reflashed the eMMC. To fix the problem, I reflashed both the eMMC and the NVMe. Then removed the root from the eMMC and boot from NVMe. Now it works like a charm.
[diego@ROCKPro64 ~]$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
mmcblk2
│
└─mmcblk2p1
vfat FAT16 BOOT_MNJRO
322C-9E25 150.3M 30% /boot
mmcblk2boot0
mmcblk2boot1
zram0
[SWAP]
nvme0n1
│
└─nvme0n1p2
ext4 1.0 ROOT_MNJRO
f0265be2-a596-447f-9720-b0c20b0d16cc 434.8G 1% /@Strit. Ethernet on my rockpro64 is not working. I described it on the “networking unstable” thread. Please see here: Rockpro64 networking unstable
Sounds like it is working. Just slow. No idea why that is though.
@Strit: Unfortunately it is so slow, that all updates time out. So currently I am not able to install any tools to examine the situation.When I ssh or scp to another local host, it seems, it transfers data quickly for a moment, then hangs and then it is able to transfer data again. Sometimes it won’t recover from the stall and I have to quit the operation. I attached an excerpt from the journal, containing all error messages (red in journal) and all messages relating to eth0 or Network Manager. I can’t see any obvious errors from the network related log messages. On the other hand I don’t know if the error messages are related to the network problem. The last 3 lines in the log are repeated in the log permanently. I don’t know what they mean.
– Logs begin at Sat 2020-10-03 20:13:07 CEST, end at Mon 2020-10-19 12:54:42 CEST. –
Oct 03 20:13:07 rock64 kernel: Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Oct 03 20:13:07 rock64 kernel: Linux version 5.8.14-1-MANJARO-ARM (gitlab-runner@odroid-n2plus-pm) (gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35) #1 SMP Wed Oct 7 09:18:37 CEST 2020
Oct 03 20:13:07 rock64 kernel: Machine model: Pine64 RockPro64 v2.1
Oct 03 20:13:07 rock64 kernel: efi: UEFI not found.
Oct 03 20:13:07 rock64 kernel: [Firmware Bug]: Kernel image misaligned at boot, please fix your bootloader!
Oct 03 20:13:07 rock64 kernel: cma: Reserved 64 MiB at 0x00000000f4000000
Oct 03 20:13:07 rock64 kernel: Zone ranges:
Oct 03 20:13:07 rock64 kernel: DMA [mem 0x0000000000200000-0x000000003fffffff]
Oct 03 20:13:07 rock64 kernel: DMA32 [mem 0x0000000040000000-0x00000000f7ffffff]
Oct 03 20:13:07 rock64 kernel: Normal empty
ct 03 20:13:07 rock64 kernel: DMA zone: 0 pages reserved
Oct 03 20:13:07 rock64 kernel: DMA zone: 261632 pages, LIFO batch:63
Oct 03 20:13:07 rock64 kernel: DMA32 zone: 11776 pages used for memmapOct 03 20:13:07 rock64 kernel: vcc5v0_host: supplied by vcc5v0_usb
Oct 03 20:13:07 rock64 kernel: busb Failed to get VBUS supply regulator
Oct 03 20:13:07 rock64 kernel: phy phy-ff770000.syscon:usb2-phy@e450.2: Failed to get VBUS supply regulator
Oct 03 20:13:07 rock64 kernel: busb Failed to get VBUS supply regulator
Oct 03 20:13:07 rock64 kernel: phy phy-ff770000.syscon:usb2-phy@e460.4: Failed to get VBUS supply regulator
Oct 03 20:13:07 rock64 kernel: busb rockchip_set_vbus_power ret=0Oct 03 20:13:07 rock64 kernel: device-mapper: uevent: version 1.0.3
Oct 03 20:13:07 rock64 kernel: device-mapper: ioctl: 4.42.0-ioctl (2020-02-27) initialised: dm-devel@redhat.com
Oct 03 20:13:07 rock64 kernel: energy_model: pd0: hertz/watts ratio non-monotonically decreasing: em_cap_state 1 >= em_cap_state0
Oct 03 20:13:07 rock64 kernel: energy_model: Created perf domain 0-3
Oct 03 20:13:07 rock64 kernel: energy_model: Created perf domain 4-5Oct 19 12:49:11 rock64 systemd-udevd[405]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Oct 19 12:49:11 rock64 systemd-udevd[405]: ethtool: could not get ethtool features for eth0
Oct 19 12:49:11 rock64 systemd-udevd[405]: Could not set offload features of eth0: Device or resource busyOct 19 12:49:12 rock64 kernel: busb rockchip_usb2phy_otg_sm_work (null) otg sm work 0
Oct 19 12:49:12 rock64 kernel: busb HOST = 0,VBUS_EN=0,vbus_attached=0
Oct 19 12:49:12 rock64 kernel: busb vbus_attach rphy->chg_state = 0
Oct 19 12:49:12 rock64 kernel: busb chg detection work state = 0Oct 19 12:49:13 rock64 NetworkManager[625]: [1603104553.8143] NetworkManager (version 1.26.2-1) is starting… (for the first time)
Oct 19 12:49:13 rock64 NetworkManager[625]: [1603104553.8146] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: disable-random-mac.conf)
Oct 19 12:49:13 rock64 NetworkManager[625]: [1603104553.8395] bus-manager: acquired D-Bus service “org.freedesktop.NetworkManager”
Oct 19 12:49:13 rock64 bluetoothd[623]: Starting SDP server
Oct 19 12:49:13 rock64 NetworkManager[625]: [1603104553.9023] manager[0xaaaad333a030]: monitoring kernel firmware directory ‘/lib/firmware’.
Oct 19 12:49:14 rock64 systemd[1]: Starting Hostname Service…
Oct 19 12:49:14 rock64 systemd[1]: Starting Permit User Sessions…
Oct 19 12:49:14 rock64 systemd[1]: Finished Permit User Sessions.
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.3906] hostname: hostname: using hostnamed
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.3908] hostname: hostname changed from (none) to “rock64”
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.4029] dns-mgr[0xaaaad3318220]: init: dns=default,systemd-resolved rc-manager=symlink
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.4073] manager[0xaaaad333a030]: rfkill: Wi-Fi hardware radio set enabled
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.4074] manager[0xaaaad333a030]: rfkill: WWAN hardware radio set enabled
Oct 19 12:49:14 rock64 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg=‘unit=systemd-hostnamed comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.5698] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.26.2-1/libnm-device-plugin-bluetooth.so)
Oct 19 12:49:14 rock64 tlp[697]: Applying power save settings…done.
Oct 19 12:49:14 rock64 systemd-logind[638]: Watching system buttons on /dev/input/event0 ( RPI Wired Keyboard 1)
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.7411] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.26.2-1/libnm-device-plugin-team.so)
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.7567] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.26.2-1/libnm-device-plugin-wwan.so)
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.7845] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.26.2-1/libnm-device-plugin-wifi.so)
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8016] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.26.2-1/libnm-device-plugin-ovs.so)
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8117] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.26.2-1/libnm-device-plugin-adsl.so)
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8137] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8148] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8156] manager: Networking is enabled by state file
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8165] dhcp-init: Using DHCP client ‘internal’
Oct 19 12:49:14 rock64 dbus-daemon[624]: [system] Activating via systemd: service name=‘org.freedesktop.nm_dispatcher’ unit=‘dbus-org.freedesktop.nm-dispatcher.service’ requested by ‘:1.6’ (uid=0 pid=625 comm="/usr/bin/NetworkManager --no-daemon ")
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8428] settings: Loaded settings plugin: keyfile (internal)
Oct 19 12:49:14 rock64 systemd[1]: Starting Network Manager Script Dispatcher Service…
Oct 19 12:49:14 rock64 tlp[697]: Setting battery charge thresholds…done.
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8651] device (lo): carrier: link connected
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8665] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8686] device (eth0): driver ‘(null)’ does not support carrier detection.
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8696] device (eth0): driver ‘rk_gmac-dwmac’ does not support carrier detection.
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.8712] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.9172] settings: (eth0): created default wired connection ‘Wired connection 1’
Oct 19 12:49:14 rock64 NetworkManager[625]: [1603104554.9209] device (eth0): state change: unmanaged → unavailable (reason ‘managed’, sys-iface-state: ‘external’)
Oct 19 12:49:14 rock64 systemd-networkd[392]: eth0: Link UP
Oct 19 12:49:14 rock64 kernel: rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=POLL)
Oct 19 12:49:14 rock64 kernel: rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found
Oct 19 12:49:14 rock64 kernel: rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW
Oct 19 12:49:14 rock64 kernel: rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link modeOct 19 12:49:23 rock64 kernel: busb rockchip_usb2phy_otg_sm_work b_idle otg sm work 1
Oct 19 12:49:23 rock64 kernel: busb HOST = 0,VBUS_EN=0,vbus_attached=1
Oct 19 12:49:23 rock64 kernel: busb vbus_attach rphy->chg_state = 5Oct 19 12:49:25 rock64 systemd-networkd[392]: eth0: Gained carrier
Oct 19 12:49:25 rock64 kernel: rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Oct 19 12:49:25 rock64 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.2985] device (eth0): carrier: link connected
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3060] device (eth0): state change: unavailable → disconnected (reason ‘carrier-changed’, sys-iface-state: ‘managed’)
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3160] policy: auto-activating connection ‘Wired connection 1’ (465c6bd0-135d-38c9-a4f3-e1880bf7664d)
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3225] device (eth0): Activation: starting connection ‘Wired connection 1’ (465c6bd0-135d-38c9-a4f3-e1880bf7664d)
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3245] device (eth0): state change: disconnected → prepare (reason ‘none’, sys-iface-state: ‘managed’)
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3285] manager: NetworkManager state is now CONNECTING
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3308] device (eth0): state change: prepare → config (reason ‘none’, sys-iface-state: ‘managed’)
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3340] device (eth0): state change: config → ip-config (reason ‘none’, sys-iface-state: ‘managed’)
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3368] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3909] dhcp4 (eth0): option dhcp_lease_time => ‘86400’
Oct 19 12:49:25 rock64 polkitd[801]: Started polkitd version 0.118
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3930] dhcp4 (eth0): option domain_name => ‘local’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3934] dhcp4 (eth0): option domain_name_servers => ‘192.168.0.254’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3937] dhcp4 (eth0): option expiry => ‘1603190965’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3939] dhcp4 (eth0): option host_name => ‘rock64’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3942] dhcp4 (eth0): option ip_address => ‘192.168.0.53’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3944] dhcp4 (eth0): option next_server => ‘192.168.0.254’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3946] dhcp4 (eth0): option requested_broadcast_address => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3949] dhcp4 (eth0): option requested_domain_name => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3951] dhcp4 (eth0): option requested_domain_name_servers => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3953] dhcp4 (eth0): option requested_domain_search => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3956] dhcp4 (eth0): option requested_host_name => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3958] dhcp4 (eth0): option requested_interface_mtu => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3960] dhcp4 (eth0): option requested_ms_classless_static_routes => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3963] dhcp4 (eth0): option requested_nis_domain => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3965] dhcp4 (eth0): option requested_nis_servers => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3968] dhcp4 (eth0): option requested_ntp_servers => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3970] dhcp4 (eth0): option requested_rfc3442_classless_static_routes => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3972] dhcp4 (eth0): option requested_root_path => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3973] dhcp4 (eth0): option requested_routers => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3973] dhcp4 (eth0): option requested_static_routes => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3974] dhcp4 (eth0): option requested_subnet_mask => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3974] dhcp4 (eth0): option requested_time_offset => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3975] dhcp4 (eth0): option requested_wpad => ‘1’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3977] dhcp4 (eth0): option routers => ‘192.168.0.254’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3977] dhcp4 (eth0): option subnet_mask => ‘255.255.255.0’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.3978] dhcp4 (eth0): state changed unknown → bound
Oct 19 12:49:25 rock64 systemd-timesyncd[489]: Network configuration changed, trying to establish connection.
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.4041] device (eth0): state change: ip-config → ip-check (reason ‘none’, sys-iface-state: ‘managed’)
Oct 19 12:49:25 rock64 dbus-daemon[624]: [system] Activating via systemd: service name=‘org.freedesktop.nm_dispatcher’ unit=‘dbus-org.freedesktop.nm-dispatcher.service’ requested by ‘:1.6’ (uid=0 pid=625 comm=“/usr/bin/NetworkManager --no-daemon “)
Oct 19 12:49:25 rock64 systemd[1]: Starting Network Manager Script Dispatcher Service…
Oct 19 12:49:25 rock64 dbus-daemon[624]: [system] Successfully activated service ‘org.freedesktop.nm_dispatcher’
Oct 19 12:49:25 rock64 systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 19 12:49:25 rock64 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm=“systemd” exe=”/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Oct 19 12:49:25 rock64 kernel: audit: type=1130 audit(1603104565.440:54): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg=‘unit=NetworkManager-dispatcher comm=“systemd” exe=“/usr/lib/systemd/systemd” hostname=? addr=? terminal=? res=success’
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.4684] device (eth0): state change: ip-check → secondaries (reason ‘none’, sys-iface-state: ‘managed’)
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.4700] device (eth0): state change: secondaries → activated (reason ‘none’, sys-iface-state: ‘managed’)
Oct 19 12:49:25 rock64 kernel: busb rockchip_usb2phy_otg_sm_work b_idle otg sm work 1
Oct 19 12:49:25 rock64 kernel: busb HOST = 0,VBUS_EN=0,vbus_attached=1
Oct 19 12:49:25 rock64 kernel: busb vbus_attach rphy->chg_state = 5
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.4735] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.4794] manager: NetworkManager state is now CONNECTED_SITE
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.4801] policy: set ‘Wired connection 1’ (eth0) as default for IPv4 routing and DNS
Oct 19 12:49:25 rock64 NetworkManager[625]: [1603104565.9588] manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 19 12:49:26 rock64 dbus-daemon[624]: [system] Successfully activated service ‘org.freedesktop.UDisks2’Oct 19 12:49:29 rock64 kernel: busb rockchip_usb2phy_otg_sm_work b_idle otg sm work 1
Oct 19 12:49:29 rock64 kernel: busb HOST = 0,VBUS_EN=0,vbus_attached=1
Oct 19 12:49:29 rock64 kernel: busb vbus_attach rphy->chg_state = 5
Oct 19 12:49:31 rock64 kernel: busb rockchip_usb2phy_otg_sm_work b_idle otg sm work 1
Oct 19 12:49:31 rock64 kernel: busb HOST = 0,VBUS_EN=0,vbus_attached=1
Oct 19 12:49:31 rock64 kernel: busb vbus_attach rphy->chg_state = 5Oct 19 12:49:40 rock64 kernel: busb rockchip_usb2phy_otg_sm_work b_idle otg sm work 1
Oct 19 12:49:40 rock64 kernel: busb HOST = 0,VBUS_EN=0,vbus_attached=1
Oct 19 12:49:40 rock64 kernel: busb vbus_attach rphy->chg_state = 5Oct 19 12:52:37 rock64 kernel: busb rockchip_usb2phy_otg_sm_work b_idle otg sm work 1
Oct 19 12:52:37 rock64 kernel: busb HOST = 0,VBUS_EN=0,vbus_attached=1
Oct 19 12:52:37 rock64 kernel: busb vbus_attach rphy->chg_state = 5
Searching the web got me an approproate result on the pine64 forum:
https://forum.pine64.org/showthread.php?tid=9673&highlight=ethernet+slow
It states, that there is a problem with some rockchip drivers and large packet sizes. It is adviced to change some configuration in the device tree:
Change
snps,txpbl = <0x20>;
to
snps,txpbl = <0x4>;
I found 2 device tree files in /boot/dtbs/rockchip :
rk3399-rockpro64-v2.dtb and rk3399-rockpro64.dtb
Both files have the recommended setting of snps.txpbl = <0x04>.
But experimenting with ping shows cleary: Short packages are transmitted immediately, while large packages are not transmitted at all.
Any ideas what I could try next?
<0x4> is not the same as <0x04> though.
But yes. 0x4 is what’s in the kernel now.
In the dtb file there was 0x04. I changed it to 0x4. Didn’t make a difference.
I took the device tree from armbian. Now the network connection is fast! The device tree files from Manjaro and armbian are quite different. Now I wonder what can be done so that the armbian device tree finds its way into Manjaro?
In the upstream DTS it’s 0x4, not 0x04. So I don’t know where you got 0x04 from…
0x04 is what you get when you decompile the .dtb file. If it is the representation of a numerical value, 0x04 and 0x4 are just the same. So I guess it is just a formatting thing the dtc does.
But the good news is that the armbian .dtb fixes the issue and new issues did not arose using the armbian .dtb.
Cool. Glad it works for you.
Now if Armbian would upstream the changes they have made, as kernel patches, we could all benefit. 
I prepared a installation on an emmc. Former tests were executed from a SD card. I copied the working armbian device tree file from the SD card to the emmc. System booted fine from the emmc, but wired connection is not working. network manager establishes the connection and drops it. In the journal I see messages, “kernel: carrier lost”. Is it plausible to anybody, that a configuration, which works when booting from a SD card is not working when booting the same configuration from an emmc?
Consider, when you were booting from SD it most likely was using uboot from emmc
That may be the difference