Hi,
-
Devkit means the nvidia development kit.
-
Ok, then we will see if other alternative ways to debug this…
Could you share what you’ve done so far? I mean what DTS change and driver update have you done to the original codebase.
Hi,
Devkit means the nvidia development kit.
Ok, then we will see if other alternative ways to debug this…
Could you share what you’ve done so far? I mean what DTS change and driver update have you done to the original codebase.
Hi:
1: In fact, the work I did was described at the beginning 2, 3 and 4 part.
2: About dts:
pcie@14160000 {
status = “okay”;
nvidia,pex-wake = <&tegra_main_gpio TEGRA194_MAIN_GPIO(L, 2)
GPIO_ACTIVE_LOW>;
vddio-pex-ctl-supply = <&p3668_spmic_sd3>;
nvidia,disable-aspm-states = <0xf>;
//nvidia,enable-power-down;
......
};
fragement-tegra-pcie-c4-dis {
ids = ">=3668-0001-000";
override@0 {
target = <&{/pcie@14160000}>;
_overlay_ {
status = "okay";
};
};
};
};
3: about RTL811G, With the help of RTL FAE. I disabled realtek driver in NX source code, disabled eqos ether.
And update RTL driver(0010-r8168-8.045.08 Linux_r8168-8.047.05.pci-dis.notso and r8168-8.047.04) in NX by make and make install. At the suggestion of FAE, we close ASPM, and check IRQ.
4: We connect NX directly to routers.
sudo busybox udhcpc
sudo ip address add 192.168.1.201 dev eth1 : set static ip address
sudo route add default gw 192.168.1.1 : add gateway
5: We connect NX directly to PC, It has been described above.
One thing I noticed in your error log:
Jan 29 00:45:25 ec-desktop nm-connection-e[21594]: Cannot save connection due to error: Invalid setting IPv4 Settings: ipv4.addresses: this property cannot be empty for 'method=manual'
Jan 29 00:45:26 ec-desktop nm-connection-e[21594]: Cannot save connection due to error: Invalid setting IPv4 Settings: IPv4 address “” invalid
Jan 29 00:45:32 ec-desktop nm-connection-e[21594]: Cannot save connection due to error: Invalid setting IPv4 Settings: IPv4 address netmask “” invalid
I doubt an invalid value would cause the interface to not show up, but what interfaces do you see under “sudo nm-connection-editor”? One thing manual would do though is to guarantee no DHCP request would ever be attempted. You might need to “sudo apt-get install network-manager-gnome” to use nm-connection-editor.
Hi,
1: In fact, the work I did was described at the beginning 2, 3 and 4 part.
Yes, but we want to check the patch/code directly but not just description. Is there any other change than dts change in pcie?
I also wonder why do you hit this error.
[ 94.976759] r8168 0004:01:00.0 (unnamed net_device) (uninitialized): bad mac address at /chosen/nvidia,ethernet-mac: missing.
This node should be prepared by cboot. Could you share the directory list of /proc/device-tree/chosen?
This problem has been solved, and it is the problem of the circuit. Thank you for your help. Sorry for taking up your time.