Overo Tobi Ethernet - Revision history

Searchworks: remove spam

2010-11-23T23:01:12Z

remove spam

Aqisecoxefi at 22:36, 23 November 2010

2010-11-23T22:36:50Z

Searchworks: remove spam

2010-11-11T06:23:09Z

remove spam

Gaoerer at 03:17, 11 November 2010

2010-11-11T03:17:17Z

Msvilans at 20:23, 21 July 2010

2010-07-21T20:23:45Z

Msvilans at 19:46, 21 July 2010

2010-07-21T19:46:47Z

Msvilans at 19:46, 21 July 2010

2010-07-21T19:46:26Z

Msvilans at 17:06, 21 July 2010

2010-07-21T17:06:35Z

Msvilans at 17:00, 21 July 2010

2010-07-21T17:00:45Z

Msvilans at 16:58, 21 July 2010

2010-07-21T16:58:24Z

@@ Line 1: / Line 1: @@
 [[Category:How_to_-_ethernet]]
 Some Overo boards do not properly bring up the eth0 wired Ethernet interface when booting up with the Tobi expansion board. The result is that the Overo will not have a working wired Ethernet connection after booting, even though you may have eth0 properly configured in ''/etc/network/interfaces''. The problem appears to be caused by a version mismatch between the ''dhclient'' and ''ifupdown'' packages on the Overo images.
@@ Line 20: / Line 19: @@
 After you have eth0 configured, reboot your Overo. You should see the following messages during boot:
-&lt;pre&gt;
+<pre>
 Configuring network interfaces... net eth0: SMSC911x/921x identified at 0xd08cc000, IRQ: 336
 eth0      no wireless extensions.
@@ Line 28: / Line 27: @@
 All rights reserved.
 For info, please visit http://www.isc.org/sw/dhcp/
-Usage: dhclient [-1dqrx] [-nw] [-p &lt;port&gt;] [-s server]
+Usage: dhclient [-1dqrx] [-nw] [-p <port>] [-s server]
                  [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val]
                  [-sf script-file] [interface]
@@ Line 50: / Line 49: @@
 Failed to bring up eth0.
 done.
-&lt;/pre&gt;
+</pre>
 Even though you have eth0 configured properly, ''ifup'' fails to bring up the eth0 interface.
@@ Line 60: / Line 59: @@
 The ''ifupdown'' package source code has a file named ''inet.defn''. Here are lines 76 through 81 from that file:
-&lt;pre&gt;
+<pre>
 :  up
 :    [[ifconfig %iface% hw %hwaddress%]]
 :    dhclient3 -pf /var/run/dhclient.%iface%.pid -lf /var/lib/dhcp3/dhclient.%iface%.leases %iface% \
-:        if (execable(&quot;/sbin/dhclient3&quot;))
+:        if (execable("/sbin/dhclient3"))
 :    dhclient -v -pf /var/run/dhclient.%iface%.pid -lf /var/lib/dhcp/dhclient.%iface%.leases %iface% \
-:        elsif (execable(&quot;/sbin/dhclient&quot;))
+:        elsif (execable("/sbin/dhclient"))
-&lt;/pre&gt;
+</pre>
 As you can see, if ''dhclient3'' is not found on the system, then at line 80 ''dhclient'' is invoked with the -v flag. This is the problem, because the Overo image has ''/sbin/dhclient'', not ''/sbin/dhclient3''. The ''dhclient'' version on the Overo image does not support the -v flag, and this is why the error message appears during boot, and the eth0 interface does not get initialized.
@@ Line 77: / Line 76: @@
 The solution is to create a symlink to trick ''ifup'':
-&lt;pre&gt;
+<pre>
 ln -s /sbin/dhclient3 /sbin/dhclient
-&lt;/pre&gt;
+</pre>
 This way, the ''inet.defn'' code will see that ''dhclient3'' is present, and (via the symlink) it will call ''dhclient'' without the troublesome -v flag.
 Now when you boot the Overo, you should no longer get the error messages. Instead, eth0 should successfully get an IP address via DHCP and you should have a working wired Ethernet connection.

@@ Line 1: / Line 1: @@
 [[Category:How_to_-_ethernet]]
 Some Overo boards do not properly bring up the eth0 wired Ethernet interface when booting up with the Tobi expansion board. The result is that the Overo will not have a working wired Ethernet connection after booting, even though you may have eth0 properly configured in ''/etc/network/interfaces''. The problem appears to be caused by a version mismatch between the ''dhclient'' and ''ifupdown'' packages on the Overo images.
@@ Line 19: / Line 20: @@
 After you have eth0 configured, reboot your Overo. You should see the following messages during boot:
-<pre>
+&lt;pre&gt;
 Configuring network interfaces... net eth0: SMSC911x/921x identified at 0xd08cc000, IRQ: 336
 eth0      no wireless extensions.
@@ Line 27: / Line 28: @@
 All rights reserved.
 For info, please visit http://www.isc.org/sw/dhcp/
-Usage: dhclient [-1dqrx] [-nw] [-p <port>] [-s server]
+Usage: dhclient [-1dqrx] [-nw] [-p &lt;port&gt;] [-s server]
                  [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val]
                  [-sf script-file] [interface]
@@ Line 49: / Line 50: @@
 Failed to bring up eth0.
 done.
-</pre>
+&lt;/pre&gt;
 Even though you have eth0 configured properly, ''ifup'' fails to bring up the eth0 interface.
@@ Line 59: / Line 60: @@
 The ''ifupdown'' package source code has a file named ''inet.defn''. Here are lines 76 through 81 from that file:
-<pre>
+&lt;pre&gt;
 :  up
 :    [[ifconfig %iface% hw %hwaddress%]]
 :    dhclient3 -pf /var/run/dhclient.%iface%.pid -lf /var/lib/dhcp3/dhclient.%iface%.leases %iface% \
-:        if (execable("/sbin/dhclient3"))
+:        if (execable(&quot;/sbin/dhclient3&quot;))
 :    dhclient -v -pf /var/run/dhclient.%iface%.pid -lf /var/lib/dhcp/dhclient.%iface%.leases %iface% \
-:        elsif (execable("/sbin/dhclient"))
+:        elsif (execable(&quot;/sbin/dhclient&quot;))
-</pre>
+&lt;/pre&gt;
 As you can see, if ''dhclient3'' is not found on the system, then at line 80 ''dhclient'' is invoked with the -v flag. This is the problem, because the Overo image has ''/sbin/dhclient'', not ''/sbin/dhclient3''. The ''dhclient'' version on the Overo image does not support the -v flag, and this is why the error message appears during boot, and the eth0 interface does not get initialized.
@@ Line 76: / Line 77: @@
 The solution is to create a symlink to trick ''ifup'':
-<pre>
+&lt;pre&gt;
 ln -s /sbin/dhclient3 /sbin/dhclient
-</pre>
+&lt;/pre&gt;
 This way, the ''inet.defn'' code will see that ''dhclient3'' is present, and (via the symlink) it will call ''dhclient'' without the troublesome -v flag.
 Now when you boot the Overo, you should no longer get the error messages. Instead, eth0 should successfully get an IP address via DHCP and you should have a working wired Ethernet connection.

@@ Line 1: / Line 1: @@
 [[Category:How_to_-_ethernet]]
 Some Overo boards do not properly bring up the eth0 wired Ethernet interface when booting up with the Tobi expansion board. The result is that the Overo will not have a working wired Ethernet connection after booting, even though you may have eth0 properly configured in ''/etc/network/interfaces''. The problem appears to be caused by a version mismatch between the ''dhclient'' and ''ifupdown'' packages on the Overo images.
 =Software=

@@ Line 1: / Line 1: @@
 [[Category:How_to_-_ethernet]]
 Some Overo boards do not properly bring up the eth0 wired Ethernet interface when booting up with the Tobi expansion board. The result is that the Overo will not have a working wired Ethernet connection after booting, even though you may have eth0 properly configured in ''/etc/network/interfaces''. The problem appears to be caused by a version mismatch between the ''dhclient'' and ''ifupdown'' packages on the Overo images.
 =Software=

@@ Line 68: / Line 68: @@
 </pre>
-As you can see, if ''dhclient3'' is not found on the system, then at line 80 ''dhclient'' is invoked with the -v flag. This is the problem, because the Overo image has ''/sbin/dhclient'', not ''/sbin/dhclient3''. The ''dhclient'' version on the Overo image does not support the -v flag, and this is why the error message appears during boot.
+As you can see, if ''dhclient3'' is not found on the system, then at line 80 ''dhclient'' is invoked with the -v flag. This is the problem, because the Overo image has ''/sbin/dhclient'', not ''/sbin/dhclient3''. The ''dhclient'' version on the Overo image does not support the -v flag, and this is why the error message appears during boot, and the eth0 interface does not get initialized.
 ===Solution===

@@ Line 57: / Line 57: @@
 The above errors during boot appear to be caused by some kind of version mismatch between the ''dhclient'' and ''ifupdown'' packages installed in the Overo images.
-The ''ifupdown'' source code has a file named ''inet.defn''. Here are lines 76 through 81 from that file:
+The ''ifupdown'' package source code has a file named ''inet.defn''. Here are lines 76 through 81 from that file:
 <pre>

← Older revision		Revision as of 19:46, 21 July 2010
Line 58:		Line 58:

	The ''ifupdown'' source code has a file named ''inet.defn''. Here are lines 76 through 81 from that file:		The ''ifupdown'' source code has a file named ''inet.defn''. Here are lines 76 through 81 from that file:
−
−	~~If you look in the ifupdown package source code, there is a file called "inet.defn". Here are lines 76 through 81 from that file:~~

	<pre>		<pre>

@@ Line 13: / Line 13: @@
    iface eth0 inet dhcp
-Usually the above configuration is already present, you just have to uncomment it.
+The above configuration should already be there, you would just have to uncomment it.
 ==Boot Messages==

@@ Line 51: / Line 51: @@
 </pre>
-Even though you have eth0 configured properly, ''ifup'' fails to bring up the eth0 interface due to a version mismatch with ''dhclient''.
+Even though you have eth0 configured properly, ''ifup'' fails to bring up the eth0 interface.
 ==Apparent Version Mismatch Problem==
-There appears to be some kind of mismatch between the ''dhclient'' and ''ifupdown'' packages installed in the Overo images.
+The above errors during boot appear to be caused by some kind of version mismatch between the ''dhclient'' and ''ifupdown'' packages installed in the Overo images.
 The ''ifupdown'' source code has a file named ''inet.defn''. Here are lines 76 through 81 from that file: