How to set static IP in TX2 with L4T -R26

I have modify file /etc/network/interfaces as
{
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
#source-directory /etc/network/interfaces.d
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 8.8.8.8 8.8.4.4

}
But it does not work

And then I remove the network-manager,
using /etc/network/interfaces to set IP, but is still does not work

I often find that although “/etc/network/interfaces.d/” is meant to have all files there read automatically, that instead I must specifically source files there. So for example, if you have “eth0” (using the IP addresses in your example), my “/etc/network/interfaces” file might have:

# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
source interfaces.d/eth0

The minimal “/etc/network/interfaces.d/eth0” file might be something like this:

auto eth0
iface eth0 inet static
address 192.168.1.10
netmask 255.255.255.0

I try

  1. # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d

and

  1. # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d source interfaces.d/eth0

but still useless, the IP always is 192.168.2.147(maybe set by network-manage), no matter what i set.
and i modify /etc/NetworkManager/Networkmager.cong,
set “managed=false” to “managed=true”,it always useless

NetworkManager is always frustrating. You may need to explore the GUI control of this from a local login. Have you logged in and use the network configuration GUI utilities?

If you are connecting to a network with DHCP server, are you sure that address 192.168.1.10 is within its static (fixed) IPs range ?

[EDIT: Side note: what does R26 stands for ? I think that first (pre)release for TX2 was R27.0, maybe on TK1 there have been R21.6… Where did you get this L4T R26 for TX2 ? Current version is R28.2]

the nmcli command line can be used to create named connections that will survive reboots. See example #9 for static IP config. In my experience a connection created this way will automatically reconnect at startup if the link is available but will not autoconnect when the system is up and the link is plugged in.

https://people.freedesktop.org/~lkundrak/nm-docs/nmcli-examples.html

Example 9. Adding an ethernet connection profile with manual IP configuration

$ nmcli con add con-name my-con-em1 ifname em1 type ethernet \
  ip4 192.168.100.100/24 gw4 192.168.100.1 ip4 1.2.3.4 ip6 abbe::cafe
$ nmcli con mod my-con-em1 ipv4.dns "8.8.8.8 8.8.4.4"
$ nmcli con mod my-con-em1 +ipv4.dns 1.2.3.4
$ nmcli con mod my-con-em1 ipv6.dns "2001:4860:4860::8888 2001:4860:4860::8844"
$ nmcli -p con show my-con-em1

The first command adds an Ethernet connection profile named my-con-em1 that is bound to interface name em1. The profile is configured with static IP addresses. Three addresses are added, two IPv4 addresses and one IPv6. The first IP 192.168.100.100 has a prefix of 24 (netmask equivalent of 255.255.255.0). Gateway entry will become the default route if this profile is activated on em1 interface (and there is no connection with higher priority). The next two addresses do not specify a prefix, so a default prefix will be used, i.e. 32 for IPv4 and 128 for IPv6. The second, third and fourth commands modify DNS parameters of the new connection profile. The last con show command displays the profile so that all parameters can be reviewed.