LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware > Linux - Embedded & Single-board computer
User Name
Password
Linux - Embedded & Single-board computer This forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.

Notices


Reply
  Search this Thread
Old 07-10-2017, 02:22 PM   #1
Emilelf
LQ Newbie
 
Registered: Jul 2017
Posts: 1

Rep: Reputation: Disabled
Ethernet connection missing after Cuda installation failure with Jetpack


Ubuntu 16.04LTS, Jetson TX2, Jetpack 3.
Computer and Jetson connected to a hub, connected to internet.

After downloading Jetpack 3, I tried to flash the Jetson and install Cuda 8.
I tried to install using two different computers (wifi turned off).
I wasn't able to install Cuda, I had an error.
For both computers, after the failure during the installation, the Ethernet connection doesn't work anymore.
I checked and compared with another computer the /etc/network/interfaces and /etc/NetworkManager/NetworkManager.conf files.

I hope that someone could help me.

I tried these commands to figure out what was wrong.

Code:
$ ifconfig eth0

eth0      Link encap:Ethernet  HWaddr 28:f1:0e:48:52:d2  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:241328 errors:0 dropped:885 overruns:0 frame:0
          TX packets:4512 errors:34 dropped:0 overruns:0 carrier:34
          collisions:541 txqueuelen:1000 
          RX bytes:24081526 (24.0 MB)  TX bytes:1106325 (1.1 MB)
          Interrupt:16 Memory:dd400000-dd420000 

$ cat /etc/network/interfaces

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

$ cat /etc/NetworkManager/NetworkManager.conf 

[main]
plugins=ifupdown,keyfile,ofono
dns=dnsmasq

[ifupdown]
managed=false


$ journalctl -f

Jul 07 18:35:05 toromachine dhclient[22025]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 (xid=0x6a052979)
Jul 07 18:35:09 toromachine dhclient[22025]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0x6a052979)
Jul 07 18:35:19 toromachine dhclient[22025]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18 (xid=0x6a052979)
Jul 07 18:35:37 toromachine dhclient[22025]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0x6a052979)
Jul 07 18:35:47 toromachine NetworkManager[19050]: <warn>  [1499477747.7752] dhcp4 (eth0): request timed out
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.7753] dhcp4 (eth0): state changed unknown -> timeout
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8079] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 22025
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8079] dhcp4 (eth0): state changed timeout -> done
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8086] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8091] manager: NetworkManager state is now DISCONNECTED
Jul 07 18:35:47 toromachine NetworkManager[19050]: <warn>  [1499477747.8098] device (eth0): Activation: failed for connection 'eth0'
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8113] device (eth0): state change: failed -> disconnected (reason 'none') [120 30 0]
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8151] policy: auto-activating connection 'eth0'
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8166] device (eth0): Activation: starting connection 'eth0' (e7361020-1796-4583-aab9-9d479aac94fe)
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8167] device (eth0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8168] manager: NetworkManager state is now CONNECTING
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8170] device (eth0): state change: prepare -> config (reason 'none') [40 50 0]
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8180] device (eth0): state change: config -> ip-config (reason 'none') [50 70 0]
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8182] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jul 07 18:35:47 toromachine NetworkManager[19050]: <info>  [1499477747.8206] dhcp4 (eth0): dhclient started with pid 22043
Jul 07 18:35:47 toromachine dhclient[22043]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x15238503)
Jul 07 18:35:50 toromachine dhclient[22043]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 (xid=0x15238503)
Jul 07 18:35:55 toromachine dhclient[22043]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x15238503)
Jul 07 18:36:04 toromachine dhclient[22043]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0x15238503)
Jul 07 18:36:15 toromachine dhclient[22043]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 (xid=0x15238503)
Jul 07 18:36:32 toromachine NetworkManager[19050]: <warn>  [1499477792.7707] dhcp4 (eth0): request timed out
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7708] dhcp4 (eth0): state changed unknown -> timeout
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7874] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 22043
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7875] dhcp4 (eth0): state changed timeout -> done
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7881] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7885] manager: NetworkManager state is now DISCONNECTED
Jul 07 18:36:32 toromachine NetworkManager[19050]: <warn>  [1499477792.7891] device (eth0): Activation: failed for connection 'eth0'
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7902] device (eth0): state change: failed -> disconnected (reason 'none') [120 30 0]
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7937] policy: auto-activating connection 'eth0'
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7945] device (eth0): Activation: starting connection 'eth0' (e7361020-1796-4583-aab9-9d479aac94fe)
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7954] device (eth0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7955] manager: NetworkManager state is now CONNECTING
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7958] device (eth0): state change: prepare -> config (reason 'none') [40 50 0]
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7969] device (eth0): state change: config -> ip-config (reason 'none') [50 70 0]
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7971] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jul 07 18:36:32 toromachine NetworkManager[19050]: <info>  [1499477792.7984] dhcp4 (eth0): dhclient started with pid 22057

          
$ cat /var/lib/NetworkManager/NetworkManager.state

[main]
NetworkingEnabled=true
WirelessEnabled=false
WWANEnabled=true
WimaxEnabled=true


$ sudo dhcpdump -i eth0

  TIME: 2017-07-07 18:45:11.570
    IP: 0.0.0.0 (28:f1:e:48:52:d2) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
    OP: 1 (BOOTPREQUEST)
 HTYPE: 1 (Ethernet)
  HLEN: 6
  HOPS: 0
   XID: 04f7d201
  SECS: 39
 FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 28:f1:0e:48:52:d2:00:00:00:00:00:00:00:00:00:00
 SNAME: .
 FNAME: .
OPTION:  53 (  1) DHCP message type
1 (DHCPDISCOVER)
OPTION: 12 ( 11) Host name
toromachine
OPTION: 55 ( 18) Parameter Request List
1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
119 (Domain Search)
12 (Host name)
44 (NetBIOS name server)
47 (NetBIOS scope)
26 (Interface MTU)
121 (Classless Static Route)
42 (NTP servers)
121 (Classless Static Route)
249 (MSFT - Classless route)
33 (Static route)
252 (MSFT - WinSock Proxy Auto Detect)
42 (NTP servers)
 
Old 08-09-2017, 08:40 AM   #2
Jjanel
Member
 
Registered: Jun 2016
Distribution: any&all, in VBox; Ol'UnixCLI; NO GUI resources
Posts: 999
Blog Entries: 12

Rep: Reputation: 364Reputation: 364Reputation: 364Reputation: 364
Hi & belated welcome to LQ. Sorry you didn't get an answer here

Looks like it got solved over here! Great!
Quote:
It was an issue with the DHCP of the university.
My computer was not allowed to be connected to the DHCP anymore.
I hope you give LQ another 'try', with a future question. Best wishes always!
 
1 members found this post helpful.
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Ethernet connection failure with different router/modem. zmpetro Linux - Networking 2 11-29-2011 03:42 PM
Ubuntu Nvidia / CUDA driver installation gourox Linux - Hardware 1 08-14-2009 12:36 AM
CUDA on Jaunty, Installation successful, but cannot run? beaute Ubuntu 0 06-01-2009 04:42 AM
Motherboard ethernet connection failure with SuSe Linux 10.1 sfzab Linux - Hardware 2 07-17-2007 02:07 PM
Ethernet Failure spaaarky21 Linux - Hardware 4 02-03-2005 12:33 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware > Linux - Embedded & Single-board computer

All times are GMT -5. The time now is 03:42 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration