Hello, my TX1 runs on Ubuntu, it only has ethernet interface ‘eth0’. Not a single wireless interface is found.
lspci gives me nothing.
I wonder does the TX1 by default has a wifi network card? How would I enable wifi on my TX1?
Thanks
Hi lanfker,
Please try the wifi config check tool in this page.
http://developer.download.nvidia.com/embedded/jetson/TX1/tools/wifi_config_check/README_wifi_config_check.txt
http://developer.download.nvidia.com/embedded/jetson/TX1/tools/wifi_config_check/wifi-config-check.sh
Hello Wayne,
From your answer, I guess the TX1 comes with a WIFI card installed already (correct me if I am wrong).
I have installed ‘linux-firmware’ with the command
sudo apt-get install linux-firmware
, and I actually have tried the script ‘wifi-config-check.sh’ with command
sudo ./wifi-config-check.sh
, and it gave me the following results(both terminal and log file):
<b>Output in the terminal: </b>
Checking MAC address configuration
MAC address configuration is correct.
Checking WiFi settings next
=========================================
Test inconclusive (WiFi settings unknown). Please make sure WiFi is enabled under network settings, reboot the system and re-run this test. If you encounter this error again, visit the product support page at https://developer.nvidia.com/embedded/support
=========================================
Please check file: /home/ubuntu/wifi-config-check-log for more details
=========================================
Output in the wifi-config-check-log:
## This generated file provides details if the Jetson-TX1 is configured properly for Wireless connections or not
Serial Number of Module is 0324415031626
Serial Number for Base board is 0324415051249
Test inconclusive (WiFi settings unknown). Please make sure WiFi is enabled under network settings, reboot the system and re-run this test. If you encounter this error again, visit the product support page at https://developer.nvidia.com/embedded/support
The network manager does not have an option ‘enable wifi’. It only has ‘enable networking’ which confuses me.
When I try the command
iw list
I got error ‘nl80211 not found.’ I suspect the Ubuntu systme lacks necessary files for WIFI support. Things are weird.
Do you install tegra with jetpack?
Does wlan0 is shown in iwconfig?
lanfker,
Could you share following info?
- “ifconfig -a” output
- dmesg logs from boot.
Hello Wayne.
Before you dive into the logs, my first question was simple. With the default Ubuntu system on a standard TX1, is the WIFI automatically supported (at least it can scan available wifi SSIDs)?
For Jetpack, I am not sure if the TX1 has it installed. Is there a way to verify that?
‘wlan0’ does not show in iwconfig. I highly suspect my Ubuntu system is has been reconfigured. I am not the one who installed the system on my TX1.
Command:
ifconfig
can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
can1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
can2 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
can3 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
can4 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
can5 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
can6 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP RUNNING NOARP MTU:16 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
dummy0 Link encap:Ethernet HWaddr 7e:2d:e9:68:bd:aa
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 00:04:4b:57:ff:bc
inet addr:192.168.10.15 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::204:4bff:fe57:ffbc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3542 errors:0 dropped:0 overruns:0 frame:0
TX packets:3365 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2276845 (2.2 MB) TX bytes:487349 (487.3 KB)
ip6tnl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1452 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:267 errors:0 dropped:0 overruns:0 frame:0
TX packets:267 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19014 (19.0 KB) TX bytes:19014 (19.0 KB)
rmnetctl Link encap:IPIP Tunnel HWaddr
NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
tunl0 Link encap:IPIP Tunnel HWaddr
NOARP MTU:0 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Kernel log from a fresh boot
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.726009] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-base.c:617 (cvgw_register_device): Functionality can registered
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.726018] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-socketcan.c:1082 (__cvgw_cvgw_socketcan_init): can device initalized
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.753033] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-bus-spi.c:365 (cvgw_spi_probe): spi probe
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.764276] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-base.c:767 (cvgw_probe): General cvgw probe function call
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.784155] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-base.c:686 (insert_modules): Adding device can
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.894268] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-base.c:730 (configure_modules): Configuring device can
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901752] socketcan can0: setting baud-rate <0>: 33.3K
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901784] socketcan can1: setting baud-rate <4>: 500K
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901806] socketcan can2: setting baud-rate <3>: 250K
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901826] socketcan can3: setting baud-rate <3>: 250K
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901851] socketcan can0: adding 29-bit rx id: 0x102F6040
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901875] socketcan can0: adding 29-bit rx id: 0x102F8040
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901896] socketcan can0: adding 29-bit rx id: 0x102FA040
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901916] socketcan can0: adding 29-bit rx id: 0x10630040
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901935] socketcan can0: adding 29-bit rx id: 0x102A8097
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901953] socketcan can0: adding 29-bit rx id: 0x102AA097
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901974] socketcan can0: adding 29-bit rx id: 0x102AC097
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.901993] socketcan can0: adding 29-bit rx id: 0x10336058
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902014] socketcan can0: adding 29-bit rx id: 0x10424040
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902032] socketcan can0: adding 29-bit rx id: 0x1020C040
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902051] socketcan can0: adding 29-bit rx id: 0x1072E05B
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902070] socketcan can1: adding 11-bit rx id: 0xF1
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902089] socketcan can1: adding 11-bit rx id: 0x1E9
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902108] socketcan can1: adding 11-bit rx id: 0x1F5
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902126] socketcan can1: adding 11-bit rx id: 0x12A
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902146] socketcan can1: adding 11-bit rx id: 0x3E9
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902166] socketcan can1: adding 11-bit rx id: 0x17D
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902184] socketcan can1: adding 11-bit rx id: 0x3D1
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902202] socketcan can1: adding 11-bit rx id: 0x120
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902221] socketcan can1: adding 11-bit rx id: 0x1E5
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902239] socketcan can1: adding 11-bit rx id: 0xC9
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902262] socketcan can2: adding 11-bit tx id: 0x140
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902278] socketcan can2: adding 11-bit rx id: 0x14A
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902299] socketcan can3: adding 11-bit tx id: 0x140
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902315] socketcan can3: adding 11-bit rx id: 0x14A
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902333] socketcan can5: adding 11-bit rx id: 0x1C
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902351] socketcan can5: adding 11-bit rx id: 0x1D
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902372] socketcan can6: adding 11-bit tx id: 0x11
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902390] socketcan can6: adding 11-bit tx id: 0x1
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902408] socketcan can6: adding 11-bit tx id: 0x2
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902425] socketcan can6: adding 11-bit tx id: 0x3
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902443] socketcan can6: adding 11-bit tx id: 0x4
Jul 20 09:16:20 tegra-ubuntu kernel: [ 28.902537] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-bus-spi.c:440 (cvgw_spi_probe): SPI probe successful!
Jul 20 09:16:20 tegra-ubuntu kernel: [ 29.294201] Received reset ack from cvgw…
Jul 20 09:16:21 tegra-ubuntu kernel: [ 29.900413] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-base.c:496 (unhandled_rx_id): Unhandled message ID 6 received
Jul 20 09:16:21 tegra-ubuntu kernel: [ 29.902016] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-base.c:496 (unhandled_rx_id): Unhandled message ID 6 received
Jul 20 09:16:21 tegra-ubuntu kernel: [ 29.903463] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-base.c:496 (unhandled_rx_id): Unhandled message ID 6 received
Jul 20 09:16:21 tegra-ubuntu kernel: [ 29.905010] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-base.c:496 (unhandled_rx_id): Unhandled message ID 6 received
Jul 20 09:16:21 tegra-ubuntu kernel: [ 29.906500] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-base.c:496 (unhandled_rx_id): Unhandled message ID 6 received
Jul 20 09:16:21 tegra-ubuntu kernel: [ 29.908012] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-base.c:496 (unhandled_rx_id): Unhandled message ID 6 received
Jul 20 09:16:21 tegra-ubuntu kernel: [ 29.909507] /home/dge/proj/tx1gw/fev/drivers/s12driver/obj/cvgw-base.c:496 (unhandled_rx_id): Unhandled message ID 6 received
For the output of
dmesg
, it is too long, so I am using google drive to share it. Here is the link: https://docs.google.com/document/d/1IFiOTnxQz2sPuw2XwqxoaeGHpVROd27yl9ZYlgQ2rDg/edit?usp=sharing Thanks!
It sure doesn’t like firefox. Are you starting firefox right after login? Is there any particular web site you are loading on firefox when it crashes (e.g., viewing flash content versus an ordinary web page)? I could see the possibility that if something goes wrong in the kernel while running firefox, then it might have an effect on drivers such as WiFi. There isn’t enough of a stack frame from the message to know much more than firefox made a system call and things went bad.
Hi linuxdev,
The WIFI never worked. I think this customized (by somebody) Ubuntu has messed up the WIFI module. I tried another brand-new TX1, and it has ‘wlan0’ by default.
I think I already know the answer to my question.
For Jetpack, I am not sure if the TX1 has it installed. Is there a way to verify that?
Please download Jetpack from this site and use it to flash your board:
I will install Jetpack. Thank you, Wayne.