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.
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.
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.
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.
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
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/
Dear yliu
Could you please file a bug for your topic?
Please share bug ID, we will look into this issue.
Please login to https://developer.nvidia.com/drive with your credentials. Please check MyAccount->MyBugs->Submit a new bug to file bug. Thanks.
The bug ID is 2710030. Just you know the situation changes a little bit after a reboot (missed this step from your guide), the time jump persist, but between current time and 7 hours before, considering I’m in PDT time zone (UTC-7). So the RTC dongle works, but it’s confusing about the time zones.
HI SteveNV,
are there any updates on this? We’re seeing similar issues with the system time constantly being reset to 2017, even with internet connection and a working RTC.
There were network problem on the setup (that should be fixed to get RTC working).
According to the log, yliu wasn’t able to ping google.com, and nv_rtc_sync service uses “time.google.com” as NTPSERVER to set current date to system as well as on RTC module.
So ping to NTPSERVER should work fine to get RTC working.
Logs from Tegra ( Ping to NTPSERVER and rtc service status ) -
nvidia@tegra-ubuntu:~$ ping time.google.com -c 5
PING time.google.com (216.239.35.0) 56(84) bytes of data.
64 bytes from time1.google.com (216.239.35.0): icmp_seq=1 ttl=41 time=58.7 ms
64 bytes from time1.google.com (216.239.35.0): icmp_seq=2 ttl=41 time=58.6 ms
64 bytes from time1.google.com (216.239.35.0): icmp_seq=3 ttl=41 time=58.8 ms
64 bytes from time1.google.com (216.239.35.0): icmp_seq=4 ttl=41 time=58.8 ms
64 bytes from time1.google.com (216.239.35.0): icmp_seq=5 ttl=41 time=58.8 ms