Hello ,
We are Installing jetpack 2.2.1 on Tegra TX1 using
Host Specification :
Internet connection is stable and all downloads are fine.
Main problem : When installing 64bit ubuntu using the JetPack the proccesser field comes empty as shown in the attached image, the OS keeps hanging and it doesn’t work probably.
note that, it works well if we installed 32bit ubuntu using JetPack.
More information
abdullah@abdullah-HP-ProBook-4540s:~$ uname -a
Linux abdullah-HP-ProBook-4540s 4.2.0-42-generic #49~14.04.1-Ubuntu SMP Wed Jun 29 20:22:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
abdullah@abdullah-HP-ProBook-4540s:~$ lsusb
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 1bcf:2c29 Sunplus Innovation Technology Inc.
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0480:a200 Toshiba America Inc
Bus 001 Device 007: ID 0955:7721 NVidia Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
abdullah@abdullah-HP-ProBook-4540s:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz
stepping : 9
microcode : 0x16
cpu MHz : 1200.468
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 5188.22
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz
stepping : 9
microcode : 0x16
cpu MHz : 1203.820
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 5188.22
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz
stepping : 9
microcode : 0x16
cpu MHz : 1218.851
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 2
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 5188.22
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz
stepping : 9
microcode : 0x16
cpu MHz : 1395.773
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 2
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 5188.22
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
kayccc
August 1, 2016, 8:12am
2
Hi Abdullah-Kamel,
I can’t see the picture that you inserted, would you please re-attach it again?
Thanks
Is JetPack being run on the Jetson? If so, this is why it fails…JetPack runs only on a desktop x86_64 PC.
t
No , JetPack is running in a pc running on ubuntu 64bit.https://www.youtube.com/watch?v=DyhRMjaUknQ
and as i said , it’s working great if 32bit os was installed through JetPack , the problem only occurs if i installed 64 bit through the JetPack
On the host, while Jetson is connected in recovery mode, what is the output of the following?
uname -a
lsusb
cat /proc/cpuinfo
On the host, while Jetson is connected in recovery mode, what is the output of the following?
uname -a
lsusb
cat /proc/cpuinfo
abdullah@abdullah-HP-ProBook-4540s:~$ uname -a
Linux abdullah-HP-ProBook-4540s 4.2.0-42-generic #49~14.04.1-Ubuntu SMP Wed Jun 29 20:22:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
abdullah@abdullah-HP-ProBook-4540s:~$ lsusb
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 1bcf:2c29 Sunplus Innovation Technology Inc.
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0480:a200 Toshiba America Inc
Bus 001 Device 007: ID 0955:7721 NVidia Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
abdullah@abdullah-HP-ProBook-4540s:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz
stepping : 9
microcode : 0x16
cpu MHz : 1200.468
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 5188.22
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz
stepping : 9
microcode : 0x16
cpu MHz : 1203.820
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 5188.22
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz
stepping : 9
microcode : 0x16
cpu MHz : 1218.851
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 2
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 5188.22
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz
stepping : 9
microcode : 0x16
cpu MHz : 1395.773
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 2
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 5188.22
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
From the above I’d say there is no reason why JetPack should fail. Unfortunately, the “image” attachment failed and is not displaying. Could you try attaching another image or screenshot…and if this doesn’t work, maybe describe in more detail? The image attach function seems to sometimes fail…I don’t know what the requirements are, maybe an image larger than a certain size doesn’t post.
i have found that many forums have the display image issue and one way of getting around that is to put the image on google drive, or similar, mark it as shareable, get the link and post the link in the forum post. that method seems to always work for me as far as i have experienced. i guess the forum in question has to allow external links, though most do.
From the above I’d say there is no reason why JetPack should fail. Unfortunately, the “image” attachment failed and is not displaying. Could you try attaching another image or screenshot…and if this doesn’t work, maybe describe in more detail? The image attach function seems to sometimes fail…I don’t know what the requirements are, maybe an image larger than a certain size doesn’t post.
i have found that many forums have the display image issue and one way of getting around that is to put the image on google drive, or similar, mark it as shareable, get the link and post the link in the forum post. that method seems to always work for me as far as i have experienced. i guess the forum in question has to allow external links, though most do.
Image updated.
I am at a disadvantage since my Fedora host can’t run JetPack. It does seem like the processor field should not be empty. I also see it says disk 0 bytes. Is this host’s hard drive completely filled? If not, then something is also preventing this from correct detection. Someone else woudl have to comment on why the processor can’t be detected since the host is obviously valid in all ways.
I am at a disadvantage since my Fedora host can’t run JetPack. It does seem like the processor field should not be empty. I also see it says disk 0 bytes. Is this host’s hard drive completely filled? If not, then something is also preventing this from correct detection. Someone else woudl have to comment on why the processor can’t be detected since the host is obviously valid in all ways.
The host hard drive is totally empty. idk why this happening
you need to just pack it in and start all over. nothing is making any sense at all. a completely empty hard drive? just no sense at all. format the drive on the host, install ubuntu, then try tx1 jetpack again.
Some parts of install do require the host to have ext4 or native Linux file system. I doubt the issues you’ve seen would be caused by incorrect file system type, but just to be thorough, what is the output of “df -h -T”, and which of the listed file systems has JetPack on it? I agree with @dkryder , something very strange is going on.
I’m going to reinstall ubuntu 14.04 64bit on the host.
After installing , it doesn’t work again.
got a host with ubuntu 14.04 installed from the official site.
jachen
August 29, 2016, 2:51am
17
Hello, Abdullah-Kamel:
If the whole system crash, would you please provide the kernel crash log?
br
Hello, Abdullah-Kamel:
If the whole system crash, would you please provide the kernel crash log?
br
Dear Chenjian,
The first time i unboxed the TX1 i flashed it using JetPack 2.0 [L4T r23.1] , everything was going well and it was working perfectly. After that the update of JetPack 2.1 was released and it’s also was working perfectly without any problems. Untill JetPack 2.2 [L4T r21.4] was released, Starting from here i faced the problem of hanging [ while working the mouse stopped and the OS doesn’t respond until hard reset ] which bothered me. i looked at System Settings>Details. There was info missed such as processor the thing i couldn’t understand !.
i found this topic which discussed the same problem of minehttps://devtalk.nvidia.com/default/topic/956165/jetson-tx1/cpu-info-not-shown-after-jetpack-2-2-1-on-tx1-/
Also, Do you recommend me to back to JetPack 2.0 ?
