Dear s18,
Can’t you set it up with the setting steps I provided above? Thanks.
It is the result that I tried earlier.
None of them will help.
nvidia@tegra-ubuntu:~$ sudo bash /usr/local/sbin/canrtc.sh set
setting time and date to "1e.2b.15.03.05.07.11"
nvidia@tegra-ubuntu:~$ sudo bash /usr/local/sbin/canrtc.sh get
Setting time and date to: 21:43:32, day of week: 3, 07/05/2017
2017/07/05 21:43:32
nvidia@tegra-ubuntu:~$ sudo bash /etc/systemd/scripts/nv_rtc_sync.sh
try_ntp 5 Jul 21:43:45 ntpdate[24435]: no server suitable for synchronization found
getting rtcSetting time and date to: 21:43:45, day of week: 3, 07/05/2017
2017/07/05 21:43:45
reboot
nvidia@tegra-ubuntu:~$ date
Wed Jul 5 21:45:00 JST 2017
Dear s18,
I wonder you have internet access and set the time correctly without the RTC dongle like below.
Did you set the time “Automatically from the Internet” in Time & Date like below capture?Image
External Media
Then you can check time with date command on the terminal.
nvidia@tegra-ubuntu:~$ date
Wed Aug 28 11:11:11 KST 2019
Could you please upload all steps you set up as I did above?
First, I removed RTC dongle and set it like an image.
Then I tried the following command.
nvidia@tegra-ubuntu:~$ date
Tue Jul 4 16:39:24 JST 2017
nvidia@tegra-ubuntu:~$ sudo bash /etc/systemd/scripts/nv_rtc_sync.sh
try_ntp 4 Jul 16:39:37 ntpdate[3585]: no server suitable for synchronization found
getting rtccould not get time from dongle
Could not get time from RTC dongle
nvidia@tegra-ubuntu:~$ date
Tue Jul 4 16:39:51 JST 2017
reboot
The date command was still in 2017
The result does not change.
Dear s18,
I’d like to know if you connect to Internet and get IP address properly.
nvidia@tegra-ubuntu:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr
inet addr:xx.xx.xx.xx Bcast:10.19.11.255 Mask:255.255.255.0
inet6 addr: fe80::204:4bff:fea4:e7ca/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9563 errors:0 dropped:0 overruns:0 frame:0
TX packets:8125 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6077291 (6.0 MB) TX bytes:662274 (662.2 KB)
Interrupt:82
nvidia@tegra-ubuntu:~$ ping www.google.com
PING www.google.com (216.58.213.100) 56(84) bytes of data.
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=1 ttl=44 time=247 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=2 ttl=44 time=247 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=3 ttl=44 time=247 ms
64 bytes from lhr25s02-in-f4.1e100.net (216.58.213.100): icmp_seq=4 ttl=44 time=247 ms
Then set the time “Automatically from the Internet” in Time & Date like below capture.
External Media
If you run the command without the RTC dongle, an error occurs. The message is expected.
Could you please upload your full step and log on the topic? Thanks.
You can see that the ip4 address has been acquired.
However, pings from ww.google.com will not return.
nvidia@tegra-ubuntu:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:04:4b:af:74:81
<b>inet addr:192.1XX.XX.XX </b>Bcast:192.1XX.XX.XXX Mask:255.255.255.0
inet6 addr: fe80::204:4bff:feaf:7481/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3055 errors:0 dropped:1 overruns:0 frame:0
TX packets:3950 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:225837 (225.8 KB) TX bytes:284224 (284.2 KB)
Interrupt:82
nvidia@tegra-ubuntu:~$ ping www.google.com
PING www.google.com (172.217.161.36) 56(84) bytes of data.
^C
--- www.google.com ping statistics ---
312 packets transmitted, 0 received, 100% packet loss, time 318461ms
Dear s18,
According to the log you provided, I think the DriveAGX seems to have no internet connection.
Did you set eth0’s IP manually? Because of eth0 inet addr : 192.1XX.XX.XX
If yes, could you please check your internal internet? Thanks.
In the XX part, this exchange is open to the public and is set to X for information protection.
I once set up Xavier and my host PC for help and advice during setup. (About setup animation scp command - DRIVE AGX General - NVIDIA Developer Forums)
However, I think that the IP address was reset when restarting.
Dear s18,
In the XX part, this exchange is open to the public and is set to X for information protection.
→ Could you let me know what mean is?
I once set up Xavier and my host PC for help and advice during setup. (About setup animation scp command - DRIVE AGX General - NVIDIA Developer Forums)
However, I think that the IP address was reset when restarting.
→ The IP setting you mentioned the way is not permanent and just for DriveAGX <–> HostPC not for public internet connection, the system will reboot and return to its default setting.
I’m sorry.
As for the meaning of the part of XX, I can’t tell you what I want to say in English, so I will post the result again.
nvidia@tegra-ubuntu:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:04:4b:af:74:81
inet addr:192.168.11.23 Bcast:192.168.11.255 Mask:255.255.255.0
inet6 addr: fe80::204:4bff:feaf:7481/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3055 errors:0 dropped:1 overruns:0 frame:0
TX packets:3950 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:225837 (225.8 KB) TX bytes:284224 (284.2 KB)
Interrupt:82
Dear s18,
Can you connect to Internet from another PC or device with that IP?
If it’s a Internet connection symptom with your company’s internal network, you should contact your IT representative.
Even if you connect the Ethernet cable connected to Xavier directly to the host PC (ubuntu16.04), you can use the Internet and get the time. But there was no ping response.
It may be different because the IP address is automatically acquired.
Host PC
@ m15: ~ $ ifconfig -a
enp110s0 Link encap: Ethernet hardware address 00: 4e: 01: 9c: 97: 2d
inet address: 192.168.11.34 broadcast: 192.168.11.255 mask: 255.255.255.0
inet6 address: fe80 :: 777c: 5d83: 699b: 564c / 64 range: link
UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1
RX packet: 338 Error: 0 Loss: 0 Overrun: 0 Frame: 0
TX packet: 270 Error: 0 Loss: 0 Overrun: 0 Carrier: 0
Collisions: 0 TX queue length: 1000
RX byte: 49745 (49.7 KB) TX byte: 41348 (41.3 KB)
Interrupt: 18
@ m15: ~ $ ping www.google.com
PING www.google.com (172.217.161.36) 56 (84) bytes of data.
^ C
--- www.google.com ping statistics ---
16 packets transmitted, 0 received, 100% packet loss, time 15357ms
Dear s18,
You mean you can access Internet but can’t reach to www.google.com with ping command?
And you can get the time properly via Automatically from the Internet?
If yes, you can set clock with RTC module and command? Thanks.
I tried ping www.google.com again on my host PC, Xavier, but there was no response.
Is it still difficult in a proxy environment?
Also, Xavier suddenly disappears from the display and other things cannot be tested.
The cause is unknown, but now it appears on the display after restarting in 1.5 hours.
- Connect Ethernet and turn on RTC Module and Dual GbE Dongle.
- Turn on Xavier
- Switch the date and time setting to automatic acquisition from the Internet
- Enter the following command
nvidia@tegra-ubuntu:~$ date
Tue Jul 11 17:03:32 JST 2017
nvidia@tegra-ubuntu:~$ sudo bash /etc/systemd/scripts/nv_rtc_sync.sh
try_ntp11 Jul 17:03:52 ntpdate[11967]: no server suitable for synchronization fo
und
getting rtcSetting time and date to: 17:03:52, day of week: 2, 07/11/2017
2017/07/11 17:03:52
nvidia@tegra-ubuntu:~$ ping www.google.com
PING www.google.com (172.217.161.36) 56(84) bytes of data.
^C
--- www.google.com ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 8173ms
The cause is unknown, but now it appears on the display after restarting in 1.5 hours.
Connect Ethernet and turn on RTC Module and Dual GbE Dongle.
Turn on Xavier
Switch the date and time setting to automatic acquisition from the Internet
Enter the following command
Also when RTC Dongle is connected
getting rtccould not get time from dongle
Could not get time from RTC dongle
You may also see an error like
There was also a response when I entered the IP address of the university server with the ping command.
nvidia@tegra-ubuntu:~$ ping 202.250.64.145
PING 202.250.64.145 (202.250.64.145) 56(84) bytes of data.
64 bytes from 202.250.64.145: icmp_seq=1 ttl=252 time=4.99 ms
64 bytes from 202.250.64.145: icmp_seq=2 ttl=252 time=4.95 ms
64 bytes from 202.250.64.145: icmp_seq=3 ttl=252 time=4.96 ms
64 bytes from 202.250.64.145: icmp_seq=4 ttl=252 time=4.97 ms
64 bytes from 202.250.64.145: icmp_seq=5 ttl=252 time=4.96 ms
64 bytes from 202.250.64.145: icmp_seq=6 ttl=252 time=4.94 ms
^C
--- 202.250.64.145 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 4.941/4.965/4.994/0.092 ms
Since it is through a proxy server in the campus network, you may not get ping results directly from google.
Dear s18,
Under proxy environment, please contact your IT representative and fix Internet connection issue.
I think you are using your PC to connect to the Internet.
To use the Internet, Drive AGX will need the same proxy settings as your PC. Thanks.
Why is the automatic acquisition from the Internet changed to manual time every time I restart Xavier?
Can I get the time from a proxy server on campus?
Or, I tried to rewrite the date command or manually, but I still could not get the date and time.
Dear s18,
Could you please help to check first to see if you get the correct date and time from your proxy server?
After that, please follow the instructions I gave you.
Tested on the host PC.
This is the result of using the ntp command on the university server (xxxxx-it.ac.jp).
<b>HOST PC</b>
$ sudo timedatectl status
Local time: 火 2019-09-10 16:35:04 JST
Universal time: 火 2019-09-10 07:35:04 UTC
RTC time: 火 2019-09-10 07:35:09
Time zone: Asia/Tokyo (JST, +0900)
Network time on: yes
NTP synchronized: no
RTC in local TZ: no
$ sudo ntpdate xxxxxxx-it.ac.jp
10 Sep 16:48:48 ntpdate[8335]: adjust time server 202.xxx.xx.xxx offset 0.008139 sec
Hi SteveNV,
I was also experiencing similar issue about system time jump on Pegasus. I verified that I have good internet connection. After setting the time to “Automatically from the Internet”, the time has been successfully synced, from some factory time of 2017 to current one of 2019. But it didn’t last long. Every half minute or so, the time on setting interface started to jump, back and forth between 2017 and 2019. This can also be observed in “watch -n1 timedatectl”, like following. Another observation is, the “NTP synchronized” keeps flipping between “yes” and “no” nonstop.
Local time: Tue 2017-07-04 02:50:49 PDT
Universal time: Tue 2017-07-04 09:50:49 UTC
RTC time: n/a
Time zone: America/Los_Angeles (PDT, -0700)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
Local time: Thu 2019-09-19 11:41:57 PDT
Universal time: Thu 2019-09-19 18:41:57 UTC
RTC time: n/a
Time zone: America/Los_Angeles (PDT, -0700)
Network time on: yes
NTP synchronized: no
RTC in local TZ: no
I attempted to fix this with RTC dongle. By following your steps, I can get correct system time from RTC dongle. But regardless, the above issue persists, even with “sudo bash /etc/systemd/scripts/nv_rtc_sync.sh”.
I found another post by you, and wondering if it is the cause of my issue? My guess is, the AURIX time has the factory time of 2017, the ntp server get the current time from Internet, these two are conflicting and changing system time dynamically. So could I fix this by setting the AURIX time to the latest? If so, how should I do it? Currently I was about to connect to AURIX server through minicom. None of the “ttyUSB*” has any response.
https://devtalk.nvidia.com/default/topic/1031778/faq/drive-px2-time-sync-guide/
Your response is highly appreciated. Thanks